BlackBerry Mobile Voice System

Version: 4.6

Feature and Technical Overview

SWD-398613-0519075943-001

Contents
1 Overview....................................................................................................................................................................................... 2 3 6 6 7 9 10 10 12 14 15 17 18 19 20 22 22 23 24 25 25 26 29 30 2 Architecture: BlackBerry MVS................................................................................................................................................... 3 Features......................................................................................................................................................................................... Phone features................................................................................................................................................................................ Features for managing user accounts and devices..................................................................................................................... Security features............................................................................................................................................................................. 4 Process flows................................................................................................................................................................................ Process flow: Making a call from a BlackBerry device (BlackBerry device initiates).............................................................. Process flow: Making a call from a BlackBerry device (PBX initiates)...................................................................................... Process flow: Making a call from a mobile phone....................................................................................................................... Process flow: Making a call to an external phone number........................................................................................................ Process flow: Receiving a call on a BlackBerry device............................................................................................................... Process flow: Transferring a call from a BlackBerry device....................................................................................................... Process flow: Moving a call from a BlackBerry device to a desk phone................................................................................... Process flow: Adding another party to a call on a BlackBerry device....................................................................................... 5 Requirements............................................................................................................................................................................... System requirements: BlackBerry MVS........................................................................................................................................ System requirements: Network..................................................................................................................................................... System requirements: PBX............................................................................................................................................................ System requirements: Media gateway......................................................................................................................................... System requirements: Voice mail integration............................................................................................................................. 6 Glossary......................................................................................................................................................................................... 7 Provide feedback......................................................................................................................................................................... 8 Legal notice..................................................................................................................................................................................

Feature and Technical Overview

Overview

Overview

BlackBerry Mobile Voice System integrates your organization's telephone system with the BlackBerry Enterprise Server to extend desk phone functionality to BlackBerry devices. BlackBerry MVS is designed to integrate with the phone application on BlackBerry devices to permit users to make calls from and receive calls to their work phone numbers and access some of the features that are available from your organization's desk phones provide a user account with a single work phone number that can ring on up to four phones simultaneously or sequentially, and direct unanswered calls to a single voice mailbox that is associated to the work phone number permit users to create ad hoc conference calls from their BlackBerry devices extend the security features of the BlackBerry Enterprise Server to authenticate BlackBerry device users to BlackBerry MVS and your organization's PBX phone system permit you to manage BlackBerry devices over the wireless network from a single location and control access to the work phone numbers and phone features that BlackBerry MVS provides

Feature and Technical Overview

Architecture: BlackBerry MVS

Architecture: BlackBerry MVS

BlackBerry Mobile Voice System is designed to integrate with an organizations PBX through a media gateway that is connected to the PBX using T1/E1 ISDN-PRI.

Component BlackBerry Enterprise Server

Description The BlackBerry Enterprise Server is designed to provide BlackBerry device management and security functionality, including authentication between BlackBerry devices and the BlackBerry MVS Server. BlackBerry MVS uses the following BlackBerry Enterprise Server components: BlackBerry Configuration Database: The BlackBerry Configuration Database stores the information that BlackBerry MVS uses. The BlackBerry MVS Connection Service retrieves information from the BlackBerry Configuration Database to send and receive secure data communication between BlackBerry MVS and the BlackBerry Enterprise Server. BlackBerry Dispatcher: The BlackBerry Dispatcher is designed to encrypt and compress, and decompress and decrypt all data that is sent to and from BlackBerry devices. The BlackBerry Dispatcher sends the data through the BlackBerry Router to and from the wireless network.

Feature and Technical Overview

Architecture: BlackBerry MVS

Component

Description BlackBerry Router: The BlackBerry Router connects to the wireless network to send data to and from BlackBerry devices.

BlackBerry MVS Server

