TCP/SCTP Tab
Click here to see this page in full context

Landslide Performance Test System – Release 24.3 September 2024

TCP/SCTP Tab

The TCP/SCTP tab is used to define the TCP and SCTP connection management settings for reliable transport over IP that are configured when either protocol is used in the bearer plane or the control plane.

 

Additional location list:

TCP/SCTP

SCTP

Heartbeat Timer

SCTP ACKs

NOTE:

  • When Iu-PS and Iu-CS are both enabled (In MME Nodal and MME Node ) when Handoff Protocol = UMTS (IuCS & IuPS over IP) the Tcl variables will begin with luCs for the lu-Cs interface. The Iu-PS interface will use the regular M3ua Tcl variables.
  • When Iu-PS and Iu-CS are both enabled (In HNB GW Nodal ) when 3G Macro RNC Emulation is enabled, Tcl variables will begin with luCs for the lu-Cs interface and IuPs for the Iu-PS interface.
  • The TCP/SCTP tab is a common tab used by multiple interfaces in multiple Test Cases. To find the TCL parameter, select the parameter and press F2 to display the Tcl Variable name for that parameter in a pop-up window. Hold down the left mouse key to maintain the focus. 

Related Measurements

Measurements collected for  the SCTP transport are reported on the SCTP report tabs.

SCTP Settings

Version (24.502)

Select the Version for 24.502. Available for selection in AMF Nodal and N3IWF Node test cases in the NWu interface only.

Select correct version such as 24.502 v15.2.0 to support the new length IE in all the NAS over TCP messages exchanged between N3WIF and UE.

Options: 15.0.0/Jun2018 (default) , 15.1.0/Sep2018, 15.2.0/Jan2019 , 15.2.0-Variant1/Jan2019 , 15.2.0-Variant2/Mar2019 , 15.4.0/Jul2019, 16.4.0/July2020

Tcl Parameter: NWuVersion

Source Port

The port used by the RNCs for SCTP associations.

Range: 0 — 65535

Default: 36412

Tcl Parameter: SctpSrcPort_1

 

Client Port

The Client port used for MME Load Testing. Available in MME Nodal when MMS Support is enabled. 

Range: 0 — 65535

Default: 30000

Tcl Parameter: MmsDataClientPort

 

Destination Port

The port used by the SGSN SUT for SCTP associations.

Note : In MME Node Network Devices, the "MSC Port" field associated with the "MSC Node" SUT is being removed. A Tcl upgrade has transferred the "MSC Port" value to the SGs|SCTP Destination Port.

Range: 0 — 65535

Default: 36412

Tcl Parameter: SctpDestPort_1

 

Window Size

The maximum number of bytes that can be sent to the SGSN without receiving an acknowledgement.

The number of payload bytes that can be sent without an ACK from the receiving end. When the window is full, the sender pauses until it receives an ACK and then resumes transmitting.

MME Nodal - Added support for the emulated eNodeB to stop sending packets after receiving an SCTP Window Size = 0.

When packets are received out of sequence, a queue will collect packets and they will be processed as the missing packets are received. The queue can buffer up to 30MB, which would allow 1,000 sessions to miss a packet and still queue the remaining packets in the window.

IMPORTANT: The window size must be larger than the payload bytes in a packet; otherwise, the packet will not be transmitted.

Range: 1000 — 65535

Default: 32768

Tcl Parameter: SctpWindowSize_1

Tcl Parameter: RadTcpWinSize
Window Scaling Factor

The Window Scaling Factor value communicates a Scale Factor to be applied to TCP/SCTP received window.

Range: 0 and 14

Default: 0

NOTE: Window Scaling is only needed when TCP/SCTP Window Size is < 65535 bytes (See RFC 1323). Scaling up to larger window sizes is part of TCP/SCTP tuning. Since the Window Size cannot be expanded, a scaling factor is used, which provides an option to increase the maximum window size from 65,535 bytes to 1 Gb.

