Is it possible to change minor asterisk versions without needing a reinstall of the system? I recently went from 22 to 20.17, but I need 20.18 for the UCM patch, which I plan to use in the future. Can it be done? Or is that unavoidable?
You can switch Asterisk versions without having to reinstall the entire system. The method to do so will depend on how you built the system. Some more information is needed.
I’d also add that if you are patching Asterisk then you can not use binary packages provided by FreePBX. You would have to build it from patched source, or if someone else is producing binary packages get them from elsewhere.
Sure, it’s a Virtual Machine on VirtualBox, using the FPBX17 ISO that’s available, I think I used the most recent one, the system has a 64GB virtual drive, 2GB RAM, 128MB VRAM (That’s the max VBOX would allow me to allocate), 2-core virtual processor, and using a bridged adapter
Hope this info helped, if not, feel free to inquire about the needed info
I’m going to guess that A, the info didn’t help, B, changing minor versions of Asterisk to what I want is NOT possible, or C, a combination of the two
Was hoping to not have to rebuild my phone system the long way around, or have a version mismatch between the phone system and the patch, but that’s okay, if the versions are mismatched, the versions are mismatched, I’ll just live with it
Your build used packaged versions of Asterisk that were created for FreePBX distros. As it was pointed out, patching the packaged versions is a lot tougher. Every time you update Asterisk you would need to re-patch it (regardless of source or package install methods).
Unless you are using a 3rd party version of chan_sip, you would never be able to get passed Asterisk 20 as chan_sip was removed in v21. So you need to make a choice; Stay on Asterisk 20 (which will be EOL this year) so that you have chan_sip you can patch. Or always have to add a 3rd party release of chan_sip then patch it.
The first options leaves you with zero support for Asterisk and the second option leaves you zero support for chan_sip/UCM outside of the authors or those that use it.
I’d be okay with that, I’m just waiting for the UCM patch to have a stable version of the Asterisk V22 patch, I also don’t anticipate requiring support until it comes time for me to clone the virtual drive onto a physical one for a laptop so I can have a server running nearly 24/7, but that’s a subject for another time. Just wishing I could get to V20.18 from V20.17, since that’s what the patch calls for, I’ll be okay once the system is patched
EDIT: I should probably mention that if using the Beta patch for V22 is a better choice, I’m open to the suggestion, and plus, who knows? I might get bored of Cisco on SIP and can locate the SCCP firmware and use the ChanSCCPB module instead, they both do about the same thing
Guessing I’m SOL…?
First of all SCCP is broken in later Asterisk versions. I produced a guide for patching SCCP into current Asterisk versions but the problem with later Asterisk versions is you can make calls from SCCP phones to other SCCP phones and you can make calls from SIP phones to other SIP phones but you can no longer make calls from SCCP to SIP phones as the internal bridge is broken.
Secondly the biggest proponent of SCCP was cygnut and he died a number of years ago. chan_sccpb is a dead project at this time unless a dev with considerable Asterisk experience picks it up. But it would only be of interest to an antique telephone museum, and the largest one of those - Connections Museum - is still waffling over whether or not to put effort into a VoIP exhibit, as their main focus is rotary dial gear.
Thirdly, the SIP firmware for all the Cisco phones is readily available on the Internet even though it is scattered but search engines can dig it out for you. Only insane people with Cisco phones would revert a SIP loaded Cisco phone back to SCCP.
Forth, the USECALLMANAGER patch isn’t supported even by the USECALLMANAGER author on FreePBX, only on Asterisk. Meaning, that there is ZERO support in the community of USECALLMANAGER users to patch into the FPBX17 ISO.
I’ve been running the “beta” batch of UCM on V22 for almost a month now, it works fine including BLF keys, etc. You will want to review the Issues in the github for it since there’s one mod you will need to make that the dev said will be fixed in the next patch version.
The only recommended way to run FreePBX with USECALLMANAGER is to install Debian, build Asterisk from scratch adding in the patch, then run the FreePBX 17 installer with the –noasterisk option, then set the asterisk version in FreePBX to version 20 so that the chan_sip front end is activated. For BLF you want to add that into the post extensions config since the regular extensions config file is auto-generated by FreePBX.
Mmkay, so this is way more complicated than I wanted it to be… should still be fun though, I’m not quite ready for that endeavor yet as I’m still just running the phone system on a VM, I’ll be wanting to build it on an actual computer sometime later
I just now felt the need to ask; there are guides on doing this, right? Like building Asterisk from scratch and installing FPBX with the -noasterisk option?
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.