/mcpvar jabberwerx_config = {unsecureAllowed: true}; <script type="text/javascript"> //Set the JabberWerx connect to unsecure because the custom authentication //on the XMPP server does not support encrypted credentials. var jabberwerx_config = {unsecureAllowed: true}; </script> <script type="text/javascript" src="thirdparty/jquery/jquery-1.5.min.js"></script> <script type="text/javascript" src="thirdparty/strophe/strophe.js"></script> <script type="text/javascript" src="thirdparty/strophe/strophe.pubsub.min.js"></script> <script type="text/javascript" src="thirdparty/util/converter.js"></script> <script type="text/javascript" src="EventTunnel.js"></script> <script type="text/javascript"> jQuery(document).ready(function () { var tunnel = new finesse.EventTunnel(); tunnel.init(); }); </script> </head> </html> Connect to XMPP over HTTP (BOSH/WebSocket) using Finesse EventTunnel To initialize the XMPP connection, the following information must be passed to the EventTunnel before it can proceed: 1. Agent ID 2. XMPP Domain 3. Agent Password 4. XMPP PubSub Domain 5. Agent XMPP Resource (Optional) The postMessage payload has the following message structure: message = type + "|" + message; where type is a number that has the following mapping: Description Value Message Type XMPP events received by the EventTunnel and published out to the parent frame 0 EVENT Agent XMPP ID 1 ID Agent XMPP password 2 PASSWORD Agent XMPP resource 3 RESOURCEID Status of the XMPP connection published by the EventTunnel 4 STATUS Domain of the XMPP service 5 XMPPDOMAIN PubSub domain of the XMPP service 6 PUBSUBDOMAIN Request to subscribe to an XMPP node 7 SUBSCRIBE Request to unsubscribe form an XMPP node 8 UNSUBSCRIBE Cisco Finesse Web Services Developer and JavaScript Guide, Release 12.5(1) 373 Cisco Finesse Notifications Connect to XMPP over HTTP (BOSH/WebSocket) using Finesse EventTunnel