Signaling Analyzer-RealTime 6.50.100 GA Release Notes-5973-1882

8/3/2019 Signaling Analyzer-RealTime 6.50.100 GA Release Notes-5973-1882

1/18

sA

Agilent Signaling Analyzer Release Notes for General Availability Release Version 6.50.100.108 Page 1 of 18

Agilent Technologies Signaling Analyzer

Release Notes for the General Availability (GA)

Version 6.50.100.108

Welcome to the General Availability (GA) release of Signaling Analyzer 6.50.100.108. These

release notes list new features, defect fixes, and issues and known problems for Signaling

Analyzer software.

Follow the instructions in this document to install or upgrade to this GA version. To upgrade

software on the DNA PRO or DNA MX systems, Agilent recommends using Instrument

Manager.

Refer to the online Network Analysis and Troubleshooting Solutions Setup Guide for other

installation and setup information. Refer to the Signaling Analyzer online Help for detailed

information about using the software.

NEW FEATURES .........................................................................................................................................2

PLATFORM FEATURES ..................................................................................................................................2LTEFEATURES ............................................................................................................................................2UMTSFEATURES ........................................................................................................................................2GERAN.......................................................................................................................................................2IMS,VOIP,SIGTRAN ................................................................................................................................2

INSTALLATION NOTES............................................................................................................................3

GENERAL INFORMATION ..............................................................................................................................4BACK UP IMPORTANT FILES PRIOR TO INSTALLATION .................................................................................4INSTALLATION/UPGRADE ISSUES FOR SIGNALING ANALYZER APIUSERS...................................................5ACROBAT READER AND QUICKTIME PLAYER INSTALLATION INFORMATION ...............................................5INSTALLATION INSTRUCTIONS FOR ELECTRONICALLY DISTRIBUTED SOFTWARE ........................................6

Installing/Upgrading Software on a PC..................................................................................................6

Installing/Upgrading Software on a DNA PRO and DNA MX................................................................6

ISSUES ADDRESSED..................................................................................................................................7

ISSUES AND KNOWN PROBLEMS .......................................................................................................18

Agilent Technologies Product Support

For a local support contact number, access http://www.home.agilent.com.

Click the Select a Country or Area link in the upper right corner, select the desired country,

select Yes or No to remember your selected country, and click Submit. You will return to the

main page. Click the Contact Us link in the upper right corner and the next page will list the

contact phone numbers for the selected country.

Trademark

See theAnalyzer Setup Guide for trademark and copyright notifications / acknowledgements.

*5973-1882*5973-1882

June 2009

Agilent Technologies, Inc. 2003-2009


2/18

sA


New FeaturesThe following new features and improvements are introduced with the Signaling Analyzer

6.50.100.108 GA.

Platform Features

Windows Vista Support

Wireshark Import/Export

Support for Symmetricom Xli GPS system for DNA systems

LTE Features

Real-Time Performance Analyzer (KPI Viewer)

Auto-Configuration

Topology Building

3GPP S1 Call Trace

UMTS Features UTRAN Auto-Configuration

IP, ATM & Hybrid Support

Path-ID discovery

Femto IP.Access Iu+

GERAN

Siemens BR10.01 Abis

TomTom over Abis & A

IMS, VoIP, SIGTRAN SIP-SS7 Combined Call Trace

IMS CT Enhancements

RADIUS, DIAMETER Accounting

MSRP, SMPP, MMS

WAP 2.0


3/18

sA


Installation NotesIf you have received these release notes with a physical shipment of software and/ or

hardware, you can find full installation instructions for the Signaling Analyzer GA Release

6.50.100.108 (and relevant hardware platforms) in the online Analyzer Setup Guide in the

Document Library on the installation DVD included with your products.

When you examine the contents of the DVD using Windows Explorer, you will see a folder

structure that shows each of the products that can be installed from the DVD: Double-click the

file called Readme.htm for additional information.

For additional documentation, open the Network Analyzer Solutions Documentation folder and

double-click the file CD_Start.exe to open the Document Library.

If you have received these release notes with an electronic distribution through your Agilent

Sales or Support Representative, go to the section called Installation Instructions for

Electronically Distributed Software later in this document.

Prior to installing the software, please read the following installation notes.


4/18

sA


General Information

Signaling Analyzer software version 6.50.100.108 is intended for use with Network

Analyzer Software version 6.50.100.040. For those systems with Network Analyzer

Software installed, update to software version 6.50.100.040 before installing Signaling

Analyzer version 6.50.100.108.

You are not required to manually uninstall Network Analyzer or Signaling Analyzersoftware. However, if you plan to manually uninstall Network Analyzer and/or Signaling

