- Joined
- Apr 19, 2021
- Messages
- 31
- Reaction score
- 6
Hey,
So I ran into an odd issue today, not sure if this is by design or a bug.
I have the latest version of 3CX installed on Debian (18.0.237)
If I go to SIP Trunks- Select a single trunk- hit Disable All
ALL trunks are disabled, both selected and unselected. But the status is not reflected on the portal. All trunks appear to be enabled and functioning, but of course no external calls can be made.
It caused a bit of a panic this morning as I was disabling a SBC after hours last night, and this morning got a call from the client saying the system was down
. After troubleshooting with the SIP provider, I realized that all the trunks had become disabled instead of just the SBC, even though they are still showing green and registered in the portal.
My question-
Should a disabled trunk show up as 'disabled' or 'offline' on the portal?
Does the 'Disable All' button disable ALL trunks, or only those that are selected?
So I ran into an odd issue today, not sure if this is by design or a bug.
I have the latest version of 3CX installed on Debian (18.0.237)
If I go to SIP Trunks- Select a single trunk- hit Disable All
ALL trunks are disabled, both selected and unselected. But the status is not reflected on the portal. All trunks appear to be enabled and functioning, but of course no external calls can be made.
It caused a bit of a panic this morning as I was disabling a SBC after hours last night, and this morning got a call from the client saying the system was down
My question-
Should a disabled trunk show up as 'disabled' or 'offline' on the portal?
Does the 'Disable All' button disable ALL trunks, or only those that are selected?
