VICIDIALNOW Audio quality, warnings and notices

[tgalan]

]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x8ac81c0', 9 retries!
Apr 1 15:52:39 WARNING[2487]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x8ac81c0', 9 retries!
Apr 1 15:52:39 WARNING[2487]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x8ac81c0', 9 retries!
Apr 1 15:52:40 WARNING[2487]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x8ac81c0', 9 retries!
Apr 1 15:52:40 WARNING[2487]: channel.c:780 channel_find_locked: Avoided deadlock for '0x89f2790', 9 retries!
Apr 1 15:52:41 WARNING[2487]: channel.c:780 channel_find_locked: Avoided deadlock for '0x89f2790', 9 retries!
Apr 1 15:52:41 WARNING[2487]: channel.c:780 channel_find_locked: Avoided deadlock for '0x89f2790', 9 retries!
Apr 1 15:52:42 WARNING[2487]: channel.c:780 channel_find_locked: Avoided deadlock for '0x89f2790', 9 retries!
Apr 1 15:52:43 WARNING[2487]: channel.c:780 channel_find_locked: Avoided deadlock for '0x89f2790', 9 retries!


app_meetme.c:2210 admin_exec: Conference Number not found
Apr 1 16:02:56 NOTICE[14145]: app_meetme.c:2210 admin_exec: Conference Number not found
Apr 1 16:03:47 WARNING[13126]: channel.c:2290 ast_write: Thread 20327312 Blocking 'SIP/107-08a856d0', already blocked by thread 53697424 in procedure ast_waitfor_nandfds
Apr 1 16:03:47 WARNING[13126]: channel.c:2290 ast_write: Thread 20327312 Blocking 'Local/78600055@default-bb01,2', already blocked by thread 31267728 in procedure ast_waitfor_nandfds
Apr 1 16:03:47 WARNING[13126]: channel.c:2290 ast_write: Thread 20327312 Blocking 'SIP/107-08a856d0', already blocked by thread 53697424 in procedure ast_waitfor_nandfds
Apr 1 16:03:47 WARNING[13126]: channel.c:2290 ast_write: Thread 20327312 Blocking 'Local/78600055@default-bb01,2', already blocked by thread 31267728 in procedure ast_waitfor_nandfds

[mflorell]

The conference not found is normal if these were happing during agent logout.

The other issues are either caused by bandwidth issues, load issues, or if you are using DTMF passthru.

[tgalan]

How can I know the Load?

I'm recording all calls to gsm format, voip carrier, ipphones all of them sip, allowing only gsm codec

Is giving me the audio issues with 4 agents using manual dial

[mflorell]

What zaptel timer are you using?

to see the load either type 'w' or 'top' in Linux CLI

[tgalan]

I have this load average: 2.72, 2.09, 3.24

with only one agent on a call

[tgalan]

mat when I type reload on asterisk cli i got this:

Apr 1 16:53:00 NOTICE[639]: cdr.c:1214 do_reload: CDR simple logging enabled.
Apr 1 16:53:00 NOTICE[639]: dnsmgr.c:338 do_reload: Managed DNS entries will be refreshed every 300 seconds.
Apr 1 16:53:00 NOTICE[639]: indications.c:505 ast_unregister_indication_country: Removed default indication country 'us'
Apr 1 16:53:00 WARNING[639]: config.c:527 process_text_line: No '=' (equal sign) in line 81 of /etc/asterisk/extensions.conf
Apr 1 16:53:00 NOTICE[639]: pbx.c:1765 pbx_extension_helper: Cannot find extension '' in context '(null)'
Apr 1 16:53:00 WARNING[639]: pbx_config.c:1713 pbx_load_module: Invalid priority/label '' at line 80
Apr 1 16:53:00 NOTICE[639]: chan_iax2.c:9137 set_config: Ignoring bindport on reload
Apr 1 16:53:00 NOTICE[639]: chan_iax2.c:8266 iax2_poke_peer: Still have a callno...
Apr 1 16:53:00 NOTICE[639]: chan_iax2.c:8266 iax2_poke_peer: Still have a callno...
Apr 1 16:53:00 WARNING[639]: config.c:497 process_text_line: Unknown directive '' at line 1 of /etc/asterisk/zapata.conf
Apr 1 16:53:00 WARNING[639]: config.c:497 process_text_line: Unknown directive '' at line 2 of /etc/asterisk/zapata.conf
Apr 1 16:53:00 WARNING[639]: config.c:497 process_text_line: Unknown directive '' at line 3 of /etc/asterisk/zapata.conf
Apr 1 16:53:00 WARNING[639]: config.c:497 process_text_line: Unknown directive '' at line 4 of /etc/asterisk/zapata.conf
Apr 1 16:53:00 WARNING[639]: config.c:497 process_text_line: Unknown directive '' at line 5 of /etc/asterisk/zapata.conf
Apr 1 16:53:00 WARNING[639]: config.c:497 process_text_line: Unknown directive '' at line 6 of /etc/asterisk/zapata.conf
Apr 1 16:53:00 WARNING[639]: config.c:497 process_text_line: Unknown directive 'context=unused' at line 10 of /etc/asterisk/zapata.conf
Apr 1 16:53:00 WARNING[639]: config.c:497 process_text_line: Unknown directive 'signalling=fxs_ks' at line 11 of /etc/asterisk/zapata.conf
Apr 1 16:53:00 WARNING[639]: config.c:497 process_text_line: Unknown directive 'channel' at line 12 of /etc/asterisk/zapata.conf
-- AMD defaults: initialSilence [2500] greeting [1500] afterGreetingSilence [800] totalAnalysisTime [5000] minimumWordLength [100] betweenWordsSilence [50] maximumNumberOfWords [3] silenceThreshold [256]

[mflorell]

What is the CPU/RAM on this system?

[tgalan]

CPU Intel Celeron 2.6ghz
RAM 1gb

but I restart the system and is working fine....

now with one agent on call i got load average: 0.90, 1.37, 1.38

[mflorell]

Single core CPU?

[williamconley]

One agent is very few, but how many calls per agents? How many active calls on the system (including the agent) is important. (1 agent at 25:1 dialing is very different than 1 agent with 2:1 dialing)

I've had issues similar to that when zaptel/asterisk were not compiled correctly for the kernel. Of course you are on VicidialNOW, but there may have been an error during install that you did not notice (even a celeron should be able to handle a few calls without issues, I have a PII running a single agent for testing).

On the other hand, if you are at 10:1 dialing with a single agent and have compression (gsm or g729) on or recording calls or using AMD, you may just be "at capacity".