Help + No Live call

[walex]

I've my incoming call routed through zap card into my vicidialnow server, the calls comes in , the softphone rang but the web page of the vicidialnow didn't indicate that a live call (coming in), pls can any one bail me out.
BELOW is my carrier diaplan

[pstn_incoming]
disallow=all
allow=ulaw
type=friend
username=pstn_incoming
secret=test
host=dynamic
dtmfmode=rfc2833
context=trunkinbound

exten => s,1,AGI(agi://127.0.0.1:4577/call_log)
exten => s,Dial(newsip:test@192.168.19.2:5060/${EXTEN:2},,tTor)
exten => s,3,Hangup

THIs is my zapata.conf

[trunkgroups]
[channels]
context=pstn_incoming
signalling=fxs_ks
channel => 1
echocancel=yes
echocancelwhenbridged=no
echotraining=800

Pls guys i need your help.

[williamconley]

Please read the stickies. Please read the manual (free version and paid version available on EFLO.net) and the manual for vicidialnow as well.

In there you will be told it's a good idea to list your hardware and software with versions (which are sep for vicidial and vicidialnow) and any Other Software you may have installed. Put this in your signature, saves a lot of time.

Next: You have a very nice exten => setup, but it is not one from Vicidial so it just comes in and goes straight to your soft phone.

Follow the instructions in the manual and let us know when you go awry. You will probably have other issues if you didn't just follow the directions (one by one, don't skip anything or change anything) ... especially if you know something about asterisk. Vicidial uses asterisk as the telephony engine, but the rules change for Vicidial. Don't change ANYTHING until your system works. Then back up all your settings before changing anything. Or get a big bottle of Tylenol.

[walex]

hi, thanks for your support, but i will like to ask if the zaptel card AX -400P will cause vicidialnow to pop up with livecall and detail of the caller if call comes in or thus the zaptel card AX-400P work with vicidailnow?

[williamconley]

any card that will work with asterisk will work with vicidial.

[walex]

Thanks very much for your quick response williamconley , i red my manual and i followed the instruction, but i still get confused on some certain file like zapata.conf and zaptel.conf , do these two file also need editing at all for the card all i should just contnue with the vicidial manual without tourching these two file, please bail me out of this confusion

[williamconley]

i'd love to bail you out. however, this is not something i play with enough to remember by rote. most of my systems are either NO hardware (ztdummy for timing, normal 25 users per box) or NOT vicidial (hardware, but pure asterisk with no vicidial installation, monster servers with 25-50 calls PER SECOND, or smaller systems with FreePBX instead).

this issue is a "make it work in asterisk" issue. After it works in asterisk, it can be made to work in vicidial.

that being said, have you read BOTH the vicidialnow getting started guide AND the vicidial manual? i believe the vicidialnow guide has some digium card reference in it for a quick start ...

[gardo]

Williamconley is right. You need to make it work in Asterisk first. Any trunks being used by Asterisk can also be utilized under ViciDial.

[oshonubi]

I have a similar situation here. I am convinced that it worked with Asterisk. I have the similar dial plan with Wale, my softphone rings, however, it does not connect to the vicidial interface.

However, I would like to believe that the solution may lie with Williams suggestions

Next: You have a very nice exten => setup, but it is not one from Vicidial so it just comes in and goes straight to your soft phone.

Can you please advice on what the dial plan should be. How can we correct the issue of the call going straight to the softphone instead of the vicidial interface.

Please help

[williamconley]

The dial plan in vicidialnow was set up to work before you even opened the box. so any changes you made would likely STOP it from working. you need to "insert" your trunks and "attach" your phones, but the dial plan that comes with vicidial 2.0.5, vicibox, and vicidialnow ... will work with vicidial.

have a look at the samples in the system already. ask for help if it turns out that what you use doesn't work ... post what YOU have now, and where you got it from.

[oshonubi]

Hi William,

Thanks for the response. While I accept your suggestion, I will like to point out that my channel is zap, the default dial plan is for SIP, i.e.

exten => _91NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91NXXNXXXXXX,2,Dial(newsip:test@10.10.10.15:5060/${EXTEN:2},,tTor)
exten => _91NXXNXXXXXX,3,Hangup

