« Back to Installation

How to locate the BOSH Server Address for hosted SDK

Combination View Flat View Tree View
Threads [ Previous | Next ]
Team,
 
I am trying to locate the Connect Bosh Server address for a customer using the SDK. The Connect Team says to ask here...It is not mentioned how you find it anywhere in the documentation. We located the customer cluster which is Eureka Cluster B. this is an urgent need.
Thanks in advance.
 
Thomas
 
I looked through the deployment guides and see no mention of how someone actually locates the WebEx Connect Bosh Server address for their service. According to the PM for Connect it is not a generic URL.
 
<h2>Overview</h2>
The Cisco AJAX XMPP Library is a client-side JavaScript library that runs in a browser. The BOSH server supports the client requests using the BOSH interface. Essentially BOSH allows for bidirectional communication between the client and server by efficiently using multiple synchronous HTTP request/response pairs without requiring the use of frequent polling. The client and server exchange data using XMPP messages that are sent as HTTP POSTs to the BOSH service.

By default the BOSH service is available at the URL <code>http://some-bosh-server:7335/httpbinding</code> on the BOSH server. To test that the BOSH service is up and running, enter the BOSH URL into a browser. You should receive a HTTP 400 'Bad Request' error. This indicates that BOSH is running. Note that you should not receive a 404 error.

Here’s some info recently posted for how to connect using BOSH:

In order to login to your @cisco.com account in the Webex Connect cloud, you need to set the httpBindingURL to < https://im.ciscowebex.com/http-bind >, then specify your Cisco JID and Cisco Connect password (NOT THE SAME AS CEC). For example:

var connArgs = {
httpBindingURL: "https://im.ciscowebex.com/http-bind"
}
client.connect(userJid, userPwd, connArgs);

This should work in any modern browser (latest released Chrome, Firefox, Safari, MSIE). Most of our examples have a centralized place where the user needs to specify the username, password, and binding URL; just update them to use the above.