BlackBerry Mobile Voice System 5.2.1 Feature and Technical Overview

BlackBerry Mobile Voice System
Version: 5.2.1
Feature and Technical Overview
Published: 2012-11-23 SWD-20121123082215916
Contents
1 2 Overview ......................................................................................................................................... 5 Features ......................................................................................................................................... 6
Features for managing user accounts and BlackBerry devices ............................................................................................. 6 Security features .............................................................................................................................................................. 10 Phone features ................................................................................................................................................................. 11
Architecture: BlackBerry MVS ....................................................................................................... 16

BlackBerry MVS high availability ....................................................................................................................................... 18 How the BlackBerry MVS determines the availability of BlackBerry MVS components ................................................. 20
BlackBerry MVS and call recording ................................................................................................ 21

Architecture: Call recording .............................................................................................................................................. 21 Restricting users to the BlackBerry MVS line ..................................................................................................................... 22
Call flows - PBX ............................................................................................................................. 23

Making a PBX-initiated call from a BlackBerry device to an internal number ...................................................................... 23 Making a BlackBerry deviceinitiated call from a BlackBerry device to an internal number ................................................ 25 Making a Voice over Wi-Fi call from a BlackBerry device to an internal number .................................................................. 26 Making a PBX-initiated call from a BlackBerry device to an external number ..................................................................... 28 Making a BlackBerry deviceinitiated call from a BlackBerry device to an external number ............................................... 30 Making a Voice over Wi-Fi call from a BlackBerry device to an external number ................................................................. 32 Receiving a PBX-initiated call on a BlackBerry device from an external number ................................................................. 33 Receiving a BlackBerry deviceinitiated call on a BlackBerry device from an external number .......................................... 35 Receiving a Voice over Wi-Fi call on a BlackBerry device ................................................................................................... 36 Holding and resuming a call on a BlackBerry device .......................................................................................................... 38 Transferring a call on a BlackBerry device using Voice over Mobile .................................................................................... 40 Transferring a call on a BlackBerry device using Voice over Wi-Fi ....................................................................................... 41 Moving a Voice over Mobile call from a BlackBerry device to a desk number ...................................................................... 43 Moving a call from a BlackBerry device using Voice over Wi-Fi to a desk number ................................................................ 44 Moving a call from a BlackBerry device to a one-time number using Voice over Mobile ....................................................... 46 Moving a call from a BlackBerry device using Voice over Wi-Fi to a one-time number ......................................................... 48 Handoff a call from Voice over Mobile to Voice over Wi-Fi .................................................................................................. 49 Handoff a call from Voice over Wi-Fi to Voice over Mobile .................................................................................................. 50 Moving a call from a desk phone to a BlackBerry device using Voice over Mobile ............................................................... 52 Moving a call from a desk phone to a BlackBerry device using Voice over Wi-Fi .................................................................. 53 Adding a BlackBerry MVS user configured for PBX-initiated calling to a Voice over Mobile call between another BlackBerry MVS user and an external user ........................................................................................................................ 55 Adding an external user to a Voice over Wi-Fi call between a BlackBerry MVS user and another external user ..................... 57
Forwarding a BlackBerry MVS call through a PBX .............................................................................................................. 58 Making a call when a user is experiencing wireless network congestion ............................................................................. 60 Using DTMF tones ............................................................................................................................................................ 61
System requirements .................................................................................................................... 63

System requirements: BlackBerry MVS ............................................................................................................................. 63 System requirements: Telephony environment .................................................................................................................. 66 System requirements: PBX ............................................................................................................................................... 68
7 8 9
Glossary ........................................................................................................................................ 70 Provide feedback .......................................................................................................................... 71 Legal notice .................................................................................................................................. 72
Overview
Overview

The BlackBerry Mobile Voice System integrates your organization's PBX environment with the BlackBerry Enterprise Server to extend desk phone features to BlackBerry devices. The BlackBerry MVS is designed to do the following: Integrate with the phone application on BlackBerry devices so that users can make calls from and receive calls to your organization's work numbers Extend commonly used PBX features that are available from users' desk phones to their BlackBerry devices Provide simplified access to your organizations voice mail system Provide Voice over Wi-Fi access to desk phone features for users of Wi-Fi enabled BlackBerry devices Extend the security features of the BlackBerry Enterprise Server to authenticate BlackBerry device users to the BlackBerry MVS and your organization's PBX environment Permit you to manage the BlackBerry MVS from a single web administration console Incorporate the use of templates and classes of service to manage users' access to their work numbers and phone features Permit you to configure the BlackBerry MVS to support high availability to help enhance the consistency and reliability of your organization's BlackBerry MVS implementation
Features
Features
Features for managing user accounts and BlackBerry devices