The second line comes with (newsip:test@10.10.10.15:5060/${EXTEN:2},,tTor), however, I am not using SIP to get into vicidial, my inbound interface is Zap, while my agent interface is SIP.

In addition, by the carrier interface, only the SIP/IAX that are saved directly through the web interface, while the Zap is not saved. How do I have my Zap protocol writing into the configuration file?

Please kindly note that most of the write-ups on vicidial, vicidialnow are on SIP.

Again, how do I "insert" trunks and "attach" phones. I believe my trunk is Zap/g1 based on extensions.conf.

As ,much as I agree with you on the dial plan for vicidial, that is meant for SIP trunking while my trunking is Zap. What should I change in the second line?

I will appreciate your immediate response.

[gardo]

Configuring Zap channels via the web interface is not yet available. It has to be done manually by editing the appropriate Asterisk conf files. What you need to do is make your Zap hardware work in Asterisk first. As for the dialplan configuration, you can check your extensions.conf. There are lots of sample entries there for different kinds of trunks.

[oshonubi]

Hi Gardo,

Thanks for the response. You seem to be the only one that understands this challenge so far. Most of the responses have been on SIP which has been quite frustrating. At least with the information that we need to configure extensions.conf manually our challenges have been resolved to some extents.

Now these are the questions:

1. Considering my zapata.conf that has a context of default, which part of extensions.conf conf do we write the dial plan?

2. From all indications, de wo need to write two different dial plans, one for inbound, the other for outbound?

3. Do we place the inbound within the context of trunkinbound or with the default?

4. How is the trunk defined in the case of Zap?


Further information, upon replacing the dialplan with exten=>s, the call goes but only to the softphone not the vicidial interface. I believe a clarity in this case will go a long way to help us understand vicidial better.

I will really appreciate your response.

[walex]

I really appreciate your contibutions talking about williamconley,gardo,oshonubi, u guys are great
I followed the in instruction given in the given in the user manual , i.e tutorial C and K and after clicking on the resume button, vicidial automatically dial in a number that was in the leads without waiting for an external number to be dialed in, and i if i pick the call through my soft phone, the the agent web interface will pop up a live call, can anne help me out pls.



This is my dial plan
exten => _9234NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _9234NXXNXXXXXX,2,Dial(SIP/204,20,to)
exten => _9234NXXNXXXXXX,3,Hangup

This is the output of my screen
== 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
== Parsing '/etc/asterisk/manager.conf': Found
== Manager 'sendcron' logged on from 127.0.0.1
-- Executing AGI("Local/92348023175974@default-cd6b,2", "agi://127.0.0.1:4577/call_log") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
-- Executing Dial("Local/92348023175974@default-cd6b,2", "SIP/204|20|to") in new stack
-- Called 204
-- SIP/204-09e26930 is ringing
-- Starting simple switch on 'Zap/1-1'
== Starting Zap/1-1 at default,s,1 failed so falling back to exten 's'
== Starting Zap/1-1 at default,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')
-- SIP/204-09e26930 answered Local/92348023175974@default-cd6b,2
> Channel Local/92348023175974@default-cd6b,1 was answered.
== Manager 'sendcron' logged off from 127.0.0.1
-- Executing Playback("Local/92348023175974@default-cd6b,1", "sip-silence") in new stack
-- Playing 'sip-silence' (language 'en')
== Spawn extension (default, 92348023175974, 2) exited non-zero on 'Local/92348023175974@default-cd6b,2'
-- Executing DeadAGI("Local/92348023175974@default-cd6b,2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16-----ANSWER-----15-----0") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... --15-----0 completed, returning 0
-- Executing AGI("SIP/204-09e26930", "agi://127.0.0.1:4577/call_log") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
-- Executing AGI("SIP/204-09e26930", "agi-VDAD_ALL_outbound.agi|NORMAL-----LB") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/agi-VDAD_ALL_outbound.agi
-- AGI Script agi-VDAD_ALL_outbound.agi completed, returning 0
-- Executing Goto("SIP/204-09e26930", "default|8600051|1") in new stack
-- Goto (default,8600051,1)
-- Executing MeetMe("SIP/204-09e26930", "8600051|F") in new stack
-- 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'
== 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

