Versions Compared

Old Version 3

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version 4

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Use this object to configure SIP signaling control parameters.

Command Syntax

Code Block
languagenone
% set global signaling sipSigControls 
	egressRNParam <disabled | enabled> 
	loopDetectionFeature <disabled | enabled> 
	maxPduSizeValue <pdusize2kb | pdusize3kb | pdusize6kb | pdusize15kb | pdusize32kb | pdusize60kb> 
	multipleContactsPerAor <disabled | enabled>
	registrarSupportContactParam <disabled | enabled>
	sendSurrogateUnRegAfterReboot <disabled | enabled>
	suppressErrorInfoHdr <disabled | enabled>
	surrogateRegisterPacingTime <0-10000>
	ucidNodeId <node_id>
 
% show global signaling sipSigControls
	egressRNParam 
	loopDetectionFeature
	maxPduSizeValue
	multipleContactsPerAor
	registrarSupportContactParam
	suppressErrorInfoHdr 
	surrogateRegisterPacingTime
	ucidNodeId
 
% delete global signaling sipSigControls

...

Parameter

Length/Range

Description

egressRNParam

N/A

The egress RN parameter. Specifies whether the 

Spacevars
0product
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.

  • disabled
  • enabled (default)

loopDetectionFeature

N/A

When enabled, the SIP Stack performs loop detection on incoming INVITE messages.

  • disabled – The SIP signaling group processes the INVITE message.
  • enabled (default)

maxPduSizeValue

N/A

The maximum PDU size recognized by the

Spacevars
0product
:

  • pdusize2kb – 2,048 bytes
  • pdusize3kb – 3,072 bytes
  • pdusize6kb – 6,000 bytes
  • pdusize15kb (default) – 15,000 bytes
  • pdusize32kb – 32,000 bytes
  • pdusize60kb – 60,000 bytes

multipleContactsPerAor

N/A

This flag enables support of multiple contacts per Address Of Record (AoR).

  • disabled – SBC maintains a single RCB per Address of Record (AoR). Any existing binding information is overwritten on receipt of REGISTER from a new contact for the same AoR.
  • enabled (default) – SBC maintains different RCBs for each new registration. A registration is considered new when the source IP port of the REGISTER request is different from earlier registration for the same AoR. If a registered UE initiates a communication on behalf of the AoR, SBC fetches the corresponding RCB based on source IP port of the UE.

 See Multiple Contacts per AoR for additional details.

registrarSupportContactParam

N/A

Enable flag to support parameters in the Contact header:

  • disabled – Parameters in the Contact header are not supported. This value is provided only for backwards compatibility.
  • enabled (default) – Parameters in the Contact header are supported.
sendSurrogateUnregAFterRebootN/A

Enable flag to trigger de-register messages to all AORs configured to use the Surrogate Registration feature after a reboot.

  • disabled (default)
  • enabled

suppressErrorInfoHdr

N/A

Enable flag to suppress Error-Info header in a response to a request message with syntax error.

  • disabled (default) – SBC includes Error-info header in the response.
  • enabled –  SBC does not include Error-Info header in an error status. 
surrogateRegisterPacingTime0-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 all Peers each peer using following command syntax:

Code Block
languagenone
% set addressContext <AC name> zone <zone name> ipPeer <peer name> surrogateRegistration state disabled
Note

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.

ucidNodeId

1-32767

UCID Node Id used to generate the UCID in the User-to-User Header. (default = 0)

...

Code Block
languagenone
% show global signaling sipSigControls
loopDetectionFeature         enabled;
registrarSupportContactParam enabled;
suppressErrorInfoHdr         enabled;
maxPduSizeValue              pdusize3kb;
egressRNParam                enabled;
multipleContactsPerAor       enabled;
surrogateRegisterPacingTime  enabled;
ucidNodeId                   13;
}

Single Radio Voice Call

...

Continuity (SRVCC)

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 rollout roll-out of a new network.

Command Syntax

...