Analyzer software by using the Start->Control Panel->Add or Remove Programs option,

be sure to remove bothNetwork Analyzer and Signaling Analyzer before you install ANY

new 6.50.100.108 software.

If you are a Signaling Analyzer API user, please see Installation Issues for Signaling

Analyzer API Users later in this document prior to installing any software.

In general, it is a good idea to keep your host computers operating system service pack

level up-to-date and apply all the important Microsoft OS patches. In particular, please

make sure the non-paged pool issue and fix included in the Win2003 Service Pack 2

(http://support.microsoft.com/kb/917114) has been installed. Some problems have been

reported with Signaling Analyzer installs that are accessed remotely.

Also, Microsoft supplies security updates on a regular basis. Agilent recommends that

these updates are applied regularly in line with best practice. The automatic update of

third party applications such as Adobe PDF Reader or Apple Quicktime is not

recommended. Use only the versions of these packages supplied by Agilent.

Trademarks all recognized.

Back Up Important Files Prior to Installation

Before you install any of the documents or software listed below, Agilent recommends that you

back up a number of configuration files. Backing up these files will allow you to quickly recover

your previous configurations should you need to revert back to the earlier version of the

software. These files are:

hardware.cfg (the most recent Signaling Analyzer software configuration)This file can be found at C:\Documents and Settings\\Application

Data\Signaling Analyzer, where is the user's login name.

*.asc (configurations for specific DNAs)

*.tbl (pathID table configuration per interface/port if path IDs are used)

*dat (Network Analyzer configurations for each DNA)

Optional files to back up (on PC installs):

Session files and folders or *.sal (legacy traffic and measurements results files)

*.rec and *.xml (captured traffic files)

If installing on a DNA MX-B or DNA PRO, back up all configuration and data files to an externalstorage device in case the embedded OS needs to be recovered.


5/18

sA


Installation/Upgrade Issues for Signaling Analyzer API Users

For software releases prior to 5.40.100, it was necessary for the Network Analyzer software to

be installed on the same PC as the Signaling Analyzer Multi-User Client, ifthat client was to be

accessed using the Signaling Analyzer API. With the 5.40.100 release and later, however, the

Network Analyzer software is no longer required to enable the API capability in the Signaling

Analyzer.Because of this improvement, the upgrade process from 5.30.100 to 6.50.100.108 for users of

the API presents a number of process issues that need to be accounted for:

If you are an API user who has installed the Network Analyzer software for the sole

purpose of enabling the API in Signaling Analyzer, you should uninstall the Network

Analyzer software prior to installing this new version of Signaling Analyzer. Then allow

the installation of API components during the Signaling Analyzer install process.

If you are installing the Signaling Analyzer to be used as a Multi-User Client (which doesnot need Network Analyzer), and you think you might want to use the API in the future,

allow the API components to be installed during the installation process. If you do not do

this and later decide to use the API, you must re-install Signaling Analyzer and choose the

correct components.

If you update a Signaling Analyzer Multi-User Client automatically from an updated

Multi-User Server or by using the Web Update Wizard, you will not be given the option to

install the API components on the client PC. If you want to use the API with this client,

manually install the software using the full install package from the CD or ftp site.

Acrobat Reader and QuickTime Player Installation Information

Along with the Signaling Analyzer software, you might need to install the Acrobat Reader

and/or the QuickTime Player on your PC, and you will need to install them on your DNA MX or

DNA PRO.

Acrobat Reader is required to enable certain parts of the documentation installed with

the Signaling Analyzer software.

QuickTime Player is required for the video playback function in the Signaling Analyzersoftware.

NOTE: This version of the Signaling Analyzer does not work with the latest Quick Time

software. Please use QuickTime Player version 7.1.3.100 provided on the software

installation DVD.

Once you have installed the Signaling Analyzer software, refer to the onlineNetwork Analysis

and Troubleshooting Solutions Setup Guide (the Analyzer Setup Guide is part of the Analyzer

Documentation Library, which is accessible from the Start menu and the Windows desktop

shortcut) for Acrobat Reader and QuickTime Player installation instructions. You must use

these instructions for Acrobat Reader installed on a DNA MX or DNA PRO.


6/18

sA


Installation Instructions for Electronically Distributed Software

Use the following installation instructions if you received your software electronically from an

Agilent Sales or Support Representative.

Installing/Upgrading Software on a PC

Obtain the Signaling Analyzer 6.50.100.108 software, or its location, from your AgilentRepresentative.

To install/upgrade this software, follow these steps:

1. Unzip the sa6.50.100.108full.zip file to a convenient location on your PC.

2. Double-click the sa6.50.100.108full.exe file.

3. Start the Signaling Analyzer application and use Help | About to verify that yourSignaling Analyzer software version is 6.50.100.108 when the installation has

completed.

Installing/Upgrading Software on a DNA PRO and DNA MX

Before installing 6.50.100.108, the DNA PRO and DNA MX must have Windows XP Embedded

SP2. The Network Analyzer Software image must be 5.00.100.008 or greater. If it is not, youmust re-image the DNA PRO or DNA MX prior to installing the 6.50.100.040 Network Analyzer

software version and the 6.50.100.108 Signaling Analyzer software. Software version

6.50.100.108 should be installed using Instrument Manager.

To upgrade software on the DNA PRO or DNA MX using the Instrument Manager:

1. Unzip the sa6.50.100.108full.zip file to a convenient location on the PC on which the

Agilent Instrument Manager is installed.

2. Start Instrument Manager and add the instrument using the Add Instrument button.

3. Select the instrument from the main view and click the SW Update button. You can

upgrade software on multiple instruments by pressing Ctrl + click.

4. Click the Browse button to find the .exe file that you placed on your PC.

5. Click OK to apply the software update.

Firmware Update on DNAs

When you have daisy-chained DNAs or DNA HDs that are connected to a DNA MX or DNA

PRO, the firmware update of those DNAs will happen automatically at the time of

installation.

CAUTION: While this firmware update is occurring, DO NOT turn off power to these

devices or remove any of their LIMs until these devices are visible in the Select LIM dialog

box in the Network Analyzer software.


7/18

sA


Issues AddressedThis section lists all of the issues that are resolved with this release (6.50.100.108).

Note: Items in blue are Network Analyzer issues or issues that span Network Analyzer and

Signaling Analyzer.

Issue ID Title

2245 Intersystem handover/deciphering failure has been fixed.

2374 Request URI is now an available column in Traffic Overview.

3005 DMT Iu standalone call trace is replaced by DMT combined Iub&Iu&Iur calltrace.We do not find issue with the data rate.

3110 CAP calling party or called party columns can now be added to the TrafficOverview.

3205 NA RTP Stats supports stacked VLAN

3256 BSSMAP Perform Location Request messages are now consistently

decoded.

3321 Unexpectedly large sal file generation is no longer an issue.

3324 Enhancement

3454 Number of items possible in the Columns sub-menu (opened from theright-click menu in Traffic Overview) has been increased to 70.

3585 Display refresh has been addressed to allow Traffic Overview to showlatest message.

3596 Signaling Analyzer no longer erroneously displays the "incompatibleversion" error.

3728 Path id is now copied correctly on Chan OC3.

3733 ETSI INAP call trace is now able to add value in call trace criteria.

3735 ETSI INAP called/calling party number is now extracted properly in INAPcall trace.

3736 Calling/called party number discrepancy in Traffic Overview and Decodeview has been resolved.

3738 SCCP CT called up when the protocol presented

3741 SART: View Filter Cancel does not apply for starting a new recording

3764 GPRS 3GPP R6 BSSGP: MS Bucket Size decode error

3773 Call-Manager drill-back / search function has been extended to search the

requested traffic from the CaptureData Folder AND from folders listedinside Open Session dialog box.

20344 Duplicate protocol listings in the Protocol Field Columns dialog box havebeen removed.

20614 RLC reassembly errors for RLC One Sided Reestablishment have beenfixed.

20626 ITU HSL stack added


8/18

sA


20688 Drill down on LAC now works properly for Iub&Iu&Iur Call Trace.

20820 Call Trace and Tabular Stats now working for IS-41.

21054 Signaling Analyzer now decodes the TargetCellId in the BSSMAP layer ofa ""handover required"" message in hexidecimal and also in the differentelements such that the cell-identity is readable.

21055 Signaling Analyzer now displays the RANAP TransportLayerAddress instandard IP address notation.

21168 Path ID handling / rules have been changed to meet customerexpectation.

21313 BSC5 high-speed A-Interface decode error has been fixed.

21441 View filter - NBAP - ProcedureCode - Can select all fields

21539 MAP call trace logic error in which the same IMSI is referenced in twoseparate sessions, but are shown as a single call, as been resolved.

21912 Target RNC-Id (octet 59) in SRNC relocation is now decoded into decimalinstead of hexidecimal.

22041 Decode of CREATE PDP CONTEXT REQUEST and RESPONSEmessage is now correct.

22111 The correct NAS protocols have been configured above MAP resulting inthe correct decoding of Prepare HO (Invoke) and Prepare HO (ReturnResult) on Sigtran.

22400 SLC in the MTP3 layer is now properly decoded as "not specified".

22447 Extra columns are no longer added to CSV export when a parameter hasa comma in the value.

22483 Highlighted messages are still highlighted after applying new view filters intraffic overview.

22560 Acronym ESTREQ is now correctly spelled out as "RLLM EstablishRequest".

22651 GERAN: Encryption key is now correctly and consistently decoded on theAbis and A-interfaces.

22652 GERAN: Y-HO indicator is no longer wrongly decoded as "reserved".

22653 GERAN: TMSI leading zeros are now properly decoded and displayed.

22654 GERAN: Naming of BR9, BR10 is now clear in View Filter dialog box.

22656 Problems with NBAP Graphical Stats when displaying SIR Error Value andSIR Values have been resolved.

22768 The NumberOfOctetsAffected parameter of the BSSGP LLC-DISCARDED

message is now decoded in decimal format.

22805 Incorrect user-interface behavior in the Protocol Stack tab in the AutoConfiguration dialog box has been corrected.

22809 Signaling Analyzer now supports SCCP reassembly for IP over AAL-5;specifically SCCP (e.g. RANAP Relocation Preparation message) isreassembled on top of M3UA/IP/AAL5.

23073 Subsystem Number (SSN=192) is now used to identify BSSAP+ protocol.


9/18

sA


23076 Whether r5 or r6 Ue, the Signaling Analyzer now consistently decodes theparameter "servingHSDSCH_RL_indicator" (RadioBearerSetup message)as either TRUE/FALSE.

23261 CAP call trace no longer times out during call.

23264 Asub BR 10 decode errors have been resolved.

23278 Radio Link Messages are no longer mis-grouped such that a messagefrom one PS call is grouped with a separate PS call (different vpi).

23286 Anomalous application behavior during and after TOL file import has beencorrected.

23315 The MAP call trace is no longer erroneously stacking multiple sessionswith the same reused OID with different IMSI value.

23331 Deciphering on Iub is now correct after relocation.

23360 Signaling Analyzer now decodes RANAPNewBSS_To_OldBss_Information field on Relocation_Req_ACKmessage.

23373 Incorrect notation of IMEISV in call traces and Traffic Overview has beencorrected.

23396 Geran PCU reassembly is now working because the proper protocol isnow activated.

23397 CN-invoketrace message now correctly decoded.

23433 Setting view filters while in pause mode now works as expected.

23449 Network Analyzer capture filter no longer inadvertently suppresses ALCAPframes.

23452 Disconnect Cause column in the A-interface call trace is now filled with theproper information from the Disconnect message.

23560 In customer BSDTM environment, the Signaling Analyzer now plays andsaves AV32 call.

23582 Signaling Analyzer no longer erroneously decodes ATM Iub data onVPI/VCI=*/4 as FACH.

23585 Layout of the graphical statistics view persists after using the configurationdialog box.

23610 ISUP 2000 call trace now supports billing duration between ANM/REL orRLC.

23634 Spontaneous Signaling Analyzer application crashes have been fixed.

23664 Deciphering problems after SRNC relocation procedure have beenaddressed.

23677 RLC reassembly problem has been fixed.

23731 SystemInformationUpdateRequest decoding error has been corrected.

23797 Video user data is now included when using an IMS call trace (includinguser data).

23799 Memory leaks associated with Telephony Network Analyzer have beenrepaired.


10/18

sA


23835 Decode no longer drops leading zeros in parameters INAP CS-2.

23857 Various CTP over SIGTRAN problems have been resolved.

23862 Resolved issues with the 3GPP R6 03-2006 to 12-2006 Iu Interface overM3UA

23864 Issues with the ITU 2000 ISUP over M3UA CTP have been resolved.

23887 GERAN TRAU frames are now captured by the Signaling Analyzer asexpected.

23909 Incorrectly reported time-outs after each CC connect message in the CallTrace phase graphics display have been corrected.

23927 RTP "payload type" statistics are now working properly.

23945 The cause of inconsistent groupings for R5 GbGr, R4 Gb, Intersystem calltraces has been resolved.

23970 Problems with AMR WAV file extraction and playback have been resolved.

24003 Max bitrate PDP context accept message is now correctly decoded.

24013 LCP decode (TRM-REQ) error in Traffic Overview has been corrected.

24093 Incorrect messaging arrows in the Call Trace Sequence Diagram viewhave been corrected.

24108 Buffer size increased to allow AAL-2 VCI list to be completely loaded.

24120 GigE NDIS NIC is no longer erroneously shown as Fast Ethernet inNetwork Analyzer SW Edition.

24260 Multi-User Server Iub filtering (Store control PDU) now correctly passes360 bit transport block TB on RACH.

24274 Values are now correctly displayed when putting "HO" and "test pattern"out of the MTN layer to the Traffic Overview.

24275 SecurityModeCommand parameters "key" and "Encryptionkey" are nowdisplayed correctly in Traffic Overview.

24296 T.30 decoder issues fixed.

24346 Call traces with Gr interface are now grouping SIGTRAN-based Grinformation correctly.

24388 Network Analyzer Channel Stats measurement (or Network Analyzer clientSS7 Channel stats measurement) shows all timeslots that areprogrammed/configured show up with the ones that are Out of Service orhave no SS7 traffic (FISU/LSSU/MSU) appear as a red state.

24389 Channel Stats measurement (SS7 - FISU/LSSU/MSUs) now shows redafter a timeout period if no valid messages are received on the channel.

24407 MAP query in Call Manager now works as expected.

24425 AV64 playback no longer cuts the data after re-establishment.

24453 CAP messages now decoded.

24454 RLC cause value in the call trace is now displayed properly and incorrecttimeouts have been corrected.

24475 Signaling Analyzer now correctly correlates IMS call sessions.


11/18

sA


24490 Traffic Overview "Last Message" and "Layer-7" are now displayed asexpected for RRC container over BSSMAP.

24493 The case in which the Network Analyzer software installed on a DNA MXat a customer site is hanging has been resolved.

24539 TBCP decode is now available with default setting.

24540 SIP calls with the same call ID, To, From header are no longer divided inthe call trace result view.

24545 NBAP cause column value is now updated properly.

24556 All legs of a call (IubIu/Iur) are getting grouped together

24561 Signaling Analyzer now can open sessions with Japanese characters.

24608 BICC decode codec parameter in IAM,APM messages is now fullydecoded.

24688 Call Trace Log Filter working correctly during handover.

24689 Active Scrambling Code is now updated in Call Trace view.

24710 Iu User plane information is now processed for call trace profiles related toRANAP R6 version 10 revision.

24713 RLC reassembly problem seen after upgrade was fixed.

24714 Missing call trace profiles - "3GPP R6 03-2006 to 12-2006 Iub&Iu&Gb&AInterface (FP&RRC, soft handover, hybrid)" and "3GPP R6 03-2006 to 12-2006 Iub&Iu&Gr&A&Gb Interface (RRC, soft handover, hybrid)" - havebeen added.

24741 Call trace problem during inter-frequency handover in which radio link onthe new frequency layer is not added to the call has been corrected.

24835 The problem in which 3G -> 2G calls are closed with a time-out when theyare actually correctly closed from a call flow perspective has been fixed.

24837 LIMs and NDIS NICs are now properly displayed in the Bearer view due tofix to system files installation.

24855 Deactivate PDP Context Request now grouped properly with theappropriate call.

24869 Issues related to 08B EUL call trace not working properly have beenresolved.

24872 Error during A-interface call trace is not reproducible and thus presumedfixed.

24880 The "CellChangeOrder Target Cell" column for DMT call traces is nowupdated properly.

24892 Export of grouped calls/messages to tcpdump/libpcap files (*.pcap, *.cap)now works properly.

24905 RAB_ASSINGNMENT_REQUEST and RAB_ASSIGNMENT_RESPONSEmessages are now properly decoded.

24941 The problem in which the Iub user plane goes missing after active set-update has been corrected.


12/18

sA


24942 The problem in which Iub user-plane data is not displayed after a Cell-Update procedure has been corrected.

24943 IubIuGnGi call trace is now grouping the Gn portions of the call correctly.

24957 Hybrid IP-ATM Iub Call Trace group ATM and IP legs together

24962 Deciphering and reassembly problems that cause the UTRAN Optimizer to

not display the correct UDP BW on the Iub (as compared to Iu) have beencorrected.

24988 RLC PDUs over HS-DSCH deciphering and reassembly errors have beencorrected.

24998 Data information element (i.e., Closed User Group) is now decoded inSETUP message (over A interface).

24999 IAM for ISUP and BICC is now more completely decoded.

25017 Setuptime, Cleardown Time, and Service fields are now updated correctlywhen using an intersystem IubIuBgA call trace.

25022 SIB reassembly problems on certain Nokia NBAP messages fixed.

25026 IP Capture Filter (Station Filter) is now working properly.

25036 Ethertype 0x023E Spanning Tree is now properly detected by SignalingAnalyzer.

25053 Decode error over Gn interface (Create PDP Context Request) has beencorrected.

25054 View Filter for Ipv4&Ipv6(Upper) complete with Identification and ICMPSequence number fields.

25055 View Filter : with redundancy fields M Flag and Sequence numberremoved

25056 BSSMAP over MAP now decoded properly.

25057 08B EUL call trace is now grouping all expected messages.

25060 View filter can now be used on BVCI field in BSSGP.

25061 The decoded CI value in BSSGP is now properly displayed in decimalformat.

25062 The detach accept message on Iu is now being decoded correctly.

25063 A-interface call trace error has been corrected.

25064 Added SS7 IS41 (Itu-t) stack.

25066 Invalid FP FACH is no longer grouped before RRCConnectionRequestwith Step 1 call trace.

25077 ALCAP REL-RLC grouped correctly within the call

25095 Post-selection reassembly without deciphering for customer variants isnow enabled.

25100 Unexpected behavior for the Technology/Interface choice in Select LogFile dialog box has been fixed.

25151 L6 Message and Last Message columns are now filled in correctly whenanalyzing BSSAP+ over Sigtran (M3UA) traffic.


13/18

sA


25154 Message to disable deciphering because not supported in current setupdisplays only once during session as expected.

25173 Error message is no longer displayed when selecting (double clicking) acall in the Call Trace view while in pause mode.

25211 Diameter statistics working

25225 SCCP reassembly is now working correctly.

25237 Signaling Analyzer now merges very large sessions with no data loss.

25239 The SessionId protocol filter is no longer failing.

25255 Show Field in Traffic Overview now works properly for UARFCN.

25266 RRC RadioBearerReconfigurationComplete is now reassembled properlyafter CellUpdateConfirm message.

25269 Crash in DNS decode fixed.

25280 Femtocell: Columns added in Call Trace for AP and AC IP addresses.

25294 RLC PDUs reassembled over RACH/FACH

25297 Signaling Analyzer now handles the procedures that cause a URNTI valueto be changed during a call.

25320 Client crash while using Call Trace Log Filter has been resolved.

25330 Application crash related to scrolling through data in Traffic Overview hasbeen resolved.

25331 CellIndividualOffset information element in the MeasurementControlmessage is now decoded correctly.

25332 Reformat CI and LAC values of inter system call traces and tabular stats tobe decimal.

25333 A number of problems with the handling of a failing handover procedure on

the A-interface have been corrected, including: (1) intersystem call tracesnot grouping all the messages, (2) handover attempts not groupedcorrectly, and (3) the Handover Failure message is incorrectly shown inthe call trace tool-tip as connection refused.

25334 Condition that causes intersystem call traces to erroneously time-out onGb calls has been corrected.

25335 Intersystem Gr call trace no longer incorrectly showing time-out.

25339 Problems with Iub uplink AMR playback have been resolved.

25353 Signaling Analyzer client crashes corrected.

25355 The causes of missing and incorrectly decoded messages after "UE-Notinvolved" Relocation have been corrected.

25382 CTAAF working correctly for 3G calls

25383 Signaling Analyzer client no longer crashes when trying to perform a CSVexport.

25384 Problems with intersystem handover and software crashes when usingIubIuGrGbA and GbGr call traces have been resolved.


14/18

sA


25408 Attach reject cause on the Gb interface is now correctly reported in theCall Trace view.

25409 The cause of the software crash when performing long WiMAX trafficcaptures has been indentified and fixed.

25429 Software crashes (Signaling Analyzer) that occur when a real-time run is

paused and then stopped have been corrected.25449 UMA PS decoding and Gb deciphering are now working properly.

25459 Added BSSLAP over BSSMAP to correct a decode problem for A-interfaceover Sigtran R4 MSC.

25479 The case where HLR is incorrectly decoded as TCAP (should be MAP)has been addressed by ensuring SSN 6 and 8 in the Sigtran stackassigned to MAP.

25480 RAND and AUTN values (GMM layer) are now correctly displayed inTraffic Overview.

25482 Missing decoding, reassembly, and deciphering for UMTS multi-call hasbeen corrected.

25483 Automatic update for Network Analyzer from a Multi-User Server nowworks properly.

25499 USSD string information element is now grouped properly in MAP protocoldecode.

25524 The PhysicalChannelReconfigurationComplete message is now displayedin compressed mode as expected.

25530 "Operation code - Process Unstructured SS Request" tag now displayedconsistently for MAP and NAS SS.

25531 UMTS Deciphering is now correct after second Location UpdateProcedure.

25533 Acceptance Tests - Active Scrambling code column now updatedcorrectly.

25547 Acceptance Tests - Cause of application crash during 3G load test hasbeen found and fixed.

25551 Acceptance Tests - MAP and Intersystem call traces with Gr now groupingMAP correctly.

25552 Acceptance Tests - Active scrambling code column is now updated inhard-handover scenario.

25594 Signaling Analyzer crash while playing back REC files has been fixed.

25595 Various decode and display errors fixed associated with CS1 messages.

25596 VPI.VCI editing anomalies have been corrected.

25598 Unexpected software crash when importing .sal file has been fixed.

25600 The Signaling Analyzer software crash when attempting to decode M2UAhas been fixed.

25601 SCTP de-bundling is now enabled for CDMA traffic.


15/18

sA


25603 Explanation provided as to why it appears that a Network Analyzer clientattaching to Multi-User Server with GigE filter configuration seems to getdouble resources and error messages.

25615 XML API ConnectToDna "copyConfig" now working properly.

25621 SCCP reassembly now working properly when multiple identical frames

are detected.25622 Gb deciphering now working.

25631 CAP - BearerCapability information element on Initial DP message is nowdecoded correctly.

25632 The cause of the Signaling Analyzer software crash when running anIubIuIur call trace during 3G load test has been fixed.

25636 CS1 Calling and Called party number are now displayed in TrafficOverview as expected.

25638 ATM/IP (08B-08B Interworking Step 2 (FP&RRC)) call trace no longergroups very partial messages.

25676 Acceptance Tests - IUA traffic decoding and configuration problems havebeen addressed.

25678 Signaling Analyzer crash associated with Traffic Overview window sizehas been fixed.

25686 "Cause value" parameter is now presented only once in the view filterdialog box.

25712 Network Analyzer no longer crashes when the user opens the Decodeview after another measurement is already running.

25722 The field link and bearer are now correctly displayed.

25736 Crash of 3gpp_r6_06_iub_iu_map_aint_gb_handover_flatten_fp has beenfixed.

25751 Signaling Analyzer software failure during an intersystem call trace hasbeen corrected.

25781 Erratic frame loss on J6804A/J6850A DNA HD has been fixed.

25801 The proprietary Iu+ call trace is no longer erroneously marking all calls asUnsuccessful.

25812 CAP SMS initial DP decode is now correct.

25822 Unexpected "Call Manager Client buffer is full" error message has beenaddressed.

25833 Radius messages are now properly decoded.

25841 The cause(s) of the software crashes at a customer's capacity lab havebeen found and corrected.

25846 Last part of RNSAP RadioLinkReconfigurationPrepare is now decoded.

25848 3GPP A Interface obsolete.

25859 T38/T30 decode problems (for DIS and DCS) have been corrected.

25865 Gr (MAP) columns have been cleaned out of Iub&Iu&Gb&A call traces.


16/18

sA


25866 Gb grouping issues involving the Iub&Iu&Gr&A&Gb call trace have beenfixed.

25867 "Days remaining" calculation when using flexible licenses is now correct.

25873 Gb deciphering now working properly.

25875 Gb deciphering now works with EGPRS UE.

25880 Call Trace configuration settings are now preserved when the applicationrestarts as a result of autorecovery.

25898 The conditions that caused the IP Multi-Segment Jitter measurement tofreeze have been fixed.

25899 IP Multi-Segment Jitter firewall feature now working properly.

25906 It is now possible to add OPC and DPC values to the call traceconfiguration dialog box when setting up an ETSI ISUP v4 Call Traceprofile.

25907 IP Connection Statistics for some of the highest utilization connections areno longer lost.

25908 SMS messages can now be turned off in the Signaling Analyzer display.

25927 Data acquisition and processing now correctly identifies the Signal Unittype, fixing the problem in which MSUs and FISUs were not beingidentified correctly in the Signaling Analyzer decodes.

25964 View filtering of BVCI in the NS layer of Gb over IP traffic is now workingproperly.

25966 The options to save decodes, hex-dump, or individual message while inpause mode have been disabled to reduce user confusion.

25974 Switch Advisor launch from the toolbar button in the Network Analyzersoftware is now working as expected.

26010 Incorrect IP address syntax in session files no longer causes SignalingAnalyzer application to crash. Syntax checking has been implemented.

26020 Signaling Analyzer software crashes during GERAN tracing has beenfixed.

26038 Nodes on Gb protocol stack working well

26066 Protocol stack related to TTC MAP has been fixed.

26088 Parameter misspelling in API manual has been corrected.

26105 The Signaling Analyzer crash (in module MSVCR80.dll) caused by anunexpectedly large value in the content length header of an HTTPmessage has been fixed.

26146 Signaling Analyzer is now decoding the information element "Lower LayerCapabilities" of the ISUP protocol.

26151 Linksets tab in the Filter Editor dialog box now shows all ports.

26208 IP over AAL5 - RANAP Relocation is now decoded properly.

26209 Signaling Analyzer no longer crashes when importing a logical naming file.

26210 The last 4,5 octets of the RRCConnectionSetupComplete message are nolonger incorrectly flagged as padding.


17/18

sA


26225 Signaling Analyzer no longer crashes when importing ASC file.

26227 Solution Reviewed for 25848 in 6.60.100.017

26259 Call with multiple RRCConnectionRequests are grouped correctly

26326 View filter on tributary now working properly.

26340 Dialog box requiring user input no longer blocks automated 2G/3G testingwhen using the Signaling Analyzer API.

26344 Abis Enhanced Measurement Report is now decoded.

26375 Eight-Port E1 traffic no longer showing incorrect FCS errors.

26376 Signaling Analyzer Free Decode Viewer now opens sessions properlywhen those sessions have pre-existing call traces in them.

26411 Signaling Analyzer now maintains a static column order for DMT calltraces and the resultant CSV output.

26438 Traffic Overview unexpectedly and erroneously stopping during test hasbeen fixed.

26446 A interface trace runs to completion smoothly

26485 Signaling Analyzer no longer crashes when applying settings discoveredby Auto Configuration.

26516 Application response and performance issues in offline analysis, andseemingly related to the new session paradigm, have been resolved.

26535 Spelling error in Analyzer.xsd that was causing operational problems in theNetwork Analyzer has been fixed.

26550 Adding ETSI INAP CS2 node above the SCCP node in the ProtocolStacks view no longer generates an error message.

26577 Signaling Analyzer is no longer erroneously showing "purged" for lines inthe call trace for long calls.

26610 SCCP reassembly is now working correctly.

26720 Signaling Analyzer is now able to properly save sessions to non-localnetwork paths.

26766 Iu-Pc PCAP decode errors have been corrected.

26787 IP Multi-Segment Jitter measurement crash when using a firewall setuphas been corrected.


18/18

sA


Issues and Known ProblemsThe following list describes known operational and analysis issues that exist in this GA release.

Unless explicitly stated, issues and known problems from previous releases may still exist, but

are not listed here. Please refer to previous copies of the release notes for additional

information.

Title: High memory usage when running Signaling Analyzer without UMTS Auto-

deciphering

Description: When running Signaling Analyzer Real Time, with Traffic Overview, UMTS

RLC/MAC Reassembly enabled (from Tools -> Options -> Reassembly), the memory

usage will be high and this is not released until session is closed. If you stop the

capture and try to run Call Trace, you will get error: "System Error: CL 0004"

Workaround: 1. Run with UMTS Auto-deciphering. Or 2. Once you see the CL 0004

error, save the session and close current Signaling Analyzer. Then open Session again

in Signaling Analyzer Offline.

Primary/Related TTI: 24971

Title: Summary View doesn't support auto-adjust column width

Description: In the Summary View, if Hide Zero is enabled, columns do notautomatically expand when the counts become greater than zero.

Workaround: Press "Ctrl+F8" or click on "Adjust Column Width" from the menu pop-

up, to re-adjust the column width.


Title: Date format in Traffic Overview and Call Trace View are using different formats

Description: In Timestamp column of Traffic Overview, the date format is the

following: DD/MM/YYYY. But in StartTime column of CallTrace View, the format is

MM/DD/YYYY.

Workaround: None


Title: Optimizer has listed extra DNAs which do not belong to session

Description: In DNA combo box, you will see other DNAs which do not belong tocurrent open session.

Workaround: Open Bearer view to check the correct DNA


Title: PDFs launched from the Help window sometimes will not open

Description: If you install the Signaling Analyzer software to a non-default location,

links to a number of PDF files that are included with the product will not be displayed.

Workaround: Most of the PDFs that are not displayed are also available in the main

Documentation Library that can be started from the desktop.

Primary / Related TTI: 25944

Title: Unexpected behavior associated with lockName argument in contextDrill API

command on Vista or Windows 2008 computers.

Description: When using the contextDrill command in the Signaling Analyzer API, andthe "lockName" argument is either not specified or not specified as the user currently

logged in, the Signaling Analyzer application will be launched in the background under

the username "SYSTEM" or the other lockName (as seen in the Processes tab of the

Windows Task Manager.)

Workaround: None.

Primary / Related TTI: None.

Signaling Analyzer-RealTime 6.50.100 GA Release Notes-5973-1882

Documents

Transcript of Signaling Analyzer-RealTime 6.50.100 GA Release Notes-5973-1882