[gardo]

Here's the snippet from extensions.conf:

; parameters for agi-VDAD_ALL_inbound.agi (9 fields separated by five dashes "-----"):
; 1. the method of call handling for the script:
; - CID - CID received, add record with phone number
; - CIDLOOKUP - Lookup CID to find record in whole system
; - CIDLOOKUPRL - Restrict lookup to one list
; - CIDLOOKUPRC - Restrict lookup to one campaign's lists
; - CLOSER - Closer calls from VICIDIAL fronters
; - ANI - ANI received, add record with phone number
; - ANILOOKUP - Lookup ANI to find record in whole system
; - ANILOOKUPRL - Restrict lookup to one list
; - 3DIGITID - Enter 3 digit code to go to agent
; - 4DIGITID - Enter 4 digit code to go to agent
; - 5DIGITID - Enter 5 digit code to go to agent
; - 10DIGITID - Enter 10 digit code to go to agent
; 2. the method of searching for an available agent:
; - LO - Load Balance Overflow only (priority to home server)
; - LB - <default> Load Balance total system
; - SO - Home server only
; 3. the full name of the IN GROUP to be used in vicidial for the inbound call
; 4. the phone number that was called, for the log entry
; 5. the callerID or lead_id of the person that called(usually overridden)
; 6. the park extension audio file name if used
; 7. the status of the call initially(usually not used)
; 8. the list_id to insert the new lead under if it is new (and CID/ANI available)
; 9. the phone dialing code to insert with the new lead if new (and CID/ANI available)
; 10. the campaign_id to search within lists if CIDLOOKUPRC
; 11. the user to queue the call to for AGENTDIRECT in-group calls
; inbound VICIDIAL call with CID delivery through T1 PRI

exten => 1234,1,Answer ; Answer the line
exten => 1234,2,AGI(agi-VDAD_ALL_inbound.agi,CID-----LB-----CL_GALLERIA-----7274515134-----Closer-----park----------999-----1)
exten => 1234,3,Hangup

The one in bold is responsible for inbound ACD.

Inbound dialplan is different from outbound dialplan. As you can see from the snippet above.

It's recommended to put your inbound in "trunkinbound".

Here's an example of defining a Zap trunk in extensions.conf:

TRUNK=Zap/g1 ; Trunk interface

We're assuming that "g1" is also defined in your zapata.conf.

Hi Gardo,

Thanks for the response. You seem to be the only one that understands this challenge so far. Most of the responses have been on SIP which has been quite frustrating. At least with the information that we need to configure extensions.conf manually our challenges have been resolved to some extents.

Now these are the questions:

1. Considering my zapata.conf that has a context of default, which part of extensions.conf conf do we write the dial plan?

2. From all indications, de wo need to write two different dial plans, one for inbound, the other for outbound?

3. Do we place the inbound within the context of trunkinbound or with the default?

4. How is the trunk defined in the case of Zap?


Further information, upon replacing the dialplan with exten=>s, the call goes but only to the softphone not the vicidial interface. I believe a clarity in this case will go a long way to help us understand vicidial better.

I will really appreciate your response.

[gardo]

This dialplan will route all calls to SIP 204 from DID 9234NXXNXXXXXX. If you want this to go to the Vicidial inbound script, check my post above.

This is my dial plan
exten => _9234NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _9234NXXNXXXXXX,2,Dial(SIP/204,20,to)
exten => _9234NXXNXXXXXX,3,Hangup

[walex]

Hello gardo, i really appreciate your contribution
i saw your responds to oshonubi,
This is the inbound number to be called, 07098141858, assuming i'm want to use 234 as my country code, from your post above
"exten => 1234,1,Answer ; Answer the line
exten => 1234,2,AGI(agi-VDAD_ALL_inbound.agi,CID-----LB-----CL_GALLERIA-----7274515134-----Closer-----park----------999-----1)
exten => 1234,3,Hangup"

