Configuring SIP Signaling


To be able to make a call using the SIP protocol, the IMG must have the SIP Signaling object created and configured. Follow steps below to configure SIP signaling as well as a few options.


Configure SIP Signaling

  1. Right-click on the Physical IMG and select New Signaling. A Signaling Object is created. Under this object pane multiple Signaling Protocols can be configured. There is no data entered in this object pane.

  2. Right-click Signaling object and select New SIP.


  3. The SIP Signaling pane appears. See Below.

ClientView Pane 10.5.0



ClientView Pane 10.5.1




SIP Signaling IP Address:

This field has a drop down menu displaying all the Interfaces configured under the Network Interfaces object. Select the correct interface that the SIP signaling will be on.


Local SIP Port:

This defaults to Port 5060 which is the default port for TCP and UDP. Thsi can be changed by clicking in the field and entering a different port number.


SIP Compact Header:

Select from a drop down where the Compact Header Feature can be enabled or disabled. If enabled the SIP message will send an abbreviated message according to RFC 3261. A wireless application where bandwidth needs to be limited is a good reason for using compact headers.


Default Transport Type:

Select from drop down menu UDP, TCP, or TLS. IMG Defaults to UDP. TLS is supported in software 10.5.1 +. If TLS is selected, this opens up a Secure Profile field and a Default Secure Profiles Field. See screen capture below.




Default SIP Username (AOR):

This field defaults to:

DIALOGIC-IMG0 - Software 10.5.1+

To change username, click in the 'Username' field and enter a different value. This field is commonly referred to as Public Address.


Default SIP Authentication Username:

Username and Password used for authentication to guard against hijacking.


Enable SIP-T:

Select from drop down menu whether SIP-T will be used. See Configuring SIP-T


Privacy Support:

To enable Privacy for the entire GCEMS, set the Privacy Support field for the method supported by the proxy. All calls will be handled according to this setting, regardless of other SIP Privacy settings on an External Gateway or ISDN/ISUP Group. See Configuring SIP Privacy.


Remote IMG's SIP Profile:

Select from a drop down menu. Menu will display all SGP profiles created under the Signaling Object. See "Configure SIP Profile" heading below


Secure Profile:

If TLS is selected in the Default Transport Type field then the Secure Profile field will get highlighted. This is a list of all the secure profiles created and is configured if the IMG will be used as an external gateway. Select one of the profiles from the drop down list.


Default Secure Profile:

If a SIP call comes in over the Secure Profile Port but the external gateway sending the call is not using TLS security the call will fail. To avoid this from happening you can select a Secure Profile from the Default Secure Profile list. Once a Secure Profile is selected then if an external gateway sends a call through the Secure Profile Port (Default 5061) the call will not get rejected.



The FQDN to be inserted in outgoing SIP messages when FDQN is enabled in the SIP Profile. See Fully Qualified Domain Name Support for more information.



  1. Once SIP signaling pane is completed Click on the link below to bring you back to list of steps to accomplish.




Configure SIP Profile (Optional)

A SIP Profile allows you to easily assign a number of SIP features to a Physical IMG. First create a SIP Profile. Once the profile is created you can assign it to a gateway in the External Gateway pane.

A SIP Profile can also be assigned to a SIP Signaling object, which will indicate to another IMG how to treat a call going to or coming from the IMG.

  1. Right-click Dialogic IMG EMS and select New SIP Profile

  2. Enable desired features and enter values in fields where required. See the SIP Profile pane reference for details.

  3. Once created you can assign the profile to an external gateway or to a SIP Signaling object.