Summary:ASTERISK-21237: detect PRI_EVENT_NOTIFY(16) instead of PRI_EVENT_HANGUP_REQ(15)
Reporter:Fabrizio Lazzaretti (fabsoft)Labels:
Date Opened:2013-03-12 07:10:50Date Closed:2013-03-12 11:31:40
Versions:11.2.1 Frequency of
Description:Im testing a connection beetwen asterisk and ericson MD110 by using a redfone tdmoe device. The dahdi sub driver is ethmf.
All is working except the callee disconnect event.
I already tryed to set hanguponpoloarityswitch to yes without fix the problem,
also, the caller leg receives a "beep" similar to a user suspension and not a busy tone(in band).
I suspect the problem affect the md110 but maybe there is a solution.
the debug output show me what happen when the callee part hangs up:

.... outgoing call to MD110.. all is ok


PRI Span: 1
PRI Span: 1 < Protocol Discriminator: Q.931 (8)  len=8
PRI Span: 1 < TEI=0 Call Ref: len= 2 (reference 9/0x9) (Sent to originator)
PRI Span: 1 < Message Type: NOTIFY (110)
PRI Span: 1 < [27 01 80]
PRI Span: 1 < Notification Indicator (len= 3): Ext: 1  User suspended (0)
PRI Span: 1 Received message for call 0x1cd2c30 on link 0x1bf9a20 TEI/SAPI 0/0
PRI Span: 1 -- Processing IE 39 (cs0, Notification Indicator)
Span 1: Processing event PRI_EVENT_NOTIFY(16)

the event received is PRI_EVENT_NOTIFY(16) instead of PRI_EVENT_HANGUP_ACK(9).

can i handle that event is a way to generate a hangup request ?

Comments:By: Richard Mudgett (rmudgett) 2013-03-12 09:56:04.345-0500

Thanks for your comments. This does not appear to be a bug report and we are closing it. We appreciate the difficulties you are facing, but it would make more sense to raise your question in the asterisk users mailing list.

A NOTIFY message does not indicate a hangup.  That is what the DISCONNECT, RELEASE, and RELEASE COMPLETE messages are for.

This looks more like a configuration problem than anything else.