Server release reason
When a call ends, the 1-to-1 Call Event callback or Group Call Event callback is called depending on the call type. Applications can get to know the reason of a call release by investigating related keys.
Available types of reasons for releasing a call are as follows:
| Type | Description | Related keys | Note |
|---|---|---|---|
| Simple | Q.850 codes. Only six codes are used for this type. | terminate | Only for 1-to-1 calls |
| LINE Planet-defined | Reasons for call releases defined by LINE Planet, with common values for client and server | disconnect_reason, releaser_type | |
| App-defined | Reasons for call releases defined by the application | user_rel_code | |
| Debug | Low-level data related to call releases | rel_code, rel_code_str |
Simple release codes
The terminate parameter uses only six codes among Q.850 codes for simplicity.
| Definition | Q.850 cause code |
|---|---|
| NORMAL_RELEASED | 16. If the callback parameter duration is greater than 0, terminate will be 16. |
| CANCELED | 77 |
| REJECTED | 21 |
| BUSY | 17 |
| NO_ANSWER | 18 |
| else | 127 |
LINE Planet-defined release codes (Disconnect reason)
LINE Planet provides reasons and sources for call disconnection, which are commonly defined for client and server. The information is delivered in the disconnect_reason and releaser_type parameters of the 1-to-1 Call Event callback or Group Call Event callback.
For more information on disconnect_reason and releaser_type, see Disconnect reasons.
Application-defined release codes
If application developers want to define their own release reasons, user_rel_code can be used. When a call ends, an application can define its own reason as a string type through PlanetKit SDK. This string value will be delivered in user_rel_code to the application server from the LINE Planet server.
Release codes for debugging
LINE Planet can track what happened when a call is released, using rel_code, and rel_code_str.