Source record · tier 2 current vendor documentation
Cisco Unified Communications Manager SIP Integration Guide for Cisco Unity Connection Release 15 - Setting Up a Cisco Unified Communications Manager SIP Trunk Integration
- Publisher
- Cisco Systems
- URL
- https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/15/integration/cucm_sip/b_15cucintcucmsip/b_14cucintcucmsip_chapter_010.html
- Published
- 2024-10-01
- Updated
- unknown
- Accessed
- 2026-09-25
- HTTP status
- 200
- License
- Cisco documentation terms of use; no-redistribution; short excerpts and locators only
Source notes citing this source
- Setting the Unified CM clusterwide service parameter Multiple Tenant MWI Modes (Cisco CallManager service, Feature - General) to True makes Unified CM apply configured translation patterns to convert voicemail extensions into directory numbers when turning MWIs on or off. in context
- On a Unity Connection voice messaging port, the Send MWI Requests check box designates that port for turning MWIs on and off. in context
- The same Unity Connection SIP trunk security profile must also have Accept Out-of-Dialog REFER and Accept Replaces Header checked. in context
- For a Unified CM SIP trunk integration with Unity Connection, the SIP trunk security profile used by the Unity Connection trunk must have Accept Unsolicited Notification checked. in context
- Unity Connection SIP-trunk MWI appears to depend on Unified CM accepting unsolicited SIP NOTIFY on the trunk, so an unchecked Accept Unsolicited Notification box on the Unity Connection trunk's security profile is a likely cause of SIP-integrated MWIs failing to change. inferred in context
- Each Unity Connection voice messaging port has settings for Enabled, Answer Calls, Perform Message Notification, Send MWI Requests and Allow TRAP Connections. in context
- In Unity Connection Administration, the port group is added from Telephony Integrations > Phone System via the Add Port Group related link, created from the SIP or SCCP port group template. in context
- In a Unity Connection cluster, each port is assigned to a specific server, and Cisco says to assign an equal number of answering and dial-out ports to the Unity Connection servers. in context
- When adding ports in Unity Connection, Number of Ports is the total for all Unity Connection servers in the cluster. in context
- Secondary Unified CM servers are added to the port group from the Port Group Basics Edit > Servers page, ordered with the lowest number as primary, and the port group is reset afterwards. in context
- The clusterwide service parameter Multiple Tenant MWI Modes is set to True only when multiple-tenant MWI notification is used, and changing it requires restarting Cisco Unified CM. in context
- The SIP trunk Destination Address is the Unity Connection server IP address, and Cisco recommends accepting the default destination port 5060. in context
- On the SIP trunk to Unity Connection, Redirecting Diversion Header Delivery is checked for both Inbound and Outbound. in context
- With a Unity Connection cluster on SIP, the voice mail pilot route pattern should target the route list rather than a single trunk, so calls reach the second server when the first is unavailable. inferred in context
- A SIP trunk integration needs no MWI on/off directory numbers in Unified CM; MWI requests arrive over the trunk as unsolicited notifications that the trunk security profile must accept. inferred in context
- Cisco Unified CM Music on Hold is not available during supervised transfers for the Cisco Unified CM SIP trunk integration. in context
- The SIP trunk integration uses a SIP profile created by copying an existing profile under Device > Device Settings > SIP Profile, with Enable ANAT checked only for IPv6 or dual-stack. in context
- On the SIP trunk, the inbound Calling Search Space, Rerouting Calling Search Space and Out-of-Dialog Refer Calling Search Space are each set to a calling search space that contains the user phones. in context
- When Unity Connection is a cluster, the SIP trunks to its servers are placed in a route group with the Top Down distribution algorithm, with the subscriber server's trunk listed first. in context
- When Unity Connection is a cluster, a route list containing the SIP trunk route group is created, and the route list is reset after it is saved. in context
- For the SIP trunk integration, a route pattern equal to the voice mail pilot number is created under Call Routing > Route/Hunt > Route Pattern and pointed at the Unity Connection SIP trunk. in context
- For a SIP trunk integration, create a SIP trunk security profile under System > Security > SIP Trunk Security Profile with Accept Out-of-Dialog REFER, Accept Unsolicited Notification and Accept Replaces Header checked. in context
- For the SIP trunk integration, the voice mail pilot number (Advanced Features > Voice Mail > Voice Mail Pilot) must match the route pattern, uses a calling search space containing the user phones and the pilot partition, and is made the system default. in context
- A voice mail profile (Advanced Features > Voice Mail > Voice Mail Profile) selects the voice mail pilot, leaves Voice Mail Box Mask blank unless multitenant services are enabled, and is made the system default. in context
Cite this source record
APA
WarmTransfer. (2024, October 1). Cisco Unified Communications Manager SIP Integration Guide for Cisco Unity Connection Release 15 - Setting Up a Cisco Unified Communications Manager SIP Trunk Integration. WarmTransfer. https://warmtransfer.net/knowledge/sources/cisco-cuc15-cucm-sip-integration-setup
BibTeX
@misc{warmtransfer-cisco-cuc15-cucm-sip-integration-setup,
title = {Cisco Unified Communications Manager SIP Integration Guide for Cisco Unity Connection Release 15 - Setting Up a Cisco Unified Communications Manager SIP Trunk Integration},
author = {{WarmTransfer}},
year = {2024},
url = {https://warmtransfer.net/knowledge/sources/cisco-cuc15-cucm-sip-integration-setup},
note = {Cisco Systems, accessed 2026-09-25}
}