Jabber Client unable to login

[dc-csa-chn]

We see the below logs in the AUdit log of the Jabber client.

What does this mean..?

Provisioned Successfully by VCS-1 at 111.111.111.222 - The Provisioning configuration wants the Jabber to register at 222.222.222.111, this is the setting at TMS.

Now Jabber sends Registration messages to this server and fails

2013-03-01 22:14:42,911 Signaling

Sending REGISTER for 103379@vc.vtc.com to 222.222.222.111 using transport auto

2013-03-01 22:14:44,215 WARNING PID 1636 TID 8364 SIP

Transport failed to send registration (sipexcept: 1) to 222.222.222.111:5061

2013-03-01 22:14:46,568 WARNING PID 1636 TID 8364 SIP

Transport failed to send registration (sipexcept: 1) to 222.222.222.111:5060

2013-03-01 22:14:46,581 Signaling

User notification: Failed to register - If the problem persists, contact IT support.

(Unable to connect to 222.222.222.111:5060)

Check your provisioning configuration, make sure the SIP domain on the VCS and in Movi is configured correctly and that the VCS is accessible over TLS and/or TCP.

Would this be because of the Network reachability issue to 222.222.222.111 or something else

[Martin Koch]

In short, yes, this can be due to network reachability issues or something else :-)

And the answer is in general also given:

"Check your provisioning configuration, make sure the SIP domain on the  VCS and in Movi is configured correctly and that the VCS is accessible  over TLS and/or TCP."

JabberVideo provisioning/registration is in general done in two steps,

* getting the provisioning information - which seems to work in your case and then

* registering at the given VCS - which fails here

So the JabberVideo client needs to be able to reach this configured VCS and it must also needs

to be able to handle and accept this registration.

Please check the Admin and Deployment guides, they can show you how the setup should look like.

The best practice is also to use DNS records and not a direct ip address to register to.