The Window Scale Option has 2 purposes:

  • Indicate that the TCP/SCTP is prepared to perform send and receive window scaling
  • Communicate a Scale Factor to be applied to its received window.
TCP Push

Select to include the Push flag in the TCP Header. Available in DRA Nodal/Node and IMS Node (when Rx Interface is enabled) test cases.

HssClnTcpPushEn HssSrvTcpPushEn ShClnTcpPushEn ShSrvTcpPushEn CxClnTcpPushEn
SyClnTcpPushEn SdSrvTcpPushEn DiaClnCcTcpPushEn DiaSrvCcTcpPushEn GxcClnTcpPushEn
CxSrvTcpPushEn TyCcClnTcpPushEn TyCcSrvTcpPushEn TxClnTcpPushEn  

 
Maximum Segment Size

Specifies the largest amount of data, specified in octets, that a computer or communications device can receive in a TCP segment. It does not count the TCP header or the IP header. The IP datagram containing a TCP segment may be self-contained within a single packet, or it may be reconstructed from several fragmented pieces:either way, the Maximum Segment limit applies to the total amount of data contained in the final reconstructed TCP segment.  

NOTE: The default TCP Maximum segment size is 536. Where a host wishes to set the maximum segment size to a value other than the default (536), the maximum segment size is specified as a TCP option, initially in the TCP SYN packet during TCP handshake. The value cannot be changed after the connection is established.

 

Available on all Service Based Producer/Consumer TCP tabs in AMF Node/Nodal, DRA Node/Nodal, HSS Node, IMS Node, Service Based Node/Nodal, and SMF Node/Nodal.

Also supported in OCS Node, OFCS Node and PCRF Node.

Available in MME Nodal when MMS Support is enabled. 

Range: 0 and 65535

Default: 2048

Tcl Parameter: RadTcpMaxSegmentSize

Tcl Parameter: MmsDataMaxSegmentSize
DSCP

The DSCP (Differentiated Service Code Point) is only applicable for the SBC Node and WiMax Nodal test cases.  

The PDSN must ensure that the MN only uses valid DSCP values based on the mobile subscriber's profile or on network policy, and may re-mark packets with inappropriate DSCP values. Enter 0 for Default Forwarding (best effort) or see the IANA DSCP Registry for Class Selection, Assured Forwarding, and Expedited Forwarding pool values.

NOTE: The DSCP value is only configurable when the Test Appliance is licensed for WIMAX testing. The Test Case also allows you to configure this value for the emulated MN.

 
Retransmission Timer

You can define the retry time with TCP/SCTP Retransmission Timer. By default the timer is configured as described in RFC 2988 — Computing TCP's Retransmission Timer. When you select Fixed Retry Time, you can specify the number of milliseconds for the timer in the field provided. The total number of retries is fixed at 5.

Options:

Fixed Retry Time (ms)

Range: 100 — 30,000 (Data Traffic), 100 — 65,535 (Diameter)

Default: 3000 (Data Traffic), 750 (Diameter)

Default: Use RFC 2988 Algorithm

Use Dynamic Algorithm

 

Retransmission Timeout Init (ms)

Retransmission Timeout Min (ms)

Retransmission Timeout Max (ms)

The following parameters to achieve timer granularity for SCTP is available only in AMF Nodal and AMF Node and MME Nodal and MME Node test cases. Available in HSS Node / DRA Nodal / DRA Node for certain interfaces such as : S6a, Sh , Cx, etc.

Retransmission Timeout Init (ms):

Range: 100 — 60000

Default: 1000

Tcl Parameter: SctpRtoInit

(<tab_prefix>SctpRtoMin<tab_suffix>)

Retransmission Timeout Min (ms):

Range: 100 — 60000

Default: 1000

Tcl Parameter: SctpRtoMin

(<tab_prefix>SctpRtoMin<tab_suffix>)

Retransmission Timeout Max (ms):

Range: 100 — 60000

Default: 60000

Tcl Parameter: SctpRtoMax

