We currently run an OCS 2007 enterprise environment integrated via Direct SIP to a CUCM 7.0.2 environment. Everything is working fine with this integration, calls between Cisco and MOC devices all works well.
Basically we require users to be able to receive calls in both their Cisco hard phones (7940) and their MOC clients on a single extension number.
At this stage calling from a MOC client to a Cisco device and viceversa as i said is working fine, the issue is to get the two to ring at the same time.
In a nut shell i have configured a cisco 7940 device with a directory number in this form, \+612XXXX4111 (e164 format) user id, remote destination, remote destination profile, a route pattern for 612XXXX4111 via the SIP trunk to OCS, in call manager as indicated in the guide. However when ringing the number internally, the MOC client rings but the Cisco device doesn't. I tried isolating the directory number and Cisco device for testing, by changing the directory number to 612xxxx4111, without the '+' and removing the route pattern temporarily; then the cisco device rang. So it seems that adding the plus in the directory number configuration field is the problem. When the '+' is in the directory number I can make calls from the Cisco device, the calling number as shown in the called device logs is 612xxxx4111 but when trying to dial it from this device it does not work. I'm not sure if someone has been trying this setup. I will really appreciate some help with this.... Also on the guide I'm not sure why two different numbers are used for the directory numbers and the remote destination, when the purpose of forking is to ring the same extension number.
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: email@example.com 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 ...