You are on page 1of 21

Prepared by: Date: Document

:
Ascom Network Testing 22 June 2011 NT11-12547



© Ascom (2011)
All rights reserved. TEMS is a trademark of Ascom. All other trademarks are the property of their respective holders.




TEMS Investigation 13.0 Local Edition
Release Note














© Ascom (2011) Document:
NT11-12547


Contents
1 About This Release ................................................... 1
2 Important Information ............................................... 1
3 New Features.............................................................. 1
3.1 TD-LTE Support ........................................................................1
3.2 Data Service Performance Verification with Generic
Device ........................................................................................1
3.1 Selection of Preferred Workspace at Startup .........................1
3.2 New Utility for Sharing Script Configuration Settings ...........2
3.3 New LTE Information Elements ...............................................2
3.4 New Connectable Equipment ...................................................2
3.4.1 User Terminals ...........................................................................2
3.4.2 LTE Scanner: Rohde & Schwarz TSMW .....................................3
3.5 Support for SSH2 Protocol in Iperf Testing ............................3
3.6 Support for 64-bit Windows 7 ..................................................3
3.7 Performance Improvements.....................................................3
3.8 Additional New Features ..........................................................4
3.9 Corrected Bugs .........................................................................4
4 Enhancements ........................................................... 4
5 Known Bugs and Limitations ................................... 5
5.1 PC Application Related ............................................................5
5.1.1 Installation and Start-up ..............................................................5
5.1.2 Application Use ...........................................................................6
5.1.3 Windows 7 Specific .....................................................................9
5.1.4 Windows Vista Specific ...............................................................9
5.2 Device Related ..........................................................................9
5.2.1 Network Connect ........................................................................9
5.2.2 General .......................................................................................9
5.3 Phone Related .........................................................................10
5.3.1 General .....................................................................................10
5.3.2 Sony Ericsson (Android) ...........................................................11
5.3.3 Sony Ericsson (R13) .................................................................11
5.3.4 Qualcomm Chipset Based Phones and PC Cards ....................12
5.3.5 Samsung Devices Based on Samsung Chipset ........................13
5.3.6 Nokia NTM3 Phones .................................................................14
5.4 AQM Module Related ..............................................................14
5.5 Scanner Related......................................................................15





© Ascom (2011) Document:
NT11-12547


5.5.1 General .....................................................................................15
5.5.2 SRU ..........................................................................................15
5.5.3 DRT 4301/4301A/4301A+ .........................................................16
5.5.4 PCTel SeeGull LX/EX ...............................................................16
5.5.5 PCTel SeeGull MX....................................................................17
5.5.6 PCTel SeeGull PCT ..................................................................17
5.6 GPS Related ............................................................................17
5.7 Call Generator Related ...........................................................17
5.8 TEMS UDP Server Related .....................................................18
6 Contact Information ................................................. 18
7 Appendix................................................................... 18






© Ascom (2011) Document:
NT11-12547 1(18)


1 About This Release
Release date: 6 July 2011
2 Important Information
A local edition of TEMS Investigation will operate only in cellular
networks located within the country or region given by the product name.
3 New Features
3.1 TD-LTE Support
The LTE standard allows both frequency division duplex (FDD) and time
division duplex (TDD) operation. So far, LTE support in TEMS Investigation
has been restricted to FDD; however, TEMS Investigation 13.0 introduces
scanning support also for the TDD mode, known as TD-LTE. Using a
Rohde & Schwarz TSMW Universal Radio Network Analyzer, it is possible
to do Top-N LTE signal scanning in both TDD and FDD mode. Any LTE
frequency band can be scanned. The data set obtained is similar to FDD
and includes RSRP, RSRQ, and SCH CINR.
3.2 Data Service Performance Verification with
Generic Device
TEMS Investigation 13.0 expands the concept of data service testing,
taking it to a whole new level of genericity. Data service testing can now be
undertaken with any off-the-shelf device as long as it comes with Windows
drivers that enable an IP data connection – for example, iPhone or
BlackBerry units, or a wide variety of network cards, USB modems,
embedded modules, etc.
This feature can be used to verify application layer performance for
arbitrary devices, as will be desirable prior to launching them in the
network. Any IP-based activity in the Service Control Designer, as well as
video streaming, can be run on such a device, and all IP information
elements will be populated.
Please note that lower-layer data (RF, Layer 2, Layer 3) is not obtained
with this kind of testing.
3.3 Selection of Preferred Workspace at Startup
When you start TEMS Investigation, you are now invited to select what
workspace to use: one recently used, some other existing workspace, or a
new one that is empty.





© Ascom (2011) Document:
NT11-12547 2(18)


