Jabber Web - Voice and Video - autologon after pagerefresh

[m.petrilli_cgi]

Hi all,

we are developing an internal tool for the data interchange between the Cisco Communication Manager and an intranet web app.

Actually we are in a test phase and we are able to connect to CUCM through CWIC javascript library using the template of the sample application provided in https://developer.cisco.com/site/jabber-websdk/develop-and-test/voice-and-video/downloads-and-docs/

Now we want to go a step foreward and implement a solution that won't request login after every page refresh or on every new page open.

We suppose that there's a way to configure the API initialization with some parameter that try to have a sort of persistent session cookie shared between all the browser tabs and in the same tab between all the page refresh.

Our solution is an ASP.NET VB web application, using Javascript and jQuery, hosted on an internal server, used on IE, Firefox, Chrome and Safari.

Is there a way to reach this?

Many thanks for any help.

[Geevarghese Cheria]

Hi,

   Your question is moved under Jabber community for getting more visibility by the concerned experts. Request to check this url - Re: Jabber Web SDK Discovery based Sign-In for related info.

Thanks and Regards,

Geevarghese

[dstaudt]

In general it is advisable to avoiding 'reloading' the Jabber SDK on page navigation, as there is significant overhead associated (on the browser/PC side as well as CUCM) with re-init-ing/re-connecting/re-registering the Jabber phone device - not to mention behaviour problems like disconnecting any active calls, and being momentarily unable to receive any inbound calls. 

Some workaround techniques have been used with varying success:

- Host the Jabber SDK code in a separate popup window

- Have the Jabber SDK webapp/code live in outer page which uses iFrames to display dynamically navigated content

- Create a browser add-on to provide a long-running container for the SDK code (Chrome only)

In the event you do need to reload the Jabber SDK - e.g. if the user manually reloads the page - then you could potentially store the authentication values (username/password in the case where Jabber needs to be authenticated via the  manual or service-discovery methods, or the SSO token in the case of single-sign-on) in HTML5 browser-local storage or a browser-cookie during the page unload event:

HTML5 Web Storage