It should work fine between CUPS and OCS through the SIP trunk. You need to make sure you have the correct Route Patterns in place for the SIP trunks to work correctly. On the OCS side, you need to configure Enterprise (I think it's called this) dialing rules to push patterns through to the SIP endpoint. (CUPS or CUCM) Also vice version... how will an Cisco IP phone "know" where OCS is unless you have a SIP trunk and Route Pattern.
CUPS is only used for OCS to use Remote Call Control for the Cisco IP phones and IM messages. If you want to make calls between the products, you will need to use a SIP trunk between the Mediation Server and a Cisco gateway or CUCM for this work. It's a little flakey and takes quite a bit of tweaking.
The problem with Mediation is that they use the "+" e164 number. So you have to strip the + out of the number when it sends it over to CUCM or not use this format at all on the OCS side. You can use voice translations at the voice gateway when it receives the SIP invite from the Mediation server. After after the "+" is stripped, send it to CUCM via h323 or SIP. But you will need to have a trunk configured for CUCM back to the gateway (for return traffic)
There should be more information coming out in the 6 months of a direct connect to CUCM from Mediation. But for now, you can go through the Voice Gateway, then to CUCM. There are some other posts on the configurations and also at the Microsoft forums.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...