You install the BlackBerry MVS software on a computer that is separate from the BlackBerry Enterprise Server. The BlackBerry MVS Server communicates with the BlackBerry Enterprise Server and PBX. For voice communication, the BlackBerry MVS Server connects to the PBX through a media gateway. For data communication with BlackBerry devices, the BlackBerry MVS Server connects to the BlackBerry Enterprise Server. The BlackBerry MVS Server includes the following services: BlackBerry MVS Call Processor: The BlackBerry MVS Call Processor communicates with the BlackBerry MVS Session Manager and BlackBerry MVS Connection Service to send and receive SIP calls and data messages. The BlackBerry MVS Call Processor connects to the media gateway to send and receive RTP packets. BlackBerry MVS uses RTP packets to provide media features, such as conferencing and music on hold, and detect DTMF codes for features such as setting up ad-hoc conferences, transferring calls, and retrieving voice mail. The BlackBerry MVS Call Processor also connects to the BlackBerry MVS web UI to send applicable changes made to a user account to the BlackBerry MVS Client. BlackBerry MVS Connection Service: The BlackBerry MVS Connection Service connects to the BlackBerry Enterprise Server to send secure data communication to and receive secure data communication from the BlackBerry MVS Client. BlackBerry MVS Notification Service: The BlackBerry MVS Notification Service connects to your organization's messaging server to provide notification messaging services. BlackBerry MVS Session Manager: The BlackBerry MVS Session Manager connects to the media gateway to communicate incoming and outgoing SIP calls. It sends incoming calls to and receives outgoing calls from the BlackBerry MVS Call Processor.

Feature and Technical Overview

Architecture: BlackBerry MVS

Component

Description BlackBerry MVS web UI: You can use the BlackBerry MVS web UI to perform BlackBerry MVS tasks, such as activating user accounts and managing the BlackBerry MVS Client over the wireless network. You can permit users to use the web UI to manage their user accounts, including phones and schedules, and schedule conferences. BlackBerry MVS database: The BlackBerry MVS database contains configuration data and transactional data that components of the BlackBerry MVS Server use.

BlackBerry device with the BlackBerry MVS Client

BlackBerry MVS users can use BlackBerry devices to extend the capabilities of their work desk phones. The BlackBerry MVS Client integrates with the phone application on BlackBerry devices and permits users to make calls from and receive calls to their work phone numbers, and to access some of the phone features that are available from your organization's desk phones. Users can have only one BlackBerry device with the BlackBerry MVS Client.

Feature and Technical Overview

Features

Features
Phone features
Feature single phone number Description

Each BlackBerry Mobile Voice System user has a single phone number that simultaneously or sequentially rings up to four phones, such as a desk phone, a BlackBerry device, and two additional phones. Users can add phones to their user accounts if you permit them to do so. BlackBerry MVS users can use the phone application on their BlackBerry devices to access the desk phone features of the BlackBerry MVS Client. Users can use the desk phone features of the BlackBerry MVS Client to perform the following actions: make a call from a work phone number answer a call to a work phone number transfer a call place a call on hold switch to another call during a call move a call to a desk phone during a conversation

access to desk phone features

caller restrictions

Users can access the desk phone features from other phones that are associated to their user accounts by calling a mobile access number and using touch-tones to access desk phone features. You can use caller restrictions to filter incoming calls. When a user receives a call, the BlackBerry MVS Server filters the phone number through two lists: allowed callers and blocked callers. If the BlackBerry MVS Server finds the phone number in the allowed callers list, it notifies the user of the call. If the BlackBerry MVS Server finds the phone number in the blocked callers list, it forwards the call directly to the user's voice mailbox. Users can also restrict all calls. If users turn on this feature, the BlackBerry MVS Server forwards calls directly to the users' voice mailboxes unless the phone numbers appear in the allowed caller list.

Feature and Technical Overview

Features for managing user accounts and devices

Feature

Description Users can manage the lists of allowed callers and blocked callers if you permit them to do so. You can integrate BlackBerry MVS with your organization's voice mail system to provide users with access to their work voice mailboxes. You can configure a voice mail message indicator to appear on BlackBerry devices when voice mail messages are waiting for users. You can schedule when BlackBerry MVS users can receive calls to their work phone numbers and the phones associated with their user accounts. Users can change these schedules if you permit them to do so. Users can use their BlackBerry devices to create ad-hoc conference calls and invite as many parties to join a call as necessary. You can permit users to use the BlackBerry MVS web UI to create scheduled conferences. Users can select whether the BlackBerry MVS Server sends an email notification message to conference participants with an access phone number and secure access code, or whether the BlackBerry MVS Server calls participants when the conference begins.

integrated voice mail

scheduling

conferencing

Features for managing user accounts and devices

You can use the BlackBerry Mobile Voice System web UI to configure and manage user accounts. Feature user accounts Description You must associate existing BlackBerry Enterprise Server user accounts with BlackBerry MVS. The BlackBerry Enterprise Server user accounts must be assigned BlackBerry devices. These are the only devices that can run the BlackBerry MVS Client. You can create administrative accounts to permit multiple administrators to access the BlackBerry MVS web UI. You can permit administrators to manage user accounts and system settings. You can use feature sets to control the features of the web UI and BlackBerry devices that users can access. Feature sets can permit users to perform the following actions: add phones to their user accounts

