Dropped call on DAHDI - Channel 0/4 got hangup request

I had a dropped call on a PRI yesterday. I searched the logs and found the following:

[2018-08-14 15:33:21] VERBOSE[14981][C-00001b23] sig_pri.c: Span 1: Channel 0/4 got hangup request, cause 16

The question is, did the hangup request come from the system or the calling party?

The hangup came from the DAHDI channel, the remote party (or the provider) ended the call.

1 Like

Thanks Lorne. I didn’t see a bye message in the logfiles from the phone so I was leaning that way.

1 Like

By default, you won’t see the SIP BYE message the Asterisk full log. In those cases, the clue to who first ends the call comes from the sequence when they leave the bridge.

Outbound call is answered by remote party:

[2018-08-15 17:12:30] VERBOSE[10164][C-00000005] app_dial.c: PJSIP/SIP-TRUNK-0000000c answered PJSIP/5005-0000000b

remote channel and local channel are bridged:

[2018-08-15 17:12:30] VERBOSE[10249][C-00000005] bridge_channel.c: Channel PJSIP/SIP-TRUNK-0000000c joined 'simple_bridge' basic-bridge <831d6d5c-918b-4ad9-910f-186b925d8bc5>
[2018-08-15 17:12:30] VERBOSE[10164][C-00000005] bridge_channel.c: Channel PJSIP/5005-0000000b joined 'simple_bridge' basic-bridge <831d6d5c-918b-4ad9-910f-186b925d8bc5>

Here we can see that the trunk channel leaves the bridge first, indicating remote user hung up first:

[2018-08-15 17:12:38] VERBOSE[10249][C-00000005] bridge_channel.c: Channel PJSIP/SIP-TRUNK-0000000c left 'simple_bridge' basic-bridge <831d6d5c-918b-4ad9-910f-186b925d8bc5>
[2018-08-15 17:12:38] VERBOSE[10164][C-00000005] bridge_channel.c: Channel PJSIP/5005-0000000b left 'simple_bridge' basic-bridge <831d6d5c-918b-4ad9-910f-186b925d8bc5>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.