Agents In ready Status 5 minutes+

All installation and configuration problems and questions

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

Agents In ready Status 5 minutes+

Postby kenrom » Mon Jul 16, 2007 6:29 pm

I have about 20 agents in a campaign with more than 10k leads in it...and agents are on READY status for more than 5 minutes and thy are not gettin any calls @ all so far this is what i have done

1.rebooted mysql and asterisk server.
2. double check both of them have the same time...

The version of asterisk i`m using is VERSION: 2.0.73 BUILD: 61129-1028

can someone plz tell me how do i fix this....

FYI: this started after all servers lost power..
kenrom
 
Posts: 8
Joined: Fri Jul 28, 2006 11:59 pm
Location: barbados

Postby enjay » Mon Jul 16, 2007 6:36 pm

Ensure asterisk is actually running by typing asterisk -r at a command prompt.

Make sure the processes are running screen -x
enjay
 
Posts: 806
Joined: Mon Jun 19, 2006 12:40 pm
Location: Utah

Postby Op3r » Mon Jul 16, 2007 6:45 pm

and also check if asterisk is really dialing
Get paid for US outbound Toll Free calls. PM me.
Op3r
 
Posts: 1424
Joined: Wed Jun 07, 2006 7:53 pm
Location: Manila

Postby jekader » Thu Jul 19, 2007 1:52 pm

Hi to everybody. I'm a real noob to VICIDIAL, and this is my first post on this forum.

My problem is pretty the same. It is my first VICIDIAL setup. I've done everything according to the scratch_install, but now I'm stuck, because the calls don't reach the operators.

In the asterisk log I can see, that there are external calls placed, then answered - but nothing gets transferred to the conference, where the operator is located. What could be the possible problem, and how could I trace, on what point the calls get stuck?

Thanks in advance.
Jenea
jekader
 
Posts: 7
Joined: Thu Jul 19, 2007 1:33 pm

Postby gerski » Tue Jul 24, 2007 6:15 am

please post your asterisk cli..
http://www.perfectnetworkcorp.com
Perfect Network Corporation
gerski
 
Posts: 432
Joined: Fri Jul 14, 2006 6:21 am

Postby jekader » Wed Jul 25, 2007 10:52 am

I've logged in to test and see the output to see, that everything is working now :)

And this is not the first problem, that has resolved by itself...

but anyway, here is the CLI output, because there are some errors in the bottom, that are costantly appearing:

Code: Select all
Connected to Asterisk 1.2.21.1 currently running on server2 (pid = 2233)
Verbosity is at least 21
    -- Remote UNIX connection
  == Parsing '/etc/asterisk/manager.conf': Found
  == Parsing '/etc/asterisk/manager.conf': Found
  == Manager 'sendcron' logged on from 127.0.0.1
  == Manager 'sendcron' logged on from 127.0.0.1
  == Manager 'sendcron' logged off from 127.0.0.1
  == Manager 'sendcron' logged off from 127.0.0.1
  == Parsing '/etc/asterisk/manager.conf': Found
  == Manager 'sendcron' logged on from 127.0.0.1
  == Parsing '/etc/asterisk/manager.conf': Found
  == Manager 'sendcron' logged on from 127.0.0.1
    -- Executing DeadAGI("Local/14166260112@default-d81a,2", "call_log.agi|14166260112") in new stack
    -- Executing DeadAGI("Local/14166210318@default-d4a7,2", "call_log.agi|14166210318") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/call_log.agi
    -- Launched AGI Script /var/lib/asterisk/agi-bin/call_log.agi
    -- AGI Script call_log.agi completed, returning 0
    -- Executing Dial("Local/14166260112@default-d81a,2", "SIP/14166260112@SIPTrunk|55|o") in new stack
    -- AGI Script call_log.agi completed, returning 0
    -- Executing Dial("Local/14166210318@default-d4a7,2", "SIP/14166210318@SIPTrunk|55|o") in new stack
    -- Called 14166260112@SIPTrunk
    -- Called 14166210318@SIPTrunk
Jul 25 11:46:18 WARNING[2309]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x81b8b70', 9 retries!
Jul 25 11:46:18 WARNING[2309]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x81b8760', 9 retries!
Jul 25 11:46:18 ERROR[2248]: chan_sip.c:11572 sipsock_read: We could NOT get the channel lock for SIP/SIPTrunk-081b5b40 - Call ID 15ec341b1321110974a39408207a976e@192.168.0.252!
Jul 25 11:46:18 ERROR[2248]: chan_sip.c:11573 sipsock_read: SIP MESSAGE JUST IGNORED: SIP/2.0
Jul 25 11:46:18 ERROR[2248]: chan_sip.c:11574 sipsock_read: BAD! BAD! BAD!
    -- SIP/SIPTrunk-081bfd58 is ringing
    -- SIP/SIPTrunk-081b5b40 is ringing
  == Refreshing DNS lookups.
 


what could be causing these? Do they affect something?
jekader
 
Posts: 7
Joined: Thu Jul 19, 2007 1:33 pm


Return to Support

Who is online

Users browsing this forum: No registered users and 68 guests