Rodrigo,

This can be caused by a number of issues, but the primary 2 are:

• Firewall or NAT issue - If you already have another soft client (e.g. CUPC) which works correctly, ensure that your browser is allowed to open non-http outgoing connections. Typical SIP ports are 5060/5061 TCP and UDP. Sometimes port 5004.
• Missing or invalid device - ensure you have a client Services Framework device configured named "ECP" followed by your username. There are 2 files in the zip that should help you with more information on this: README.txt and JabberSDK_CUCU_Guide.txt

Regards,

Martin.

Hi Rodrigo,

Can you see any error in the JavaScript console (ex: Firebug) of your browser ?

Another cause could be related to DNS problems. On your CUCM administration, page, go to System => Server, click Find, click your Server.
If the "Host Name / IP Address" field contains a host name, it should be resolvable from your client machine.
Example:
The CUCM Server configuration says "Host Name / IP Address" is "mycucm".
From the client machine the "ping mycucm" command should succeed.
If not, 2 solutions:
1. change the CUCM config to use a plain IP address
2. in the client's local hosts file, add an entry with the cucm host name. On Windows, edit C:\Windows\System32\drivers\etc\hosts as an administrator and append a line like
1.2.3.4 mycucm

In both case, retest the ping command

Hope it helps,

Thomas