Simultaneous Caller/callee Hangup; Hangup Extensions Execute Only Once; Unable To Determine If Destination Channel Up

Home » Asterisk Users » Simultaneous Caller/callee Hangup; Hangup Extensions Execute Only Once; Unable To Determine If Destination Channel Up
Asterisk Users 2 Comments

Hello

This is a question regarding whether there’s any way within hangup extensions to determine whether the caller or callee leg (or both) of a bridged call has hung up. The test case I have is running under Asterisk 1.8.17.0, but the behaviour is observed in 1.8.18.0 (and also
1.6.2.18).

Within the dialplan, the Dial() application with the “F” flag, so that once the caller hangs up, the dialplan jumps to a new priority which enables the called party to enter some digits which describe the outcome of the call. Also, the “g” flag is used to attempt to continue execution of the dialplan if the called party hangs up.

Minimally, the dialplan is covered by the following:

[test]
exten => _1000,1,Set(_CALLER_HUNGUP

2 thoughts on - Simultaneous Caller/callee Hangup; Hangup Extensions Execute Only Once; Unable To Determine If Destination Channel Up

  • No. I don’t see this as a bug. Priority 4 and 10 can only execute while the channel is not hung up. This is normal dialplan execution. Only the h exten can execute on a hung up channel. Since both channels are hanging up at the same time, neither priority 4 nor 10
    are able to get executed.

    The new pre-dial and hangup handler features in Asterisk 11 would be a solution to your problem. Otherwise, I don’t really see a solution without rethinking your post call processing.

    Richard

  • Thanks for the info Richard. I guess we need to be looking at Asterisk 11. Is there no way to determine whether another channel is up from within an h exten?

    Thanks again

    John Signature