FYI Not Quite Soup: Wazo 18.03

[2devnull]

When will the script be ready for 18.01? That is what the latest ISO installs:

WARNING: Incredible PBX image for version 18.01 is not yet available.
You have two options. Stop here and try later by pressing Ctrl-C now.
If you abort install now, you can rerun this install script again later.
Proceed with the install and manually configure everything in the GUI.
To continue with installation, press ENTER. Or press Ctrl-C to abort

Thanks

 

[wardmundy]

Coming soon.

 

[2devnull]

Great.....will there be a way to easily upgrade or another fresh install will be required?

 

[wardmundy]

Great.....will there be a way to easily upgrade or another fresh install will be required?

Have you tried following the existing tutorial to upgrade your server? That's all we do to build a newer one. Just change the version number.

 

[2devnull]

Have you tried following the existing tutorial to upgrade your server? That's all we do to build a newer one. Just change the version number.

Hey Ward, no I didn't. Will take a look (however 18.01 is now on Debian Stretch, so hope things wouldn't break in the script due to certain things like ifconfig etc Stretch no longer installs automatically)

EDIT: Seems need to change one statement:
****************************************************************************
* *
* The Debian GNU/Linux system must be upgraded from version 8 (jessie) *
* to 9 (stretch). This is mandatory to upgrade to newer versions of Wazo. *
* To do this, you must run the following command: *
* *
* wazo-dist-upgrade *
********************

*****************************************************************************
* *
* The Debian GNU/Linux system will be upgraded from version 8 (jessie) *
* to 9 (stretch). Hence, this upgrade will be longer than other upgrades. *
* *
* Please make sure you have read the upgrade notes: *
* http://documentation.wazo.community/en/latest/upgrade/18.01/stretch.html *
* *
* You must RESTART the machine after the upgrade. *
* *
*****************************************************************************

Update: After upgrade, I got this email. Assuming it is already taken care of?

Return-Path: <[email protected]>
X-Original-To: [email protected]
Delivered-To: [email protected]
Received: by wazo.incrediblepbx.com (Postfix, from userid 0)
id ; Thu, 1 Feb 2018 09:19:32 -0500 (EST)
Subject: Debconf: Configuring postgresql-common -- Obsolete major version 9.4
To: <[email protected]>
X-Mailer: mail (GNU Mailutils 2.99.98)
Message-Id: <[email protected]>
Date: Thu, 1 Feb 2018 09:19:32 -0500 (EST)
From: [email protected] (root)

The PostgreSQL version 9.4 is obsolete, but the server or client packages
are still installed. Please install the latest packages (postgresql-9.6
and postgresql-client-9.6) and upgrade the existing clusters with
pg_upgradecluster (see manpage).

Please be aware that the installation of postgresql-9.6 will automatically
create a default cluster 9.6/main. If you want to upgrade the 9.4/main
cluster, you need to remove the already existing 9.6 cluster
(pg_dropcluster --stop 9.6 main, see manpage for details).

The old server and client packages are no longer supported. After the
existing clusters are upgraded, the postgresql-9.4 and
postgresql-client-9.4 packages should be removed.

Please see /usr/share/doc/postgresql-common/README.Debian.gz for details.

--
Debconf, running at [ Debconf is not confident this error message was displayed, so it mailed it
to you. ]​

Update:
After the upgrade to 18.01, pbxstatus shows Debian 8 (Jessie) instead of Stretch even after reboot. Assuming this isn't an issue either. UPDATE: It seems it is hard-coded: OSrelease="Debian 8 (jessie)". I made the change in the pbxstatus script.

Right now on 17.17 I have only tested with Google Voice and for outbound calls it is one-way. I know from reading here that this is usually due to NAT, however I don't have this issue on the same server with an older Scientific Linux Incredible PBX I have been running for years. Is there anything Wazo does differently in this regard?

 

[wardmundy]

Looks like you missed a step or two...

The upgrade must be done with three commands:

• xivo-dist phoenix: Ensures your system is not restricted to a specific version
• wazo-upgrade: Installs the wazo-dist-upgrade script and makes sure the system is up-to-date.
• wazo-dist-upgrade: Upgrade to the latest version of Wazo with Debian 9 (stretch). This upgrade will take longer than usual.

You may need to reboot your machine before and after running wazo-dist-upgrade. wazo-dist-upgrade will tell you if a reboot is needed.

 

[2devnull]

I seemed to have made it through the upgrade "successfully" AFAIK. My earlier problem still remains (any help on that is appreciated):

I have only tested with Google Voice and for outbound calls it is one-way. I know from reading here that this is usually due to NAT, however I don't have this issue on the same server with an older Scientific Linux Incredible PBX I have been running for years. Is there anything Wazo does differently in this regard?

 

[2devnull]

Just an update to this. I fixed my issue. It was the IP phone. Apparently *RTP encryption* was set to on and for Wazo, it needed to be off.

 

