Total Active Calls from Dashboard Far More Calls than Exist

We are running FreePBX
NAT = Yes, Static IP

We are experiencing lots of very high active calls anywhere from over a hundred to several hundred. This is displayed from the dashboard when looking at the statistics.

When looking at the full log file I see lots of the following:

[2018-04-16 08:41:26] DEBUG[35033][C-0000033e] format_wav.c: Skipping unknown block ‘LIST’
[2018-04-16 08:37:35] WARNING[34090][C-0000031e] chan_sip.c: This function can only be used on SIP channels.
[2018-04-16 08:37:35] ERROR[34030][C-000002ef] res_pjsip_header_funcs.c: This function requires a PJSIP channel.
[2018-04-16 08:37:35] WARNING[34092][C-0000031e] app_dial.c: Unable to create channel of type ‘SIP’ (cause 20 - Subscriber absent)
NOTICE[13090] chan_sip.c: Disconnecting call ‘SIP/TwilioIn4-00000705’ for lack of RTP activity in 31 seconds
[2018-04-16 08:37:49] WARNING[13090] chan_sip.c: Autodestruct on dialog ‘[email protected]:5060’ with owner SIP/1322-00000706 in place (Method: BYE). Rescheduling destruction for 10000 ms

Other symptoms we are seeing is when you place a call from the outside to the PBX, I hear the bleep and then a long period of silence and then eventually I hear the IVR announcement play.
When transferring a call, there is a long delay in the pickup.

This is a system that has been running very stable for quite some time. Two things have recently changed. We recently installed the datadog-agent v6 but we have since removed that agent. The other is that we moved the cdr and cel tables to another folder with more disk space. I had initially created a symlink to the whole directory but that apparently according to some docs I read was not a good thing to do. I have since put the .FMT files back to where they were and only symlinked the MYI and MYD files and initially that seemed to make everything run fine. After a couple days though, we are experiencing the issue again. I have checked the tables by running “check table cdr” and “check table cel” and they show as OK.

Any suggestions?

Additionally, when I reboot the server, asterisk will not start. I have to start it manually by using “service asterisk start” and then it starts fine. Here are some of the logs I found after restarting.

(config category=‘1234’ global force_rport=‘Yes’ peer/user force_rport=‘No’)
[2018-04-16 08:56:09] WARNING[13926] chan_sip.c: !!! PLEASE NOTE: Setting ‘nat’ for a peer/user that differs from the global setting can make
[2018-04-16 08:56:09] WARNING[13926] chan_sip.c: !!! the name of that peer/user discoverable by an attacker. Replies for non-existent peers/users
[2018-04-16 08:56:09] WARNING[13926] chan_sip.c: !!! will be sent to a different port than replies for an existing peer/user. If at all possible,
[2018-04-16 08:56:09] WARNING[13926] chan_sip.c: !!! use the global ‘nat’ setting and do not set ‘nat’ per peer/user.
[2018-04-16 08:56:09] WARNING[13926] chan_sip.c: !!! (config category=‘1235’ global force_rport=‘Yes’ peer/user force_rport=‘No’)
[2018-04-16 08:56:09] NOTICE[13926] pbx_ael.c: File /etc/asterisk/extensions.ael not found; AEL declining load
[2018-04-16 08:56:09] ERROR[13926] pbx_dundi.c: Unable to load config dundi.conf
[2018-04-16 08:56:09] NOTICE[13926] func_odbc.c: Unable to load config for func_odbc: func_odbc.conf
[2018-04-16 08:56:10] WARNING[13926] res_hep_rtcp.c: res_hep is not loaded or running; declining module load
[2018-04-16 08:56:10] WARNING[13926] res_hep_pjsip.c: res_hep is not loaded or running; declining module load
[2018-04-16 08:56:10] WARNING[13926] app_festival.c: No such configuration file festival.conf
[2018-04-16 08:56:10] NOTICE[14041] chan_sip.c: Peer ‘204’ is now Reachable. (164ms / 2000ms)
[2018-04-16 08:56:10] NOTICE[14041] chan_sip.c: Peer ‘203’ is now Reachable. (70ms / 2000ms)
[2018-04-16 08:56:10] ERROR[13926] chan_unistim.c: Unable to load config unistim.conf
[2018-04-16 08:56:10] ERROR[13926] app_amd.c: Configuration file amd.conf missing.

Can you restore from a backup? That might be the quickest path to stability.

Yes, but I was hoping to avoid that. Thanks.

Assuming you are logged in as root, in which case you definitely don’t want to start asterisk this way. Use:

fwconsole restart

Could starting asterisk using “service asterisk start” cause the issues I’m having? It seems to me that the not starting on reboot is symptom #1.

If you want to use “service asterisk start” or perhaps “systemctl start asterisk” if using systemd , you need to make sure that the AST_USER and AST_GROUP are “asterisk”. For redhat and that will be defined in /etc/sysconfig/asterisk in debian that would be in “/etc/default asterisk” , either recipe should be able to start asterisk properly as a system service.


This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.