administrator accounts

feature sets

Feature and Technical Overview

Features for managing user accounts and devices

Feature

Description access features of the BlackBerry MVS Client on their BlackBerry devices configure some of the BlackBerry MVS Client settings access the conferencing features of BlackBerry MVS

user access to the web UI methods of connecting calls

Users can manage their user accounts and conferences using the web UI if you permit them to do so. BlackBerry MVS starts incomings calls to BlackBerry devices using your organization's PBX. You can manage how outgoing calls from BlackBerry devices connect to your organization's PBX using the following methods: start calls using BlackBerry devices start calls using your organization's PBX

If BlackBerry devices start calls, the BlackBerry MVS Server sends a message with a DNIS from a DNIS pool to a BlackBerry device. The BlackBerry device calls the BlackBerry MVS Server using the DNIS. After the BlackBerry MVS Server receives a call with the DNIS, it completes the call. If your organization's PBX starts calls, the BlackBerry MVS Server sends a message with an ANI from an ANI pool to a BlackBerry device. The BlackBerry MVS Server calls the BlackBerry device using the ANI. After the BlackBerry device receives a call with the ANI, the BlackBerry device connects to the call. You can make the BlackBerry MVS Client available to users over the wireless network. The BlackBerry MVS Server can send updates to users over the wireless network. If you delete or suspend user accounts, users can no longer access their work phone numbers or use the BlackBerry MVS Client on their BlackBerry devices.

wireless device management

Feature and Technical Overview

Security features

Security features
Feature authentication of BlackBerry Mobile Voice System users Description Only authenticated BlackBerry MVS users can use their BlackBerry devices to extend the capabilities of their work desk phones. The BlackBerry Enterprise Server is designed to authenticate BlackBerry device users to BlackBerry MVS. Only authenticated BlackBerry device users can access the work phone numbers and features of the BlackBerry MVS Client. BlackBerry MVS is designed to take advantage of the security features of the BlackBerry Enterprise Solution. The BlackBerry Enterprise Solution is designed to use a symmetric key encryption algorithm to protect data in transit between BlackBerry devices and BlackBerry MVS. For more information, see the BlackBerry Enterprise Solution Security Technical Overview. BlackBerry MVS creates log files to record information about the call activity of users, error messages, warnings, daily activities, and other events that are related to BlackBerry MVS. You can run predefined reports to collect information about the BlackBerry MVS environment and use this information for analysis and troubleshooting. You can configure notification groups to send notification email messages to contacts about BlackBerry MVS events that might require action.

standard message encryption

monitoring

notification groups

Feature and Technical Overview

Process flows

Process flows

Process flow: Making a call from a BlackBerry device (BlackBerry device initiates)

This process flow applies to a user who makes a call from a BlackBerry device and the BlackBerry device starts the call. 1. 2. 3. 4. 5. 6. A BlackBerry Mobile Voice System user makes a call from a BlackBerry device to another extension within the user's organization. The BlackBerry MVS Client starts an outgoing call request, which identifies the user and includes the destination extension number. The BlackBerry device compresses and encrypts the call request, and sends it to the wireless network over port 3101. The wireless network sends the call request to the BlackBerry Enterprise Server. The BlackBerry Enterprise Server decrypts and decompresses the call request, and sends it to the BlackBerry MVS Connection Service over the LAN using a TCP connection. The BlackBerry MVS Connection Service sends the call request to the BlackBerry MVS Call Processor over a UDP port number.

10

Feature and Technical Overview

Process flow: Making a call from a BlackBerry device (BlackBerry device initiates)

7.

8. 9. 10. 11. 12. 13. 14. 15.

16. 17. 18. 19.

