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 ..
Author : Stefan Viljoen
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 1.8.32.3 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 1.8.11.0 and Asterisk 1.8.32.2 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..
MatthewThank you very much for the reply.I must have something seriously wrong somewhere else then – I retested now and the apparent effect is asI describe but your info definitely contradicts that. But youre obviously correct.One more question – ..
guysIm running 1.8.32.3 with CEL logging over ODBC to MariaDB 5.5.41 on the same CentOS 7 machine.Ive noticed that the CDR entries made are all in-time, e. g. the call will take place and the CDR entry is immediately written into the CDR table in ..
allIm running a 1.8.32.3 instance of Asterisk on CentOS 7.About 80 SIP phones connected.Im getting tens of thousands of error messages in the CLI, and callers are having extreme difficulty dialing, they can dial once and then if they try to dial ag..
Regarding this Asterisk instance as discussed previously (Asterisk 1.8.11.0)that was consuming enormous amounts of file descriptors (100 000+ for about50 simultaneous calls) it appears I have managed to solve my problem by upgrading the 1.8.11.0 Aster..
MarkusThanks for the reply, I have set those files previously as well…It seems the problem for me is on my CentOS 7 box that the Asterisk binary does not know that these are the limits, and imposes a 1024 open file limit count for some reason.It se..