Jabber IM and Presence (CUCM) and Video endpoints (VCS) Integration
We are integrating Cisco Jabber (IM &Presence) via CUCM to video endpoints registered as SIP to VCS Control.
To give you an overview with the existing deployment:
1. IP phones and Jabber (IM & Presence) registered on CUCM can make calls with each other without any issue.
2. Endpoints and MCU registered on VCS Control can make calls with each other without issue.
3. IP phones registered on CUCM can make calls to endpoints/MCU registered on VCS Control and vise versa via SIP trunk without any issue.
4. Jabber (IM & Presence) registered on CUCM cannot make successful call to endpoints/MCU registered on VCS Control and vise versa via SIP trunk.
- Item #4 is the current issue we are resolving. When a Jabber (IM & Presence) initiates a call to a VCS endpoint, the endpoint will ring then it disconnects immediately. Same issue when VCS endpoint will initiate call to Jabber (IM & Presence).
Endpoints used during test calls:
firstname.lastname@example.org - Cisco MCU 4510 (registered on VCS)
email@example.com - Cisco IP Communicator (registered on CUCM)
firstname.lastname@example.org - Cisco Jabber (IM & Presence) (registered on CUCM)
4901 -----> 4012 - OK
4901 -----> 4016 - Not OK
Please see attached debug logs from VCS side for comparison between call from 4901 -----> 4012 and 4901 ------> 4016.
Thank you in advance for your inputs to resolve this issue.
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 ...