ASCOM | TEMS AUTOMATIC - 2 | TEMS Automatic 7.2.1

TEMS Automatic 7.2.1
External Release Note
TEMS Automatic 7.2.1 External Release Note
2010-02-17
 Ascom 2010. All rights reserved.
TEMS is a trademark of Ascom. All other trademarks are the property of their respective holders.
No part of this document may be reproduced in any form without the written permission of the
copyright holder.
The contents of this document are subject to revision without notice due to continued progress in
methodology, design and manufacturing. Ascom shall have no liability for any error or damage of
any kind resulting from the use of this document.
2 (10)
1/287 01 - FAP 901 0916 Rev D
 Ascom 2010
Public
2010-02-17
1.
2.
3.
4.
 Ascom 2010
Public
TEMS Automatic 7.2.1 External Release Note
About This Release...................................................................4
Corrections................................................................................5
Known Bugs and Limitations.....................................................8
Contact Information...................................................................9
1/287 01 - FAP 901 0916 Rev D
3 (10)
2010-02-17
1.
TEMS Automatic 7.2.1 External Release Note
About This Release
Release date:
2010-02-17
Main contents:
-
Service Testing over Ethernet. Offers the possibility of testing data services
over a wireline connection.
-
Passive mode measurements with TEMS Pocket Remote: In passive mode,
measurements are made when the phone user engages in a voice call or
browses the Web, rather than during similar activity generated by TEMS
Automatic for measurement purposes.
-
BCH decoding: MTU scanning devices can capture and decode BCH data,
which is displayed in TEMS Presentation along with new missing neighbor
events derived from this data.
-
TCP settings configurable from the Operator Console. It is possible to
define TCP settings profiles that will be applied on the MTU. These TCP
settings profiles will be possible to view and filter on during post-processing.
-
Possible to set from Operator Console if NDIS or RAS shall be used for
data connection towards devices.
-
Improved installer scripts for ComServer and Operator Console
-
For information on TEMS Presentation see "Release notes for TEMS
Presentation 1.2, 1/287 01 - FAP 901 0916 Rev A"
Compatibility
-
 Ascom 2010
