Inbound calls not connecting *SOLVED*

[deephack]

Hello all,

This is my first attempt at setting up inbound calling, have experience with setting up outbound and have that working fine. Here are my specs:-

Scratch built using instructions in docs folder
ViciDial 2.8-404a build 130605-0841
Asterisk 1.4.44
Loadavg 0.04
HP DL160 G6 with 2x Intel Xeon E5606 @ 2.13Ghz with 8Gb DDR3
GSM codec
Pure VoIP with IAX2 trunk for outbound
Ubuntu 12.04.2

I've set up a DID using the instructions in the ViciDial Manager manual and pointed it at an in group. I've ensured that the context for my carrier is set to trunkinbound. When I try to make an inbound call it doesn't ring and fails to connect. I get the following CLI output.

-- Accepting AUTHENTICATED call from <my provider>:
> requested format = ulaw,
> requested prefs = (),
> actual format = ulaw,
> host prefs = (ulaw|alaw),
> priority = mine
-- Executing [<DID number>@trunkinbound:1] AGI("IAX2/gz1-7537", "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
== Auto fallthrough, channel 'IAX2/gz1-7537' status is 'UNKNOWN'
-- Executing [h@trunkinbound:1] DeadAGI("IAX2/gz1-7537", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0---------------") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0
-- Hungup 'IAX2/gz1-7537'


I checked the /var/log/astguiclient folder for a didin log file and haven't found any. If I enable agi debug I get this.

-- Launched AGI Script /var/lib/asterisk/agi-bin/agi-DID_route.agi
AGI Tx >> agi_request: agi-DID_route.agi
AGI Tx >> agi_channel: IAX2/gz1-12314
AGI Tx >> agi_language: en
AGI Tx >> agi_type: IAX2
AGI Tx >> agi_uniqueid: 1372412237.309
AGI Tx >> agi_callerid: <My CID>
AGI Tx >> agi_calleridname: <My CID>
AGI Tx >> agi_callingpres: 0
AGI Tx >> agi_callingani2: 0
AGI Tx >> agi_callington: 0
AGI Tx >> agi_callingtns: 0
AGI Tx >> agi_dnid: unknown
AGI Tx >> agi_rdnis: unknown
AGI Tx >> agi_context: trunkinbound
AGI Tx >> agi_extension: <DID number>
AGI Tx >> agi_priority: 1
AGI Tx >> agi_enhanced: 0.0
AGI Tx >> agi_accountcode:
AGI Tx >>

What should I check next?

[williamconley]

what page and line are you on in the manual (where setting up inbound calls is covered)? And which manual version?

Of course, I refer to the Vicidial Manager's Manual which is free ... which you would have used to set this up ...

You seem to have the call arriving (very good), but when you say you have it pointed to an ingroup, did you specify WHICH ingroup?

Before you set up a specific DID, you should consider deleting it and allowing the call to be handled by the existing "default" did which will play 'number not in service' and hang up. If you see this happen in your CLI and hear those sounds ... then you do have control of the call in the Vicidial scripting system and just need to follow the manual.

[deephack]

Hi William,

I take instruction from tutorial F - Create an inbound-group, point a DID at it, and take calls which is on page 29 of the manager manual. I have selected the in group yes.

Just tried your suggestion of removing the DID and I'm finding that exactly the same thing happens. I just get the channel auto-fallthrough message, also with the did log never being created I'm thinking that the AGI is failing to run correctly. Could this be something to do with my perl install? I'm going to check over the installed CPAN modules to make sure I haven't missed something.

[williamconley]

perhaps you should check your iax debug logs. if you are trying to use a codec you don't have, the call will fail.

did you follow all the instructions in the manual for inbound?

share your DID configuration and your carrier configuration.

[deephack]

Yes I followed the entire section I mentioned in the manager manual. Just looked at the IAX debug and it looks completely normal I get the following flow:-

NEW
ACK
AUTHREQ
AUTHREP
ACK
ACCEPT
ACK
HANGUP

Also in the normal logging I get the accepting authenticated call message which would suggest all is well on the IAX side.

DID config

DID Extension: <DID number> - Matches what I'm receiving in the logs
DID Description: Main inbound number
Active: Y
Admin User Group: ADMIN
DID Route: IN_GROUP
Record Call: N
Extension: 9998811112
Extension Context: default
Voicemail Box:
Phone Extension:
Server IP:
Call Menu:
User Agent:
User Unavailable Action: Voicemail
User Route Settings In-Group: inbound - Primary inbound group
In-Group ID: inbound - Primary inbound group
In-Group Call Handle Method: CID
In-Group Agent Search Method: LB
In-Group List ID: 999
In-Group Campaign ID:
In-Group Phone Code: 1
Clean CID Number:
Filter Inbound Number: DISABLED
Filter Phone Group ID:
Filter URL:
Filter Action: EXTEN
Filter Extension: 9998811112
Filter Extension Context: default
Filter Voicemail Box:
Filter Phone Extension:
Filter Server IP:
Filter Call Menu:
Filter User Agent:
Filter User Unavailable Action: VOICEMAIL
Filter User Route Settings In-Group: AGENTDIRECT - Single Agent DIrect Queue
Filter In-Group ID: --NONE--
Filter In-Group Call Handle Method: CID
Filter In-Group Agent Search Method: LB
Filter In-Group List ID: 999
Filter In-Group Campaign ID:
Filter In-Group Phone Code: 1
Custom 1:
Custom 2:
Custom 3:
Custom 4:
Custom 5:

Carrier Config

Carrier ID: Maven
Carrier Name: Maven
Carrier Description: Maven
Admin User Group: --ALL--
Registration String: register => <not telling >
Template ID:
Account Entry:
[gz1]
disallow=all
allow=ulaw
allow=alaw
type=friend
username=gz1
secret=<password>
host=dynamic
context=trunkinbound
requirecalltoken=no
Protocol: IAX2
Globals String:
Dialplan Entry:
exten => _10XXXXXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _10XXXXXXXXXX,2,Dial(IAX2/<same as reg string>/${EXTEN:1},,tTor)
exten => _10XXXXXXXXXX,3,Hangup

exten => _10XXXXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _10XXXXXXXXX,2,Dial(IAX2/<same as reg string>/${EXTEN:1},,tTor)
exten => _10XXXXXXXXX,3,Hangup
Server IP: 10.20.0.14
Active: Y

[deephack]

Just edited the trunkinbound context and added a specific extension rule for the DID pointing to a playback command. This worked perfectly, call connected and played the message. Definitely something going wrong once the call is passed to the AGI script. I'm still thinking I messed up the Perl install somewhere. I'm going to continue looking at it.

-- Accepting AUTHENTICATED call from <Providers IP>:
> requested format = ulaw,
> requested prefs = (),
> actual format = ulaw,
> host prefs = (ulaw|alaw),
> priority = mine
-- Executing [<DID number>@trunkinbound:1] Playback("IAX2/gz1-1416", "discon-or-out-of-service") in new stack
-- <IAX2/gz1-1416> Playing 'discon-or-out-of-service' (language 'en')
-- Executing [<DID number>@trunkinbound:2] Hangup("IAX2/gz1-1416", "") in new stack
== Spawn extension (trunkinbound, <DID Number>, 2) exited non-zero on 'IAX2/gz1-1416'
-- Executing [h@trunkinbound:1] DeadAGI("IAX2/gz1-1416", "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 ... ---------- completed, returning 0
-- Hungup 'IAX2/gz1-1416'

[deephack]

Okay I've got this working now but I am a bit worried about possible consequences, more on that later.

I found that if I ran agi-DID_route.agi from the command line I got the following.

Can't locate Asterisk/AGI.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.14 /usr/share/perl/5.14 /usr/local/lib/site_perl .) at ./agi-DID_route.agi line 107.
BEGIN failed--compilation aborted at ./agi-DID_route.agi line 107.

So looks like I'm missing asterisk-perl although I installed it as per the scratch instructions and every other part of ViciDial is working. I know from experience that failing to install asterisk-perl makes the outbound autodialler not work. Anyway I issue "cpan -i Asterisk::AGI" and then re-run. Now everything inbound wise works perfectly.

My only worry is that doing this via CPAN drew in asterisk-perl version 1.03 and I know that the manual says nothing above 0.08 works with ViciDial. Have I just done something awful? Everything appears to be still working.

[williamconley]

it's only awful if it doesn't work. LOL

check autodial and transfers and ... etc.

[circuit]

Hi there,

I have the same problem. I did my install from the ISO

Not sure why, calls to the phone and extension work. It is just when this script "agi-VDAD_ALL_inbound.agi" is called, it hangs up.

I have a Centos 5.11, Asterisk 1.8. Here is the Info,

VERSION: 2.9-441a
BUILD: 140612-1628
© 2014 ViciDial Group

I installed it using GoautoDial's yum repo. I have GoAdmin ® 3.3-1406088000 on the same box.

Everything seems to work fine. However, I can't route calls to my INGROUP. I have been searching all the forums. Almost tried everything. The agent is selecting the INGROUP. The campaign is allowed to have blended call handling. I can get calls to my phone directly, but can't when I set the DIDROUTE to "INGROUP"

Thanks,

[circuit]

Amazingly, I can see call attempts in the DID report, in DID traffic.

However, calls are not getting routed to the INGROUP. Nothing in the INGROUP stats

[circuit]

Just so you know, this is an install on a Xen Virtual Instance ? Can that make a difference ? I can call out flawlessly

[williamconley]

Ordinarily this is because the DID points to an Ingroup ... but you failed to select WHICH Ingroup (or deleted it after selecting it).