Possible bug - clicking "Disable All" on SIP trunks page also disables all bridge connections

[urofi]

v16 Enterprise version on Debian. I'm testing a SIP provider for a new location, which is bridged with 2 other locations. I see no way to disable just one SIP trunk besides deleting it so I go and click on "Disable All" on the SIP Trunk page. To my surprise this also disabled all bridge connections, they show red instead of green. This even works if there are no configured SIP trunks, clicking Disable All will still disable bridges.

This seems like an oversight, I would want bridge connections to stay alive no matter what unless I explicitly disable them, there should be a separate way to disable bridges on the bridge page, and not for bridges to be affected by disabling SIP trunks. I can imagine situations where I'd want SIP trunks disabled but bridges functioning, such as an issue with spam calls or other issue with the SIP provider.

Also seems this proves that bridges are basically sip trunks in a GUI disguise.

 

[cobaltit]

Technically bridges are SIP trunks as evident by the trunk count on the dashboard. While not expected, at least the status is reflected correctly. Good catch.

 

[YiannisH_3CX]

Hello @urofi

Please note that we are aware of this behaviour as technically bridges are trunk connections. We will look into it however and see if any improvements can be made for the future. For the time being however this will remain as is.