Hello Genesys community !

Who else has the problem with Accepting / Answering an inbound alerting call within the Embedded Salesforce client / Widget ?

Its been going on quite a while, we've had over 25 cases open for the same issue..  SFDC Agent running Chrome in a Single Tab session, 3rd party cookie URLs added to the browser settings, as well as in Memory Saver to avoid memory free from the SFDC and Genesys , and remain those tabs as Active, 

Intermittently when an inbound call is alerting, the agent clicks the Pickup icon, and there is a spinning wheel, indicating delay / buffering of some type, then the Agent is placed into Not Responding.   Is able to go Back on Q, and get a successful call.  We see this over and over.   Wiresharks logs, Net Console, Zscaler ..etc.. all not giving any definitive reason.

We cannot be the only ones facing this..

Not to mention the annoying "The WebRTC window is unable to Display" error also wide spread over our environments.

Thank you in advance

John

This could be a number of issues.  I would suggest you have a look at the console logs for problems with the pickup.  Also, check the agent for station errors.  You might want to use the Notification Topic for Events to watch for these errors.  

Hello Genesys community !

Who else has the problem with Accepting / Answering an inbound alerting call within the Embedded Salesforce client / Widget ?

Its been going on quite a while, we've had over 25 cases open for the same issue..  SFDC Agent running Chrome in a Single Tab session, 3rd party cookie URLs added to the browser settings, as well as in Memory Saver to avoid memory free from the SFDC and Genesys , and remain those tabs as Active, 

Intermittently when an inbound call is alerting, the agent clicks the Pickup icon, and there is a spinning wheel, indicating delay / buffering of some type, then the Agent is placed into Not Responding.   Is able to go Back on Q, and get a successful call.  We see this over and over.   Wiresharks logs, Net Console, Zscaler ..etc.. all not giving any definitive reason.

We cannot be the only ones facing this..

Not to mention the annoying "The WebRTC window is unable to Display" error also wide spread over our environments.

Thank you in advance

John

Thanks Robert. We have exhausted many troubleshooting methods.

We are following this thread which is showing numerous other customers have this identical problem.

https://community.genesys.com/discussion/agents-unable-to-pick-up-calls

Firefox seems to solve the issue .. as a non-chromium based browser. 

We are not using Firefox as an approved browser .  

Thanks

This could be a number of issues.  I would suggest you have a look at the console logs for problems with the pickup.  Also, check the agent for station errors.  You might want to use the Notification Topic for Events to watch for these errors.  

Hello Genesys community !

Who else has the problem with Accepting / Answering an inbound alerting call within the Embedded Salesforce client / Widget ?

Its been going on quite a while, we've had over 25 cases open for the same issue..  SFDC Agent running Chrome in a Single Tab session, 3rd party cookie URLs added to the browser settings, as well as in Memory Saver to avoid memory free from the SFDC and Genesys , and remain those tabs as Active, 

Intermittently when an inbound call is alerting, the agent clicks the Pickup icon, and there is a spinning wheel, indicating delay / buffering of some type, then the Agent is placed into Not Responding.   Is able to go Back on Q, and get a successful call.  We see this over and over.   Wiresharks logs, Net Console, Zscaler ..etc.. all not giving any definitive reason.

We cannot be the only ones facing this..

Not to mention the annoying "The WebRTC window is unable to Display" error also wide spread over our environments.

Thank you in advance

John

Hello Genesys community !

Who else has the problem with Accepting / Answering an inbound alerting call within the Embedded Salesforce client / Widget ?

Its been going on quite a while, we've had over 25 cases open for the same issue..  SFDC Agent running Chrome in a Single Tab session, 3rd party cookie URLs added to the browser settings, as well as in Memory Saver to avoid memory free from the SFDC and Genesys , and remain those tabs as Active, 

Intermittently when an inbound call is alerting, the agent clicks the Pickup icon, and there is a spinning wheel, indicating delay / buffering of some type, then the Agent is placed into Not Responding.   Is able to go Back on Q, and get a successful call.  We see this over and over.   Wiresharks logs, Net Console, Zscaler ..etc.. all not giving any definitive reason.

We cannot be the only ones facing this..

Not to mention the annoying "The WebRTC window is unable to Display" error also wide spread over our environments.

Thank you in advance

John

I see this problem occur sometimes when the Genesys Cloud Browser app is running alongside the embedded framework client.

