Showing results for 
Search instead for 
Did you mean: 

Jabber and Windows IE 11

Cisco Employee
Cisco Employee

I saw an announcement that Jabber now is supported for running on Windows 8.1 and also supported on IE 11.

Is there a new jabberwerx.js file that I can download so that I can use it on IE 11?


12 Replies 12



The MR6 (3.0.6) does suppoer Win8.1 and IE 11.

You can visit this page below

and download both SDK and plugin to try it out



So, this support does not extend to Jabber IM & Presence?

I am looking for a jabberwerx.js file that works on IE 11, the one I have has errors when running in an IE 11 browser.

Is it supposed to work in IE 11?

-john mennear


Hi John,

The release note is for voice and video SDK.

You can see the latest release note as well as the developer guide for IM/Presence as well.

From the developer guide, there is a note mentioned under the Supported Browsers section as below

Internet Explorer versions 8 and 9 are explicitly tested and documented. IE 10 and later are standards compliant and will be treated like Chrome and Firefox where only the latest versions are regression tested.

Since IE11 might involved some changes architecturally, I'm not sure if "regression testing" will address all the possible issues.

Here is the latest version that you can download, feel free to give it a try and let us know if any help is needed.



I used the jabberwerx.js and jabberwerx.Cisco.js in my Office365 Javascript application while using IE 11.

The code breaks in the same places that it does in IE 9.

Do you think the BU cares if they cannot claim that they support Office 365?

What should I do?

-john mennear


Hi, John,

We are looking into this and will get back to you.


Yes, that is correct.

And to be sure, I copied the files and rebuilt the solution, redeployed to Office365 and tested with my IE 11 browser.

Same errors as before.

-john mennear



One thing you can quickly check is that you can access the BOSH URL from your browser. There's a slim chance that there is a certificate problem of somesort. You should see a page describing the XMPP protocols supported when you navigate to the BOSH URL.

More likely there is some difference in Office 365's IE 11 (though I could not find such differences documented anywhere). IE 8, 9 and 10 used an XMLDomainRequest object for cross site scripting. This object came with restrictions that did not allow CORS with different protocols (an application can not be served as http and access a cross site script to an https URL).  IE 11 removed the XMLDomainRequest object and replaced it with CORS for XMLHttpRequest (XMLHttpRequest enhancements (Windows))), something jQuery supports directly and which does allow differing protocols.

The problematic piece of code you identified above would only execute when CAXL was trying to (essentially) proxy an XMLHttpRequest using an XMLDomainRequest. If the XMLDomainRequest object was undefined (IE 11) that particular piece of code should never execute. So it must be that IE 11 in Office 365 implements XMLDomainRequest and therefore has the same restrictions as IE 8, 9, 10.

CAXL 2014.04 added an additional check to always use jQuery's CORS implementation if supported. That check must be failing as well, meaning the only way CORS will work at all in Office 365 would be to keep using XMLDomainRequest. In other words, CAXL cannot be updated to handle the problem you are seeing.

A possible work around would be to make sure you are serving your app from the same protocol as the CUPS server you are trying to connect to. I found this discussion that may be applicable: Issues with performing an ajax call within an Office365 app for Excel

I could be wrong about all this John. I didn't spend a lot of time looking for blogs or similar problem reports posted on the web. But I did some debugging to day to make sure CAXL was using jQuery's default XMLHttpRequest implementation on IE11 in Windows 7 and 8.1, and that CORS was working correctly when using different protocols. In all cases jQuery reported that the browser supported CORS and that the XMLDomainRequest object did not exist, and CAXL worked appropriately.

I wish I had better news, John. Perhaps the blog posting will provide a work around.

Joe Fuhrman

CAXL Developer


I am testing using Firefox, Chrome and IE. Only IE is failing when using Office365 and jabberwerx.js.

I did the test as you asked from the IE11 browser, and it worked, as I expected:

This URI is for XMPP communication via the BOSH protocol.

Please reference the following protocols:

  • RFC 3920<>: Extensible Messaging and Presence Protocol (XMPP): Core

  • RFC 3921<>: Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence

  • XEP-0124<>: Bidirectional-streams Over Synchronous HTTP (BOSH)

  • XEP-0206<>: XMPP Over BOSH

Unfortunately, I think what all this means is that we, Cisco, cannot advertise that jabber CAXL is supported on IE 10 or 11 for IM and Presence. And also we, Cisco, cannot advertise that Jabber CAXL is supported for Office 365.

-john mennear


Looking at this email again, what are the restrictions on 8, 9 and 10?

I was having another problem with IE 9 which prompted me to install IE 11. Is there a trick to get IE 9 to work that I missed?

-john mennear


Did you ever learn anything about this issue John, or find a version of jabberwerx that supports IE 11?



I am facing issues while using jabberwrex.js in IE11.

the error message in console window is

"Unable to parse xml because default namespace of XML is empty"

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: