John.Morgan | 2017-12-06 17:43:45 UTC | #1
The API documentation has four DisconnectType values regarding transfers:
- transfer
- ConsultTransfer
- ForwardTransfer
- ConferenceTransfer
I can replicate situations where DisconnectType = transfer. What are the business rules for the other three Disconnect Types, and/or how can we trigger them in an example call.
tim.smith | 2017-12-06 17:44:16 UTC | #2
What API are you using and what response property are you looking at specifically?
John.Morgan | 2017-12-14 18:01:12 UTC | #3
/api/v2/conversations/calls/{Conversation ID}
I'm looking at DisconnectType in the participant object.
John.Morgan | 2017-12-21 03:55:28 UTC | #4
Here's a link to /api/v2/conversations/calls/{Conversation ID} and the quote from the documentation. Do you have any notes on how the other transfers are used or how we can duplicate the different transfer values listed in the documentation?
CallConversation -> CallMediaParticipant -> disconnectType
(string) The reason the participant was disconnected from the conversation. Valid values: client, endpoint, error, other, peer, spam, system, transfer, transfer.conference, transfer.consult, transfer.forward, transfer.noanswer, transfer.notavailable, transport.failure
John.Morgan | 2018-01-08 17:26:11 UTC | #5
Do you have any documentation on this?
tim.smith | 2018-01-08 18:37:53 UTC | #6
I've checked with the dev team and they do not have anything documented publicly for this.
system | 2018-02-08 18:50:44 UTC | #7
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: 2192