-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Core - Trunks/Routing, fwconsole
-
Labels:None
-
Sprint:Sprint 16!
-
ToDo:
-
Asterisk Version:13.27.1
-
Distro Version:14.0.13.4
-
Distro:FreePBX Distro
Hi,
{{fwconsole trunks --enable 1
fwconsole trunks --disable 1}}
These cmd are only setting the trunk to disabled/enabled status on the DB/web gui.
It does not affect the sip trunk status.
{noformat}
If we disable a trunk from fwconsole and then show the current status from 'sip show peer', we see the trunk is still enabled and registered.
If we enable a disabled trunk (not registered), it's only shown as enabed from the web gui - it's not registering automatically.{noformat}
Official FreePBX wiki is not telling you need to run 'fwconsole reload' after running the trunks cmd. Needs to be updated.