VoLTE  or  SIP VoIP  or  Vo5G


In VoLTE testing, the VoLTE tab allows you to define the UE and IMS Node parameters for SIP Subscription, registration, call profile, authentication, call establishment/release rates.

NOTES:
  • In IP Application Node test case, this tab is labeled SIP VoIP and supports only Remote IMS Node Type.
  • In IMS Nodal Test case, this tab is labeled SIP VoIP and supports the PS Domain (Ml, Mw, Mx and ISC Interfaces) and CS Domain (Nc Interface).
  • In Wifi Offload Gateway Nodal and PSAP Node this tab is labeled SIP VoIP.
  • In the 5G test cases (UPF Nodal, AMF Nodal, etc) this tab is labeled Vo5G.
  • All Tcl Variables for the E911 VoLTE tab begin with Ve911. E911 VoLTE is available on SGW Nodal TC when Enable E911 Call Preemption is selected or on MME Nodal when Emergency PDNs and 2-Way Live Audio Bridging. 
  • On MME Nodal when 2-Way Live Audio Bridging is enabled and Emergency PDNs is not enabled, this tab is labeled VoLTE 2.
  • On AMF Nodal, the E911 Vo5G tab becomes available when Enable E911 Call is enabled.All Tcl Variables for the E911 Vo5G tab begin with Ve911.

UE

IMS Nodal

P-CSCF Built-In/ATCF Built-In

MSC Built-In

AS Information

P-CSCF Built-In

IMS Node

(IMS Node Type = Remote, GM Interface)

Registration

Security

 

Subscription (IMS Node - Mw) 

Subscription (IMS Node - Mw) 

Call Info

SIP Stack Options (UE)

SIP Stack Options (IMS node)

 

Call Flow Info

 

Optional Call Info

Optional Call Info (IMS Nodal - NC)

Emergency Info

Emergency Info

Emergency Header Options

 

SIP Subscriber URI Scheme

SIP Endpoint URI Scheme

 

 

 

Use tel-URI for SIP Subscriber

Use tel-URI for SIP Endpoint

Multimedia Priority Service (MPS)

Apply Test Data File to UE Parameters

Apply Test Data File to IMS Parameters

 


UE

The UE pane parameters allows you to define UE profile required for identification to the IMS network.

SIP Subscriber per UE

Indicates the number of SIP Subscribers supported per UE.

If 2 is entered, the each UE places at least 2 simultaneous calls per UE. That is, each UE has at least 2 Public User Identities or at least 2 SIP Subscribers configured per UE.

Options: 1 or 2

Default : 1 (Default was changed to 1 as of release 18.8)

NOTEs:

  • In IP Application Node test case (SIP VoIP Tab), the number of SIP Subscribers can be up to 50K. This is controlled by a license upper limit value.
  • 50K is the max value for appliances and VMs with Max Sessions of 50K or greater.
  • For licensing levels where the Max Subs is less than (<) 50k, this value will be equal to the number of Max Sessions supported.

Tcl Parameter: SipSubscribersPerUe

Enable Multiple Terminate Calls

Select to support unexpected SIP INVITE and MSRP call path setup. This unexpected SIP call initiated from SUT side and this scenario happens if there are any stored MSRP messages in CPM. In that case SUT will initiate SIP call towards the UE once UE is registered for both Originate and Terminate UE.  

When enabled, additional SIP clients acting as TERMINATE Sip Client, are ready to handle the INVITE as SUT would send it.

Available in AMF Nodal, MME Nodal, SGW Nodal, Wifi Offload Gateway Nodal. 

Tcl Parameter: UeMultTermCallsEn

IMS APN or IMS PDU (in Vo5G)

The values listed depends on the value you select in the Default Bearers per Session on the Mobile Subscriber pane of the Test Configuration tab. In Wifi Offload Gateway Nodal Test Case, the values depend on the Mobile Subscribers APN Settings (if Specify Mobile Subscribers APNs is enabled).

Select the required IMS APN.

NOTE:
  • IMS APN is not available in IP Application Node test case.
  • In UPF Nodal, IMS APN is replaced with IMS PDU (Protocol Data Unit). The values listed depends on the value you select in Number of PDUs on the Mobile Subscriber pane.

 

Tcl parameter: ImsApnIndex

Tcl parameter: Ve911ImsApnIndex

Functionality Pattern

Select to indicate the SIP functionality pattern Originate Terminate (OTOT...), Terminate Originate (TOTO...), All Originate, or All Terminate.

Option: OTOT... (0); TOTO... (1); All Originate (2); All Terminate (3)

See also VOLTE Calls and Phonebook Map.

Tcl Parameter: UePattern

Tcl Parameter: Ve911UePattern

Starting Audio RTP Port

The port number for the first port of the RTP Audio session.

Range: 1 - 65534

Default: 6000

Tcl Parameter: UeRtpAudioPort

Tcl Parameter: Ve911UeRtpAudioPort

Starting Video RTP Port

The port number for the first port of the RTP Video session.

Range: 1 - 65534

Default: 7000

Tcl Parameter: UeRtpVideoPort

Tcl Parameter: Ve911UeRtpVideoPort

Starting MSRP Port

The first port of the MSRP session. The starting MSRP Port number should be different from the RTP Audio/Video port numbers.  

Range: 1 - 65534

Default: 2855  

Tcl Parameter: UeMsrpPort

Tcl Parameter: Ve911UeMsrpPort

Starting RTT Port

The port number for the first port of the RTT (Real Time Text) session.

Range: 1 - 65534

Default: 8000

Tcl Parameter: UeRttPort

Tcl Parameter: Ve911UeRttPort

Gm Retained After Handoff

Available when test case is Inter Technology Mobility.

Default = False

Tcl Parameter: GmRetainedEn

Enable OPTIONS Timer (s)

Available for GM Interface only (between UE and P-CSCF). Not available when Supplementary is enabled.

The OPTIONS Timer will start when the UE is successfully registered.

Range: 1 - 65535

Default = 60 (Seconds)

Tcl Parameter: UeOptionsEn

Tcl Parameter: UeOptionsTimer

Tcl Parameter: Ve911UeOptionsEn

Tcl Parameter: Ve911UeOptionsTimer

Enable Separate Phonebook

Available on E911 VoLTE tab (or Volte 2 tab). When enabled a second E911 Phonebook Tab or Phonebook 2 becomes available for input.

Supported on the MME Nodal test case when Emergency PDNs is enabled and 2-Way Live Audio Bridging is enabled, E911 VoLTE and E911 Phonebook become available when Enable Separate Phonebook is enabled.

Supported on the MME Nodal test case when Emergency PDNs is not enabled but 2-Way Live Audio Bridging is enabled, VoLTE 2 and Phonebook 2 become available when Enable Separate Phonebook is enabled.

 

Tcl Parameter: Ve911SeparatePhonebookEn

Enable Preconditions

Select to indicate support for SIP Preconditions, which ensures network resources are reserved (using pre-defined reservation mechanisms before beginning a session) for a SIP session. Additional details in the SIP Editor.

NOTE: When attempting to publish dedicated bearer information required for the VisionWorks Results (Customizing Report Options) capability with VoLTE tests (when the Info Tab is enabled), the VoLTE Enable Preconditions checkbox must be enabled.

 

Tcl Parameter: PreconditionsEn

Tcl Parameter: Ve911PreconditionsEn

Resource Reservation Delay (ms)

Available when Enable Preconditions is selected in the Wifi Offload Gateway Nodal and IMS Nodal  (Mw/ISC) interfaces test cases. Use when 183 Session progress is included/required with Preconditions.

Enter Resource Reservation Delay in ms.

Range: 1 to 65535.

Default = 10

Tcl Parameter: ResourceResvDelayEn

Tcl Parameter: ResourceResvDelay

Enable Supplementary

Select to edit and define customized SIP flows, actions, and messages or use the default/Built-in flows.

NOTES:
  • You may need to add a Wait-For-Time Built-in Action after the initial SIP Register when using SIP Supplementary Built-in Scripts. The Wait-For-Time Delay will depend on the response time of the test requirements. 

 

Clearing your select displays the default flow and you may edit the SIP headers as required.

Tcl Parameter: SupplementalEn

Enable Emergency

In MME Nodal, AMF Nodal, gNB CU SA Nodal, etc test cases, select to allow setting up of Emergency call flow functionality. The Emergency service requires you to define the phone number associated with Public User Identity. Configure Emergency Phone Number to Emergency Service URN Translation table for SIP Endpoints and SIP Subscribers.

In MME Nodal, added initial support for PSAP - LPP to Presense-based GEOPRIV location object format (RFC 4119)- sent in the SIP INVITE for Emergency Calls in xml format.

Tcl Parameter: EmergencyEn

NOTE: The following dependencies apply when you select Enable Emergency:

  • S11 | GTPv2 | MS ISDN is enabled

  • Gm | P-Headers are enabled (and greyed and you cannot change them).

  • VoLTE | Enable Mobile to Mobile is not available

  • VoLTE | Enable Registration is enabled by default (and greyed)

  • VoLTE | Functionality Pattern is set to All Originate (and greyed)

  • Phonebook | SIP Endpoints | Emergency Phone to Emergency service URN translation is available for configuration.

Enable Mobile to Mobile

Select to allow Mobile to Mobile (back to back) testing. Only the two functionality patters, OTOT... (0); TOTO... (1) are available and uses SIP Subscriber phonebook for originating or terminating calls with the SIP Server Profile, depending on your selection. The test case uses IMS Node as a proxy.

When you select Enable Mobile to Mobile, calls are established between the Mobile Subscribers belonging to the same test case (that is, subscribers populated in the phonebook).

See also VOLTE Calls and Phonebook Map.

Tcl Parameter: BackToBackEn

Enable Subscription

If enabled, SIP Subscriber will send "SUBSCRIBE" requests for all the users that are getting registered.

Tcl Parameter : SipSubscriptionEn

Tcl Parameter : Ve911SipSubscriptionEn

Enter Subscription Expires in seconds. (Per TS24.229 section 5.1.1.3 - Expire Header)  

Range: 0 to 4294967295

Default: 600000

Tcl Parameter : SipSubExpires

Tcl Parameter : Ve911SipSubExpires

Enable Call Setup

When checked, the fields in Call Info will become available.

For "Registration Only" Mode, Disable "Enable Call Setup", and use the fields in the Registration tab to will send "REGISTER" request with or without Deregistration. In the configurable SIP, the GM -> Control tab will show a new message flow that includes only registration related messages.

NOTE:

  • Either Enable Registration or "Enable Call setup" must be enabled otherwise VoLTE Nodal will not trigger any traffic.
  • Enable Registration and "Enable Call Setup" work in conjunction.  For "Registration Only" Mode, Disable "Enable Call Setup".
  • "Register Only" mode is also supported using Script/Action approach via Supplementary Services or ODC/Sequencer.

 

Tcl Parameter : SipCallSetupEn

Tcl Parameter : Ve911SipCallSetupEn

Enable RTP Traffic

Select to indicate that the RTP (Real-time Transport Protocol) data traffic that supports/ carries the media streams (e.g., audio and video) and configure Gm > Media-RTP parameters.

NOTE: The RTP DMFs requires Originate and Terminate sides to have the same add/remove configuration to function correctly. See also VOLTE Calls and Phonebook Map.

 

Tcl Parameter : RtpTrafficEn

Tcl Parameter : Ve911RtpTrafficEn

Enable MSRP

Select Enable MSRP to configure MSRP within SIP/SDP parameters on Gm | Media | MSRP tab. After you Enable MSRP, select Send Messages on the Gm | Media | MSRP tab to define MSRP options and send messages.

Tcl Parameter : MsrpEn

Tcl Parameter : Ve911MsrpEn

Enable SMS-over-IP

Support SMS-over-IP as specified in 3GPP TS 24.341 and 24.011. SMS-over-IP is one of the ways to support traditional short messages over the IMS network. Different from MSRP, SMS-over-IP does not establish and manage a separate session to send/receive short messages, instead, short messages are carried over SIP Message packets directly. The SMS messages in the format defined in 3GPP TS 24.011 are included in the payload of the SIP MESSAGE packets.

Enables the SMS tab for configuration.

Available when IMS Node Type = Remote and when Interface = Gm.

When enabled, IP-SW-GW PSI (IP Short Message Gateway) is between the mobile subscribers and SMS Service Centre PSI to provide transport layer inter-working for submission and delivery of short messages.  

Tcl Parameter : SmsOverIpEn

Enable Late SDP Offer

