The Agent page should be able to access the resource like (CSS,images) used on the Customer CoBrowse page. Because when Customer page is in CoBrowse session the src links for these resources are converted to the absolute location where these resources are present. So to render these resources at Agent side (Agent page) the resource location should be accessible from the agent browser.

FYI,
As I remember in one of the customer deployment they maintain 2 copies of such resources one on DMZ and another on intranet. So that Agent system access same resources from the intranet location and customer page over the DMZ location.

@Bandwidth details are included in Avaya Co-browse docs.

As such CoBrowse documents don't specify the required bandwidth to run the CoBrowse however performance testing has been around the network connections.

Hi Ganesh,

Allowing custom (customer) javascript to pass and execute at Agent side will lead the security risk. To adhere the security CoBrowse doesn’t allow custom javscript pass on at Agent side.


So, currently there is no option which allows custom javascript at Agent (workspace) side.

Thanks & Regards
~Manish Negi

Hi,

BotConnector supports Unicode character's (able to support multi byte characters), however one has to make sure that the custom plugin also supports it.



Thanks & Regards
~Manish Negi

Hi Raul,


CoBrowse is an SDK based solution, it has API’s to create CoBrowse session from both the ends. Either Agent or customer both parties are allowed to create the CoBrowse session and other party joins it.


Currently in OOTB Oceana solution Agent creates the CoBrowse session for the preconfigured CoBrowse pages and Customer joins the session automatically. As the token is passed with URL to the end customer over the chat.


If I am not wrong you want a website enabled with CoBrowse (no chat interaction) for which Agent can initiates the CoBrowse session.


Yes, we can do that in fact the standalone CoBrowse has been implemented in this manner only. OOTB standalone solution allows either Agent or Customer to initiate the CoBrowse session and other party joins it. Here after generation of the CoBrowse session one has to provide the CoBrowse session (passphrase) to other party through any media that could be using email or over the voice.

So in a nut shell being an SDK based solution CoBrowse facilitates implementors to have their own implementation by provided api's to initiate the CoBrowse by either Agent or Customer. So it doesn’t matter if the CoBrowse Webpage has chat enabled or not as CoBrowse can be enabled on any Webpage (using the CoBrowse sdk) and initiated by either party.

Please refer the devconnect document for the detailed CoBrowse client sdk apis

https://www.devconnectprogram.com/site/global/products_resources/avaya_client_sdk/programming_docs/current/javascript/sharing/index.gsp



Incase any assistance is needed please feel free to contact CoBrowse snapin team

Thanks & Regards
~Manish Negi