3.4 New Utility for Sharing Script Configuration
Settings
The TEMS Settings Manager is a new utility which lets you save to file any
service and scanner settings that are used for service testing. For example,
such a file may contain all details of how to perform an LTE Reference
Signal scan with a PCTel MX scanner, or all the parameters needed to
access and interact with a particular FTP server. The TEMS Settings
Manager boosts usability by enabling easy distribution of configuration data
among users and among instances of TEMS Investigation.
The utility can also be seen as a complement to the script saving function in
the Service Control Designer, which creates files specifying the activities to
perform during testing.
Here is an overview of how to share configuration sets between computers:
 On the “sender” PC:
 Save workspace.
 Save script as redistributable script.
 Export configuration sets.
 On the “receiver” PC (with above data from sender available on some
suitable storage medium):
 Import configuration sets exported from sender.
 Start TEMS Investigation.
 Open sender’s workspace.
 Open sender’s script. The script can now be not only run but also
freely modified on the receiver PC.
3.5 New LTE Information Elements
With LG devices, a range of new LTE information elements are obtained,
including PDSCH Transmission Distribution, PBCH BLER, and PUSCH
BLER. Furthermore, many LTE elements previously available with LG are
now also offered with Qualcomm devices.
3.6 New Connectable Equipment
3.6.1 User Terminals
 Sony Ericsson Xperia arc (Android-based smartphone):
Note: Regarding driver installation for this phone, see section 5.3.2.
 GSM/EDGE 850/900/1800/1900
 WCDMA/HSPA 900/2100 (LT15i)
 WCDMA/HSPA 800/850/1900/2100 (LT15a)





© Ascom (2011) Document:
NT11-12547 3(18)


 HSDPA Category 8 (7.2 Mbit/s), HSUPA Category 5 (2.0 Mbit/s)
 Nokia C7-00
 WCDMA/HSPA 850/900/1700/1900/2100 MHz
 GSM/GPRS/EDGE 850/900/1800/1900 MHz
 HSDPA Category 9 (10.2 Mbit/s), HSUPA Category 5 (2.0 Mbit/s)
 HTC Imagio
 Digital Dual (CDMA, PCS) / 1x, EV-DO Rev A
 GSM quad-band (GSM/GPRS/EDGE)
 WCDMA/HSDPA/HSUPA
 ZTE MF683
3.6.2 LTE Scanner: Rohde & Schwarz TSMW
The R&S TSMW Universal Radio Network Analyzer enables TD-LTE
measurements in TEMS Investigation 13.0.
Scanner capabilities include:
 Support for all LTE frequency bands: 30 MHz to 6 GHz
 Top N LTE signal scanning for TDD as well as FDD
The R&S TSMW scanner handles a range of other technologies, and
support for these is planned for inclusion in future releases of TEMS
Investigation. Such technology expansions will then be possible to do
remotely by means of a scanner software upgrade.
3.7 Support for SSH2 Protocol in Iperf Testing
The SSH2 protocol (Secure Shell version 2) is now offered as an
alternative to Telnet as connection client when doing Network Bandwidth
testing with Iperf. Unlike the Telnet protocol, which sends logins and
passwords in plain text, SSH2 uses cryptography to authenticate the
remote computer and therefore renders the Iperf server less vulnerable to
hacker attacks.
SSH2 requires a separate license option and installation package, since it
is subject to export restrictions due to its use of strong encryption.
3.8 Support for 64-bit Windows 7
TEMS Investigation 13.0 can be run under 64-bit Windows 7.
3.9 Performance Improvements
For any given device configuration and test setup, TEMS Investigation 13.0
generates lower CPU load than previous versions. Other improvements
include better memory management and reduced start-up time.





© Ascom (2011) Document:
NT11-12547 4(18)


3.10 Additional New Features
 Internal GPS of PCTel MX available as data source in TEMS
Investigation
 UMTS network connect can be done from within TEMS Investigation
with Samsung GT-B3730, GT-B3740 LTE/UMTS dual-technology
devices
3.11 Corrected Bugs

4 Enhancements
Regarding support for new devices, please see chapter 3.
 Support added for DRT 4301/4301A/4301A+ firmware version 2.03.0.
 Support added for trace files from Ericsson BSS with firmware
version MTRFIL (1/190 83-CNT 248 1109), rev S.
 Support added for DIGI HubPort (7 port, 5.5–30 V DC powered USB 2.0
hub non-captive connector).





© Ascom (2011) Document:
NT11-12547 5(18)


5 Known Bugs and Limitations
5.1 PC Application Related
5.1.1 Installation and Start-up
 When installing TEMS Investigation for the first time, it may take 10–20
minutes for the installation to complete (if .NET Framework 4.0 was not
already present on the PC). On some PCs, a reboot may take place
after the .NET Framework installation.
 In the course of the TEMS Investigation 13.0 installation, if the HASP
