I'm testing Jabber amongst a few users at the moment - I'm noticing that all users seem to randomly de-register, sometimes in the middle of a call. It then says "waiting for next login attempt" and eventually re-registers. These are all local registrations with uncontested 1Gbps connections back to VCS control, with no packet loss at all when in a call so I don't think it's a network issue.
In theory this can be a network issue (routing issue) and it has been seen before. Jabber can log in fine but when the registration expires and the jabber client tries to re-register it does not receive a 200 OK from the VCS or any response at all due to whatever netowork issue at hand which forces the Jabber client to de-register since the registration has timed out.
So I think the first place to start looking is on the wire taking a packet capture and analyze the re-registration. It might be a good idea to get help from TAC as well on this.
The issue might be rooted elsewhere but this scenario I am mentioning has been seen before.
hi Team, we are planning to deploy Multi-Factor Authentication for Jabber. The main requirement is to use MFA over internet (MRA).Is it possible to deploy MFA just for MRA and don't touch impact any on-prem existing setup?Can someone please guide on ...
Looking to expand your professional network? Interested in gaining an edge with exclusive technology insights? Engage with Cisco experts, share feedback on products and connect with peers from across the globe. Cisco Champion 2021 applications are open fo...
UCCX does not natively protect HTTP Triggers.
I wanted to come up with a solution to handle HTTP cookie based authentication.
There is a zip file for this project attached to this article. It was written on UCCX 12.5...
CUCM can backup the manually or have sehchduler to backup the configuration and historical reports from the server diester recovery systemStep 1. Navigate to CUCM > Disaster Recovery System > Backup > Manual Backup as shown in the...