Chad_Maggard | 2017-10-25 21:42:08 UTC | #1
Using this page produces "Browser not supported" error in Chrome,Firefox and IE. Can someone give me a clue as to what could be wrong?
<!DOCTYPE html> <html lang="en"> <head> <link rel="chrome-webstore-item" href="https://chrome.google.com/webstore/detail/chpkaocjjopjgclkahflonfkhdhkdenh" data-domain="www.example.com"> </head> <body onload="onloaded()"> <div id="before"> Branding content goes here.<br/> This is on the customer's own web site.<br/> The form is an embedded iframe that's coming from ININ.<br/> </div> <div id="screenshareContainer"></div> <div id="after"> Content of customer's website below iframe/form<br /> Content of customer's website below iframe/form<br /> Content of customer's website below iframe/form<br /> </div>
<script src="https://apps.mypurecloud.com/webchat/jsapi-v1.js" type="text/javascript"></script>
<script type="text/javascript">
var config = { // Webchat service URL
"webchatServiceUrl": "https://realtime.mypurecloud.com:443",
//Webchat app URL
"webchatAppUrl": "https://apps.mypurecloud.com/webchat",
// Numeric organization ID "orgId": ,
// String organization ID "orgName": "",
// Log level (DEBUG, INFO, WARN, ERROR, or FATAL) "logLevel": "DEBUG",
// Locale code of end-user which will be used to localize the widget "locale": "en",
"orgGuid": "54bc67ee-079c-4b59-a4c1-1e05768ed7a4",
// CSS class if widget is rendered as frame "cssClass": "screenshare-frame",
// Additional CSS properties if widget is rendered as an iframe. // These properties apply to the iframe itself, not to its content. "css": { "width": "480px", "height": "282px", "border": "none" },
// The URL of a CSS file to apply to the content of the iframe. "contentCssUrl": "screenshare.css",
//Some customers may use an external application and browser support will not prohibit the initiation of screen share in that case "standAloneApplication": false,
//The URL of your branded extension in the Chrome web store. Only used if you plan for end users to screen share from Chrome. "chromeWebstoreUrl": "https://chrome.google.com/webstore/detail/chpkaocjjopjgclkahflonfkhdhkdenh" };
function onloaded() { ININ.screenshare.create(config, function(err, screenshare) { if (err) { if (err.name === 'UNSUPPORTED_BROWSER') { // Redirect to instructions for unsupported browser, or handle appropriately alert('Sorry, your browser is not supported!'); return; } }
screenshare.renderScreenShareForm({ containerEl: 'screenshareContainer' }); }); } </script> </body> </html>
anon57595521 | 2017-10-31 14:50:00 UTC | #2
Hey Chad,
A couple things to note here:
- If you're using the embedded form for screen share, (i.e., the form is embedded on a page on
your-site.com then you'll need to deploy your own version of the Screen Share extension in order to support Chrome. Here are instructions for doing so: https://developer.inindca.com/api/screenshare/ under the "Branding the Chrome Extension" section - IE is not supported at all for screen share.
- It looks like some of your properties in the config are incomplete or incorrect. Make sure you fill out the orgName, orgId, and orgGuid.
We'd suggest developing in Firefox first, as it's the easiest to get up and running with screen share. If you have those three properties configured and still get the error, let me know what version of Firefox (and Chrome) you're using, and we can look a little closer.
Chad_Maggard | 2017-10-31 15:05:10 UTC | #3
Note, I took out orgName, orgId, and orgGuid for security reasons, I didn't think it was the smartest thing to do, putting out that type of information for the world to see. Am I wrong for thinking this way?
anon57595521 | 2017-10-31 16:55:41 UTC | #4
Nope, that's a good idea. I just wanted to make sure (since you did leave orgGuid in your post, I wasn't sure if you removed the other intentionally or not).
Chad_Maggard | 2017-11-06 15:27:54 UTC | #5
That orgGUID is the original one from the example provided by Genesys, not mine. Where do I find mine to replace this one? What is this used for?
anon57595521 | 2017-11-20 17:19:26 UTC | #6
That's used to validate the security key for screen share against PureCloud for your organization. We're working to consolidate orgId and orgGuid into a single field. You can find that under Admin > Organization Settings > Advanced.
anon57595521 | 2017-11-20 17:20:21 UTC | #7
Also if you'd like quicker support please contact PureCloud support directly. Unfortunately I don't get notifications for these posts.
Chad_Maggard | 2017-11-20 18:06:19 UTC | #8
:-) Per what support says, I am working this issue through both channels. I have a support ticket open and I am working with you.
anon57595521 | 2017-11-21 21:49:28 UTC | #9
Hey Chad, Please make sure your page is being served over HTTPS, if you're not. Chrome requires HTTPS pages and a chrome extension for doing screen sharing, so your page will have to be HTTPS, and you'll have to have a chrome extension installed that matches your domain in the allowed domains list.
Chad_Maggard | 2017-11-27 17:55:45 UTC | #10
anon57595521, post:9, topic:2011
and a chrome extension for doing screen sharing, so your page will have to be HTTPS, and you'll have to have a chrome extension installed that matches your domain in the allowed domains list.
setting the site to use https worked. The page now loads... Thank you.
Chad_Maggard | 2017-11-28 14:21:41 UTC | #11
But now I am having a problem with the sessions not connecting. Both sides 'look' like they are waiting for the other side. I have tried using Firefox and Chrome. Firefox gets further in the process than Chrome does.
system | 2017-12-29 14:22:28 UTC | #12
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 2011