vicidial.org

by **wizzbangca** » Wed Sep 29, 2010 6:39 pm

I have been working with VicidialNOW with no problems for well over a year now. I go to use goautodial now that it's out of rc stage and start having problems immediately. I downloaded goautodial yesterday and successfully install on an AMD 64 3000+ system with 512 ddr ram. Connected to the SIP trunk just fine. Created a user and extension for the user to use. The soft phone connects just fine. The user logs in to the test campaign I created with my cell phone as the only number. The soft rings and when answered says there is currently only one person in the conference. So far so good.

At this point the campaign is set to manual dial. The user clicks to dial the next available number. My cell phone rings and i pick up. The user and i can hear each other just fine.

I set the campaign to ratio dialing and a ratio of 4 to 1. I reset the only lead in the database. Log the user out and have them log back in. My phone rings, I say "hello" and nothing else happens. I look at the asterisk logs, the default survey hello file was never played.

I went looking around for something to help me figure out what is happening. I found something about the audio store. I set that up. Tried the test survey again and got the same response. Looked around for more help, and found no one has had a problem with the survey campaign just hanging up on them. Doesn't quite surprise me.

I'm at a loss. Logs are below.

[Sep 29 19:09:17] -- SIP/sipgully-00000007 answered Local/91XXXXXXXXXX@default-04f1,2

[Sep 29 19:09:17] > Channel Local/91XXXXXXXXXX@default-04f1,1 was answered.

[Sep 29 19:09:17] -- Executing [8373@default:1] Playback("Local/91XXXXXXXXXX@default-04f1,1", "sip-silence") in new stack

[Sep 29 19:09:17] ERROR[11263]: utils.c:966 ast_carefulwrite: write() returned error: Broken pipe

[Sep 29 19:09:17] ERROR[11263]: utils.c:966 ast_carefulwrite: write() returned error: Broken pipe

[Sep 29 19:09:17] ERROR[11263]: utils.c:966 ast_carefulwrite: write() returned error: Broken pipe

[Sep 29 19:09:17] == Manager 'sendcron' logged off from 127.0.0.1

[Sep 29 19:09:17] -- <Local/91XXXXXXXXXX@default-04f1,1> Playing 'sip-silence' (language 'en')

[Sep 29 19:09:17] WARNING[11317]: file.c:1292 waitstream_core: Unexpected control subclass '-1'

[Sep 29 19:09:17] -- Executing [8373@default:2] AGI("Local/91XXXXXXXXXX@default-04f1,1", "agi://127.0.0.1:4577/call_log") in new stack

[Sep 29 19:09:17] -- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0

[Sep 29 19:09:17] -- Executing [8373@default:3] AMD("Local/91XXXXXXXXXX@default-04f1,1", "2000|2000|1000|5000|120|50|4|256") in new stack

[Sep 29 19:09:17] -- AMD: Local/91XXXXXXXXXX@default-04f1,1 XXXXXXXXXX begin_of_the_skype_highlighting 1 XXXXXXXXXX end_of_the_skype_highlighting (null) (Fmt: 64)

[Sep 29 19:09:17] -- AMD: initialSilence [2000] greeting [2000] afterGreetingSilence [1000] totalAnalysisTime [5000] minimumWordLength [120] betweenWordsSilence [50] maximumNumberOfWords [4] silenceThreshold [256]

[Sep 29 19:09:17] -- AMD: Changed state to STATE_IN_SILENCE

[Sep 29 19:09:18] -- AMD: Channel [Local/91XXXXXXXXXX@default-04f1,1]. Too long...

[Sep 29 19:09:18] -- AMD: Channel [Local/91XXXXXXXXXX@default-04f1,1]. Too long...

[Sep 29 19:09:18] -- Executing [8373@default:4] AGI("Local/91XXXXXXXXXX@default-04f1,1", "VD_amd.agi|8373") in new stack

[Sep 29 19:09:18] -- Launched AGI Script /var/lib/asterisk/agi-bin/VD_amd.agi

[Sep 29 19:09:19] -- AGI Script VD_amd.agi completed, returning 0

[Sep 29 19:09:19] -- Executing [8373@default:5] AGI("Local/91XXXXXXXXXX@default-04f1,1", "agi-VDAD_ALL_outbound.agi|SURVEYCAMP-----LB") in new stack

[Sep 29 19:09:19] -- Launched AGI Script /var/lib/asterisk/agi-bin/agi-VDAD_ALL_outbound.agi

[Sep 29 19:09:20] -- AGI Script agi-VDAD_ALL_outbound.agi completed, returning 0