The BlackBerry MVS Call Processor checks the database and verifies that the call request is from a registered user. The BlackBerry MVS Call Processor creates a message with a DNIS number that the BlackBerry MVS Client uses to complete the call, and sends the message to the BlackBerry MVS Connection Service. The BlackBerry MVS Connection Service sends the message to the BlackBerry Enterprise Server over the LAN using a TCP connection. The BlackBerry Enterprise Server compresses and encrypts the message, and sends it to the wireless network over port 3101. The BlackBerry device sends a delivery confirmation to the BlackBerry Enterprise Server. The BlackBerry MVS Client calls the DNIS number and sends the call to the PBX over the PSTN. The PBX sends the call to the media gateway. The media gateway converts the call to a SIP call, and sends the SIP call to the BlackBerry MVS Session Manager over the LAN. The BlackBerry MVS Session Manager sends the SIP call to the BlackBerry MVS Call Processor over a UDP port number or TCP connection. The BlackBerry MVS Call Processor verifies that the DNIS number and ANI in the SIP call are the same as the DNIS number and ANI from the original outgoing call request. The BlackBerry MVS Call Processor retrieves the destination extension number from the call request and creates a SIP call to dial the destination extension number. The BlackBerry MVS Call Processor sends the SIP call to the BlackBerry MVS Session Manager. The BlackBerry MVS Session Manager sends the SIP call to the media gateway over the LAN. The media gateway converts the SIP call to ISDN, and sends the call to the PBX. The PBX sends the call to the destination extension number. The recipient answers the call and voice communication can occur.

11

Feature and Technical Overview

Process flow: Making a call from a BlackBerry device (PBX initiates)

Process flow: Making a call from a BlackBerry device (PBX initiates)

This process flow applies to a user who makes a call from a BlackBerry device and the PBX starts the call. 1. 2. 3. 4. 5. 6. 7. A BlackBerry Mobile Voice System user makes a call from a BlackBerry device to another extension within the user's organization. The BlackBerry MVS Client starts an outgoing call request, which includes the destination extension number. The BlackBerry device compresses and encrypts the call request, and sends it to the wireless network over port 3101. The wireless network sends the call request to the BlackBerry Enterprise Server. The BlackBerry Enterprise Server decrypts and decompresses the call request, and sends it to the BlackBerry MVS Connection Service over the LAN using a TCP connection. The BlackBerry MVS Connection Service sends the call request to the BlackBerry MVS Call Processor over a UDP port number. The BlackBerry MVS Call Processor checks the database and verifies that the call request is from a registered user. The BlackBerry MVS Call Processor creates a message with an ANI from the pool of ANI numbers and sends the message to the BlackBerry MVS Connection Service. The BlackBerry MVS Connection Service sends the message to the BlackBerry Enterprise Server over the LAN using a TCP connection. The BlackBerry Enterprise Server compresses and encrypts the message, and sends it to the wireless network over port 3101.

8. 9.

12

Feature and Technical Overview

Process flow: Making a call from a BlackBerry device (PBX initiates)

10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21.

22. 23. 24. 25.

The wireless network sends the call request to the BlackBerry device. The BlackBerry device sends a delivery confirmation to the BlackBerry Enterprise Server. The BlackBerry Enterprise Server sends the delivery confirmation to the BlackBerry MVS Connection Service over the LAN. The BlackBerry MVS Connection Service sends the delivery confirmation to the BlackBerry MVS Call Processor over a UDP port number. The BlackBerry MVS Call Processor creates a SIP call to dial the BlackBerry device and sends the SIP call to the BlackBerry MVS Session Manager. The BlackBerry MVS Session Manager sends the SIP call to the media gateway over the LAN. The media gateway converts the SIP call to ISDN, and sends the call to the PBX. The PBX sends the call to the BlackBerry device. The BlackBerry device verifies that the ANI is the same as the ANI from the original message and sends an acknowledgment to the PBX over the PSTN using DTMF codes. The BlackBerry device plays a ring tone to the user. The PBX sends the DTMF codes to the media gateway. The media gateway converts the DTMF codes to an RTP packet, and sends the RTP packet to the BlackBerry MVS Call Processor over the LAN. The BlackBerry MVS Call Processor recognizes the acknowledgment, retrieves the destination extension number from the original call request, and creates a SIP call to dial the destination extension number. The BlackBerry MVS Call Processor sends the SIP call to the BlackBerry MVS Session Manager. The BlackBerry MVS Session Manager sends the SIP call to the media gateway over the LAN. The media gateway converts the SIP call to ISDN, and sends the call to the PBX. The PBX sends the call to the destination extension number. The recipient answers the call and voice communication can occur.

13

Feature and Technical Overview

Process flow: Making a call from a mobile phone

Process flow: Making a call from a mobile phone

1. 2. 3. 4. 5.

