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;
Configure the SBC for the maximum number of transfers (10-100
) allowed within a call; default is 10
.
% set global signaling maxNumTransfers <10-100>
To configure maxNumTransfers
, use the following example:
% set global signaling maxNumTransfers 30 % commit
maxNumTransfers
, use the following example:In the "configure" mode:
% show global signaling maxNumTransfers maxNumTransfers 30
In the "display" mode (when you exit the "configure" mode):
> show table global signaling maxNumTransfers 30; messageManipulation { inputAdapterProfile DD1; outputAdapterProfile DD1; } sipPeerOverloadControl { samplingPeriod 2; discardPeriod 2; stepDownGain 100; rejectThreshold 1; } sipSigControls { registrarSupportContactParam enabled; maxPduSizeValue pdusize15kb; }
The SBC supports applying SIP message manipulation (SMM) profiles (SIP adaptor profiles) at the global level. Use the following parameters to assign SIP adaptor profiles that apply globally on ingress or egress. Refer to SIP Message Manipulation for more information on SMM.
% set global signaling messageManipulation inputAdapterProfile <profile name> outputAdapterProfile <profile name>
% set global signaling messageManipulation inputAdapterProfile globalInput % set global signaling messageManipulation outputAdapterProfile globalOutput % commit
The SBC can be configured in a signaling-only mode so that the SBC participates in the exchange of signaling messages that set up a call but does not reserve or allocate any media resources for the session. The media component of the session is handled as direct media between the call participants.
% set global signaling sigOnlyMode sigOnlyModeValue <global | off>
% set global signaling sigOnlyMode sigOnlyModeValue global commit
Use this flag to configure support for SIP IP Peer Statistics in the SBC.
% set global signaling sipIpPeerStats <disabled | enabled>
To configure sipIpPeerStats
, use the following example:
% set global signaling sipIpPeerStats enabled % commit
sipIpPeerStats
, use the following example:In the "configure" mode:
% show global signaling sipIpPeerStats sipIpPeerStats enabled;
In the "display" mode (when you exit the "configure" mode):
> show table global signaling sipIpPeerStats enabled; maxNumTransfers 30; sipPeerOverloadControl { samplingPeriod 2; discardPeriod 2; stepDownGain 100; rejectThreshold 1; } sipSigControls { registrarSupportContactParam enabled; maxPduSizeValue pdusize15kb; }
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 egressRemoveEnudmi <disabled | enabled> 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> offerAnswerTimer <10-300> % 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; offerAnswerTimer 28 }
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;
The SBC supports special behavior of SIP Signaling, when interfacing with Microsoft Teams.
% set global signaling teamsSupport <disabled | enabled>
To configure sipIpPeerStats
, use the following example:
% set global signaling teamsSupport enabled % commit
teamsSupport
, use the following example:In the "configure" mode:
% show global signaling teamsSupport teamsSupport enabled;
In the "display" mode (when you exit the "configure" mode):
> show table global signaling teamsSupport enabled; maxNumTransfers 30; sipPeerOverloadControl { samplingPeriod 2; discardPeriod 2; stepDownGain 100; rejectThreshold 1; } sipSigControls { registrarSupportContactParam enabled; maxPduSizeValue pdusize15kb; }
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;
Configure the SBC for the maximum number of transfers (10-100
) allowed within a call; default is 10
.
% set global signaling maxNumTransfers <10-100>
To configure maxNumTransfers
, use the following example:
% set global signaling maxNumTransfers 30 % commit
maxNumTransfers
, use the following example:In the "configure" mode:
% show global signaling maxNumTransfers maxNumTransfers 30
In the "display" mode (when you exit the "configure" mode):
> show table global signaling maxNumTransfers 30; messageManipulation { inputAdapterProfile DD1; outputAdapterProfile DD1; } sipPeerOverloadControl { samplingPeriod 2; discardPeriod 2; stepDownGain 100; rejectThreshold 1; } sipSigControls { registrarSupportContactParam enabled; maxPduSizeValue pdusize15kb; }
The SBC supports applying SIP message manipulation (SMM) profiles (SIP adaptor profiles) at the global level. Use the following parameters to assign SIP adaptor profiles that apply globally on ingress or egress. Refer to SIP Message Manipulation for more information on SMM.
% set global signaling messageManipulation inputAdapterProfile <profile name> outputAdapterProfile <profile name>
% set global signaling messageManipulation inputAdapterProfile globalInput % set global signaling messageManipulation outputAdapterProfile globalOutput % commit
The SBC can be configured in a signaling-only mode so that the SBC participates in the exchange of signaling messages that set up a call but does not reserve or allocate any media resources for the session. The media component of the session is handled as direct media between the call participants.
% set global signaling sigOnlyMode sigOnlyModeValue <global | off>
% set global signaling sigOnlyMode sigOnlyModeValue global commit
Use this flag to configure support for SIP IP Peer Statistics in the SBC.
% set global signaling sipIpPeerStats <disabled | enabled>
To configure sipIpPeerStats
, use the following example:
% set global signaling sipIpPeerStats enabled % commit
sipIpPeerStats
, use the following example:In the "configure" mode:
% show global signaling sipIpPeerStats sipIpPeerStats enabled;
In the "display" mode (when you exit the "configure" mode):
> show table global signaling sipIpPeerStats enabled; maxNumTransfers 30; sipPeerOverloadControl { samplingPeriod 2; discardPeriod 2; stepDownGain 100; rejectThreshold 1; } sipSigControls { registrarSupportContactParam enabled; maxPduSizeValue pdusize15kb; }
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 egressRemoveEnudmi <disabled | enabled> 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> offerAnswerTimer <10-300> % 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; offerAnswerTimer 28 }
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;
The SBC supports special behavior of SIP Signaling, when interfacing with Microsoft Teams.
% set global signaling teamsSupport <disabled | enabled>
To configure sipIpPeerStats
, use the following example:
% set global signaling teamsSupport enabled % commit
teamsSupport
, use the following example:In the "configure" mode:
% show global signaling teamsSupport teamsSupport enabled;
In the "display" mode (when you exit the "configure" mode):
> show table global signaling teamsSupport enabled; maxNumTransfers 30; sipPeerOverloadControl { samplingPeriod 2; discardPeriod 2; stepDownGain 100; rejectThreshold 1; } sipSigControls { registrarSupportContactParam enabled; maxPduSizeValue pdusize15kb; }