[Sep 29 19:09:20] -- Executing [8373@default:6] AGI("Local/91XXXXXXXXXX@default-04f1,1", "agi-VDAD_ALL_outbound.agi|SURVEYCAMP-----LB") in new stack

[Sep 29 19:09:20] -- Launched AGI Script /var/lib/asterisk/agi-bin/agi-VDAD_ALL_outbound.agi

[Sep 29 19:09:21] -- AGI Script agi-VDAD_ALL_outbound.agi completed, returning 0

[Sep 29 19:09:21] -- Executing [8373@default:7] Hangup("Local/91XXXXXXXXXX@default-04f1,1", "") in new stack

[Sep 29 19:09:21] == Spawn extension (default, 8373, 7) exited non-zero on 'Local/91XXXXXXXXXX@default-04f1,1'

[Sep 29 19:09:21] -- Executing [h@default:1] DeadAGI("Local/91XXXXXXXXXX@default-04f1,1", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------") in new stack

[Sep 29 19:09:21] -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0

[Sep 29 19:09:21] -- Executing [h@default:1] DeadAGI("Local/91XXXXXXXXXX@default-04f1,2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16-----ANSWER-----17-----4") in new stack

[Sep 29 19:09:22] -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... --17-----4 completed, returning 0

[Sep 29 19:09:22] == Spawn extension (default, 91XXXXXXXXXX, 2) exited non-zero on 'Local/91XXXXXXXXXX@default-04f1,2'

by **wizzbangca** » Wed Sep 29, 2010 6:56 pm

I just tried to use predictive dialing by following the steps on page 16 of the manager's manual. Guess what? I got hung up right way, given no chance to say hello. I really don't know what to do.

by **mflorell** » Wed Sep 29, 2010 7:25 pm

Have you tried it without AMD?

by **wizzbangca** » Wed Sep 29, 2010 8:07 pm

I tried with 8366, 8373, 8368. All with the same results.

by **mflorell** » Wed Sep 29, 2010 8:12 pm

Please post agiout logfile output of this call.

by **williamconley** » Wed Sep 29, 2010 9:52 pm

when you post, please post your entire configuration including (but not limited to) your installation method and OS with kernel or version, vicidial version and build, asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box.

Similar to This:
Vicibox X.X from .iso | Vicidial X.X.X Build XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation

this IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)
____

help matt help you, be sure he knows what you are working with

also: have you tried this in auto-dial 1:1 ratio with a single logged in user before switching to "remote agent" 4:1? makes the logs smaller and often resolves the issue (then switching to remote 4:1 is a formality)

by **wizzbangca** » Wed Sep 29, 2010 9:56 pm

by **wizzbangca** » Wed Sep 29, 2010 10:10 pm

Funny how many people have been, and keep on ignoring you. Maybe you should try reading before policing. People might pay more attention.

williamconley wrote:when you post, please post your entire configuration including (but not limited to) your installation method and OS with kernel or version, vicidial version and build, asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box.

Similar to This:
Vicibox X.X from .iso | Vicidial X.X.X Build XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation

this IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)
____

help matt help you, be sure he knows what you are working with

also: have you tried this in auto-dial 1:1 ratio with a single logged in user before switching to "remote agent" 4:1? makes the logs smaller and often resolves the issue (then switching to remote 4:1 is a formality)

by **mflorell** » Wed Sep 29, 2010 10:16 pm

Local channel resolution issue, check your firewall this usually is caused by one-way audio.

by **williamconley** » Wed Sep 29, 2010 10:27 pm

wizzbangca wrote:Funny how many people have been, and keep on ignoring you. Maybe you should try reading before policing. People might pay more attention.

williamconley wrote:when you post, please post your entire configuration including (but not limited to) your installation method and OS with kernel or version, vicidial version and build, asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box.

Similar to This:
Vicibox X.X from .iso | Vicidial X.X.X Build XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation

this IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

interesting. i did. i don't see your vicidial version, asterisk version or any versions (yesterday helps right now, but does not rule out any changes or "updates" after download).

i don't police (i didn't delete your entry), i am trying to help. you'd be surprised how many times matt and the rest of us "helpers" have gone to a great deal of effort to help someone only to find out later that they made some modification to the system which would have been revealed by the version numbers in question and was the problem the whole time.