You can use the MVS Console to configure and manage BlackBerry Mobile Voice System user accounts. You create templates and classes of service that define the features and configuration properties that are available to BlackBerry device users. Feature User account activation Description You associate existing BlackBerry Enterprise Server user accounts with the BlackBerry MVS. When users' devices connect to the wireless network, the BlackBerry MVS performs the following actions: Associates devices with BlackBerry MVS user accounts Registers devices, on behalf of BlackBerry MVS users, to your organization's PBX environment (Devices must be registered before users can make BlackBerry MVS calls.) Controls the features of the BlackBerry MVS Client, based on the configuration properties of the BlackBerry MVS user accounts
Templates
You use templates to define the configuration properties of new BlackBerry MVS user accounts. When you assign a template to new user accounts, the BlackBerry MVS assigns the template settings to the user accounts. If necessary, you can change the settings for individual user accounts. Changes to templates affect settings for new user accounts only, not existing user accounts. You can use templates to configure the following features: The phone number that users call to access voice mail Allowed caller list and blocked caller list Schedule of when users can receive calls to the work number on their devices MWI for the devices Default network for work calls (Voice over Mobile or Voice over Wi-Fi) automatically move active calls between Voice over Mobile and Voice over Wi-Fi Sounds that play when the BlackBerry MVS is setting up an outgoing call
Features
Feature Classes of service
Description You use classes of service to permit users to configure the BlackBerry MVS Client on their devices. A class of service defines the values for all administration fields that are not specific to a BlackBerry MVS user account. A class of service can permit users to perform the following actions: Transfer calls Move calls to their desk numbers Move calls from their desk phones to their BlackBerry devices Move calls to their mobile numbers. Users can only move calls to the mobile number if the following options are set in the user's template: Default Line for outgoing calls: BlackBerry MVS Line When the BlackBerry MVS Line is unavailable, use the Mobile Line: Never Default Network for BlackBerry MVS calls: Wi-Fi When Wi-Fiis unavailable, use Mobile: No
Move calls to one-time numbers Manually move calls from Voice over Wi-Fi to Voice over Mobile (When you move a call from Voice over Wi-Fi to Voice over Mobile, the call is always a PBX-initiated call regardless of the call direction setting that is configured in the class of service.) Manually move calls from Voice over Mobile to Voice over Wi-Fi Configure a call schedule Add participants to an active call Automatically move active calls between Voice over Mobile and Voice over Wi-Fi Set the mobile numbers from a device Forward incoming BlackBerry MVS calls to an internal extension or another phone Allow the device to use the no data coverage number to make calls when the network is experiencing congestion. If you select the "Device can use the no data coverage number to make calls when the network is experiencing congestion" option, you must also type a phone number in the No Data Coverage Number field on the BlackBerry MVS Server page in the MVS Console. During times of network congestion, if an outgoing call takes too long to initiate, the BlackBerry device will use the no data coverage number to initiate the call. The no data coverage number must be unique and dedicated to the BlackBerry MVS. The no data coverage number must also be different than the number that you use for the Telephony Connector DID/DDI Number and the number that you use for the PBX Initiated Calling Caller Identification Number. This option is enabled by default, however your organization might not need to use it for several reasons: Your organization's data calls set up successfully
Features
Feature
Description You do not want to enable no data calling across the entire product suite BlackBerry device-initiated calling charges are not acceptable You do not want your organization's users to fallback to a no data call
Use only the BlackBerry MVS line for making and taking calls Change the call move to desk phone number Change the BlackBerry MVS line label Change the default line for outgoing calls Change the sound that plays when the BlackBerry MVS is setting up an outgoing call Change the phone number used to access voice mail Change caller restrictions Change the default network for BlackBerry MVS calls Select the automatic handoff method Enable and disable automatic handoff
In a class of service, you can configure the following actions: Control access to Voice over Wi-Fi calling for pushed Wi-Fi profiles and user-defined WiFi profiles on the Class of Service screen Configure the call direction for incoming calls and outgoing calls. You can specify whether calls are initiated by the PBX or by the devices. See below for more details on call direction. Turn off BlackBerry MVS Only Calling based on call direction in combination with roaming Ignore the caller identification number of the calling party in PBX-initiated calls. During normal call setup some wireless networks might alter the caller identification number. If the BlackBerry MVS Client does not recognize the number, the BlackBerry MVS Client rejects the call. To avoid this, you can permit the BlackBerry MVS Client to ignore the number. When you do this, the BlackBerry MVS Client accepts the call. Even if you have not enabled this feature, when the BlackBerry MVS Client detects that the user is roaming, and the user receives a call that has an altered caller identification number, the BlackBerry MVS Client will still accept the call. When you change a class of service, the BlackBerry MVS updates the affected user accounts and devices over the wireless network. User management If you delete or deactivate user accounts, users cannot access their work numbers or use the BlackBerry MVS Client on their devices. The BlackBerry MVS automatically sends updates to the BlackBerry Enterprise Server, which sends the updates to the users over the wireless network.
Features
Feature User licensing
Description In the MVS Console, you can view the number of BlackBerry MVS Client Access Licenses that your organization's users are using and the expiration date of the licenses. If you exceed the number of user accounts that can exist on a BlackBerry MVS, the BlackBerry MVS informs you that you require more BlackBerry MVS Client Access Licenses. You use administrative roles to permit multiple administrators to access the MVS Console. Administrative roles permit administrators to perform the following actions: Configure BlackBerry MVS Server instances, telephony connectors, voice mail connectors, templates, and classes of service Create or delete BlackBerry MVS user accounts (If you delete a BlackBerry MVS user account, the associated BlackBerry Enterprise Server user account is not deleted.) View or configure user accounts
Management of administrative roles
Call direction, Caller Identification Number, Optional ANI numbers, DID/DDI Number
Call direction determines how the setup of the media path between the PBX and the BlackBerry device is initiated for Voice over Mobile calls. Call direction can be PBX-initiated or device-initiated and can be configured for incoming and outgoing calls. For call direction, incoming and outgoing are with respect to the BlackBerry device. With PBX-initiated call direction, the PBX must send the Caller Identification Number as the calling party number when it initiates call setup. The Caller Identification Number tells the BlackBerry MVS Client that this is a BlackBerry MVS call. You configure the Caller Identification Number on the Telephony Connector page of the MVS Console. The BlackBerry MVS Client compares the last six digits of the calling party number with the last six digits of the Caller Identification Number to determine a match. During normal call setup some wireless networks might alter the caller identification number. If the BlackBerry MVS Client does not recognize the number, the BlackBerry MVS Client rejects the call. To avoid this, you can permit the BlackBerry MVS Client to ignore the number. When you do this, the BlackBerry MVS Client accepts the call. If the wireless network alters the number in the calling party number field, the optional ANI numbers allow the BlackBerry MVS Client to identify a call as a BlackBerry MVS call. Part of the BlackBerry MVS provisioning information that the BlackBerry MVS Server sends to the BlackBerry MVS Client includes the optional ANI numbers so that the BlackBerry MVS Client has a record of the numbers that can call. You configure the optional ANI numbers on the Telephony Connector page of the MVS Console. With device-initiated call direction, the BlackBerry MVS Client sends the DID/DDI Number as the called party number when it initiates call setup. The DID/DDI Number tells the PBX that this is a BlackBerry MVS call. You configure the DID/DDI Number on the MVS Server page of the MVS Console. If your organization uses devices that operate on GSM networks, PBX-initiated calling offers optimal performance and reliability for BlackBerry MVS calls. If your organization uses devices that operate on CDMA networks, device-initiated calling offers optimal performance and reliability for BlackBerry MVS calls.
Features
Feature Phone number translation
Description The Location feature provides phone number normalization. The feature translates the globally unique E.164 number starting with a plus sign (+) to a locally significant number by stripping the plus sign (+) and adding International Direct Dial (IDD) or National Direct Dial (NDD) access codes corresponding to the PSTN dial plan for the selected location. Normalization is applied to the called number of outgoing external calls that start with a plus sign. The 'called number' refers to a called number sent from the MVS Session Manager to the PBX. 'Outgoing' means from the enterprise to the external network. Use this feature when your organization's PBX does not support the plus sign or does not add the prefixes automatically.
Provisioning
Provisioning data for BlackBerry MVS users is stored in the BlackBerry Configuration Database. The BlackBerry Configuration Database sends the data to the user's devices over the wireless network when you add a user to the BlackBerry MVS, or when you enable or disable a user in the MVS Console. The data includes user settings, preferences and audio conference information. The input validation rules for the MVS Console are restrictive to help you recognize data entry errors. If you make an error when adding data, a tool tip message displays an explanation of the error.
Input validation rules
Security features
Feature Authentication of BlackBerry Mobile Voice System users Description The BlackBerry Enterprise Server is designed to authenticate BlackBerry device users to BlackBerry MVS and your organization's PBX phone system. When users connect to the wireless network, their BlackBerry devices are designed to authenticate to your organization's PBX phone system through BlackBerry MVS using encrypted data messages. Only an authenticated BlackBerry device can access the work phone number and phone features. Only authenticated BlackBerry MVS users can use their BlackBerry devices to extend the capabilities of their desk phones. Standard message encryption BlackBerry MVS is designed to use the security features of the BlackBerry Enterprise Solution. The BlackBerry Enterprise Solution uses a symmetric key encryption algorithm that is designed to protect data that is in transit between a BlackBerry device and BlackBerry MVS. For more information, see the BlackBerry Enterprise Solution Security Technical Overview. The BlackBerry MVS call logs provide information about the call activity of BlackBerry device users. They also include information about error messages,
Call and diagnostic logging
10
Features
Feature
Description warnings, information that you can use to troubleshoot issues, and other events that are related to BlackBerry MVS.
Phone features
To use the following phone features, appropriate data coverage and voice coverage are required. For example, appropriate coverage includes GPRS, EDGE, or 3G for devices that operate on GSM networks; 1XEV for devices that operate on CDMA networks; or a Wi-Fi network for Wi-Fi enabled BlackBerry devices. Feature Default phone number selection Description BlackBerry Mobile Voice System users have two phone numbers that are associated with their BlackBerry devices: a phone number that is provided by their wireless service providers and a work number that is provided by your organization. To configure which phone number to use by default, the following options are available: Default line for outgoing calls: Users can select the mobile number or the work number as the default phone line for making outgoing calls. When users click Last selected, the next outgoing call uses the most recently selected line. When the BlackBerry MVS Line is unavailable, use the Mobile line (appears when you choose BlackBerry MVS Line or Last selected): Always: Users can use the work number to make outgoing calls. If the work number is not available, outgoing calls use the mobile number. Ask: Users can use the work number to make outgoing calls if the work number is available. If the work number is not available, users can use the mobile number, if they accept a prompt to do so. Never: Users can use only the work number to make outgoing calls. This option does not appear if Last selected is configured as the default line for outgoing calls.
Default network selection
Users of Wi-Fi enabled BlackBerry devices can use Voice over Wi-Fi to access desk phone features. Users can select either Voice over Mobile or Voice over WiFi as the default network to make and receive calls. To configure the default network, the following options are available:
11
Features
Feature
Description Default network for work calls: Choose Wi-Fi or Mobile. When Wi-Fi is unavailable, use mobile (appears when Wi-Fi is selected): Yes: When a user is connected to a Wi-Fi network, the BlackBerry MVS uses Voice over Wi-Fi to make and receive work calls; however, the user can use the work number regardless of Wi-Fi network availability. When the user is outside a Wi-Fi coverage area, the BlackBerry MVS uses Voice over Mobile. No: A user must be connected to a Wi-Fi network to use the work number.
When mobile is unavailable, use Wi-Fi (appears when Mobile is selected): Yes: The BlackBerry MVS uses Voice over Mobile for work calls, even if a user is connected to a Wi-Fi network. The user can manually move calls to Voice over Wi-Fi if the user is connected to a Wi-Fi network. No: The BlackBerry MVS uses only Voice over Mobile for work calls. A user cannot use Voice over Wi-Fi for work calls.
Network handoff
You can permit BlackBerry MVS users to automatically move an active call from Voice over Wi-Fi to Voice over Mobile or from Voice over Mobile to Voice over WiFi. This action can occur only one time per call. To configure network handoff, the following options are available: Automatic handoff with user notification: A message and an audible alert notifies the user when an active call moves between Voice over Wi-Fi and Voice over Mobile. During automatic handoff with user notification, the user can cancel the handoff of a Voice over Mobile call moving to a Wi-Fi network. Automatic handoff with user prompt: A message and an audible alert asks the users if they want to move an active call between Voice over Wi-Fi and Voice over Mobile. If the user does not confirm the request, the call does not move. Automatic handoff is not available: Automatic network handoff is not available.
Scheduling
You can schedule when BlackBerry MVS users can answer calls that are made to their work numbers. You can also configure whether users can change the schedules on their BlackBerry devices. You can permit users to schedule when they receive calls for each day of the week. BlackBerry MVS users can use the phone application on their BlackBerry devices to access the desk phone features on their BlackBerry devices. BlackBerry MVS users can use desk phone features to perform the following actions:
Access to desk phone features
12
Features
Feature
Description Hold and resume calls Transfer calls Make and receive a second call (if the users are using a device that operates on a GSM network and is running BlackBerry Device Software later than version 6.0, or the users are using a BlackBerry Curve 9360 smartphone or a BlackBerry Bold 9790 smartphone) Move calls to their desk phones Move calls to one-time numbers Move work calls from Voice over Mobile to Voice over Wi-Fi Move work calls from Voice over Wi-Fi to Voice over Mobile (When you move a call from Voice over Wi-Fi to Voice over Mobile, the call is always a PBXinitiated call regardless of the call direction setting that is configured in the class of service.) Move calls from their desk phones to their BlackBerry devices Move calls from the work number to the mobile number Switch active calls Add participants to an active call Forward incoming BlackBerry MVS calls to an internal extension or another phone
Voice mail integration
You can integrate the BlackBerry MVS with your organization's voice mail system to provide BlackBerry device users with access to the voice mail messages for their work numbers. A voice mail MWI appears on BlackBerry devices when new voice mail messages are available. BlackBerry MVS users can look up names in their organization's corporate directory. You can filter incoming calls to work numbers on BlackBerry devices. When the BlackBerry MVS Server receives a BlackBerry MVS call from the PBX, before the BlackBerry MVS Server rings a BlackBerry device, it filters the incoming number through the blocked caller list and allowed caller list. If the BlackBerry MVS Server finds an incoming number in the allowed caller list, and the user did not select No Callers Allowed, the BlackBerry MVS Server rings the BlackBerry device. If the BlackBerry MVS Server finds the incoming number in the blocked caller list, the BlackBerry MVS Server does not ring the BlackBerry device. If the user does not answer the call on the desk phone, the PBX sends the call to the user's voice mail, if voice mail is configured. If the user's voice mail is not configured, the blocked caller receives a busy signal. You can select one of the following caller restriction options:
Corporate directory Caller restrictions
13
Features
Feature
Description All Callers Allowed All Callers Except Blocked Allowed Callers Only No Callers Allowed
You can permit users to allow all calls, which might include calls from blocked callers or unknown numbers. You can also permit users to change the caller restrictions on their BlackBerry devices. BlackBerry MVS Only Calling You can configure your organization's users so that they can use only the BlackBerry MVS line and not the phone number that is provided by the wireless service provider. When a BlackBerry MVS user is configured for BlackBerry MVS Only Calling, the following occurs: The BlackBerry device does not display the mobile line Incoming calls to the mobile line do not appear on the BlackBerry device Users cannot use the mobile line to make outgoing calls
A user who is configured for BlackBerry MVS Only Calling can make or take a call using the mobile line in the following scenarios: The BlackBerry MVS is unavailable The BlackBerry MVS Client is not registered with the PBX The BlackBerry Configuration Database is unavailable
When you configure your organization's users for BlackBerry MVS Only Calling, you must also configure a length of time that inbound calls are permitted on the mobile line so that emergency services personnel can contact a user who makes an emergency call. You can permit inbound calls on the mobile line from 0 to 2880 minutes. When you configure a class of service with BlackBerry MVS Only Calling, you have the option to turn off the feature based on call direction in combination with roaming. For example, you can select the option to turn off BlackBerry MVS Only Calling for incoming calls when a user is roaming. If you have configured your organization's users for BlackBerry MVS Only Calling, you must also type a phone number in the No Data Coverage Number field on the BlackBerry MVS Server page in the MVS Console. During times of network congestion, if an outgoing call takes too long to initiate, the BlackBerry device will use the no data coverage number to initiate the call. The no data coverage number must be unique and dedicated to the BlackBerry MVS. The no data coverage number must also be different than the number that you use for
14
Features
Feature
Description the Telephony Connector DID/DDI Number and the number that you use for the PBX Initiated Calling Caller Identification Number.
15
Architecture: BlackBerry MVS
The basic BlackBerry Mobile Voice System includes a standalone BlackBerry MVS Server that is integrated with one BlackBerry Enterprise Server and one PBX.
The BlackBerry MVS includes one of each of the following components: Component MVS Console Description The MVS Console is the UI that you use to maintain the BlackBerry MVS. The MVS Console uses the BlackBerry Configuration Database for information storage and retrieval. MVS Session Manager The MVS Session Manager communicates with:
16
Component
Description The MVS BlackBerry Enterprise Server Connector to send and receive BlackBerry MVS requests to and from BlackBerry devices A PBX to set up and end calls to and from devices A voice mail system to display MWIs on BlackBerry devices The MVS Witness Server to support redundancy when the MVS Session Manager is used in a high availability pair
The MVS Session Manager includes: the FMC Phone which extends desk phone features to BlackBerry devices. the MVS Event Manager which collects application events from BlackBerry devices and BlackBerry MVS components and stores them as event files on the BlackBerry MVS Server.
MVS Data Manager
The MVS Data Manager manages transactions between the BlackBerry Configuration Database and the MVS Session Manager, the MVS Witness Server, and the MVS BlackBerry Enterprise Server Connector. The MVS BlackBerry Enterprise Server Connector communicates with the BlackBerry Dispatcher for all transactions between the MVS Session Manager and BlackBerry devices. The MVS BlackBerry Enterprise Server Connector also provides a path between the MVS Data Manager and devices for transactions such as device provisioning, where the information comes directly from the BlackBerry Configuration Database. In a BlackBerry MVS high availability installation, the MVS Witness Server supports the failover of MVS Session Manager instances and MVS BlackBerry Enterprise Server Connector instances.
MVS BlackBerry Enterprise Server Connector
MVS Witness Server
The BlackBerry MVS also includes functionality that the BlackBerry Enterprise Server and the BlackBerry device provide: BlackBerry Enterprise Server The BlackBerry Enterprise Server provides BlackBerry device management and security, including authentication between BlackBerry devices and the BlackBerry MVS Server. The BlackBerry MVS uses the following BlackBerry Enterprise Server components: The BlackBerry Configuration Database which stores the configuration information for the BlackBerry MVS. The BlackBerry Dispatcher which provides compression and encryption processing for all data that BlackBerry devices send and receive. The BlackBerry Dispatcher communicates with BlackBerry devices through the BlackBerry Router. The BlackBerry Router which communicates with the BlackBerry devices.
BlackBerry MVS Client
The BlackBerry MVS Client integrates with the BlackBerry device to allow BlackBerry MVS users to extend the capabilities of their work desk phones to their BlackBerry devices.
17
BlackBerry Domain The BlackBerry MVS uses the BlackBerry Configuration Database for all data storage requirements. You can configure the BlackBerry Configuration Database when you install the BlackBerry Enterprise Server. You can configure several BlackBerry Enterprise Server instances to use the same BlackBerry Configuration Database. A BlackBerry Domain consists of one BlackBerry Configuration Database and all the BlackBerry Enterprise Server instances that use the database. One BlackBerry MVS can support several BlackBerry Enterprise Server instances and all their users if they are all in the same BlackBerry Domain. BlackBerry MVS configuration The BlackBerry MVS components communicate with each other and the BlackBerry Configuration Database to create a 'map' of all BlackBerry MVS Server instances, their components, and their associations. This map is referred to as the BlackBerry MVS configuration. A BlackBerry MVS Server and its components are added to the BlackBerry MVS configuration when you install a BlackBerry MVS Server. You can use the MVS Console to remove a BlackBerry MVS component from the BlackBerry MVS configuration. For more information on adding a BlackBerry MVS Server, see the BlackBerry MVS Installation guide. For more information on removing a BlackBerry MVS Server component, see the BlackBerry MVS Administration guide.
BlackBerry MVS high availability

