Summary:ASTERISK-22125: PRI_EVENT_NOTIFY option to give a "code of event"
Reporter:Emiliano (emilianosch)Labels:
Date Opened:2013-07-18 20:32:06Date Closed:2013-07-19 11:58:28
Versions:Frequency of
Environment:AsteriskNow 2.0.2 + yum updateAttachments:

When i make a call from my E1 PRI (TelcoA) to a analog line (TelcoB).
And the user of the analog line hangup, the TelcoA send to me a PRI_EVENT_NOTIFY and 60 seconds later send a DISCONNECT.

What are the posibility to give a "code" when a PRI_EVENT_NOTIFY appears to work with the dialplan to hangup this outbound calls?

Sorry for my bad english.

Comments:By: Richard Mudgett (rmudgett) 2013-07-19 11:51:54.788-0500

Features requests are no longer submitted to or accepted through the issue tracker. Features requests are openly discussed on the mailing lists [1] and Asterisk IRC channels and made note of by Bug Marshals.

[1] http://www.asterisk.org/support/mailing-lists

This is not a trivial request.

1) The NOTIFY message Notification indicator code says the far end was suspended.  According to Q.931 that code is used when the far end used the SUSPEND procedure described in Q.931 section 5.6.2.  Receipt of this NOTIFY message does *not* mean that the far end hung up the call because the call could be resumed by the far end using the RESUME procedure described in Q.931 section 5.6.4.

2) Dialplan does not execute while a call is in progress.  It executes to setup the call and to deal with call hangup (h exten).  When this NOTIFY message comes in, the call is already established so dialplan is no longer running.

You could modify the source code to respond to the receipt of this message by hanging up the call.  The location in the Asterisk source code dealing with the message is in the sig_pri.c file, routine pri_dchannel() switch case PRI_EVENT_NOTIFY.  However, any patch resulting from this is not likely to be acceptable for inclusion.  I cannot see this being anything but a work around for a misbehaving far end.

By: Birger "WIMPy" Harzenetter (wimpy) 2013-07-19 12:21:30.374-0500

Looks like the other end accidentally put the call on hold instead of hanging up.

Not uncommon for POTS users. When they hangup and lift the handset immediately again to place another call can result in a too short hangup that is interpreted as a flash signal to put the call on hold.

By: Emiliano (emilianosch) 2013-07-19 14:52:11.836-0500

Hi, thanks for the replies...

More information: In the trace I make and hang up the call...

In conclusion the telco send this messages...