Releasing calls
Learn about the standard processes by which calls are released.
For simplicity, the examples on this page use abbreviated attribute values. For example, ConnID 1, which – in actual events – displays as <ConnID>@<metainformation>.
The following comments and abbreviations are used in the call models:
- OPT—Optional.
- DIAL—Might be a dialed number or is not present if Voice Microservices have no information about the other party.
Release phase
The following table describes the release phase.
Party A | Party B |
Conversation | |
Release (TReleaseCall) | |
EventReleased ConnID 1 |
EventReleased ConnID 1 |
Release from conference phase
The following table describes the release from conference phase.
Party A | Party B | Party C |
Conference | ||
Release (TReleaseCall) | ||
EventPartyDeleted ConnID 1 |
EventReleased ConnID 1 |
EventPartyDeleted ConnID 1 |
Conversation |
a. If more than two parties remain in the conference call, CallState has a value of Conferenced; otherwise, CallState has a value of OK.
Delete from conference phase
The following table describes the release phase.
Party A | Party B | Party C |
Conference | ||
Delete B (TDeleteFromConference) | ||
EventPartyDeleted ConnID 1 |
EventReleased ConnID 1 |
EventPartyDeleted ConnID 1 |
Conversation |
a. If more than two parties remain in the conference call, CallState has a value of Conferenced; otherwise, CallState has a value of OK.