1)i don't underdtand the meaning of that 1234,
2) How can i define that g1 in zapata.conf,

[oshonubi]

Hi Gardo,

Thanks for response. The following are my observations:

1. The configuration you gave was on T1 while my zap is TDM400.

2. What does the number 1234 in the exten=>1234 mean. Is that the DID by the carrier? Can we keep it or use our DID?

3. The number, 7274515134 is it arbitrary or from the carrier?

4. The CL_GALLERIA must it be defined as an IN_GROUP or arbitrary?

5. Can all these by defined by the DID in the Administration Interface?

I have followed based on your advice, however whenever I dialed into the system, using the DID, I get 'That is not a valid extension'

Please explain this

It's recommended to put your inbound in "trunkinbound".

Does it mean we have to copy the following to trunkinbound context in the extensions.conf

exten => 1234,1,Answer ; Answer the line
exten => 1234,2,AGI(agi-VDAD_ALL_inbound.agi,CID-----LB-----CL_GALLERIA-----7274515134-----Closer-----park----------999-----1)
exten => 1234,3,Hangup

We're assuming that "g1" is also defined in your zapata.conf.

How do we define the g1 interface in zapata.conf

Whenever I dial the number, this is what I get.

vici*CLI>
== 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
-- Starting simple switch on 'Zap/1-1'
== Starting Zap/1-1 at default,s,1 failed so falling back to exten 's'
== Starting Zap/1-1 at default,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')
== 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
-- 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'

[gardo]

1234 is the DID being sent by your carrier to your Asterisk server.
7274515134 is the phone number that was called, for the log entry

You can check the parameters below for the different fields and their values.

; parameters for agi-VDAD_ALL_inbound.agi (9 fields separated by five dashes "-----"):
; 1. the method of call handling for the script:
; - CID - CID received, add record with phone number
; - CIDLOOKUP - Lookup CID to find record in whole system
; - CIDLOOKUPRL - Restrict lookup to one list
; - CIDLOOKUPRC - Restrict lookup to one campaign's lists
; - CLOSER - Closer calls from VICIDIAL fronters
; - ANI - ANI received, add record with phone number
; - ANILOOKUP - Lookup ANI to find record in whole system
; - ANILOOKUPRL - Restrict lookup to one list
; - 3DIGITID - Enter 3 digit code to go to agent
; - 4DIGITID - Enter 4 digit code to go to agent
; - 5DIGITID - Enter 5 digit code to go to agent
; - 10DIGITID - Enter 10 digit code to go to agent
; 2. the method of searching for an available agent:
; - LO - Load Balance Overflow only (priority to home server)
; - LB - <default> Load Balance total system
; - SO - Home server only
; 3. the full name of the IN GROUP to be used in vicidial for the inbound call
; 4. the phone number that was called, for the log entry
; 5. the callerID or lead_id of the person that called(usually overridden)
; 6. the park extension audio file name if used
; 7. the status of the call initially(usually not used)
; 8. the list_id to insert the new lead under if it is new (and CID/ANI available)
; 9. the phone dialing code to insert with the new lead if new (and CID/ANI available)
; 10. the campaign_id to search within lists if CIDLOOKUPRC
; 11. the user to queue the call to for AGENTDIRECT in-group calls
; inbound VICIDIAL call with CID delivery through T1 PRI

exten => 1234,1,Answer ; Answer the line
exten => 1234,2,AGI(agi-VDAD_ALL_inbound.agi,CID-----LB-----CL_GALLERIA-----7274515134-----Closer-----park----------999-----1)
exten => 1234,3,Hangup

[oshonubi]

Hi Gardo,

Greetings! Thanks for the response. I really appreciate it. From all indications, for a Zap user, he may need to do his configuration at the back end. The reason is very simple, the carrier does not support zap interface for the time being. To this extent, you advice worked. The system is up and running for now still trying to test it.

The followings are what I did.

1. On the extensions.conf, default context, I wrote my dial plan. In my country there exist various operators with different numbering plans. For instance the legacy CDMA operators and cable line operators use 7 digits, while the new CDMA operators, GSM operators use 11 digits. My PSTN operator uses 11 digits as well. To this extent, I did various dial plans for all the operators to take care of the outbound call. Now my system can dial any of these lines taking into considerations, area codes as well.