key contains HASP SRM version 4 firmware, it will be upgraded to SRM
version 5. While the upgrade is in progress, this is indicated by the
HASP key LED blinking. If the blinking does not stop within one minute,
the firmware upgrade has failed. You then need to restart the Sentinel
HASP License Manager service in Windows, or reboot the PC.
 The application start-up time may be prolonged if slow network shares
are mounted on the machine.
 For the license attach/detach mechanism in the Admin Control Center
to work correctly, the Sentinel HASP License Manager on the license
server and client machines must be of the same version. Always
crosscheck the versions manually to avoid attach/detach failures.
 If TEMS Investigation takes a long time to start up (more than about 45
seconds), the delay may be caused by the OS trying unsuccessfully to
check the application’s Verisign certificate. If a network has been
detected, the OS will try to contact Verisign to verify that the certificate
is not on the Certificate Revocation List (CRL). TEMS Investigation will
not continue until this procedure times out.
There are two ways to remedy this:
1) Open up your proxy to enable access to the Certificate Revocation
List. The details of how to accomplish this may vary between
countries.
2) Turn off the certificate revocation check in Internet Explorer:
 Open Internet Explorer, and from the Tools menu select Internet
Options.
 On the Advanced tab, under Security, uncheck the option “Check
for publisher’s certificate revocation” and click Apply.
(This procedure can be automated by the use of Group Policies.)
 When installing TEMS Investigation under Chinese or Japanese
Windows, TEMS Investigation will not recognize file paths such as
C:\User\<user name>\..., where <user name> contains Chinese or
Japanese characters. This will prevent proper use of the application.
(Similar problems may occur with other non-ASCII characters.)





© Ascom (2011) Document:
NT11-12547 6(18)


5.1.2 Application Use
Note: PC settings and hardware capabilities that are checked by the
Computer Diagnostics utility are not covered here. See the Getting
Started Manual, chapter 7.
 User-created workspaces from previous versions of TEMS Investigation
need to be recreated. New workspaces are supplied with the
application.
 When using the Copy Worksheet function, any Map settings will be lost.
 When many devices are used for data collection, the number of
windows in the workspace should be kept to a minimum to lower the
CPU load. It is also advisable to start a new logfile recording at least
once every hour in order to reduce RAM consumption.
 The XML cell file format permits only “YYYY-MM-DD” as date format.
 A separately powered USB 2.0 hub is strongly recommended for drive
tests. That is, the USB hub should not be powered through the USB
port alone. Depending on the type and number of devices connected,
the hub may otherwise not be able to deliver sufficient power. It needs
also to be stressed that an uninterrupted USB connection between PC
and device is vital for successful recording of realtime measurement
data.
 Some GPS units may be erroneously identified in Windows as an “MS
Serial Ballpoint” device. If this occurs, perform the following steps:
1) With Administrator privileges on the PC, choose Start > Run >
regedit.
2) Navigate to HKEY_LOCAL_MACHINE > System > Current Control
Set > Services > sermouse.
3) Locate the entry “Start” and double-click on it.
4) Change the value Data from 3 to 4. This will prevent Windows from
identifying the GPS device as a mouse. Note, however, that leaving
the setting Data = 4 will prevent you from identifying new mouse
devices until you change the value back to 3.
 During logfile recording as well as during logfile replay, temporary files
are created by the application to enable the user to browse the history
of the logfile. These files can become very large (3–4 times the logfile
size), the exact size depending on the number of devices activated in
the application at recording time. The temporary files are named
according to the format “temsn” and created in the Windows temp
directory (default: C:\path\tmp, where the path is defined by the
environment variable TMP; in Windows XP, the TMP variable can be
modified from the Control Panel: System Properties > Advanced >
Environment Variables). Make sure there is plenty of space on the disk
where the temp directory resides. The temporary files are removed
when you exit the application; however, if the application terminates





© Ascom (2011) Document:
NT11-12547 7(18)


abnormally, this might not happen. The files must then be removed
manually.
 When using the pinpointing function, you must click the Pinpoint button
before starting logfile recording, not the other way around.
 When a Network Connect activity is executed in a Service Control
script, a restricted form of IP sniffing is started which is performed
continuously for the sake of collecting input to KPI calculations. If your
data collecting device is unable to perform the IP sniffing (example:
Sierra Wireless USB 306/307 connected via NDIS under Windows 7),
you can work around the problem by editing a line in the file <TEMS
Investigation install dir>\Application\Investigation.exe.config, which by
default reads: <dataServicesConfiguration ipSniffEnabled="true"
ignoreIPSniffError="false" />. You can either disable IP sniffing by
setting ipSniffEnabled="false" (and consequently miss out on KPI data),
or you can ignore failure to start IP sniffing and go ahead with the
execution anyway: ignoreIPSniffError="true". By the latter method you
obtain KPIs normally for all devices where the IP sniffing does not fail.
 Service Control Designer: To copy, cut, and paste material in text fields,
