[asterisk-users] Automatic call-out problem

[Tzafrir Cohen]

On Fri, Jan 18, 2008 at 01:14:51PM +0100, Artifex Maximus wrote:
> Hello!
> 
> My setup is Asterisk 1.2.26 with Zaptel 1.2.22.1, libpri-1.2.7 on
> Fedora Core 4. I am making automatic call-out campaign with this setup
> on 4 PRI. The scripts for this:
> 
> ====================================================================
> 
> caller php script write this to outgoung folder:
> 
> fwrite($outfile,"Channel: Zap/g1/$phonenumber\n");
> fwrite($outfile,"MaxRetries: 0\n");
> fwrite($outfile,"RetryTime: 5\n");
> fwrite($outfile,"WaitTime: 20\n");
> fwrite($outfile,"Context: 0100q\n");
> fwrite($outfile,"Callerid: $dbid\n");
> fwrite($outfile,"Extension: $phonenumber\n");
> fwrite($outfile,"Set: par_telszam=$phonenumber\n");
> 
> ====================================================================
> 
> extensions.conf:
> 
> [0100q]
> exten => _XXXX.,1,Wait(1)
> exten => _XXXX.,n,Set(__TRIES=1)
> exten => _XXXX.,n,Set(__FMT_DATE=%Y-%m-%d %H:%M:%S)
> exten => _XXXX.,n,Set(__SZAM=${par_telszam})
> exten => _XXXX.,n,System(echo -e
> "${SZAM}\,felvette\,${STRFTIME(${EPOCH},,${FMT_DATE})}" >>
> /tmp/0100q_0.txt)

What is this for? Why would you invent your own personal logging and not
use Asterisk's one?

Use a unique-enough message and Verbose. What you use is quite
inefficient.

Anyway, why not show us a trace from the CLI?

  set verbose 3

And see what happens when you drop a call file.

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir