OCS R2 and CUCM6.1 integration, Caller ID and name when using Unity call handler
We just have done MS OCS R2 and Cisco CUCM6.1 integration and most of features work as expected. As there is no DID for each user, external incoming calls are transferred to internal extension using AA in Unity 5.01 then ring on both of Cisco phone and Office Communicator (CUCM Unified Mobility feature).
Now the problem is that the caller ID displays on Office Communicator is the number of Unity voicemail ports, but not the orignal calling number.
When I check SIP messages on MS mediation server, it shows the number of Unity voicemail ports is sent to OCS.
The caller name and caller ID on Cisco phone are correct.
Call main number --> Cisco 2851, PRI --> CUCM6.1 --> Unity Call Handler --> CUCM6.1 --> ring Cisco phone
SIP trunk --> OCS Mediation --> OCS
Is there anyway to configure CUCM to send orignal calling number over SIP trunk to OCS?
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...