Public
MTU 700
MTU 750
HTU 2.0 (K800i)
HTU 2.1 (K800i)
TEMS Pocket Remote 6.0 (Z750
TEMS Pocket Remote 6.3 (W760 and C702)
TEMS Pocket Remote 7.0.1 (C905a)
1/287 01 - FAP 901 0916 Rev D
4 (10)
2010-02-17
2.
TEMS Automatic 7.2.1 External Release Note
Corrections
This section includes corrections made in TEMS Automatic 7.2.1.
ID
Summary
Datacard Device restart
QM000029308
Correction: Now the "SetRatLock" method does not return
false if the device is not implemented.
MMS send by MTU is rejected by WAP Gateway
Sub sys
MTU
QM000029659
Correction: Enabled possibility to use other ports.
MTU can't be configured in database.
QM000030548
Correction: Added support of MNC = 0.
Database
FTP server (running IIS7) experience 3 minute timeout when
the MTU is checking for files.
QM000031074
QM000031266
QM000031703
QM000032814
QM000032853
QM000032937
Application
Correction: A message from Microsoft IIS7 FTP server was
not handled properly by the TEMS FTP client.
Missing roles in table tCDMALBSMeasurement
MTU Field
Work
Correction: OC does not try to delete from CDMA tables
when running a UMTS system
Qualcomm data card in undefined state, not sending PDP
Context Activation
Operator
Console
Correction: New fault handling for PDP context activation
message
Lost PESQ measurements due to resynchronization that is
caused by HO
Correction: Extended time limit for resync to avoid most
resync events.
MTU always gets in unconfigured mode after restart.
Correction: Added support of MNC = 0.
Possible TEMS Client TCP port issue
Correction: The MTU firewall is modified to not block the
TCP packets.
Application
Application
Consultation
Application
This section includes corrections made in TEMS Automatic 7.2.
ID
QM000024381
QM000025964
 Ascom 2010
Public
Summary
Sub sys
Geobase failed due to arithmetic overflow in OLAP cube
UMTS_CallSetupTime. -- Code improved to prevent
occurrence of overflow.
Call Generator
Not possible for end user to remove only one Call Generator
from a server. -- End user rights extended and minor
Call Generator
1/287 01 - FAP 901 0916 Rev D
5 (10)
2010-02-17
QM000027264
QM000027403
QM000027505
QM000027513
QM000027560
QM000027798
QM000027836
QM000027937
QM000027938
QM000028057
QM000028203
QM000028290
 Ascom 2010
Public
TEMS Automatic 7.2.1 External Release Note
changes to user interface implemented in order to enable
uninstallation of individual Call Generator instances.
Blocked call attributed to "Unknown" CGI in statistics,
although it occurred in an identifiable cell. -- Reason: CGI
was unknown in logfile at the time of the call attempt.
Problem solved by adding CGI (if known) to Blocked Call
event when RRC Connection Release message causing the
block is received.
RNT files from MTU were sometimes put in the Garbage
folder. -- This happened when an MTU had lost track of time
(for example, after being upgraded with no GPS coverage).
The MTU then timestamped RNT files with a fictitious 2004
date, and the back-end consequently ignored this file in
favor of an RNT file with a more recent (but genuine)
timestamp previously stored in the database. System
behavior now changed to accept an RNT file even if it
appears older than the one in the database.
MTU status was given as "On" in Operator Console although
MTU had been powered off. -- This happened when the
"Transfer at shutdown" option was turned on. The status
was not updated correctly after the data transfer was
completed. Bug fixed.
RSI: Mobile-to-mobile calls were not reported for the phone
device; they only appeared if the serial number of the MTU
itself was added in the RSI user interface. -- This has now
been fixed so that mobile-to-mobile calls are reported for the
phone.
Area aliases were truncated to 10 characters when
processing TEMS Presentation data with Microsoft Excel or
Crystal Reports. -- Bug fixed.
After upgrading MTU700 software from TA 4.2 to TA 7.0, the
MTU was unable to communicate with SIM cards in Sony
Ericsson T610 and Siemens MC45. -- Problem solved in
MTU upgrade package.
Call Generator was tagged with red alarm bell even though it
had reported no alarms. -- Erroneous handling in Operator
Console of the option "Generate Call Generator alarms from
latest access" (alarm was turned on by default if the dialog
option had never been touched). The code has now been
fixed so that the behavior always reflects the setting in the
Preferences dialog.
Call Generator online help could not be opened from Help >
Contents. -- Bug fixed in application.
Call Generator online help could not be opened from Help >
Contents. -- Bug fixed in application.
TEMS Pocket Remote Configuration Guide did not describe
how to activate the TEMS Pocket Remote functionality in the
phone. -- Information added to document.
Successfully set-up call (with Connect Acknowledge
received) was registered as Blocked Call with cause No
Network. -- Event generation was faulty; bug fixed.
Error when trying to schedule incremental processing of
1/287 01 - FAP 901 0916 Rev D
TLH
Communication
Server
Communication
Server
RSI
Statistics
MTU
Operator
Console
Call Generator
Call Generator
Document Product
TLH
Statistics
6 (10)
2010-02-17
TEMS Automatic 7.2.1 External Release Note
Geobase.
-- This error could not be reproduced, and its cause remains
doubtful; however, a workaround is as follows:
Create a scheduled task manually by pointing out the path to
StatApp.exe, which can be found in the TEMS Presentation
installation folder.
To this scheduled task, add the following parameters:
0 Databaseserver Databasename "Geobasename"
"Geobasename" Database Full Username Password
The complete command line will look like this:
C:\Program Files\Ascom\TEMS Products\TEMS
Presentation\Presentation\StatApp.exe 0 <DatabaseServer>
<Databasename> "<Geobasename>" "<Geobasename>"
Database <Full\Incremental> <Username> <Password>
The username and password can be left out if Windows
Integrated Security is in use.
Example:
C:\Program Files\Ascom\TEMS Products\TEMS
Presentation\Presentation\StatApp.exe 0 localhost Statistics
"My Geobase" "My Geobase" Database Full
 Ascom 2010
