Skip to end of metadata
Go to start of metadata

To create or modify an existing SIP Signaling Group:

  1. In the WebUI, click the Settings tab.
  2. In the left navigation pane, go to Signaling Groups.
  3. From the Create Signaling Group drop down box, select SIP Signaling Group.

Modifying a SIP Signaling Group

  1. Click the expand () Icon next to the entry you wish to modify.
  2. Edit the entry properties as required, see details below.

Creating a SIP Signaling Group

Prerequisites:

Before you can create a SIP Signaling Group, you must have defined at least the following configuration resource:

To create a SIP Signaling Group:

  1. From the Create Signaling Group drop down box at the top of the Signaling Group Table, select SIP Signaling Group.

Description

Descriptive name for the signaling group.

Admin State

Specifies the admin state of the Signaling group.

  • Enable: Enables the signaling group.
  • Disable: Disables the signaling group.
  • Drain: When Drain is selected, calls that are currently up remain connected. However, new calls and forking are not allowed for the Signaling Group. This allows all the calls to be drained from the SG.

SIP Channels and Routing - Field Definitions

Action Set Table

Specifies a defined Action Set Table for this Signaling Group.

Call Routing Table

Specifies the Call Routing Table to be used by this Signalling Group.

Number of Channels

Specifies the number of SIP channels available for calls in this Signaling Group.

SIP Profile

Specifies the SIP Profile to use for this Signaling Group

SIP Mode

Specifies the SIP Registration Mode to use in this Signaling Group.

  • Basic Call: Sends INVITEs to the selected server table.
  • Forward Reg. After Local Processing: Forwards the REGISTER request after inserting it to the local registrar.
  • Local Registrar: Maintains local registrar only. Uses registrar bindings to terminate a call.

If Fwd. Reg. After Local Processing is configured as the SIP Mode, the selected SIP Server Table for that same Signaling Group should not be configured with a Contact Registrant Table. The SBC does not support Fwd Reg. After Local Processing and a Contact Registrant Table in the same Signaling Group.

See also: Configuring the Sonus SBC 1000-2000 for Site Survivability.

Registrar

Specifies the Registrar Table attached to the Signaling Group for routing purpose and adding registration records.

Registrar TTL

Specifies the Time-To-Live (TTL) value for inbound registrations. Inbound registration values should be equal to or greater than this. This is configured in all registration scenarios.

Outbound Registrar TTL

Specifies the Time-To-Live (TTL) value for outbound registrations. This is configured only in the Forward modes of operation only.

SIP Server Table

Specifies the SIP Server Table to be used in the Signaling Group. The options in this field are derived from the configuration of SIP Server tables, see Creating and Modifying Entries in SIP Server Tables.

If a SIP Server Table is added which includes a server that has Stagger Registration enabled, Stagger Registration occurs. Also, if a SIP server table is removed which included a server that had Stagger Registration enabled, Stagger Un-registration occurs. For more information about Stagger Registration, see Creating and Modifying Entries in SIP Server Tables .

If you select an entry in the SIP Server table that is defined as DNS SRV, the Load Balancing field is not visible. See Load Balancing.

Load Balancing

This field applies only when the SIP Server Table selected from the drop down list is IP/FQDN based and does not contain SRV servers (load balancing is not required if the SIP Server Table which contains a SRV server). See SIP Server Table.

Specifies the load balancing method used with this Signaling Group. Used only in the SIP Basic Call Mode.

  • Round Robin: Each initial INVITE sent to the next server in the pool. As the basic algorithm, the scheduler selects a resource pointed to by a counter from a list, after which the counter is incremented and if the end is reached, returned to the beginning of the list. Round-robin selection has a positive characteristic of preventing starvation, as every resource will be eventually chosen by the scheduler.
  • Priority: The request goes to the server with highest priority.
  • First: The initial request goes to the first available server.

Channel Hunting

Specifies the method that Call Control uses to allocate SIP channels.

  • Standard: Specifies the first available low numbered channel.
  • Reverse Standard: Specifies last available high numbered channel.
  • Round Robin: Specifies channels based on next available from low numbered to high numbered.
  • Least Idle: Specifies that channels are chosen based on the least idle channel.
  • Most Idle: Specifies that channels are chosen based on the most idle channel.

Notify Lync CAC Profile

Enables whether any CAC Profile updates received locally are transmitted to the SIP servers listed in this Signaling Group Configuration. Valid entry: Enable (Default, updates received locally are transmitted to SIP servers), or Disable (updates received locally are not transmitted to SIP servers) .

Challenge Request

