- Joined
- Dec 4, 2009
- Messages
- 2
- Reaction score
- 0
When i end an unanswered external call from a client on the 3cx, the called party still rings (for at least about 30 seconds).
I have traced the calls and found that the client is sending a "cancel" request to the 3cx, and get a "200 ok" and "487 request terminated" as it should. The call is terminated from the clients point of wiew. The 3cx then sends a "bye" request (instead of a "Cancel" request?) to the sip provider and the sip provider returns "200 ok" to the "bye" request. The 3cx seems to disconnect (green light in the status wiew). The problem is that the sip provider does not disconnect the ringing on the outbound leg. It seems to me that unanswered calls should be terminated by a "cancel" rather than a "bye" request. Is it possible to make the 3cx send a "cancel" request instead of a "bye" request if an external call is canceled before it is answered? Or is there other workarounds?
Morten
I have traced the calls and found that the client is sending a "cancel" request to the 3cx, and get a "200 ok" and "487 request terminated" as it should. The call is terminated from the clients point of wiew. The 3cx then sends a "bye" request (instead of a "Cancel" request?) to the sip provider and the sip provider returns "200 ok" to the "bye" request. The 3cx seems to disconnect (green light in the status wiew). The problem is that the sip provider does not disconnect the ringing on the outbound leg. It seems to me that unanswered calls should be terminated by a "cancel" rather than a "bye" request. Is it possible to make the 3cx send a "cancel" request instead of a "bye" request if an external call is canceled before it is answered? Or is there other workarounds?
Morten