After misinterpreting a less than candid marketing release from Sangoma in October, I found myself the unwitting production user of alpha code for FreePBX 15. Believe the developers, not the marketers. However…
The upgrade from Asterisk 13 to 16 was without incident and hands off.
The GUI upgrade script to FreePBX 15 from 14 also worked like a charm with no human intervention. When this is finally released for the masses, stock installs of FreePBX/Asterisk should have little issue.
Except…
First Issue: Upon completion of the upgrades I suddenly had codec issues. The codec_g729.so file installed with the upgrade (as well as one other I don’t use) did not have its owner:group properly set to asterisk:asterisk and its permissions set to 755. This was evidenced by incoming callers hearing silence and outgoing calls largely ringing busy. Easy fix. Change permissions and owners.
Second Issue: My trunk SIP settings were suddenly inadequate. Apparently in prior iterations of FreePBX certain settings were picked up from general Advanced and SIP settings and were default for trunks. I say this because my installations worked flawlessly prior to the upgrade. Whether or not this trunk default setting is supposed to be the case now or whether I was simply benefitting from an unfound bug or an undocumented feature is unknown. Doesn’t matter. The fix was to explicitly declare disallow=all, allow=ulaw&alaw&g729 (in my case) and sendrpid=yes as well as trustrpid=yes (in my case, your VoIP provider may need different settings) in the trunk SIP settings.
Other than these two momentarily frightening and puzzling issues, the upgrade was completely uneventful except for my premature jump into alpha code on production machines.
If you have GUI exceptions pop up on 15, try doing explicit upgrades of named modules instead of fwconsole ma updateall. Because my nightly OS and application updates used updateall, and because I was now on alpha code, the code updates were not always in sync. This may require manual inspection and intervention from time to time until GA.
It should also be noted that when code hiccups occur the fix will typically be applied to stable FreePBX first and then 15 a few hours later as was my experience this week. The code is seemingly stable enough that I elected not to rebuild machines and downgrade to GA code.
One final recommendation - when reporting bugs in the 15 code, perhaps add a line at the top of your description which says PERTAINS TO VERSION 15 so that users and support alike can discriminate more easily. Do this even if you have correctly specified the version in the reporting fields above. This might have avoided a Trumpian text exchange earlier in the week. The clean version is:
U: This fish smells.
S: Search for better smelling fish. All our fish smells good.
U: But THIS fish smells.
S: It can’t smell, we got rid of all our smelly fish. Search for non-smelly fish. (another search performed)
U1 & U2: Dammit - we both say THIS fish smells.
S: OHHHHHHH! Yes, THAT fish smells. Why didn’t you say so in the first place!
(Fish replaced. Everybody happy.)
Memo to self: Never, never, never, ever act on a marketing announcement. Duh. That said, this is the most stable alpha code I have ever seen.