Hi
@OLOL
I understand your perspective, but it doesn't work that way.
An SBC (Session Border Controller) is a network endpoint that can have users associated with it. These users might belong to different departments, or even the same department. However, there's no department segregation at the network level, as the SBC operates purely on that level.
Think of the SBC as a VPN; it connects everything behind it to the server. Ultimately, it introduces a group of users to the system, and these users need to be assigned to their respective departments.
Even if we could assign an SBC to a specific department (e.g., Sales), implementing logic to automatically add "everything behind the Sales SBC" to the Sales department would be very challenging.
You should add SBCs based on your remote locations. If you have multiple locations, you need multiple SBCs. These SBCs don't need to be department-specific; rather, the users connected behind them should be assigned to the appropriate departments.
I hope this helps!