Feature and Technical

Transcription

1 BlackBerry Mobile Voice System for SIP Gateways and the Avaya Aura Session Manager Version: 5.3 Feature and Technical Overview

2 Published: SWD

3 Contents 1 Overview Features...5 Features for managing user accounts and BlackBerry devices... 5 Security features...9 Phone features Architecture: BlackBerry MVS with SIP intermediary BlackBerry Domain...16 BlackBerry MVS configuration...17 Architecture: BlackBerry MVS high availability BlackBerry MVS and call recording Architecture: Call recording...20 Restricting users to the BlackBerry MVS line Call flows: SIP Gateway with the Avaya Aura Session Manager Call flow: Making a PBX-initiated call from a BlackBerry device to an internal number Call flow: Making a BlackBerry device initiated call to an internal number Call flow: Making a call from a BlackBerry device using Voice over Wi-Fi to an internal number Call flow: Receiving a PBX-initiated call on a BlackBerry device from an external number Call flow: Receiving a BlackBerry device initiated call on a device from an external number Call flow: Receiving a call on a BlackBerry device using Voice over Wi-Fi...33 Call flow: Holding and resuming a call on a BlackBerry device...35 Call flow: Transferring a call on a BlackBerry device using Voice over Mobile System requirements...39 System requirements: BlackBerry MVS System requirements: Telephony environment System requirements: SIP gateway Glossary Provide feedback Legal notice...49

4 Overview Overview 1 The BlackBerry Mobile Voice System integrates your organization's PBX environment with a BlackBerry Enterprise Server instance or a BlackBerry Enterprise Service 10 instance 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 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 and BlackBerry Enterprise Service 10 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 4

5 Features Features 2 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 Description User account activation You associate existing BlackBerry Enterprise Server and BlackBerry Enterprise Service 10 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 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 5

6 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. When you make a configuration change to a class of service, the BlackBerry MVS Server sends the change to the BlackBerry device where the change is saved locally. If a user makes a configuration change to the class of service settings on a device, the device sends the change to the BlackBerry MVS Server. A class of service can permit users to perform the following actions: Transfer calls Move calls to their desk numbers. (In an Avaya integration, users do not have to use the BlackBerry MVS Client to move calls; they can pick up the desk phone, enter their password, and proceed with the call.) 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 MVSLine When the BlackBerry MVS Line is unavailable, use the Mobile Line: Never Default Network for BlackBerry MVScalls: Wi-Fi When Wi-Fi is 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 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: 6

7 Features Feature Description Your organization's data calls set up successfully 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 Wi- Fi 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. 7

8 Features Feature Description The BlackBerry MVS automatically sends updates to the BlackBerry Enterprise Server, which sends the updates to the users over the wireless network. User licensing Management of administrative roles 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 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. 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. You configure the Caller Identification Number on the Telephony Connector page of the MVS Console. 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. 8

9 Features Feature Description If your organization uses devices that operate on CDMA networks, device-initiated calling offers optimal performance and reliability for BlackBerry MVS calls. Phone number translation Provisioning Input validation rules 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 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, and preferences. 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. Security features Feature Authentication of BlackBerry Mobile Voice System users Standard message encryption Description The BlackBerry Enterprise Server and BlackBerry Enterprise Service 10 are designed to authenticate BlackBerry device users to the BlackBerry MVS and your organization's PBX phone system. When users connect to the wireless network, the BlackBerry MVS Client is designed to register with the BlackBerry MVS Server. 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. The 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 the BlackBerry MVS. For more information, see the BlackBerry Enterprise Solution Security Technical Overview. 9

10 Features Feature Call and diagnostic logging Description The BlackBerry MVS call logs provide information about the call activity of BlackBerry device users. They also include information about error messages, warnings, information that you can use to troubleshoot issues, and other events that are related to the 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 Wi- Fi as the default network to make and receive calls. To configure the default network, the following options are available: 10

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 Wi- Fi. 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 Access to desk phone features 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: 11

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 5.0 or 6.0, or the users are using a BlackBerry Curve 9360 smartphone or a BlackBerry Bold 9790 smartphone) Move calls to their desk phones. (In an Avaya integration, users do not have to use the BlackBerry MVS Client to move calls; they can pick up the desk phone, enter their password, and proceed with the call.) 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 the work number to the mobile number Switch active calls Forward incoming BlackBerry MVS calls to an internal extension or another phone Voice mail integration Corporate directory Caller restrictions 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. 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: All Callers Allowed 12

13 Features Feature Description 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 cellular line Incoming calls to the cellular line do not appear on the BlackBerry device Users cannot use the cellular line to make outgoing calls A user who is configured for BlackBerry MVS Only Calling can make or take a call using the cellular 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 the Telephony Connector DID/DDI Number and the number that you use for the PBX Initiated Calling Caller Identification Number. 13

14 Architecture: BlackBerry MVS with SIP intermediary Architecture: BlackBerry MVS with SIP intermediary 3 The basic BlackBerry Mobile Voice System includes a standalone BlackBerry MVS Server instance that is integrated with a BlackBerry Enterprise Server instance and one SIP gateway, or a BlackBerry Enterprise Service 10 instance and one SIP gateway, or a BlackBerry Enterprise Server and a BlackBerry Enterprise Service 10 instance connected to one SIP gateway. You can use the SIP gateway implementation to translate DTMF tones from RFC2833 to SIP INFO for incoming BlackBerry MVS calls and from SIP INFO to RFC2833 for outgoing BlackBerry MVS calls. The SIP intermediary in the following diagrams can be either an Avaya Aura Session Manager or an Acme Packet Session Border Controller. The following architecture diagram shows the BlackBerry MVS installed with a BlackBerry Enterprise Server. The BlackBerry MVS includes one of each of the following components: 14

