vicidial.org

Hello,

I am using vidialnow VERSION: 2.2.1-237
BUILD: 100510-2015

I try to add DID for an In-group as following the newest manager guide, however this function seems not work, the incoming call does not send to agent who is ready to take calls.

I check the extensions.conf and extensions-vicidial.conf file but dont see any commands related to this DID.

Anyone please tell me this function is not completed yet?

Thanks all
Mike

The DID function is working properly. Most probably you just missed some configuration steps. Please post Asterisk CLI when dialing/receiving calls.

gardo wrote:The DID function is working properly. Most probably you just missed some configuration steps. Please post Asterisk CLI when dialing/receiving calls.

As I understand that when we add the DID int the GUI, the system will automatically write the commands to extensions-vicidial.conf file. However in my case, there is no commands written in the conf file and incoming call was rejected.

Here is my DID list
INBOUND DID LISTINGS:
# DID DESCRIPTION ACTIVE ROUTE MODIFY
5 22202265 CIMONALIA Y IN_GROUP MODIFY

And here is the Asterisk CLI

chan_iax2.c:7663 socket_read: Rejected connect attempt from 192.168.1.250, request '22202265@default' does not exist

I dont know where I miss, pls help

DIDs are not written to the dialplan, only Call Menus and phones are. DIDs are handled in an AGI. You need to make sure your trunks are set to the context=trun kinbound for this to work.

mflorell wrote:DIDs are not written to the dialplan, only Call Menus and phones are. DIDs are handled in an AGI. You need to make sure your trunks are set to the context=trun kinbound for this to work.

Thanks for your guidance, I will test it out and update.

Hi Matt,

Thanks for the information provided. However need to clarify that the information in the manager's manual needs to be updated. I have the same challenge. I had to get my phone to work on vicidial by doing some manipulations in the extensions.conf for it to work. This means that I cannot configure my DID from the from end. In addition, does DID work for Zap interface or only works for SIP/AIX based on the functionality of vicidial?

Thanks

Please tell me what page on the manager manual has incorrect information.

DID configuration can work for Zap, IAX and SIP trunks, if they are configured properly.

Hi Matt,

Thanks for the response. Based on the user manual, I configured the DID with the following parameters:

DID Extension : 07042909629

DID Description: Trials

DID Route: IN_GROUP

In-Group ID: Single Agent Direct Queue

In-Group Call Handle Method: CIDLOOKUP

In-Group Agent Search Method: LB

In-Group Phone Code : 1

Upon saving it, I got, I am sorry, that is not a valid extension. Is there anything wrong or is there anything that needs to be done at the front end that I have not done.

Thanks

Hi Matt,

This is my asterisk cli

[Jun 28 14:46:26] -- Starting simple switch on 'Zap/1-1'
[Jun 28 14:46:27] == Starting Zap/1-1 at default,s,1 failed so falling back to exten 's'
[Jun 28 14:46:27] == Starting Zap/1-1 at default,s,1 still failed so falling back to context 'default'
[Jun 28 14:46:27] -- Sent into invalid extension 's' in context 'default' on Zap/1-1
[Jun 28 14:46:27] -- Executing Playback("Zap/1-1", "invalid") in new stack
[Jun 28 14:46:27] -- Playing 'invalid' (language 'en')
[Jun 28 14:46:42] -- Timeout on Zap/1-1
[Jun 28 14:46:42] == CDR updated on Zap/1-1
[Jun 28 14:46:42] -- Executing Goto("Zap/1-1", "#|1") in new stack
[Jun 28 14:46:42] -- Goto (default,#,1)
[Jun 28 14:46:42] -- Executing Playback("Zap/1-1", "invalid") in new stack
[Jun 28 14:46:42] -- Playing 'invalid' (language 'en')
[Jun 28 14:46:45] == Spawn extension (default, #, 1) exited non-zero on 'Zap/1-1'
[Jun 28 14:46:45] -- Executing DeadAGI("Zap/1-1", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0---------------") in new stack
[Jun 28 14:46:45] -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0
[Jun 28 14:46:45] -- Hungup 'Zap/1-1'

Thanks

what does your zapata.conf have set for the context?

the context is default

what happens when you change it to "trunkinbound" and you reboot?

will try it and get back to you.

Hi Matt,

Thanks for the response. These are my files and observations


/etc/asterisk/zapata-channels.conf

signalling=fxs_ks
callerid=asreceived
group=0
context=trunkinbound
channel => 1
context=default

/etc/asterisk/zapata.conf

[trunkgroups]
[channels]

musiconhold=default
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
canpark=yes
echocancel=yes
echocancelwhenbridged=no
echotraining=800
rxgain=3.0
txgain=1.0
group=1
callgroup=1
pickupgroup=1
immediate=no
hanguponpolarityswitch
busydetect=yes
busycount=4
context=trunkinbound
signalling=fxs_ks
channel => 1

#include /zapata-channels.conf



This is my asterisk cli:

-- Starting simple switch on 'Zap/1-1'
== Starting Zap/1-1 at trunkinbound,s,1 failed so falling back to exten 's'
== Starting Zap/1-1 at trunkinbound,s,1 still failed so falling back to context 'default'
-- Sent into invalid extension 's' in context 'default' on Zap/1-1
-- Executing Playback("Zap/1-1", "invalid") in new stack
-- Playing 'invalid' (language 'en')
-- Timeout on Zap/1-1


This is my DID configuration

DID Extension : 07042909629

DID Description: Trials

DID Route: IN_GROUP

In-Group ID: Single Agent Direct Queue

In-Group Call Handle Method: CIDLOOKUP

In-Group Agent Search Method: LB

In-Group Phone Code : 1

I still got the message, I am sorry, that is not a valid extension


Please let me know where I got it wrong.

Are you using POTS lines?

admin.php version and build?

Hi Matt,

Thanks, I am using FXO interface with CDMA line with 2.0.5-206, build 90525-1014.

FXO lines can't do DIDs, so all calls will come through as 's' exten.

You should consider upgrading to 2.2.1, I think the admin.php error you are experiencing is a bug in that version.

Hell

Please kindly advice on how to upgrade to version 2.2.1. From vicidial now, the information available is on version 2.2.0. Hoping to hear from you.

Thank you.

2.2.1 is the official release of the 2.2.0 tree, so the ViciDialNow instructions should work for you.

Hi Matt,

Thanks for that. I will go through it and get back to you.

Hi Matt,

Thanks for the response so far. Based on your advice, I have ungraded to version 2.2.1 and did the configuration as informed. However the same issue still remains. This is my asterisk cli

-- Starting simple switch on 'Zap/1-1'
== Starting Zap/1-1 at trunkinbound,s,1 failed so falling back to exten 's'
== Starting Zap/1-1 at trunkinbound,s,1 still failed so falling back to context 'default'
-- Sent into invalid extension 's' in context 'default' on Zap/1-1
-- Executing Playback("Zap/1-1", "invalid") in new stack
-- Playing 'invalid' (language 'en')
-- Timeout on Zap/1-1
== CDR updated on Zap/1-1
-- Executing Goto("Zap/1-1", "#|1") in new stack
-- Goto (default,#,1)
-- Executing Playback("Zap/1-1", "invalid") in new stack
-- Playing 'invalid' (language 'en')
-- Executing Hangup("Zap/1-1", "") in new stack
== Spawn extension (default, #, 2) exited non-zero on 'Zap/1-1'
-- Executing DeadAGI("Zap/1-1", "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 'Zap/1-1'

Is there anything I may be getting wrong? My other configurations remain the same.

What exactly do you want it to do?

You can't use DIDs on a POTS line.

What you can do is alter the trunkinbound context on extensions.conf to add a line for the 's' exten that includes the DID AGI script, then you can route calls using the web gui.

Hi Matt,

Thanks for the response. Kindly help with the instructions on how to achieve this:
What you can do is alter the trunkinbound context on extensions.conf to add a line for the 's' exten that includes the DID AGI script, then you can route calls using the web gui.

I will glad to have the instruction.

Thanks

Add this line to trunkinbound:

exten => s,1,AGI(agi-DID_route.agi)


Then reload in Asterisk

Hi Matt,

Thanks for the response. I added the line as informed and this is the response from asterisk cli

[Jul 2 04:21:22] -- Starting simple switch on 'Zap/1-1'
[Jul 2 04:21:23] -- Executing AGI("Zap/1-1", "agi-DID_route.agi") in new stack
[Jul 2 04:21:23] -- Launched AGI Script /var/lib/asterisk/agi-bin/agi-DID_route.agi
[Jul 2 04:21:23] -- AGI Script agi-DID_route.agi completed, returning 0
[Jul 2 04:21:23] -- Executing Wait("Zap/1-1", "2") in new stack
[Jul 2 04:21:25] -- Executing Answer("Zap/1-1", "") in new stack
[Jul 2 04:21:25] -- Executing Playback("Zap/1-1", "ss-noservice") in new stack
[Jul 2 04:21:25] -- Playing 'ss-noservice' (language 'en')
[Jul 2 04:21:30] -- Executing Playback("Zap/1-1", "vm-goodbye") in new stack
[Jul 2 04:21:30] -- Playing 'vm-goodbye' (language 'en')
[Jul 2 04:21:31] -- Executing Hangup("Zap/1-1", "") in new stack
[Jul 2 04:21:31] == Spawn extension (default, 9998811112, 5) exited non-zero on 'Zap/1-1'
[Jul 2 04:21:31] -- Executing DeadAGI("Zap/1-1", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------") in new stack
[Jul 2 04:21:31] -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0
[Jul 2 04:21:31] -- Hungup 'Zap/1-1'


When I commented the line this is my asterisk cli:


[Jul 2 04:23:43] -- Starting simple switch on 'Zap/1-1'
[Jul 2 04:23:44] == Starting Zap/1-1 at trunkinbound,s,1 failed so falling back to exten 's'
[Jul 2 04:23:44] == Starting Zap/1-1 at trunkinbound,s,1 still failed so falling back to context 'default'
[Jul 2 04:23:44] -- Executing Answer("Zap/1-1", "") in new stack
[Jul 2 04:23:44] -- Executing AGI("Zap/1-1", "agi://127.0.0.1:4577/call_log") in new stack
[Jul 2 04:23:44] -- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
[Jul 2 04:23:44] -- Executing Ringing("Zap/1-1", "") in new stack
[Jul 2 04:23:44] -- Executing AGI("Zap/1-1", "agi-VDAD_ALL_inbound.agi|CIDLOOKUP-----LB-----salesline-------------------------101-----234") in new stack
[Jul 2 04:23:44] -- Launched AGI Script /var/lib/asterisk/agi-bin/agi-VDAD_ALL_inbound.agi
[Jul 2 04:23:47] -- Started music on hold, class 'default', on Zap/1-1
[Jul 2 04:23:51] -- Stopped music on hold on Zap/1-1
[Jul 2 04:23:52] -- Started music on hold, class 'default', on Zap/1-1


Here are DID configurations:

DID Extension : 07042909629

DID Description: Trials

DID Route: IN_GROUP

In-Group ID: Single Agent Direct Queue

In-Group Call Handle Method: CIDLOOKUP

In-Group Agent Search Method: LB

In-Group Phone Code : 1


Here is my zapata.conf

[trunkgroups]
[channels]

musiconhold=default
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
canpark=yes
echocancel=yes
echocancelwhenbridged=no
echotraining=800
rxgain=3.0
txgain=1.0
group=1
callgroup=1
pickupgroup=1
immediate=no
hanguponpolarityswitch
busydetect=yes
busycount=4
context=trunkinbound
signalling=fxs_ks
channel => 1

#include /zapata-channels.conf

Here is my zapata-channels.conf

signalling=fxs_ks
callerid=asreceived
group=0
context=trunkinbound
channel => 1
context=trunkinbound


Please let me know if there is still anything wrong in my configuration.

Thanks.

Do you have a 'default' DID entry in your vicidial system?

Yes

agiout output for this call?

Hi Matt

Please kindly explain the meaning of your statement. Does it mean the asterisk cli?

/var/log/astguiclient ... there are many logs (which can be turned on and off in the gui under admin->servers)

one of them is agiout

Hi Matt,

The agi output is with a value of FILE.

The following is the reading of the /var/log/astguiclient/

FASTagiout.2010-06-30
FASTagiout.2010-07-01
FASTagiout.2010-07-02
VDadaptive-TESTCAMP.2010-06-30
action_full.2010-06-30
action_full.2010-07-01
action_full.2010-07-02
action_launch.2010-06-30
action_launch.2010-07-01
action_launch.2010-07-02
action_process.2010-06-30
action_process.2010-07-01
action_process.2010-07-02
action_send.2010-06-30
action_send.2010-07-01
action_send.2010-07-02
adapt.2010-06-30
adapt.2010-07-01
adapt.2010-07-02
agiout.2010-06-30
agiout.2010-07-01
agiout.2010-07-02
didin.2010-07-02
hopper.2010-06-30
hopper.2010-07-01
hopper.2010-07-02
listen.2010-06-30
listen.2010-07-01
listen.2010-07-02
listen_process.2010-06-30
listen_process.2010-07-01
listen_process.2010-07-02
remoteagent.2010-06-30
remoteagent.2010-07-01
remoteagent.2010-07-02
screenlog.0.2010-06-30---223148
screenlog.0.2010-07-01---120220
screenlog.0.2010-07-01---140027
screenlog.0.2010-07-01---33252
screenlog.0.2010-07-01---40956
screenlog.0.2010-07-01---60535
screenlog.0.2010-07-01---74222
screenlog.0.2010-07-01---94606
screenlog.0.2010-07-02---35417
screenlog.0.2010-07-02---44559
screenlog.0.2010-07-02---85956
timeclockautologout.2010-06-30
timeclockautologout.2010-07-01
timeclockautologout.2010-07-02
update.2010-06-30
update.2010-07-01
update.2010-07-02
vdautodial.2010-06-30
vdautodial.2010-07-01
vdautodial.2010-07-02

On check on FASTagiout.2010-07-01

2010-07-01 00:50:27|VDfastAGI|begin|+++++++++++++++++ FastAGI Start ++++++++++++++++++++++++++++++++++++++++
2010-07-01 00:50:27|VDfastAGI|begin|Perl Environment Dump:
2010-07-01 00:50:27|VDfastAGI|begin|0|--debug
2010-07-01 00:50:27|VDfastAGI|begin|URL HVcauses: |PRI|NODEBUG|16|||0|
2010-07-01 00:50:27|VDfastAGI|begin|AGI Environment Dump:
2010-07-01 00:50:27|VDfastAGI|begin| -- accountcode =
2010-07-01 00:50:27|VDfastAGI|begin| -- callerid = 07026285893
2010-07-01 00:50:27|VDfastAGI|begin| -- calleridname = unknown
2010-07-01 00:50:27|VDfastAGI|begin| -- callingani2 = 0
2010-07-01 00:50:27|VDfastAGI|begin| -- callingpres = 0
2010-07-01 00:50:27|VDfastAGI|begin| -- callingtns = 0
2010-07-01 00:50:27|VDfastAGI|begin| -- callington = 0
2010-07-01 00:50:27|VDfastAGI|begin| -- channel = Zap/1-1
2010-07-01 00:50:27|VDfastAGI|begin| -- context = default
2010-07-01 00:50:27|VDfastAGI|begin| -- dnid = unknown
2010-07-01 00:50:27|VDfastAGI|begin| -- enhanced = 0.0
2010-07-01 00:50:27|VDfastAGI|begin| -- extension = h
2010-07-01 00:50:27|VDfastAGI|begin| -- language = en
2010-07-01 00:50:27|VDfastAGI|begin| -- network = yes
2010-07-01 00:50:27|VDfastAGI|begin| -- network_script = call_log--HVcauses--PRI-----NODEBUG-----16---------------
2010-07-01 00:50:27|VDfastAGI|begin| -- priority = 1
2010-07-01 00:50:27|VDfastAGI|begin| -- rdnis = unknown
2010-07-01 00:50:27|VDfastAGI|begin| -- request = agi://127.0.0.1:4577/call_log--HVcauses ... ----------
2010-07-01 00:50:27|VDfastAGI|begin| -- type = Zap
2010-07-01 00:50:27|VDfastAGI|begin| -- uniqueid = 1277959807.2
2010-07-01 00:50:27|VDfastAGI|begin|AGI Variables: |1277959807.2|Zap/1-1|h|Zap|07026285893|
2010-07-01 00:50:27|VDfastAGI|call_log|Process to run: |agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------|call_log|END|
2010-07-01 00:50:27|VDfastAGI|call_log||CALL HUNG UP|
2010-07-01 00:50:27|VDfastAGI|call_log|URL HVcauses: |PRI|NODEBUG|16|||0|
2010-07-01 00:50:27|VDfastAGI|call_log||DELETE from live_inbound where uniqueid IN('1277959807.2','1277959807.2') and server_ip='192.168.19.61'|
2010-07-01 00:50:27|VDfastAGI|call_log|+++++ CALL LOG HUNGUP: |1277959807.2|Zap/1-1|h|2010-07-01 00:50:27|min: |
2010-07-01 00:50:27|VDfastAGI|call_log|DEBUG: NODEBUG
2010-07-01 00:50:27|VDfastAGI|call_log|VD_hangup : 07026285893 Zap/1-1 1 0
2010-07-01 00:50:27|VDfastAGI|call_log||SELECT lead_id,callerid,campaign_id,alt_dial,stage,UNIX_TIMESTAMP(call_time),uniqueid,status,call_time,phone_code,phone_number,queue_position FROM vicidial_auto_calls where uniqueid = '1277959807.2' or callerid = '07026285893' limit 1;|


This part of the file (too long to paste)


Please let me know what is wrong

that doesn't help, I was looking for the agiout file: "agiout.2010-07-02"