Once I close GC App or restart the browser, the problem goes away.

By the way, running GC alongside the embedded framework client, is not supported by Genesys and will cause unpredictiable behavior.
This is a big pain in the butt issue because customers should be allowed to access features of GC App at the same time as running a CRM application that uses the embedded framework. I opened a support case with Genesys and they said they will not fix it and directed me to submit the following idea.

So go vote for it and let's get this issue fixed:-)

Allow the embedded frame work to run concurrently with GC App
https://genesyscloud.ideas.aha.io/ideas/OPCRM-I-31" title="https://genesyscloud.ideas.aha.io/ideas/opcrm-i-31" href="https://genesyscloud.ideas.aha.io/ideas/OPCRM-I-31" rel="noreferrer noopener" target="_blank" class="fui-Link ___1rxvrpe f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1hu3pq6 f11qmguv f19f4twv f1tyq0we f1g0x7ka fhxju0i f1qch9an f1cnd47f fqv5qza f1vmzxwi f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn">https://genesyscloud.ideas.aha.io/ideas/OPCRM-I-31

Hello Genesys community !

Who else has the problem with Accepting / Answering an inbound alerting call within the Embedded Salesforce client / Widget ?

Its been going on quite a while, we've had over 25 cases open for the same issue..  SFDC Agent running Chrome in a Single Tab session, 3rd party cookie URLs added to the browser settings, as well as in Memory Saver to avoid memory free from the SFDC and Genesys , and remain those tabs as Active, 

Intermittently when an inbound call is alerting, the agent clicks the Pickup icon, and there is a spinning wheel, indicating delay / buffering of some type, then the Agent is placed into Not Responding.   Is able to go Back on Q, and get a successful call.  We see this over and over.   Wiresharks logs, Net Console, Zscaler ..etc.. all not giving any definitive reason.

We cannot be the only ones facing this..

Not to mention the annoying "The WebRTC window is unable to Display" error also wide spread over our environments.

Thank you in advance

John

I see this problem occur sometimes when the Genesys Cloud Browser app is running alongside the embedded framework client.

Once I close GC App or restart the browser, the problem goes away.

By the way, running GC alongside the embedded framework client, is not supported by Genesys and will cause unpredictiable behavior.
This is a big pain in the butt issue because customers should be allowed to access features of GC App at the same time as running a CRM application that uses the embedded framework. I opened a support case with Genesys and they said they will not fix it and directed me to submit the following idea.

So go vote for it and let's get this issue fixed:-)

Allow the embedded frame work to run concurrently with GC App
https://genesyscloud.ideas.aha.io/ideas/OPCRM-I-31" title="https://genesyscloud.ideas.aha.io/ideas/opcrm-i-31" href="https://genesyscloud.ideas.aha.io/ideas/OPCRM-I-31" rel="noreferrer noopener" target="_blank" class="fui-Link ___1rxvrpe f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1hu3pq6 f11qmguv f19f4twv f1tyq0we f1g0x7ka fhxju0i f1qch9an f1cnd47f fqv5qza f1vmzxwi f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn">https://genesyscloud.ideas.aha.io/ideas/OPCRM-I-31

Hello Genesys community !

Who else has the problem with Accepting / Answering an inbound alerting call within the Embedded Salesforce client / Widget ?

Its been going on quite a while, we've had over 25 cases open for the same issue..  SFDC Agent running Chrome in a Single Tab session, 3rd party cookie URLs added to the browser settings, as well as in Memory Saver to avoid memory free from the SFDC and Genesys , and remain those tabs as Active, 

Intermittently when an inbound call is alerting, the agent clicks the Pickup icon, and there is a spinning wheel, indicating delay / buffering of some type, then the Agent is placed into Not Responding.   Is able to go Back on Q, and get a successful call.  We see this over and over.   Wiresharks logs, Net Console, Zscaler ..etc.. all not giving any definitive reason.

We cannot be the only ones facing this..

Not to mention the annoying "The WebRTC window is unable to Display" error also wide spread over our environments.

Thank you in advance

John

Hi John,

We had this issue too and narrowed it down to the Browser 'Sleeping' unused tabs, Once the tab containing the Web App is set to sleep it disrupts the connection to Genesys, disabling this function seems to have resolved the issue

I see this problem occur sometimes when the Genesys Cloud Browser app is running alongside the embedded framework client.