(<tab_prefix>SctpRtoMax<tab_suffix>)

 

TcpRetryTime I2TcpRetryTime IscTcpRetryTime MlTcpRetryTime MwTcpRetryTime
MxTcpRetryTime RadTcpRetryTime N2TcpRetryTime N2SctpRtoMin N2SctpRtoMax
CxSrvTcpRetryTime ShSrvTcpRetryTime CxSrvSctpRtoMin CxSrvSctpRtoMax ShSrvSctpRtoMin
ShSrvSctpRtoMax ShSrvSctpRtoInit CxSrvSctpRtoInit HssSrvTcpRetryTime HssSrvSctpRtoInit
HssSrvSctpRtoMax HssSrvSctpRtoMin HssClnTcpRetryTime HssClnSctpRtoInit HssClnSctpRtoMax
HssClnSctpRtoMin TyCcSrvTcpRetryTime TyCcSrvSctpRtoInit TyCcSrvSctpRtoMax TyCcSrvSctpRtoMin
TyCcClnTcpRetryTime TyCcClnSctpRtoInit TyCcClnSctpRtoMax TyCcClnSctpRtoMin DiaSrvTcpRetryTime
DiaSrvSctpRtoInit DiaSrvSctpRtoMax DiaSrvSctpRtoMin DiaClnTcpRetryTime DiaClnSctpRtoInit
DiaClnSctpRtoMax DiaClnSctpRtoMin DraAppTcpRetryTime DraAppSctpRtoInit DraAppSctpRtoMax
DraAppSctpRtoMin RanO1NcTcpRetryTime NonRtRicO1NcTcpRetryTime MmsDataTcpRetryTime  

 

Related Measurements
Min TCP Header Size (bytes)

Select to add the minimum Header size for TCP Transport. Will pad with Zero's, if necessary, to reach the minimum amount specified.

Available when Transport = TCP and VoLTE (Gm, I2, ISC, Ml, Mw, Mx Interfaces).

Range: 20 to 60

Default: 20

Tcl Parameter: SipMinTcpHeaderSize

I2SipMinTcpHeaderSize IscSipMinTcpHeaderSize MlSipMinTcpHeaderSize MwSipMinTcpHeaderSize MxSipMinTcpHeaderSize
RanO1NcMinTcpHeaderSize NonRtRicO1NcMinTcpHeaderSize MmsDataMinTcpHeaderSize    

 
Max # of packets before ACK

Select to enter the maximum number of packets to wait for before forcing an ACK (if not sent otherwise). This option is used to control delayed ACK.

Available in SMF Nodal Test Case Namf , AMF-SMF, AMF-UDM Interfaces. Available in SMF Node Test Case Nsmf Interface, SMF-AMF and SMF-PCF Interfaces.

Available in AMF Node Test Case Namf, Nsmf Interface, AMF-AMF, AMF-SMF, AMF-LMF and AMF-GMLC Interfaces.

 Available in MME Nodal when MMS Support is enabled. 

Range: 0 to 255 (0 (zero) means this configuration is disabled, not used)

Default: 0

Tcl Parameter:

NamfTcpPacketToForceAckEn N11NsmfTcpPacketToForceAckEn NsmfTcpPacketToForceAckEn N11NamfTcpPacketToForceAckEn
NamfTcpPacketToForceAck N11NsmfTcpPacketToForceAck NsmfTcpPacketToForceAck N11NamfTcpPacketToForceAck
N8NudmTcpPacketToForceAckEn N7NpcfTcpPacketToForceAckEn NlsNlmfTcpPacketToForceAckEn N14NamfTcpPacketToForceAckEn
N8NudmTcpPacketToForceAck N7NpcfTcpPacketToForceAck NlsNlmfTcpPacketToForceAck N14NamfTcpPacketToForceAck
NlgNgmlcTcpPacketToForceAckEn NlgNgmlcTcpPacketToForceAck MmsDataTcpPacketToForceAckEn MmsDataTcpPacketToForceAck
Respond RST to Challenge ACK

