- Joined
- Dec 13, 2023
- Messages
- 5
- Reaction score
- 1
Hi,
We have been receiving this following alert several times within a single month.
"Trunk L:90000(WebMeeting bridge) has changed status to registered"
I am aware that there is an existing thread that has already been closed
(https://www.3cx.com/community/threads/trunk-notification.75576/).
However, I would like to gain a deeper understanding of why this alert is being triggered in the first place. Specifically, I would like clarification on the underlying reasons or conditions that cause this alert to be raised, rather than focusing only on the alert itself.
Additionally, it would be helpful to know what steps can be taken to prevent this issue from occurring again in the future by addressing the root cause, not just suppressing or acknowledging the alert.
Thank you in advance for your guidance.
We have been receiving this following alert several times within a single month.
"Trunk L:90000(WebMeeting bridge) has changed status to registered"
I am aware that there is an existing thread that has already been closed
(https://www.3cx.com/community/threads/trunk-notification.75576/).
However, I would like to gain a deeper understanding of why this alert is being triggered in the first place. Specifically, I would like clarification on the underlying reasons or conditions that cause this alert to be raised, rather than focusing only on the alert itself.
Additionally, it would be helpful to know what steps can be taken to prevent this issue from occurring again in the future by addressing the root cause, not just suppressing or acknowledging the alert.
Thank you in advance for your guidance.