AllI have an Asterisk 220.127.116.11 instance that will at random intervals stop logging CDR data to MSSQL via FreeTDS.On investigation Ill find that the FreeTDS module has been unloaded somehow. It is not listed in cdr show status or show module like.Try..
all Im trying to limit the maximum concurrent calls on my Asterisk to try and mitigate another problem I posted about earlier. Ive edited /etc/asterisk/asterisk.conf And uncommented this line, and put a value of 60 in there: maxcalls = 60 in an eff..
guys Does anybody have any opinion on what causes tens of thousands of these messages per hour to pop up in the CLI: [Jun 30 14:24:59] WARNING: chan_sip.c:4057 __sip_autodestruct:Autodestruct on dialog email@example.com:5060w..
JonathanThx for the reply.Yup, have tried them, may just be our incompetence and inexperience with Asterisk, but cannot get either of them to work right with our particular setup.Due to legacy issues we run very different dialplans at 17 different sit..
allI get this warning in the Asterisk CLI about once every ten minutes or so:[Nov 23 14:47:36] WARNING: res_odbc.c:647ast_odbc_prepare_and_execute: SQL Execute returned an error -1: HY000:[MySQL][ODBC 5.1 Driver][mysqld-5.1.73]Deadlock found w..
JoshuaThanks for the response.Interesting that you mention that toll-free numbers can do this, this problem trunk happens to receive calls from the national telecoms provider here (Telkom SA) sourced from a toll-free number. The SIP trunk provider ..
GuysIve got a strange problem – on my asterisk instance, when a call starts to ring, I do core show channeland I get the usual output with the duration and billsec fields included.For most of my calls, things are normal, e. g. duration field starts increment..
CarlosI have experienced something similar starting Asterisk 18.104.22.168 on CentOS 7on commodity / whitebox hardware.The problem was that Asterisk was starting too quickly in the systemd startup sequence, before the required services it needs to run w..
CarlosWe had similar issues with Asterisk 22.214.171.124 and Asterisk 126.96.36.199 with timerfd and pthread timing.The server instance would run for 20 or 30 minutes and then producde legions of error lines about timerfd or pthread, whichever we were using…
ViniciusThanks for replying.bases.maybe the DBMS is using too much CPU and starving Asterisk?I dont think so – I think I have a locking issue in the DB specifically with my stored procedure -and- Asterisk trying to access the CEL table simultaneously.L..