use the context menu in the text field. The keyboard accelerators
Ctrl + C, etc. cannot be used for this purpose.
 Service Control Designer: In a script workflow, it is not possible to
collapse the individual branches (Sequence activities) of a Parallel
activity. Only the Parallel activity as a whole can be collapsed.
 Service Control Designer: If multiple Service Control Designers are
open simultaneously, a script run from one of them could fail.
 When you save a Service Control script to file, any user names and
passwords (e.g. for FTP or HTTP servers) given in commands are
saved with the file (encrypted). Note that another user who runs your
script will be accessing the server using the same user name and
password.
 When running video telephony from a Service Control script, the phone
needs to be locked on WCDMA.
 UDP upload testing causes very high CPU load.
 When using the serving cell indication in the Map window to show the
strongest scanned CPICH, this works only for the 1st UMTS frequency
(the one decoded into the information elements named “1st”).
 The Channel Verification tool causes the Sony Ericsson W600i phone to
be deactivated, and moreover it cannot be reactivated until the
application has been restarted.
 PESQ is not computed for the AMR-WB speech codec.
 When turning on all extended logs for Sony Ericsson and Qualcomm
chipset based devices (without turning off something else), the data
volume logged will be huge, and it may be necessary to swap logfiles
more often than once every hour to prevent RAM usage from becoming
excessive.





© Ascom (2011) Document:
NT11-12547 8(18)


 Logfiles merged with uplink data (MTR) files may contain internal
reports with erroneous timestamps.
 The phone must be locked to GSM when performing GSM Channel
Verification with a WCDMA capable phone. How to set this lock (on
Radio Access Technology) is described in the User’s Manual,
section 8.1.6.
 SMS and MMS testing with Service Control scripts does not work for
CDMA devices that do not support AT commands.
 IP packet capture/analysis may stop after less than one minute when
using multiple CDMA phones.
 During video streaming, if stripes appear in the picture, try changing the
color setting to 16 colors in the Windows display settings.
 Whenever possible, logfile swapping should be done in idle mode.
 After swapping logfiles, a Network Connect activity must be recorded at
the beginning of the new one for average throughputs to be calculated.
 The Swap Logfiles function does not work properly if used during
scanning.
 If you swap logfiles while running the Status Control Monitor, the Logfile
Progress indicator turns red, and the message “No records written to
file” appears. After a few updates, Logfile Progress is indicated
correctly.
 If Iperf is installed on a Linux/Unix server, the network port on that
server must be mapped to terminal vt100.
Map the port by editing a line in /etc/profile:
tset -I -Q -m network:vt100
An incorrect mapping will cause the following error:
tset: unknown terminal type network
Terminal type?
 If Iperf is installed on a Linux/Unix server, the PS1 variable must be
changed to PS1=”>” in the Unix shell Bash in order for Iperf information
to be correctly displayed.
 If Iperf is installed on a Linux/Unix server, then to enable the use of
passwords in Iperf testing, make sure the default setting for passwords
(PasswordAuthentication yes) is used in the configuration file on the
SSH server /etc/ssh/sshd_config.
 The waveform in Network Bandwidth line charts will be jagged and not
smooth, due to the low resolution of the Iperf process.
 Full IP sniffing can only be done with one device at a time. If full IP
sniffing with more than one device is attempted, TEMS Investigation will
stop working correctly.
 Full IP sniffing is not recommended in high data rate scenarios (say,
> 25 Mbit/s).





© Ascom (2011) Document:
NT11-12547 9(18)


 IP sniffing (unless restricted using the “Optimized Performance” option)
cannot be turned on while doing data service testing at throughputs
above 25 Mbit/s. If turned on, it will cause TEMS Investigation to crash.
 The information element LTE Total RS Power is valid only for the
bandwidths 5 MHz and 10 MHz.
5.1.3 Windows 7 Specific
 Under 64-bit Windows 7 (x64), the Investigation.exe file must be
excluded from virus scanning to avoid a known issue with the Sentinel
HASP driver. The problem does not arise with 32-bit (x86) Windows 7
installations.
 User Access Control needs to be turned off to allow IP trace. It may also
need to be disabled for other reasons, depending on its configuration.
5.1.4 Windows Vista Specific
 User Access Control needs to be turned off to allow IP trace. It may also
need to be disabled for other reasons, depending on its configuration.
 When starting the GeoSet Manager, an error message about writing to
the Windows registry appears; however, .gst files can still be created.
5.2 Device Related
5.2.1 Network Connect
 Some LTE devices must be connected to the network manually, using