A BlackBerry Mobile Voice System user calls the mobile access number from a mobile phone. The mobile phone sends the call to the PBX over the PSTN. The PBX sends the call to the media gateway. The media gateway converts the call to a SIP call, and sends the call to the BlackBerry MVS Session Manager. The BlackBerry MVS Session Manager sends the SIP call to the BlackBerry MVS Call Processor over a UDP port number or TCP connection. 6. The BlackBerry MVS Call Processor checks the database and verifies that the DNIS number is the mobile access number. The BlackBerry MVS Call Processor verifies that the ANI is from a phone number that is associated to a registered user. The BlackBerry MVS Call Processor sends a jingle and dial tone to the user's mobile phone. 7. The user dials an extension within the organization and presses the number sign (#) key on the mobile phone. 8. The mobile phone sends the call to the PBX over the PSTN. 9. The PBX sends the call to the media gateway. 10. The media gateway converts the call to a SIP call, and sends the SIP call to the BlackBerry MVS Server over the LAN. 11. The BlackBerry MVS Session Manager sends the SIP call to the BlackBerry MVS Call Processor. 12. The BlackBerry MVS Call Processor creates another SIP call to dial the destination extension number. The BlackBerry MVS Call Processor sends the SIP call to the BlackBerry MVS Session Manager.

14

Feature and Technical Overview

Process flow: Making a call to an external phone number

13. 14. 15. 16.

The BlackBerry MVS Session Manager sends the SIP call to the media gateway over the LAN. The media gateway converts the SIP call to ISDN, and sends the call to the PBX. The PBX sends the call to the destination extension number. The recipient answers the call and voice communication can occur.

Process flow: Making a call to an external phone number

This process flow applies to a user who makes a call from a BlackBerry device and the BlackBerry device starts the call. 1. 2. 3. 4. 5. 6. 7. A BlackBerry Mobile Voice System user makes a call from a BlackBerry device to a phone number that is external to the user's organization. The BlackBerry MVS Client starts an outgoing call request, which identifies the user and includes the destination extension number. The BlackBerry device compresses and encrypts the call request, and sends it to the BlackBerry device over the wireless network. The wireless network sends the call request to the BlackBerry Enterprise Server. The BlackBerry Enterprise Server decrypts and decompresses the call request, and sends it to the BlackBerry MVS Connection Service over the LAN using a TCP connection. The BlackBerry MVS Connection Service sends the call request to the BlackBerry MVS Call Processor over a UDP port number. The BlackBerry MVS Call Processor checks the database and verifies that the call request is from a registered user. The BlackBerry MVS Call Processor creates a message with a DNIS number that the BlackBerry MVS Client uses to complete the call, and sends the message to the BlackBerry MVS Connection Service.

15

Feature and Technical Overview

Process flow: Making a call to an external phone number

8. 9. 10. 11. 12. 13. 14. 15.

16. 17. 18. 19.

The BlackBerry MVS Connection Service sends the message to the BlackBerry Enterprise Server over the LAN using a TCP connection. The BlackBerry Enterprise Server compresses and encrypts the message, and sends it to the wireless network over port 3101. The BlackBerry device sends a delivery confirmation to the BlackBerry Enterprise Server, and decrypts and decompresses the message. The BlackBerry MVS Client calls the DNIS number, and sends the call to the PBX over the PSTN. The PBX sends the call to the media gateway. The media gateway converts the call to a SIP call, and sends the SIP call to the BlackBerry MVS Session Manager over the LAN. The BlackBerry MVS Session Manager sends the SIP call to the BlackBerry MVS Call Processor over a UDP port number or TCP connection. The BlackBerry MVS Call Processor verifies that the DNIS number and ANI in the message are the same as the DNIS number and ANI from the original outgoing call request. If they are the same, the BlackBerry MVS Call Processor retrieves the destination phone number from the original message and creates a SIP call to dial the destination phone number. The BlackBerry MVS Call Processor sends the SIP call to the BlackBerry MVS Session Manager. The BlackBerry MVS Session Manager sends the SIP call to the media gateway over the LAN. The media gateway converts the SIP call to ISDN, and sends the call to the PBX. The PBX sends the call to the destination phone number over the PSTN. The recipient answers the call and voice communication occurs.

16

Feature and Technical Overview

Process flow: Receiving a call on a BlackBerry device

Process flow: Receiving a call on a BlackBerry device