Once I close GC App or restart the browser, the problem goes away.

By the way, running GC alongside the embedded framework client, is not supported by Genesys and will cause unpredictiable behavior.
This is a big pain in the butt issue because customers should be allowed to access features of GC App at the same time as running a CRM application that uses the embedded framework. I opened a support case with Genesys and they said they will not fix it and directed me to submit the following idea.

So go vote for it and let's get this issue fixed:-)

Allow the embedded frame work to run concurrently with GC App
https://genesyscloud.ideas.aha.io/ideas/OPCRM-I-31" title="https://genesyscloud.ideas.aha.io/ideas/opcrm-i-31" href="https://genesyscloud.ideas.aha.io/ideas/OPCRM-I-31" rel="noreferrer noopener" target="_blank" class="fui-Link ___1rxvrpe f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1hu3pq6 f11qmguv f19f4twv f1tyq0we f1g0x7ka fhxju0i f1qch9an f1cnd47f fqv5qza f1vmzxwi f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn">https://genesyscloud.ideas.aha.io/ideas/OPCRM-I-31

Hello Genesys community !

Who else has the problem with Accepting / Answering an inbound alerting call within the Embedded Salesforce client / Widget ?

Its been going on quite a while, we've had over 25 cases open for the same issue..  SFDC Agent running Chrome in a Single Tab session, 3rd party cookie URLs added to the browser settings, as well as in Memory Saver to avoid memory free from the SFDC and Genesys , and remain those tabs as Active, 

Intermittently when an inbound call is alerting, the agent clicks the Pickup icon, and there is a spinning wheel, indicating delay / buffering of some type, then the Agent is placed into Not Responding.   Is able to go Back on Q, and get a successful call.  We see this over and over.   Wiresharks logs, Net Console, Zscaler ..etc.. all not giving any definitive reason.

We cannot be the only ones facing this..

Not to mention the annoying "The WebRTC window is unable to Display" error also wide spread over our environments.

Thank you in advance

John

FYI, in Chrome, it is called a memory saver.  You can also configure tabs that you do not want to go to sleep due to inactivity.

Hi John,

We had this issue too and narrowed it down to the Browser 'Sleeping' unused tabs, Once the tab containing the Web App is set to sleep it disrupts the connection to Genesys, disabling this function seems to have resolved the issue

I see this problem occur sometimes when the Genesys Cloud Browser app is running alongside the embedded framework client.

Once I close GC App or restart the browser, the problem goes away.

By the way, running GC alongside the embedded framework client, is not supported by Genesys and will cause unpredictiable behavior.
This is a big pain in the butt issue because customers should be allowed to access features of GC App at the same time as running a CRM application that uses the embedded framework. I opened a support case with Genesys and they said they will not fix it and directed me to submit the following idea.

So go vote for it and let's get this issue fixed:-)

Allow the embedded frame work to run concurrently with GC App
https://genesyscloud.ideas.aha.io/ideas/OPCRM-I-31" title="https://genesyscloud.ideas.aha.io/ideas/opcrm-i-31" href="https://genesyscloud.ideas.aha.io/ideas/OPCRM-I-31" rel="noreferrer noopener" target="_blank" class="fui-Link ___1rxvrpe f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1hu3pq6 f11qmguv f19f4twv f1tyq0we f1g0x7ka fhxju0i f1qch9an f1cnd47f fqv5qza f1vmzxwi f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn">https://genesyscloud.ideas.aha.io/ideas/OPCRM-I-31

Hello Genesys community !

Who else has the problem with Accepting / Answering an inbound alerting call within the Embedded Salesforce client / Widget ?

Its been going on quite a while, we've had over 25 cases open for the same issue..  SFDC Agent running Chrome in a Single Tab session, 3rd party cookie URLs added to the browser settings, as well as in Memory Saver to avoid memory free from the SFDC and Genesys , and remain those tabs as Active, 

Intermittently when an inbound call is alerting, the agent clicks the Pickup icon, and there is a spinning wheel, indicating delay / buffering of some type, then the Agent is placed into Not Responding.   Is able to go Back on Q, and get a successful call.  We see this over and over.   Wiresharks logs, Net Console, Zscaler ..etc.. all not giving any definitive reason.

We cannot be the only ones facing this..

Not to mention the annoying "The WebRTC window is unable to Display" error also wide spread over our environments.

Thank you in advance

John