their connection managers, rather than automatically in the Service
Control script. This applies to:
 Samsung R900 (in LTE mode)
 Most Qualcomm LTE devices (e.g. Huawei E398, Pantech UML
290, Qualcomm FFAs, ZTE)
 For Samsung GT-B3710 without AT port, the connection manager must
be started to enable the Network Connect activity in Service Control.
Note that when the network connect is performed manually, a Network
Connect activity must still be included in the Service Control script for the
subsequent data service activities to execute correctly.
5.2.2 General
 In Windows XP, some issues with poor uplink and downlink throughput
can be resolved by manually adjusting the TCP window size. This
setting is found in the registry under:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\
Parameters\





© Ascom (2011) Document:
NT11-12547 10(18)


The ideal TCP window size for a given maximum bit rate is dependent
on the network delay. Here is an example showing how to do the
calculation.
Suppose that:
Maximum bit rate = 3.6 Mbit/s
Network delay = 500 ms
Maximum Segment Size (MSS) = Maximum Transmission Unit (MTU) –
header size = 1500 – 40 = 1460 bytes
Then:
Bandwidth-delay product (BDP) = 3.6 × 10
6
bit/s × 500 × 10
–3
s =
1,800,000 bits, or 1,800,000 / 8 = 225,000 bytes
Unscaled TCP Receive Window (RWIN) = floor(Max Buffer Size / MSS)
= floor(65,535 / 1460) = 44.
That is, 44 segments totaling 44 × 1460 = 64,240 bytes is a good
configuration for a connection with MTU = 1500 and MSS = 1460.
To obtain the optimum scaled RWIN, multiply the unscaled RWIN by 2
repeatedly until the BDP is reached:
64,240 × 2 = 128,480 (< BDP)
128,480 × 2 = 256,960 (> BDP).
Thus, given the above assumptions, the optimum RWIN = TCP Receive
Window is 256,960 bytes.
You will need to restart Networking in Windows XP for the new TCP
window size to take effect.
 Windows Vista and Windows 7 have a function for automatic tuning of
TCP settings. Check whether that function is enabled as follows:
1) Open a Command Prompt using the Run As Administrator option
(right-click the Command Prompt item on the Start menu).
2) Type netsh interface tcp show global and inspect the value returned
for Receive Window Auto-Tuning Level.
3) If this parameter is disabled, give the command netsh interface tcp
set global autotuninglevel=<autotunelevel> to enable it. The value of
<autotunelevel> should be “highlyrestricted” if the server you are
contacting does not have RFC1323 implemented or does not
support the TCP receive window scaling factor. Otherwise,
<autotunelevel> should have the value “normal”.
5.3 Phone Related
5.3.1 General
 If you intend to use a USB hub for connecting multiple devices, install
the devices one at a time to avoid problems with driver mix-up in





© Ascom (2011) Document:
NT11-12547 11(18)


Windows. It is wise to do this in the office, before starting TEMS
Investigation. When all devices have installed, start TEMS Investigation
and check that all devices are detected properly and can be activated in
the application.
 Certain connectable devices respond to very few AT commands. One
example is the Samsung SPH-M320.
5.3.2 Sony Ericsson (Android)
General instructions for Xperia arc and Xperia X10:
 Make sure no APN is set in the phone: Press the Menu button, then
choose Settings > Wireless & networks > Mobile networks > Access
Point Names, and make sure nothing is set. (If an APN is already
present in the phone, the Network Connect activity in the TEMS
Investigation script, which tries to set the APN, will fail.)
 Activate USB debugging so that all relevant ports become visible: Press
the Menu button, then choose Settings > Applications > Development,
and make sure USB debugging is enabled.
Instructions for driver installation:
 Connect the Xperia phone to the PC. Windows will try to find drivers;
when the automatic driver installation fails, open the Device Manager on
your computer.
 Locate the Xperia phone with missing drivers under Device Manager >
Other devices.
 Right-click the first “SEMC HSUSB Device” and select Update Driver
Software > Browse my computer for driver software.
 Browse all the way to the directory where the applicable driver for your
operating system is stored; note that 32-bit and 64-bit Windows must be
distinguished. Example of path: ...\Drivers\Sony Ericsson\x10\Win64.
 Click Next.
 Repeat the procedure for the remaining “SEMC HSUSB Device” items.
5.3.3 Sony Ericsson (R13)
 Avoid mixing USB 2.0 (High Speed) and USB 1.1 (Full Speed) Sony
Ericsson phones, as doing so will cause some SEMC devices not to
communicate correctly over AT with TEMS Investigation.
 USB 1.1 default Sony Ericsson phones are: Z750, C702 and W760.
 USB 1.1 and 2.0 changeable Sony Ericsson phones are: C905 and
W995.
 In Windows Vista, device drivers can take a while to get running after
