FreePBX Distro 10.13.66-9 and High Availability.
Freepbx-a is online and master. Freepbx-b is turned off.
Don’t see errors on pcs status.
However I can’t make any calls, I am getting this on the CLI:
Call from ‘5350’ (10.1.12.32:5060) to extension ‘1802’ rejected because extension not found in context ‘from-internal’. That is happening on all extensions.
What is wrong suddenly?
It was working fine before.
This says there is no extension 1802.
Yes, 1802 is a valid extension. I have hundreds of these messages and I get this error on every call I make. Fwconsole restart, reboot, nothing fixes that issue.
My system is down entirely because of this.
[2016-04-28 08:57:29] NOTICE[59931][C-00000009] chan_sip.c: Call from ‘5463’ (10.1.12.35:5060) to extension ‘2627’ rejected because extension not found in context ‘from-internal’.
[2016-04-28 09:14:20] NOTICE[59931][C-0000000c] chan_sip.c: Call from ‘5103’ (10.1.12.10:5060) to extension ‘2442’ rejected because extension not found in context ‘from-internal’.
[2016-04-28 09:18:00] NOTICE[59931][C-0000000d] chan_sip.c: Call from ‘5103’ (10.1.12.10:5060) to extension ‘2442’ rejected because extension not found in context ‘from-internal’.
[2016-04-28 09:20:03] NOTICE[59931][C-00000010] chan_sip.c: Call from ‘5547’ (10.1.12.15:5060) to extension ‘2250’ rejected because extension not found in context ‘from-internal’.
[2016-04-28 09:20:15] NOTICE[59931][C-00000011] chan_sip.c: Call from ‘5547’ (10.1.12.15:5060) to extension ‘5430’ rejected because extension not found in context ‘from-internal’.
There’s something badly wrong with your /etc/asterisk/extensions_additonal.conf
Running ‘fwconsole reload’ from the console should fix it, as that regenerates all the files (the same as clicking the red apply changes button)
IF that doesn’t fix it, please open a commercial support ticket.
Yes, ‘fwconsole reload’ fixed it.
This failure must have happend during a cluster failover, we had some network issue where the nodes swapped roles. Although this shouldn’t corrupt /etc/asterisk/extensions_additonal.conf.
My favorite two-word lie.
I’ve been doing this so long that when I hear “Shouldn’t” I’ve come to associate it with “must have”. I’ve said it a thousand times myself, and almost always end up saying “but somehow it did.” 
I’m pretty sure we all agree that it shouldn’t have, but when you’ve eliminated every logical possibility…
Con el fwconsole reload, no reconoce el comando 
without logs no one can help you
From command line enter:
pcs status
Then show us the output of that command
This thread is 4 years old. Create a new thread with a proper description. Hay una categoría española aqui.