Select to Respond RST to Challenge ACK per RFC #5961 4.2 : 

 "1) If the SYN bit is set, irrespective of the sequence number, TCP
MUST send an ACK (also referred to as challenge ACK) to the remote peer:

<SEQ=SND.NXT><ACK=RCV.NXT><CTL=ACK>

After sending the acknowledgment, TCP MUST drop the unacceptable segment and stop processing further.

By sending an ACK, the remote peer is challenged to confirm the loss of the previous connection and the request to start a new connection.

A legitimate peer, after restart, would not have a TCB in the synchronized state. Thus, when the ACK arrives, the peer should send a RST segment back with the sequence number derived from the ACK field that caused the RST."

 

Available in AMF Nodal Test Case Nnrf Client, SMF-AMF Interfaces.

Available in AMF Node Test Case Nnrf Client,  AMF-AMF, AMF-SMF, AMF-AUSF, AMF-UDM, AMF-NSSF, AMF-LMF and AMF-GMLC Interfaces.

Available in DRA Nodal Test Case Nnrf Client, PCF-BSF Interfaces.

Available in DRA Node Test Case Nnrf Client Interface.

Available in HSS Node Test Case Nnrf Client Interface.

Available in IMS Node Test Case AF-PCF Interface.

Available in RIC Nodal Test Case O1-HTTP Interface.

Available in SMF Nodal Test Case Nnrf Client, AMF-SMF, AMF-UDM Interfaces.

Available in SMF Node Test Case Nnrf Client, SMF-AMF, SMF-PCF and SMF-UDM Interfaces.

Available to all NF Consumer tabs in Service Based Node/Nodal. 

 

 

Tcl Parameter:

NnrfClnRstToChallengeAckEn N11NamfRstToChallengeAckEn N14NamfRstToChallengeAckEn N50NamfRstToChallengeAckEn
N8NudmRstToChallengeAckEn N11NsmfRstToChallengeAckEn N12NausfRstToChallengeAckEn N22NnssfRstToChallengeAckEn
NlsNlmfRstToChallengeAckEn NlgNgmlcRstToChallengeAckEn NpcfNbsfRstToChallengeAckEn N5NpcfRstToChallengeAckEn
N7NpcfRstToChallengeAckEn N10NudmRstToChallengeAckEn N13NudmRstToChallengeAckEn N21NudmRstToChallengeAckEn
N15NpcfRstToChallengeAckEn N30NpcfRstToChallengeAckEn N28NchfRstToChallengeAckEn N40NchfRstToChallengeAckEn
NsmsfNchfRstToChallengeAckEn N29NnefRstToChallengeAckEn N33NnefRstToChallengeAckEn N35NudrRstToChallengeAckEn
N36NudrRstToChallengeAckEn N37NudrRstToChallengeAckEn NafNbsfRstToChallengeAckEn NnefNbsfRstToChallengeAckEn
N51NamfRstToChallengeAckEn N29NsmfRstToChallengeAckEn N52NudmRstToChallengeAckEn CseppN32cRstToChallengeAckEn
NrfNudrRstToChallengeAckEn N17NeirRstToChallengeAckEn RanO1HttpRstToChallengeAckEn  

 
Link Recovery

Select Link Recovery to restart the SCTP link recovery procedure after an initial link failure. During AMF, HNB, MME and UMTS testing, Link Recovery re-initiates subsequent SCTP association with SUT (HNB/eNodeB/RNC) after the link fails. The initial initiation works with 7 heartbeats in an interval of 30 sec.

In HNB GW Nodal test case, Link Recovery is available for selection only when HNB-GW Recovery (HNB GW Nodal > Iuh > HNBAP tab) is not selected.

In AMF Nodal test case, Link Recovery is available for N2 Interface, NGAP | SCTP.

Available in HSS Node / DRA Nodal / DRA Node for certain interfaces such as : S6a, Sh , Cx, Gx, Gy, etc.

