Network Drive Testing (preparation, glossary, hints)

I came across a great presentation about drive testing by using TEMS Investigation. This presentation was prepared by edukasipro. It includes:

  • Preparations before drive test
  • Glossary for telecommunication abbreviations
  • Explanations for common issues such as “handover”, “swap feeder”, “overshoot”
  • TEMS Investigation screens and hints

Here is: http://www.scribd.com/doc/105341886/Tems-Investigation-Training

Solved: “Failed to start IP sniffer” error on TEMS Investigation

We use equipments such as data cards, mobile phones, scanners to log network activity on TEMS Investigation. You may face an error when you try to start the script which uses your equipments activated:

Status: Failed
Unknown error, Failed to start IP sniffer

IP sniffer error

Workaround

IP sniffing is required to collect data that will become inputs for KPIs (Key Performance Indicators). KPIs are used for measuring user-preceived performance of CS (circuit-switched) and PS (packet-switched) services. Examples for KPIs are data transfer time, attach failure ratio, network unavailability etc.

IP sniffer error

Workaround

IP sniffing is required to collect data that will become inputs for KPIs (Key Performance Indicators). KPIs are used for measuring user-preceived performance of CS (circuit-switched) and PS (packet-switched) services. Examples for KPIs are data transfer time, attach failure ratio, network unavailability etc.

If your data collecting device is unable to perform IP sniffing, you can deactivate this feature to avoid the error above.

Solution

  • Open the config file of TEMS Investigation. It generally stays in this directory: C:\Program Files (x86)\Ascom\TEMS Products\TEMS Investigation\Application\ Investigation.exe.config
  • Change the parameters that you need in this line:

    <dataServicesConfiguration ipSniffEnabled="true" ignoreIPSniffError="false" />
    • If you just want to ignore errors,  set ignoreIPSniffError parameter to “true”
    • If you want to disable IP sniffing, set ipSniffEnabled parameter to “false”

Solved: “Error 734: The PPP Link Control Protocol Was Terminated” on TEMS Investigation

While you are trying to have a call on a mobile phone connected to TEMS Investigation, you may face an error like this:

An error concerning RAS occured, State AuthNotify. 734.0: The PPP link control protocol was terminated

The PPP link control protocol was terminated.

Indeed, this isn’t a specific problem for TEMS, see below.

The PPP link control protocol was terminated.

Indeed, this isn’t a specific problem for TEMS, see below.

Solution 1

This is a common problem for Point-to-Point Protocol (PPP) dial-up connection. So, Microsoft has a help page for that. It says:

  1. Click Start, point to Settings, and then click Network and Dial-up Connections.
    NOTE: For Windows Server 2003, click Start, point to Control Panel, and then point to Network Connections.
  2. Right-click the appropriate dial-up networking connection, and then click Properties.
  3. Click the Networking tab, and then click Settings.
  4. Click to clear the Negotiate multi-link for single link connections check box (if it is selected).
  5. Click OK, and then click OK.
  6. Double-click the connection, and then click Dial.
    • If this procedure resolves the issue and you can establish a dial-up connection, you do not have to follow the remaining steps in this article.
    • If this does not resolve the issue and you cannot establish a dial-up connection, go to step 7 to continue to troubleshoot this issue.
  7. Right-click the connection, and then click Properties.
  8. Click the Security tab.
  9. Under Security options, click Allow unsecured password in the Validate my identity as follows box, and then click OK.
  10. Double-click the connection, and then click Dial to verify that you can establish a dial-up connection.

Solution 2

If the first resolution doesn’t work, try this one. There is useful information about this problem in TEMS Investigation help file:

  1. Click Start, point to Settings, and then click Network and Dial-up Connections.
    NOTE: For Windows Server 2003, click Start, point to Control Panel, and then point to Network Connections.
  2. Right-click the appropriate dial-up networking connection, and then click Properties.
  3. Click the Networking tab, and then click Settings.
  4. Click to clear the Negotiate multi-link for single link connections check box (if it is selected).
  5. Click OK, and then click OK.
  6. Double-click the connection, and then click Dial.
    • If this procedure resolves the issue and you can establish a dial-up connection, you do not have to follow the remaining steps in this article.
    • If this does not resolve the issue and you cannot establish a dial-up connection, go to step 7 to continue to troubleshoot this issue.
  7. Right-click the connection, and then click Properties.
  8. Click the Security tab.
  9. Under Security options, click Allow unsecured password in the Validate my identity as follows box, and then click OK.
  10. Double-click the connection, and then click Dial to verify that you can establish a dial-up connection.

Solution 2

If the first resolution doesn’t work, try this one. There is useful information about this problem in TEMS Investigation help file:

Possible causes:

  • PDP Context Activation failure. See the Activate PDP Context Reject message in the Layer 3 Messages window for the cause value.
  • The phone lacks an APN for the network. Try setting the APN by sending the following command to the phone: AT+CGDCONT=1, “IP”,”my_server.com” (replace the final string by the correct URL).

In order to get information how to send AT command, check my previous post out. Also you’ll need the APN address. For AT&T users, check this page out.