Indicates whether or not incoming request messages are challenged for security purposes. If this option is set to Enable, you must specify a realm and at least one entry in the Authorization Table.

  • True: All requests are challenged for realm, user, and password.
  • False: No request messages are challenged.

Outbound Proxy

Specifies the outbound proxy through which all SIP messages are sent. For in-depth configuration detail, see Outbound Proxy Configuration.

Outbound Proxy Port

Specifies the port number for the outbound proxy, if one is configured. The port number must be in the range 1024 through 65535.

No Channel Available Override

In the event of a No Channel/Circuit available release cause code, the specified cause code is sent to the relevant protocol module. For more information see the list of Cause Codes.

Call Setup Response Timer

Specifies the interval of time, in seconds, after a call is initiated that the Sonus SBC 1000/2000 waits for a call to connect before terminating the incoming call.

Media Information - Field Definitions

RTP Proxy Mode

Enables whether the Signaling Groups supports RTP Proxy mode. In RTP Proxy mode, the SBC will proxy or switch the media stream between endpoints in order to negotiate common media capabilities and handle unsupported/unknown audio codecs. The media flows through the SBC without requiring DSP resources. Default entry: Enable.

RTP DSP Mode

Enables whether the Signaling Group supports RTP DSP mode. In RTP DSP mode, the SBC uses DSP resources for media handling, but it does not facilitate the capabilities/features between endpoints that are not supported within the SBC (codec/capability mismatch). Default entry: Enable.

Media List ID

Specifies the Media List used by this Signaling Group.

Play Ring Back

Specifies how ringback is played on a channel.

The Play Ringback configuration functions with only 180 Ringing or ISDN Alert. The function is not executed for 183 w/SDP.

  • Auto: Configured for Auto, the Sonus SBC 1000/2000 operates in the nominal RFC 3960pattern
    • Sonus SBC 1000/2000 generates ringback until in-band media arrives.
    • Sonus SBC 1000/2000-generated ringback is discontinued in the presence of in-band ringback.
    • Additionally, any ALERT is sent with PI=8 regardless of whether or not a SDP was received on the SIP side. Doing so allows the Sonus SBC 1000/2000 to send in-band audio without signaling PROGRESS.

Click to see more information about this topic.

  • Always:Sonus SBC 1000/2000 provides ringback, ignoring any arriving in-band media.
    • For SIP-originated call legs, 180w/SDP will be sent to permit Sonus SBC 1000/2000 to provide in-band ringback via early media.
    • For ISDN-originated call legs, ALERT+PI will be sent along with Sonus SBC 1000/2000-inband ringing.

Click to see more information about this topic.

  • Never:Sonus SBC 1000/2000 does not provide ringback and cuts through ringback from the source when/if it arrives.
    • With NEVER, Sonus SBC 1000/2000 will send 180/ALERT to the originating call leg without SDP/PI as in this configuration Sonus SBC 1000/2000 will not supply inband ringback.

Click to see more information about this topic.

(info) Note: The Play Ring Back setting is activated only after the channel receives an ALERT or 180 Ringing. Issues with ringback and 183 Session Progress must be addressed using a Message Translation.
Click to see more information about Activating Play Ring Back.

Tone Table

Specifies the Tone Table used by this Signaling Group. Only visible if Always or Auto is specified for Play Ring Back.

Early 183

Specifies whether to send a SIP 183 response immediately after receiving an Invite message. The early 183 Session Progress with SDP provides the SRTP key that will be used to decrypt the transmit stream from Sonus SBC 1000/2000 to the SIP peer. This setting is used to prevent the peer device (eg. Mediation server) from staying in the Trying state. This setting is required for Lync 2010 interoperability.

Early 183 is applicable only when RTP DSP Mode is enabled as the media mode.

Music on Hold

The field enables Music on Hold at the SIP Signaling group level. Available options:

  • Enabled. Enables Music on Hold for the SIP Signaling Group.
  • Disabled. Disables Music on Hold for the SIP Signaling Group. Default entry.
  • Enables for 2-Way Hold Only. The SBC will not play Music on Hold if the other side sends 1-way hold (a=sendonly), and the SBC will play Music On Hold if the other side sends 2-way hold (a-inactive). This is mainly used if the other system's Music on Hold is preferred. If the SBC is not configured to play Music on hold at all, and the other side sends 2-way hold (a-inactive), then the SBC will not play any audio stream for MOH.

For detailed information about enabling Music On Hold as part of the Media configuration, see Configuring the Media System. For detailed information about uploading music files, see Uploading Music on Hold Files.

Mapping Tables

SIP To Q.850 Override Table

Specifies the SIP to Q.850 Override Table to be used for this Signaling Group.

Q.850 To SIP Override Table