and we are Troubleshooting here. i don't know about you, but when I troubleshoot, i like to do a quick baseline check before i begin to be sure i know what i'm dealing with. (yep, there's gas in the tank ... that sort of thing)

simply trying to help. that's why you're here, right? :roll:

but if you don't think i'm helpin ...

by **wizzbangca** » Wed Sep 29, 2010 11:03 pm

You may not be policing, but the amount of use of the one size fits all message you use sure seems like it. When I first joined the forum, browsing around was much more enjoyable without the constant policing message you use. You would probably get a better response with a custom message. A custom message does show you are trying to help with the problem.

With your newest message, you pointed out a major detail I thought I mentioned. Without you pointing that out, I would keep overlooking the fact I didn't mention anything about updates.

I'm using the standard goautodial iso downloaded yesterday with no updates or configuration changes except what was mentioned above. I have been able to duplicate this problem on three other computers and a virtual machine using two different sip providers.

by **mflorell** » Wed Sep 29, 2010 11:24 pm

This is usually a firewall issue that causes loss of audio or one-way audio.

I would also recommend not using a virtual machine.

Have you tried replicating this issue with ViciBox?

by **wizzbangca** » Thu Sep 30, 2010 12:03 am

In the morning I will check the firewall. Thanks for the suggestion. I don't use virtual machines for anything other than basic troubleshooting and testing. A physical system is always used for production.

I haven't used vicibox. Might be worth looking into as an alternative.

by **wizzbangca** » Thu Sep 30, 2010 2:49 pm

Added port 5060 to the network firewall. No change. I can register a phone outside the network now and get the dialer to start dialing out from outside the network. Calls are still immediately hung up on using all campaign vdad extensions and all dialing methods except manual. On manual, both parties can hear each other. Not sure if that constitutes as one way audio.

by **mflorell** » Thu Sep 30, 2010 4:20 pm

If you are using SIP you need to open a lot more than that. Usually 10000-20000 and if this is a separate router it really needs to be SIP-aware.

by **wizzbangca** » Thu Sep 30, 2010 6:46 pm

Opening all the ports I can find related to SIP didn't work. There is only 1 router on the network, and that's the one that we're configuring. The existing SIP phones are working fine.

We tried vicibox, but ended up getting lost between the install and following the installation instructions on the website.

by **mflorell** » Thu Sep 30, 2010 7:25 pm

What version of ViciBox and which install instructions?

by **wizzbangca** » Thu Sep 30, 2010 7:26 pm

Everything came from the website about 4 hours ago. We downloaded the iso from the server portion of the website and followed the Walk Through on the server portion of the site as well. The walk through assumes the live cd is used. The server disc doesn't follow the walk through and the walk through doesn't follow the server disc. When the installer is an average computer user and I'm 1200 miles away trying to walk through the installation using the Walk Through to get to the point whereI can take over with ssh, walk throughs that don't follow the server disc doesn't exactly help out too much.

edit: added more details

by **wizzbangca** » Thu Sep 30, 2010 9:18 pm

we re-tried vicibox for the heck of it. What a mistake. We experienced the following problems immediately:

1. Apache doesn't automatically start. As if any of my clients are going to want to remember to start apache if they have to restart the dialer. Why should I have to go modify linux start up to start apache automatically?

2. A 404 is returned when trying to access /vidial/welcome.php. Apache configuration in vicibox is so unfamiliar to me, no way am I going to try to figure out why a 404 shows up. I tried trolling through the linux file system to find the location of the php files, good luck with that. They're not in the standar /var/www or /var/www/html directories. Anyways, this problem shouldn't be happening anyway.

I have scrapped the idea of using vicibox again. The downloaded iso should never have those two problems for any reason. What other problems are there if I did seem to figure out how to solve the 404 error?

by **Kumba** » Fri Oct 01, 2010 12:10 am

Along the same lines of what William stated, your unwillingness to divulge the version numbers of what you downloaded are not helping us help you. Unfortunately there are multiple ways you can download ViciBox and other components. While it may seem apparent to you, those of us not involved in this project with you do not know these things intuitively.

Just to make sure we are on the same page, I will assume you downloaded the versions linked to from the vicibox.com website. Those versions would be these links:

http://download.vicidial.com/iso/vicibo ... -3.0.5.iso
http://download.vicidial.com/iso/vicibo ... nstall.pdf

If what you downloaded was not the above then you have downloaded an older version of ViciBox.

Assuming that you downloaded and installed the above software using the above guide, then I would venture to guess that you didn't say 'Y' to install the web server role. This would result in Apache not starting, and returning a 404 error page. It is also possible that you did not install the OS onto the hard-drive, or when rebooting you did not boot from the hard drive.

Your local channel resolution issue is usually caused by poorly configured sip.conf settings, or a bad network setup (router/etc). I can help you diagnose things and recommend settings to change that would probably resolve your issue, but I am choosing not to. Good luck with your install.

vicidial.org

Survey Campaigns Drop Calls When Answered

Survey Campaigns Drop Calls When Answered

Who is online