you plug in a Sony Ericsson phone, so that the detect may take some
time to complete. (Look at the status indicator on the Navigator’s
Equipment tab to view the current detect status for the device.)





© Ascom (2011) Document:
NT11-12547 12(18)


 When connecting a USB hub with Sony Ericsson phones to a Windows
Vista PC, the phone with the lowest port number in the USB hub is
sometimes not detected. This is solved by unplugging and reinserting
the phone.
 When using a USB hub with a Windows Vista PC for connecting Sony
Ericsson phones, we recommend that you plug the phones into the USB
hub one at a time.
 The driver software for the memory stick needs to be installed on the
PC to avoid problems when connecting a phone that is turned off. If the
K790/K800 has a memory stick, do as follows when first connecting the
phone:
1) Insert the USB cable.
2) Wait for drivers to install.
3) Unplug and insert again to make the memory stick driver install.
 If a Sony Ericsson TEMS Pocket phone is activated in TEMS
Investigation and the USB cable is pulled, TEMS Pocket will remain
disabled until either 1) the phone is restarted, or 2) the phone is
activated again in TEMS Investigation and then deactivated normally in
the application.
 When AMR-WB speech coding is used, the Sony Ericsson phone is
unable to measure GSM C/I.
 When locking the phone on a WCDMA cell, the signal strength
measurements will become invalid for other cells.
 GSM channel verification: 1) The phone must be on GSM before start of
test, otherwise the test will stall and after 20 seconds an error “BCCH
Lost” will be displayed. 2) The channel verification function attempts to
disable handover on the phone, but this does not work for phones prior
to W760i and C702.
 Sony Ericsson K600/W600: If CKPD is going to be used to execute
video calls, it is necessary to disable the keylock first.
 When sending SMS messages from Sony Ericsson phones such as
Z750 and W760, the number of characters is severely limited (worst
case: max 23 characters).
5.3.4 Qualcomm Chipset Based Phones and PC Cards
 Some Qualcomm chipset based commercial UEs may not have test
reporting activated. The device may then be impossible to activate in
TEMS Investigation, or seem to be locked to GSM, and/or only deliver
low-level reports. Please contact the UE vendor; Ascom is not
authorized to change this behavior.
 The hardware information and the number of devices used are
sometimes missing in the logfile information (accessed by clicking the
Information [“i”] button on the Replay toolbar).





© Ascom (2011) Document:
NT11-12547 13(18)


 AT commands in Service Control scripts are not always executed by
Qualcomm chipset based devices.
 When an Ericsson Fixed Wireless Terminal is activated, it is not
possible to do data service testing with any other devices at the same
time.
 To enable detection of the Ericsson Fixed Wireless Terminals,
uncomment the line containing "QualcommNetworkDetector" in the file
<TEMS Investigation install dir>\Application\Configuration\
Investigation.Equipment.config. If TEMS Investigation is running, you
must restart the application for the change to take effect.
 Care needs to be taken when using the NV interface to write to a
Qualcomm chipset based device, since an inappropriate NV write may
damage the device.
 If a Qualcomm chipset based device is not detected by TEMS
Investigation, although it is built on a supported chipset, you can run the
Manual UE Configuration utility to help TEMS Investigation recognize
the device. See the User’s Manual, section 7.3.4 for details on how to
operate this utility.
 Qualcomm FFAs of chipset families with LTE capability (MDM9200 and
MDM9600) are autodetected in TEMS Investigation as “Unknown
MDM9x00”, a base type with only LTE reporting.
 HTC Touch Pro2 phones with TCP router need special configuration to
be usable with TEMS Investigation. See the User’s Manual,
section 7.3.3.3.
 Service testing with Samsung SPH-M320 does not work.
 Samsung Omnia II does not answer incoming voice or video calls.
 FTP does not work with Samsung Omnia SCH-i910.
 IP sniffing does not work with Sierra Wireless devices such as USB
306/307. The best course of action is to set ignoreIPSniffError="true" in
the file <TEMS Investigation install dir>\Application\
Investigation.exe.config; see section 5.1.2.
 Sierra Wireless AC503 stops sending RF logs after 10–20 minutes of
dual data session testing. To restore RF data delivery you need to
disconnect and reconnect the device.
 For Samsung Metro GT-S5350, video call dialing is not supported;
however, answering a video call is possible. SMS Send works, but may
generate error messages.
5.3.5 Samsung Devices Based on Samsung Chipset
 The event IP Interruption Time cannot be generated for Samsung
chipset based devices.





© Ascom (2011) Document:
NT11-12547 14(18)


5.3.6 Nokia NTM3 Phones
 When the Nokia phone switches from GSM to WCDMA, GSM values
remain in TEMS Investigation presentation windows. These are old
values and linger because Nokia NTM3 phones stop reporting on GSM
after the switch.
 If you encounter problems activating a Nokia NTM3 phone in TEMS
