Bugra | 2024-01-09 19:52:56 UTC | #1
Last week, we ran some tests using our Genesys account within region euc1. When we tested the integration in our AWS Paris (EU) environment, the integration worked smoothly, but when we tested it in the AWS Ohio (US) environment, we saw that we could not receive call events.
The integration structure is as follows: We track the events of a call, and when the call end event arrives, we import this call into our system in a few minutes using Genesys APIs. In our AWS Ohio region, we cannot receive calls because we cannot receive call events. There are no other errors in the integration; the services perform their other functions without any problems (adding Genesys users as agents to our system, etc.) and we can use Genesys APIs. Therefore, we are sure the error occurred because we could not receive the call events.
Since our Genesys test account is in the EU and our system is in the US, we thought this might create a conflict. Is there a restriction on Genesys, such as not sending events to different regions? Otherwise, what could be the reason for not sending events?
crespino | 2024-01-09 20:08:13 UTC | #2
How are you getting call events in the US region? Are you using websockets with the Notification API and subscribing to a specific event?
I assume you are authenticating to the org in the US region with OAuth and getting an access token, correct?
Bugra | 2024-01-10 13:17:34 UTC | #3
Yes, we're using web sockets and we're authenticating with OAuth and getting an access token. To avoid misunderstanding, our Genesys org is in the EUC, but we're trying to get the call events into our application which is hosted in the US. We can authenticate without error and we see the web socket is open. But somehow, we're not getting any call events.
system | 2024-02-09 13:17:38 UTC | #4
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 24014