Source record · tier 2 current vendor documentation
System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Trunks
- Publisher
- Cisco
- URL
- https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_01000.html
- Published
- unknown
- Updated
- unknown
- Accessed
- 2026-09-21
- HTTP status
- 200
- License
- Cisco.com terms and conditions; no-redistribution; short excerpts and locators only
Source notes citing this source
- A Unified CM SIP trunk can have up to 16 destination addresses (IPv4, IPv6 or FQDN) or a single DNS SRV record. in context
- If no SIP trunk security profile is assigned to a Unified CM SIP trunk, a nonsecure profile is assigned. in context
- A device pool must already be configured before a Unified CM SIP trunk is configured. in context
- A secure SIP trunk cannot be deployed while Unified CM is running in the 90-day evaluation period. in context
- When multiple non-secure SIP trunks with different listening ports point to the same destination, they may use the wrong port in a mid-call INVITE and the call drops. in context
- The SIP trunk's Run on All Active Unified CM Nodes checkbox enables the trunk on all cluster nodes. in context
- In Cisco Unified CM Administration, SIP trunk security profiles are configured under System > Security > SIP Trunk Security Profile. in context
- In Cisco Unified CM Administration, SIP profiles are configured under Device > Device Settings > SIP Profile. in context
- The Unified CM SIP trunk configuration has an SRTP Allowed checkbox, checked in the documented procedure. in context
- The Unified CM 15 SIP trunk configuration task flow is: configure SIP profiles, then configure a SIP trunk security profile, then configure SIP trunks. in context
- For a TLS-encrypted trunk, the SIP trunk security profile uses Device Security Mode Encrypted, TLS for both incoming and outgoing transport type, and an incoming port whose TLS default is 5061. in context
- A SIP trunk is created in Cisco Unified CM Administration under Device > Trunk by clicking Add New and choosing SIP Trunk as the Trunk Type. in context
- The TLS SIP trunk security profile procedure includes entering an X.509 Subject Name used to authenticate the peer's certificate. in context
- In Unified CM 15, a SIP trunk accepts up to 16 destination addresses. in context
- The Unified CM 15 trunk chapter lists a Session Management Edition among the destinations a SIP trunk can connect to, alongside gateways, proxies, applications and remote clusters. in context
- The Release 15 trunk task flow puts configuring SIP profiles first, then the SIP trunk security profile, then the SIP trunks themselves. in context
- If no SIP trunk security profile is assigned to a SIP trunk, Unified CM assigns a nonsecure profile by default. in context
- From Unified CM Release 15 onward, H.323 Gatekeeper Control options are no longer available. in context
- Inference: the documented LGW coexistence design (two non-secure trunks with different listening ports to one LGW at 5060) matches the conditions of the Release 15 restriction on mid-call INVITE port use. Whether that design is exposed to the call-drop behaviour is not established by any source retrieved. inferred in context
- A Unified CM SIP trunk can have up to 16 destination addresses, given as IPv4 or IPv6 addresses, fully qualified domain names or a single DNS SRV record. in context
- Unified CM documents a restriction: when several non-secure SIP trunks with different listening ports point to the same destination or port, they may use the wrong port in a mid-call INVITE and the call drops. in context
- Unified CM SIP trunks connect Unified CM to external devices such as SIP gateways, SIP proxy servers, UC applications, conference bridges, remote clusters or a Session Management Edition. in context
- The SIP trunk's Run on All Active Unified CM Nodes check box enables the trunk on all cluster nodes. in context
- The SIP Trunk Service Type options are None (Default), Call Control Discovery, Extension Mobility Cross Cluster, Cisco Intercompany Media Engine and IP Multimedia System Service Control. in context
- A SIP trunk that has a security profile assigned takes on that profile's settings. in context
- Cisco says that if applications using a Unified CM SIP trunk have SIP interoperability issues, a default SIP Normalization or Transparency script may be needed, and a SIP profile can carry an SDP transparency profile. in context
- If no SIP trunk security profile is assigned to a SIP trunk, Unified CM assigns a nonsecure profile by default. in context
- Cisco's Unified CM Release 15 SIP trunk task flow is: configure SIP profiles, configure a SIP trunk security profile, then configure the SIP trunk with those profiles and its destination addresses. in context
- A Cisco Unified Communications Manager SIP trunk can be assigned up to 16 different destination addresses using IPv4 or IPv6 addressing, fully qualified domain names, or a single DNS SRV record. in context
- The Cisco Unified Communications Manager trunk configuration task flow is to configure a SIP profile, then a SIP trunk security profile carrying settings such as TLS signalling encryption and digest authentication, then the SIP trunk that applies both profiles. in context
- The Unified CM SIP trunk task flow is: configure SIP profiles, then the SIP trunk security profile, then the SIP trunk. in context
- Encrypted media over a Unified CM SIP trunk requires the SRTP Allowed check box on the trunk. in context
- A Unified CM SIP trunk accepts up to 16 destination addresses (IPv4, IPv6 or FQDN) or a single DNS SRV record. in context
- An encrypted Unified CM SIP trunk uses a SIP trunk security profile with Device Security Mode set to Encrypted and TLS as the incoming and outgoing transport; the default TLS incoming port is 5061. in context
- Cisco advises applying a default SIP normalization or transparency script to a Unified CM SIP trunk or SIP profile when there are SIP interoperability issues with the far end. in context
- Checking Run on All Active Unified CM Nodes enables a SIP trunk on all cluster nodes. in context
- Unified CM uses SIP trunks to connect to external devices such as SIP gateways when SIP is the call control signaling protocol. in context
- A Unified CM SIP trunk can have up to 16 destination addresses using IPv4, IPv6 or FQDNs, or a single DNS SRV record. in context
- A Unified CM SIP trunk is created under Device > Trunk > Add New with Trunk Type SIP Trunk, after which the administrator sets destinations, the SIP trunk security profile and the SIP profile and saves. in context
- The Unified CM SIP trunk task flow is to configure a SIP profile, then a SIP trunk security profile, then the SIP trunk with both profiles applied. in context
- Unified CM SIP trunk setup is three tasks in order: configure SIP profiles, configure a SIP trunk security profile, then configure SIP trunks. A trunk can have up to 16 destination addresses or a single DNS SRV record. in context
- For an encrypted Unified CM SIP trunk, the security profile sets incoming and outgoing transport to TLS (default incoming port 5061), and the trunk's SRTP Allowed check box allows encrypted media. in context
- Cisco advises that SIP interoperability issues with applications using a Unified CM trunk may require one of the default SIP normalization or transparency scripts. in context
- Checking Run on All Active Unified CM Nodes enables a SIP trunk on all cluster nodes. in context
- Unified CM uses SIP trunks to connect to external devices such as SIP gateways, SIP proxy servers, UC applications, remote clusters or Session Management Edition. in context
- A Unified CM SIP trunk can have up to 16 destination addresses using IPv4, IPv6 or FQDNs, or a single DNS SRV record with the Destination Address is an SRV box checked. in context
- The Unified CM 15 SIP trunk task flow is: configure SIP profiles, then a SIP trunk security profile, then the SIP trunk with those profiles assigned. in context
- A Unified CM SIP trunk can have up to 16 destination addresses given as IPv4 or IPv6 addresses, FQDNs, or a single DNS SRV record. in context
- Unified CM SIP trunk setup runs: configure a SIP profile, configure a SIP trunk security profile, then configure the SIP trunk applying both. in context
- Unified CM uses SIP trunks to connect to external devices such as SIP gateways, SIP proxy servers, UC applications, remote clusters or Session Management Edition. in context
- In Unified CM Release 15 an administrator marks a SIP trunk destination as SRV by checking 'Destination Address is an SRV' in the trunk configuration. in context
- In Unified CM Release 15 a SIP trunk can have up to 16 destination addresses as IPv4 or IPv6 addresses or FQDNs, or a single DNS SRV record. in context
Cite this source record
APA
WarmTransfer. (2026, September 21). System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Trunks. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-cucm-sysconfig-15-trunks
BibTeX
@misc{warmtransfer-cisco-cucm-sysconfig-15-trunks,
title = {System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Trunks},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/sources/cisco-cucm-sysconfig-15-trunks},
note = {Cisco, accessed 2026-09-21}
}