NO LIVE CALLS WAITING

[Justin123]

I can see AST_timeonVDADall

DIALABLE LEADS: 4090
HOPPER LEVEL: 50
LEADS IN HOPPER: 50

NO LIVE CALLS WAITING

In CLI I see :

May 18 15:31:36 WARNING[26882]: pbx.c:4818 ast_add_extension2: Unable to register extension '102', priority 1 in 'vicidial-auto', already in use
May 18 15:31:36 WARNING[26882]: pbx_config.c:1757 pbx_load_module: Unable to register extension at line 218
May 18 15:31:36 WARNING[26882]: pbx.c:4818 ast_add_extension2: Unable to register extension '102', priority 2 in 'vicidial-auto', already in use
May 18 15:31:36 WARNING[26882]: pbx_config.c:1757 pbx_load_module: Unable to register extension at line 219
-- Registered extension context 'trunkinbound'
== Parsing '/etc/asterisk/sip_notify.conf': Found

I have to restart the dialer to make it work again.

[mflorell]

Those warnings should not have anything to do with outbound dialing issues.

[Justin123]

I don't see anything else in CLI except

asterisk@cli>

[mflorell]

Please post the output of "screen -ls"

[williamconley]

If you see those warnings the system has just reloaded after some sort of change. Or just a "reload" command.

Please list your vicidial/vicidialNOW versions and hardware/software configurations. Do you have any other software installed (FreePBX ...etc)? Did you make any changes to your configuration files that were overwritten by the vicidial system when it reloaded?

That warning, by the way, is a slight bug where the cc102 and gs102 extensions collide. Does come in handy, though, because it tells me you have 2.0.5, which means that you could be experiencing "stomped" configuration files. If you upgraded from 2.0.4 and were unaware of the impending stomp ... that can happen quite easily.