EDIT: It looks like the siptraces endpoint can take as an input the conversation Id of the second call. Can someone confirm if the conversation Id presented in the response of that is a translation of the x-inin-cnv header? If so then I can potentially use this to get the "original" call, and then query that for participant data/attributes but it still looks like there's only certain fields that can be PATCHed.
Scenario is this:
- Agent A makes a call outbound which matches a number plan and outbound route that trombones the call back in. Let's call this Conversation A1
- Tromboned call comes in. Let's call this Conversation A2.
I'm going to pass the conversation Id from A1 to conversation A2. The problem here is that A2 has no knowledge of the user who originated that call or the queue if the call was made on behalf. So if you have a policy that deletes calls made from a particular queue/agent, that only takes care of A1. Call A2 still gets recorded unless some other policy matches it.
What I'm hoping to be able to do somehow via API in the receiving flow of the A2 call is to look up the conversation of A1 and merge/overwrite data in A2 such as the originating participant/queue etc. That way if someone looks at the interaction for conversation A2 in any of the views, the agent/queue column contains the information from the original call.
I thought maybe I could use one of the PATCH endpoints to do it but none seem to get to the level I need and provide the actual data points I need to update.
Has anybody done anything similar and is it even possible?
In an ideal world I'd have some way of blending/merging those two calls together so they only appear as one conversation (A1) and A2 just appears as a segment of that.