Page 1 of 1

Inbound calls not coming through

PostPosted: Wed Sep 23, 2009 4:28 pm
by ykhan
I have setup a new server (VicidialNOW 1.2, Vicidial: 2.0.5-173) and have setup inbound calls (per tutorial in the paid manual). Issue is that calls are nto coming through to a logged in agent in Resume state. Following is the CLI from login to logout:

Code: Select all
 -- Executing MeetMe("SIP/cc100-083f3830", "8600051|F") in new stack
  == Parsing '/etc/asterisk/meetme.conf': Found
    -- Created MeetMe conference 1023 for conference '8600051'
    -- Playing 'conf-onlyperson' (language 'en')
  == 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
  == Manager 'sendcron' logged off from 127.0.0.1
  == Parsing '/etc/asterisk/manager.conf': Found
  == 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
    -- Executing AGI("SIP/222311325-b780f030", "agi-DID_route.agi") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/agi-DID_route.agi
    -- AGI Script agi-DID_route.agi completed, returning 0
  == Refreshing DNS lookups.
    -- Timeout on SIP/222311325-b780f030
  == CDR updated on SIP/222311325-b780f030
    -- Executing Goto("SIP/222311325-b780f030", "#|1") in new stack
    -- Goto (default,#,1)
    -- Executing Playback("SIP/222311325-b780f030", "invalid") in new stack
    -- Playing 'invalid' (language 'en')
    -- Executing Hangup("SIP/222311325-b780f030", "") in new stack
  == Spawn extension (default, #, 2) exited non-zero on 'SIP/222311325-b780f030'
    -- Executing DeadAGI("SIP/222311325-b780f030", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------") in new stack
    -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16--------------- completed, returning 0
  == 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 MeetMeAdmin("Local/55558600051@default-749f,2", "8600051|K") in new stack
    -- Hungup 'Zap/pseudo-692734048'
  == Spawn extension (default, 8600051, 1) exited non-zero on 'SIP/cc100-083f3830'
  == Parsing '/etc/asterisk/meetme.conf': Found
    -- Executing DeadAGI("SIP/cc100-083f3830", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------") in new stack
Sep 23 13:49:49 NOTICE[13861]: app_meetme.c:2210 admin_exec: Conference Number not found
    -- Executing Hangup("Local/55558600051@default-749f,2", "") in new stack
  == Spawn extension (default, 55558600051, 2) exited non-zero on 'Local/55558600051@default-749f,2'
    -- Executing DeadAGI("Local/55558600051@default-749f,2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------") in new stack
    -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16--------------- completed, returning 0
    -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16--------------- completed, returning 0


I cannot figure it out. Please help.

PostPosted: Wed Sep 23, 2009 9:55 pm
by williamconley
Hello, Yousef:

First let us be sure we are talking about the same thing. I am VERY happy you posted both your VicidialNOW and Vicidial versions. Thank you!

1) Your agent Logs In using the "Agent Log In" link from the welcome page.

2) Your agent hears "You are the only person in this conference" upon logging in.

3) During Log In your agent chooses the "InGroup" that you created for this inbound DID.

4) You call the DID, and the call is terminated without connecting to an agent.

If any of the above are incorrect, please let me know.

Now for the questions:

How did you set the DID up in "Show DIDs" in Vicidial In-Groups? What "DID Route" does it take (IN_GROUP, or AGENT, EXTEN, VOICEMAIL or PHONE)

If you chose "IN_GROUP", Which In-Group ID did you choose? (and the rest of the settings for In_Group in the "modify a did record" screen?)

Can you look at your vicidial logs during the moment this call came through to determine what decisions vicidial made? (/var/log/astguiclient)

PostPosted: Thu Sep 24, 2009 9:11 am
by ykhan
Hi William,

The flow you have is the exact scenario I am running into.

How did you set the DID up in "Show DIDs" in Vicidial In-Groups? What "DID Route" does it take (IN_GROUP, or AGENT, EXTEN, VOICEMAIL or PHONE)


Code: Select all
DID Extension:       XXXXXXXXXX
DID Description:      Default DID
Active:      Y
DID Route:      IN_GROUP
Extension:      998811112
Extension Context:      trunkinbound
Voicemail Box:     
Phone Extension:     
Server IP:      192.168.1.2
User Agent:     
User Unavailable Action:      VOICEMAIL
User Route Settings In-Group:      HELP
In-Group ID:      --NONE--
In-Group Call Handle Method:      InboundGroup - Standard Ingroup
In-Group Agent Search Method:      CIDLOOKUP
In-Group List ID:      999
In-Group Campaign ID:      Inbound
In-Group Phone Code:      1


Following are the outputs from some of the files that seem relavant:
agiout.2009-09-24
Code: Select all
2009-09-24 7:01:31|agi-DID_route.agi||INSERT INTO vicidial_did_log SET uniqueid='1253800891.104',channel='SIP/222311325-b7820e68',server_ip='192.168.1.2',caller_id_number='14164885400',caller_id_name='14164885400',extension='7275551212',call_date='2009-09-24 7:01:31',did_id='',did_route='';|
2009-09-24 7:01:31|agi-DID_route.agi|--    DID LOG : |1|INSERT INTO vicidial_did_log SET uniqueid='1253800891.104',channel='SIP/222311325-b7820e68',server_ip='192.168.1.2',caller_id_number='14164885400',caller_id_name='14164885400',extension='7275551212',call_date='2009-09-24 7:01:31',did_id='',did_route='';|


didin.2009-09-24
Code: Select all
2009-09-24 7:01:31|1253800891.104|SIP/222311325-b7820e68|7275551212|14164885400|14164885400|||


Please let me know if you need output from any other files. Thanks for your help.

PostPosted: Thu Sep 24, 2009 10:59 am
by williamconley
DID Route: IN_GROUP

So the DID is being sent to an "IN_GROUP". Cool. But there are many in-groups .. which one? Let's look:
In-Group ID: --NONE--

This could be a problem.

PostPosted: Thu Sep 24, 2009 11:32 am
by ykhan
Sorry that was incorrect information (copy and paste to blame :) ). The setting is:

In-Group ID: InboundGroup - Standard Ingroup

PostPosted: Thu Sep 24, 2009 2:40 pm
by ykhan
Ok, so I have also checked with "DID Route" set to "AGENT" and entered the User Number for the agent. Logged in as that agent (Ratio dialing set to 1) and initiated an inbound call. Call still did not route through properly. Now I am at a loss since it seems that something is not passing to the agi-DID_route.agi and so its not handlin ghte call routing properly, but of course I probably am wrong. What else can I check? Thanks.

PostPosted: Thu Sep 24, 2009 7:40 pm
by williamconley
what do you get on your CLI during this event?

PostPosted: Thu Sep 24, 2009 9:51 pm
by ykhan
Same as above.

PostPosted: Sun Sep 27, 2009 5:07 pm
by williamconley
in the above, it says you sent it somewhere invalid. sort of like the "in-group = none".

so what does your vicidial log say? it will contain the logic of where it tried to send the call, if your logging is on.

PostPosted: Mon Sep 28, 2009 8:20 am
by ykhan
I have checked the log folder, but I am not sure which log file would contain that information. I have posted the output of two of the files I thought may be relevant. Any specific files I should be looking at?