Skip to end of metadata
Go to start of metadata

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:

  • Call Admission Control. Provides SIP level call admission control by regulating call attempts.
  • Source IP Untrusted Alarm. Sets alarm  when an Invite is received from for an untrusted source.
  • Skype/Lync Third Party Presence.  Enables the SBC 1000/2000 to pass a non-Skype/Lync device's presence information to a Skype/Lync presence server on behalf of an existing Skype/Lync client.
  • Skype/Lync STUN Server. When ICE Support is set to Enabled and ICE Mode is Full, Stun Server needs to be configured.
  • UserInfo Handling. Determines whether legacy or RFC 3261 rules are applied to the User Info portion of the SIP URI. (For examples, refer to UserInfo Decode Options for Transformation Table - Comparison of Legacy and RFC-3261.)

Configure SIP Settings

To configure SIP Settings:

  1. In the WebUI, click the Settings tab.

  2. In the left navigation pane, go to SIP > Node-level SIP Settings.

  3. Configure the options.

  4. Click Apply.


    Figure : SIP Settings


Node-Level SIP Settings - Field Definitions

Click '' on the WebUI screen to configure additional items

 Click here to expand...

Configuring an Object within an Object

  1. Access a WebUI page that includes a field for a configuration resource with support for object within an object configuration. For example, the SIP Signaling Group Table includes a number of such fields.

  2. Click the field-specific () icon next to a specific object. In the example below, the Call Routing Table field supports object within object configurability:

     

    Figure : Signaling Group Table - Example

  3. At the Create window, enter a description for the newly created object.

  4. Click OK.

     

    Figure : Create Call Routing Table - Example

  5. The Call Route Table is created. The field is auto-populated with the newly-created table, and the "changed field" is highlighted (i.e., the Call Routing Table field).

     

    Figure : Populated Field


CAC Admin State

A 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.

Alarm for Untrusted Invite

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.

Presence Destination

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.

STUN Server Destination

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.

UserInfo Decode

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


IE_SIP_PARAMETER_UI_CALLING_EXT=> 2222

which leads to the following Input Fields in Transformation:

 
Calling Address/Number = 2298082
Calling Extension = 2222

RFC 3261

Calling Num=> 2298082;ext=2222

 
IE_SIP_PARAMETER_UI_CALLING_EXT=> 2222

which leads to the following Input Fields in Transformation:

 
Calling Address/Number = 2298082;ext=2222
Calling Extension = 2222

For examples, refer to UserInfo Decode Options for Transformation Table - Comparison of Legacy and RFC-3261.