Asterisk Version Switch from 13 to 16


(Jyoti) #1

Hello Team,

I wanted to upgrade AMI 3.4 to 4.1 so first I have upgraded AMI 3.4 to 3.5 successfully.

Then the system suggested to me switch the Asterisk Version 13 to 16. And when I switched Asterisk 16, it displays as beta version.

Please help how to proceed as I dont want beta and at first place it should switch to beta version.

Before Upgrade FreePBX Details: We have determined you are running TWM-AMI v3.4

…and your SmartUpgrade stub is v3.1.2

This means you are running FreePBX Distro v12.7.6-1910-1.sng7

with FreePBX Framework version 14.0.13.23

which is currently using Asterisk v13.29.2

We have determined you are running TWM-AMI v3.5

…and your SmartUpgrade stub is v3.1.2

This means you are running FreePBX Distro v12.7.6-2002-2.sng7

with FreePBX Framework version 14.0.13.28

which is currently using Asterisk v16.9.0 b

Please help.


#2

Asterisk version 16.9.0 is the current release (not beta) version available in the Distro.


(Jyoti) #3

then why does it display as " Asterisk v16.9.0 b"

what does it mean


(Itzik) #4

How did you switch? You need to run

asterisk-version-switch

(Jyoti) #5

I used ```
smartupgrade asterisk-version-switch


And even `asterisk-version-switch` give the same options and results

(Lorne Gaetz) #6

Your system rpms are out of date. If you upgrade, you will not see the beta message:

yum upgrade asterisk-version-switch

(Jyoti) #7

My system is up to date. Nothing to do message I am getting when fired above mentioned yum upgrade command


#8

β€œsmart upgrade” seems to be a third party tool; either ask the developer of that tool, or don’t use it and use only the standard tools being referenced here.


(Sergio Lobera) #9

I think @billsimon is on the correct path, are you using an AWS instance ?

Can you share with us the output of this command? yum repolist


(Jyoti) #10

[root@TestGoogleeServer ~]# yum upgrade asterisk-version-switch
Loaded plugins: fastestmirror, versionlock
Loading mirror speeds from cached hostfile
No packages marked for update
[root@TestGoogleeServer ~]# yum repolist
Loaded plugins: fastestmirror, versionlock
Loading mirror speeds from cached hostfile
repo id repo name status
sng-base/7/x86_64 Sangoma-7 - Base 10,019
sng-epel/7/x86_64 Sangoma-7 - Sangoma Epel mirror 16,253
sng-extras/7/x86_64 Sangoma-7 - Extras 419
sng-pkgs/7/x86_64 Sangoma-7 - Sangoma Open Source Packages 1,286
sng-updates/7/x86_64 Sangoma-7 - Updates 2,235
repolist: 30,212


(Jyoti) #11

Yes I am using AWS Instance.


(Jyoti) #12

[root@TestGoogleeServer ~]# asterisk-version-switch

Press 1 for Asterisk 13 (LTS) (With Opus and G729 codecs)
Press 2 for Asterisk 15 (With Opus and G729 codecs)
Press 3 for Asterisk 16 (LTS) (With Opus and G729 codecs)
Press 4 for Asterisk 13 Certified (LTS) (With Opus and G729 codecs)
Press 5 for Asterisk 17

Press 9 to exit and not change your Asterisk Version

Pick the Asterisk Version you would like to change to:

I choose option 3 and the results is as mentioned above


#13

What results? you have never posted the output of asterisk-version-switch before. You have only shown the output of the third-party tool.


(Jyoti) #14

I have switched the Asterisk version From "Asterisk v13.29.2
" [quote=β€œLinux_01, post:1, topic:67256”]

which is currently using Asterisk v13.29.2

To

which is currently using Asterisk v16.9.0 b

[/quote]

Its displays Asterisk v16.9.0 b

Why there is b

the options given by both smartupgarde asterisk-version switch

and asterisk-version switch are both same and also results are also same.

I tried twice


(Jyoti) #15

What I am trying to say is:

I have tried to switch the Asterisk Version 13 to 16 by using both options; ie by using command β€œsmartupgarde asterisk-version switch” and β€œasterisk-version-switch”.

In both cases, the output version is " Asterisk v16.9.0 b"

So where am I going wrong

Please help


#16

I think your provider has customized the image in a way that is preventing standard yum from working as we expect; so you should ask the provider of your image for help. Or change to something more standard.


(Jyoti) #17

We have we want to do in-place upgarde of FreePBX TWM AMI Version3.4 to V4.1.

So I have take AMI backup of current AWS EC2 instance and build a test server with the AMI.

After doing in-place upgrade from AMI 34. to AMI 4.1 they have recommenced to switch Asterisk Version. My current " Asterisk v13.29.2" and upgraded to β€œAsterisk v16.9.0 b”

Need guidance for this as I am new to FreePBX


(Jared K Smith) #18

Just out of curiosity, what’s the output of β€œrpm -q asterisk16” after switching to Asterisk 16 using β€œasterisk-version-switch”?


(Jyoti) #19

rpm -qa asterisk16

asterisk16-16.9.0-1.sng7.x86_64

CLI> core show version
Asterisk 16.9.0 built by mockbuild @ jenkins7 on a x86_64 running Linux on 2020-03-21 00:51:54 UTC

smartupgrade show-current-version

β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ•— β–ˆβ–ˆβ•—β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ•— β–ˆβ–ˆβ•—
β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•—β–ˆβ–ˆβ•‘ β–ˆβ–ˆβ•‘β–ˆβ–ˆβ•”β•β•β•β•β• β–ˆβ–ˆβ•”β•β•β•β•β•β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•—β–ˆβ–ˆβ•”β•β•β•β•β•β–ˆβ–ˆβ•”β•β•β•β•β•β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•—β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•—β•šβ–ˆβ–ˆβ•—β–ˆβ–ˆβ•”β•
β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•‘β–ˆβ–ˆβ•‘ β–ˆβ•— β–ˆβ–ˆβ•‘β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•”β•β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•— β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•”β•β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•”β• β•šβ–ˆβ–ˆβ–ˆβ•”β•
β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•‘β–ˆβ–ˆβ•‘β–ˆβ–ˆβ–ˆβ•—β–ˆβ–ˆβ•‘β•šβ•β•β•β•β–ˆβ–ˆβ•‘ β–ˆβ–ˆβ•”β•β•β• β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•—β–ˆβ–ˆβ•”β•β•β• β–ˆβ–ˆβ•”β•β•β• β–ˆβ–ˆβ•”β•β•β•β• β–ˆβ–ˆβ•”β•β•β–ˆβ–ˆβ•— β–ˆβ–ˆβ•”β–ˆβ–ˆβ•—
β–ˆβ–ˆβ•‘ β–ˆβ–ˆβ•‘β•šβ–ˆβ–ˆβ–ˆβ•”β–ˆβ–ˆβ–ˆβ•”β•β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•‘ β–ˆβ–ˆβ•‘ β–ˆβ–ˆβ•‘ β–ˆβ–ˆβ•‘β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•—β–ˆβ–ˆβ•‘ β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ•”β•β–ˆβ–ˆβ•”β• β–ˆβ–ˆβ•—
β•šβ•β• β•šβ•β• β•šβ•β•β•β•šβ•β•β• β•šβ•β•β•β•β•β•β• β•šβ•β• β•šβ•β• β•šβ•β•β•šβ•β•β•β•β•β•β•β•šβ•β•β•β•β•β•β•β•šβ•β• β•šβ•β•β•β•β•β• β•šβ•β• β•šβ•β•

Welcome to SmartUpgrade for AWS FreePBX!

Performing pre-upgrade cleanup of tmp directory…

Updating SmartUpgrade script manager to the latest version…
…done.

Setting permissions and running script manager now…
Checking your current SmartUpgrade stub version…
Your SmartUpgrade stub is up-to-date. Continuing…

Checking your current TWM-AMI version…
Downloading updated version matricies…

We have determined you are running TWM-AMI v4.1

…and your SmartUpgrade stub is v3.1.2

This means you are running FreePBX Distro v12.7.6-2002-2.sng7
with FreePBX Framework version 15.0.16.49
which is currently using Asterisk v16.9.0 b


(Jyoti) #20

Please confirm whether its the Asterisk Version β€œAsterisk v16.9.0 b” is beta as mentioned above.