Public
1/287 01 - FAP 901 0916 Rev D
7 (10)
2010-02-17
3.
TEMS Automatic 7.2.1 External Release Note
Known Bugs and Limitations
This section includes known bugs and limitations in TEMS Automatic 7.2.1.
ID
QM000016331
QM000021021
QM000022311
QM000022783
QM000024584
QM000026728
QM000027047
 Ascom 2010
Summary
Workaround
Modem over the air upgrade
contains no validation and is
handled as a normal MTU
software upgrade. This requires
the user to apply the modem
upgrade package only to MTU's
with the correct HW. Also the
software upgrade history will
show the normal MTU software
in state stopped after an
upgrade of the modem firmware
even of the MTU software is
correctly running.
Z750 not capable of HSDPA
testing at full throughput.
Max throughput for HSDPA on
Z750 is around 1,5 Mbps, MTU
internal limitation
GSM scanning sometimes fails
on Z750
MMS testing doesn't work for
WAP 2.0.
Round-trip times may not agree
exactly between IP logs
(*.pcap) and TEMS logfiles
(*.log). The two major reasons
for this are:
1) The temporal resolution of
the IP logging is limited (10 ms,
message timestamps taken
from Windows).
2) Measurements for TEMS
logfiles are made in the
application layer, i.e. further
removed from the hardware
than the IP logging which is
done at the device driver level.
The application layer
measurements may also be
affected by Windows process
scheduling in case of high
processing load on the MTU.
Attach sometimes fails although
Layer 3 signaling indicates that
the Attach was successful.
Lock on band option does not
Public
1/287 01 - FAP 901 0916 Rev D
Subsystem
Mobile
Configuration
MTU
Mobile
MTU
8 (10)
2010-02-17
QM000027486
QM000027928
QM000028088
QM000028749
QM000028955
QM000028957
QM000028963
QM000029173
work properly with Option PC
Cards. When set to execute a
work order with multiple actions
defined, each locking on a
different GSM band, the PC
card does not complete some
actions but switches
prematurely to the next action.
C/I data did not display in
TEMS Presentation although
C/I measurement was activated
in the work order. -- Bug fixed
but not acknowledged by
customer.
TLH crashes and restarts
frequently after being moved to
the database server.
Call Generator channels lock up
and cannot be restarted by the
Call Generator.
Uploader.exe sometimes fails to
upload files to some ftp servers
(proftpd)
Unable to save message, hr 1
Call Generator fails to release
phone lines, so that many
mobile-originated calls are
blocked with message "Release
Complete cause 44 (Channel
not available)".
Due to high processor load on
the MTU it is not recommended
to do testing on the Ethernet
device with IP logging turned on
at the same time as doing other
measurments on the mobile or
the data card. It is okay to run
measurements on the Ethernet
device at the same time as the
other devices as long as IP
logging is not turned on.
We found mismatches earlier in
the database - the pointer
seems to be not valid.
4.
 Ascom 2010
TEMS Automatic 7.2.1 External Release Note
Public
MTU
TLH
Call
Generator
MTU
Consultation
Call
Generator
MTU
Logfile
Handler
Contact Information
1/287 01 - FAP 901 0916 Rev D
9 (10)
2010-02-17
TEMS Automatic 7.2.1 External Release Note
For customer support contact information, please visit our website on the
Internet: www.tems.com
 Ascom 2010
Public
1/287 01 - FAP 901 0916 Rev D
10 (10)
Download PDF