I agree with Niel. This won't work for the initial inbound voice call that makes it into your Genesys org and starts an interaction.
It will work if the initial inbound SIP interaction was a 200, then the IVR transfers to an external number or an external transfer by the action of an agent and where the outbound transfer failed with the above mentioned error codes.
The trouble is looking for the right trigger to execute a workflow (perhaps the v2.detail.events.conversation.{id}.customer.end may work for you). The workflow would need to execute a Call Data Action to get the conversation details by conversationId as the JSON you get from the trigger doesn't have the segments you need to parse through that contain the "sipResponseCodes" dimension you need to evaluate. You will need to determine which disconnectTypes values occur when you get the sip code errors you mentioned, then set that as the filter in your trigger. Otherwise you'll need to trigger each interaction to get the conversation details, then loop through each participants.sessions.segments looking for sipResponseCodes values. If the value you have matches any of your codes, then take the true path and execute another call data action to disconnect the interactionid.
I hope this helps you.
------------------------------
Carlos Albor
Principal PS Consultant
------------------------------
Original Message:
Sent: 12-11-2024 05:33
From: Niel Vicente
Subject: Configure a Genesys cloud Architect flow or API to disconnect the call with a SIP error response
Hi Peter,
Don't see how this is possible as a 200OK is sent by the Edge before the call even hits an architect flow.
Once session is established, it is not possible to respond with a 5xx or 4xx message as disconnecting the call will induce a BYE request.
Question is: why cant you re-route the call from the flow itself?
Or transfer the call back to the SBC with a UUI data and use that as your reference in SBC to reroute?
------------------------------
Niel Vicente
Technical Lead - DAMAC Properties
Ex-Genesys
Original Message:
Sent: 12-11-2024 03:32
From: Peter Schriekenberg
Subject: Configure a Genesys cloud Architect flow or API to disconnect the call with a SIP error response
Hi guys, i have a question if some one has a idea if it's possible to Configure a Genesys cloud Architect flow or API to disconnect the call with a SIP error that our SBC can interpret as a signal to reroute or take alternative action. I like to know is there a way to add a Disconnect Action: Within the flow, with a "SIP Response." a specific SIP error code (e.g., 503 for Service Unavailable or 404 for Not Found).
#API/Integrations
#ArchitectureandDesign
#SIP/VoIP
#Telephony
------------------------------
Peter Schriekenberg
Application manager
------------------------------