Thanks Tim, I tried your suggestion below the logs: -- Accepting AUTHENTICATED call from xxx.xx.xx.xx: > requested format = ulaw, > requested prefs = (), > actual format = ulaw, > host prefs = (ulaw), > priority = mine -- Executing [xxx1463@fax-out:1] Dial("IAX2/503-7761", "dahdi/g3/wwxxx1463") in new stack -- Called g3/wwxxx1463 -- DAHDI/4-1 answered IAX2/503-7761 -- Registered IAX2 '503' (AUTHENTICATED) at xxx.xx.xx.xx:4570 [Aug 1 09:04:59] NOTICE[3392]: chan_iax2.c:8486 update_registry: Restricting registration for peer '503' to 300 seconds (requested 60) -- Registered IAX2 '503' (AUTHENTICATED) at xxx.xx.xx.xx:44145 [Aug 1 09:05:03] NOTICE[3391]: chan_iax2.c:8486 update_registry: Restricting registration for peer '503' to 300 seconds (requested 60) -- Hungup 'DAHDI/4-1' == Spawn extension (fax-out, xxx1463, 1) exited non-zero on 'IAX2/503-7761' -- Hungup 'IAX2/503-7761'
[root@drew home]# faxstat -s HylaFAX scheduler on host.xxxxx.com: Running Modem ttyIAX0 (+1.xxx.8626): Running and idle JID Pri S Owner Number Pages Dials TTS Status 9 126 S root xxx1463 0:1 1:12 16:10 No carrier detected Any suggestions? Thanks a bunch! -----Original Message----- From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Tim Nelson Sent: Wednesday, August 01, 2012 8:42 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] Asterisk Dahdi 1.6.2.23 Iaxmodem ----- Original Message ----- > Hello Ruben, > I belive the problem is not hylafax, is the way dahdi is configure, > here is a part of the call log: > > -- Accepting AUTHENTICATED call from xxx.xx.xx.xx: > > requested format = ulaw, > > requested prefs = (), > > actual format = ulaw, > > host prefs = (ulaw), > > priority = mine > -- Executing [xxx1463@fax-out:1] Dial("IAX2/503-2966", > "dahdi/g3/xxx1463") in new stack > -- Called g3/xxx1463 > -- DAHDI/4-1 answered IAX2/503-2966 > > As you can see above dahdi answered and IAXmodem thinks is the remote > fax machine answered. That's what I'm trying to change. > No, that simply means DAHDI successfully made the call out your POTS line, and Asterisk has 'bridged' the call between your IAXmodem peer and the DAHDI channel. You could be experiencing some digit loss when dialing, causing the calls to *sometimes* go through or not. Try adding a 'ww' to your dialstring to allow the POTS line to settle before dialing: Dial(DAHDI/g3/ww${EXTEN}) --Tim -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users