Signaling - Sip Sig Controls

Specifies whether or not the SIP Stack will perform loop detection on incoming INVITE messages. The options are:

• Enabled (default)

• Disabled


Specifies whether a Registrar supports parameters in the Contact header:

• Enabled (default): Parameters in the Contact header are supported. In most cases, you should select the Enabled setting.
• Disabled: Parameters in the Contact header are not supported. This value is provided only for backwards compatibility.

• Enabled
• Disabled (default)

The maximum PDU size that recognized by SBC software:

• 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

The egress RN parameter. Specifies whether the SBC 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)

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

• Disabled – Only a single contact per Address of Record is supported.
• Enabled (default) – The SBC maintains different RCBs for each new registration and verifies the source IP address and port during Registration Control Block (RCB) lookup.

The SBC supports validating the source IP address and the port even if Multiple Contacts Per Aor flag is Disabled. The SBC also supports locating the RCB using the AoR to perform additional validation on the source IP address and port if the the flag Require Registration is set to "required" or "required-non-priority". This is applicable for both calls and OOD requests that are originated from the IAD.

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 Multiple Contacts Per Aor is Enabled, 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. Any of the registered UEs may initiate a communication on behalf of the AoR, and the SBC fetches the corresponding RCB based on source IP port of the UE.

NOTE: Even though the default value of Multiple Contacts Per Aor is "Enabled", during an upgrade the value can be either "Enabled" or "Disabled".

See Multiple Contacts per AoR for additional details.

Enable this flag to allow the SBC to send the Contact header as a star (*) in DEREGISTER messages if Multiple Contacts Per Aor is Disabled.

• Disabled
• Enabled (default)

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. The value ranges from 0 to 10000 and the default value is 0.

If surrogate registration is active and you wish to disable pacing, first disable surrogate registration for all Peers from IP Peer- Surrogate Registration page.

NOTE: Please research the feature in order 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.

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

• Disabled (default)
• Enabled

Use this flag to control the sending of 503 message during a switchover.

• Disabled  – The request is dropped with no 503 messages sent for Invites. 
• Enabled  (default) – Send 503 message during a switchover.

NOTE: The Retry-after tag is set to 60 seconds for 503 sent.