Note: In case of Unity Connection cluster, you can add a separate Route Group for the second SIP Trunk created. Select the SIP Trunk created in Step 2 and click on Add to Route Group.
Add a new Route Group and give it an appropriate name. Navigate to Call Routing > Route/Hunt > Route Group. For SIP Profile, select the Standard SIP Profile from the drop down. This CSS comes into picture for calls transferred back to the CUCM from the Unity Connection and must have access to the user phones. Choose the new Security Profile created in Step 1. Select the SIP trunk security profile from the drop down menu.
Each SIP trunk points to one Unity Connection server. Note: For a Unity Connection cluster (Publisher and Subscriber), create 2 SIP trunks. In the Destination Address field, enter the IP address of the Unity Connection server to which the CUCM connects. For the Outbound Call settings, check the box Redirecting Diversion Header Delivery – Outbound. Also, check the box Redirecting Diversion Header Delivery-Inbound. For the Inbound Calls settings, select the appropriate CSS which has access to the phones. Provide a name for the Trunk and assign an appropriate Device Pool. In order to create a SIP trunk, navigate to Device > Trunk and select Add New. On the new profile, check these options Accept out-of-dialog refer, Accept unsolicited notification and Accept replaces header. The default profile is Non-Secure SIP Trunk Profile. On CUCM Admin page, navigate to System > Security > SIP Trunk Security Profile. If your network is live, ensure that you understand the potential impact of any command. All of the devices used in this document started with a cleared (default) configuration. The information in this document was created from the devices in a specific lab environment.
#ONSIP WITH CUCM SOFTWARE#
The information in this document is based on these software and hardware versions: Prerequisites RequirementsĬisco recommends that you have knowledge of these topics: In this example, the SIP integration is non-secure. This document describes the procedure to integrate Cisco Unified Communication Manager (CUCM) with Cisco Unity Connection (CUC) with the use of Session Initiation Protocol (SIP).
0 kommentar(er)
