Archives : July-2020
Home » 2020 (paged 13)
This is not a big issue… I just noticed a build script that was pulling the16.11.1 release from https://downloads.asterisk.org/pub/telephony/asterisk has started to fail and went to investigate (I need to test a patch for a bugifx). It looks like w..
On Asterisk 16.11.1 when enabling cel I get error with BRIDGE_START and BRIDGE_END events zone-s*CLI> module reload cel The module cel reported a reload failure — Reloading module cel (CEL Engine) [2020-07-10 17:57:01] ERROR[16163]: cel.c:..
1. Im looking for an (anomized) example of a Jitsi Desktop provisioning file compliant with Asterisk?Jitsi Doc mentions it should adhere to Java properties file syntax (see[1]) but a working example would help.If this example file included the follow..
in dialplan -Asterisk 16.2 from Debian Buster- we have same = n,Dial(PJSIP/101&PJSIP/102&PJSIP/103,15,tT) If thew call is not answered after 20 seconds, we launch a new dial with same and/or other extensions same = n,Dial(PJSIP/101&PJSIP/104&PJSIP/110,20,..
Does anyone know of any projects that would allow you to use Redis in place of AstDB? By in place of I dont mean for what Asterisk needs but to store values. For instance for CNAM currently we need to use an AGI to connect to redis to pull CNAM. So..
all Im running an Asterisk 13.22.0 instance on CentOS 7 – I7-8700 12 core HT with 16GB of RAM. The server maintains a total active call count of approx 285 calls with 440 channels at any one time. The totals never go below 200 calls concurrently acti..
All,I have polycom phones setup in an office connected to a cloud asterisk server. The polycom phones can call out just fine – audio just fine. However a call coming into the cloud asterisk answers fine – get the autoattendant, enter the extension ..
We have a box up and we are starting to see a lot of Exceptionally long queue length queuing in the logs. From all the research so far it seems like this leads to their systems crashing and being unreachable. In our case the box remains up and ta..
Hi. Ive just upgraded from Asterisk 13 to Asterisk 16 (as part of a Debian & Devuan version upgrade). Whenever Asterisk starts, Im now getting entries such as the following in my log file: WARNING[13905]: logger:0 in ***: Log queue threshold (1000) exceed..
Currently Im experiencing crashes on Asterisk more recently, see messages below (crashed reason: segfault signal 6).abrt-hook-ccpp[19864]: Process 7082 (asterisk) of user 0 killed by SIGABRT- dumping coreasterisk: ERROR[15373][C-0004e304]: astobj2.c:..