Lync 2013 as a softphone client identical to my 9971 phone?
Customer is interested in having Lync 2013 integrated with CallManager 10.0.1. They want to use Lync client for either Desk Phone Control or Softphone Control and be identical extension to what the Cisco phone has.
Customer wants the exact same extension 4444 on Lync and on his 9971 phone. He can answer on either device, etc.
George that document has different extensions and is just a SIP Route Pattern to OCS/Lync. It doesn't have Dual Forking or the same extensions on both sides, etc. It won't meet the customer's requirements.
Thats correct, the way you do it is using Single Number reach. You give 9971 extension 1111, create a single number reach destination of 21111 and there is a route pattern of 2XXXX to Lync/OCS. On the SIP trunk, you strip off 2 and only send XXXX and then configure Lync's extension with XXXX (in this case 1111) and any call to 1111 will ring both Lync and 9971. Calls to Lync will be completed by extending the call using SNR (This is outlined in the "Configure Mobility" section).
SNR won't provide the high level of intelligence between the two the customer would like to see. He would like to see a solution where Lync and the 9971 are tightly coupled, sort of 1 and the same phone. Similar to a shared line. I don't see a solution for him. Perhaps a 3rd party solution might be able to help.
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...