The BlackBerry Mobile Voice System high availability installation is illustrated below.
18
High availability ensures that there is no single point of failure of BlackBerry MVS components. To provide high availability: 1. Install two BlackBerry MVS Server instances. 2. Configure both BlackBerry MVS Server instances (through the MVS Console). 3. Use the MVS Console to configure a high availability association of one of the BlackBerry MVS Server instances with the other. The association creates a high availability pair. High availability is achieved through active-active and active-standby models of redundancy. The following table summarizes the redundancy model for each BlackBerry MVS component: Component MVS Data Manager MVS Console MVS Witness Server MVS Event Manager Model Active-active Active-active Active-active Active-active
19
Component
Model
MVS Session Manager (except MVS Event Manager) Active-standby MVS BlackBerry Enterprise Server Connector Active-standby
In an active-standby model, you associate two BlackBerry MVS Server instances to form a high availability pair. When you associate two MVS Session Manager instances, one of the MVS Session Manager instances becomes active and the other standby, and one of the MVS BlackBerry Enterprise Server Connector instances becomes active and the other standby. The components themselves determine which one becomes active and which one standby. If the active component fails, the components and the MVS Witness Server manage the failover from the active component to the standby component. In an active-active model, both components are always active. If a component fails, the BlackBerry MVS automatically stops using that component. For example, because the MVS Data Manager instances use an active-active model, two MVS Data Manager instances provide redundancy for the high availability pair. By comparison, there must be one active and one standby MVS Session Manager for every high availability pair.
How the BlackBerry MVS determines the availability of BlackBerry MVS components
Active components report their status to an MVS Event Manager every ten seconds. An active component is considered unavailable if it reports that it is unable to provide service for 60 seconds, or if it fails to report its status for 60 seconds. Only two MVS Event Manager instances are required to support the high availability pair because the MVS Event Manager instances use an active-active redundancy model. The status of all components in the BlackBerry Domain is shown on the MVS Console Dashboard. In a high availability environment, the MVS Witness Server instances monitor the status of all MVS Session Manager instances and all MVS BlackBerry Enterprise Server Connector instances in the BlackBerry Domain. If an active MVS Session Manager or MVS BlackBerry Enterprise Server Connector component becomes unavailable, an MVS Witness Server facilitates the failover of service to the standby component. During failover, active calls are not affected but BlackBerry Mobile Voice System users cannot use the features that are typically available to them during a call. The users also cannot send or receive a second call. In addition to this automatic process, you can manually start a failover through the MVS Console. Only two MVS Witness Server instances are required to support the high availability pair because the MVS Witness Server instances use an active-active redundancy model. The MVS Witness Server instances themselves determine which one handles a particular failover.
20
BlackBerry MVS and call recording
The BlackBerry Mobile Voice System does not record calls. However, you can use a third-party call recording solution to record BlackBerry MVS calls. The BlackBerry MVS was tested using a passive mode of recording, where the recording solution monitors specific network connections to capture the necessary call signaling messages and related media.
Architecture: Call recording

If you connect the BlackBerry Mobile Voice System directly to the PBX using SIP, you must configure an external hardwarebased MTP. The recording solution monitors (or spans) the switch ports that are connected to the BlackBerry MVS Server and the external MTP resource. This spanning mechanism copies all messages and media that is destined for or originates from the BlackBerry MVS Server and the external MTP resource to the recording solution. The recording solution then captures, tags and archives the messages and media appropriately.
21
Restricting users to the BlackBerry MVS line

You can configure the organization's users to use only the BlackBerry Mobile Voice System line and not the phone number that is provided by the wireless service provider. In the MVS Console, you must configure a class of service for the users that you will record calls for. In the class of service, you must select the Restrict calls to use only the BlackBerry MVS line check box, and clear the User can transfer a call check box and the User can move a call to a one time number check box. There are also parameters set through a BlackBerry Enterprise Server IT policy that can block all incoming non-BlackBerry MVS calls from reaching the user's mobile line. For more information about restricting calls to the BlackBerry MVS line, refer to the following KB article: http://www.blackberry.com/btsc/KB26757. A user who is configured for BlackBerry MVS Only calling can make or take a call using the mobile line in the following scenarios: The BlackBerry MVS is unavailable The BlackBerry MVS Client is not registered with the PBX The BlackBerry Configuration Database is unavailable
22
Call flows - PBX
Call flows - PBX

