SIP Trunk Overview
If you are deploying SIP for call control signaling, configure SIP trunks that connect Cisco Unified Communications Manager to external devices such as SIP gateways, SIP Proxy Servers, Unified Communications applications, remote clusters, or a Session Management Edition.
Within Cisco Unified CM Administration, the SIP Trunk Configuration window contains the SIP signaling configurations that Cisco Unified Communications Manager uses to manage SIP calls.
You can assign up to 16 different destination addresses for a SIP trunk, using IPv4 or IPv6 addressing, fully qualified domain names, or you can use a single DNS SRV record.
You can configure the following features on SIP trunks:
-
Line and Name Identification Services
-
Delayed Offer, Early Offer and Best Effort Early Offer
-
Signaling encryption and authentication
-
Media encryption with SRTP
-
IPv6 dual stack support
-
Video
-
Presentation sharing with BFCP
-
Far end camera control
-
DTMF relay
-
Calling party normalization
-
URI dialing
-
Q.SIG support
-
T.38 fax support
-
SIP OPTIONS
-
Choice of DTMF signaling
![]() Note |
When Q.SIG is enabled in Small-scale IP telephony (SIPT) from Cluster A to Cluster B, and if "INVITE" is received with anonymous or any text, then the Cisco Unified Communications Manager does not encode it to Q.SIG data. When you decode the same in the leaf cluster, it displays empty and empty number is forwarded. |
![]() Note |
When Q.SIG is enabled, URI dialing does not respond as expected and if Q.SIG is disabled, then the Cisco Call Back does not respond between two clusters. |
IPv6 Dual Stack Support
![]() Note |
You can also configure IPv6 clusterwide via a clusterwide service parameter. However, the Common Device Configuration setting overrides the clusterwide defaults. |
Secure SIP Trunks
You can also configure your trunks with security such as digest authentication and signaling and media encryption by configuring a SIP trunk security profile that includes security features such as digest authentication and TLS signaling and associate that profile to the SIP trunks in your network. For the trunk to allow encrypted o encrypt call media, you must also configure the trunk to allow SRTP media.
SIP Trunk Security Profile Overview
You must assign a SIP trunk security profile to each SIP trunk in your network. By default, Cisco Unified Communications Manager applies a predefined, nonsecure SIP trunk security profile for autoregistration to all SIP trunks.
The SIP trunk security profile allows you to configure security settings such as digest authentication and TLS signaling encryption for the SIP trunks in your network. When you configure a SIP trunk security profile, and then assign that profile to a SIP trunk, the security settings from the profile get applied to the trunk.
You can configure multiple SIP trunk security profiles to cover the different security requirements that you have for different sets of SIP trunks in your network.
![]() Note |
To configure your network with security, you must also set up a CTL client and configure IPSec. For details, see the Security Guide for Cisco Unified Communications Manager. |