[2devnull]

Well, all over a sudden today I get a message that the party is busy or unreachable. Looked in the log file and saw this:
Unable to create channel of type 'Motif' (cause 66 - Channel not implemented)

Since it was working just before bed last night, I suspect a GV OAuth time out? How to fix this?

 

[Sylvain Boily]

No, looks like you chan_motif.so is not loaded. By default is not loaded in wazo, so check your modules.conf.

 

[Sylvain Boily]

No, looks like you chan_motif.so is not loaded. By default is not loaded in wazo, so check your modules.conf.

And also it depends on res_xmpp.so.

 

[wardmundy]

For the pioneers, I think we're ready...

It’s Soup: The Definitive Quick Start Guide to Wazo 18.03

 

[billsimon]

I've been playing with Wazo 18 but can't figure out the new admin interface. I installed all the plugins but they seem kind of... sparse? Do you know when we can expect that side of things to get filled out? Basically I loaded them and looked around but the only way to really do anything useful is to go back to the classic interface.

 

[wardmundy]

@billsimon: The best answer will probably come from @Sylvain Boily.

Another word of caution. The move to Debian 9 by 3CX and Wazo is problematic for those on a budget. None of the OpenVZ (i.e. cheap cloud) providers of which we are aware support the new 3.x kernel which means you are forced to use KVM platforms. These typically cost about double the price of comparable OpenVZ platforms. The solution used to be OVH, but they now have almost doubled the price of their platform. This leaves you with Vultr and Digital Ocean basically.

 

[wardmundy]

Well, there's some good news and bad news. The good news is the upgrade from 17.17 to 18.03 appears to work fine. The bad news is that new installs with Debian 9 and 18.03 fails because the configuration wizard is broken. We've reported the issue to @Sylvain Boily and will have to await a fix. In the meantime, we've rolled back to tutorial and installer to 17.17. Sorry.

 

[ZachG]

Another word of caution. The move to Debian 9 by 3CX and Wazo is problematic for those on a budget. None of the OpenVZ (i.e. cheap cloud) providers of which we are aware support the new 3.x kernel which means you are forced to use KVM platforms. These typically cost about double the price of comparable OpenVZ platforms. The solution used to be OVH, but they now have almost doubled the price of their platform. This leaves you with Vultr and Digital Ocean basically.

OVH is still offering their VPS SSD 1 @ $4.47/mo.
https://www.ovh.com/world/vps/vps-ssd.xml
it looks like they're moving away from that product, and they're not deploying it in the new US data center. but i've had very good performance with Beauharnois location (i'm in Ohio).
They offer unmetered bandwidth, so i've got another vps running Nextcloud & acting as my personal VPN.

 

[wardmundy]

Spent a good bit of time wrestling with Wazo 18.03 installer over this weekend. No cigar!

If you start with a minimal install of Debian 9 as suggested on the Wazo site, the install bombs:

The following packages have unmet dependencies (no hint what those might be!):
 xivo-base : Depends: wazo-auth but it is not going to be installed
             Depends: wazo-service but it is not going to be installed
             Depends: wazo-webhookd but it is not going to be installed
             Depends: xivo-confd but it is not going to be installed
             Depends: xivo-ctid-ng but it is not going to be installed
             Depends: xivo-dird but it is not going to be installed
             Depends: xivo-manage-db but it is not going to be installed
             Depends: xivo-websocketd but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 xivo : Depends: xivo-base (= 14:18.03~20180212.153210.c5ff859.deb9) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
./wazo_install.sh: line 65: xivo-service: command not found

This is even after tweaking to enable en_US.UTF-8 with dpkg-reconfigure locales AND adding a number of missing pieces to the minimal install:

apt-get update
apt-get -y install cloud-init
apt-get -y install wget gnupg gnupg1 gnupg2 dialog
apt-get -y install network-manager nano wget python2.7
wget http://mirror.wazo.community/fai/xivo-migration/wazo_install.sh
chmod +x wazo_install.sh
./wazo_install.sh

I think it is fair to say that the Wazo Devs are installing this on a platform that is materially different than a minimal Debian 9 OS.

So we're leaving this for @Sylvain Boily & Co. to sort out.

 

[wardmundy]

What will work is to install Incredible PBX for Wazo 17.17 and then upgrade by issuing these commands. That gets you to 18.03.

 

[Sylvain Boily]

Hello, this issue is happened this week end because debian released a new version of stretch with a new version of postgres. It broke our packaging... We'll fix this issue today. Sorry about that.

 

[wardmundy]

Hello, this issue is happened this week end because debian released a new version of stretch with a new version of postgres. It broke our packaging... We'll fix this issue today. Sorry about that.

Thanks, @Sylvain Boily. That's the downside of open source development with lots of moving parts. Personally, I'm not sure Debian 9 is quite ready for production use.