[asterisk-users] About .call files when the congestion is on my side

[Anselm Martin Hoffmeister]

Am Montag, den 15.10.2007, 11:26 +0300 schrieb Cosmin Prund:
> Hello everyone.
> 
>  
> 
> I’m working on an application that needs to automatically send faxes.
> To send the faxes I create .call files but the .call files mostly fail
> because my lines are always congested within business hours! Is there
> any trick I can use to give the end user a better chance at actually
> receiving the faxes?

Are you aware of the MaxRetries, RetryTime and WaitTime in your
call-files? You can set quite large numbers, e.g. a RetryTime of
15 minutes and a MaxRetries of 32 would try for up to 8 hours.

Note though that any "answered" call will stop the retry cycle.
This is embarassing for Zap channels that cannot detect remote
ringing / remote busy reliably. As you use ISDN this should not
be a problem

> I already tried using the local channel for dialing (so I can put in
> there a loop that waits for a line to be available) but this doesn’t
> work because I’m sending faxes using chan_capi’s capicommand(sendfax)
> – and that command requires an chan_capi channel, it doesn’t like the
> “local” channel. Besides, looping in the dialplan would probably
> interfere with the “Wait” option in the .call file so that’s a really
> bad solution. 

If you want to do this (looping) use MaxRetries = 0. I do not understand
why having the remote side connecting to a local extension that does
faxing would not work. Or is it that the CAPI FAX stuff will only work
on unAnswer()ed channels?

Can you provide an example .call file?

Regards,
Anselm