Create a SIP Signaling Group:
From the Create Signaling Group drop down box, select SIP Signaling Group.
Click '' on the WebUI screen to configure additional items
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.
Click the field-specific () icon next to a specific object. In the example below, the Call Routing Table field supports object within object configurability:
At the Create window, enter a description for the newly created object.
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).
Field definitions for the Create SIP Signaling Group window are listed by feature.
Quick Links - Configuration Options by Feature
Configure a SIP Signaling Group:
From the Create Signaling Group drop-down box, select SIP Signaling Group.
|Signaling Group Type||Supported in SBC Edge||Supported in SBC SWe LIte|
Configure the field options. Field definitions below are listed in SIP Signaling Group feature groups. See Quick Links - Configuration Options by Feature.
Video/Application Stream Mode
If the selected Outbound NAT Traversal is Static NAT, you must enter the field NAT Public IP (Signaling/Media) appears.
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.
This section defines a listening port and protocol for the SIP Signaling Group
Federated IP addresses and FQDNs specified in a SIP Signaling Group are whitelisted.
The Federated IP/FQDN feature acts as an access control by defining from which server a SIP Signaling Group will accept messages.