vicidial.org

Hello everyone!,
I have vicidial 2.12 installed from scratch , I have + asterisk + web database on the same server , plus I have an E1 card digium 2 spans on the same server. when I make a call, I answer this is queued and not passed to the agent , This does not happen if you use a SIP carrier . carrier through SIP call if delivered to the agent.

i have centos 6.5 + asterisk 1.8 vici , mariadb 5.5

Any reason you did not install with VICIbox?

io ho un uguale post. io ho installato vicibox 7.0.3 express

I have a Same message. I installed 7.0.3 vicibox express

carletto80 wrote:I have a Same message. I installed 7.0.3 vicibox express

"I have same message" i assume to mean you have the same PROBLEM (not message, LOL). And I will offer you the same advice as njujihara below with one addition: Do not use "express"! Use standard. It's better tested by more users. And be sure the hardware is installed before installing Vicibox at the command line.

njujihara wrote:Hello everyone!,
I have vicidial 2.12 installed from scratch , I have + asterisk + web database on the same server , plus I have an E1 card digium 2 spans on the same server. when I make a call, I answer this is queued and not passed to the agent , This does not happen if you use a SIP carrier . carrier through SIP call if delivered to the agent.

i have centos 6.5 + asterisk 1.8 vici , mariadb 5.5

Please let us in on the secret of why you did not use Vicibox for installation, as Matt asked. This often tells us what your true problem is. If you have enough access to the server to put in a PRI card, you also have enough access to use Vicibox. And your experience will be MUCH better with Vicibox. Seriously.

next up: If I recall correctly, the dialplan entries may be different for a PRI, but configuring the PRI itself is often painful. Verify manual dialing works (just asterisk, no vicidial challenges) first. Then work out autodial and search the extensions.conf (and this board) for PRI irregularities related to adding an audio card to the system.

njujihara wrote:Hello everyone!,
I have vicidial 2.12 installed from scratch , I have + asterisk + web database on the same server , plus I have an E1 card digium 2 spans on the same server. when I make a call, I answer this is queued and not passed to the agent , This does not happen if you use a SIP carrier . carrier through SIP call if delivered to the agent.

i have centos 6.5 + asterisk 1.8 vici , mariadb 5.5

how did yo did it ??

williamconley wrote:

carletto80 wrote:I have a Same message. I installed 7.0.3 vicibox express

"I have same message" i assume to mean you have the same PROBLEM (not message, LOL). And I will offer you the same advice as njujihara below with one addition: Do not use "express"! Use standard. It's better tested by more users. And be sure the hardware is installed before installing Vicibox at the command line.

njujihara wrote:Hello everyone!,
I have vicidial 2.12 installed from scratch , I have + asterisk + web database on the same server , plus I have an E1 card digium 2 spans on the same server. when I make a call, I answer this is queued and not passed to the agent , This does not happen if you use a SIP carrier . carrier through SIP call if delivered to the agent.

i have centos 6.5 + asterisk 1.8 vici , mariadb 5.5

Please let us in on the secret of why you did not use Vicibox for installation, as Matt asked. This often tells us what your true problem is. If you have enough access to the server to put in a PRI card, you also have enough access to use Vicibox. And your experience will be MUCH better with Vicibox. Seriously.

next up: If I recall correctly, the dialplan entries may be different for a PRI, but configuring the PRI itself is often painful. Verify manual dialing works (just asterisk, no vicidial challenges) first. Then work out autodial and search the extensions.conf (and this board) for PRI irregularities related to adding an audio card to the system.

my boss like centos....

Then your boss will LOVE GoAutoDial. Automated installer for Vicidial ... On CentOS! (And remember to thank Gardo!)

finally install vicibox. and works fine now i try to configure AMD ,I have a sore brain trying to configure this... but i call sangoma and they tell me LYRA not sell anymore.....

all you have to do is change the routing extension to 8369.

williamconley wrote:all you have to do is change the routing extension to 8369.

you would not bleave how meeny times ive for got to do this << when creating new canpains

p.s. this setting needs to be inputed in Campaign, Details,then under routing extension. add the above and AMD will Work and bu the look of it you have 12.2
thir is now

AM Message Wildcards -This option, if enabled, allows you to go to the AM Message Wildcard administration page where you can define wildcards that can match data in a default lead field and can play a different message based upon the data in a specific lead. Default is N for disabled

AMD send to Action -This option allows you to define whether a call is sent to the AMD Action when an answering machine is detected. If this is set to N, then the call will be hung up as soon as it is determined to be an answering machine. Default is N.

CPD AMD Action -If you are using the Sangoma ParaXip Call Progress Detection software then you will want to enable this setting either setting it to DISPO which will disposition the call as AA and hang it up if the call is being processed and has not been sent to an agent yet or MESSAGE which will send the call to the defined Answering Machine Message for this campaign. Default is DISABLED. Setting this to INGROUP will send an answering machine to an inbound group. Setting this to CALLMENU will send an answering machine to a Call Menu in the system.

CPD Unknown Action -If you are using the Sangoma ParaXip Call Progress Detection software and you want to send calls that have an Unknown result to a destination other than an agent, then you will want to enable this setting either setting it to DISPO which will disposition the call as AA and hang it up if the call is being processed and has not been sent to an agent yet or MESSAGE which will send the call to the defined Answering Machine Message for this campaign. Default is DISABLED. Setting this to INGROUP will send an answering machine to an inbound group. Setting this to CALLMENU will send an answering machine to a Call Menu in the system.

all of witch are good to use and help adviod AM's or just redirect them wair ever you like if at all

hope it helps