Find the attached file for Spirent TestCenter FAQ
What causes 8100 eAirAccess (eAA) or CS8 Interactive Tester to have an "Enable CallProcessing failed" message with reason "No response from S1AP for provision request" ErrorCode: 0x20E?
Below is an example of the error "Enable CallProcessing failed" message with reason "No response from S1AP for provision request".
The likely reason is the second Gigabit Ethernet cable (GB2) on the landslide server (SR3620) is not connected to the 8100 switch.
Use the Spirent Rack setup guide to double check the Ethernet cabling of the system.
Another issue which would cause a similar issue is if you do not have the correct license on the e2010 for MIMO and Fading. Run a static test case which does not use MIMO or Fading, it you do not see the above error it is likely a licensing issue for the e2010.
8100 LTS TTWB : Why am I unable to open the TTCN logs ( TD version 7.0) on TTCN (TestDrive version 6.5 and before )?
You cannot view the TTCN logs ( TD version 7.0) on TTCN (TestDrive older versions 6.5 and before ) this is due to the compatibility issue and all Support/ Application engineers are advised to upgrade their systems to the latest (TD 7.0) in-order to view TTCN logs from the latest TD 7.0 versions.
Below is the screen shot of the error that you see when you try to open a new log using the older version.
And for vice versa, you may have to save the (TestDrive older version logs 6.5 and before ) to the newer format as promoted to be able to read/open it in TD TTCN 7.0 .
Vertex:Why minimum bulk delay setting is 5us?
Vertex use an internal filter to implement bulk delay function, the minimum delay of this filter is about 5us, turn this filter off will produce 0 delay, use this filter will have minimum delay of 5us
8100 Radio Access Testing - Development Library and at&t 17397 Decive Aggression Management testing: How do I enable/disable the PS domain
Objective/Summary How do I enable / disable PS domain in order to allow/prevent a UE from registering on a PS domain?
Notes In order to disable/enable the PS domain, do the following:
8100 Radio Access LTE Audio Quality (AQ): procedures to generate detail report
Objective/Summary Generating detail report for AQ test is different from other products. This topic will introduce in details.
Environment/Versions 8100 Radio Access LTE: AT&T AQ CMCC AQ
Procedure 1. On TestManager GUI, select Report - Create Report - Custom Report - New Detailed... 2. By default there's Report Header component on the right side. Remove it. And then move Audio Quality Report component from left side to right side. Make sure it looks as below. Now we can generate detail report.
Notes If we generate detailed report follows below procedure (other test modules use it to create detail report): Report - Create Report - Spreadsheet Report - Detailed Report We'll see it's a quite simple report.
8100 Radio Access: system cannot capture ethernet packets, how to resolve?
Objective/Summary Some tests require capture Ethernet packets - we will see EthernetPacketLog folder under result folder. Sometimes we may see this file is empty. This topic tells how to resolve this issue.
Environment/Versions 8100 Radio Access LTE
Procedure 1. Ensure switch works. 2. Check cablings, especially ensure E13, E15, E19, E20 and E36 are connected correctly: 3. Configure 192.168.0.210 VLAN ID to 1 as below procedures
Notes Some USB-to-Ethernet adapter may not support VLAN ID field - we cannot see VLAN ID as above step #3. Then bypass step #3.
AT&T 19093 VoLTE Speech Quality
Objective/Summary AT&T 19093 VoLTE Speech Quality
Latest Version: Spirent suite version 1.6.89 (supports 10776 v16.3 19093 v1.8)
Known Issues:
Documentation: LTE Audio Quality (Speech Quality) Quick Start Guide to setup and install Nomad and Attero equipment
Vertex: How to avoid embedded PC speed down from 1Gbps to 100Mbps?
Objective/Summary Use this procedure only when you are experiencing PC speed down on the internal network
Procedure Settings on embedded PC:
Hardware change on Vertex: Connect the RED box to the BLUE box on the DSPM below:
Vertex:Know Issue: 4x16-100MHz topology port issues
Procedure There is a typo in our baseconfiguration file caused this topology mapping is wrongly implemented