Recent content by Valamagules

Check what you are sharing with other elements in the SDS sharing form. Not everything should be shared across the cluster, so make sure you only enable the things that should be shared. For example, the MiCollab would have nothing to do with Embedded VM, and because it does not understand this...

Correct, trusted service level does not consume a device license.

Use a trusted extension and call reroute it always to voicemail. Two things to remember 1) to tick the activate call flow option in the call flow. 2) enable transfer to any number in the voicemail option settings

Presuming you are using MiVB, the option is Meet Me conferencing, which is has very limited functionality and unlicensed. If you have a MiColllab server with the MiVB, then your best option is to use the AWV module that comes with it. This is a licensed moduled, and has more conferencing functions.

I am wondering the same

If you have a single IP (LAN), then your MBG config will be that of a DMZ deployment. You will need to be very specific with your NATing rules, Mitel has documented this clearly in the Engineering guidelines. Yes it is possible for the 4 scenarios you have outlined.

In Voicemail Option, you will find how many digit should a voicemail be. The default value is 3, so I think it’s throwing this error because your extension range is 4 but the vm is still set to 3. Make sure you set the value to match the extension range which in your case 4. Warning - if you...

Have you tried deleting the user and re-create?

Is this a new PC workstation or was an earlier version of console work on it before? If I can remember clearly, Console is not supported on some Windows’s version, like Home Edition lincensed, there is a compatibility list in MOL.

This is where export and import comes handy. Simply export out the RG form (Selected only) and then renumber the user according to your ring order preferences. Then delete all member from the RG then import the modified form.

If you choose to connect the systems back, then need to Sync the system back to SLS, sync with he DLM and do a blank sync between the MiVB members once you have the systems hooked back online. Critical LV means you are in hot water if you don’t fix it.

The symptoms indicates that the systems are in a sharing license cluster (DLM). Systems needs to continue to communicate with the licensing server (online) to ensure the licensing status remains healthy. If you remove one system from the cluster or offline, you will get into this LV status...

Connect RS323 cable and check messages. Alarm points to either a boot issue or database/disk read.

Do you see any traffic on the CCS trace on either the SMB or EX? Is the IP trunk configuration correct between the two PBX? SSH to the MiVb that is hosting the SIP trunk and run tugtail command and make calls in to see if calls is actually landing in the MiVB and the messages. If calls are...