I need to reconfigure my extensions after every update

FreePBX Endpoints
1

I have Freepbx 17.0.25 on Asterisk 22.7.0 as of today.

I have been running since 17 went GA and it has been fine, with module updates all working great.

However, whenever I do a system update which includes Asterisk, it all goes pear shaped.

I am managing 2 systems on the same versions with the same issue. Extensions all login fine and they can dial out, but nobody can be called on their extension. Calls go to voicemail. The fix is to go into edit each extension and hit submit. No changes necessary. Then reload and that extension is working again.

This issue goes to other parts of Freepbx too, but off the top of my head I can’t recall. Undoubtedly they will come to me over the next day as things fail.

When Asterisk does its updates, it keeps the original config files, so that does not seem to be the issue. Also running a fwconsole reload does not do it. I have to touch the extensions (and some other items) first.

I will mention that about a year ago I did an apt install on Asterisk to force an upgrade and this was when I first encountered the issue, but since then everything has been working fine other than updates.

Any ideas? My second system is a large in-production system with lots of Sangoma phone users (which I think were also affected) and I don’t want to bring down a company phone system.

That one is still on Asterisk 22.5.2

Cheers

2

This doesn’t sound right, I have never come across anything like it. Try following the exact steps here and see if things go more smoothly:

For anyone with similar issues on v16, use this:

1 Like
3

Nice procedure there. I pretty much do it this way, although I tend to do the module updates via the gui. I will create a snapshot of the big system and then try it all via CLI and see how it goes.

Great tip on needrestart. I haven’t seen that before and I so often come across systems that have old kernels running because the system wasn’t rebooted.

Cheers.

1 Like
4

I wouldn’t ever do module updates via the GUI unless it was just one or two, and if doing so felt like less effort than logging in over SSH. It crashes, hangs and may be unfinished, yet doesn’t tell you that. You’ll also get a clearer picture if something went wrong, not just a blank page needing a refresh.

1 Like
5

Maybe related but not, there was a bug in an earlier version of 17 that any new extension was created with an incorrect parameter, and it would prevent the extension from being called. Wondering if you are somehow reverting to this ?

6