ckasha | 2025-01-03 11:45:14 UTC | #1
Hi Everyone,
I am currently working with Genesys Cloud Communicate and utilizing the Conversation Details API to fetch information about calls routed to a station. However, I have encountered a limitation: when a call is routed to a station, the participant purpose is returned as "station," but the station ID is not included in the API response.
Participant JSON:
{ "participantId": "3e45e56d-c0bf-482c-ac72-3d6c8a87cf7f", "participantName": "Extension", "purpose": "station", "sessions": [ { "ani": "tel:+1206xxxxxxx", "direction": "inbound", "dnis": "tel:+1206xxxxxxx", "edgeId": "5bc22eb2-81e9-4bbf-901e-346bb10f16c0", "mediaType": "voice", "peerId": "1479955e-2fa6-3535-a4f5-6c6f30aca3d1", "provider": "Edge", "remote": "BUTLER", "remoteNameDisplayable": "Extension", "sessionDnis": "sip:x82211@10.87.000.000;language=en-US;user=station", "sessionId": "6bd9a9da-e79b-3f35-91a8-7f07d75454fe", "metrics": [ { "emitDate": "2024-12-18T00:23:22.440Z", "name": "tAlert", "value": 12 } ], "segments": [ { "conference": false, "disconnectType": "transfer", "segmentEnd": "2024-12-18T00:23:22.440Z", "segmentStart": "2024-12-18T00:23:22.428Z", "segmentType": "alert" } ] } ] }
This creates a challenge when trying to identify which specific station is handling a particular call, especially in environments where multiple stations are in use.
Key Points:
- The Conversation Details API returns the participant purpose as "station" but does not provide the station ID.
- Without the station ID, it becomes difficult to directly correlate the call with the station it was routed to.
Questions:
- How can we identify the station handling a call when station ID is not included in the API response?
- Are there any workarounds or best practices to map the conversation to a specific station?
system | 2025-02-03 11:46:09 UTC | #2
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: 31031