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 [h@restrictedroute-6c29c7be927c93a6bee7baa45eaf40e4: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’