Summary:	ASTERISK-11356: Incoming Call with E&M signalling is not working properly. (AsteriskNow 1.4.9.)
Reporter:	Andre Toshio Kimura (akimura)	Labels:
Date Opened:	2008-02-01 12:12:34.000-0600	Date Closed:	2011-06-07 14:02:46
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_zap
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	We have a TE220 card configured with E&M signalling on AsteriskNow 1.4.9. Asterisk communicates via this signalling to a Adtran TA604 (an IAD). This IAD exchanges MGCP messages with a switch where MGCP test lines are provisioned.             ______            ________            __________            |      |          |        |    E&M   |          | Cisco7960---|  Sw  |---MGCP---| Adtran |T1------T1| Asterisk |---SIP_Phone  -->       |______|    -->   |________|    -->   |__________|   --> When we try to place an incoming call to the SIP lines on Asterisk, and error is occurring as following: -- Starting simple switch on 'Zap/25-1' [Feb  1 13:34:30] WARNING[4621]: chan_zap.c:5630 ss_thread: getdtmf on channel 25: Success -- Hungup 'Zap/25-1' asterisk*CLI> We saw that there was a bug for a similar problem, but specifically for E&M Wink. For us E&M Wink also worked, but we do need to use E&M only. (http://bugs.digium.com/view.php?id=10360) Thank you ****** ADDITIONAL INFORMATION ****** Our configuration files: zaptel.conf: span=1,0,0,esf,b8zs e&m=1-24 loadzone = us defaultzone=us zapata.conf: group=1 context=default signalling=em channel=1-48 rxwink=300 usecallerid=yes hidecallerid=no callwaiting=yes usecallingpres=yes callwaitingcallerid=yes threewaycalling=yes transfer=yes canpark=yes cancallforward=yes callreturn=yes echocancel=yes echocancelwhenbridged=yes rxgain=0.0 txgain=0.0 callgroup=1 pickupgroup=1 immediate=no
Comments:	By: Jason Parker (jparker) 2008-02-08 15:02:42.000-0600 You put that you are using an older 1.4.  You're going to need to try updating to the latest version (I believe asterisknow has 1.4.17 now). By: Jason Parker (jparker) 2008-03-19 14:49:26 Closing, due to lack of response.  Assumed fixed.