Bug on ViciBox 5.0.3 - causing eternal waiting for ring

[ricardochenhe]

Problem:
Vicidial shows 'waiting for ring..." even after the call is picked up

Bug:
Server information is defaulted with asterisk version 1.4.x.x instead of 1.8.23.0

Solution:
1. Change the asterisk version
2. Rebuild conf files
3. wait for it to take effect
4. Dial and cross fingers

[Kumba]

Not sure how you installed ViciBox v.5.0.3 and got an asterisk version of 1.4. That was a ViciBox v.5.0.0 bug. At this point without more information about how things were installed I would have to say it's a user contributed error.

[ricardochenhe]

I used standard ViciBox5.i686-5.0.3

Steps:
1. Boot from liveCD
2. os-install
3. reboot and answer the questions (hostname, etc)
3. vicibox-install
4. reboot

I don't recall if there was a value with default 1.4.x.x asterisk during the install process but I'm sure I didn't type or selected any.

[williamconley]

Vicibox 5.0 has been known to place "1.4" in the server value even though 1.8 is installed.

Usually wait for ring only persists if the dialplan does not include the agi line. Vicidial is never notified the call was answered because vicidial wasn't listening (agi script attaches Vicidial to the call ... no agi = vicidial isn't listening). manual dial calls often use a different dial prefix than the campaign so this is easily caused by multiple or non-standard carrier configurations.

[ricardochenhe]

Hi William,

I read about dial plan missing the agi line, however my dial plan has it and it started working properly after I changed the asterisk version while mantaining the dialplan untouch.

I only tested manual dial thou.

I copied the dialplan from a existing and known good vicibox 4.x.x.

I'll post the dialpan in the next post

[williamconley]

don't copy dialplans from server to server.

use the "copy sample conf files" option during install. that way your conf files (including dialplan) will match your svn revision.

anything custom should be in the GUI (under system or server settings or in the call menu etc).

[ricardochenhe]

Ooops, sorry, I copied it from the GUI, not the .cnf file itself.

This is my dial plan

exten => _91XXXXXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91XXXXXXXXXX,2,Dial(SIP/${EXTEN:1}@gafachi3a,,tTo)
exten => _91XXXXXXXXXX,3,Hangup

[Kumba]

I am guessing he took a database from a ViciBox v.4 database and moved it to this new server after he installed v.5 on it.

[williamconley]

don't think so. then he wouldn't have had to copy the dialplan ... it would already have been there.

As he said, it was the 1.4 asterisk version in the version field when 1.8 was installed by the installer. This is a known bug is it not?

[Kumba]

don't think so. then he wouldn't have had to copy the dialplan ... it would already have been there.

As he said, it was the 1.4 asterisk version in the version field when 1.8 was installed by the installer. This is a known bug is it not?

If you have a database installed and working on ViciBox v.4.0. The asterisk version would be 1.4. Now if you install ViciBox v.5, drop the database, and re-import the database from the v.4 installation, asterisk version would be 1.4.

ONLY version 5.0.0 had the 1.4 bug. The database on v.5 would show 1.4 but that's not a dialer.

[williamconley]

We just installed with 5.0.3 (but it says 5.0.2 because the ssh splash screen wasn't updated) and experienced this same error.

[ricardochenhe]

My install was a clean install, did not imported anything from old version.

I have another box with 4.x.x and all I did was to copy the dial plan and account entry from the GUI, because both boxes (4.x and 5.0.3 box) use the same carrier.

[ricardochenhe]

Maybe the bug got fixed in the preload version but not in the standard liveCD ISO?