asterisk users - Nov 2004 - Problems with call files (/var/spool/asterisk/outgoing)

I've seen other posts about this problem, but I haven't found a
solution.

I'm dumping eight call files into the "outgoing" directory at one
time.
  Three of the calls are successful while the other five are lost.  Here 
is the call file:

Channel: Zap/g2/3036701917
MaxRetries: 1000
RetryTime: 60
WaitTime: 45
Application: TxFAX
Data: <filename>.tiff|caller

Note: All calls are going to the same fax machine, so some attempts on 
the second line will get a busy signal (there are two POTS lines in 
group 2).

In the messages log, I get many of the following set:

Unable to request channel Zap/g2/3036701917
Call failed to go through, reason 0
Can't change device with no technology!

In message log I also get:
Call completed to Zap/g2/3036701917
for the successful calls.

Is there a workaround for this?  If an outgoing call can't get a free 
line or gets a busy then I would want it to be retried later.

I'm using today's cvs and spandsp-pre6.

Thanks,
Mike

P.S.  I've changed the call file to "Channel: Zap/27/3036701917"
so it
uses only one outgoing POTS line.  With this change, I'm still getting 
the "Unable to request..." message set, but I'm not losing call
files
(the calls are being retried).  All eight faxes are successfully 
delivered using one outgoing line.

This tells me that getting a busy signal causes the call file to be 
removed and not retried. Bug?

Cheers,


-- 
Michael Welter
Introspect Telephony Corp.
Denver, Colorado US
+1.303.674.2575
mike@introspect.com
www.introspect.com

Michael Welter wrote:
<snip>
> 
> Channel: Zap/g2/3036701917
> MaxRetries: 1000
> RetryTime: 60
> WaitTime: 45
> Application: TxFAX
> Data: <filename>.tiff|caller
> 
> Note: All calls are going to the same fax machine, so some attempts on 
> the second line will get a busy signal (there are two POTS lines in 
> group 2).
> 
<snip>
> 
> I'm using today's cvs and spandsp-pre6.
> 
<snip>
> 
> 
The problem with the call files is that the busy tone is not being 
detected, and the reason the busy tone is not detected is because the 
fax tone (CNG) is being injected onto the line by the TxFax application.

When I remove "|caller" from the call files (no CNG tones), all fax 
calls are properly sent (busy is detected by * and the call retried). 
However, by removing "|caller| and not sending the CNG tones, some fax 
receivers will not be able to properly handle the call.

Is there some way for * to detect busy tones while ignoring (filtering) 
the CNG tones?

Thanks,
Mike

-- 
Michael Welter
Introspect Telephony Corp.
Denver, Colorado US
+1.303.674.2575
mike@introspect.com
www.introspect.com

Hello,

 
> The problem with the call files is that the busy tone is not being
> detected, and the reason the busy tone is not detected is because the
> fax tone (CNG) is being injected onto the line by the TxFax application.
> 
> When I remove "|caller" from the call files (no CNG tones), all
fax
> calls are properly sent (busy is detected by * and the call retried).
> However, by removing "|caller| and not sending the CNG tones, some fax
> receivers will not be able to properly handle the call.
> 
> Is there some way for * to detect busy tones while ignoring (filtering)
> the CNG tones?
Maybe by setting the following in zapata.conf

;faxdetect=both
;faxdetect=incoming
;faxdetect=outgoing
;faxdetect=no

-- 
Nicol?s Gudi?o
Buenos Aires - Argentina