NOTE: If SCTP fails for any reason, the HNB, or eNodeB or gNodeB, or RNC tries to re-establish SCTP connectivity by sending the SCTP INIT message for the specified Max Retries for duration of the Heartbeat interval.

Type: True/False

Default: True

Tcl Parameter:

SctpLinkRecoveryEn N2SctpLinkRecoveryEn SctpLinkRecoveryEn_1
CxSrvSctpLinkRecoveryEn ShSrvSctpLinkRecoveryEn DraAppSctpLinkRecoveryEn
HssClnSctpLinkRecoveryEn HssSrvSctpLinkRecoveryEn TyCcClnSctpLinkRecoveryEn
TyCcSrvSctpLinkRecoveryEn DiaClnSctpLinkRecoveryEn DiaSrvSctpLinkRecoveryEn

In MME Nodal test case, select Restart on Link Recovery to indicate restarting all links/connectivity between eNodeB and the MME SUT.

SctpRestartOnLinkRecoveryEn SctpRestartOnLinkRecoveryEn_1

In AMF Nodal anf gNB CU node test cases, select Resend NgapSetupRequest to re send the NgapSetupRequest.

N2SctpRestartOnLinkRecoveryEn

 
Maximum Number of Retransmissions Associations Path0 Path1 Path2 Path3

Maximum Number of Retransmissions is the maximum number of attempts made by the RNC/eNodeB to retransmit an SCTP payload after the ACK Timeout has expired. In the case where a certain number of retries has been reached, an abort to tear down the SCTP link will be sent followed by an INIT to re-establish the link.

Range: 0 - 255

Default: 5

Tcl Parameter:

SctpMaxRetransAssoc SctpMaxRetransAssoc_1
HssSrvS6aSctpHeartbeatMaxRetransAssoc  
NOTE: The Maximum Number of Retransmissions in SCTP tab does not apply to the INIT message. Landslide will keep sending INIT message if there is no response to INIT.

 

If Multi-Homed is enabled (in the HSS Nodal (MME HSS I/F), HSS Node (HSS node) and MME Nodal (eNodeB Control Node), MME Node Test Cases (MME S1 Node)), LCS Nodal/LCS Node (MME Slg Node ) then:

Path0 and Path1 become available (per RFC 4960)

Range: 0 - 255

Default: 5

Tcl Parameter:

SctpMaxRetransPath0 SctpMaxRetransPath0_1 HssClnSctpMaxRetransPath0 HssSrvS6aSctpMaxRetransPath0
SctpMaxRetransPath1 SctpMaxRetransPath1_1 HssClnSctpMaxRetransPath1 HssSrvS6aSctpMaxRetransPath1

 

If Multi-Homed and SCTP 2x2 Mesh are enabled (in the HSS Nodal (MME HSS I/F), HSS Node (HSS node) and MME Nodal (eNodeB Control Node), MME Node Test Cases (MME S1 Node)), LCS Nodal/LCS Node (MME Slg Node ) ,Multi-Homed and SCTP 2x2 Mesh  is only configurable for the following interfaces in  HSS Node / DRA Nodal Test Cases : MME S6a Node , PCRF Node when AGW Rx is enabled, OCS Node Ro, PGW , and Generic interfaces then:

Path2 and Path3 become available (per RFC 4960)

Range: 0 - 255

Default: 5

Tcl Parameter:

SctpMaxRetransPath2 SctpMaxRetransPath2_1 HssClnSctpMaxRetransPath2 HssSrvS6aSctpMaxRetransPath2
SctpMaxRetransPath3 SctpMaxRetransPath3_1 HssClnSctpMaxRetransPath3 HssSrvS6aSctpMaxRetransPath3
Heartbeat Interval (s)

Use the Heartbeat Interval to set the time interval in seconds between two consecutive Heartbeat Request messages.

