Troubleshooting Guide
Debugging JavaScript The first thing to do if you experience problems while using the Jabber SDK is to open up your browser's JavaScript console and other debugging tools.Internet Explorer
Select Tools > Developer Tools (or press F12). Clicking the Script tab will open the Console view in the right-hand pane, which is where you will see any error messages from the Jabber SDK or other errors that may be causing problems.Firefox
For Firefox, the excellent Firebug add-on is the best way to debug JavaScript. Go to http://getfirebug.com/ for more details.Chrome
Chrome comes with a good set of tools. Click the Spanner Icon and select Tools > JavaScript Console.Safari
By default, the developer tools in Safari are hidden. You can turn them on by going to Preferences > Advanced and checking "Show Develop menu in menu bar". This will activate the Develop menu which contains a number of tools - to show the console select Show Error Console.Common Errors
TFTP fetch error
The most common reason for this error is that you haven't set up a device in CUCM. Check the instructions in JabberSDK_CUCM_Guide.txt which is in the docs folder. Another reason for this error may be if your firewall is blocking TFTP access from your browser. Check with your system administrator.Plugin not installed
Make sure that you have installed the browser plugin as described in http://developer.cisco.com/web/jabbersdk/startLog Files
The browser plugin that's used by the SDK to enable telephony writes a log file to your local file system. The file is called softphone.log and you can find it at the following locations:-- Windows XP C:\Documents and Settings\{username}\Local Settings\Application Data\softphone.log
- Windows 7/Vista C:\Users\{username}\Application Data\Local\softphone.log
- Mac OS X /Users/{username}/Library/Application Support/softphone.log
This log file contains a lot of very detailed information and it's not really intended as a diagnostic tool for SDK users, but it can be useful if contacting Cisco support.
