No internal calls. 503 service unavailable

FreePBX Configuration
1

I am in a bit of a pickle. I upgraded full distribution of 2 working systems recently, including my own. Asterisk was held back, so I did a apt install on it, then updated all modules and got it all happy. Or so I thought. I have now found that both system will not make internal calls, nor can they be called into via DIDs.All extensions are registered and can make external calls.

I missed this up until now because my client system is going live tomorrow when numbers are ported and it was during testing today I realised I had broken it.

Here is a SIP fragment showing the call failure.
SIP/2.0 503 Service Unavailable
Via: SIP/2.0/TCP 10.255.0.6:64437;rport=64722;received=202.90.x.x;branch=z9hG4bK53ee13182a746c41
Call-ID: 50fb5b43145d31ea
From: “Mark Dutton” sip:[email protected];tag=6a9c1cb729986d1e
To: sip:[email protected];tag=fdf2412d-5d33-407e-8481-8145ed80a1d2
CSeq: 10757 INVITE
Server: FPBX-17.0.19.28(22.4.1)
Reason: Q.850;cause=34
Content-Length: 0

The Q.850 code is no channel available.

Seem I broke something here and I really need to straighten it out ASAP. Any ideas? I have a feeling this is not a hard fix. I ran verbose logging level 15, but not seeing anything obvious in the output.

System details below
Asterisk 22.4.1
Current PBX Version: 17.0.19.28
Current System Version: 12.7.8-2408-1.sng12
Total Module Count: 88
Enabled: 88

2

OK, I have found that if I go into any extension, save it and update config, that extension is OK. No other components seem to have been affected, but is there a way through fwconsole to force all entries to update the underlying config files in the event of doing something like this?

3

I believe that is what update config does; the .conf files are not maintained incrementally, but are rewritten entirely, from the FreePBX database.

4

I read it that way too, but I had to touch every extension then apply changes to fix the issue.