Calls disconnected ramdomly during calls

Seeking reason for call hang-ups. Would like to see more specific info on hang-ups like which party, and if any errors were involved. It takes a lot of effort to seek the reason for a disconnect so any help would be appreciated. For example, could the CDR trace be enhanced to display who hung up and note if any errors were involved. It would be nice if the log also made this more clear for those of us not conversant in reading the log.

Do the following log entries shed any light on my problem?

Thanks

[2016-11-07 10:57:00] VERBOSE[5219][C-000000a8] app_dial.c: – IAX2/VOIPms-3652 is making progress passing it to SIP/301-0000028b
[2016-11-07 10:57:00] VERBOSE[5219][C-000000a8] app_dial.c: – SIP/301-0000028b requested media update control 26, passing it to IAX2/VOIPms-3652
[2016-11-07 10:57:04] VERBOSE[5219][C-000000a8] app_dial.c: – IAX2/VOIPms-3652 is ringing
[2016-11-07 10:57:21] VERBOSE[5219][C-000000a8] app_dial.c: – IAX2/VOIPms-3652 answered SIP/301-0000028b
[2016-11-07 10:57:21] VERBOSE[5219][C-000000a8] bridge_channel.c: – Channel SIP/301-0000028b joined ‘simple_bridge’ basic-bridge <44dd5f63-2abe-4036-916e-f83e59f4d748>
[2016-11-07 11:09:05] VERBOSE[5219][C-000000a8] bridge_channel.c: – Channel SIP/301-0000028b left ‘simple_bridge’ basic-bridge <44dd5f63-2abe-4036-916e-f83e59f4d748>
[2016-11-07 11:09:05] VERBOSE[5219][C-000000a8] app_macro.c: == Spawn extension (macro-dialout-trunk, s, 23) exited non-zero on ‘SIP/301-0000028b’ in macro ‘dialout-trunk’
[2016-11-07 11:09:05] VERBOSE[5219][C-000000a8] pbx.c: == Spawn extension (restrictedroute-6c29c7be927c93a6bee7baa45eaf40e4, 8452068199, 8) exited non-zero on ‘SIP/301-0000028b’
[2016-11-07 11:09:05] VERBOSE[5219][C-000000a8] pbx.c: – Executing [[email protected]:1] Hangup(“SIP/301-0000028b”, “”) in new stack
[2016-11-07 11:09:05] VERBOSE[5219][C-000000a8] pbx.c: == Spawn extension (restrictedroute-6c29c7be927c93a6bee7baa45eaf40e4, h, 1) exited non-zero on ‘SIP/301-0000028b’

Your phone hung up

So can you suggest how to discover why the PBX thinks the phone hung up?

Because it did, you need to ask your phone or the network. The PBX is acting appropriately

Ok… Do SIP phones just vanish when they hang up or do they normally go through a “hang up” sequence? In other words, how does the PBX know the phone hung-up?

There are lots of reasons why a SIP phone will hang up. Some of them are physical (e.g., a button got pushed somewhere or the unit lost power) and some are logical (e.g., the network got congested and the phone just quit or the phone rebooted because of a fault).

The problem with troubleshooting intermittent problems is that they are so hard to trigger, but if you want to try something, you can start a Wireshark packet capture of the phone and let it run until a call gets disconnected. With the Wireshark output, you should be able to see why the phone decided to escape the call.

Thanks. In this case, the phone calls had been under way for some time and the call just went away. So… yes I would like to pin down why. I would like to see the CDR say, something like, “Caller Hangup” or “Called Hangup”. Even better, if a reason code was part of the process of hanging up then I would like to have a reason displayed if not a normal hangup. The system log above reported "Hangup(“SIP/301-0000028b”) which looks like the extension and some code. Let me Google it. Nope no initial hits on the web. I wonder what 28b means.

is the id of the call, neither the CLI nor the CDR will show who “hungup”, but turn on sip debugging for that extension/ip and you would see the SIP transactions and why the call was hungup.