TUTORIAL Incredible Wazo Upgrade to 17.17

[wardmundy]

Incredible PBX for Wazo 17.13 is now available with new Admin GUI and Asterisk 14.6.1. See steps above for upgrade procedure for existing servers and new upgraded security model info. Details here. Changelog here. Updated tutorial here. Be sure to also perform the Google Voice upgrade procedure if you're updating from any existing version. It's now covered in the upgrade procedure above.

Build verified (above) on WootHosting.

 

[kyle95wm]

@wardmundy when I did the upgrade, it overwrote the changes I made in
/etc/nginx/sites-enabled/xivo I had to comment out the default cert lines and re-add my own custom ones.

 

[wardmundy]

Yep. This is something @Sylvain Boily definitely needs to fix. Not sure why Wazo has to overwrite the NGINX config with every new release. There needs to be some way to protect custom settings and certificates.

 

[kyle95wm]

Wazo has documentation on using your certs, but the setup is a PITA. The upside is these cert configs will be persistent across upgrades. However, the certs must be under the default cert directory.

 

[JFrost]

Upgrading from 17.13 to 17.14 using procedure in post #47.
At 'wazo-upgrade' got error about not finding repo and can't download "xivo-upgrade"

Am not sure about the advice to 'run "xivo-dist phoenix" '.
Please advise,
thx.


Output:

---------------------

2017-10-11 02:44:46 root@pbx:~# wazo-upgrade
Could not find any Wazo repository to download "xivo-upgrade" from. Check your /etc/apt/sources.list.d or run "xivo-dist phoenix".
2017-10-11 02:44:54 root@pbx:~#​

 

[wardmundy]

Upgrading from 17.13 to 17.14 using procedure in post #47.
At 'wazo-upgrade' got error about not finding repo and can't download "xivo-upgrade"

Am not sure about the advice to 'run "xivo-dist phoenix" '.


Output:

---------------------

2017-10-11 02:44:46 root@pbx:~# wazo-upgrade
Could not find any Wazo repository to download "xivo-upgrade" from. Check your /etc/apt/sources.list.d or run "xivo-dist phoenix".
2017-10-11 02:44:54 root@pbx:~#​

I've alerted @Sylvain Boily and the other developers that there's a problem with the latest update. Thanks.

 

[wardmundy]

A new step was added in this release so the upgrade procedure should start like this...

xivo-dist wazo-17.14
apt-get update
/etc/init.d/netfilter-persistent stop
wazo-upgrade
iptables-restart
...

Tutorial has been modified accordingly.

 

[JFrost]

A new step was added in this release so the upgrade procedure should start like this...

xivo-dist wazo-17.14
apt-get update
/etc/init.d/netfilter-persistent stop
wazo-upgrade
iptables-restart
...

Tutorial has been modified accordingly.

Thanks ward. I have copied those instructions to a script (and 'sed' update the version before running.) Do you know if this new step of 'apt-get update' going to be permanent or just for this run?

Thank you.


Edit -
Appears to be upgrading properly now fyi. Ty.

 

[wardmundy]

Will be fixed in next release.

 

[kyle95wm]

I see we're having a problem with the latest version of Wazo. No thanks on upgrading for now. I'm staying on my trusty 17.13

 

[JFrost]

Thank you Ward for moving my posts to a new thread https://pbxinaflash.com/community/threads/wazo-17-14-upgrade-issues.21985/#post-132928

It does look like the second snippet of code (that updates OAuth) is probably responsible for the problem in some way as all that Sylvain did to fix was recompile the XMPP module, which appears to be what that second code snippet was touching. Apparently it IS possible for that code to bork the Asterisk service.

I think it warrants looking into. Figuring out exactly what part of the script broke Asterisk is over my head but maybe it's as simple as a version check before running? (don't run if last run == same asterisk version as current)

Or maybe there is/was a problem with git repo or something else... idk like I said, but it does seem worth looking into in case it's a bug so someone else doesn't get hit.


J.

 

[wardmundy]

It's not a bug. We've already upgraded a half dozen servers with no problems.

 

[JFrost]

Have you tried running it against an already patched server and see what happens?

 

[kyle95wm]

@wardmundy you might wanna add this as part of the upgrade steps

cp /etc/nginx/sites-enabled/xivo /root

and then before nginx restarts:

cp /root/xivo /etc/nginx/sites-enabled/xivo

 

[wardmundy]

@kyle95wm: Good idea, especially now that we support HTTPS credentials.

 

[wardmundy]

Incredible PBX for Wazo 17.15 is now available with new Admin GUI and Asterisk 15.0.0. See steps above for upgrade procedure for existing servers and new upgraded security model info. Details here. Changelog here. Updated tutorial here.

NOTE: There is no (working) native Google Voice support in this build. You'll need to use Simonics SIP/GV gateway for the time being.

Build verified (above) on Vultr.

 

[kyle95wm]

Someone will have to try this upgrade on a server and let me know how it goes. I may do this upgrade in a couple weeks on production.

 

[wardmundy]

Hopefully we'll have the Google Voice component decoded by then.

 

[kyle95wm]

I don’t really care about GV since it’s not relevant to my infrastructure. I just want to make sure my install won’t break.

 

[bcimaglia]

Following the upgrade process to go from 17.13 to 17.15 and adding
noload => app_flite.so to modules.conf 17.15 and run with the current config. The issue that I am having is adding a new static IP using add-ip,

The following services are available for activation with 184.111.111.111:

0 - ALL Services

1 - SIP (UDP)

2 - SIP (TCP)

3 - IAX

4 - Web

5 - WebMin

6 - FTP

7 - t*f*t*p

8 - SSH

9 - AutoConfig

Enter the services desired by number. Separate entries with commas.

For example: 1,4 would activate standard UDP SIP plus web access.


0


The following whitelisted services were requested for 184.111.111.111:

ALL Services

[ ok ] Restarting netfilter-persistent (via systemctl): netfilter-persistent.service.

No IPtables problems found.

IPtables now running.

[ ok ] Restarting fail2ban (via systemctl): fail2ban.service.

Another app is currently holding the xtables lock. Perhaps you want to use the -w option?

Another app is currently holding the xtables lock. Perhaps you want to use the -w option?

Another app is currently holding the xtables lock. Perhaps you want to use the -w option?

iptables v1.4.21: invalid mask `' specified

Try `iptables -h' or 'iptables --help' for more information.

The following iptables rules now are in effect for 184.111.111.111:

I am not sure what I am missing and it is probably something simple but does anyone have a suggestion?