In this section:
These sections describe the configuration objects used for signaling. The following diagram depicts a basic signaling configuration.
Use this object to configure global Diameter signaling controls.
% set global signaling diamSigControls addSonusSpecificAVP <disabled | enabled> defaultCCF <ipAddress> enableRfApp <disabled | enabled> generateFailedEventAcr <disabled | enabled> maxACRretransmission <0-3> rfInterimAccInrvl <0-180>
Parameter | Length/Range | Description |
---|---|---|
addSonusSpecificAVP | N/A | Enable flag to send additional CDR information within Sonus vendor-specific Attribute Value Pairs (AVPs) in Accounting-Request (ACR) messages over the existing Rf Interface.
See Rf Interface Support for AVP details. |
defaultCCF | Up to 32 characters | <ip address> (default = 0.0.0.0) – Specify the IP address to use as the default CCF realm configuration if CCF is not received in the PCFA. |
enableRfApp | N/A | Use this flag to enable the Rf Accounting application at the system level to send accounting information over Rf Interface. See Rf Interface Support for feature details.
|
generateFailedEventAcr | N/A | Enable flag to prevent failed call ACR event from being sent.
|
maxACRretransmission | 0-3 | Specify the maximum number of ACR retransmissions to use if the SBC does not receive ACA (default = 3). |
rfInterimAccInrvl | 0-180 | Use this parameter to specify the interim account interval value to send when no interval is received in ACA. Set value to “0” to not send interim record (default = 30). If ACA has a different value than |
This object allows you to configure the signaling timers for the gateway.
% set global signaling gwSigTimers congRelDelay <delay in seconds> establish <timer value, in seconds> idle <idle time, in hours> keepalive <keepalive time, in seconds> retry <number of minutes to attempt to recover GW signaling link> % show global signaling gwSigTimers % delete global signaling gwSigTimers
Parameter | Description |
---|---|
| Amount of time (in seconds) that a call which is rejected due to congestion will be delayed before the release is issued. (default = 0). |
| The Gateway Signal Channel Establishment Timer (in seconds.) This value applies to all signal channels. (default = 10). |
| Amount of time (in hours) a GW Signaling Link May be idle before it is taken down. (default = 0). |
| The Gateway Signal Channel Keep-alive Timer (in seconds.) This value applies to all signal channels. (default = 3). |
| Amount of time (in minutes) the SBC will continue to attempt to recover a GW Signaling Link as long as there are stable calls up. (default = 60). |
This object allows you to configure signaling timers for the node.
% set global signaling h323SigTimers establish <timer value, in seconds> t301 <timer value, in seconds> t302 <timer value, in seconds> t303 <timer value, in seconds> t304 <timer value, in seconds> t310 <T3timer value, in seconds10> tcpConnect <tcpConnect> % show global signaling h323SigTimers % delete global signaling h323SigTimers
Parameter | Length/Range | Description |
---|---|---|
| 0-127 | The H225 signal channel establishment timer (in seconds). Default value is 4. |
| 0-65535 | The T301 call timer (in seconds). Default value is 180 seconds. |
| 0-127 | The T302 call timer (in seconds). Default value is 15 seconds. |
| 0-127 | The T303 call timer (in seconds). Default value is 4 seconds. |
| 0-127 | The T304 call timer (in seconds). Default value is 20 seconds. |
| 0-127 | The T310 call timer (in seconds). Default value is 10 seconds. |
| 0-127 | The TCP connect timer (in seconds). Default value is 3 seconds. |
To display the global configuration of all h323SigTimers:
% show global signaling h323SigTimers establish 33; tcpConnect 77; t301 444; t302 33; t303 22; t304 33; t310 33;
This object allows you to configure SIP Peer Overload parameters.
% set global signaling sipPeerOverloadControl discardPeriod <1-10 seconds> rejectThreshold <0-50> samplingPeriod <1-10> stepDownGain <1-200> % show global signaling sipPeerOverloadControl % delete global signaling sipPeerOverloadControl
Parameter | Length/Range | Description |
---|---|---|
| 1-10 | Discard period (in seconds) for the Peer Overload back-off algorithm. (default = 2). |
| 0-50 | Specifies the reject threshold (in rejects/sec) for the Peer Overload backoff algorithm. (default = 1). |
| 1-10 | Specifies the sampling period (in seconds) for the Peer Overload back-off algorithm. (default = 2). |
| 1-200 | Specifies the step down gain for the Peer Overload back-off algorithm. (default = 100). |
| 1-64 | To display different levels of output information in show commands. |
To display the global configuration of all SIP overload control:
% show global signaling sipPeerOverloadControl samplingPeriod 2; discardPeriod 1; stepDownGain 44; rejectThreshold 33;
Use this object to configure SIP signaling control parameters.
% set global signaling sipSigControls egressRNParam <disabled | enabled> loopDetectionFeature <disabled | enabled> maxPduSizeValue <pdusize2kb | pdusize3kb | pdusize6kb | pdusize15kb | pdusize32kb | pdusize60kb> multipleContactsPerAor <disabled | enabled> registrarSupportContactParam <disabled | enabled> send503DuringSwitchover <disabled | enabled> sendSurrogateUnRegAfterReboot <disabled | enabled> suppressErrorInfoHdr <disabled | enabled> surrogateRegisterPacingTime <0-10000> ucidNodeId <node_id> % show global signaling sipSigControls % delete global signaling sipSigControls
Parameter | Length/Range | Description |
---|---|---|
| N/A | The egress RN parameter. Specifies whether the Unable to show "metadata-from": No such page "_space_variables" sends a Redirecting Number Information Element (RNIE) in the egress leg of the call per RFC3398 when the R-URI and the To header differ.
|
| N/A | When enabled, the SIP Stack performs loop detection on incoming INVITE messages.
|
| N/A | The maximum PDU size recognized by the Unable to show "metadata-from": No such page "_space_variables" :
|
| N/A | Use this flag to support multiple contacts per Address Of Record (AoR).
The SBC supports validating the source IP address and the port even if In case of refresh registration that is originated from a different IP/port, the SBC forwards the request to the registrar and move the sate to "UPDATING". Any calls or OOD requests that are originated from the IAD while the RCB is in updating state must be validated using the previously authenticated IP/port. When the flag See Multiple Contacts per AoR feature page for additional details. Even though the default value of |
| N/A | Enable flag to support parameters in the Contact header:
|
send503DuringSwitchover | N/A | Use this flag to control the sending of 503 message during a switchover.
The Retry-after tag is set to 60 seconds once the 503 message is sent. |
sendSurrogateUnregAFterReboot | N/A | Enable flag to trigger de-register messages to all AORs configured to use the Surrogate Registration feature after a reboot.
|
| N/A | Enable flag to suppress Error-Info header in a response to a request message with syntax error.
|
surrogateRegisterPacingTime | 0-10000 | Use this parameter to specify the time gap, in milliseconds, between a final response of surrogate register and the next surrogate register message sent across all peers. (default = 0, disabled) If surrogate registration is active and you wish to disable pacing, first disable surrogate registration for each peer using following command syntax: % set addressContext <AC name> zone <zone name> ipPeer <peer name> surrogateRegistration state disabled Please research the feature to fully understand pacing semantics before using it. This setting is not required in generic deployments. Pacing is applied to all surrogate REGISTER requests generated for all surrogate AoRs. |
| 1-32767 | UCID Node Id used to generate the UCID in the User-to-User Header. (default = 0) |
To display the global configuration of all SIP signaling control parameters:
% show global signaling sipSigControls loopDetectionFeature enabled; registrarSupportContactParam enabled; suppressErrorInfoHdr enabled; maxPduSizeValue pdusize3kb; egressRNParam enabled; multipleContactsPerAor enabled; surrogateRegisterPacingTime enabled; ucidNodeId 13; }
SRVCC provides the ability to transition a voice call from the VoIP/IMS packet domain (LTE) to the legacy circuit domain. Variations of SRVCC are being standardized to support both GSM/UMTS and CDMA 1x circuit domains. For an operator with a legacy cellular network who wishes to deploy IMS/VoIP-based voice services in conjunction with the rollout of an LTE network, SRVCC offers VoIP subscribers with coverage over a much larger area than would typically be available during the roll-out of a new network.
% set global signaling srvcc atcfUri (1-63 chars) callLingerTimer (1-32 seconds) eStnSr (1-32 chars) pstopsSti (0-32 chars) stnSr (1-32 chars)
set global signaling srvcc pstopsSti +1-pstopsSti-222 commit show global signaling srvcc pstopsSti pstopsSti +1-pstopsSti-222;