This process flow applies to a user who receives a call on a BlackBerry device and the BlackBerry Mobile Voice System is configured to have the PBX start the call. 1. 2. 3. 4. 5. A caller within an organization dials the extension of a BlackBerry MVS user. The PBX sends the call to the media gateway. The media gateway converts the call to a SIP call and sends it to the BlackBerry MVS Session Manager over the LAN. The BlackBerry MVS Session Manager sends the SIP call to the BlackBerry MVS Call Processor over a UDP port number or TCP connection. The BlackBerry MVS Call Processor checks the database and verifies that the DNIS number is associated to a registered user. The BlackBerry MVS Call Processor checks the database for the phone numbers that are associated to the user's accounts and how to start the call with the BlackBerry device. After the BlackBerry MVS Call Processor identifies that the PBX should start calls to the BlackBerry device, the BlackBerry MVS Call Processor creates a message, which includes an ANI from the pool of ANI numbers, and the name and phone number of the caller. The BlackBerry MVS Call Processor sends the message to the BlackBerry MVS Connection Service over a TCP connection. The BlackBerry MVS Connection Service sends the message to the BlackBerry Enterprise Server over a UDP port number.

6.

17

Feature and Technical Overview

Process flow: Transferring a call from a BlackBerry device

7. 8. 9. 10. 11. 12. 13. 14. 15.

The BlackBerry Enterprise Server compresses and encrypts the message, and sends it to the BlackBerry device over the wireless network. The BlackBerry device sends a delivery confirmation to the BlackBerry Enterprise Server, and decrypts and decompresses the message. The BlackBerry MVS Client verifies that the message is from the BlackBerry MVS Server, and sends a confirmation to the BlackBerry MVS Call Processor. The BlackBerry MVS Call Processor creates a SIP call to forward the incoming call to the user. The BlackBerry MVS Call Processor sends the SIP call to the BlackBerry MVS Session Manager. The BlackBerry MVS Session Manager sends the SIP call to the media gateway over the LAN. The media gateway converts the SIP call to ISDN, and sends the call to the PBX. The PBX sends the call to the BlackBerry device. The BlackBerry MVS Client verifies that the ANI is the same as the ANI from the original message, and displays the caller name and phone number from the message to the user. The user answers the call and voice communication occurs.

Process flow: Transferring a call from a BlackBerry device

1. 2.

A BlackBerry Mobile Voice System user dials the extension of Party B to transfer an active call with Party A using a BlackBerry device. The BlackBerry MVS Client sends the transfer code and destination phone number of Party B to the PBX over the PSTN using DTMF codes.

18

Feature and Technical Overview

Process flow: Moving a call from a BlackBerry device to a desk phone

3. 4.

The PBX sends the DTMF codes to the media gateway. The media gateway converts the DTMF codes to an RTP packet, and sends the RTP packet to the BlackBerry MVS Server over the LAN. 5. The BlackBerry MVS Call Processor recognizes the transfer code, places Party A on hold, and creates a SIP call to dial the destination phone number. The BlackBerry MVS Call Processor sends the SIP call to the BlackBerry MVS Session Manager. 6. The BlackBerry MVS Session Manager sends the SIP call to the media gateway over the LAN. 7. The media gateway converts the SIP call to ISDN, and sends the call to the PBX. 8. The PBX sends the call to the destination extension number. 9. Party B answers the call, speaks to the user, and accepts the call from Party A. 10. The user completes the transfer on the BlackBerry device. 11. BlackBerry MVS Server ends the call with the BlackBerry device, and Party A can now speak with Party B.

Process flow: Moving a call from a BlackBerry device to a desk phone

1. 2. 3. 4. 5.

A BlackBerry Mobile Voice System user selects the option on a BlackBerry device to move a call to a desk phone. The BlackBerry MVS Client sends the move code to the PBX over the PSTN using DTMF codes. The PBX sends the DTMF codes to the media gateway. The media gateway converts the DTMF codes to an RTP packet, and sends the RTP packet to the BlackBerry MVS Server over the LAN. The BlackBerry MVS Call Processor recognizes the move code, checks the database for the user's desk phone number, and creates a SIP call to dial the desk phone number. The BlackBerry MVS Call Processor sends the SIP call to the BlackBerry MVS Session Manager.

19

Feature and Technical Overview

Process flow: Adding another party to a call on a BlackBerry device

6. 7. 8. 9. 10.

The BlackBerry MVS Session Manager sends the SIP call to the media gateway over the LAN. The media gateway converts the SIP call to ISDN, and sends the call to the PBX. The PBX sends the call to the desk phone. The user answers the call on the desk phone. The BlackBerry MVS Client ends the call on the BlackBerry device, and the user can continue the call on the desk phone.

Process flow: Adding another party to a call on a BlackBerry device

1. 2. 3. 4. 5.

6. 7. 8.