Making a PBX-initiated call from a BlackBerry device to an internal number
1. A caller within an organization uses a BlackBerry device to dial the extension number of another BlackBerry Mobile Voice System user.
23
Call flows - PBX
2. The BlackBerry MVS Client creates a call establishment request, which includes the destination number. The BlackBerry MVS Client compresses and encrypts the call establishment request, and sends it to the BlackBerry Enterprise Server over the wireless network. 3. The BlackBerry Enterprise Server decrypts and decompresses the call establishment request, and sends it to the MVS BlackBerry Enterprise Server Connector. 4. The MVS BlackBerry Enterprise Server Connector sends the request to the MVS Session Manager. 5. The MVS Session Manager sends a confirmation response to the BlackBerry device and, using a SIP trunk, requests that the PBX establish a call to the device using the mobile number. 6. The PBX sends the call to the device over the PSTN and the wireless network using the caller ID number of the telephony connector as the ANI. 7. The BlackBerry MVS Client receives the call. If the ANI in the incoming call matches the ANI that are specified in the Telephony Connector Caller Identification Number field or the Telephony Connector Optional ANI numbers available for identifying BlackBerry MVS calls fields of the MVS Console, or if no ANI exists, the BlackBerry MVS Client accepts the call. The BlackBerry MVS Client sends a verification code to the MVS Session Manager using DTMF tones. 8. If no ANI value exists, the MVS Session Manager sends a verification code response to the device using DTMF tones. The MVS Session Manager, using a SIP line, requests that the PBX establish a call to the internal number using the extension number. 9. The PBX determines that the extension number is internal to the organization and rings the extension number over the organization's LAN. 10. The recipient answers the call at a desk phone. 11. The MVS Session Manager uses DTMF tones to indicate that the call is connected to the device, and connects the SIP line call leg to the SIP trunk call leg. Voice communication occurs.
24
Call flows - PBX
Making a BlackBerry deviceinitiated call from a BlackBerry device to an internal number
1. A caller within an organization uses a BlackBerry device to dial the extension number of another BlackBerry Mobile Voice System user. 2. The BlackBerry MVS Client creates a call establishment request, which includes the destination number. The BlackBerry MVS Client compresses and encrypts the call establishment request, and sends it to the BlackBerry Enterprise Server over the wireless data network.
25
Call flows - PBX
3. The BlackBerry Enterprise Server decrypts and decompresses the call establishment request, and sends it to the MVS BlackBerry Enterprise Server Connector. 4. The MVS BlackBerry Enterprise Server Connector sends the request to the MVS Session Manager. 5. The MVS Session Manager sends a confirmation request to the device. The confirmation request includes the DID/DDI number that the BlackBerry MVS Client uses to communicate with the MVS Session Manager. 6. The BlackBerry MVS Client uses the wireless voice network to make a call to the PBX using the DID/DDI number. 7. The PBX routes the call to the MVS Session Manager over the SIP trunk using the DID/DDI number. 8. The MVS Session Manager answers the call to the DID/DDI number. 9. The MVS Session Manager and the BlackBerry MVS Client use a two-way protocol to authenticate the call. 10. The MVS Session Manager verifies the call and requests that the PBX make a call to the extension number using the SIP line. 11. The PBX determines that the extension number is internal to the organization and rings the extension number over the organization's LAN. 12. The recipient answers the call at a desk phone. 13. The MVS Session Manager uses DTMF tones to indicate to the device that the call is connected to the extension number. The MVS Session Manager connects the SIP line call leg to the SIP trunk call leg, and voice communication occurs.
Making a Voice over Wi-Fi call from a BlackBerry device to an internal number
26
Call flows - PBX
1. A BlackBerry Mobile Voice System user connects to an organization's Wi-Fi network and authenticates with the BlackBerry MVS. The BlackBerry MVS user makes a call from a BlackBerry device to an extension number within the organization. 2. The BlackBerry MVS Client creates a call establishment request, which includes the destination number. The device compresses and encrypts the call establishment request, and sends it to the BlackBerry Enterprise Server over the WiFi network. 3. The BlackBerry Enterprise Server decrypts and decompresses the call establishment request, and sends it to the MVS BlackBerry Enterprise Server Connector over a TCP connection. 4. The MVS BlackBerry Enterprise Server Connector sends the request to the MVS Session Manager. 5. The MVS Session Manager sends the request using SIP to the PBX over a UDP port. 6. The PBX determines that the extension number is internal to the organization and rings the extension number over the organization's LAN. 7. The recipient answers the call at a desk phone and voice communication occurs over an RTP connection that the PBX opens between the two endpoints.
27
Call flows - PBX
Making a PBX-initiated call from a BlackBerry device to an external number
1. A BlackBerry Mobile Voice System user makes a call from a BlackBerry device to a number that is external to the organization. 2. The BlackBerry MVS Client creates a call establishment request, which includes the destination number. The BlackBerry MVS Client compresses and encrypts the call establishment request, and sends it to the BlackBerry Enterprise Server over the wireless network. 3. The BlackBerry Enterprise Server decrypts and decompresses the call establishment request, and sends it to the MVS BlackBerry Enterprise Server Connector.
28
Call flows - PBX
4. The MVS BlackBerry Enterprise Server Connector sends the request to the MVS Session Manager. 5. The MVS Session Manager sends a confirmation response to the device and, using a SIP trunk, requests that the PBX establish a call to the BlackBerry device using the mobile number. 6. The PBX sends the call establishment request to the device over the PSTN and wireless network. 7. The BlackBerry MVS Client receives a call. If the ANI in the incoming call matches the ANI that are specified in the Telephony Connector Caller Identification Number field or the Telephony Connector Optional ANI numbers available for identifying BlackBerry MVS calls fields of the MVS Console, or if no ANI exists, the BlackBerry MVS Client accepts the call. The BlackBerry MVS Client sends a verification code request to the MVS Session Manager using DTMF tones. 8. If no ANI value in the incoming call, the MVS Session Manager sends a verification code response to the device using DTMF tones and, using a SIP line, requests that the PBX establish a call to the external number. 9. The PBX determines that the extension number is external to the organization and rings the number over the PSTN. 10. The recipient answers the call at an external phone. 11. The MVS Session Manager uses DTMF tones to indicate that the call is connected to the device. The MVS Session Manager connects the SIP line call leg to the SIP trunk call leg. Voice communication occurs.
29
Call flows - PBX
Making a BlackBerry deviceinitiated call from a BlackBerry device to an external number
1. A BlackBerry Mobile Voice System user makes a call from a BlackBerry device to a phone number that is external to the organization. 2. The BlackBerry MVS Client creates a call establishment request, which includes the external number. The BlackBerry MVS Client compresses and encrypts the call establishment request, and sends it to the BlackBerry Enterprise Server over the wireless data network.
30
Call flows - PBX
3. The BlackBerry Enterprise Server decrypts and decompresses the call establishment request, and sends it to the MVS BlackBerry Enterprise Server Connector. 4. The MVS BlackBerry Enterprise Server Connector sends the request to the MVS Session Manager. 5. The MVS Session Manager sends a confirmation request to the device. The confirmation request includes the DID/DDI number that the BlackBerry MVS Client uses to communicate with the MVS Session Manager. 6. The BlackBerry MVS Client uses the wireless voice network to make a call to the PBX. 7. The PBX routes the call to the MVS Session Manager over the SIP trunk using the DID/DDI number. 8. The MVS Session Manager answers the incoming call. The MVS Session Manager sends a message to the BlackBerry MVS Client to indicate that it answered the call. 9. The MVS Session Manager and the BlackBerry MVS Client use a two-way protocol to authenticate the call. 10. The MVS Session Manager verifies the call and requests that the PBX make a call to the external number over the PSTN using the SIP line. 11. The PBX determines that the number is external to the organization and rings the external number over the PSTN. 12. The recipient answers the call at an external phone. 13. The MVS Session Manager uses DTMF tones to indicate to the device that the call is connected to the external number. The MVS Session Manager connects the SIP line call leg to the SIP trunk call leg, and voice communication occurs.
31
Call flows - PBX
Making a Voice over Wi-Fi call from a BlackBerry device to an external number
1. A BlackBerry Mobile Voice System user connects to an organization's Wi-Fi network and authenticates with the BlackBerry MVS. The BlackBerry MVS user makes a call from a BlackBerry device to a number that is external to the organization. 2. The device creates a call establishment request, which includes the destination number. The device then compresses and encrypts the call establishment request, and sends it to the BlackBerry Enterprise Server over the Wi-Fi network. 3. The BlackBerry Enterprise Server decrypts and decompresses the call establishment request, and sends it to the MVS BlackBerry Enterprise Server Connector over a TCP connection. 4. The MVS BlackBerry Enterprise Server Connector sends the request to the MVS Session Manager. 5. The MVS Session Manager sends the request using SIP to the PBX over a UDP port. 6. The PBX determines that the phone number is external to the organization and rings the phone number over the PSTN.
32
Call flows - PBX
7. The recipient answers the call at the external phone and voice communication occurs over an RTP connection that the PBX opens between two endpoints.
Receiving a PBX-initiated call on a BlackBerry device from an external number
1. A caller who is external to an organization dials the work number of a BlackBerry Mobile Voice System user. 2. The PBX creates a call establishment request and sends it to the MVS Session Manager over the SIP line. 3. The MVS Session Manager filters the request through the receiving BlackBerry MVS user's unknown caller ID setting, call scheduling setting, allowed caller list, and blocked caller list. If the call is permitted, the MVS Session Manager sends the request to the BlackBerry Enterprise Server.
33
Call flows - PBX
4. The BlackBerry Enterprise Server compresses and encrypts the incoming call request, and sends it to the wireless network. The incoming call request contains the caller ID information and phone number of the caller. 5. One of the following occurs: If the BlackBerry device receives the incoming call request, the device decrypts and decompresses it. The device then encrypts and compresses a call establishment response, and sends it to the BlackBerry Enterprise Server. The BlackBerry Enterprise Server decrypts and decompresses the call establishment response, and sends it to the MVS BlackBerry Enterprise Server Connector. If the device does not receive the incoming call request, the MVS BlackBerry Enterprise Server Connector stops responding while it waits for the call establishment response.
6. The MVS BlackBerry Enterprise Server Connector sends the request to the MVS Session Manager. 7. The MVS Session Manager, using the SIP trunk, requests that the PBX establish a call to the device using the mobile number. 8. The PBX sends the call request to the device over the PSTN and wireless network. 9. The BlackBerry device receives the call. One of the following occurs: If the device receives the call establishment request, the caller ID information from the call establishment request appears on the device. If the ANI matches the ANI in the Telephony Connector Caller Identification Number field of the MVS Console, the call appears on the BlackBerry device as a BlackBerry MVS call. If the ANI matches an ANI in the Telephony Connector Optional ANI numbers available for identifying BlackBerry MVS calls fields of the MVS Console, the call appears on the BlackBerry device as a BlackBerry MVS call. If the device does not receive the call establishment request, the call appears on the device as a call from an unknown number.
10. The device rings and the BlackBerry MVS user accepts the call. 11. The BlackBerry MVS Client sends a verification code request to the MVS Session Manager using DTMF tones. 12. If no ANI value exists in the incoming call, the MVS Session Manager sends a verification code response to the device using DTMF tones. One of the following occurs: If the device receives the call establishment request, the caller ID information from the call establishment request appears on the device. If the device does not receive the call establishment request, the call appears on the device as a call from an unknown number.
13. If no ANI value exists in the incoming call, and the BlackBerry MVS Client receives the verification code response from the MVS Session Manager, the BlackBerry MVS Client switches the call so that it appears as a BlackBerry MVS call. 14. The MVS Session Manager connects the SIP line call leg to the SIP trunk call leg, and voice communication occurs.
34
Call flows - PBX
Receiving a BlackBerry deviceinitiated call on a BlackBerry device from an external number
1. A caller who is external to an organization dials the work number of a BlackBerry Mobile Voice System user. 2. The PBX creates a call establishment request and sends it to the MVS Session Manager over the SIP line. 3. The MVS Session Manager filters the request through the recipients unknown caller ID setting, call scheduling setting, allowed caller list, and blocked caller list. If the call is permitted, the MVS Session Manager sends the call establishment request to the BlackBerry Enterprise Server.
35
Call flows - PBX
4. The BlackBerry Enterprise Server compresses and encrypts the incoming call request and sends it to the wireless data network. The call establishment request includes the caller ID information and phone number of the caller, and the DID/DDI number that the BlackBerry MVS Client uses to communicate with the MVS Session Manager. 5. The BlackBerry device decrypts and decompresses the incoming call request, compresses and encrypts a call establishment response, and sends the call establishment response to the BlackBerry Enterprise Server. 6. The BlackBerry Enterprise Server decrypts and decompresses the call establishment response, and sends it to the MVS BlackBerry Enterprise Server Connector. 7. The MVS BlackBerry Enterprise Server Connector sends the request to the MVS Session Manager. 8. The BlackBerry MVS Client uses the wireless voice network to make a call to the PBX. 9. The PBX routes the call to the MVS Session Manager over the SIP trunk using the DID/DDI number. 10. The MVS Session Manager answers the call and sends a message to the BlackBerry MVS Client to indicate that it answered the call. 11. The MVS Session Manager and the BlackBerry MVS Client use a two-way protocol to authenticate the call. 12. The MVS Session Manager verifies that the call is a BlackBerry MVS call. 13. The device rings and the BlackBerry MVS user accepts the call. 14. The BlackBerry MVS Client sends a connection request using the SIP trunk through the PBX to the MVS Session Manager using DTMF tones. 15. The MVS Session Manager connects the SIP line call leg to the SIP trunk call leg, and voice communication occurs.
Receiving a Voice over Wi-Fi call on a BlackBerry device
36
Call flows - PBX
1. A BlackBerry Mobile Voice System user connects to an organization's Wi-Fi network and authenticates with the BlackBerry MVS. 2. Using a desk phone, another user within the organization dials the extension number of the BlackBerry MVS user. 3. The PBX creates a call establishment request and sends it to the MVS Session Manager over a UDP port using a SIP. 4. The MVS Session Manager filters the request through the recipient's allowed caller list, blocked caller list, and call scheduling setting, and sends the request to the BlackBerry Enterprise Server. 5. The BlackBerry Enterprise Server compresses and encrypts the call establishment request, and sends it to the BlackBerry device over the Wi-Fi network. 6. The device decrypts and decompresses the request, and accepts the call. 7. The BlackBerry MVS user answers the call and voice communication occurs over an RTP connection that the PBX opens between the two endpoints.
37
Call flows - PBX
Holding and resuming a call on a BlackBerry device
1. A BlackBerry Mobile Voice System user is on a call that uses the SIP line call leg. On the BlackBerry device, the user presses the Menu key and clicks Hold. 2. The BlackBerry MVS Client creates a hold request. One of the following events occurs: If the user is in a wireless coverage area where data services are not available, the BlackBerry MVS Client uses DTMF tones to send the hold request to the PBX over the wireless network. The PBX converts the DTMF tones to KPML and sends the KPML to the MVS Session Manager. If the user is in a wireless coverage area where data services are available, the BlackBerry MVS Client compresses and encrypts the hold request, and sends it to the wireless network. The BlackBerry Enterprise Server decrypts and
38
Call flows - PBX
decompresses the hold request, and sends it to the MVS BlackBerry Enterprise Server Connector. The MVS BlackBerry Enterprise Server Connector sends the request to the MVS Session Manager. 3. The MVS Session Manager places the SIP line call leg into a hold state through the PBX. The hold state includes music on hold if your organization's telephony infrastructure is configured for music on hold. If the BlackBerry MVS user makes another call, the MVS Session Manager reuses the SIP line leg to make the call. 4. On the BlackBerry device, the BlackBerry MVS user presses the Menu key and clicks Resume. 5. The BlackBerry MVS Client creates a resume request. One of the following events occurs: If the user is in a wireless coverage area where data services are not available, the BlackBerry MVS Client uses DTMF tones to send the resume request to the PBX over the wireless network. The PBX converts the DTMF tones to KPML and sends the KPML to the MVS Session Manager. The MVS Session Manager, through the PBX, removes the hold state from the SIP line call leg, and the call can continue. If the user is in a wireless coverage area where data services are available, the BlackBerry MVS Client compresses and encrypts the hold request, and sends it to the BlackBerry Enterprise Server over the wireless network. The BlackBerry Enterprise Server decrypts and decompresses the resume request, and sends it to the MVS BlackBerry Enterprise Server Connector. The MVS BlackBerry Enterprise Server Connector sends the request to the MVS Session Manager. The MVS Session Manager, through the PBX, removes the hold state from the SIP line call leg, and the call can continue.
39
Call flows - PBX
Transferring a call on a BlackBerry device using Voice over Mobile
1. A BlackBerry Mobile Voice System user is on a BlackBerry device call with Party A using Voice over Mobile. To transfer the call, the BlackBerry MVS user presses the Menu key, clicks Transfer, and clicks the phone number of Party B. When the transfer process starts, the BlackBerry MVS puts Party A on hold. 2. The BlackBerry MVS Client creates a transfer request, which includes the destination number. One of the following events occurs: If the user is in a wireless coverage area where data services are not available, the BlackBerry MVS Client uses DTMF tones to create the transfer request and sends it to the MVS Session Manager. If the user is in a wireless coverage area where data services are available, the BlackBerry MVS Client compresses and encrypts the transfer request, and sends it to the BlackBerry Enterprise Server over the wireless network. The
40
Call flows - PBX
BlackBerry Enterprise Server decrypts and decompresses the hold request, and sends it to the MVS BlackBerry Enterprise Server Connector. The MVS BlackBerry Enterprise Server Connector sends the request to the MVS Session Manager. 3. The MVS Session Manager sends the transfer request to the PBX to create a new call on the SIP line to Party B. 4. When Party B answers, the MVS Session Manager connects the SIP trunk call leg and SIP line call leg. The BlackBerry MVS user and Party B can communicate. 5. The BlackBerry MVS Client creates a complete transfer request. One of the following events occurs: If the user is in a wireless coverage area where data services are not available, the BlackBerry MVS Client uses DTMF tones to create the complete transfer request and send it to the MVS Session Manager. If the user is in a wireless coverage area where data services are available, the BlackBerry MVS Client compresses and encrypts the complete transfer request, and sends it to the BlackBerry Enterprise Server over the wireless network. The BlackBerry Enterprise Server decrypts and decompresses the complete transfer request, and sends it to the MVS BlackBerry Enterprise Server Connector. The MVS BlackBerry Enterprise Server Connector sends the request to the MVS Session Manager.
6. The MVS Session Manager instructs the PBX to connect Party A to Party B and end the call with the BlackBerry MVS user's extension number. Party A can now speak with Party B. 7. The MVS Session Manager releases the SIP trunk call leg to the mobile number of the BlackBerry MVS user.
Transferring a call on a BlackBerry device using Voice over Wi-Fi
41
Call flows - PBX
1. A BlackBerry Mobile Voice System user connects to an organization's Wi-Fi network and authenticates with the BlackBerry MVS. During an active call with Party A, the user wants to transfer the call to Party B. The user presses the Menu key, clicks Transfer, and dials the extension number of Party B. The user places Party A on hold. 2. The BlackBerry device starts a call establishment request, which includes the destination extension number of Party B. The device compresses, encrypts, and sends the request to the BlackBerry Enterprise Server over the Wi-Fi network. 3. The BlackBerry Enterprise Server decrypts, decompresses, and sends the request to the MVS BlackBerry Enterprise Server Connector over a TCP connection. 4. The MVS BlackBerry Enterprise Server Connector sends the request to the MVS Session Manager. 5. The MVS Session Manager sends the request using SIP to the PBX over a UDP port. 6. The PBX determines that the extension number is an internal number and rings the extension number over the organization's LAN. 7. Party B answers the call, speaks to the BlackBerry MVS user over an RTP connection that the PBX opens, and agrees to accept the transferred call from the BlackBerry MVS user.
42
Call flows - PBX
8. The BlackBerry MVS user selects the complete transfer option on the device to complete the transfer.
Moving a Voice over Mobile call from a BlackBerry device to a desk number
1. During a Voice over Mobile call on a BlackBerry device, a BlackBerry Mobile Voice System user presses the Menu key, clicks Move Call, and clicks Desk. 2. The BlackBerry MVS Client creates a call move request. One of the following events occurs: If the user is in a wireless coverage area where data services are not available, the BlackBerry MVS Client uses DTMF tones to create the request, and sends the request to the MVS Session Manager over the wireless network.
43
Call flows - PBX
If the user is in a wireless coverage area where data services are available, the BlackBerry MVS Client compresses and encrypts the request, and sends it to the BlackBerry Enterprise Server over the wireless network. The BlackBerry Enterprise Server decrypts and decompresses the request, and sends it to the MVS BlackBerry Enterprise Server Connector MVS Session Manager. The MVS BlackBerry Enterprise Server Connector sends the request to the MVS Session Manager.
3. The MVS Session Manager sends the request to the PBX to establish a call to the extension number for the BlackBerry MVS user's desk phone over the SIP line. 4. The PBX determines that the phone number is an internal number and rings the extension number over the organization's LAN. 5. The user answers the call at the desk phone. 6. The PBX verifies through SIP messaging with the MVS Session Manager that the call was answered. 7. The MVS Session Manager ends the SIP trunk call leg with the device. The call ends on the device, and the user continues the call at the desk phone.
Moving a call from a BlackBerry device using Voice over Wi-Fi to a desk number
44
Call flows - PBX
1. A BlackBerry Mobile Voice System user connects to a Wi-Fi network and authenticates with the BlackBerry MVS. On the BlackBerry device, the user presses the Menu key, clicks Move Call, and clicks Desk. 2. The device starts a call move request. The device compresses, encrypts, and sends the request to the BlackBerry Enterprise Server over the Wi-Fi network. 3. The BlackBerry Enterprise Server decrypts, decompresses, and sends the request to the MVS BlackBerry Enterprise Server Connector over a TCP connection. 4. The MVS BlackBerry Enterprise Server Connector sends the request to the MVS Session Manager. 5. The MVS Session Manager sends the request using SIP to the PBX over a UDP port. 6. The PBX determines that the desk number is an internal number and rings the desk number over the LAN. 7. The recipient answers the call at the desk phone and voice communication occurs over an RTP connection that the PBX opens between the two endpoints.
45
Call flows - PBX
Moving a call from a BlackBerry device to a one-time number using Voice over Mobile
1. During a Voice over Mobile call on a BlackBerry device, a BlackBerry Mobile Voice System user presses the Menu key, clicks Move Call, and clicks One-Time Number. On the Options screen, the user clicks or types a one-time number to move the call to. 2. The BlackBerry MVS Client creates a call move request, which includes the one-time number to move the call to. One of the following events occurs: If the user is in a wireless coverage area where data services are not available, the BlackBerry MVS Client uses DTMF tones to create the request, and sends it to the MVS Session Manager over the wireless network.
46
Call flows - PBX
If the user is in a wireless coverage area where data services are available, the BlackBerry MVS Client compresses and encrypts the request, and sends it to the BlackBerry Enterprise Server over the wireless network. The BlackBerry Enterprise Server decrypts and decompresses the request, and sends it to the MVS BlackBerry Enterprise Server Connector. The MVS BlackBerry Enterprise Server Connector sends the request to the MVS Session Manager.
3. The MVS Session Manager sends the request to the PBX to establish a call to the one-time number over the SIP line. 4. The PBX determines that the one-time number is external to the organization and rings the one-time number over the PSTN. 5. The user answers the call at the external phone. 6. The PBX verifies through SIP messaging with the MVS Session Manager that the call was answered. 7. The MVS Session Manager ends the SIP trunk call leg with the BlackBerry device, and ends the call on the BlackBerry device. The user continues the call on the one-time number.
47
Call flows - PBX
Moving a call from a BlackBerry device using Voice over Wi-Fi to a one-time number
1. A BlackBerry Mobile Voice System user connects to a Wi-Fi network and authenticates with the BlackBerry MVS. On the BlackBerry device, the user presses the Menu key, clicks Move Call, and clicks One-Time Number. On the Options screen, the user clicks or types a phone number to move the call to. 2. The device starts a call move request. The device compresses, encrypts, and sends the request to the BlackBerry Enterprise Server over the Wi-Fi network. 3. The BlackBerry Enterprise Server decrypts, decompresses, and sends the request to the MVS BlackBerry Enterprise Server Connector over a TCP connection. 4. The MVS BlackBerry Enterprise Server Connector sends the request to the MVS Session Manager. 5. The MVS Session Manager sends the request using SIP to the PBX over a UDP port. 6. The PBX determines that the one-time number is an external number and rings the one-time number over the PSTN.
48
Call flows - PBX
7. The recipient answers the call at the external phone and voice communication occurs over an RTP connection that is open between the device and PBX.
Handoff a call from Voice over Mobile to Voice over Wi-Fi
1. A BlackBerry Mobile Voice System user has a BlackBerry device that is configured to use Wi-Fi as the default network and to use the mobile network when the Wi-Fi network is unavailable. 2. In an area with no Wi-Fi coverage, the user makes a Voice over Mobile call on a BlackBerry device. 3. The user moves into an area with Wi-Fi coverage. One of the following actions occurs:
49
Call flows - PBX
If the template setting for Network handoff is set to Automatic handoff with user notification, the BlackBerry device automatically sends the request to move the Voice over Mobile call to the Wi-Fi network. The user can cancel this action. If the template setting for Network handoff is set to Automatic handoff with user prompt, the BlackBerry device prompts the user to confirm the request to move the Voice over Mobile call to the Wi-Fi network. If the user confirms the request, the device moves the Voice over Mobile call to the Wi-Fi network.
4. The device starts a call move request. The device compresses and encrypts the request, and sends it to the BlackBerry Enterprise Server over the Wi-Fi network. 5. The BlackBerry Enterprise Server decrypts and decompresses the request and sends it to the MVS BlackBerry Enterprise Server Connector. 6. The MVS BlackBerry Enterprise Server Connector sends the request to the MVS Session Manager. 7. The MVS Session Manager establishes a Wi-Fi call with the device. 8. The device answers the Wi-Fi call on behalf of the user. 9. The MVS Session Manager instructs the PBX to change the RTP connection from the mobile network to the Wi-Fi network. 10. The PBX switches the mobile call with the Wi-Fi call. 11. The MVS Session Manager disconnects the mobile call, and notifies the device that the mobile call was moved. The user receives a notification that the Voice over Mobile call was moved to the Wi-Fi network. 12. The user continues the call on the device.
Handoff a call from Voice over Wi-Fi to Voice over Mobile
50
Call flows - PBX
1. A BlackBerry Mobile Voice System user has a BlackBerry device that is configured to use the Wi-Fi as the default network and to use the mobile network when the Wi-Fi network is unavailable. 2. During a call on a BlackBerry device using Voice over Wi-Fi, the user starts to move out of an area with Wi-Fi coverage. One of the following actions occurs: If the template setting for Network handoff is set to Automatic handoff with user notification, the BlackBerry device automatically sends the request to move the Wi-Fi call to the Voice over Mobile network. If the template setting for Network handoff is set to Automatic handoff with user prompt, the BlackBerry device prompts the user to confirm the request to move the Wi-Fi call to the Voice over Mobile network. If the user confirms the request, the device moves the Wi-Fi call to the Voice over Mobile network.
3. The device starts a call move request. The device compresses and encrypts the request, and sends it to the BlackBerry Enterprise Server over the Wi-Fi network. 4. The BlackBerry Enterprise Server decrypts and decompresses the request and sends it to the MVS BlackBerry Enterprise Server Connector. 5. The MVS BlackBerry Enterprise Server Connector sends the request to the MVS Session Manager. 6. The MVS Session Manager sends the request using SIP to the PBX over a UDP port.
51
Call flows - PBX
7. The PBX determines that the phone number is an external number and rings the mobile phone number over the PSTN. 8. The device answers the Voice over Mobile call on behalf of the user. 9. The MVS Session Manager instructs the PBX to change the RTP connection from the Wi-Fi network to the mobile network. 10. The PBX switches the Wi-Fi call with the mobile call. 11. The MVS Session Manager disconnects the Wi-Fi call, and notifies the device that the Wi-Fi call was moved. The user receives a notification that the Wi-Fi call was moved. 12. The user continues the call on the device.
Moving a call from a desk phone to a BlackBerry device using Voice over Mobile
52
Call flows - PBX
1. A BlackBerry Mobile Voice System user makes or answers a call on the desk phone. The PBX establishes a connection between the two endpoints and voice communication occurs. 2. On the BlackBerry device, the user presses the Send key and then presses the Menu key. If data services are available, the Move Call From Desk menu item appears. The user clicks Move Call From Desk. The user is prompted to place the desk phone on hold. 3. On the desk phone, the user places the call on hold. 4. The device compresses and encrypts the request, and sends it to the BlackBerry Enterprise Server. 5. The BlackBerry Enterprise Server decrypts and decompresses the request and sends it to the MVS BlackBerry Enterprise Server Connector. 6. The MVS BlackBerry Enterprise Server Connector sends the request to the MVS Session Manager. 7. The call leg is established using one of the following methods: The BlackBerry MVS Client uses the wireless voice network to make a call to the PBX. The PBX routes the call to the BlackBerry MVS Session Manager over the SIP trunk using the DID/DDI number. The PBX sends the call to the BlackBerry device using the Caller Identification Number of the Telephony Connector. The BlackBerry MVS Client receives a call. The BlackBerry MVS Client sends a verification code request to the MVS Session Manager using DTMF tones. If the ANI in the incoming call is empty, the MVS Session Manager sends a verification code response to the BlackBerry device using DTMF tones.
8. The MVS Session Manager, using the SIP line, requests that the PBX move the call to the BlackBerry MVS line. 9. The call continues on the BlackBerry device.
Moving a call from a desk phone to a BlackBerry device using Voice over Wi-Fi
53
Call flows - PBX
1. A BlackBerry Mobile Voice System user makes or answers a call on the desk phone. The PBX establishes the connection between the two endpoints and voice communication occurs. 2. On the BlackBerry device, the user presses the Send key and then presses the Menu key. The user clicks Move Call From Desk. The user is prompted to place the desk phone on hold. 3. On the desk phone, the user places the call on hold. 4. The device compresses and encrypts the request, and sends it to the BlackBerry Enterprise Server. 5. The BlackBerry Enterprise Server decrypts and decompresses the request and sends it to the MVS BlackBerry Enterprise Server Connector. 6. The MVS BlackBerry Enterprise Server Connector sends the request to the MVS Session Manager. 7. The device establishes the call leg over the Wi-Fi network to the PBX. 8. The MVS Session Manager, using the SIP line, requests that the PBX move the call to the BlackBerry MVS line. 9. The call continues on the device.
54
Call flows - PBX
Adding a BlackBerry MVS user configured for PBX-initiated calling to a Voice over Mobile call between another BlackBerry MVS user and an external user
1. A BlackBerry Mobile Voice System user, Party A, is on a Voice over Mobile call with an external user, Party B. 2. Party A presses the Menu key on the BlackBerry device, clicks Add Participant, and dials the number of another BlackBerry MVS user, Party C.
55
Call flows - PBX
3. The BlackBerry MVS Client creates a hold request. The MVS Session Manager places the SIP line call leg into a hold state through the PBX. 4. The MVS Session Manager uses the SIP line interface to request that the PBX establish another call leg to the number of Party C. 5. The PBX determines that the number is internal to the organization and sends a new call request to the MVS Session Manager. 6. The MVS Session Manager determines the call is PBX-initiated and uses the SIP trunk interface to request that the PBX ring the number of Party C. 7. The MVS Session Manager connects the two call legs. 8. When Party C answers the call, Party A presses the Menu key and clicks Join Conference. 9. The BlackBerry MVS Client sends a join request to the MVS Session Manager. 10. The MVS Session Manager requests that the PBX join Party A, Party B, and Party C to the conference call. 11. The MVS Session Manager, through the PBX, ends the hold state from the SIP line call leg. 12. Voice communication occurs among Party A, Party B, and Party C.
56
Call flows - PBX
Adding an external user to a Voice over WiFi call between a BlackBerry MVS user and another external user
1. Using Voice over Wi-Fi, a BlackBerry Mobile Voice System user, Party A, is on a call with an external user, Party B. 2. Party A presses the Menu key on the BlackBerry device, clicks Add Participant, and dials the external number of Party C. 3. The BlackBerry MVS Client creates a hold request. The MVS Session Manager places the SIP line call leg into a hold state through the PBX. 4. The MVS Session Manager uses the SIP line interface to request that the PBX establish another call leg to the external number of Party C. 5. The PBX determines that the number is external to the organization and rings the external number of Party C.
57
Call flows - PBX
6. When Party C answers the call, Party A presses the Menu key and clicks Join Conference. 7. The MVS Session Manager requests that the PBX join Party A, Party B, and Party C to the conference call. 8. The MVS Session Manager, through the PBX, ends the hold state from the SIP line call leg. 9. Voice communication occurs among Party A, Party B, and Party C.
Forwarding a BlackBerry MVS call through a PBX
58
Call flows - PBX
1. A BlackBerry Mobile Voice System administrator enables the user for call forwarding. 2. The BlackBerry MVS user configures a phone number to forward calls to. The phone number can be internal or external to the organization. 3. A caller dials the work number of the BlackBerry MVS user. 4. The PBX creates a call establishment request and sends it to the MVS Session Manager over the SIP line. 5. The MVS Session Manager filters the request through the BlackBerry MVS user's unknown caller ID setting, call scheduling setting, allowed caller list, blocked caller list and call forwarding settings. 6. The MVS Session Manager detects that call forwarding is enabled and sends a SIP 302 redirect to the PBX. 7. The PBX creates a call establishment request and redirects the call over the PSTN or LAN to the configured call forwarding number.
59
Call flows - PBX
Making a call when a user is experiencing wireless network congestion
Even if you have configured your organization's users for PBX-initiated calling, if users makes calls when they are experiencing wireless network congestion, the BlackBerry MVS Client uses BlackBerry device-initiated calling to make the call. 1. A BlackBerry Mobile Voice System user within an organization, who is in an area with wireless network congestion, uses a BlackBerry device to dial the extension number of another BlackBerry MVS user. The BlackBerry MVS Client starts a timer. 2. The BlackBerry MVS Client creates a call establishment request, which includes the destination number. The BlackBerry MVS Client compresses and encrypts the call establishment request, and tries to send the request to the BlackBerry Enterprise Server over the wireless network.
60
Call flows - PBX
3. Due to network congestion the call establishment request does not reach the BlackBerry Enterprise Server or the response from the BlackBerry Enterprise Server does not reach the BlackBerry device before the timer on the device expires. 4. The timer on the BlackBerry MVS Client expires, and the BlackBerry MVS Client sends a BYE message to the BlackBerry MVS Server to end the call. 5. The BlackBerry MVS Client uses the no data coverage calling number (that the administrator configured for the BlackBerry MVS Server) to call the MVS Session Manager. 6. The MVS Session Manager answers the call. 7. The BlackBerry MVS Client sends an authorization code and the number it wants to call to the MVS Session Manager using DTMF tones. 8. The MVS Session Manager, using a SIP line, requests that the PBX establish a call to the internal number using the extension number. 9. The PBX determines that the extension number is internal to the organization and rings the extension number over the organization's LAN. 10. The MVS Session Manager sends a message to the BlackBerry MVS Client to show the desk phone is ringing using DTMF tones. 11. The recipient answers the call at a desk phone. 12. The MVS Session Manager connects the SIP line call leg to the SIP trunk call leg, and voice communication occurs. 13. The MVS Session Manager sends a connected tone to the BlackBerry MVS Client. The BlackBerry MVS Clientdisplays that the call is connected. 14. The BlackBerry MVS Client acknowledges to the MVS Session Manager that it received the connected tone.
Using DTMF tones
1. A BlackBerry Mobile Voice System user is on a call to a voice mail account using the work number. The BlackBerry device emits DTMF tones for one of the following reasons: 61
Call flows - PBX
The user pressed a key. The user is in a wireless coverage area where data services are not available. The BlackBerry MVS Client uses DTMF tones to send call control requests.
2. The gateway detects and removes the DTMF tones from the media stream, and indicates to the PBX that it removed the DTMF tones. 3. The PBX sends the DTMF tones to the MVS Session Manager using KPML over the SIP line. 4. The MVS Session Manager performs one of the following actions: If the MVS Session Manager recognizes the DTMF tones as a call control sequence for the BlackBerry MVS, it performs an action (for example, sending a response as DTMF tones using KPML over the SIP trunk) based on the DTMF tones that it received. If the MVS Session Manager does not recognize the DTMF tones, it relays the DTMF tones through KPML to the PBX over the SIP line.
5. The PBX sends the DTMF tones to the gateway. 6. The gateway emits the DTMF tones into the media stream.
62
System requirements
System requirements
System requirements: BlackBerry MVS
Item Hardware Requirement Operating system Two Intel Xeon 2.0 GHz processors 250 GB disk space 4 GB RAM Two drives that are configured as RAID 1 or better
Any of the following operating systems: Windows Server 2008 SP2 (32-bit or 64-bit) Windows Server 2008 R2 (64-bit) Windows Server 2008 R2 SP1 (64-bit) Windows Server 2008 R2 SP1 (64-bit)
BlackBerry Enterprise Server
Any of the following BlackBerry Enterprise Server software: BlackBerry Enterprise Server 5.0.2 or later for Microsoft Exchange BlackBerry Enterprise Server 5.0.2 or later for IBM Lotus Domino BlackBerry Enterprise Server 5.0.2 or later for Novell GroupWise
Data management system
The required data management system depends on the version of the BlackBerry Enterprise Server that your organizations uses. All data management systems must have named pipes turned off and TCP/IP network protocols turned on. BlackBerry Enterprise Server 5.0.2 or BlackBerry Enterprise Server 5.0.3: Microsoft SQL Server 2005 SP3 (32-bit or 64-bit) Microsoft SQL Server 2005 SP4 (32-bit or 64-bit)
63
System requirements
Item
Requirement Microsoft SQL Server 2005 Express Edition SP3 (32-bit) Microsoft SQL Server 2008 SP1 (32-bit or 64-bit) Microsoft SQL Server 2008 SP2 (32-bit or 64-bit) Microsoft SQL Server 2008 SP3 (32-bit or 64-bit) Microsoft SQL Server 2008 R2 (32-bit or 64-bit) Microsoft SQL Server 2008 R2 SP1 (32-bit or 64-bit) Microsoft SQL Server 2008 Express Edition SP1 (32-bit or 64-bit) Microsoft SQL Server 2008 Express Edition SP3 (32-bit or 64-bit) Microsoft SQL Server 2008 Express Edition R2 (32-bit or 64-bit) Microsoft SQL Server 2008 Express Edition R2 SP1 (32-bit or 64-bit) Microsoft SQL Server 2008 Express Edition R2 SP2 (32-bit or 64-bit)
BlackBerry Enterprise Server 5.0.4: Java platform Browser Microsoft SQL Server 2005 SP3 (32-bit or 64-bit) Microsoft SQL Server 2005 SP4 (32-bit or 64-bit) Microsoft SQL Server 2005 Express Edition SP3 (32-bit) Microsoft SQL Server 2008 SP2 (32-bit or 64-bit) Microsoft SQL Server 2008 SP3 (32-bit or 64-bit) Microsoft SQL Server 2008 R2 (32-bit or 64-bit) Microsoft SQL Server 2008 R2 SP1 (32-bit or 64-bit) Microsoft SQL Server 2008 Express Edition SP1 (32-bit or 64-bit) Microsoft SQL Server 2008 Express Edition SP3 (32-bit or 64-bit) Microsoft SQL Server 2008 Express Edition R2 SP1 (32-bit or 64-bit) Microsoft SQL Server 2008 Express Edition R2 SP2 (32-bit or 64-bit)
Version 1.6 update 16 Any of the following browsers: Windows Internet Explorer 8 with JavaScript turned on Windows Internet Explorer 9 with JavaScript turned on Mozilla Firefox Google Chrome
64
System requirements
Item
Requirement
Organization's telephony infrastructure PBX vendor that is BlackBerry MVS platform-compliant BlackBerry Device Software Any of the following BlackBerry Device Software versions: BlackBerry Device Software 6.0 to 7.1
Make sure that the organization's devices are running the latest build of the BlackBerry Device Software that the wireless service provider has accepted. BlackBerry device The BlackBerry devices should be on the latest carrier accepted handheld build. Any of the following devices: Wireless service plan BlackBerry Bold 9650 smartphone BlackBerry Bold 9700 smartphone BlackBerry Bold 9790 smartphone BlackBerry Bold 9900 smartphone BlackBerry Bold 9930 smartphone BlackBerry Curve 8530 smartphone BlackBerry Curve 9220 smartphone BlackBerry Curve 9310 smartphone BlackBerry Curve 9320 smartphone BlackBerry Curve 9330 smartphone BlackBerry Curve 9350 smartphone BlackBerry Curve 9360 smartphone BlackBerry Curve 9380 smartphone BlackBerry Pearl 9100 smartphone BlackBerry Style 9670 smartphone BlackBerry Torch 9800 smartphone BlackBerry Torch 9810 smartphone BlackBerry Torch 9850 smartphone BlackBerry Torch 9860 smartphone Porsche Design P'9981 smartphone
Any of the following features:
65
System requirements
Item
Requirement Data and voice (not required if you use only Wi-Fi to make and take BlackBerry MVS calls) Caller ID (not required if you use only Wi-Fi to make and take BlackBerry MVS calls)
Virtual environment (if applicable)
Any of the following virtual environment software: VMware ESXi 4 and later VMware ESXi 5 and later Microsoft Hyper-V Server 2008 R2
System requirements: Telephony environment