Specifies the Q.850 To SIP Override Table to be used for this Signaling Group.

Pass-thru Peer SIP Response Code

The default value is Enabled. If you disable the pass-thru peer SIP response, then the mapping tables will be applied to SIP-SIP calls.

SIP IP Details - Field Definitions

NAT Traversal

Specifies whether or not the Signaling Group uses a third-party entity IP address inside SIP message to support network address translation (NAT). Only visible when NAT Traversal is set to Static NAT.

  • None: Specifies that network address translation is not used.
  • Static NAT: Specifies that network address translation is used.

Symmetric NAT (port forwarding) is the only supported NAT type. This NAT configuration type means that packets received on a specific NAT server port are always forwarded to the same Sonus SBC 1000/2000 port, for example, packets on the NAT public IP, port 5060 are forwarded to a private (Sonus SBC 1000/2000) IP, port 5060.

Application Layer IP

Specifies how the Signaling Group will select the local IP.

  • Auto: Means Sonus SBC 1000/2000 connects to the peer and queries the local IP which is used in SIP headers and SDP.
  • Bind: Binds to specified interface and uses that IP (1st/2nd) in headers and SDP.

NAT Public IP Address

Specifies the public IP of the NAT server visible from Internet. The NAT server's ports must be configured to allow SIP and RTP traffic, for example: port range 5060-5061 for SIP and 16000-17000 for RTP.

The IP address specified in this field must be publicly accessible.

Signaling/Media Source IP

Specifies the the logical port over which SIP session are conducted. Only visible when NAT Traversal is set to None

  • Auto: The node automatically selects the port over which the session is conducted.
  • Ethernet IP : Specifies the logical Ethernet port over which the session is conducted.

Signaling DSCP

Each SIP-SG is configurable with the DSCP value to be used for signaling. This allows for improved quality of service in real time applications, such as conferencing and conversations.. The settings take effect for both client and server modes of SIP. The default value of 40 is the most common value used in the VOIP networks for signaling packets. The configured value should be chosen according to the QoS policies of the IP network in which the signaling packets travel.

Valid entry range: 0 to 63 (inclusive). Default value: 40.

Listen Ports - Field Definitions

This section defines a listening port and protocol for the SIP Signaling Group

Port

Specifies the port to listen for SIP messages.

Protocol

Specifies the protocol with which this port can receive SIP messages.

TLS Profile

If TLS is selected this specifies the TLS Profile this port will use for secure SIP messages.

Federated IP/FQDN - Field Definitions

The Federated IP/FQDN feature acts as an access control by defining from which server a SIP Signaling Group will accept messages.

IP Address/FQDN

Specifies the IP Address or Fully Qualified Domain Name of a server from which the Sonus SBC 1000/2000 will accept SIP messages.

When an IP Address is specified the Netmask is mandatory.

When an FQDN is specified all the all IPs in that domain are added. If the Netmask is not specified 255.255.255.255 is assumed.

Federated IP Netmask

Specifies the network address mask to apply against the specified server address.

Message Manipulation

This option enables or disables the ability for the Sonus SBC 1000/2000 to manipulate SIP messages using previously configured Message Tables.

Select from the drop down list: Enable (enables the feature) or Disable (disables the feature).

Inbound Message Manipulation - Field Definitions

The rules in these tables are used to manipulate inbound SIP messages in the Signaling Group. The Signaling Group will support a maximum of 10 Message Rule Tools allowed in the Signaling Group (inbound direction).

Up. Moves the message table entry up in the list.The rules are applied in the order the tables are listed.

Down. Moves the message table entry down in the list.The rules are applied in the order the tables are listed.

Add. Displays a drop down list of available message tables. Select an entry and click Apply.

Remove. Removes the message table entry from the list.

Outbound Message Manipulation - Field Definitions

The rules in these tables are used to manipulate inbound SIP messages in the Signaling Group. The Signaling Group will support a maximum of 10 Message Rule Tools allowed n the Signaling Group (outbound direction).

Up. Moves the message table entry up in the list. The rules are applied in the order the tables are listed.

Down. Moves the message table entry down in the list.The rules are applied in the order the tables are listed.

Add. Displays a drop down list of available Message Tables. Select an entry and click Apply.

Remove. Removes the message table entry from the list.

Qoe Reporting - Field Definitions

Enable QoE Reporting

Enables and disables the QoE reporting features.

Send QoE data to Headquarters

If enabled, a notification is transmitted to the headquarters gateway at the termination of each call.

HQ Gateway Address

The IPv4 address of the headquarters gateway.

HQ Gateway Port

The reporting port on the headquarters gateway specified by the HQ Gateway Address attribute.