A BlackBerry Mobile Voice System user dials the extension of Party B to conference the party into an active call with Party A using a BlackBerry device. The BlackBerry MVS Client sends the code for the ad hoc conference and the destination extension number of Party B to the PBX over the PSTN using DTMF codes. The PBX sends the DTMF codes to the media gateway. The media gateway converts the DTMF codes to an RTP packet, and sends the RTP packet to the BlackBerry MVS Call Processor over the LAN. The BlackBerry MVS Call Processor recognizes the code for the ad hoc conference, places Party A on hold, and creates a SIP call to dial the destination extension number of Party B. The BlackBerry MVS Call Processor sends the SIP call to the BlackBerry MVS Session Manager. The BlackBerry MVS Session Manager sends the SIP call to the media gateway over the LAN. The media gateway converts the SIP call to ISDN, and sends the call to the PBX. The PBX sends the call to the destination extension number.

20

Feature and Technical Overview

Process flow: Adding another party to a call on a BlackBerry device

9. Party B answers the call and speaks to the user. 10. The user completes the conference on the BlackBerry device, and all parties can speak with each other.

21

Feature and Technical Overview

Requirements

Requirements
System requirements: BlackBerry MVS
Item hardware Requirement

operating system database management system BlackBerry Enterprise Server

rack-mount chassis with redundant power supplies Intel Xeon Dual Core 3.0 GHz (or better) processor 4 GB RAM two or more 146 GB (or more) hot-swap drives that are configured as RAID 1 or better: logical drive with 60 GB primary partition, and an extended partition that spans the remainder of the drives capacity (configured as the C: drive and D: drive) DVD drive 24x or faster dual on-board NIC one available PCI-X slot Intel PRO/1000 MT Dual Port Server Adapter (P/N: PWLA8492MT) for voice network traffic

Windows Server 2003 R2 SP2 Standard or Enterprise Microsoft SQL Server 2005 SP2 Standard or Enterprise enabled for both Windows authentication and Microsoft SQL Server authentication BlackBerry Enterprise Server for IBM Lotus Domino version 4.1 SP5 or later BlackBerry Enterprise Server for Microsoft Exchange version 4.1 SP5 or later BlackBerry Enterprise Server for Novell GroupWise version 4.1 SP5 or later

browser notification messages BlackBerry device

Windows Internet Explorer version 6.0 or 7.0 with JavaScript turned on SMTP address for email notification messages Any of the following BlackBerry devices: BlackBerry 8700 Series BlackBerry 8800 Series BlackBerry Bold 9000 smartphone BlackBerry Curve 8300 Series BlackBerry Curve 8900 smartphone BlackBerry Pearl 8100 Series

22

Feature and Technical Overview

System requirements: Network

Item

Requirement BlackBerry Pearl 8220 smartphone BlackBerry Storm Series data voice or phone

BlackBerry Device Software wireless service plan PDF file viewer other suggested third-party software

BlackBerry Device Software version 4.2.1 or later

Adobe Reader version 5.0 or later Wireshark network protocol analyzer Antivirus software

System requirements: Network

Item data network Requirement To support data traffic between the BlackBerry MVS Server and your organization's LAN, the following conditions: voice network one or more Ethernet ports, and one or more static IP addresses to support the Ethernet connection between the BlackBerry MVS Server and LAN one Ethernet port and one static IP address to support the Ethernet connection between the media gateway and LAN port numbers opened to maintain a connection between the BlackBerry MVS Server and BlackBerry Enterprise Server

To support voice traffic between the BlackBerry MVS Server and media gateway, the following conditions: dedicated voice-quality switch or VLAN with QoS one Ethernet port and one static IP address to support the Ethernet connection between the BlackBerry MVS Server and voice LAN one Ethernet port and one static IP address to support the Ethernet connection between the media gateway and voice LAN

To meet these requirements, you must configure IEEE 802.1p and IEEE 802.1Q parameters for the VLAN.

23

Feature and Technical Overview

System requirements: PBX

System requirements: PBX

Item PBX environment Requirement PBX hardware PBX that your organization's media gateway supports DSP resources to support call processing and voice traffic on the PBX voice network T1/E1 ISDN-PRI trunks to support the anticipated voice traffic between the PBX and media gateway QSIG T1/E1 ISDN-PRI tie lines between the media gateway and PBX use of Coordinated Dial Plan, Universal Dial Plan, or similar routing DS1 card that supports T1/E1 ISDN-PRI CAT5e cabling or better to connect trunk lines If you use multiple spans, each span must have connection points to connect the PBX to the media gateway

PBX licensing PRI provisioning

