Summary:	ASTERISK-06922: E1 PRI Disconnect audio message indication
Reporter:	Javier Ergas (jergas)	Labels:
Date Opened:	2006-05-08 11:58:32	Date Closed:	2011-06-07 14:08:20
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) cli_futuro.txt ( 1) debug_pri_contaline.log
Description:	We setup Asterisk systems for our customers and for local Telco’s customers in Chile using Digium Hardware. We have the same problem with Q.931 disconnect process on every E1 Asterisk system installed, and we found out there are other users experiencing the same problem, here in Chile and in other countries. Calling to a disconnected number or any not operational number, the telco sends a Disconnect message, a cause (on the Asterisk’s Hangupcause variable) and an audio message notifying the disconnection cause to the user. Asterisk does not allow the user to hear the audio message form the telco, instead it cuts off the call. Any other legacies PRI PBX I've tested allow the user to hear the audio message from the telco. A few months ago I was dealing with this problem, someone suggested using the Hangupcause code, and it solved the problem momentarily. We wrote a script to play an internal audio message on the Asterisk Box depending on the Hangupcause variable when calling a not operational number, but we are not happy with that solution, we would like to have the same behavior as the legacies systems. I’m attaching a full log and links to some posts to better explain the problem. ****** ADDITIONAL INFORMATION ****** http://lists.digium.com/pipermail/asterisk-users/2006-April/146828.html http://lists.digium.com/pipermail/asterisk-users/2005-December/133257.html http://lists.digium.com/pipermail/asterisk-users/2004-April/036531.html
Comments:	By: Serge Vecher (serge-v) 2006-05-08 12:21:39 this probably belongs in libpri project, but can't change it. By: Serge Vecher (serge-v) 2006-05-25 20:53:20 jergas: is this an issue in 1.2.7.1? By: Javier Ergas (jergas) 2006-05-26 07:56:42 Yes it is an issue in 1.2.7.1. you can see it on the attached file. By: Matthew Fredrickson (mattf) 2006-07-06 16:59:19 Suspended due to inactivity.