Best practices: Installing and configuring the BlackBerry MVS

Best practices for installing BlackBerry MVS components

  • During installation, the BlackBerry MVS Server Instance Name field defaults to the hostname of the computer where you are installing the BlackBerry® MVS Server.
    • The instance name is independent of the hostname of the computer; changing the hostname has no impact on BlackBerry® Mobile Voice System.
    • You can change the instance name provided that the name is unique in the BlackBerry Domain. A name can be up to sixty-four characters long and can include alphanumeric characters, _ (underscore), - (hyphen), (, ), space, tab, line feed, and carriage return.
  • During installation, the BlackBerry MVS Data Manager Host name or IP field defaults to the IP address of the computer where you are installing the BlackBerry MVS Server. Normally, you do not change this.
  • Immediately after installation, the Windows® Services for all BlackBerry MVS components are active unless you have manually chosen to not start the services. These services are required.
  • After installation, you must add the BlackBerry MVS Server to the BlackBerry MVS configuration to make it available for service. You do this through the MVS Console.
    • When you add the BlackBerry MVS Server, to configure all components leave all of the component check boxes selected.
  • The optimum component configuration within a BlackBerry Domain is:
    • If you have only standalone BlackBerry MVS Server instances, you can remove all MVS Witness Server instances from the BlackBerry MVS configuration.
    • If you have only standalone BlackBerry MVS Server instances, you can remove all but one MVS Data Manager and one MVS Event Manager from the BlackBerry MVS configuration.
    • If you have one or more high availability pairs, you can remove all but two MVS Data Manager instances, two MVS Event Manager instances, and two MVS Witness Server instances from the BlackBerry MVS configuration.
    • To remove a component from the BlackBerry MVS configuration, clear the component check box in the Edit Server pane of the MVS Console.

      If you remove a component from the BlackBerry MVS configuration, a best practice is to disable the corresponding Windows service also.

  • One MVS BlackBerry Enterprise Server Connector can support multiple BlackBerry Enterprise Server instances when all BlackBerry Enterprise Server instances are in the same BlackBerry Domain.
  • A BlackBerry Enterprise Server can only be associated with one MVS BlackBerry Enterprise Server Connector.
  • One MVS FMC Phone can support up to 10,000 BlackBerry MVS users.
    • To support more BlackBerry MVS users, install additional BlackBerry MVS Server instances. To make the additional capacity available, you must associate each additional MVS BlackBerry Enterprise Server Connector with at least one BlackBerry Enterprise Server. This might require you to disassociate a BlackBerry Enterprise Server from an existing MVS BlackBerry Enterprise Server Connector because a BlackBerry Enterprise Server can be associated with only one MVS BlackBerry Enterprise Server Connector.
  • If you configure BlackBerry device-initiated calling, you must configure a unique DID/DDI number for each MVS FMC Phone/telephony connector combination. You must also configure your organization's call routing patterns so that the PBX can route the device-initiated calls to the MVS FMC Phone that is associated with the DID/DDI number.
  • Communication between a BlackBerry MVS Server and a BlackBerry Enterprise Server occurs through a dedicated TCP port for the connection between the MVS BlackBerry Enterprise Server Connector and the BlackBerry Dispatcher. The TCP port is configured through the MVS Console when you add the BlackBerry MVS Server.

    One MVS BlackBerry Enterprise Server Connector can be connected to one or more BlackBerry Dispatcher instances; a BlackBerry Dispatcher can be connected to only one MVS BlackBerry Enterprise Server Connector.

  • Communication between a BlackBerry MVS and a BlackBerry Configuration Database occurs through the following:
    • A dedicated TCP port for the connection between the MVS Data Manager and the BlackBerry Configuration Database. The TCP port is configured when you install the BlackBerry MVS Server.
    • An internal connection between the MVS Console and the BlackBerry Configuration Database. This connection is configured by the BlackBerry MVS installer during installation.

Best practices for configuring the BlackBerry MVS for high availability

  • To configure high availability, you use the MVS Console to associate two standalone BlackBerry MVS Server instances to form a high availability pair.
  • You do not need to configure the active-standby status of the MVS Session Manager instances and the MVS BlackBerry Enterprise Server Connector instances; the components negotiate the status themselves
  • Two MVS Data Manager instances, two MVS Witness Server instances, and two MVS Event Manager instances are required in a BlackBerry Domain to provide high availability.
  • High availability eliminates single point of failure for BlackBerry MVS components, but the BlackBerry MVS cannot provide redundancy for the network between the computers where the BlackBerry MVS Server instances are installed. To provide redundancy for the network, you must provide redundancy for the communication path between the computers. To provide complete high availability for the entire BlackBerry MVS service, also consider redundancy for the PBX, the BlackBerry Configuration Database, and the BlackBerry Enterprise Server instances in the domain. For more information, contact your organization's IT administrator.

Best practices for testing network ping time

  • The maximum time that a network ping can take to travel from the BlackBerry MVS Server to the BlackBerry Enterprise Server or BlackBerry Configuration Database and back to the BlackBerry MVS Server must be 240 milliseconds.
  • The maximum time that a network ping can take to travel from the BlackBerry MVS Server to the PBX and back to the BlackBerry MVS Server must be 240 milliseconds.

Best practices for configuring a telephony connector

A telephony connector identifies the IP address and ports that BlackBerry MVS uses to send and receive SIP messages to and from a node in your telephony infrastructure. A telephony connector definitiion also includes parameters for call setup and phone number normalization. You configure telephony connectors through the MVS Console.

  • One BlackBerry MVS can support one or more nodes.
  • Communication between a BlackBerry MVS and a node is achieved using at least one unique SIP connection between the MVS Session Manager and the node.
  • You must configure at least one telephony connector.
  • You can use multiple telephony connectors to divide your organization's users between nodes in your telephony infrasctructure. You can configure telephony connectors for nodes in the same cluster or in separate clusters.
  • When you use PBX-initiated call direction, you must configure a Caller Identification Number for each telephony connector. The PBX must use the Caller Identification Number as the calling party number when the PBX calls the BlackBerry device. The BlackBerry MVS Client compares the last six digits of the calling party number with the last six digits of the Caller Identification Number. If they match, the BlackBerry MVS Client treats the call as a BlackBerry MVS call. Ensure that any digit manipulation of the Caller Identification Number preserves the last six digits in the calling party number sent to the BlackBerry MVS Client.

Was this information helpful? Send us your comments.