Select to enable Late Media Support. Available when Enable Call Setup is selected. If enabled:

  • will not send SDP with the INVITE message
  • expects to receive SDP offer in 183 message
  • will respond with SDP answer in the PRACK message

Tcl Parameter : UeLateSdpOfferEn

Tcl Parameter : Ve911UeLateSdpOfferEn

REGISTER Response Delay (ms)

Select to configure a delay (in milliseconds) before sending the response to SIP REGISTER request. The delay will be applied to "401 Unauthorized" or "200 OK" responses depending if registration mode is secure or not. This delay will be applied to the very first response only.

The delay will not be applied to"

  • protected REGISTER if secure mode
  • DE-REGISTER (expires = 0)

Range = 1 to 65535

Default value = 1 ms

Tcl Parameter : RegRespDelayEn

Tcl Parameter : RegRespDelay

Tcl Parameter : Ve911RegRespDelayEn

Tcl Parameter : Ve911RegRespDelay

INVITE Response Delay (ms)

Select to configure a delay (in milliseconds) before sending the response to SIP INVITE request. This applies to all possible SIP INVITE Messages (180 / 183 / 200 OK)messages. The message in which it applies is determined by your call flow information configuration. See Call Flow Info Panel.

Range = 1 to 65535

Default value = 1 ms

Tcl Parameter : InviteRespDelayEn

Tcl Parameter : InviteRespDelay

Tcl Parameter : Ve911InviteRespDelayEn

Tcl Parameter : Ve911InviteRespDelay

Final Response Delay (ms)

Select to configure a delay (in milliseconds) before sending the final (200 OK) response to SIP INVITE request. This only applies to the final 200 OK message.

Range = 1 to 65535

Default value = 1 ms

Tcl Parameter : Delay2xxForInvValEn

Tcl Parameter : Delay2xxForInvVal

Tcl Parameter : Ve911Delay2xxForInvValEn

Tcl Parameter : Ve911Delay2xxForInvVal

Traffic Start

Indicates when the traffic registration starts.

NOTE: Traffic start mode (When All Session Established or When Session Established ) must be the same when VoLTE and DMF use the same APN or No APN.

 

Options: When All Session Established (0); When Session Established (1)

Default: When Session Established (1)

Tcl Parameter : UeRegStart

Tcl Parameter : Ve911UeRegStart

Enable Multimedia Priority Service (MPS)

Select to enable the Multimedia Priority Service (MPS).  In order for initiating a priority call, an originating UE needs to include a SIP Resource-Priority header with its outgoing INVITE requests; and, a core network will decide whether such calls are allowed based on current resources. Originating UE could include multiple priority levels for a same or different namespaces (Per RFC 4412).  A priority level is text string consisting of a namespace and a level separated by a dot such as “wps.4”.  Multiple levels are allowed and they are separated by a comma and a space such as “wps.4, wps.3”.  

By default, this input text box is set to “wps.4” for indicating priority level 4 of the “Wireless Priority Service” namespace.

The WPS namespace derives its name from the "Wireless Priority Service:, defined in GSM and other wireless technologies. The  WPS namespace defines the following resource values, listed from lowest priority to highest priority:

(lowest)  wps.4

               wps.3

               wps.2

               wps.1

(highest) wps.0

RFC 4412 specification defines five unique namespaces : DSN, DRSN, Q735, ETS, and WPS, constituting their registration with IANA. Refer to RFC for additional details.

Enable for VoLTE Priority Call.

Tcl Parameter : UeMpsEn

Tcl Parameter : UeMpsLevel

Tcl Parameter : Ve911UeMpsEn

Tcl Parameter : Ve911UeMpsLevel

MPS Mandatory

Checkbox is used for indicating to a receiver of MPS request whether processing MPS is mandatory. When checked, a receiver (such as IMS-Node) will react differently (i.e. ignore unknown resource or forbid unknown resource).

Tcl Parameter : UeMpsMandatoryEn

Tcl Parameter : Ve911UeMpsMandatoryEn

Enable RTT OTT Client

Available in SGW Nodal and Wifi Offload Gateway Nodal test cases. Enables the OTT Access Auth Tab under the Gm Interface.

The difference between native VOLTE Client and RTT OTT Client can be summarized as following:

  • RTT OTT Client and native VOLTE Client use different APNs
  • Native VOLTE Client’s Public and Private Identities are provisioned on LS GUI (Phone Book). RTT OTT Client receives its Public and Private Identities from the network during user authentication process.
  • RTT OTT has to initiate user authentication against API GW using HTTP/HTTPS protocol prior to IMS registration. This authentication is based on OAuth authorization framework defined by RFC 6749.
  • As a result of OAuth RTT OTT Client receives
    • IMPU (Public User ID) that will be used instead of the one that is configured on GUI;
    • IMPI (Private User ID) that will be used instead of the one that is configured on GUI;
    • SBC FQDN: usually SBC FQDN has to be resolved by DNS and used as SBC/P-CSCF IP address. To simplify it Landslide VOLTE solution has P-CSCF IP address configured on GUI.

Tcl Parameter : UeOttAuthEn

Tcl Parameter : Ve911UeOttAuthEn

Enable GETS Analysis

Available in AMF Nodal, IP Application Node and MME Nodal test cases. Enabled when Supplementary Mode is turned on. Select for Government Emergency Telecommunications Service (GETS) KPIs to be reported to the TEST.PROCS file. 

This is a licensed feature. The GETS Feature requires POLQA to be enabled and UE Info Level set to 10 for the Test Server assigned for AMF Nodal and MME Nodal (MO and MT).

The TAS has been enhanced to record the announcements which are compressed to tar.gz and become a part of the "Test Results" when Enable GETS Analysis is enabled. Storing the announcement for GETS core call aids in the assessment of call failure conditions. 

  1. Once a test is completed, all the .wav files belonging to that particular test session can be found at /home/spcoast/sNNNN/tsNNN where NNNN is the RID number . 
  2. ALL the .wav files from /home/spcoast/sNNNN/tsNNN are compressed to tcIndex_announcement.tar.gz. and saved at /home/spcoast/sNNNN/tsNNN where TAS can retrieve based on the file extension. 
  3. The wave file is compressed to tcIndex_announcement.tar.gz. The TAS adds the STARTTIME_RID_tsN_ prefix.   (Example:  21-01-21_22_24.27_RID-281_tc0_announcewav.tar.gz). 
  4. The wave file itself is named tsN_tcN_ueN_subN_stream_N.wav, tsN where N is the test server number, where N is the test case index, ueN where N is the UE Index, subN where N is the subcriber index, streamN where N is the RTP stream number.
  5. Limitation / Caveat : Test Server must be configured with Legacy mode and POLQA resources, Fireball not supported, No UE specific index for this release, Turn on "Do not delete temp files", Turn on Per Session results. 

The user can open the compressed file to get their .wav file from test results.

The GETS KPIS are :

GETS VOICE_TONE_RECEIVE_FAILURE - Voice tone was not received

UE_VOLTE_GETS_PIN_FAILURE - GETs PIN error message was not recognized

UE_VOLTE_GETS_DEST_ NUM_PLAY_FAILURE - Playback failure “Please enter your destination number now"

UE_VOLTE_GETS_PLAYBACK_ FAILURE - Playback failure “You are using GETS xxxxx”

Tcl Parameter : GetsAnalysisEn

Enable Registration Failed Threshold (%)

Available in AMF and MME Nodal test cases when Enable Registration and Calls Start After = " When All Users Registered".

When Enable Registration Failed Threshold is enabled, even if all Sessions are not established, if the PDN Failed Threshold (%) percentage on MME Nodal or Registration Failed Threshold (%) on AMF Nodal or PDU Failed Threshold (%) percentage on SMF Nodal, is within this limit, SIP Registration will be initiated for rest of the established PDUs. Otherwise when not enabled, if the Traffic Start pattern chosen is "When All Session Established", only when all the PDU are established VOLTE will start Registration. 

Similarly in case of Volte Call, if the Call Start pattern chosen is "When All User Registered", however even if all Sessions are not Registered, if the Registration Failed Threshold percentage is within the limit, SIP Call will be initiated for rest of the registered UEs. 

On AMF/MME/SMF Nodal VOLTE tab to support Registration Failed Threshold percentage, there are 2 layers of thresholds :

Example :
1000 UEs are configured 
50 failed to establish a pdu (or PDN for MME nodal)
your threshold is 10% , threshold not exceeded 
thus 950 will continue to register

 

Example : a threshold for the SIP invite, percentage based on the SIP registered UEs 
1000 UEs are configured 
50 failed to SIP register  
your threshold is 10% , threshold not exceeded 
thus 950 will continue to send invite 

 

Range : 0 to 100

Default : 10

Tcl Parameter: UeRegFailThreshPctEn

Tcl Parameter: UeRegFailThreshPct

Enable OIDC User Authentication for MCPTT

Available in IP Application Node, MME Nodal, PGW Nodal, SGW Nodal and Network Host (server DMF only) test cases when Enable Supplementary is selected. Enables the OIDC User Auth Tab under the Gm Interface.

Select for UE authentication for Mission Critical Push-to-Talk (MCPTT) as specified in the 3GPP TS 23.280, 22.179, 23.179, 24.379, 24.380, 33.179, 24.382, 24.384 specifications, OpenID Connect 1.0, and IETF RFC 6749 (OAuth 2.0).

Mission Critical Push-to-Talk (MCPTT) is one of important technologies that helps to enable the public safety broadband network proposed by First Responder Network Authority (FirstNet).

MCPTT is one of the services under the 3GPP Mission Critical Services (MCS) framework. All of the MCS utilize the MC core provided by 3GPP networks to enable MCS subscribers to communicate with fast setup times, strong security and priority handling. MC services include MCPTT, as well as MC Data, MC Video, etc. These services are provided in two modes, On-network, which is using E-UTRAN and EPS bearers, and Off-network, which is using public safety Proximity Services (ProSe).   

MCPTT client is authenticated and authorized for MCPTT service through interfaces between identity management, key management, group management clients (reside in MCPTT client) and identity management, key management, group management servers in Common Service Core (CSC). This feature focuses on the interface CSC-1, which is between identify management client and identity management server. Please see the following diagram from 3GPP TS 23.280.

Landslide is emulating MCPTT clients, SIP core, and MC service domain. Identity management client is part of MCPTT UE. However, Identity management server is part of CSC and a logic function outside of MCPTT server. Identity management server (or the HTTP proxy in the same domain as the IdM server) can be emulated by a separate Network Host test case with Landslide DMF:

OAuth is a widely-used authorization framework based on HTTP. It allows applications to access resources on other servers in a secure and efficient way, without passing credentials from the resource owner to the third-party applications directly. Instead, it obtains tokens from the resource owner, and using the tokens to access the protected resource for a specific scope, lifetime, and with other access restrictions.

