Access to Federated Domains through Intra-Domain Federation
We are looking at having Lync and Jabber running in unison. Currently I have intra-Domain Federation working and playing nicely. I am now looking to extend the capability of the federation by enabling Jabber users to access Lync federated SIP domains via the Lync Edge. But also I would like to allow Lync users to access XMPP federated domains via the CUCM IM&P Server.
Currently I have CUCM + CUCM IM&P 9.1 Federated with Lync 2013.
I added an addition static route on the Lync 2013 Server for cisco.com and pointed it to the trusted application pool of the routing presence nodes.
I can see the SIP SUBSCRIBE messages getting to the IM&P node. It then procedes to attempt a connection to cisco.com via SIP TLS, instead of translating to to XMPP like I hoped it would. This is probably the expected behaviour of the SIP proxy on the IM&P server.
So essentially the question is
Is there any way known to force it to translate the sip SIMPLE to xmpp for domains that don't exist inside the enterprise.
Unfortunately I found no way of getting this to work. So if you are in a situation where you have Lync and Jabber on the same SIP domain, there is no way I found to get Lync to contact XMPP federated partners through CUCM IM&P.
This was a little while ago, and I have not attempted it since. So it may work with newer versions, but I wouldn't bet money on it.
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 ...