Stefan-Michael. Guenther (in-put GbR)
2006-Aug-05 06:31 UTC
[asterisk-users] Fax tone detected, but no fax extension for CAPI
Hello, I have a fax server with an AVM Fritzcard that is connected to port number 4 of an EICON DIVA Server 4 BRI. As you can see from the following debug messages, asterisk is accepting the incoming fax call on ISDN4 and forwards it to port number 3 (ISDN3). But at the end the call is terminated before the fax has been sent with the error message "Fax tone detected, but no fax extension for CAPI/ISDN3". Google doesn't find a lot for this message. Does anyone of you have an idea what's going wrong or what might be missing? I have tested it with two different fax numbers and ISDN3 is able to answer and start calls. CONNECT_IND (PLCI=0x1a04,DID=07218304493,CID=5683099,CIP=0x4,CONTROLLER=0x4) > ISDN4: msn='*' DNID='07218304493' MSN == ISDN4: Incoming call '5683099' -> '07218304493' -- ISDN4: CAPI/ISDN4/07218304493-0: 07218304493 matches in context faxout == Started pbx on channel CAPI/ISDN4/07218304493-0 -- ISDN4: info element SETUP == ISDN4: pbx already started on channel CAPI/ISDN4/07218304493-0 > CAPI devicestate requested for ISDN4/07218304493 -- Executing Answer("CAPI/ISDN4/07218304493-0", "") in new stack == ISDN4: Answering for 07218304493> CAPI devicestate requested for ISDN4/07218304493-- Executing Dial("CAPI/ISDN4/07218304493-0", "CAPI/g1/07218304493|10|r") in new stack > data = g1/07218304493 > parsed dialstring: 'g1' 'NULL' '07218304493' '' > capi request group = 2 > parsed dialstring: 'g1' 'NULL' '07218304493' '' == ISDN3: Call CAPI/ISDN3/07218304493-1 (pres=0x00, ton=0x00) -- Called g1/07218304493 == ISDN4: Requested RINGING-Indication for CAPI/ISDN4/07218304493-0 Aug 5 14:20:03 WARNING[9873]: chan_capi.c:3951 capi_signal_progress: wrong channel state to signal PROGRESS -- ISDN4: attempting ALERT in state 6 -- ISDN3: info element CALL PROCEEDING -- CAPI/ISDN3/07218304493-1 is proceeding passing it to CAPI/ISDN4/07218304493-0 -- CAPI/ISDN3/07218304493-1 answered CAPI/ISDN4/07218304493-0 == ISDN4: Requested Indication-STOP for CAPI/ISDN4/07218304493-0 -- Attempting native bridge of CAPI/ISDN4/07218304493-0 and CAPI/ISDN3/07218304493-1 == ISDN4:ISDN3 Requested native bridge for CAPI/ISDN4/07218304493-0 and CAPI/ISDN3/07218304493-1 > CAPI devicestate requested for ISDN3/07218304493> ISDN3: c_dtmf = Y-- Fax tone detected, but no fax extension for CAPI/ISDN3/07218304493-1 ; capi.conf ; [ISDN3] incomingmsn=* isdnmode=MSN immediate=yes context=isdnin ntmode=no controller=3 group=1 ;dialout group callgroup=1 accountcode=ISDN3 devices=2 [ISDN4] incomingmsn=* immediate=yes ntmode=yes controller=4 group=9 callgroup=1 context=faxout accountcode=ISDN4 devices=2 ; extensions.conf ; [faxout] exten => _X.,1,Answer exten => _X.,2,DIAL(CAPI/g1/${EXTEN},10,r) exten => _X.,3,Congestion Thanks for any help, Stefan -- ******************************************** in-put GbR - Das Linux-Systemhaus Stefan-Michael Guenther Moltkestrasse 49 D-76133 Karlsruhe Tel./Fax : +49 (0)721 / 83044 - 98/93 http://www.in-put.de ******************************************** Schulungen Installationen Beratung Support Voice-over-IP-Loesungen ******************************************** -- ******************************************** in-put GbR - Das Linux-Systemhaus Stefan-Michael Guenther Moltkestrasse 49 D-76133 Karlsruhe Tel./Fax : +49 (0)721 / 83044 - 98/93 http://www.in-put.de ******************************************** Schulungen Installationen Beratung Support Voice over IP - L?sungen ********************************************
IAX Provider--> Asterisk/NAT Firewall--> IAXy (192.168.0.x) When a call comes into the Asterisk box, it then rings the IAXy. When the IAXy is answered, I get.. -- IAX2/homeiaxy-6 answered IAX2/teliax-4 -- Channel 'IAX2/teliax-4' unable to transfer -- Channel 'IAX2/homeiaxy-6' unable to transfer This is the same behavior when calling outbound, and I've tried a few other calls to other IAX-capable boxes -- same results. I'd ideally like the IAXy to talk directly to the IAX provider and bypass the Asterisk box after the call is setup. I presume this is just a limitation of IAX and/or the IAXy, but maybe someone could advise me if that is actually the case? Regards, Jeff
Avi Miller
2006-Aug-06 01:42 UTC
[asterisk-users] Fax tone detected, but no fax extension for CAPI
Stefan-Michael. Guenther (in-put GbR) wrote:> I have a fax server with an AVM Fritzcard that is connected to port number 4 > of an EICON DIVA Server 4 BRI.If the inbound is always going to be fax, set faxdetect=off in capi.conf, so that it just runs the default. Otherwise, add a fax extension: [faxout] exten => _X.,1,Answer exten => _X.,2,DIAL(CAPI/g1/${EXTEN},10,r) exten => _X.,3,Congestion exten => fax,1,Dial(CAPI/g1/${EXTEN},10,r) That'll dial out the call when it detects its a fax. hope that helps, Avi
Armin Schindler
2006-Aug-06 02:19 UTC
[asterisk-users] Fax tone detected, but no fax extension for CAPI
On Sat, 5 Aug 2006, Stefan-Michael. Guenther (in-put GbR) wrote:> Hello, > > I have a fax server with an AVM Fritzcard that is connected to port number 4 > of an EICON DIVA Server 4 BRI. As you can see from the following debug > messages, asterisk is accepting the incoming fax call on ISDN4 and forwards > it to port number 3 (ISDN3). > But at the end the call is terminated before the fax has been sent with the > error message "Fax tone detected, but no fax extension for CAPI/ISDN3".The log doesn't show anything about the call is terminated. Anyway, the message "Fax tone detected, but no fax extension for" is just a notice. If you don't have an extension "fax" in your context, nothing else is done. With newer chan_capi you can disable this with faxdetect=off. Armin> Google doesn't find a lot for this message. Does anyone of you have an idea > what's going wrong or what might be missing? > > I have tested it with two different fax numbers and ISDN3 is able to answer > and start calls. > > CONNECT_IND (PLCI=0x1a04,DID=07218304493,CID=5683099,CIP=0x4,CONTROLLER=0x4) > > ISDN4: msn='*' DNID='07218304493' MSN > == ISDN4: Incoming call '5683099' -> '07218304493' > -- ISDN4: CAPI/ISDN4/07218304493-0: 07218304493 matches in context faxout > == Started pbx on channel CAPI/ISDN4/07218304493-0 > > -- ISDN4: info element SETUP > == ISDN4: pbx already started on channel CAPI/ISDN4/07218304493-0 > > CAPI devicestate requested for ISDN4/07218304493 > -- Executing Answer("CAPI/ISDN4/07218304493-0", "") in new stack > == ISDN4: Answering for 07218304493 > > > CAPI devicestate requested for ISDN4/07218304493 > -- Executing Dial("CAPI/ISDN4/07218304493-0", "CAPI/g1/07218304493|10|r") > in new stack > > data = g1/07218304493 > > parsed dialstring: 'g1' 'NULL' '07218304493' '' > > capi request group = 2 > > parsed dialstring: 'g1' 'NULL' '07218304493' '' > == ISDN3: Call CAPI/ISDN3/07218304493-1 (pres=0x00, ton=0x00) > > -- Called g1/07218304493 > == ISDN4: Requested RINGING-Indication for CAPI/ISDN4/07218304493-0 > Aug 5 14:20:03 WARNING[9873]: chan_capi.c:3951 capi_signal_progress: wrong > channel state to signal PROGRESS > -- ISDN4: attempting ALERT in state 6 > > -- ISDN3: info element CALL PROCEEDING > -- CAPI/ISDN3/07218304493-1 is proceeding passing it to > CAPI/ISDN4/07218304493-0 > > -- CAPI/ISDN3/07218304493-1 answered CAPI/ISDN4/07218304493-0 > == ISDN4: Requested Indication-STOP for CAPI/ISDN4/07218304493-0 > -- Attempting native bridge of CAPI/ISDN4/07218304493-0 and > CAPI/ISDN3/07218304493-1 > == ISDN4:ISDN3 Requested native bridge for CAPI/ISDN4/07218304493-0 and > CAPI/ISDN3/07218304493-1 > > CAPI devicestate requested for ISDN3/07218304493 > > > ISDN3: c_dtmf = Y > -- Fax tone detected, but no fax extension for CAPI/ISDN3/07218304493-1 > > ; capi.conf > ; > [ISDN3] > incomingmsn=* > isdnmode=MSN > immediate=yes > context=isdnin > ntmode=no > controller=3 > group=1 ;dialout group > callgroup=1 > accountcode=ISDN3 > devices=2 > > [ISDN4] > incomingmsn=* > immediate=yes > ntmode=yes > controller=4 > group=9 > callgroup=1 > context=faxout > accountcode=ISDN4 > devices=2 > > ; extensions.conf > ; > [faxout] > exten => _X.,1,Answer > exten => _X.,2,DIAL(CAPI/g1/${EXTEN},10,r) > exten => _X.,3,Congestion > > Thanks for any help, > > Stefan > -- > > ******************************************** > in-put GbR - Das Linux-Systemhaus > Stefan-Michael Guenther > Moltkestrasse 49 D-76133 Karlsruhe > Tel./Fax : +49 (0)721 / 83044 - 98/93 > http://www.in-put.de > ******************************************** > Schulungen Installationen > Beratung Support > Voice-over-IP-Loesungen > ******************************************** > > -- > > ******************************************** > in-put GbR - Das Linux-Systemhaus > Stefan-Michael Guenther > Moltkestrasse 49 D-76133 Karlsruhe > Tel./Fax : +49 (0)721 / 83044 - 98/93 > http://www.in-put.de > ******************************************** > Schulungen Installationen > Beratung Support > Voice over IP - L??sungen > ******************************************** > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >
Armin Schindler
2006-Aug-06 05:07 UTC
[asterisk-users] Fax tone detected, but no fax extension for CAPI
On Sun, 6 Aug 2006, Stefan-Michael. Guenther (in-put GbR) wrote:> > > Protocol error layer 1 (broken line or B-channel removed by signalling > > > protocol) > > > > This is the cause of your problem! Your physical ISDN connection is > > broken. Maybe your cross/NT connection is not setup correct. > > > okay, then one last question before I start testing all the options in the > configuration menu of the EICON card: > > Is this error caused by the port where the fax comes in (ISDN4/port 4) or by > the outgoing port (ISDN3/port 3)?It looks like ISDN3, but you can check this by running divactrl mlog -c 3 -o and/or divactrl mlog -c 4 -o to see the cards logs.> P.S: I have spent about two weeks now on this topic, together with the really > helpful support from EICON. If I finish this configuration successfully, I > promise I will write a HOWTO on it and post the link on the list;-))We can add this to the melware.org wiki then.... Armin