Item DTMF Requirement Your organization's telephony environment must be able to perform the following actions: Detect and intercept DTMF tones from the mobile call leg between the PBX and BlackBerry devices Notify the BlackBerry MVS Server of the DTMF tones using KPML notification Emit DTMF tones into the audio path when the BlackBerry Mobile Voice System requests them Send DTMF tones that are at least 100 milliseconds in duration to devices
If your organization's telephony environment includes components, such as a voice mail server, that receive DTMF tones from the BlackBerry MVS, the telephony environment must be able to present the DTMF tones in the correct format (for example, RFC 2833, inband media, H.323). Caller Identification Number, ANI numbers (Calling party) When you use PBX-initiated call direction, you must configure a Caller Identification Number for each telephony connector. This number must be unique and dedicated to the BlackBerry MVS. 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
66
System requirements
Item
Requirement 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 device. You can specify additional ANI numbers for identifying BlackBerry MVS calls. Part of the BlackBerry MVS provisioning information that the BlackBerry MVS Server sends to the BlackBerry MVS Client includes the optional ANI numbers so that the BlackBerry MVS Client has a record of the numbers that can call. The BlackBerry MVS Client uses a combination of the caller identification number and the numbers in the Optional ANI numbers list to identify BlackBerry MVS calls. If your organization has a hunt group that is configured in the PBX with multiple outgoing trunks, and each trunk has its own ANI number, you must type each ANI number in the MVS Console. If you configure your organization's BlackBerry MVS for BlackBerry deviceinitiated calling, you must configure a DID/DDI number in your organization's telephony environment. This number must be unique and dedicated to the BlackBerry MVS. You must also configure the DID/DDI number in the MVS Console for each BlackBerry MVS Server. The DID/DDI number is used to provision the user accounts that you configured for the device. In the class of service, make sure that you choose BlackBerry Smartphone > PBX for users that you want to use BlackBerry deviceinitiated calling. You must verify that a call that arrives at the DID/DDI number prompts the telephony environment to send a SIP invitation to the BlackBerry MVS over the SIP connection that has been configured between the telephony environment and the BlackBerry MVS.
DID/DDI number (Called party)
DID/DDI number (No Data Coverage number)
If you configure a no data coverage number, you must configure a corresponding DID/DDI number on your organization's PBX. The BlackBerry MVS Client uses the no data coverage number to connect to the MVS Session Manager when the BlackBerry MVS user is using a wireless network that is experiencing congestion. If your organization's BlackBerry MVS is configured for high availability, you must make sure that you use a unique no data coverage number for each instance of theBlackBerry MVS Server.
Voice mail server (if necessary)
If your organization uses solicited voice mail, the BlackBerry MVS requires a SIP line to your organization's voice mail server, which must be compliant with RFC 3842, so that a MWI displays on users' devices.
67
System requirements
System requirements: PBX

