I have several users that are reporting dropped calls. I noticed something in the Call Event Log for those calls which seems to be different than calls that are not dropping, but I’m not sure what it tells me or if it’s significant at all.
Normal calls seem to look like this:
|CHAN_START|from-internal|
|CHAN_START|from-trunk|
|ANSWER|from-trunk|
|ANSWER|macro-dialout-trunk|
|BRIDGE_ENTER|from-trunk|
|BRIDGE_ENTER|macro-dialout-trunk|
|BRIDGE_EXIT|macro-dialout-trunk|
|BRIDGE_EXIT|from-trunk|
|HANGUP|from-trunk|
|CHAN_END|from-trunk|
|HANGUP|restrictedroute-c4ca4238a0b923820dcc509a6f75849b|
|CHAN_END|restrictedroute-c4ca4238a0b923820dcc509a6f75849b|
|LINKEDID_END|restrictedroute-c4ca4238a0b923820dcc509a6f75849b|
Note that both parties seem to BRIDGE_EXIT before the HANGUP and CHAN_END occurs.
Here’s what the dropped calls look like:
|CHAN_START|from-internal|
|CHAN_START|from-trunk|
|ANSWER|from-trunk|
|ANSWER|macro-dialout-trunk|
|BRIDGE_ENTER|from-trunk|
|BRIDGE_ENTER|macro-dialout-trunk|
|BRIDGE_EXIT|from-trunk|
|HANGUP|from-trunk|
|CHAN_END|from-trunk|
|BRIDGE_EXIT|macro-dialout-trunk|
|HANGUP|restrictedroute-c4ca4238a0b923820dcc509a6f75849b|
|CHAN_END|restrictedroute-c4ca4238a0b923820dcc509a6f75849b|
|LINKEDID_END|restrictedroute-c4ca4238a0b923820dcc509a6f75849b|
Note that the external side goes through BRIDGE_EXIT, HANGUP, and CHAN_END before the internal side gets to BRIDGE_EXIT.
Is this an indication that the call is dropping due to an issue at the SIP Provider (or carrier on the external end) or is this just a concidence that this pattern seems to appear on the dropped calls?