15 Architecture: BlackBerry MVS with SIP intermediary Component MVS Console MVS Session Manager 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. The MVS Session Manager communicates with: The MVS BlackBerry Enterprise Server Connector to send and receive BlackBerry MVS requests to and from BlackBerry devices A SIP gateway to route BlackBerry MVS calls to and from the PBX A voice mail server to provide device users with access to the voice mail messages for their work numbers The MVS Witness Server when the MVS Session Manager is in a high availability pair. If the active MVS Session Manager fails, the MVS Witness Server manages the failover to the standby MVS Session Manager. The MVS Session Manager includes: FMC Phone: FMC Phone extends desk phone features to BlackBerry devices. MVS Event Manager: The MVS Event Manager collects application events from BlackBerry devices and BlackBerry MVS components and stores them as event files on the BlackBerry MVS Server. MVS Data Manager MVS BlackBerry Enterprise Server Connector MVS Witness Server 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. If your organization's BlackBerry MVS is integrated with a BlackBerry Enterprise Server, 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. If your organization's BlackBerry MVS is integrated with a BlackBerry Enterprise Service 10 instance, the MVS BlackBerry Enterprise Server Connector communicates with the BlackBerry MDS Connection Service for communication 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. 15

16 Architecture: BlackBerry MVS with SIP intermediary The BlackBerry MVS also includes functionality that is provided by the BlackBerry Enterprise Server and the BlackBerry device: 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: BlackBerry Configuration Database: The BlackBerry Configuration Database stores the configuration information for the BlackBerry MVS. BlackBerry Dispatcher: The BlackBerry Dispatcher 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. BlackBerry Router: The BlackBerry Router communicates with the BlackBerry devices. BlackBerry Enterprise Service 10 BlackBerry Enterprise Service 10 provides BlackBerry device management and security, including authentication between BlackBerry devices and the BlackBerry MVS Server. The BlackBerry MVS uses the following BlackBerry Enterprise Service 10 components: The BlackBerry Configuration Database which stores the configuration information for the BlackBerry MVS. The BlackBerry MDS Connection Service for communication between the MVS Session Manager and BlackBerry devices. 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. BlackBerry Domain The BlackBerry MVS uses the BlackBerry Configuration Database for all data storage requirements. You configure the BlackBerry Configuration Database when you install the BlackBerry Enterprise Server or BlackBerry Enterprise Service 10. You can configure several BlackBerry Enterprise Server instances or several BlackBerry Enterprise Service 10 instances to use the same BlackBerry Configuration Database. A BlackBerry Domain consists of one BlackBerry Configuration Database and all the BlackBerry Enterprise Server instances or BlackBerry Enterprise Service 10 instances that use the database. One BlackBerry MVS can support several BlackBerry Enterprise Server instances or several BlackBerry Enterprise Service 10 instances and all their users if they are all in the same BlackBerry Domain. 16

17 Architecture: BlackBerry MVS with SIP intermediary 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 disable a BlackBerry MVS component from the BlackBerry MVS configuration. For more information on adding or removing a BlackBerry MVS Server component, see the BlackBerry MVS Administration Guide. Architecture: BlackBerry MVS high availability The BlackBerry Mobile Voice System high availability installation with a BlackBerry Enterprise Server is illustrated below. The SIP intermediary in the following diagrams can be either an Avaya Aura Session Manager or an Acme Packet Session Border Controller. 17

18 Architecture: BlackBerry MVS with SIP intermediary To make sure that there is no single point of failure of BlackBerry MVS components, you install two instances of each BlackBerry MVS component. After you install the BlackBerry MVS Server instances, to enable high availability, you use the MVS Console to pair one BlackBerry MVS Server with another. 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 MVS Session Manager (except MVS Event Manager) MVS BlackBerry Enterprise Server Connector Model Active-active Active-active Active-active Active-active Active-standby Active-standby In an active-standby model, high availability is achieved when one BlackBerry MVS Server is paired with another, through the MVS Console. When you have paired the two MVS Session Manager instances, one of the MVS Session Manager instances becomes active and the other standby. The same holds for the two MVS BlackBerry Enterprise Server Connector 18

19 Architecture: BlackBerry MVS with SIP intermediary instances: One becomes active, one standby. The components themselves determine which one becomes active and which one standby. If the active component fails, failover from the active component to the standby component is managed by the components in conjunction with the MVS Witness Server. In an active-active model, components are always active. If a component fails, the BlackBerry MVS automatically stops using that component. High availability is achieved by providing two components of the same type at the BlackBerry Domain level, and not for every high availability pair. For example, because MVS Data Manager instances use an active-active model, two MVS Data Manager instances provide redundancy for all BlackBerry MVS Server instances in the BlackBerry Domain. By comparison, there must be one active and one standby MVS Session Manager for every high availability pair. 19

20 BlackBerry MVS and call recording BlackBerry MVS and call recording 4 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 a SIP gateway, the recording solution monitors (or spans) the switch port that is connected to the SIP gateway. This spanning mechanism copies all messages and media to the recording solution that is destined to or that originates from the SIP gateway. The recording solution then captures, tags and archives the messages and media appropriately. 20