Item KPML Support for BlackBerry devices SIP line SIP trunk Requirement The PBX must support KPML for the exchange of DTMF tones between the PBX and the BlackBerry Mobile Voice System. The device must be an endpoint for the PBX. You must configure a SIP line from the BlackBerry MVS to the PBX so that the PBX can establish calls to devices. You must configure a SIP trunk from the BlackBerry MVS to the PBX so that the PBX can send calls to the mobile numbers on devices. When you configure the SIP trunk, you must provide the IP address and port number of the BlackBerry MVS Server. The phone numbers that the BlackBerry MVS sends to the PBX might not contain leading digits to indicate how the PBX should route the call. You might need to configure the PBX so that the call routing patterns add or remove leading digits for routing to internal numbers or external numbers. For example, you should consider creating the following call routing patterns: One that permits BlackBerry MVS users to make calls from the call log or contact list on their devices without adding 9 before a phone number One that removes an NDD number from phone numbers that are dialed from devices if the BlackBerry MVS user is in the same geographic location as the PBX. The PBX should be configured to manage calls from devices if the user types (519) 555-0100 or (1) (519) 555-0100. One for regions or countries that your organization's users frequently travel to
Call routing patterns for internal numbers and external numbers
Ensure the Class of Service setting of "User may change the mobile phone number" is checked. When your organization's users are roaming internationally, it might be necessary for the users to manually change the mobile number on their devices to reflect what the PBX must dial to contact the user. For example, if the user is from the United Kingdom the mobile number on the user's device should be changed to include the IDD (00), the home country code (44), and the user's area code and local phone number. For more information on changing the mobile phone number on the device, visit www.blackberry.com/support to read article KB17940. DID/DDI number To configure BlackBerry device-initiated calling, you must configure your organization's call routing patterns so that the PBX can route the device-initiated calls that use a DID/DDI number to the BlackBerry MVS Server that is associated with the DID/DDI number. For example, if the DID/DDI number that you configure in the MVS Console for the BlackBerry MVS Server is +15195550100, for any device-
68
System requirements
Item
Requirement initiated calls that arrive at the PBX using a DID/DDI number of +15195550100, the PBX must route the calls to the BlackBerry MVS Server that is associated with the DID/DDI number of +15195550100. You require one DID/DDI number for each BlackBerry MVS Server in your organizations environment.
69
Glossary
Glossary
ANI BlackBerry MVS CDMA DTMF EDGE GPRS GSM KPML LAN MAC PBX PSTN SIP TCP Automatic Number Identification BlackBerry Mobile Voice System Code Division Multiple Access Dual Tone Multi-Frequency Enhanced Data Rates for Global Evolution General Packet Radio Service Global System for Mobile Communications Key Press Markup Language local area network Media Access Control Private Branch Exchange Public Switched Telephone Network Session Initiation Protocol Transmission Control Protocol
70
Provide feedback
Provide feedback
To provide feedback on this deliverable, visit www.blackberry.com/docsfeedback. To verify that you are using the most recent documentation, refer to www.blackberry.com/go/mvsdocs.
71
Legal notice
Legal notice
names, and logos are the property of Research In Motion Limited and are registered and/or used in the U.S. and countries around the world. IBM, Lotus, and Domino are trademarks of International Business Machines Corporation. Mozilla and Firefox are trademarks of Mozilla Foundation. Intel and Xeon are trademarks of Intel Corporation. JavaScript is a trademark of Oracle and/or its affiliates. Microsoft, Hyper-V, Internet Explorer, SQL Server, Windows, and Windows Server are trademarks of Microsoft Corporation. Novell and GroupWise are trademarks of Novell, Inc. VMware is a trademark of VMware, Inc. Wi-Fi is a trademark of the Wi-Fi Alliance. All other trademarks are the property of their respective owners. This documentation including all documentation incorporated by reference herein such as documentation provided or made available at www.blackberry.com/go/docs is provided or made accessible "AS IS" and "AS AVAILABLE" and without condition, endorsement, guarantee, representation, or warranty of any kind by Research In Motion Limited and its affiliated companies ("RIM") and RIM assumes no responsibility for any typographical, technical, or other inaccuracies, errors, or omissions in this documentation. In order to protect RIM proprietary and confidential information and/or trade secrets, this documentation may describe some aspects of RIM technology in generalized terms. RIM reserves the right to periodically change information that is contained in this documentation; however, RIM makes no commitment to provide any such changes, updates, enhancements, or other additions to this documentation to you in a timely manner or at all. This documentation might contain references to third-party sources of information, hardware or software, products or services including components and content such as content protected by copyright and/or third-party websites (collectively the "Third Party Products and Services"). RIM does not control, and is not responsible for, any Third Party Products and Services including, without limitation the content, accuracy, copyright compliance, compatibility, performance, trustworthiness, legality, decency, links, or any other aspect of Third Party Products and Services. The inclusion of a reference to Third Party Products and Services in this documentation does not imply endorsement by RIM of the Third Party Products and Services or the third party in any way. EXCEPT TO THE EXTENT SPECIFICALLY PROHIBITED BY APPLICABLE LAW IN YOUR JURISDICTION, ALL CONDITIONS, ENDORSEMENTS, GUARANTEES, REPRESENTATIONS, OR WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, ANY CONDITIONS, ENDORSEMENTS, GUARANTEES, REPRESENTATIONS OR WARRANTIES OF DURABILITY, FITNESS FOR A PARTICULAR PURPOSE OR USE, MERCHANTABILITY, MERCHANTABLE QUALITY, NON-INFRINGEMENT, SATISFACTORY QUALITY, OR TITLE, OR ARISING FROM A STATUTE OR CUSTOM OR A COURSE OF DEALING OR USAGE OF TRADE, OR RELATED TO THE DOCUMENTATION OR ITS USE, OR PERFORMANCE OR NON-PERFORMANCE OF ANY SOFTWARE, HARDWARE, SERVICE, OR ANY THIRD PARTY PRODUCTS AND SERVICES REFERENCED HEREIN, ARE HEREBY EXCLUDED. YOU MAY ALSO HAVE OTHER RIGHTS THAT VARY BY STATE OR PROVINCE. SOME JURISDICTIONS MAY NOT ALLOW THE EXCLUSION OR LIMITATION OF IMPLIED WARRANTIES AND CONDITIONS. TO THE EXTENT PERMITTED BY LAW, ANY IMPLIED WARRANTIES OR CONDITIONS RELATING TO THE DOCUMENTATION TO THE EXTENT THEY CANNOT BE EXCLUDED AS SET OUT ABOVE, BUT CAN BE LIMITED, ARE HEREBY LIMITED TO NINETY (90) DAYS FROM THE DATE YOU FIRST ACQUIRED THE DOCUMENTATION OR THE ITEM THAT IS THE SUBJECT OF THE CLAIM.
2012 Research In Motion Limited. All rights reserved. BlackBerry, RIM, Research In Motion, and related trademarks,
72
Legal notice
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW IN YOUR JURISDICTION, IN NO EVENT SHALL RIM BE LIABLE FOR ANY TYPE OF DAMAGES RELATED TO THIS DOCUMENTATION OR ITS USE, OR PERFORMANCE OR NONPERFORMANCE OF ANY SOFTWARE, HARDWARE, SERVICE, OR ANY THIRD PARTY PRODUCTS AND SERVICES REFERENCED HEREIN INCLUDING WITHOUT LIMITATION ANY OF THE FOLLOWING DAMAGES: DIRECT, CONSEQUENTIAL, EXEMPLARY, INCIDENTAL, INDIRECT, SPECIAL, PUNITIVE, OR AGGRAVATED DAMAGES, DAMAGES FOR LOSS OF PROFITS OR REVENUES, FAILURE TO REALIZE ANY EXPECTED SAVINGS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, LOSS OF BUSINESS OPPORTUNITY, OR CORRUPTION OR LOSS OF DATA, FAILURES TO TRANSMIT OR RECEIVE ANY DATA, PROBLEMS ASSOCIATED WITH ANY APPLICATIONS USED IN CONJUNCTION WITH RIM PRODUCTS OR SERVICES, DOWNTIME COSTS, LOSS OF THE USE OF RIM PRODUCTS OR SERVICES OR ANY PORTION THEREOF OR OF ANY AIRTIME SERVICES, COST OF SUBSTITUTE GOODS, COSTS OF COVER, FACILITIES OR SERVICES, COST OF CAPITAL, OR OTHER SIMILAR PECUNIARY LOSSES, WHETHER OR NOT SUCH DAMAGES WERE FORESEEN OR UNFORESEEN, AND EVEN IF RIM HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW IN YOUR JURISDICTION, RIM SHALL HAVE NO OTHER OBLIGATION, DUTY, OR LIABILITY WHATSOEVER IN CONTRACT, TORT, OR OTHERWISE TO YOU INCLUDING ANY LIABILITY FOR NEGLIGENCE OR STRICT LIABILITY. THE LIMITATIONS, EXCLUSIONS, AND DISCLAIMERS HEREIN SHALL APPLY: (A) IRRESPECTIVE OF THE NATURE OF THE CAUSE OF ACTION, DEMAND, OR ACTION BY YOU INCLUDING BUT NOT LIMITED TO BREACH OF CONTRACT, NEGLIGENCE, TORT, STRICT LIABILITY OR ANY OTHER LEGAL THEORY AND SHALL SURVIVE A FUNDAMENTAL BREACH OR BREACHES OR THE FAILURE OF THE ESSENTIAL PURPOSE OF THIS AGREEMENT OR OF ANY REMEDY CONTAINED HEREIN; AND (B) TO RIM AND ITS AFFILIATED COMPANIES, THEIR SUCCESSORS, ASSIGNS, AGENTS, SUPPLIERS (INCLUDING AIRTIME SERVICE PROVIDERS), AUTHORIZED RIM DISTRIBUTORS (ALSO INCLUDING AIRTIME SERVICE PROVIDERS) AND THEIR RESPECTIVE DIRECTORS, EMPLOYEES, AND INDEPENDENT CONTRACTORS. IN ADDITION TO THE LIMITATIONS AND EXCLUSIONS SET OUT ABOVE, IN NO EVENT SHALL ANY DIRECTOR, EMPLOYEE, AGENT, DISTRIBUTOR, SUPPLIER, INDEPENDENT CONTRACTOR OF RIM OR ANY AFFILIATES OF RIM HAVE ANY LIABILITY ARISING FROM OR RELATED TO THE DOCUMENTATION. Prior to subscribing for, installing, or using any Third Party Products and Services, it is your responsibility to ensure that your airtime service provider has agreed to support all of their features. Some airtime service providers might not offer Internet browsing functionality with a subscription to the BlackBerry Internet Service. Check with your service provider for availability, roaming arrangements, service plans and features. Installation or use of Third Party Products and Services with RIM's products and services may require one or more patent, trademark, copyright, or other licenses in order to avoid infringement or violation of third party rights. You are solely responsible for determining whether to use Third Party Products and Services and if any third party licenses are required to do so. If required you are responsible for acquiring them. You should not install or use Third Party Products and Services until all necessary licenses have been acquired. Any Third Party Products and Services that are provided with RIM's products and services are provided as a convenience to you and are provided "AS IS" with no express or implied conditions, endorsements, guarantees, representations, or warranties of any kind by RIM and RIM assumes no liability whatsoever, in relation thereto. Your use of Third Party Products and Services shall be governed by and subject to you agreeing to the terms of separate licenses and other agreements applicable thereto with third parties, except to the extent expressly covered by a license or other agreement with RIM. Certain features outlined in this documentation require a minimum version of BlackBerry Enterprise Server, BlackBerry Desktop Software, and/or BlackBerry Device Software.
73
Legal notice
The terms of use of any RIM product or service are set out in a separate license or other agreement with RIM applicable thereto. NOTHING IN THIS DOCUMENTATION IS INTENDED TO SUPERSEDE ANY EXPRESS WRITTEN AGREEMENTS OR WARRANTIES PROVIDED BY RIM FOR PORTIONS OF ANY RIM PRODUCT OR SERVICE OTHER THAN THIS DOCUMENTATION. Research In Motion Limited 295 Phillip Street Waterloo, ON N2L 3W8 Canada Research In Motion UK Limited 200 Bath Road Slough, Berkshire SL1 3XE United Kingdom Published in Canada
74

