MiVB Cluster Behavior and User Management Limitations
Mitel Administration (MA) can manage users in MiVoice Business (MiVB) clusters, but only under certain conditions. Whether a user can be managed depends on which MiVB system is connected and where the user is hosted.
Supported User Scenarios
| User Setup | Supported? | Explanation |
|---|---|---|
|
A (Primary Host A) |
Yes | The user is hosted on the same MiVB that MA is connected to. |
|
A-B (Primary A, Secondary B) |
Yes | The user is hosted on Primary A, and changes sync to Secondary B. |
|
B-A (Primary B, Secondary A) |
Partially | The user is hosted on B, but MA is connected to A. Some actions may work, but full management is not guaranteed. |
|
B (Primary Host B only) |
No | The user is hosted on B, and MA is not connected to it. The system shows “MiVB not reachable.” |
Template Limitations
- If a user template refers to a MiVB that is not connected to MA, it may import successfully but cannot be used to create users.
- In newer versions, MA may block such templates during import to avoid errors.
Error Message Behavior
If you try to manage a user whose Primary MiVB is not the one MA is connected to, you may see this message: "MiVB not reachable".
This means MA cannot reach the user’s actual Primary MiVB, so the user cannot be managed.
CLD-Based Deployments
In CloudLink Daemon (CLD) environments, you can explicitly assign which MiVB controls a user. This makes it easier to manage users correctly, compared to older CloudLink Gateway (CLGW) setups.