08-25-2016 01:07 AM - edited 03-17-2019 06:19 PM
Hi,
I have Jabber for Windows v11.7.0 Build 42920 in phone mode connected to CUCM v10.5.2.13901-2. UC services on CUCM are created for CTI, directory and MeetingPlace. For MeetingPlace service, protocol selected is HTTP and port 80.
However, in Jabber client, connection status for Meetings is: "Last connection not successful". Adress is correct (configured in UC services), but protocol shows HTTPS instead of configured HTTP. In traffic capture from my PC to MeetingPlace server, I see only HTTPS requests, but on MeetingPlace HTTPS is not enabled so this cannot work. Why is Jabber ignoring protocol and port settings defined in UC services on CUCM?
Is this some bug in Jabber or CUCM...or there could be other issue somewhere?
Thanks,
S.
Solved! Go to Solution.
08-25-2016 04:50 AM
This is because jabber only support Cisco Webex meeting servers. It won't support other Meeting place server even it has been listed in Service profile. Refer the below release notes link where it has mentioned the list of on-premises server supported by jabber.
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/11_7/jabw_b_release-notes-ciscojabberforwindows-117.html
Earlier version of jabber have same behavior.
I hope this helps.
08-25-2016 04:24 AM
If i look at the jabber 11.7 deployment guide , it always tell to configure port as HTTPS not HTTP. In other words it means HTTP is not supported. Refer the below 2 guides.
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/11_7/cjab_b_on-premises-deployment-for-cisco-jabber-117/cjab_b_on-premises-deployment-for-cisco-jabber-117_chapter_0110.html
refer the diagram in below link.
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/11_7/cjab_b_planning-guide-jabber-117/cjab_b_planning-guide-jabber-117_chapter_010.html
08-25-2016 04:34 AM
That is true regarding that documentation, but in same documentation there is no any word about MeetingPlace standard or express....this documentation is for WebEx only.
But, why is in CUCM allowed to select HTTP and custom port if this is actually not used at all?
Is there maybe any lower version of Jabber client that supports HTTP for MeetingPlace?
08-25-2016 04:50 AM
This is because jabber only support Cisco Webex meeting servers. It won't support other Meeting place server even it has been listed in Service profile. Refer the below release notes link where it has mentioned the list of on-premises server supported by jabber.
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/11_7/jabw_b_release-notes-ciscojabberforwindows-117.html
Earlier version of jabber have same behavior.
I hope this helps.
08-25-2016 04:55 AM
OK, thanks!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide