The Node-Level SIP Settings feature enables SIP options to be configured that apply to the SBC 1000/2000 at the node-level. These items include the following:
To configure SIP Settings:
Configure the options.
Click Apply.
Click '
' on the WebUI screen to configure additional itemsA Call Admission Profile provides SIP level call admission control by regulating call attempts per second, and the rate of new invite/non-invite sessions. Once the SBC limits are met, SIP will no longer accept/issue new invite or non-invite sessions (except 911 calls). This feature protects the SBC from overload conditions (an overload condition is detected if the average rate of invite and non-invite sessions exceeds the pre-determined limit or the CPU threshold is exceeded). It also prevents internal/external DOS attacks in an otherwise normal network using overload detection and resource leaks/malfunction detection.
When rejecting calls or sessions on account of admission-control, SBC sends "480 Temporarily Unavailable" response to the peers.
Options: Enable (default; enables SIP level call admission control) or Disable (disables SIP level call admission control.
Enables the "SIP Request From Untrusted IP" alarm to be sent when the SBC receives an INVITE message from an untrusted IP source. Options: Enable (alarm is sent); Disable (alarm is not sent). For more information on alarms, see Alarms and Events Reference.
Determines the server to which a Publish message is sent containing the presence information. This server is defined in a SIP Server Table. Only servers whose protocol is TLS are available in the Presence Destination list box.
When ICE Support is set to Enabled and ICE Mode is configured as Full, Stun Server configuration is required. This field specifies the STUN Server Destination, which is used to gather ICE candidates when ICE Mode is configured as Full. Only servers whose protocol is configured as UDP are available in the STUN Server Destination list box.
This server is defined in a SIP Server Table.
Options include: Legacy (default) or RFC 3261 (decode).
Using the example <sip:2298082;ext=2222@vervain.com>:
If this is selected... | Then the CCC/CallRouter will receive... |
---|---|
Legacy | Calling Num => 2298082
which leads to the following Input Fields in Transformation: |
RFC 3261 | Calling Num=> 2298082;ext=2222 which leads to the following Input Fields in Transformation: |
For examples, refer to UserInfo Decode Options for Transformation Table - Comparison of Legacy and RFC-3261.