TNG4* Custom CSV is correct format but not logging calls

[Belinda Frick]

TNG for Asterisk [TNG4*] Custom CSV is correct format but not logging calls in TNG.

If not expired and everything seems to be ok but still not logging calls we can check for the following entries in the logs:

Typically after a startup you should have the following line:

Code: Select all

[AMI LOG] - Requesting Dialplan...

And then if you NEVER get

Code: Select all

[AMI LOG] - Dialplan Processed

But instead something like "Waiting on Dial plan and peerlist"

Code: Select all

"Waiting on Dial plan and peerlist"

We have found that the AMI timeout settings on Asterisk has to be increased.

By default it is set to 100ms, but we had instances where it needs to be increased to 1000ms or 10 000ms (with Asterisk 1.4.24).

Navigate /etc/asterisk/manager.conf to increase the writetimeout for the [tng] user beyond the 1000 millisecond figure to successfully have TNG start and load dialplan.

See example below:

Code: Select all

[tng]
secret=xxxxxx
deny=0.0.0.0/0.0.0.0
permit=127.0.0.1/255.255.255.0
read=system,call,log,verbose,command,agent,user
write=system,call,log,verbose,command,agent,user
writetimeout=10000

[Belinda Frick]

When using the master.csv file as input for TNG for Asterisk, you do not need the full AMI settings - see changes to 'write' and 'read' options to reduce processing - refer to forum post:

Re: TNG Not Importing Data

Code: Select all

read = system,command ;

only require these to process dialplan and peerlist; reduces overhead and

Code: Select all

write = system,command ;

only require these to process dialplan and peerlist

We do not need the verbose logging, etc. on the Asterisk side for TNG.

NOTE: Thanks to Andrew Engelbrecht for suggestions.