Investigation, there is a need for a power reboot of the phone.
 When locking the Nokia phone on a band, this action should be
preceded by disabling the band lock. If you click OK between selections
of different bands, the phone will lock on all bands that you have
selected at some point.
 When WCDMA band lock is enabled, any attempt to access a cell on
any other WCDMA band will result in that cell being barred for
approximately 20 minutes. Therefore you cannot immediately go back
to the band you were on before applying the band lock (or to a cell on
that band). Furthermore, if the phone is locked on a WCDMA band and
you lock on a different band, then release that lock, you will get no
substantial phone logs for 20 minutes. For the above reasons, if you do
not want to wait through the 20-minute period, it is recommended that
you restart the phone before locking on a different WCDMA band or
releasing the band lock.
 To run the SMS Send script activity on a Nokia 6720, you must set the
parameter Request Delivery Report to False. If the default setting True
is retained, sending of SMS messages will not work.
 High data throughput may cause the Nokia C7 phone to reboot (see
Nokia release notes). Also, the video call capability of the Nokia C7 is
not supported in TEMS Investigation.
5.4 AQM Module Related
 The drivers for AQM modules are not signed, so that warning messages
will appear during installation.
 If the USB connection is broken during AQM measurement, the PC
application may need to be restarted to enable reactivation of phones.
 When running AQM measurements, it is recommended to use the Start
Recording and Stop Recording activities in the script to ensure that
each logfile contains a full call sequence. Automatic swapping of logfiles
is not recommended, as this can cause the merge mechanism to fail.
 PESQ calls may fail with error message “3 AQM Module errors”. This
message is shown when the PC application has tried to contact the
AQM module three times and failed on all occasions. This can be
caused for example by the module being physically disconnected from
the USB port or by the module not responding. The proper procedure
when this happens is either to reset the AQM module using the reset
button located on the back of the module, or to restart the module by
power-cycling it. The AQM module then needs to be paired once again





© Ascom (2011) Document:
NT11-12547 15(18)


with its phone. This is done from the Navigator’s Equipment tab (bottom
pane, Activities “subtab”) by right-clicking the PESQ Device Pairing item
and choosing the correct AQM module in the setup dialog.
Failures of this kind are also recorded in the logfile in the form of error
messages indicating that the connection to the AQM module has been
lost. If such failures occur frequently, this indicates a bad USB
connection or power cable.
5.5 Scanner Related
5.5.1 General
 Starting several scans in rapid succession (e.g. pilot scan and RSSI
scan) may cause TEMS Investigation to stop updating scan data, and
possibly even hang the application. The workaround is to wait until one
scan starts returning data before starting another.
 LTE scanning:
1) For RSSI scans, the bandwidth must always be set to 100 kHz.
2) For all LTE scanning methods, the set of channel numbers available
for scanning is dependent on the bandwidth selected, and some
bandwidths may not be at all applicable to the band in question.
Example (EUTRA Band 7):
RSSI scan:
 100 kHz bandwidth; available channels 2750–3449
Signal scan:
 1.4 MHz bandwidth: N/A
 3 MHz bandwidth: N/A
 5 MHz bandwidth: available channels 2772–3428
 10 MHz bandwidth: available channels 2795–3405
 15 MHz bandwidth: available channels 2817–3383
 20 MHz bandwidth: available channels 2840–3360
5.5.2 SRU
 Always install new drivers from the TEMS Investigation driver
installation CD and not from the internal SSD drive, which may hold
older drivers.
 It is crucial that to supply the SRUs with adequate power. It may be
necessary to use the accompanying 12 V adapter.
 To prevent problems detecting the SRUs in TEMS Investigation, stop
the Mobile Broadband Service and preferably set startup type to
disable.





© Ascom (2011) Document:
NT11-12547 16(18)


5.5.3 DRT 4301/4301A/4301A+
 The DRT scanner will reboot after a period of time if it is connected via
a LAN and is detected by multiple TEMS Investigation users. The
scanner API does not support multiple connections.
 Swap logfile cannot be used while scanning with a DRT scanner, since
each logfile must contain a scan start.
5.5.4 PCTel SeeGull LX/EX
 If you do not deactivate the scanner properly from within TEMS
Investigation, problems may arise when you try to activate it again. For
example, if you remove the cable from the serial port without first
deactivating the scanner in the application, measurements will continue
to run in the scanner, and when it is connected to the port again the
activation might fail. To solve the problem, turn the scanner off and on
and the activation function will work again.
 When plugging in a PCTel SeeGull LX scanner that uses a serial
connection, click the Refresh button on the Navigator’s Equipment tab
to ensure that the scanner is detected.
 With some PCTel scanners only 2560 measurement points can be
allocated for spectrum scanning, even though the scanner in fact has
more measurement points available.
 The PCTel scanners may sometimes report many scan drop messages.
The scanner uses this message to tell the host how many scan data
messages were dropped and not delivered through the data link.
Automatic scan data is dropped when the scanner is scanning faster
than the data can be delivered through the data link, causing the
pipeline to overfill.
 For EV-DO scanners, the “Use Pilot Increment” option is not available.
 When setting up a follow phone scan in CDMA, all fields in the setup
dialog must have some value set, otherwise you cannot click OK. Enter
dummy values in the dialog as needed.
 For the PCTel SeeGull EX scanner, version 2.0.1.0 and later, be sure to
install the driver delivered with TEMS Investigation. Do not install any
driver provided on PCTel’s web site. The reason is as follows: If you
have PCTel’s own driver installed, then if the scanner is activated in
TEMS Investigation and you pull its cable, the scanner port will not
disappear from Windows and thus not from the TEMS Investigation user
interface either. The driver delivered with TEMS Investigation contains a
modification that removes the scanner port in the situation just
described. When a PCTel LX MM2 scanner is connected to TEMS
Investigation you cannot use the Activate All function; rather, you must
activate each device separately.





© Ascom (2011) Document:
NT11-12547 17(18)


5.5.5 PCTel SeeGull MX
Detection of PCTel SeeGull MX scanner:
 After the driver has installed and Windows has detected the device for
the first time, the scanner should be rebooted.
 The USB cable must be connected at startup in order for the scanner to
boot correctly.
 After powering on the scanner, always wait for its bootup procedure to
complete (LED turns dark green) before starting TEMS Investigation.
This can take up to 90 seconds, during which time the LED is pale
green or orange.
 If the scanner is turned off during use, you must exit TEMS
Investigation and repeat bullets 2 and 3 above before you can connect
the scanner again.
5.5.6 PCTel SeeGull PCT
 PCTel SeeGull PCT scanner may not be detected on some PCs. If this
problem occurs, disable the “Intel Active Management Technology –
SOL” driver if it exists on the PC, then restart TEMS Investigation.
5.6 GPS Related
 While in dead reckoning mode, Garmin Street Pilot 2650 labels its
calculated positions as invalid in the PC interface yet presents the
positions on its display without any such indication. The positions
calculated by dead reckoning are indeed mostly useful and enable
TEMS Investigation to plot the route reasonably correctly when GPS
coverage is temporarily lost. (To make use of the “invalid” positions you
need to turn on an option in the GPS window properties; see the User's
Manual, section 26.1.)
 To activate the Nokia LD-3W Bluetooth GPS device, first start up TEMS
Investigation. Then connect the GPS logically in Windows, outside of
the TEMS Investigation application. Only after this can the GPS be
successfully activated on the Navigator’s Equipment tab.
 If the power is lost on a Bluetooth GPS device, you may need to restart
TEMS Investigation to be able to activate the device in the application.
 If a Bluetooth GPS cannot be found, try to restart the GPS. Wait for the
application and computer to establish the pairing. A “Refresh
equipment” operation may be needed in the Navigator if the device still
does not appear.
5.7 Call Generator Related
 The Call Generator installation requires an English-language edition of
Windows.





© Ascom (2011) Document:
NT11-12547 18(18)


 For the Call Generator Windows Server 2003 to function correctly,
make sure you have Powershell installed. With Administrator privileges
on the PC, choose Start > Run > Powershell. If the tool is not installed,
download and install Windows Management Framework Core package
(Windows PowerShell 2.0 and WinRM 2.0) from Microsoft (download
link: support.microsoft.com/kb/968930).
5.8 TEMS UDP Server Related
 If the following error message appears when the server is starting up:
“Error 1053: The service did not respond to the start or control request
in a timely fashion”, do one of the following (the two procedures have
the same effect):
1) Remove the internet cable. Start the service. Plug in the internet
cable.
2) Open a command prompt and type ipconfig/release. Start the
service. At the command prompt, type: ipconfig/renew.
6 Contact Information
For customer support contact information, please visit our website on the
Internet: www.ascom.com/networktesting
7 Appendix
OPEN SOURCE LICENSING INFORMATION
The USB driver (libusb0) used for AQM module is part of the open source
libusb Windows project. This project can be found on the Internet at
http://libusb-win32.sourceforge.net. The libusb-win32 project retains all
rights and copyrights to the libusb-win32 code. The library (DLL) is
distributed under the terms of the GNU Lesser General Public License
(LGPL) and the driver is distributed under the terms of the GNU General
Public License (GPL). The LGPL and GPL license text can be found on
TEMS Investigation driver installation CD. The source code for libusb-win32
is freely available and can be found on the TEMS Investigation driver
installation CD.