CUP and Lync will not exchange full presence state for the same user. You can get on/off-hook state of the phone replicated across to Lync through the CSTA in CUP. Independant of this, a remote destination will show Remote in Use state which counts as off-hook to CUP and by extension Lync.
To my knowledge you're not supposed to mix these two options together. In every PowerPoint that I have seen it has been an OR statement. You can have SIP forking [mobile connect] OR remote call control.
Also, begining in CUP 8.6 you can do intradomain federation that allows you to have your user population split between products. The key here is the user must be on one platform or the other, not both.
Im integration the CUCM <-> CUPS <-> LYNC. they have now a SIP trunk between the LYNC and CUCM and using for do a calls from LYNC. So is mean I have to unconfigure this and then configure the RCC?.
Also I need to configure presence task. the important task is that BOSS can see status of the EMPLOYES but EMPLOYES can not see the status of the BOSS. this is possible to do?.
Also do you have the implementation between CUCM <-> CUPS version 8.5?
As I undertood the presence with RCC is just on-hook and off-hook?. So mean the client bought the PResence Server CUPS just for see just this two states!.
Finally The conectivity beetween CUCM and CUPS is using trunk SIP. And Conectivity between CUPS and LYNK is using RCC (just CTI gateway, not TRUNK SIP). And there isnt connectivity between CUCM <-> CUPS.
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...
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 discusses the bas...