Page 2 of 2

Re: Upgrading ViciBox v.8 to Asterisk 13

PostPosted: Wed Apr 25, 2018 6:05 pm
by mflorell
I believe that Asterisk 13.20 does have the patched AMD on it. We did a lot of testing on AMD and it seems to work like it did in the 11.X branch now.

As for a new version of vicibox, not sure what the timeline on that is at the moment.

Re: Upgrading ViciBox v.8 to Asterisk 13

PostPosted: Wed Apr 25, 2018 6:07 pm
by vkad
mflorell wrote:Also, check your server version in the web admin. If your system is properly configured, you shouldn't be running the "AST_update.pl" script at all under Asterisk 13, it should be running the "AST_update_AMI2.pl" script.



Apart from running perl install.pl do we need to change anything else to disable "AST_update.pl" and enable "AST_update_AMI2.pl"

Re: Upgrading ViciBox v.8 to Asterisk 13

PostPosted: Wed Apr 25, 2018 6:20 pm
by mflorell
You just need to make sure that the Asterisk version on the Modify Server page is set correctly, VICIdial will take care of the rest.

Re: Upgrading ViciBox v.8 to Asterisk 13

PostPosted: Sun Apr 29, 2018 10:06 pm
by rrb555
Using ViciPhone I am getting this error message
Code: Select all
[Apr 29 23:00:38] ERROR[2799]: tcptls.c:447 tcptls_stream_close: SSL_shutdown() failed: error:00000005:lib(0):func(0):DH lib, Underlying BIO error: Broken pipe
  == WebSocket connection from 'myserverip:45560' forcefully closed due to fatal write error


Can this be ignored?

Re: Upgrading ViciBox v.8 to Asterisk 13

PostPosted: Thu May 03, 2018 12:14 pm
by Invictus
vkad wrote:Does the latest version of asterisk have Answering Machine Detection? Also, any chance of a new iso? I was thinking of upgrading to new system over the weekend. any chance that we can get the latest iso before then :) thanks.


I also had problems with AMD in asterisk 13 (http://vicidial.org/VICIDIALforum/viewtopic.php?f=4&t=38166&p=132480#p132480), by editing 8369 exten in extensions.conf, problem solved.

in /etc/asterisk/extensions.conf

try changing
Code: Select all
; VICIDIAL_auto_dialer transfer script AMD with Load Balanced:
exten => 8369,1,AGI(agi://127.0.0.1:4577/call_log)
exten => 8369,n,AMD(2000,2000,1000,5000,120,50,4,256)
exten => 8369,n,AGI(VD_amd.agi,${EXTEN})
exten => 8369,n,AGI(agi-VDAD_ALL_outbound.agi,NORMAL-----LB)
exten => 8369,n,Hangup()


to
Code: Select all
; VICIDIAL_auto_dialer transfer script AMD with Load Balanced:
exten => 8369,1,Playback(sip-silence)
exten => 8369,n,AGI(agi://127.0.0.1:4577/call_log)
exten => 8369,n,AMD(2000,2000,1000,5000,120,50,4,256)
exten => 8369,n,AGI(VD_amd.agi,${EXTEN})
exten => 8369,n,AGI(agi-VDAD_ALL_outbound.agi,NORMAL-----LB)
exten => 8369,n,Hangup()

Re: Upgrading ViciBox v.8 to Asterisk 13

PostPosted: Mon May 28, 2018 9:56 pm
by vkad
mflorell wrote:Also, check your server version in the web admin. If your system is properly configured, you shouldn't be running the "AST_update.pl" script at all under Asterisk 13, it should be running the "AST_update_AMI2.pl" script.


How can I check if AST_update_AMI2 is running?

Re: Upgrading ViciBox v.8 to Asterisk 13

PostPosted: Tue May 29, 2018 7:32 am
by mflorell
"ps -A"

You should see "AST_update_AMI2" in the list

Re: Upgrading ViciBox v.8 to Asterisk 13

PostPosted: Tue May 29, 2018 12:21 pm
by williamconley
vkad wrote:
mflorell wrote:Also, check your server version in the web admin. If your system is properly configured, you shouldn't be running the "AST_update.pl" script at all under Asterisk 13, it should be running the "AST_update_AMI2.pl" script.


How can I check if AST_update_AMI2 is running?

Code: Select all
screen -list

Re: Upgrading ViciBox v.8 to Asterisk 13

PostPosted: Thu Jul 19, 2018 12:01 pm
by bedirect
When do you plan to make the ViciBox with Asterisk 13 available?

It's been a while since the latest comments about the time you'll make it available.

We need to do a new installation so it will be nice to get it out of the box.

Re: Upgrading ViciBox v.8 to Asterisk 13

PostPosted: Mon Aug 13, 2018 11:39 am
by kieran333
Hi all,

I have managed to get this working however I keep getting SRTCP unprotect failed because of authentication failure in the CLI output - Any Ideas?

VERSION: 2.14-683a
BUILD: 180809-1547
Asterisk: 13.21.1-vici

Re: Upgrading ViciBox v.8 to Asterisk 13

PostPosted: Wed Aug 15, 2018 4:40 am
by williamconley
kieran333 wrote:Hi all,

I have managed to get this working however I keep getting SRTCP unprotect failed because of authentication failure in the CLI output - Any Ideas?

VERSION: 2.14-683a
BUILD: 180809-1547
Asterisk: 13.21.1-vici


Post the exact code, full line, best if part of the full phone call from beginning to end (not 3000 lines of unrelated code: Just one test call from beginning to end including your error).

Also post your installer with full version (ie: 8.X.X ??) and the link to the instruction set you used for your upgrade (never assume ...).

Re: Upgrading ViciBox v.8.0 to Asterisk 13

PostPosted: Wed Sep 26, 2018 4:12 pm
by alo
Dropping a quick question here.

I want to test running one of the dialer servers on asterisk 13 tomorrow. Is it cool if I only update one of the dialers and leave the others on Asterisk 11.25.3-vici, or will that cause issues? All servers will stay on SVN 3032
Vicibox 8

Re: Upgrading ViciBox v.8.0 to Asterisk 13

PostPosted: Wed Sep 26, 2018 5:10 pm
by williamconley
alo wrote:Dropping a quick question here.

I want to test running one of the dialer servers on asterisk 13 tomorrow. Is it cool if I only update one of the dialers and leave the others on Asterisk 11.25.3-vici, or will that cause issues? All servers will stay on SVN 3032
Vicibox 8


Asterisk version can be different for every server as long as the running vicidial code on all servers is the same and supports all the asterisk instances presently running. So: Assuming SVN 3032 supports asterisk 13, you're good to go.

However: I might suggest a virtual machine for this test instead of taking down a live server (unless you really don't need it ...). That way you can screw it up a few times and just reset to the fresh install (assuming you snapshotted after the fresh install, of course.)