we have TNG implemented on Asterisk free PBX locally on server, the calls not pulling into tng, is there a way i can check what is the cause of this,
i have kill the tng connection, and started daemon with ./tng -D
on the logs files i get the follwoing.
[root@cal-mun-pbx logs]# tail -f 20230206/tng.log
2023-02-06 14:10:38:375 [22.214.171.124] - SynchronizeData: 990000 records scanned
2023-02-06 14:10:38:377 [126.96.36.199] - SynchronizeData: 1000000 records scanned
2023-02-06 14:10:38:379 [188.8.131.52] - SynchronizeData: Entering date range now.
2023-02-06 14:10:38:564 [184.108.40.206] - 565 Data records synchronized
2023-02-06 14:11:31:971 [220.127.116.11] - [AMI LOG] - Waiting on Dial Plan and Peer List
2023-02-06 14:48:16:432 [18.104.22.168] - [AMI LOG] - Waiting on Dial Plan and Peer List [Repeated 36 times]
2023-02-06 14:48:16:432 [22.214.171.124] - admin disconnected after timeout
2023-02-06 14:48:16:432 [126.96.36.199] - gail disconnected after timeout
2023-02-06 14:48:24:316 [188.8.131.52] - User gail connected from 172.16.1.53
2023-02-06 14:48:37:013 [184.108.40.206] - [AMI LOG] - Waiting on Dial Plan and Peer List
TNG needs to download the dial plan from the Asterisk first to be able to detect the call direction of the calls.
It looks like it is attempting to download the dialplan and not receiving the full dialplan.
Is the TNG user and password for the AMI still correct and working?
HI Leon van Heerden,
Yes, all still same, where is the tng user located? does it need to be on Asterisk “free pbx” as user?
Use CDR File=1
CDR File Location=/var/log/asterisk/cdr-custom/.cs
Strip Breakout Digit=0
HI, i can see the user logged in.
- Yes file exist
- last message says ami user disconnects
asterisk -rx “show manager connected”
Username IP Address
2023-01-13 04:59:02:018 [220.127.116.11] - AMI Disconnected:0 -
2023-01-13 04:59:02:044 [18.104.22.168] - AMI Exception:Connection Closed Gracefully.
2023-01-13 04:59:02:169 [22.214.171.124] - AMI Exception:ConnectToAsterisk: Socket Error # 111Connection refused.
2023-01-13 04:59:06:545 [126.96.36.199] - AMI connected to port 5038 on 127.0.0.1
is there a way to see the process status on the calls being pulled in to TNG.
it looks like the TNG user are busy.
when preforming top
25342 root 25 0 933m 723m 2432 R 110.5 18.3 219:21.03 tng