capacity and licensing for ISDN, trunks, stations, and QSIG Support for the following provisioning: ISDN-PRI interface B8ZS/ESF DS1 signaling that can transmit at 1.544 Mbps for T1 carriers or HDB3 DS1 signaling that can transmit at 2.048 Mbps for E1 carriers two-way B-channels one D-channel for each T1/E1 span (NFAS is not supported) trunk-to-trunk transfer or tandem switching QSIG PBX that is capable of sending and receiving a caller ID of up to 14 digits PSTN trunks (local, long distance, and international) that are capable of sending and receiving a caller ID of up to 14 digits

caller ID

You might be required to reprovision your organization's PRI spans. DID one DID per user five DID numbers per 100 users for ANI and DNIS pool numbers one DID for the BlackBerry Mobile Voice System command number one DID number for the mobile access number

24

Feature and Technical Overview

System requirements: Media gateway

Item voice circuit and PBX capacity

Requirement one DID number for the conference bridge access number (optional) Prior to installing Blackberry MVS, verify that there is adequate local and long distance capacity on carrier circuits connected to your PBX. To support Blackberry MVS, your carrier circuits should have adequate capacity for one additional outbound call per MVS user. Typical capacity for the PBX to Media Gateway T1s is one QSIG PRI for every one hundred users. Ensure that you have adequate ports for the trunk groups that will be created as well as slot space for each T1/DS1 card.

System requirements: Media gateway

Item media gateway Requirement One or more of the following media gateways: media gateway environment Dialogic 2000 Media Gateway Series NET VX1200 ISDN-PRI tie line that is configured to use QSIG SIP interface that supports G.711 (A-law or Mu-law) Ethernet administration port ability to send and receive an ANI of up to 14 digits dedicated VLAN, LAN, or QoS prioritization within the voice-enabled data network

System requirements: Voice mail integration

To permit the BlackBerry MVS Server to access your organization's voice mail system, the voice mail system must support dial strings for voice mail deposit and retrieval.

25

Feature and Technical Overview

Glossary

Glossary
ANI Automatic Number Identification B-channel bearer channel BlackBerry MVS BlackBerry Mobile Voice System CAT5e category 5e D-channel data channel DID Direct Inward Dial DNIS Dialed Number Identification Service DS1 digital signal 1 DSP digital signal processing DTMF Dual Tone Multiple-frequency IEEE Institute of Electrical and Electronics Engineers IP Internet Protocol ISDN Integrated Services Digital Network ISDN-PRI Integrated Services Digital Network Primary Rate Interface

26

Feature and Technical Overview

Glossary

LAN local area network messaging server A messaging server sends and processes messages and provides collaboration services, such as updating and communicating calendar and address book information. mobile access number A mobile access number is a phone number that BlackBerry Mobile Voice System users can call to access features of the BlackBerry MVS from any phone. NFAS Non-Facility Associated Signaling NIC network interface card PBX Private Branch Exchange PCI-X Peripheral Component Interconnect Extended PDF Portable Document Format PRI Primary Rate Interface PSTN Public Switched Telephone Network QoS Quality of Service QSIG Q Signaling RAID redundant array of independent (or inexpensive) disks RTP Real-time Transport Protocol SIP

27

Feature and Technical Overview

Glossary

Session Initiation Protocol SMTP Simple Mail Transfer Protocol TCP Transmission Control Protocol UDP User Datagram Protocol VLAN virtual local area network

28

Feature and Technical Overview

Provide feedback

Provide feedback
To provide feedback on this deliverable, visit www.blackberry.com/docsfeedback.

29

Feature and Technical Overview

Legal notice

Legal notice

2010 Research In Motion Limited. All rights reserved. BlackBerry, RIM, Research In Motion, SureType, SurePress and related trademarks, 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. Adobe and Reader are trademarks of Adobe Systems Incorporated. Dialogic is a trademark of Dialogic Corporation. IBM, Domino, and Lotus are trademarks of International Business Machines Corporation. IEEE is a trademark of the Institute of Electrical and Electronics Engineers, Inc. Intel and Xeon are trademarks of Intel Corporation. JavaScript is a trademark of Sun Microsystems, Inc. Microsoft, Internet Explorer, SQL Server, Windows, and Windows Server are trademarks of Microsoft Corporation. NET VX1200 is a trademark of Network Equipment Technologies, Inc. Novell and GroupWise are trademarks of Novell, Inc. 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 web sites (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, NONINFRINGEMENT, 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.

30

Feature and Technical Overview

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.

31

Feature and Technical Overview

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 Centrum House 36 Station Road Egham, Surrey TW20 9LF United Kingdom Published in Canada

32