OpenId Connect ((http://openid.net/connect/faq)) is a thin layer built upon OAuth 2.0 to enhance the flows to perform authentication properly.

Tcl Parameter : UeOidcAuthEn

Enable Floor Control for MCPTT

Available in IP Application Node, MME Nodal, PGW Nodal, SGW Nodal, WiFi Offload Gateway Nodal and IMS Node test cases when Enable Supplementary is selected. Enables the OIDC User Auth Tab under the Gm Interface. Select to enable Floor Control for Mission Critical Push-to-Talk (MCPTT) as specified in the 3GPP TS 23.280, 22.179, 23.179, 24.379, 24.380, 33.179, 24.382, 24.384 specifications.

Floor control is used to determine which subscriber has the authority to talk at a certain time during an MCPTT call. Please refer to 3GPP TS 23.179 for floor control commands and procedures, and 3GPP TS 24.380 Clause 8 for floor control protocol over RTCP. We will support the following commands : Floor Request, Floor Granted, Floor Idle, Floor Release and Floor Taken and procedure "Floor Request, Floor Granted and Floor Taken during an MCPTT Session".  several new SIP Built-in Actions and two new SIP Built-in Scripts are available for Floor Control.  

Landslide test cases are acting as MCPTT UE, SIP Core and Application Services layer.

An MCPTT private call is between two users. An MCPTT group call is between several users, where each user has the ability to gain access to the permission to talk in an arbitrated manner. TS 24.379 Landslide will provide means to emulate both types of the calls. Two new SIP Built-in Scripts are provided for the following two types of flows. One is private call with floor control (MCPTT Private Call with Floor Control) and the other is prearranged group call (MCPTT Group Call with Floor Control). In addition, several new SIP Built-in Actions are provided :

Action Name

Description

MCPTT_PrivateCall_Connect

Establish a MCPTT Private Call Connection

MCPTT_GroupCall_Connect

Set up MCPTT Group Call for 5 users with floor Control

MCPTT_PrivateCall_Floor_Request

Send Floor Request for Private Call

MCPTT_PrivateCall_Floor_Release

Send Floor Release for Private Call

MCPTT_GroupCall_Floor_Request

Send Floor Request for Group Call

MCPTT_GroupCall_Floor_Release

Send Floor Release for Group Call

 

Enter the Starting Floor Control RTCP Port. Range : 1 to 65535 , Default : 10000

Tcl Parameter : UeFloorCtlEn

Tcl Parameter : UeFloorCtlRtcpPort

DSCP Value

Available for Gm interface.

The DSCP (Differentiated Service Code Point - RFC 2474) is a mechanism, for classifying and managing network traffic and providing quality of server (QoS) by providing low-latency to critical network traffic such as voice or streaming media while providing simple best-effort service to non-critical services such as web traffic or file transfers. It is 6 bits in the differentiated services fields (DS Field) in the IP Header.

Range : 0 to 255

Default : 0

The DSCP Calculator becomes available for input.

Tcl Parameter : UeDscpValue

Enable Registration

Select to send a registration request from the UE to a Registrar server.

NOTE: Enable Registration is mandatory for back to back testing.

The following are available when you select Enable Registration:

  • Expires: The length of time for which the UE registration is valid. When the time specified expires, the UE should register again.

  • Temporary User ID: When checked, the IMSI from the PhoneBook Tab is used for Registration as Temporary User ID. Per 3GPP TS 23.238

NOTES:

  • An IMS network element is designed to support not only UE which has IMS credential (has IMC or ISIM) but also those without IMS credential (ISIM-less, IMC-less i.e. UE supports non-3gpp access only). When a UE does not have IMS credential, the UE can create a temporary user id from its IMSI for registering with the IMS. Upon successful registration, the IMS network will provide the UE with new user/public ids for subsequent usage (i.e. making calls). New ids are stored in P-Associated-Uri of a 200-OK response of Register from IMS.
  • The landslide “Temporary User Id” check boxes are designed to simulate the functions of IMS and UE to cover the condition of no IMS credentials.

  • The checkbox on the nodal side is used for simulating UE function and the one on the node side is for the IMS function. You need to enable both sides in order for them to inter work correctly.

 

  • Retry Timeout: The number of seconds the UE waits before starting subsequent registration attempt. If a Registration fails, the UE does not re-attempt Registration immediately. It waits for a period specified (Retry Timeout of seconds) and then repeats.

NOTE: For UDP protocol, the retransmission of a SIP general requests is based on 2 timers: T1 and T2. If a request does not receive a response, the request is sent again in T1 seconds and increments of T1 seconds (T1 + T1) and continues to re-transmit every T2 seconds until it exceeds 64*T1 seconds. [RFC 3261]

  • Number of Retries: The number of registration attempts. Enter 0 to disable retries.

Tcl Parameter :

SipRegEn

SipTempId

SipRegExpires

SipRegTimeout

SipRegRetries

Ve911SipRegEn

Ve911SipTempId

Ve911SipRegExpires

Ve911SipRegTimeout

Ve911SipRegRetries

 

Enable Deregistration on Call Release

If enabled, UE Sip subscriber deregisters on each call release and registers on before every call setup. Default = False

Tcl Parameter : SipDeregOnReleaseEn

Tcl Parameter : Ve911SipDeregOnReleaseEn

Alter Security Header

Available when Enable Authentication is selected.

Select to modify the "Security-Client" header. Security-Client is modified each time UE is registering or deregistering to negotiate different

SPI-C, SPI-S, secure port-C, secure port-S.

Default = False

Tcl Parameter : SipAlterDeregSpiEn

Tcl Parameter : Ve911SipAlterDeregSpiEn

Hold Time (s) Pend Time (s)

Used for Registration only test cases. Once the subscriber is registered, the next Registration will be sent after Hold Time + Pend Time.

If Enable Deregistration is checked, once the subscriber is Registered, the Deregistration message will be sent out after the Hold Time (r) expires and after the Pend Time (r) expires, the new Registration will be sent out.

Range: 0 to 65535

Default: 5

Tcl Parameter : SipRegHoldTime

Tcl Parameter : SipRegPendingTime

Registration Rate

Available when you select Enable Registration.

If Enable Supplementary is selected, the fields are called Script Rate scripts/s and Script Delay (s).

  • Registration Rate (reg/s): Indicates the rate of traffic registered per second. Able to modify while test is running.

Option: 0.0010 - 3000.00

Default: 1000

  • Registration Delay (s): Indicates the length of time to wait before attempting to register traffic with the registrar.

Option: 1 - 65535

Default: 10

Tcl Parameter : UeRegRate

Tcl Parameter : UeRegDelay

Tcl Parameter : Ve911UeRegRate

Tcl Parameter : Ve911UeRegDelay

Deregistration Rate (reg/s)

Enter Deregistration rate to be used on a graceful stop.

  • This Timer value is based on type of Test configured. For Registration only test case, this De-Registration Rate value will be used.
  • For other cases, Call Release Rate will be used to terminate the session and hence De-Registration will occur.
  • CAVEAT: If the Deregistration rate timer value is set too low, you can see a burst of De-registrations. For example, if you have 4K Subscribers and De-Registration/Call Release rate is set to 1 sub/sec, you will see constant De-Registration up to some time, and then you will see a burst of De-Register messages.

Option: 1.0 - 1000.0

Default: 1000.0

Tcl Parameter : SipDeregRate

Enable 3rd Party Registration

Available on IMS Nodal when ISC Interface is enabled. Enable for support of third party registration. 3rd Party registration involves encapsulating the SIP REGISTER and 200 OK messages exchanged between P-CSCF and I/S-CSCF as message body in the SIP REGISTER sent from S-CSCF to SCC-AS. This is a licensed feature.

Third-party REGISTER request and 200 OK will be embedded as a message body.  

Tcl Parameter : Sip3rdPartyRegEn

Ensure Constant Rate

If enabled, REGISTER message will be sent continuously on a timed basis. After first successful REGISTER, timer will start and subsequent Register messages will be sent based on timer value. Timer value is calculated by:

Example to calculate the time value:

Registration Rate = 50/sec

Number of Mobile nodes = 100

 

Case 1: Sip subscriber per UE=1

TimeValue in milli secs = (Number of Mobile Nodes X Sip subscriber per UE X 1000) / Reg Rate

                                     = 100 X 1 X 1000/50

                              = 2000 ms = 2secs

 

Case 2: Sip Subscriber per UE=2

TimeValue in milli secs = (Number of Mobile Nodes X Sip subscriber per UE X 1000) / Reg Rate

                                     = 100 X 4 X 1000/50

                              = 4000 ms = 4secs

Not supported for Supplementary messages.

NOTE: May be used in conjunction with Enable Deregistration thus user is able to generate continuous registrations and/or continuous registrations plus de-registrations.

 

Tcl Parameter : EnsureConstantRegRateEn

Ensure Reregistration

Select to reregister during an active call. The re-registration will occur based on 1/2 the value of the Expires (s) parameter.

Tcl Parameter : EnsureReRegEn

Terminator Initiate Deregistration

Select for terminator to initiate Deregistration. Enabled when Registration is checked or implied, and disabled for Supplementary or Command Mode/Sequencer.

This checkbox will facilitate cleanup of resources for MT as well as by initiating BYE and subsequent De-Registration.

Tcl Parameter : SipTermInitDeRegEn

Override Expires (s)

Enable to override the Expires timer. Enter the override expires timer value in seconds. The Re-Register message will be sent when the Override Expiry timer value expires. Available when  Enable Registration is selected. Range: 0 to 4294967295 Default: 600

Tcl Parameter : SipRegOverrideExpiresEn

Tcl Parameter : SipRegOverrideExpires

Tcl Parameter : Ve911SipRegOverrideExpiresEn

Tcl Parameter : Ve911SipRegOverrideExpires

Try All Available P-CSCFs if Any Failed

Reattempt All Available P-CSCFs if Failed

 

Reattempt Wait Time (s)

Select to enable trying other available P-CSCFs retrieved from PCO if any have failed.

Available in AMF Nodal , MME Nodal, SGW Nodal and Wifi offload Gateway Nodal test cases.

Select Reattempt All Available P-CSCFs if Failed to start over and reattempt all available P-CSCFs in the PCO, if previous attempt fails.

Enter the Reattempt Wait Time in seconds.

Range : 0 to 65535

Default : 120 seconds

After the Number of Retries, if UE still gets error code as one of 403(Forbidden), 408(Request Timeout), 480(Temporarily Unavailable), 500(Internal Server Error), 503(Service Unavailable), and 504(Server timeout), or TCP connection is failed to establish, then UE will switch to the next P-CSCF.

If after the UE tries all P-CSCF addresses using the procedure shown section for Override Timer Values for Registration but still fails to register to IMS, it will repeat the registration procedures again, after a fixed configurable time interval.

 

Tcl Parameter : SipRegTryAllPcscfEn

Tcl Parameter : SipRegReattemptPcscfEn

Tcl Parameter : SipRegReattemptWaitTime

Enable Authentication

Available only when you select Enable Authentication. (In AMF Nodal, SGW Nodal, MME Nodal, IP Application Node, IMS Node test cases, etc.)

Select the type of authentication used by an IMS Node to authenticate communication between UE and IMS Node (Authentication Server).

HTTP Digest

Indicates support for HTTP Digest using MD5 (RFC 3261 and RFC 2617) which provides the digest password generation.

IMS AKA

Indicates support for IMS AKA authentication (RFC 3310 provides mechanism maps to AKA parameters to HTTP Digest Authentication parameters).

 

Authorization Header

Select to Add @Domain to the Username Field.

Used to enable/disable adding domain name in the Auth Header username.

Tcl parameter : UeAuthHeaderAddDomainToUsernameEn

Tcl parameter : Ve911UeAuthHeaderAddDomainToUsernameEn

The AKA Version, Operator Variant, and Enable IPSec are only available  when you select Authentication type as IMS AKA.  

AKA Version Select to indicate the AKA version used for authentication. Options : 1 or 2
Algorithm

Select an Authentication Algorithm. Additional fields become available for input.

Options : Milenage ( Defined in 3GPP TS 35.205) , Test Algorithm ( Defined in 3GPP TS 34.108) , TUAK ( Defined in 3GPP TS 35.231)

TUAK is a 3GPP defined algorithm and key generation set of functions (f1, f1*, f2, f2, f4, f5, and f5*). 

TUAK is currently available in AMF Nodal, MME Nodal when VoLTE is enabled, IP Application Node when SIP VoIP is enabled (Gm Interface), and IMS Node (Gm Interface) - See IMS Authentication.

Tcl Parameter: UeAuthAlgorithm

RES Length (bytes)

Per 3GPP (33.102) specified RES Length of 4-16 octets. Not available when Use Real SIM Card or Use SIM Server is enabled on the Mobile Subscribers Pane. IMS AKA Authentication via using SIM Server.

Available when Algorithm = Milenage or Test Algorithm.

Range: 4 to 16

Default : 8

Tcl Parameter : UeAuthResLen

Tcl Parameter : Ve911UeAuthResLen

Operator Variant

The 128-bit, operator-specific MILENAGE constant (OP) provisioned for the network. Not available when Use Real SIM Card or Use SIM Server is enabled on the Mobile Subscribers Pane. IMS AKA Authentication via using SIM Server.

Available when Algorithm = Milenage or Test Algorithm.

Select OPc to add authentication with OPc value.

Range: Up to 32 hex characters, excluding "0x."

Default: 0x63BFA50EE6523365FF14C1F45F88737D

Encrypt - Click on Encrypt to encrypt the Operator Variant / OPc. Any user type can enter the value in plain text, and then click an “Encrypt” button which will encrypt the value and switch the TC-GUI to use parameter variable name with _Enc Suffix. (encrypted-mode). The fields in the GUI will become like passwords with just "****************" in them and they will be not be edit able. When the Operator Variant / OPc is encrypted , the TDF-CSV editor will automatically encrypt the value when it is saved in the cell "Operator Variant Encrypted" or "Operator-c Variant Encrypted". Additonal details in Apply Test Data File to NAS Protocol.

Decrypt - Click on Decrypt to decrypt the Operator Variant / OPc.

TUAK Algorithm

The following fields become available when Algorithm = TUAK. For information about how the fields are used in the TUAK algorithm the user should refer to the 3GPP TS 35.231 specification.

Key This is the secret key and is analogous to the Milenage Secret Key field. Enter either a String value or a Hex value beginning with 0x.

Tcl Parameter: UeTuakKey

TOP The Edit Top data input box associated with TOP allows the user to input a 32 byte Hex string value used for the operator variant. Tcl Parameter: UeTuakOpType
Key Length (bytes) Select the maximum length supported for the secret key. Support for 16 or 32 bytes. Tcl Parameter: UeTuakKeyLen
RES Length (bytes) Select the maximum length supported for the RES value. Support of 4 or 8 bytes only. Tcl Parameter: UeTuakResLen
Keccak_f Iterations Enter the number of times the Keccak permutation is performed. Range : 1 to 255 Default : 1 Tcl Parameter: UeTuakIterations
MAC Length (bytes) Select the maximum length supported for the MAC fields (MAC-A and MAC-S). Support 8 bytes. Tcl Parameter: UeTuakMacLen
CK Length (bytes) Select the maximum length supported for the confidentiality key. Support 16 bytes only. Tcl Parameter: UeTuakCkLen
IK Length (bytes) Select the maximum length supported for the integrity key. Support 16 bytes only. Tcl Parameter: UeTuakIkLen

Tcl Parameter :

SipUeAuthenticationType

SipUeEncryptionAlgorithm

UeAkaVersion UeAuthenticationEn

UeOpVar

UeOpVar_Enc

UeOpType

Ve911SipUeAuthenticationType

Ve911SipUeEncryptionAlgorithm

Ve911UeAkaVersion Ve911UeAuthenticationEn

Ve911UeOpVar

Ve911UeOpVar_Enc

Ve911UeOpType

 

Enable IPSec: Available only when you select Authentication. Select to indicates that VoLTE supports IMS-AKA with and without IPSec, which is configurable on a per UE/SIP client basis.  

Tcl parameter : UeIpSecEn

Tcl parameter : Ve911UeIpSecEn

  • ESP Data Mode: Available when you select Enable IPSec. Select the Data Mode to be transmitted between the UE and the IMS Node.

Options: Transport, Tunnel

Default: Transport

Tcl parameter : UeEspDataMode

Tcl parameter : Ve911UeEspDataMode

  • Encryption Algorithm: Available when you select Enable IPSec. Select the method of cryptographic encryption of the data to be transmitted between the UE and the IMS Node.

Options: NULL, DES_EDE3_CBC, AES_CBC

Default: NULL

Tcl parameter : UeEncryptionAlgorithm

Tcl parameter : Ve911UeEncryptionAlgorithm

  • Security Algorithm: Available when you select Enable IPSec. Select the Security Algorithm - Ensures packet message integrity between two parties is intact.

Options: HMAC-MD5-96 (Default) , HMAC-SHA-1-96

Default: HMAC-MD5-96

Tcl parameter : UeSecurityAlgorithm

Tcl parameter : Ve911UeSecurityAlgorithm

  • Number of Tunnels per Subscriber: Available when you select Enable IPSec. Select the number of IPSec tunnels per subscriber.

Options: 2, 3 or 4

Default: 4

Tcl parameter : UeTunnelsPerSub

Tcl parameter : Ve911UeTunnelsPerSub

Use Test Algorithm for Authentication - available only when you select Enable Authentication and Authentication Type = "IMS AKA". Select to use test algorithm for Authentication.

Tcl parameter : SipUeAuthTestAlgoEn

Tcl parameter : Ve911SipUeAuthTestAlgoEn

Reuse Credentials (nonce/response) - available only when you select Enable Authentication. Select to reuse previous credentials (nonce/response).

Tcl parameter : UeReuseCredentials

Tcl parameter : Ve911UeReuseCredentials

Reuse Cnonce - available only when you select Enable Authentication. Select to always use same cnonce in Registration AND ReRegistration and to use nextnonce as nonce when nextnonce is provided in 200OK message

Tcl parameter : UeReuseCnonce

Tcl parameter : Ve911UeReuseCnonce

Call Flow Info

    Provisional Response

Select to enable Provisional Responses.

Not available when Enable Supplementary is enabled or ODC/Sequencer is selected.

 

Call Connect

100 Trying

Select 100 Trying to send 100 Trying for Provisional Response for Call establishment.

Tcl Parameter : CallEst100ProvisionalRspsEn

Tcl Parameter : Ve911CallEst100ProvisionalRspsEn

Call Connect

183 Session In Progress

Reliable

Select 183 Session In Progress and/or Reliable for flexible configuration of Provisional Response for Call establishment.

When Enable Preconditions  is enabled - both 183 Session In progress and Reliable are automatically enabled.

If Reliable is unchecked, UAS replies with 183, non-reliable, prior to sending 200 OK.

If Reliable is checked, UAS will send 183, reliable, first and then subsequently (after PRACK/200 OK exchange) 183, non-reliable.

NOTE: If Reliable is not checked, the SIP flow on the Gm tab should not include the PRACK/200 OK transaction.

 

Tcl Parameter : CallEst183ProvisionalRspsEn

Tcl Parameter : CallEst183ProvisionalRspsRelEn

Tcl Parameter : Ve911CallEst183ProvisionalRspsEn

Tcl Parameter : Ve911CallEst183ProvisionalRspsRelEn

180 Ringing

Reliable

 

Select 180 Ringing and/or Reliable for flexible configuration of Provisional Response for Call establishment.

When Enable Preconditions  is enabled - 180 Ringing is automatically enabled. Reliable is available but it is not automatically enabled.

 

If Reliable is unchecked, UAS replies with 180, non-reliable, prior to sending 200 OK.

If Reliable is checked, UAS will send 180, reliable, first and then subsequently (after PRACK/200 OK exchange) 180, non-reliable and final 200 OK.

NOTE: If Reliable is not checked, the SIP flow on the Gm tab should not include the PRACK/200 OK transaction.

Tcl Parameter : CallEst180ProvisionalRspsEn

Tcl Parameter : CallEst180ProvisionalRspsRelEn

Tcl Parameter : Ve911CallEst180ProvisionalRspsEn

Tcl Parameter : Ve911CallEst180ProvisionalRspsRelEn

Call Modify

100 Trying

Select to send 100 Trying for Provisional Response for Call Modify.

Tcl Parameter : CallMod100ProvisionalRspsEn

Tcl Parameter : Ve911CallMod100ProvisionalRspsEn

Call Modify

183 Session In Progress

Reliable

Select 183 Session In Progress and/or Reliable for flexible configuration of Provisional Response for Call Modify.

If Reliable is unchecked, UAS replies with 183, non-reliable, prior to sending 200 OK.

If Reliable is checked, UAS will send 183, reliable, first and then subsequently PRACK/200 OK exchange.

NOTE: If Reliable is not checked, the SIP flow on the Gm tab should not include the PRACK/200 OK transaction.

Tcl Parameter : CallMod183ProvisionalRspsEn

Tcl Parameter : CallMod183ProvisionalRspsRelEn

Tcl Parameter : Ve911CallMod183ProvisionalRspsEn

Tcl Parameter : Ve911CallMod183ProvisionalRspsRelEn

Enable SDP Answer in Provisional Response (Preview)

 

Select to generate SDP Offer and SDP Answer for SIP in accordance with RFC 6337. Available on all VoLTE/VoIP Nodal test cases and IMS Node test case for all interfaces (Gm, Ml, etc ) except for Nc.

The basic rule for SIP SDP Answer:

  • If SIP Call Setup includes at least one reliable 1xx message then the first reliable 1xx message includes SDP Answer. SIP 200 OK does not include SDP Answer.
  • If in SIP Call Setup neither 1xx (183 or 180) message includes reliable 1xx then the very first 1xx may include SDP Answer that is for review/inspection by Caller only. 200 must include SDP Answer.

See Call flows showing how SDP Offer / Answer are managed based on Call Flow Options - Provisional Response Configurations:

 

Figure 1-1: INVITE-SDP: 183 - Reliable, 180          Figure 1-2: INVITE-SDP: 183 , 180- Reliable

                     

 

Figure 1-3: INVITE-SDP: 183, 180 - "Preview"       Figure 1-4: INVITE-SDP: 183, 180

                      

Figure 1-5: INVITE- No SDP: 183 - Reliable, 180     Figure 1-6: INVITE- No SDP: 183, 180 - Reliable

                      

 

Figure 1-7: INVITE- No SDP: 183, 180

 

 

In the case of “Enable Late SDP Offer” is not enabled (INVITE includes SDP Offer) and all Provisional responses are unreliable then the first 1xx Response may include the SDP Answer “Preview” (See Section 3.1.1 @ RFC 6337).

As of Release 19.6, "Enable SDP Answer in Provisional Response (Preview)" checkbox is automatically enabled when either Call Connect 180/183 + Reliable is checked. Prior to release 19.6, either of the Reliable checkboxes disabled "Enable SDP Answer in Provisional Response". This change now provides an option to send SDP in 183/180 (Provisional Reliable Response) or in 200 OK of the INVITE. Sending SDP in 183/180 (Provisional Reliable Response) is as per RFC 6637 and sending SDP in 200 OK of INVITE is as per RFC 3261.

NOTE: If Reliable is not checked, the SIP flow on the Gm tab should not include the PRACK/200 OK transaction.

 

Tcl Parameter : CallSdpAnsInProvRspsEn

 

Call Starts After

Available when you select Enable Registration. Indicates when the call starts.

Call Start Delay is a global timer.

In the case "When User Registered" is selected, the timer starts immediately after first UE is registered.

In the case "When All Users Registered" is selected, the timer starts after all UEs are registered.

Options: When All Users Registered (0); When User Registered (1)

NOTE: VoLTE Traffic start will be restricted to "When User Registered" for VoLTE with SRVCC in MME Nodal and SGW Nodal Test cases.

 

Default: When User Registered (1)

Tcl Parameter : UeCallStart

Tcl Parameter : Ve911UeCallStart

Call Hold Time (s)

Available when P-CSCF Mode is SIP Endpoints. Indicates the length of call. Able to modify while test is running.

Option: 1 - 65535

Default: 20 (s)

Tcl Parameter : UeCallLength

Tcl Parameter : Ve911UeCallLength

Call Pending Time (s)

Indicates the idle time. Able to modify while test is running.

Option: 1 - 65535

Default: 10

Tcl Parameter : UeCallPending

Tcl Parameter : Ve911UeCallPending

Call Establishment Rate (calls/s)

Indicates the rate at which the UE attempts to establish calls with the SIP Endpoint. Able to modify while test is running.

Option: 0.001 - 1000.0

Default: 1000.0

Tcl Parameter : UeCallEstabRate

Tcl Parameter : Ve911UeCallEstabRate

Call Start Delay (s)

Indicates the length of time to wait before attempting to establish calls with the SIP Endpoints.

Option: 1 - 65535

Default: 10

Tcl Parameter : UeCallEstabDelay

Tcl Parameter : Ve911UeCallEstabDelay

Call Release Rate (calls/s)

Indicates the rate at which the UE attempts to release calls established with the SIP Endpoint.

Option: 0.001 - 1000.0

Default: 1000.0

Tcl Parameter : UeCallReleaseRate

Tcl Parameter : Ve911UeCallReleaseRate

Session Expires (s)

Enables SIP servers and endpoints to know if an endpoint is no longer in a session (for example, in the event of a crash) and to limit the duration of a session. An endpoint that has the Session Expires timer extension activated, will send periodic keep-alive messages to notify that it is active or to extend the duration of the session. Refer to RFC 4028 - "Session Timers in the SIP".

Not available when Script/Actions are used.. part of regular VoLTE and Supplementary/OCD/Sequencer.

Option: 90 - 65535

Default: 90

Tcl Parameter : ImsNodeSessionExpiresEn

Tcl Parameter : ImsNodeSessionExpires

Tcl Parameter : UeSessionExpiresEn

Tcl Parameter : UeSessionExpires

Tcl Parameter : Ve911UeSessionExpiresEn

Tcl Parameter : Ve911UeSessionExpires

Session Expires Refresher Options Originator Mode Terminator Mode

Available when Session Expires is enabled on VoLTE - Call Info Panel and on IMS Node Emulator Cnfg.

Select to initiate the SIP UPDATE message from a MT VoLTE SIM Server at the expiration of the Session-Expires timer.

Refer to RFC 4028 - The Session Expiry Timer is a SIP Session specific mechanism for Call parties and optionally Proxies to be sure that opposite side of the Call is alive. During a Call Session one of the side, Caller (UAC) or Callee (UAS), sends re-INVITE or UPDATE message and other side of the Call confirms it by sending 200 OK. An example of the SIP Session expiry flow diagram is shown below:

The SIP Session Timer Expiry negotiation is accomplishing during initial Call Setup.

MO (User A for the given example) sends INVITE that conveys:

  1. Header Supported: with value "timer", that means the side does support the Session Timer Expiry
  2. Header Session-Expires: with the Expiry interval value (120 seconds for the given case) and optionally refresher with two optional values: UAC or UAS. The fact, that it is missed in the given example means that it is to User B to decided who will be doing the periodic refreshing updates: UAS or UAC.

MT (User B) in 200 OK to INVITE provides the result of the negotiation it is willing to take:

  1. Header Supported: with value "timer" means that User B is also supports the Session Timer Expiry.
  2. Header Session-Expires: refresher = UAS and Timer Expiry interval of 90 means that UAS side (User B for the given example) will be in charge of sending periodic expiry updates. User B haven't accepted the expiry interval of 120 seconds and changed it to it's own setting: a lower value of 90 seconds.  

 

SIP sides should negotiate who is making SIP session refreshing: MO or MT, during Call Setup:

  • INVITE ' Session-Expire header suggests UAC, UAS, or none
  • 200 OK'  Session-Expire header contains who is actually is the refresher: UAC or UAS.

Originator Mode - Select NONE, UAC or UAS.

Terminator Mode - Select NONE, UAC or UAS.

Tcl Parameter : ImsNodeRefresherOrigMode

Tcl Parameter : ImsNodeRefresherTermMode

Tcl Parameter : UeRefresherOrigMode

Tcl Parameter : UeRefresherTermMode

Ensure Constant Call Rate

If enabled, re-send the INVITE message through TCL events. The TCL events will be generated for a range of subscribers (calculated based on the desired call rate), and INVITEs will be sent for these subscribers. In the next iteration, a new range of subscribers will be generated and the INVITEs will be sent accordingly. This process of continuous and looped TCL triggers will be started only after the test case has gone through the expected initial registrations and INVITEs. Once the regular INVITE's have been triggered at the TCL level for all subscribers, only then will the constant call traffic be triggered at the TCL level.

Set Call Starts After to "When All Users Registered".

Fully controlled through events generated at TCL.

Not supported for Supplementary Services and SIP Endpoint Mode.

For this feature to work correctly: Call Hold Time + Pending Time = floor (Number of Originating Subscribers / Establishment Rate)

Tcl Parameter : EnsureConstantCallRateEn

Media Control Options

Available only when you select Enable RTP Traffic and selected at least one DMF type as Video on Gm > RTP tab. The Media Control Options allow you to configure the media that will be a part of the session and order of the media.

NOTE: Voice call starts at beginning of call and is released at end of call. The Call Order column/pane is automatically populated as per your selection of when Video/MSRP starts or released.

Video Starts At (s)

Indicates the length of time in seconds to wait before video starts (for example, if the time specified is 10seconds, then your video starts 10seconds after the Voice call starts)  

MSRP Starts At (s)

 

Available only when you select Enable MSRP.

This option does not require "Enable RTP Traffic " or RTP media (DMF type as Video) to be enabled.

Indicates the length of time in seconds to wait before MSRP starts (for example, if the time specified is 20seconds, then your video starts 30seconds after the Voice call starts)  

RTT Starts At (s)

 

Indicates the length of time in seconds to wait before RTT (Real Time Text) starts (for example, if the time specified is 10seconds, then your RTT starts 10seconds after the Voice call starts)  

Video Released

Select when you wish the video to be released. You may select to release video at end of call or mid-way and specify a time.

For example, if you select release video mid-way after 30seconds and you had selected to Start Video at 10seconds, the Call Order column displays 40-Video Release to indicate when the video will be released.

MSRP Released

Select when you wish MSRP to be released. You may select to release MSRP at end of call or mid-way and specify a time.

For example, if you select release MSRP mid-way after 40seconds and you had selected to Start MSRP at 200seconds, the Call Order column displays 60-MSRP Release to indicate when MSRP will be released.

This option does not require "Enable RTP Traffic " or RTP media (DMF type as Video) to be enabled.

RTT Released

Select when you wish RTT to be released. You may select to release RTT at end of call or mid-way and specify a time.

For example, if you select release RTT mid-way after 40seconds and you had selected to Start RTT at 200seconds, the Call Order column displays 60-RTT Release to indicate when RTT will be released.

NOTE: If you choose to release Video/MSRP/RTT at end of call, the Call Order column/pane doesn't populate any information.
SIP Stack Options

Select Enable Advanced Stack options to enable four additional parameters to alleviate running out of RAM (memory) when the number of transactions is too high to fit into memory. This can occur when running high scale tests.

Tcl Parameter : UeSipStackOptsEn

Transaction Multiplier

Available when Enable Advanced Stack Options is selected.

Range: 0.0 to 10.0

Default: 1.0

It is the multiplier value that will be applied to the default "Maximum Transactions" of the stack. "Maximum Transactions" is the maximum number of SIP transactions that the SIP Stack can handle simultaneously. This variable also impacts the memory allocation made by the stack.

Tcl Parameter : UeSipStackOptsTransMult

INVITE Linger Time (ms)

 

Available when Enable Advanced Stack Options is selected.

This is the time that a transaction lives after a call gets established.

Range: 0 to 4294967295 (Int32)

Default: 4001

After sending an ACK for an INVITE final response, when working with unreliable transport, a client cannot be sure the server has received the ACK message. The client should be able to retransmit the ACK upon receiving retransmissions of the final response for inviteLingerTimer milliseconds.

Tcl Parameter : UeSipStackOptsInviteLinger

GENERAL Linger Time (ms)

Available when Enable Advanced Stack Options is selected.

Similar to INVITE Linger time, however it is applicable to non INVITE SIP messages.

Range: 0 to 4294967295 (Int32)

Default: 4001

After a server sends a final response, when working with unreliable transport, it cannot be sure the client has received the response message. The server should be able to retransmit the response upon receiving retransmissions of the request for generalLingerTimer milliseconds.

Tcl Parameter : UeSipStackOptsGeneralLinger

To/From Tag Size (bytes)

 

Available when Enable Advanced Stack Options is selected.

Enter the size in bytes to modify the size of the To/From tag. The default is 128 however you may change it from 4 up to 128 bytes.

Range: 4 to 128

Default: 128

Tcl Parameter : UeSipStackOptsToFromTagSize

 

Select Use Fixed SIP Timer Values to enable additional timer values that the user can adjust. Available when Enable Advanced Stack options is enabled.

Tcl Parameter : UeSipStackOptsFixedSipTimerEn

T1 - RTT Estimate (ms)

Available when Enable Advanced Stack Options and Use Fixed SIP Timer Values are enabled.

Range: 0 to 4294967295  (Int32)

Default: 500

Enter a T1 (RTT Estimate) timer value in milliseconds.

Tcl Parameter : UeSipStackOptsSipTimerT1

T2 - Max Retransmit Interval (ms)

 

Available when Enable Advanced Stack Options and Use Fixed SIP Timer Values are enabled.

This is the maximum retransmit interval for non-INVITE requests and INVITE responses.

Range: 0 to 4294967295 (Int32)

Default: 4000

Tcl Parameter : UeSipStackOptsSipTimerT2

T4 - Max Duration in Network (ms)

Available when Enable Advanced Stack Options and Use Fixed SIP Timer Values are enabled.

This is the maximum duration a message will remain in the network.

Range: 0 to 4294967295 (Int32)

Default: 5000

Tcl Parameter : UeSipStackOptsSipTimerT4

D - Wait for Response Retrasmit (ms)

 

Available when Enable Advanced Stack Options and Use Fixed SIP Timer Values are enabled.

This is the Wait time for response retransmits.

Range: 0 to 4294967295 (Int32)

Default: 32000

Tcl Parameter : UeSipStackOptsSipTimerD

 

Select Override Timer Values for Registration to enable additional timer values that the user can adjust. Available when Enable Advanced Stack options is enabled.

Registration retransmission mechanism shown below , leverage this feature for UDP. The retransmission interval is calculated as:

T([n+1]th-interval) = MIN(2^n * T1, T2)

For example, 1st retransmission interval will be MIN(T1, T2), 2nd retransmission interval will be MIN(2*T1, T2), 3rd retransmission interval will be MIN(4*T1, T2), and so on.

Retransmission will be exhausted in the case of either

  • Number of retransmission reaches max number of retransmission, or
  • Total retransmission time, which is T(1st-interval) + T(2nd-interval) + T(3rd-interval) + ... exceeds max request transaction time
      

This retransmission flow is explained in the following diagram Figure 2-3.

Tcl Parameter : UeSipStackOptsOvReqTimerEn

T1 - RTT Estimate (ms)

Available when Enable Advanced Stack Options and Override Timer Values for Registration are enabled.

Range: 0 to 2147483647

Default: 500

Enter a T1 (RTT Estimate) timer value in milliseconds.

Tcl Parameter : UeSipStackOptsOvRegTimerT1

T2 - Max Retransmit Interval (ms)

 

Available when Enable Advanced Stack Options and Override Timer Values for Registration are enabled.

This is the maximum retransmit interval for REGISTER.

Range: 0 to 2147483647

Default: 4000

Tcl Parameter : UeSipStackOptsOvRegTimerT2

Transaction Timeout (ms)

Available when Enable Advanced Stack Options and Override Timer Values for Registration are enabled.

This is the Wait time for response retransmits.

Range: 0 to 2147483647

Default: 10000

Tcl Parameter : UeSipStackOptsRegTransTimeout

Max Request Retransmissions

 

Available when Enable Advanced Stack Options and Override Timer Values for Registration are enabled.

This is the maximum number of Request Retransmissions.

Range: 0 to 127

Default: 5

Tcl Parameter : UeSipStackOptsOvRegMaxRetrans

 

Optional Call Info

Available when Gm Interface is enabled. Also available in the CC tab on the CDMA Voice Nodal test case.

 

Terminating Subscribers

Select to indicate whether to Accept (default) or Ignore Incoming calls.

If Reject Incoming calls is selected,

Enter Cause Code: Range 300 to 699, Default = 480

Tcl Parameter : UeRejectCauseCode

Ignore Incoming Calls is used for instructing terminating subscribers to ignore and don’t respond to incoming calls.  For back-to-back testing, this option should be used when originating subscribers is configured with the new “Originating subscriber – Make then immediately terminate calls” option.

Tcl Parameter : UeIncomingCallsAction

Tcl Parameter : Ve911UeIncomingCallsAction

Originating Subscribers

Select to indicate whether to Make normal calls (default) or Make then immediately terminate calls.

When Make then immediately terminate calls is enabled:

  • This option is used for instructing originating subscribers to generate a call attempt (send INVITE message) but then immediately terminate them without having to wait for responses from receivers. 
  • After terminating a call attempt, originating subscribers shall wait for expiration of a configured pending time and repeat the action of generate and terminate new call attempt until a test is stopped. 
  • When this option is chosen, a configured call-hold time will not be used.
  • Also, because originating subscribers silently terminate their outgoing calls, they may receive responses from receivers of the terminated calls.  If that happens, originating subscribers shall ignore and will not process the responses.

When Make then cancel calls is enabled :

  • This option is used for instructing originating subscribers to generate a cancel call (send CANCEL message) and then immediately terminate without having to wait for responses from receivers. All received messages will be ignored.
  • If Unsuccessful No Answer (per RFC 3665, section 3.8) is selected and Terminating Subscriber send a 200 OK before the CANCEL message then the Originating Subscriber will send CANCEL and BYE messages.
  • If Unsuccessful No Answer (per RFC 3665, section 3.8) is selected and Terminating Subscriber send a 200 OK after the CANCEL message then the Originating Subscriber will send a CANCEL and wait for a 487 message before terminating.
  • New messages have been added to CANCEL flow, they are highlighted in red below. This gives the user the ability to change “ACK on INVITE 487” message using SIP editor. 

 

Tcl Parameter : UeOutgoingCallsAction

Tcl Parameter : Ve911UeOutgoingCallsAction

Tcl Parameter : UeUnsuccessNoAnswerEn

Tcl Parameter : Ve911UeUnsuccessNoAnswerEn

 

Available when Nc Interface is enabled in IMS Nodal test case. Also available in the CC tab on the CDMA Voice Nodal test case.

 

Terminating Subscribers

Select to indicate whether to Accept, Reject or Ignore Incoming calls.

If Accept Incoming calls is selected,

Select Accept procedure: Normal (default) or Auto-answer.

Tcl Parameter : UeAcceptProc

If  Accept procedure = Normal then

Select to Send call progress (CPG)

Tcl Parameter : UeSendCpgEn

If Send call progress (CPG) is enabled, Reliable CPG is available for input.

Tcl Parameter : UeReliableCpgEn

If Send call progress (CPG) is enabled, Number of CPGs and Number of CPGs are available for input.

Number of CPGs: Range 1 (default) to 10

Tcl Parameter : UeNumCpgs

Time between CPGs (ms): Range 0 to 4294967295, default = 200

Tcl Parameter : UeTimeBetweenCpgs

Tcl Parameter : UeIncomingCallsAction

If Reject Incoming calls is selected,

Enter Cause Code: Range 300 to 699, Default = 480

Tcl Parameter : UeRejectCauseCode

If Ignore Incoming calls is selected,

Select Silence or Send Address-Complete

Enter Cause Code: Range 300 to 699, Default = 480

Tcl Parameter : UeIgnoreCauseCode

Tcl Parameter : UeIgnoreCallsAction

Originating Subscribers

Select to indicate whether to Make normal calls (default) or Make then cancel calls.

Tcl Parameter : UeOutgoingCallsAction

Emergency Info

Available when Enable Emergency is enabled on the VoLTE Tab from AMF Nodal Test Configuration or MME Nodal Test Configuration. Enter Emergency Info for SIP 300 Multiple Choices message for E911 Calls.

Destination Realm

Enter the Destination Realm for the Subsequent INVITE.

Default: 911.spirent.com

Tcl Parameter : DestRealm

ESRK to Destination IP Mapping

Enter ESRK (Emergency Service Routing Key). A 10-digit number used for the purpose of routing an E911 call to the appropriate Public Safety Answering Point (PSAP) when that call is originating from wireless equipment. The Emergency Services Routing Digit (ESRD) identifies the cell site and sector of the call origination in a wireless call scenario. The Emergency Services Routing Key (ESRK) uniquely identifies the call in a given cell site/sector and correlates data that is provided to a PSAP by different paths, such as the voice path and the Automatic Location Identification (ALI) data path. Both the ESRD and ESRK define a route to the proper PSAP.

ESRK value returned in 300 Multiple Choice message to Destination IP.

Enter an integer.

Enter Destination IP Address. Enter a valid IPv4 or IPv6 address.

Enter up to 10 ESRK to Destination IP mappings.

Tcl Parameter : NumEsrkDestIpEntries

Tcl Parameter : EsrkDestIpMap1

ESRK to Market IP Mapping

Enter ESRK (Emergency Service Routing Key). A 10-digit number used for the purpose of routing an E911 call to the appropriate Public Safety Answering Point (PSAP) when that call is originating from wireless equipment. The Emergency Services Routing Digit (ESRD) identifies the cell site and sector of the call origination in a wireless call scenario. The Emergency Services Routing Key (ESRK) uniquely identifies the call in a given cell site/sector and correlates data that is provided to a PSAP by different paths, such as the voice path and the Automatic Location Identification (ALI) data path. Both the ESRD and ESRK define a route to the proper PSAP.

ESRK value returned in 300 Multiple Choice message to Market Id.

Enter an integer.

Enter Market ID Mapping.

Enter a 4 digit Market ID.

Enter up to 10 ESRK to Market ID mappings.

Tcl Parameter : NumEsrkMktIdEntries

Tcl Parameter : EsrkMktIdMap1

Emergency Header Options

Select to enable Emergency Header Options. Available in PSAP Node test case in SIP VoIP and in MME Nodal test case.

The PSAP Node test case will attach the same custom header in the 180 Ringing/200 OK message. The MME Nodal will abort the call if the Custom Header is not found in the 180Ringing/200 OK if Only Accept Calls with Custom Header is enabled.

Select Add Custom Header to SIP Message.

Select Only Accept Calls with Custom Header.

Enter Header Name and Header Value. Up to 64 Characters.

Tcl Parameter : UeEmergHdrCustomHdrEn

Tcl Parameter : UeEmergHdrFilterEn

Tcl Parameter : UeEmergHdrName

Tcl Parameter : UeEmergHdrValue

Use tel-URI for SIP Subscriber Use tel-URI for SIP Endpoint

Select to indicate support for MSISDN based Public Identities in both Tel-URI (e.g., +972-3-7212345) and SIP-URI ([email protected]) forms:

Tcl Parameter : SipTelUriSubscriberEn

Tcl Parameter : SipTelUriEndpointEn

SIP Subscriber URI Scheme

SIP Endpoint URI Scheme

Available when IMS Node is Endpoint. Select to indicate support for MSISDN based Public Identities in both Tel-URI (e.g., +972-3-7212345) and SIP-URI ([email protected]) forms:

Options: SIP-URI, tel-URI or SIPS-URI (only when GM TLS or Mm TLS is installed)

Tcl Parameter: SipSubscriberUriScheme

Tcl Parameter: SipEndpointUriScheme

Apply Test Data File to UE Parameters

Select to apply a Test Data file (TDF) of unique OPc values per UE. Available for all interfaces with the exception of Ml in IMS Nodal test case.

Select to apply a Test Data file (TDF) for "Single TC Support" - This flag is used to set the num of RV sockets to license numbers. The default value of num of RV sockets is still set to number of subscribers. Available for All Nodal test cases. Example file : Single TC support.csv

Additional parameters are available for some test cases:

  • IP Application Node - OPc, P-CSCF IP Address, P-CSCF Port
  • MME Nodal / SGW Nodal -  OPc, P-CSCF IP Address, P-CSCF Port, IMS APN, Multimedia Priority Service, MPS Mandatory, Add Via IP to Call-ID (see below), Enable MRFP IP Reporting
  • AMF Nodal , SMF Nodal - P-CSCF IP Address, P-CSCF Port - See sample file : AMFVo5GP-CSCF.csv

Parameter "Add Via IP to Call-ID Header" in MME Nodal is per spec reference RFC 3261 section 20.8 "Call-ID".

Enter the subscriber Number and True (1) or False (0) to set the "Add Via IP to Call-ID Header" to use the local IP (used to set Contact header) to create the new Call Id. The Call-ID header is automatically generated by RV stack unless you set the Call ID manually via IP Address in this TDF file parameter. A rand() function and the local IP (used to set Contact header) is used to create the new Call Id. Supported in : SIP Registration, SIP Call Setup, SIP Subscription, SIP Options and the supporting SIP Actions.

See example : 

Parameter "Enable MRFP IP Reporting" is available in MME Nodal. As Transcoder and Tones MRFP IPs can be present in different SIP messages. It is used to to peg Connection information from SDP and Analytics to cross-check with reference data to identify the MRFP IP.  Enter the subscriber Number and True (1) or False (0) to set the "Enable MRFP IP Reporting". 

MRFP_IP Processing : 

  • For MO Call (Landslide Initiated) : Read the c line in SDP of 183 or 200 OK response, the IP Address inside the c line should be reported as the MRFP IP.
  • For MO Call (Landslide Initiated) : Read the c line in SDP of incoming INVITE request, the IP Address inside the c line should be reported as the MRFP IP.
  • For Supplementary services "Simple Call" between subscriber A & B using supplementary service. Both subscribers are emulated by Landslide: The MRFP IP will be reported for each subscriber .This MRFP IP string will be reported on successful script completion.
  • For Supplementary services "3 Party Call" : SIP call between subscriber A, B, C and D, where subscriber D is conference server, all subscribers are emulated by Landslide. MRFP IP will be reported for each subscriber, MRFP IP(s) will be concatenated if a subscriber creates more than 1 call leg. 

MRFP IP string will be reported on successful script completion.

Sample TDF file that contains Enable MRFP IP Reporting :Enable MRFP IP reporting.csv

Added parameter "Enable Update with Send Receive" is available in MME Nodal. When enabled, Landslide will send the SIP UPDATE message with a=sendrecv

Sample TDF file that contains Enable Update with Send Receive :Update_Send_Recv.csv

Tcl Parameter : SipUeCfgFileEn

IMS Nodal

Define IMS Nodal parameters for UE call registration during VoLTE testing.

ATCF Built-in    P-CSCF Built-In

ATCF Built-In

Enable ATCF

STN-SR

Management URI

Path URI

 

Select to enable ATCF. Available when Mw or ISC Interface is selected on IMS Nodal test case.  If ISC Interface and Enable RTP Traffic are enabled, ATCF Built-in is disabled.

Added ATCF and P-CSCF related information in the REGISTER and Call related message towards the SCC-AS (IMS Node Mode = B2BUA). This is a licensed feature.

  • STN-SR: Enter the Session Transfer number. Default = 1-237-888-9999.
  • Management URI: Enter ATCF URI. Default = atfc.spirent.net.
  • Path URI: Enter ATCF Path URI. Default = [email protected]. (available when ISC Interface is selected on IMS Nodal test case)

Tcl Parameter: PcscfAtcfEn

Tcl Parameter: AtcfEn

Tcl Parameter: AtcfStnSr

Tcl Parameter: AtcfMgmtUri

Tcl Parameter: AtcfPathUri

MSC Built-In

Available when Test Activity = Inter Technology Mobility, Handoff Protocol = E-SRVCC (Single Radio Voice Call Continuity) and PS Domain = ISC on IMS Nodal test case.

Enter Management URI.

Default: msc.spirent.net

Tcl Parameter: MscMgmtUri

AS Information

Available when Test Activity = Inter Technology Mobility, Handoff Protocol = E-SRVCC (Single Radio Voice Call Continuity) and PS Domain = ISC on IMS Nodal test case.

Enter SCC AS Number (Enter valid Phone number).

Default: +1-237-555-4444

Tcl Parameter: SccAsNumber

P-CSCF Built-In  (When ISC Interface)

Host

Available when Enable 3rd Party Registration is selected and when ISC Interface is selected on IMS Nodal test case. Added ATCF and P-CSCF related information in the REGISTER and Call related message towards the SCC-AS (IMS Node Mode = B2BUA). This is a licensed feature.

  • Host: Enter the P-CSCF Host Name. Default = pcscf.spirent.com

Tcl Parameter: IscPcscfHost

 

IMS Node

Define IMS Node parameters for UE call registration during VoLTE testing.

 

IMS Node Type Select to Indicate whether the IMS Node is Local or Remote.
NOTE: The Application Node test case supports only Remote IMS Node Type.

Tcl Parameter: ImsNodeType

Tcl Parameter: Ve911ImsNodeType

P-CSCF Mode

Indicate whether IMS Node emulates SIP Endpoints or SIP Proxy.

  • SIP Endpoints: SIP Endpoints to emulates SIP Registrar and SIP Endpoints used to create or receive SIP messages.
  • Proxy: Proxy to emulates SIP Proxy to route requests as appropriate and applies when you select Enable Mobile-To-Mobile on the UE pane.

P-CSCF IP Address

P-CSCF Port

Available when IMS Node Type is Remote and requires an IP Address to identify the IMS Node and P-CSCF specific signalling port for entire IMS Node. P-CSCF Port: Default: 5060 (Default = 5061 if TLS is enabled)  

Tcl Parameter: ImsNodeIpAddr

Tcl Parameter: ImsNodeIpPort

Tcl Parameter: Ve911ImsNodeIpAddr

Tcl Parameter: Ve911ImsNodeIpPort

P-CSCF Address Option

Available when IMS Node Type is Remote and indicates P-CSCF IP address used to send the Gm layer traffic.

Select an option to use PCO received IP address for P-CSCF registration.

Options:

  • Use Provisioned Address (0)(default)
  • Use IPV4 Address from PCO (1)
  • Use IPV6 Address from PCO (2)

Tcl Parameter: ImsNodePcscfAddrType

Tcl Parameter: Ve911ImsNodePcscfAddrType

Use IPV4 Address from PCO

Indicates that the IPV4 Address returned in the PCO IE from the PGW Node is used as the destination address for the P-CSCF Node. S2a/S2b/S5/S8 Protocol Configuration Options-  P-CSCF IPv4 Address

Use IPV6 Address from PCO

Indicates that the IPV6 Address returned in the PCO IE from the PGW Node is used as the destination address for the P-CSCF Node. S2a/S2b/S5/S8 Protocol Configuration Options-  P-CSCF IPv6 Address

Provisioned Address Statically provisioned P-CSCF is used to send the Gm layer traffic.

 

I-CSCF IP Address

I-CSCF Port

Available when IMS Node Type is Remote and requires an IP Address to identify the IMS Node and I-CSCF specific signalling port for entire IMS Node.

I-CSCF Port: Default: 5060

Tcl Parameter: IcscfNodeIpAddr

Tcl Parameter: IcscfNodeIpPort

Functionality Pattern

Displays only when IMS Node Type is Local.

The functionality pattern of IMS Node depends on your selection on the UE pane. Available when P-CSCF Mode is SIP Endpoints.

On UE Pane On IMS Node Pane
OTOT TOTO
TOTO OTOT
All Originate All Terminate
All Terminate All Originate

 

Starting Audio RTP Port

Available when P-CSCF Mode is SIP Endpoints. The port number for the first port of the RTP Audio session.

Range: 1 - 65534

Default: 6000

Tcl Parameter: ImsNodeStartingRtpAudioPort
Increment Audio Port per Subscriber

Select to increment Audio Port numbers assigned to different UEs across all subscribers. Endpoint Node.

Examples below without and with Increment Audio Port per Subscriber enabled:

1 Subscriber per UE with 1 Audio Media :

UE Idx

Subscriber Idx

Audio Media Port

Audio Media RTCP Port

Audio Media Port

with Increment Audio Port per Subscriber enabled

Audio Media RTCP Port

with Increment Audio Port per Subscriber enabled

0

0

6000

6001

6000

6001

1

1

6004

6005

6002

6003

3

3

6000

6001

6004

6005

4

4

6004

6005

6006

6007

 

2 Subscribers per UE with 1 Audio Media :

UE Idx

Subscriber Idx

Audio Media Port

Audio Media RTCP Port

Audio Media Port

with Increment Audio Port per Subscriber enabled

Audio Media RTCP Port

with Increment Audio Port per Subscriber enabled

0

0

6000

6001

6000

6001

0

1

6004

6005

6002

6003

1

0

6000

6001

6004

6005

1

1

6004

6005

6006

6007

2

0

6000

6001

6008

6009

2

1

6004

6005

6010

6011

3

0

6000

6001

6012

6013

 

2 Subscribers per UE with 3 Audio Media

UE Idx

Subscriber Idx

Audio Media1 Port

Audio Media1 RTCP Port

Audio Media 1 Port - with Increment Audio Port per Subscriber enabled

Audio Media RTCP Port - with Increment Audio Port per Subscriber enabled

Audio Media2 Port

Audio Media2 RTCP Port

Audio Media2 Port -  with Increment Audio Port per Subscriber enabled

Audio Media 2RTCP Port -  with Increment Audio Port per Subscriber enabled

Audio Media3 Port

Audio Media3 RTCP Port

Audio Media 3Port -  with Increment Audio Port per Subscriber enabled

Audio Media3 RTCP Port -  with Increment Audio Port per Subscriber enabled

0

0

6000

6001

6000

6001

6002

6003

6002

6003

6004

6005

6004

6005

0

1

6004

6005

6006

6007

6006

6007

6008

6009

6008

6009

6010

6011

1

0

6000

6001

6012

6013

6002

6003

6014

6015

6004

6005

6016

6017

1

1

6004

6005

6018

6019

6006

6007

6020

6021

6008

6009

6022

6023

2

0

6000

6001

6024

6025

6002

6019

6026

6027

6004

6005

6028

6029

2

1

6004

6005

6030

6031

6006

6023

6032

6033

6008

6009

6034

6035

3

0

6000

6001

6036

6037

6002

6027

6038

6039

6004

6005

6040

6041

 

 

Tcl Parameter: ImsNodeIncrStartingRtpAudioPort

Starting Video RTP Port

Available when P-CSCF Mode is SIP Endpoints. The port number for the first port of the RTP Video session.

Range: 1 - 65534

Default: 7000

Tcl Parameter: ImsNodeStartingRtpVideoPort
Starting MSRP Port

The first port of the MSRP session. The starting MSRP Port number should be different from the RTP Audio/Video port numbers.  

Range: 1 - 65534

Default: 2855

   Tcl Parameter: ImsNodeStartingMsrpPort
Starting RTT Port

The starting RTT (Real Time Text) Port number should be different from the RTP Audio/Video/MSRP port numbers.  

Range: 1 - 65534

Default: 8000

    Tcl Parameter: ImsNodeStartingRttPort
IP-SM-GW PSI

When enabled, IP-SW-GW PSI (IP Short Message Gateway) is between the mobile subscribers and SMS Service Centre PSI to provide transport layer inter-working for submission and delivery of short messages, lawful interceptions, etc.   Range: Up to 255 characters, (if blank = disabled, req-url and to-uri will fallback to SIP Phonebook)    

Tcl Parameter: IpSmGwPsi

Service Centre PSI

When enabled the SMS Service Centre PSI provides transport layer inter-working for submission and delivery of short messages, lawful interceptions, etc.   Range: Up to 255 characters, (if blank = disabled, req-url and to-uri will fallback to SIP Phonebook)     Default: SIP-URI Scheme, prefix with "+" for tel-URI (+1234)  

Tcl Parameter: ServiceCentrePsi

MCPTT Server PSI

Available when IMS Node = Remote and Supplementary is enabled. Part of the Mission Critical Push-To-Talk (MCPTT) services. Select to have a participating MCPTT Server PSI included in the SIP Messages. Range: Up to 255 characters       Default: participating.func.ims-operator.net   

Tcl Parameter: McpttSrvPsi

Enable Rx Select Rx Interface to define the Rx interface between the PCRF and the IMS Node. See also AF Node.  The Rx Interface is available only when you your system is licensed for PCRF function.   Select to include Rx Subscriber ID parameters to be included for PCRF testing in IMS Node test case.   Get Identities from PCRF - Available when Enable Emergency is checked and Enable Rx. When checked, "Include MSISDN" and "Include IMSI" will be grayed out as these values will be obtained dynamically from PCRF. Per 3GPP 29.212 and 29.214.
NOTE: AAR will be sent from IMS over Rx ONLY when INVITE message is received.
  Tcl Parameter: ImsNodeIdsFromPcrfEn
 
  • Include MSISDN : The MSISDN directory number for the mobile subscriber ID included as part of the PCC-R3-P/PCRF Subscriber ID. This value is incremented for each mobile subscriber.

Tcl Parameter: PCRFClnCcMsisdnEn

Tcl Parameter: PCRFClnCcMsisdn

  • Include IMSI (The International Mobile Subscriber Identifier) included as part of the PCC-R3-P/PCRF Subscriber ID.

Tcl Parameter: PCRFClnCcImsiEn

Tcl Parameter: PCRFClnCcImsi

  • Include Public ID: Select to Include SIP Public ID.

Tcl Parameter:  PCRFClnCcPublicIdEn

  • Include Private ID: Select to Include SIP Private ID.

Tcl Parameter:  PCRFClnCcPrivateIdEn

  • Enable NetLoc Mode.

Tcl Parameter:  ImsNodeNetLocEn

ANI Report Timeout (s)

Range: 0 - 60

Default: 30

Tcl Parameter: ImsNodeAniReportTimeout

NOTE: The following Call patters are viable only when Functionality Pattern on the UE pane of the VoLTE tab is: OTOT... ; TOTO... ; or All Terminate. These parameters are not available when functionality pater is All Originate.
Call Hold Time (s)

Available when P-CSCF Mode is SIP Endpoints. Indicates the length of call.

Option: 1 - 65535

Default: 20 (s)

Tcl Parameter: ImsNodeCallLength

Call Pending Time (s)

Available when P-CSCF Mode is SIP Endpoints. Indicates the idle time.

Option: 1 - 65535

Default: 10

Tcl Parameter: ImsNodeCallPending

Call Establishment Rate (calls/s)

Available when P-CSCF Mode is SIP Endpoints. Indicates the rate at which the UE attempts to establish calls with the SIP Endpoint.

Option: 0.0010 - 3000.00

Default: 1000.0

Tcl Parameter: ImsNodeCallEstabRate

Call Start Delay (s)

Available when P-CSCF Mode is SIP Endpoints. Indicates the length of time to wait before attempting to establish calls with the SIP Endpoints.

Option: 1 - 65535

Default: 10

Tcl Parameter: ImsNodeCallDelay

Call Release Rate (calls/s)

Available when P-CSCF Mode is SIP Endpoints.  Indicates the rate at which the UE attempts to release calls established with the SIP Endpoint.

Option: 0.0010 - 3000.00

Default: 1.0

Tcl Parameter: ImsNodeCallReleaseRate

Subscription

Available on IMS Node when Enable Subscription and Interface =  Mw.

  • Enable Subscription - When checked, IMS-Node will attempt to process received subscription; otherwise, it will reject subscription request with a 501 response-code  for indicating not-implemented function
  • Expires (s) - used for entering optional subscription expiration time. When enabled, IMS-Node will take the proposed expired time value in a received subscribe request as the expiration time of a subscription; otherwise, when checked and an expires value is entered, IMS-Node will use a configured expires time as the expiration of the subscription. Range : 0 to 4294967295. Default : 600000
  • Allow Events :  Specify a list of supported/allowed events.  Currently, Registration event as specified in RFC 3668 is supported.  When IMS-Node receives subscribe request for an event included in this allowed list (i.e. reg), it will handle the request and generate notification as specified in the listed specification. (i.e. send notification when there is a change in registration state, aor, contact, etc.).   Tcl Parameter: SipSubEventRegEn
  • Unknown Events : IMS-Node considers a received event is unknown/unsupported if the event value in a request is not in the list of allowed event and will respond to the request based on the following choice
    • Reject : default option. If the reject option is selected, IMS-Node will reject a request with a configured response-code. Enter Response Code : Range 200 to 999. A default response-code is 489 (bad event). Tcl Parameter: SipSubUnkEventAction , Tcl Parameter: SipSubUnkEventRspCode
    • Accept - if the accept option is selected, IMS-Node will accept a request and respond with a 2xx response-code.  NOTE: this option is added for development/interop testing purpose; it should be used with extra care because each subscribed event has its own specification/syntax/procedure.  For example:  dialogue (RFC 4235),  present (RFC 3856,5263), conference(RFC 4575), etc. This option should be used with manual notification.
  • Notification - specify how IMS-Node generate notification for subscribed events.
    • Auto - default option. When selected, IMS-Node will generate notification based on change of state/status of resource such as registration state etc. Tcl Parameter: SipSubUnkEventNtfy
    • Manual - When selected, IMS-Node will generate notification message based on a specified interval and count regardless whether there is any change in state/status of subscribed event. This option was added for development/interop testing puropse and it should be used with extra care. For unknown/unsupported subscribed event, IMS-NODE will generate a notify request with empty message-body; users should use the SIP message editor to modify and add correct content to notify requests.
      • Notification Interval (s) - Enter the time in seconds between generated notification. Range : 1 to 65535. Default : 5. Tcl Parameter: SipSubUnkEventNtfyPeriod
      • Notification Count - Enter the number of generated notifications. Range : 0 to 255. Default : 1. Zero (0) is valid and used for not generating any notification. Tcl Parameter: SipSubUnkEventNtfyCount
Application Servers

Use built-in Application servers - Available when P-CSCF Mode is Proxy. (Service Centralization and Continuity is available for both SIP Endpoint and Proxy for Mw and ISC interfaces only)

Used to indicate whether the test is to use "built-in" services configured on the L/S IMS node or to use external application servers from a SUT.

NOTE: Currently, the use of external Application Servers is not supported

   Communications Diversion - The communications Diversion check box must be checked with the CFU (call forwarding) built-in. When enabled the App Servers Tab is presented for provisioning. Communications Barring - The communications Barring check box when enabled,  the App Servers Tab is presented for provisioning. Service Centralization and Continuity - The Service Centralization and Continuity check box is enabled when Interface = Mw or ISC. When enabled,  the App Servers Tab is presented for provisioning. Support for call flow between ATCF and SCC AS. Communications Waiting - The communications Waiting check box when enabled, the App Servers Tab is presented for provisioning. Used to provision Call Waiting. MCPTT - The MCPTT check box when enabled (P-CSCF Mode = Proxy, Enable Supplementary), the App Servers Tab is presented for provisioning. Part of the Mission Critical Push-To-Talk (MCPTT) services.  

Tcl Parameter: AppServerEn

Tcl Parameter: AppCommDiversionEn

Tcl Parameter: AppCommBarringEn

Tcl Parameter: AppSccEn

Tcl Parameter: AppCommWaitingEn

Tcl Parameter: AppMcpttEn

Enable Authentication

Select for an IMS Node to authenticate communication between UE and IMS Node (Authentication Server).

  • Type: Select authentication type from the drop down menu. Options: IMS AKA or HTTP Digest
  • AKA Version: Select to indicate he AKA version used for authentication.
  • Select an Authentication Algorithm. Additional fields become available for input.
  • Options : Milenage ( Defined in 3GPP TS 35.205) , Test Algorithm ( Defined in 3GPP TS 34.108) , TUAK ( Defined in 3GPP TS 35.231). TUAK is a 3GPP defined algorithm and key generation set of functions (f1, f1*, f2, f2, f4, f5, and f5*). 

Tcl Parameter: ImsAuthAlgorithm

  • RES Length (bytes) : Per 3GPP (33.102) specified RES Length of 4-16 octets. Range: 4 to 16, Default : 8. Available when Algorithm = Milenage or Test Algorithm.
  • AMF : Enter up to a 2 byte hex string for the AMF. Range: 2-Byte hex string, Default : 0x8000. Available when Algorithm = Milenage or Test Algorithm. Tcl parameter: ImsAuthAmf
  • Operator Variant: The 128-bit, operator-specific MILENAGE constant (OP) provisioned for the network. Select OPc to add authentication with OPc value. Available when Algorithm = Milenage or Test Algorithm. 

    Encrypt - Click on Encrypt to encrypt the Operator Variant / OPc. Any user type can enter the value in plain text, and then click an “Encrypt” button which will encrypt the value and switch the TC-GUI to use new parameter variable name with _Enc Suffix. (encrypted-mode). The fields in the GUI will become like passwords with just "****************" in them and they will be not be edit able. When the Operator Variant / OPc is encrypted , the TDF-CSV editor will automatically encrypt the value when it is saved in the cell "Operator Variant Encrypted" or "Operator-c Variant Encrypted". Additonal details in Apply Test Data File to NAS Protocol.

    Decrypt - Click on Decrypt to decrypt the Operator Variant / OPc.

Range: Up to 32 hex characters, excluding "0x."

Default: 0x63BFA50EE6523365FF14C1F45F88737D

 

The following fields become available when Algorithm = TUAK. For information about how the fields are used in the TUAK algorithm the user should refer to the 3GPP TS 35.231 specification.

Key This is the secret key and is analogous to the Milenage Secret Key field. Enter either a String value or a Hex value beginning with 0x.

Tcl Parameter: ImsTuakKey

TOP The Edit Top data input box associated with TOP allows the user to input a 32 byte Hex string value used for the operator variant. Tcl Parameter: ImsTuakOpType
Key Length (bytes) Select the maximum length supported for the secret key. Support for 16 or 32 bytes. Tcl Parameter: ImsTuakKeyLen
RES Length (bytes) Select the maximum length supported for the RES value. Support of 4 or 8 bytes only. Tcl Parameter: ImsTuakResLen
Keccak_f Iterations Enter the number of times the Keccak permutation is performed. Range : 1 to 255 Default : 1 Tcl Parameter: ImsTuakIterations
MAC Length (bytes) Select the maximum length supported for the MAC fields (MAC-A and MAC-S). Support 8 bytes. Tcl Parameter: ImsTuakMacLen
AMF

Enter up to a 2 byte hex string for the AMF. Range: 2-Byte hex string, Default : 0x8000.

Tcl Parameter: ImsTuakAmf

CK Length (bytes) Select the maximum length supported for the confidentiality key. Support 16 bytes only. Tcl Parameter: ImsTuakCkLen
IK Length (bytes) Select the maximum length supported for the integrity key. Support 16 bytes only. Tcl Parameter: ImsTuakIkLen

Tcl Parameter:

AuthenticationEn

AkaVersion

AuthenticationType

ImsAuthResLen

ImsOpType

ImsOpVar

ImsOpVar_Enc

 

Enable AUTH of Non REGISTER Requests: Available only when you select Authentication and Mode = Sip Endpoint or Proxy. Select to support Authentication of SIP UE in the case when IMS Core challenges INVITE request. When enabled, Landslide will respond with SIP INVITE again with AUTH Parameters.

407 response on INVITE when Enable AUTH is enabled.

Tcl parameter: AuthOfNonRegisterReqEn

 

Enable IPSec: Available only when you select Authentication. Select to indicate that IMS Node supports IMS-AKA with and without IPSec, which is configurable on a per UE/SIP client basis.

   

Tcl parameter: ImsIpSecEn

  • ESP Data Mode: Available when you select Enable IPSec. Select the Data Mode to be transmitted between the UE and the IMS Node.

Options: Transport, Tunnel

Default: Transport

Tcl parameter: ImsEspDataMode

  • Encryption Algorithm: Available when you select Enable IPSec. Select the method of cryptographic encryption of the data to be transmitted between the UE and the IMS Node.

Options: NULL, DES_EDE3_CBC, AES_CBC

Default: NULL

Tcl parameter: ImsEncryptionAlgorithm

  • Security Algorithm: Available when you select Enable IPSec. Select the Security Algorithm - Ensures packet message integrity between two parties is intact.

Options: HMAC-MD5-96 (Default) , HMAC-SHA-1-96

Default: HMAC-MD5-96

Tcl parameter: ImsSecurityAlgorithm

  • Number of Tunnels per Subscriber: Available when you select Enable IPSec. Select the number of IPSec tunnels per subscriber.

Options: 2, 3 or 4

Default: 4

Tcl parameter : ImsTunnelsPerSub

 

Use Test Algorithm for Authentication - available only when you select Enable Authentication and Authentication Type = "IMS AKA". Select to use test algorithm for Authentication.

Tcl parameter : ImsAuthTestAlgoEn

SIP Stack Options

Select Enable Advanced Stack options to enable four additional parameters to alleviate running out of RAM (memory) when the number of transactions is too high to fit into memory. This can occur when running high scale tests.

Tcl Parameter: ImsNodeSipStackOptsEn

 

Transaction Multiplier

Available when Enable Advanced Stack Options is selected.

Range: 0.0 to 10.0

Default: 1.0

It is the multiplier value that will be applied to the default "Maximum Transactions" of the stack. "Maximum Transactions" is the maximum number of SIP transactions that the SIP Stack can handle simultaneously. This variable also impacts the memory allocation made by the stack.

Tcl Parameter: ImsNodeSipStackOptsTransMult

INVITE Linger Time (ms)

Available when Enable Advanced Stack Options is selected.

Range: 0 to 4294967295 (Int32)

Default: 4001

After sending an ACK for an INVITE final response, when working with unreliable transport, a client cannot be sure the server has received the ACK message. The client should be able to retransmit the ACK upon receiving retransmissions of the final response for inviteLingerTimer milliseconds.

Tcl Parameter: ImsNodeSipStackOptsInviteLinger

GENERAL Linger Time (ms)

Available when Enable Advanced Stack Options is selected.

Range: 0 to 4294967295 (Int32)

Default: 4001

After a server sends a final response, when working with unreliable transport, it cannot be sure the client has received the response message. The server should be able to retransmit the response upon receiving retransmissions of the request for generalLingerTimer milliseconds.

Tcl Parameter: ImsNodeSipStackOptsGeneralLinger

To/From Tag Size

(bytes)

Available when Enable Advanced Stack Options is selected.

Enter the size in bytes to modify the size of the To/From tag. The default is 128 however you may change it from 4 up to 128 bytes.

Range: 4 to 128

Default: 128

Tcl Parameter : ImsNodeSipStackOptsToFromTagSize

 

Select Use Fixed SIP Timer Values to enable additional timer values that the user can adjust. Available when Enable Advanced Stack options is enabled.

Tcl Parameter : ImsNodeSipStackOptsFixedSipTimerEn

T1 - RTT Estimate (ms)

Available when Enable Advanced Stack Options and Use Fixed SIP Timer Values are enabled.

Range: 0 to 4294967295  (Int32)

Default: 500

Enter a T1 (RTT Estimate) timer value in milliseconds.

Tcl Parameter : ImsNodeSipStackOptsSipTimerT1

T2 - Max Retransmit Interval (ms)

 

Available when Enable Advanced Stack Options and Use Fixed SIP Timer Values are enabled.

This is the maximum retransmit interval for non-INVITE requests and INVITE responses.

Range: 0 to 4294967295 (Int32)

Default: 4000

Tcl Parameter : ImsNodeSipStackOptsSipTimerT2

T4 - Max Duration in Network (ms)

Available when Enable Advanced Stack Options and Use Fixed SIP Timer Values are enabled.

This is the maximum duration a message will remain in the network.

Range: 0 to 4294967295 (Int32)

Default: 5000

Tcl Parameter : ImsNodeSipStackOptsSipTimerT4

D - Wait for Response Retransmit (ms)

 

Available when Enable Advanced Stack Options and Use Fixed SIP Timer Values are enabled.

This is the Wait time for response retransmits.

Range: 0 to 4294967295 (Int32)

Default: 32000

Tcl Parameter : ImsNodeSipStackOptsSipTimerD

Multimedia Priority Service (MPS)

Select Enable MPS (Multimedia Priority Service) to enable three additional parameters and a Priority Count/Resource table.

  • When the “Enable MPS ” box is unchecked, Landslide P-CSCF shall ignore Resource-Priority headers in received requests and process the requests as if Resource-Priority headers are not present.
  • When the “Enable MPS” box is checked, Landslide P-CSCF shall compare content of Resource-Priority headers against subscriber MPS configuration and determine whether it should reject requests, process requests without priority handling or process request with priority handling.

 Tcl Parameter: ImsNodeMpsEn

MPS Priority

Available when Enable MPS is selected. Configure a MPS Priority value of all subscribers. MPS Priority is a 32-bit unsigned value which is part of a user-profile in HSS/SPR for indicating whether a subscriber is subscribed to MPS; and, this value will be used in the permitting process. (See 3GPP TS 29.272 for a complete definition of MPS Priority). 

Range: 0 to 4294967295 (Int32)

Default: 2

Tcl Parameter: ImsNodeMpsPriority

MPS Identifier

Available when Enable MPS is selected. The MPS-Identifier AVP contains the national variant for MPS service name indicating an MPS session.

Tcl Parameter: ImsNodeMpsId

Highest Permitted Reservation Priority

Available when Enable MPS is selected.

Configure the highest reservation priority value of subscriber.  Landslide P-CSCF will use this configuration value for comparing with a requested value in the permitting process. Valid reservation priority values are in range from the lowest priority 0 to the highest priority 15;

Reservation Priority: Reservation-priority is a number between 0-15 for indicating lowest to highest reservation priority. Reservation-priority is used between P-CSCF and PCRF for indicating reservation priority of a call.  When a priority call is permitted, P-CSCF chooses a reservation-priority for a requested resource-priority and sends to PCRF.  The decision of which resource will get which priority is local/operator dependent.

Default: 3

Tcl Parameter: ImsNodeResvPriorityHi

Priority Count

Priority Resource

Available when Enable MPS is selected.  A configuration table is available for allowing users to specify resource reservation priority values of resource-priority strings.

  • Valid reservation priority values are in range from the lowest priority 0 to the highest priority 15
  • Resource priority is a string of characters used for indicating requested resource priority of a call (i.e. dsn.immediate).  Resource priority are used in SIP (Gm interface)

For example, users can specify a resource-priority string=’dsn.immediate’ has a reservation priority value of 3. Landslide P-CSCF uses reservation priority values in the below permitting process and it will send reservation priority values to PCRF when resource requests are permitted.

Tcl Parameter: ImsNodeNumMpsEntries

Tcl Parameter: ImsNodePriority_1

Tcl Parameter: ImsNodeResource_1

Apply Test Data File to IMS Node Parameters

Select to apply a Test Data file (TDF) of unique OPc values per UE. 

Note: A new Max Call Legs Per UE configuration parameter has been introduced in the TDF for IMS Node Parameters when running in B2BUA Mode.  By default the Call Legs per UE is set to the default value of 6. With the new TDF parameter, this parameter can be used to increase the number of call legs as required.

Additional parameters are available for some test cases:

  • MME Nodal / SGW Nodal -  OPc, Multimedia Priority Service, MPS Mandatory

Tcl Parameter : ImsNodeCfgFileEn

 

^ Back to Top