09-05-2012 04:59 PM - edited 03-17-2019 11:44 PM
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.
Any idea where to start looking?
09-05-2012 10:04 PM
Hi Nick
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.
/Magnus
09-06-2012 04:22 PM
Thanks Magnus - I guess it's Wireshark time.
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