MiVB virtual

Home Forums Unified Communications MiVoice Business MiVB virtual

Viewing 14 posts - 1 through 14 (of 14 total)
  • Author
  • #5476
    Oleg Pushin

    Hello everyone!

    Have a question regarding MiVB virtual. Frankly speaking I have never worked with this call manager, haven`t even seen it. Have a potential customer now, whom we want to propose MiVB as a communication platform for hotel. About 400 extension and 60 SIP dect terminals are planned to be used. Regarding customer requirements system need to have server and media gateway redundancy. MiVB is supposed to be deployed in VmWare environment on two different hosts. As far as I understood from the manual, MiVB has a native resiliency mechanism besides VmWare HA, which is expensive. First question is – do we need a special license for server redundancy or this lisence MiVoice Business Virtual for Enterprise 54005748 is enough?

    Customer is going to have two PRI links, one per service provider for redundancy. So we need two 3300, which will work as TDM – SIP gateway only. The thing which I can`t understand is how MiVB as call manager works with these gateways, does it control them via MGCP/MEGACO or proprietary protocol, like MXONE control MGU. Or maybe there is just sip trunks are needed between MiVB cluster and 3300?


    When you license a MiVoice Business as Enterprise all your licensing gives you the ability to create a redundant environment. The MiVoice Business has a proprietary communication between the systems. It’s amazing to see the phones fail over to the other controller without even dropping a call. The only issue I see is that is a hotel and if they have analog sets there is no fail over for these devices, only IP of course.

    Oleg Pushin

    Hello Michael!
    Thanks for your answer.
    Sounds great about “seamless” fail over of IP phones. Does it depend on the model of IP phones or signalling protocol, I mean MiNET or SIP?

    And still have a question regarding 3300 if they are used as trunk gateways. Does MiVB controls them or they exist by themselves somehow? I mean what will happen in case of one of the gateways power off for example, will the calls to PSTN be forwarded to another gateway. Or if the primary MiVB server is out of service for some reason, will the calls towards PSTN be distributed&? And another question is, as far as I understood from the documentation, if virtual deployment of MiVB is used then “MiVoice Business Virtual has the following characteristics: ∙ includes Media Server functionality such as conferencing, music on hold, and group paging.” What about hardware media resources that are located on 3300 are they also used or not?


    Here is some information on SIP Devices fail over.

    Each time a SIP device registers with either its primary MiVoice Business system or its
    secondary system, the system transfers the registration information, consisting of the Address
    of Record, Contact, and registration refresh timeout (Expires) parameters.
    SIP endpoint devices support resiliency performance to varying degrees and it is therefore
    useful to classify them based on the resiliency performance level they offer. Mitel classifies SIP
    device resiliency based on the following performance levels:
    • Devices that use DNS Lookup (Bronze level): Most SIP devices in this level achieve resiliency using Domain Name Servers (DNS) that support multiple IP addresses against a
    single Fully Qualified Domain Name (FQDN).
    • Partner devices (Silver level): SIP devices in this level can be programmed to recognize
    the difference between two potential servers and can switch between them if a SIP REGISTER, INVITE, or SUBSCRIBE request times out.
    • Partner devices that support OPTIONS requests (Gold level): SIP devices in this level are
    programmed to switch to the alternate server if a SIP REGISTER, INVITE, SUBSCRIBE,
    or OPTIONS request times out. This feature provides significantly faster failure detection
    by the device and therefore faster failover to the secondary system.
    • Partner devices that support the P-Alternate-Server SIP header (Platinum level): SIP devices in this level support the Mitel proprietary P-Alternate-Server SIP header in 200 OK
    or 301 Moved Permanently responses. The header includes data designating the potential
    servers and which server the device must use.

    If a MiVoice Border Gateway fails it depends on the SIP trunk provider on whether the SIP calls will go to another MBG. I would recommend downloading a copy of the Mitel MiVoice Business RESILIENCY GUIDELINES, this is a great document that walks through the entire process.

    Oleg Pushin

    Michael, thank you very much for your assistance. Understood regarding SIP devices. About gateways, there won`t be MBGs in this scheme, connection to service provider is via E1 trunk with PRI signalling. So, there will be two 3300 CX II with T1/E1 Combo MMC II in each one and they will be used as trunk gateways only, all sip endpoints will register on virtual cluster. I have found another good document called “Mitel Voice Cluster Design and Implementation, Rls 9.0”. There is almost mine scheme on page 27. Here adopted scheme https://yadi.sk/i/pTz1u5ODqTjDew. Do I correctly understand that all licenses (including the major one “MiVoice Business Virtual for Enterprise 54005748”) and license “MiVoice Business License – Digital Link 54000303” to PRI trunks, end user licenses “MiVoice Bus License – Enterprise User 54004975
    “, must be applied to Virtual Primary Node only? The thing i still cannot understand is: what signalling is used between Virtual Nodes and hardware 3300 CX II, is additional license required for internal links?

    Oleg Pushin

    Seems that internal IP trunk are set up using ARS Direct IP Route. Am I right? If yes, do these trunks require license?


    Each controller will have a MiVoice Business base software, and you can apply user licenses to each of the controllers for load balancing. Then you can configure redundancy of the extensions to fail over to other controller if one should fail. If you had two CX controllers with T1/Combo cards for resiliency you would need to apply a digital link licence to each controller. When you cluster the controllers there is not a requirement for any trunk licensing between controllers.

    Oleg Pushin

    It is becoming more clear. In the case if I have:
    Two virtual MiVB (primary and secondary) with one “MiVoice Business Virtual for Enterprise 54005748”, user licenses “MiVoice Bus License – Enterprise User 54004975”, for example 400. This pair of MiVB will handle relisency for IP users – failover.

    Two hardware 3300 CXII with two core license “MiVBus Enterprise SW for 3300 (no users) 54005968” one per each gateway and “MiVoice Business License – Digital Link 54000303” digital trunk license (one per each gateway). This pair of MiVB will handle PSTN trunk resilency.

    Then during installation i should make a cluster which consists of 4 nodes (not 2 as I thought earlier).
    Regarding license mechanism is it mandatory to use Designated License Manager and GARID, like it described here

    Does the secondary virtual MiVB must have his own ARID?


    Yes, each MiVoice Business will have their own ARID on the AMC. So you should have 4 application records, 1 for each vMVB and 1 for each CX controller.

    Oleg Pushin

    Got it, and the last qeustion from me in this branch, I hope. The quantity of MiVoice Business Virtual for Enterprise 54005748 is 1 or 2?


    It sounded like you wer going to have two virtual MiVoice Business systems for resiliency so in that scenario you will need to have 2 54005748 vMVB base packages.

    Oleg Pushin

    Yes, i was talking about two vMiVB, I`ve recently read about license in a cool document System Administration Tool Help, Rls 9.0 SP3. There is a description about license models, so three possible models are described:

    License Model
    The Application Management Center (AMC), Mitel’s license key and product administration service, supports the following license models:

    Standalone System: A standalone system is a single controller that lacks support for clustering, IP trunks or resiliency. All other MiVoice Business features, with the exception of XNET trunks, are supported. A standalone system cannot share its licenses with other systems and does not support resiliency.

    Non-Shared Enterprise System: A non-shared enterprise system is a networked controller that supports the full range of MiVoice Business features and options, including clustering, IP trunks, and resiliency. A non-shared enterprise system cannot share its licenses with other systems.

    Shared Enterprise System: A shared enterprise system is a networked controller that supports the full range of MiVoice Business features and options, including clustering, IP trunks, and resiliency. Because it belongs to an application group in the AMC, a shared enterprise system can share licenses with other group members. For example, if the application group has three members, and each group member has 100 IP User Licenses, the application group has a total of 300 pooled licenses. These licenses can be removed from one group member and allocated to another; there is no need to reinstall the system software or synchronize with the AMC to complete this task.

    I suppose that I misunderstood the possibility of sharing license between the members of the application group. The core license which is 54005748 cannot be shared between the members.
    Besides that I`ve been working with MXONE for a long time and cannot get used to the fact that in a multiple nodes system there is no central node, which is the only one that must be licensed (LIM1 or server1 I mean). Thank you very much for your help once more. Now everything is clear for me.

    Oleg Pushin

    On the other hand, in genreal description it is said the following

    Shared Enterprise Systems
    MCD 5.0 introduced shared Enterprise System licencing. Enterprise licensing allows groups of MiVoice Business systems to be amalgamated into a single Application Group at the AMC. The customer chooses a single system within the group of systems to act as the Master License.
    Manager Designated License Manager (DLM) which connects to the AMC Application Group. All the underlying Group systems licensing is controlled by the DLM.

    So, one could be chosen as Master License node and in this case only DLM connects to AMC


    When you add the Enterprise License Group 54005330 to one of the applications records then you can share licenses between controllers in that cluster, Single Line, User Licenses or whatever. You’ll select the DLM Designated License Manager that will communicate to the AMC. I would also recommend looking at ULM Unified Licensing Manger in the MiCollab I&M manual. If you have a contact center and/or a MiCollab you will create a ULM being the top of the licensing food chain, then you put the MiCollab, MiCC and DLM under it giving you one place to put your licensing and manage the licensing.

Viewing 14 posts - 1 through 14 (of 14 total)
  • You must be logged in to reply to this topic.