Reference RFC 4960 - "On an idle destination address that is allowed to heartbeat, it is recommended that a HEARTBEAT chunk is sent once per RTO of that
destination address plus the protocol parameter ’HB.interval’, with jittering of +/- 50% of the RTO value, and exponential backoff of the RTO if the previous HEARTBEAT is unanswered. A primitive is provided for the SCTP user to change the HB.interval and turn on or off the heartbeat on a given destination address. The heartbeat interval set by the SCTP user is added to the RTO of that destination (including any exponential backoff). Only one heartbeat should be sent each time the heartbeat timer expires (if multiple destinations are idle). It is an implementation decision on how to choose which of the candidate idle destinations".

Range: 0 - 65535

Default: 30

Tcl Parameter:

SctpHeartbeatInterval SctpHeartbeatInterval_1
HssSrvS6aSctpHeartbeatInterval  
NOTE:
  • The heartbeat mechanism provides a means to detect failures, quickly inform peers in the event of a recovery from node failures, and allow a peer to take appropriate action.
  • The time is always 1 higher than the set value.
Enable ACK

Select to indicate acknowledge messages from primary transport address used to reach the endpoint.
Secondary ACK

Secondary ACK is available when you select Multi-Homed as follows in various test cases:

Select to indicate acknowledge messages from secondary transport address used to reach the endpoint.

The primary path that carries traffic switches to a secondary path for carrying traffic when a fault is detected (See RFC-4960)

Tcl Parameter:

HssSrvS6aSctpAckEn HssSrvS6aSctpSecAckEn CxSrvSctpAckEn ShSrvSctpAckEn
3-SACK Rule

SCTP connections conform with 3 SACK (Selective Acknowledgement) GAP count rule as specified in RFC-4960.

Tcl Parameter: Sctp3SackRuleEn

(<tab prefix> + Sctp3SackRuleEn + <tab suffix>)

Selective Acknowledgement (SACK) is sent to the peer endpoint to acknowledge received data chunks and to inform the peer endpoint of gaps in the received subsequences of data chunks as represented by their TSNs.

The SACK contains the Cumulative TSN Ack, Advertised Receiver window Credit (a_rwnd), Number of Gap Ack Blocks, and Number of Duplicate TSNs fields.

The SACK also contains zero or more Gap Ack Blocks.  Each Gap Ack Block acknowledges a subsequence of TSNs received following a break in the sequence of received TSNs.  By definition, all TSNs acknowledged by Gap Ack Blocks are greater than the value of the Cumulative TSN Ack.
SACK Threshold (packets)

Indicates the number of packets received before sending SACK to the peer endpoint.   

Range: 0 - 65535

Default: 2

Tcl Parameter: SctpSackThreshold

(<tab prefix> + SctpSackThreshold + <tab suffix>)

 
Process SACK Revocations

Available in HSS Node (S6a, Cx, Sh), MME Nodal and MME Node (S1-MME). Select for support of RENEGing per RFC 4960.

Tcl Parameter: HssSrvS6aSctpSackRevokingEn

Tcl Parameter: CxSrvSctpSackRevokingEn

Tcl Parameter: ShSrvSctpSackRevokingEn

Tcl Parameter: SctpSackRevokingEn
Chunk Bundling (bytes)

Select specify chunks (packets in bytes) to be bundled.

Option: 0 - 65535

Default: 0

Tcl Parameter: SctpChunkSize

Available in the following test case tabs:

  • Home eNodeB GW Node | S1-MME | SCTP, and S1-Home eNodeB | SCTP tabs.  

  • MME Nodal | S1-MME | SCTP, and Target Iu-PS | SCTP tabs.  

  • UMTS | Iu-PS | SCTP and Target Iu-PS | SCTP tabs.
Chunk Bundle Timer (ms)

Select specify chunks bundle timer in milliseconds. Used in conjunction with Chunk Bundling.

NOTE: Prior to Release 15.5, this was a hard coded value of 200ms.

Option: 10 - 200

Default: 100

Tcl Parameter: SctpChunkTimer

