Jabber 9.2 Failback from TCP 5222 to TCP 443

[s.lehmann]

Hi all,

if i check the deployment guide for J4W i see that it supports failback to https, if XMPP (TCP 5222) is not available.

http://www.cisco.com/en/US/docs/voice_ip_comm/jabber/Windows/9_2/JABW_BK_C9731738_00_jabber-windows-install-config_chapter_010.html#JABW_RF_P3E0FDE4_00

We have noticed that the feature is not available in our cloud based deployment.

Do i have to enable eny specific setting in Webex Connect Admin?

Any other experiences?

Steffen

[coflaher]

This only occurs if port 5222 is blocked. Is this blocked in your environment?

[s.lehmann]

One of us does not understand the feature.
Of course is 5222 blocked, because I want to see jabber doing a fail back to https.

Do I misunderstand the fail back?

Sent from Cisco Technical Support iPad App

[coflaher]

Yes, if port 5222 is blocked, its will failover to BOSH 443.

This is not recommended though and port 5222 should be opened/