2. I found it difficult inputing the DID at the front end to work, to this extent, I used your instructions

exten => 1234,1,Answer ; Answer the line
exten => 1234,2,AGI(agi-VDAD_ALL_inbound.agi,CID-----LB-----CL_GALLERIA-----7274515134-----Closer-----park----------999-----1)
exten => 1234,3,Hangup

However I changed the 1234 to s since all I got was "that is not a valid extension". Then I changed the CL_GALLERIA to "MY_INGROUP"
So my new inbound dial plan is

exten => s,1,Answer ; Answer the line
exten => s,2,AGI(agi-VDAD_ALL_inbound.agi,CID-----LB-----MY_INGROUP-----7274515134-----Closer-----park----------999-----1)
exten => s,3,Hangup

It is working though still under testing.

I hope to do a better documentation on this for Zap interface users if need be.

Once again Gardo, it is good getting you to assist.

Thank you.

[walex]

Here's the snippet from extensions.conf:

; parameters for agi-VDAD_ALL_inbound.agi (9 fields separated by five dashes "-----"):
; 1. the method of call handling for the script:
; - CID - CID received, add record with phone number
; - CIDLOOKUP - Lookup CID to find record in whole system
; - CIDLOOKUPRL - Restrict lookup to one list
; - CIDLOOKUPRC - Restrict lookup to one campaign's lists
; - CLOSER - Closer calls from VICIDIAL fronters
; - ANI - ANI received, add record with phone number
; - ANILOOKUP - Lookup ANI to find record in whole system
; - ANILOOKUPRL - Restrict lookup to one list
; - 3DIGITID - Enter 3 digit code to go to agent
; - 4DIGITID - Enter 4 digit code to go to agent
; - 5DIGITID - Enter 5 digit code to go to agent
; - 10DIGITID - Enter 10 digit code to go to agent
; 2. the method of searching for an available agent:
; - LO - Load Balance Overflow only (priority to home server)
; - LB - <default> Load Balance total system
; - SO - Home server only
; 3. the full name of the IN GROUP to be used in vicidial for the inbound call
; 4. the phone number that was called, for the log entry
; 5. the callerID or lead_id of the person that called(usually overridden)
; 6. the park extension audio file name if used
; 7. the status of the call initially(usually not used)
; 8. the list_id to insert the new lead under if it is new (and CID/ANI available)
; 9. the phone dialing code to insert with the new lead if new (and CID/ANI available)
; 10. the campaign_id to search within lists if CIDLOOKUPRC
; 11. the user to queue the call to for AGENTDIRECT in-group calls
; inbound VICIDIAL call with CID delivery through T1 PRI

exten => 1234,1,Answer ; Answer the line
exten => 1234,2,AGI(agi-VDAD_ALL_inbound.agi,CID-----LB-----CL_GALLERIA-----7274515134-----Closer-----park----------999-----1)
exten => 1234,3,Hangup

The one in bold is responsible for inbound ACD.

Inbound dialplan is different from outbound dialplan. As you can see from the snippet above.

It's recommended to put your inbound in "trunkinbound".

Here's an example of defining a Zap trunk in extensions.conf:

TRUNK=Zap/g1 ; Trunk interface

We're assuming that "g1" is also defined in your zapata.conf.

Hi Gardo,

Thanks for the response. You seem to be the only one that understands this challenge so far. Most of the responses have been on SIP which has been quite frustrating. At least with the information that we need to configure extensions.conf manually our challenges have been resolved to some extents.

Now these are the questions:

1. Considering my zapata.conf that has a context of default, which part of extensions.conf conf do we write the dial plan?

2. From all indications, de wo need to write two different dial plans, one for inbound, the other for outbound?

3. Do we place the inbound within the context of trunkinbound or with the default?

4. How is the trunk defined in the case of Zap?


Further information, upon replacing the dialplan with exten=>s, the call goes but only to the softphone not the vicidial interface. I believe a clarity in this case will go a long way to help us understand vicidial better.

I will really appreciate your response.