Available in the following test case tabs:

  • Home eNodeB GW Node | S1-MME | SCTP, and S1-Home eNodeB | SCTP tabs.  

  • MME Nodal | S1-MME | SCTP, and Target Iu-PS | SCTP tabs.  

  • UMTS | Iu-PS | SCTP and Target Iu-PS | SCTP tabs.
Max Data Chuck Length (bytes)

Provides the capability to send out big packet without fragment on S1-MME interface on MME Nodal test case.

This variable is used to SCTP fragmentation as described in RFC#2960 6.9 section (Fragmentation and Reassembly). It is corresponding to the value of Length field in RFC#2960 3.3.1 section(Payload Data (DATA)).

Range: 17 - 65535

Default: 1016

Tcl Parameter: SctpMaxDataChuckLen
ACK Delayed (ms)

Indicates the delay time for an ACK in milliseconds.   

Range: 1 - 500

Default: 100

Tcl Parameter: SctpAckDelay

(<tab prefix> + SctpSackThreshold + <tab suffix>)

 
Process SCTP Fragments Reorder

Available on Hss Node (Cx, Sh), MME Nodal, MME Node, PCRF Nodal (Gx, Rx) and PCRF Node (Gx, Rx). Select to enable support of processing SCTP fragments reorder.

Tcl Parameter: SctpProcessFragReorder
Number of Streams

Available on AMF Nodal/AMF Node (N2 interface), HSS Node (Cx, Sh), HSS Nodal (Sh,  Cx S-CSCF, Cx I-CSCF), MME Nodal/MME Node - S1-MME interface.

Enter the number of streams. 

Note : The number of streams are the same for in and out streams unless you enable Different Number of Inbound/Outbound Streams which is only supported in limited test cases- see below.

Range : 1 to 32 (HSS test cases), 2 to 65535 ( AMF and MME test cases)

Default : 1 (HSS test cases), Default : 2 (AMF and MME test cases)

Tcl Parameter: SctpNumStreams

Tcl Parameter: N2SctpNumStreams

Tcl Parameter: CxSrvSctpNumStreams

Tcl Parameter: ShSrvSctpNumStreams

Tcl Parameter: ShClnSctpNumStreams

Tcl Parameter: HssCxIcscfClnSctpNumStreams

Tcl Parameter: HssCxScscfClnSctpNumStreams
Different Number of Inbound/Outbound Streams

Available on AMF Nodal/AMF Node (N2 interface) and MME Nodal/MME Node - S1-MME interface.

Enable to enter different number of inbound / outbound streams. When enabled, the Number of Streams becomes disabled.

Enter Inbound Number of Streams.

Enter Outbound Number of Streams.

Range : 1 to 65535

Default : 2 (AMF and MME test cases)

Tcl Parameter: SctpInboundNumStreams

Tcl Parameter: SctpOutboundNumStreams

Tcl Parameter: N2SctpInboundNumStreams

Tcl Parameter: N2SctpOutboundNumStreams
Enable Per-Packet Retry Timers

Available on MME Nodal, S1-MME | SCTP. When enabled, each SCTP packet has a retransmission timer that gets set.

Tcl Parameter: SctpPerPacketRetryTimerEn
Initiate Connection

Available in HSS Node/Nodal. Select to initiate connection towards MME instead of waiting for connection from MME.

Tcl Parameter: CbcSrvSBcSctpInitConnectionEn

Tcl Parameter: CbcClnSBcSctpInitConnectionEn

Available in the following test case tabs:

  • HSS Node | SBc | SCTP tab.  

  • HSS Nodal | SBc | SCTP tab.  
Accept All SCTP Stream ID

Available in CDMA Voice Nodal test case.

Select to accept any Stream ID from MSC.

Tcl Parameter: SctpAcceptAllStreamIdEn
Emulate Out Of Range SCTP Stream ID

Available in CDMA MSCe Node test case.

Select to emulate an out of range SCTP Stream ID from MSC.

Tcl Parameter: SctpStreamIdTestEn

 

^ Back to Top

© 2024 Spirent Communications Inc. All Rights Reserved.