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>
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
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
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
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> sendDeRegisterContactAsStar <disabled | enabled> sendSurrogateUnRegAfterReboot <disabled | enabled> suppressErrorInfoHdr <disabled | enabled> surrogateRegisterPacingTime <0-10000> ucidNodeId <node_id> % show global signaling sipSigControls % delete global signaling sipSigControls
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;