TromboneDisconnectCall is usually used by the caller to terminate the trombone operation and remain connected to Blueworx Voice Response. When it receives this request, the custom server asks TDM Manager to disconnect the caller and third party from the TDM bus. When this completes successfully, the TromboneDisconnectCall request returns a zero response in the disconnect_call_status to indicate that the two trombone parties are now disconnected, and that the caller is connected to Blueworx Voice Response.
If this process fails, the TromboneDisconnectCall request returns a non-zero response in the disconnect_call_status to indicate that the trombone disconnect operation has failed for the given reason.
None.
The status of the disconnect request, as shown in Table 1.
Make Call Status |
Error Description |
---|---|
0 |
Trombone function request was successful. |
105 |
CA_Get_Channel_Info() failed, probably because the outbound call was terminated. |
106 |
A TDM connect or disconnect request failed because of an adapter hardware problem. |
107 |
A TDM connect or disconnect request failed because the requested port was already connected. This may be caused by other applications running that can make TDM connect and disconnect requests. |
108 |
A TDM connect or disconnect request failed because there was no call present. One of the parties has probably hung up. |
109 |
A TDM connect or disconnect request failed because the Timeslot Manager was not ready. It may be very busy, or not available. |
110 |
A TDM connect or disconnect request failed because of an internal custom server problem. |
111 |
A TDM connect or disconnect request failed because of an unexpected return code from the request. |
112-199 |
Spare: may be used for user-defined values. |