BlackBerry Mobile Voice System 5.2.1 Feature and Technical Overview

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

BlackBerry Mobile Voice System 5.2.1 Feature and Technical Overview

Hochgeladen von

Copyright:

Verfügbare Formate

BlackBerry Mobile Voice System

Feature and Technical Overview

Published: 2012-11-23 SWD-20121123082215916

Architecture: BlackBerry MVS ....................................................................................................... 16

BlackBerry MVS and call recording ................................................................................................ 21

Call flows - PBX ............................................................................................................................. 23

System requirements .................................................................................................................... 63

Feature and Technical Overview

Feature and Technical Overview

Features for managing user accounts and BlackBerry devices

Feature and Technical Overview

Feature Classes of service

Feature and Technical Overview

Feature and Technical Overview

Feature User licensing

Management of administrative roles

Feature and Technical Overview

Feature Phone number translation

Input validation rules

Call and diagnostic logging

Feature and Technical Overview

Default network selection

Feature and Technical Overview

Access to desk phone features

Feature and Technical Overview

Voice mail integration

Corporate directory Caller restrictions

Feature and Technical Overview

Feature and Technical Overview

Feature and Technical Overview

Architecture: BlackBerry MVS

Architecture: BlackBerry MVS

Feature and Technical Overview

Architecture: BlackBerry MVS

MVS Data Manager

MVS BlackBerry Enterprise Server Connector

MVS Witness Server

BlackBerry MVS Client

Feature and Technical Overview

Architecture: BlackBerry MVS

BlackBerry MVS high availability

Feature and Technical Overview

Architecture: BlackBerry MVS

Feature and Technical Overview

Architecture: BlackBerry MVS

Feature and Technical Overview

BlackBerry MVS and call recording

BlackBerry MVS and call recording

Architecture: Call recording

Feature and Technical Overview

BlackBerry MVS and call recording

Restricting users to the BlackBerry MVS line

Feature and Technical Overview

Call flows - PBX

Call flows - PBX

Feature and Technical Overview

Call flows - PBX

Feature and Technical Overview

Call flows - PBX

Making a BlackBerry deviceinitiated call from a BlackBerry device to an internal number

Feature and Technical Overview

Call flows - PBX

Feature and Technical Overview