Page 1
BlackBerry Mobile Voice System
Version: 5.0 | Service Pack: 2
Planning Guide
Page 2
SWD-1000192-0414013325-001
Page 3
Contents
1 Overview........................................................................................................................................................... 2
2 Requirements................................................................................................................................................... 3
System requirements: BlackBerry MVS............................................................................................................ 3
System requirements: Telephony environment............................................................................................... 5
System requirements: PBX............................................................................................................................... 6
3 Planning your organization's Wi-Fi infrastructure............................................................................................ 8
Best practice: Planning your organization's Wi-Fi infrastructure..................................................................... 8
4 Planning a BlackBerry MVS installation............................................................................................................ 10
Best Practices: Installing and configuring the BlackBerry MVS......................................................................... 10
5 Configuring call direction.................................................................................................................................. 12
PBX-initiated calling.......................................................................................................................................... 12
BlackBerry device–initiated calling................................................................................................................... 12
6 BlackBerry MVS high availability....................................................................................................................... 13
Support for BlackBerry Enterprise Server failover............................................................................................ 14
Support for PBX failover................................................................................................................................... 14
How the BlackBerry MVS determines the health of MVS Session Manager instances..................................... 14
Conditions for failover to a standby MVS Session Manager............................................................................. 14
Scenario: What happens after the active MVS Session Manager stops responding........................................ 15
7 Glossary............................................................................................................................................................ 16
8 Provide feedback.............................................................................................................................................. 18
9 Legal notice....................................................................................................................................................... 19
Page 4
Planning Guide
Overview
Overview
The BlackBerry® Mobile Voice System integrates your organization's PBX phone system 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 organization’s 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 phone system
• 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
1
2
Page 5
Planning Guide
Requirements
Requirements
System requirements: BlackBerry MVS
Item Requirement
hardware
operating system Any of the following operating systems:
BlackBerry® Enterprise Server Any of the following BlackBerry® Enterprise Server software:
data management system Any of the following data management systems:
browser Any of the following browsers:
your organization's telephony
environment
BlackBerry device Any of the following devices:
• two Intel® Xeon® 2.0 GHz processors
• 4 GB RAM
• two drives that are configured as RAID 1 or better
For a computer that is running only the MVS Console, you require only one
2.0 GHz processor, and 2GB RAM.
• Windows Server® 2003 R2 SP2 Standard (32 bit or 64 bit)
• Windows Server 2003 R2 SP2 Enterprise (32 bit or 64 bit)
• Windows Server 2008 R2
• BlackBerry® Enterprise Server 4.1 SP7 or later for Microsoft® Exchange
• BlackBerry Enterprise Server 5.0 or later for Microsoft Exchange
• BlackBerry® Enterprise Server 4.1 SP7 or later for IBM® Lotus®
Domino®
• BlackBerry Enterprise Server 5.0 or later for IBM Lotus Domino
• BlackBerry® Enterprise Server 4.1 SP7 or later for Novell® GroupWise®
• BlackBerry Enterprise Server 5.0 or later for Novell GroupWise
• Microsoft® SQL Server® 2000 with named pipes and TCP/IP network
protocols turned on
• Microsoft SQL Server 2005 SP2 with named pipes and TCP/IP network
protocols turned on
• Microsoft SQL Server 2008 with named pipes and TCP/IP network
protocols turned on
• Windows® Internet Explorer® 7
• Windows Internet Explorer 8 with JavaScript® turned on
• Mozilla® Firefox® 3.5 or later
PBX vendor that is BlackBerry MVS platform-compliant
2
• BlackBerry® Pearl™ 8100 Series
3
Page 6
Planning Guide
System requirements: BlackBerry MVS
Item Requirement
• BlackBerry® Pearl™ 8220 smartphone
• BlackBerry® Curve™ 8300 smartphone
• BlackBerry® Curve™ 8310 smartphone
• BlackBerry® Curve™ 8320 smartphone
• BlackBerry® Curve™ 8330 smartphone
• BlackBerry® Curve™ 8520 smartphone
• BlackBerry® Curve™ 8530 smartphone
• BlackBerry® 8700 Series
• BlackBerry® 8800 smartphone
• BlackBerry® 8820 smartphone
• BlackBerry® Curve™ 8900 smartphone
• BlackBerry® Curve™ 8910 smartphone
• BlackBerry® Curve™ 8980 smartphone
• BlackBerry® Bold™ 9000 smartphone
• BlackBerry® Pearl™ 9100 smartphone
• BlackBerry® Curve™ 9300 smartphone
• BlackBerry® Curve™ 9330 smartphone
• BlackBerry® Storm™ 9500 smartphone
• BlackBerry® Storm™ 9530 smartphone
• BlackBerry® Storm2™ Series
• BlackBerry® Tour™ 9630 smartphone
• BlackBerry® Bold™ 9650 smartphone
• BlackBerry® Style™ 9670 smartphone
• BlackBerry® Bold™ 9700 smartphone
• BlackBerry® Bold™ 9780
• BlackBerry® Torch™ 9800 smartphone
BlackBerry® Device Software Any of the following BlackBerry Device Software versions:
• BlackBerry Device Software 4.5 or later for devices that operate on
GSM® networks (Voice over Mobile support only)
• BlackBerry Device Software 4.7.1 or later for devices that operate on
CDMA networks (Voice over Mobile support only)
• BlackBerry Device Software 5.0 or later for Voice over Wi-Fi® support
and Voice over Mobile support
• BlackBerry 6 for the BlackBerry Torch 9800
wireless service plan Any of the following features:
• data
• voice (not required if you use only Wi-Fi to make and take BlackBerry
MVS calls)
4
Page 7
Planning Guide
Item Requirement
• caller ID
virtual environment (if applicable) Any of the following virtual environment software:
• VMware® ESX® Server 3.5.0
• VMware ESX Server 4.x
PDF file viewer Adobe® Reader® 5.0 or later
System requirements: Telephony environment
System requirements: Telephony environment
Item Requirement
DTMF Your organization's telephony environment must be able to perform the following
actions:
• detect and intercept DTMF tones from the cellular 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
ANI number (Calling party)
DID/DDI number (Called
party)
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, in-band media, H.323).
• The Calling Line ID of a received call identifies the BlackBerry MVS call that is
presented to the device. The Calling Line ID must be configured in the MVS
Console to match the ANI that your organization's telephony environment plans
to use for all BlackBerry MVS calls.
• Any BlackBerry MVS calls that a device makes must use the ANI that you
configured in your organization's telephony environment so that the called party
can see the caller ID that is configured for the BlackBerry MVS user.
• 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 device–
initiated calling, you must configure a DID/DDI number in your organization's
telephony environment. You configure the DID/DDI number in the MVS Console
for each MVS Session Manager. The DID/DDI number is used to provision the
user accounts that you configured for the device.
5
Page 8
Planning Guide
Item Requirement
• In the class of service, make sure that you choose BlackBerry Smartphone > PBX
for users that you want to use BlackBerry device–initiated 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 telephony
connector that has been configured between the telephony environment and
the BlackBerry MVS.
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.
System requirements: PBX
System requirements: PBX
Item Requirement
KPML The PBX must support KPML for the exchange of DTMF tones between the PBX
and the BlackBerry® Mobile Voice System.
support for BlackBerry devices The device must be an endpoint for the PBX.
G.729 is supported by BlackBerry MVS 5.0 and later. It is supported on all devices
except for the BlackBerry® Bold™ 9000 device and devices that operate on CDMA
networks.
SIP line The BlackBerry MVS requires a SIP line be connected to the PBX so that the PBX
can establish calls to devices.
If you configure the BlackBerry MVS for high availability, you must configure a
SIP line on each MVS Session Manager.
SIP trunk The BlackBerry MVS requires that a SIP trunk be connected 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 MVS
Session Manager.
If you configure the BlackBerry MVS for high availability, you must configure a
SIP trunk on each MVS Session Manager.
call routing patterns for internal
numbers and external numbers
6
The phone numbers that the BlackBerry MVS sends to the PBX are E.164
formatted numbers and 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
Page 9
Planning Guide
System requirements: PBX
Item Requirement
• 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
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 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 MVS Session Manager that is associated with the DID/
DDI number. For example, if the DID/DDI number that you configure in the MVS
Console for the MVS Session Manager is +15195550100, for any device-initiated
calls that arrive at the PBX using a DID/DDI number of +15195550100, the PBX
must route the calls to the MVS Session Manager that is associated with the DID/
DDI number of +15195550100.
You require one DID/DDI number for each MVS Session Manager in your
organization’s environment.
7
Page 10
Planning Guide
Planning your organization's Wi-Fi infrastructure
Planning your organization's Wi-Fi
3
infrastructure
If your organization plans to use Wi-Fi® enabled BlackBerry® devices for making and taking BlackBerry® Mobile Voice
System calls, you must make sure that your Wi-Fi infrastructure can support Voice over Wi-Fi calls. During the planning
process, you should collaborate with your organization's Wi-Fi infrastructure vendor to make sure that the Wi-Fi
infrastructure is designed and configured to support Voice over Wi-Fi calls.
To make sure that your organization's Wi-Fi infrastructure can support Voice over Wi-Fi calls, you should use
BlackBerry devices to perform an in-depth site survey. For more information, visit www.blackberry.com/support to
read article KB13299. The results of the survey should permit you to perform the following tasks:
• design and configure a Wi-Fi controller-based architecture
• identify the type of authentication and level of encryption that your organization requires
• configure a QoS implementation
• determine the expected Wi-Fi coverage and capacity boundaries of the access points
• determine the capacity of your organization's Wi-Fi infrastructure. Make sure that you account for the expected
usage for both BlackBerry MVS users and individuals who use Wi-Fi technology on their laptop computers.
• create documentation for your organization's users to help them configure their devices to connect to Wi-Fi
networks and make Voice over Wi-Fi calls
Best practice: Planning your organization's Wi-Fi infrastructure
The following guidelines are intended to help you design a Wi-Fi infrastructure that permits BlackBerry devices to
connect to an access point that has a medium-to-high data rate. When the data rate of the access point is too low
or the signal strength of the access point is too weak, the device should roam to an access point with a higher data
rate or a stronger signal strength. When designing your organization's Wi-Fi infrastructure, you should consider the
following guidelines:
• Establish a minimum signal strength level of -65 dBm in the planned coverage area.
• Establish a minimum SNR of 25 dB in the planned coverage area.
• When roaming in the planned coverage area, make sure that it takes no longer than 50 milliseconds to perform
an access point to access point handoff.
• Eliminate any 802.11b-only devices and the associated data rates. By eliminating the 802.11b-only devices,
802.11g devices do not need to enter protection mode, which reduces the maximum data throughput of the
devices.
Using Wi-Fi enabled BlackBerry devices for making and taking BlackBerry MVS calls from a home office or a hotspot
is unpredictable because of the instability of those types of networks and cannot be expected to be as reliable as
when the user is in a controlled environment. If your organization's users make Voice over Wi-Fi calls from a home
office or hotspot, you must make sure that the integrated VPN client on their BlackBerry devices is configured for a
highly secure connection to your organization's network through the Internet.
8
Page 11
Planning Guide
Best practice: Planning your organization's Wi-Fi infrastructure
For more information about planning your organization's Wi-Fi infrastructure, visit http://na.blackberry.com/eng/
ataglance/networks to see the Considerations for Planning and Deploying a Wireless LAN document.
9
Page 12
Planning Guide
Planning a BlackBerry MVS installation
Planning a BlackBerry MVS installation
You can install the MVS Console and MVS Session Manager on the computer that hosts the BlackBerry® Enterprise
Server or on a separate computer. During the first BlackBerry® Mobile Voice System installation process, you must
install both BlackBerry MVS components and provide the IP address, name and port number for your organization's
BlackBerry Configuration Database.
If your organization's environment requires high availability, you must have three computers available to host two
MVS Session Manager instances and a MVS Console. You can use high availability to provide minimum downtime for
BlackBerry MVS users if one of your organization's MVS Session Manager instances stops responding or requires
maintenance. The failover process is automatic, but you can perform a manual failover to perform scheduled
maintenance.
If your organization's environment includes multiple BlackBerry Enterprise Server instances, you can configure one
MVS Session Manager for each BlackBerry Enterprise Server, or you can associate all BlackBerry Enterprise Server
instances with one MVS Session Manager. You can install only one MVS Session Manager on a computer. If your
organization's users are associated with different PBXs, you must configure multiple telephony connectors, which
provide connectivity to each PBX. You require only one MVS Console to manage the BlackBerry MVS in each BlackBerry
Domain.
If your organization's environment already includes one MVS Console, during the BlackBerry MVS installation process,
you must install the MVS Session Manager only. You must also provide the host name or IP address, and the port
number for your organization's MVS Console.
To add another MVS Session Manager to your organization's environment, you must load security key stores that
the BlackBerry MVS generates during the installation process.
4
During the BlackBerry MVS installation process, you might be required to involve the administrators of your
organization's PBX, voice mail system, LAN, security network, or BlackBerry Enterprise Server.
Best Practices: Installing and configuring the BlackBerry MVS
Best practices for installing BlackBerry MVS components
• The first time that you install the BlackBerry® Mobile Voice System software and associate it with a BlackBerry
Configuration Database, you must install both the MVS Session Manager and MVS Console. You can install the
components on the same computer or on separate computers.
• You can install the MVS Session Manager and MVS Console on dedicated physical hardware, or on a dedicated
virtual computer, or on the computer that hosts the BlackBerry® Enterprise Server. If you plan to install the
BlackBerry MVS components on the computer that hosts the BlackBerry Enterprise Server, your organization
can have no more than 500 users, and the BlackBerry MVS installation cannot be configured for high availability.
• You can install only one MVS Session Manager (which is a Windows® service) for each Windows Server® instance.
• You can install only one MVS Console for each BlackBerry Configuration Database in your organization's
environment.
10
Page 13
Planning Guide
• You can install multiple MVS Session Manager instances with a BlackBerry Configuration Database if you
configure the MVS Session Manager instances to use a single MVS Console.
Best Practices: Installing and configuring the BlackBerry MVS
Best practices for testing network ping time
• During times of high network use, the maximum time that a network ping can take to travel from the BlackBerry
MVS Server to the BlackBerry Enterprise Server or BlackBerry Configuration Database and back to the BlackBerry
MVS Server must be 240 milliseconds.
• During times of high network use, the maximum time that a network ping can take to travel from the BlackBerry
MVS Server to the PBX and back to the BlackBerry MVS Server must be 240 milliseconds.
Best practices for installing the BlackBerry MVS on a virtual computer
• If you install the BlackBerry MVS in a virtual environment, the virtual instance should perform as well as a
computer with two Intel® Xeon® 2.0 GHz processors with 4 GB of RAM and two drives that are configured as
RAID 1 or better.
Best practices for configuring the MVS Session Manager
• A MVS Session Manager can support multiple BlackBerry Enterprise Server instances when all BlackBerry
Enterprise Server instances use the same BlackBerry Configuration Database.
• You can associate each BlackBerry Enterprise Server with only one MVS Session Manager.
• A MVS Session Manager can support up to 10,000 BlackBerry MVS users.
• To add more BlackBerry MVS users, you can install additional MVS Session Manager instances. You must
associate each additional MVS Session Manager with at least one BlackBerry Enterprise Server that is not already
associated with another MVS Session Manager.
• If you configure BlackBerry device–initiated calling, you must configure a unique DID/DDI number for each MVS
Session Manager in your organization’s environment. You must also configure your organization's call routing
patterns so that the PBX can route the device-initiated calls to the MVS Session Manager that is associated with
the DID/DDI number.
Best practices for configuring the BlackBerry MVS for high availability
• When you configure the BlackBerry MVS for high availability, you install the MVS Console, the active MVS Session
Manager, and the standby MVS Session Manager on different computers in the same BlackBerry Domain. Both
MVS Session Manager instances use the same MVS Console and BlackBerry Configuration Database.
Best practices for configuring a telephony connector
• In a MVS Session Manager, you can configure one or more telephony connectors that provide connectivity to
the PBX. All telephony connectors in a MVS Session Manager can support up to 10,000 BlackBerry MVS users.
• You can use multiple telephony connectors to divide your organization's users between distinct nodes of the
PBX. You can configure telephony connectors for nodes of the PBX that exist in the same cluster or in separate
clusters in your organization's phone system.
• In a telephony connector, the value that you configure for the caller ID number must match the last six digits of
the outgoing ANI that you specify in your organization's phone system. If the value that you configure for the
caller ID number has fewer than six digits, that value must be an exact match for the outgoing ANI. If a complete
ANI does not arrive at the device (which might happen during international roaming, for example), the BlackBerry
MVS user might not be able to make or receive BlackBerry MVS calls.
11
Page 14
Planning Guide
Configuring call direction
Configuring call direction
You can configure the BlackBerry® Mobile Voice System to use PBX-initiated calling or BlackBerry device–initiated
calling for incoming calls and outgoing calls.
5
PBX-initiated calling
You can configure the BlackBerry® Mobile Voice System to use PBX-initiated calling. When a BlackBerry device
receives or sends a call request, the BlackBerry MVS sends a call request to the PBX so that the PBX can make a call
to the device. The device verifies that the call is from the BlackBerry MVS, and it either connects the caller to the
BlackBerry MVS user or initiates an outgoing call to the dialed number.
If your organization uses devices that operate on GSM® networks, PBX-initiated calling offers optimal performance
and reliability for BlackBerry MVS calls.
BlackBerry device–initiated calling
You can configure the BlackBerry® Mobile Voice System to use BlackBerry device–initiated calling. When a device
receives or sends a call request, the BlackBerry MVS sends a call request, which includes the DID/DDI number, to the
PBX. The PBX routes the call to the BlackBerry MVS. The BlackBerry MVS answers the call, verifies that the call is from
the device, and either connects the caller to the BlackBerry MVS user or initiates an outgoing call to the dialed number.
If your organization uses devices that operate on CDMA networks, device-initiated calling offers optimal performance
and reliability for BlackBerry MVS calls.
12
Page 15
Planning Guide
BlackBerry MVS high availability
BlackBerry MVS high availability
6
BlackBerry® Mobile Voice System high availability consists of an active MVS Session Manager and a standby MVS
Session Manager. You can use high availability to help provide minimum downtime for BlackBerry MVS users if one
of your organization's MVS Session Manager instances stops responding or requires maintenance. The failover
process is designed to be automatic, but you can perform a manual failover before you perform scheduled
maintenance.
When you configure the BlackBerry MVS for high availability, you install the MVS Console, active MVS Session
Manager, and standby MVS Session Manager on different computers in the same BlackBerry Domain. Both MVS
Session Manager instances use the same MVS Console and BlackBerry Configuration Database.
Both MVS Session Manager instances connect to the MVS Console. The MVS Console periodically checks that the
active MVS Session Manager is healthy. If the health of the active MVS Session Manager falls below the failover
threshold or if the active MVS Session Manager stops responding, the MVS Console promotes the standby MVS
Session Manager.
If any of your organization's users are on BlackBerry MVS calls when the active MVS Session Manager stops
responding, the calls remain active but the users cannot use the features that are typically available to them during
a call. While the active MVS Session Manager fails over, the users cannot send or receive any BlackBerry MVS calls
until the failover process completes.
13
Page 16
Planning Guide
You cannot configure high availability for the MVS Console because you can install only one MVS Console in a
BlackBerry Domain.
To manage your organization's users, if the computer that you installed the MVS Console on stops responding, you
should determine why the MVS Console stopped responding. Alternatively, you can install another MVS Console
instance and connect it to the active and standby MVS Session Manager instances.
Support for BlackBerry Enterprise Server failover
Support for BlackBerry Enterprise Server failover
The BlackBerry® Mobile Voice System supports BlackBerry® Enterprise Server failover. If any of your organization's
users are on BlackBerry MVS calls when the active BlackBerry Enterprise Server stops responding, the calls remain
active, but the users cannot use the features that are typically available to them during a call. The users also cannot
send or receive a second call. While the active BlackBerry Enterprise Server fails over, the users cannot send or receive
any BlackBerry MVS calls until the failover process completes.
Support for PBX failover
The BlackBerry® Mobile Voice System does not support PBX failover. If any of your organization's users are on
BlackBerry MVS calls when the active PBX stops responding, the calls remain active until the BlackBerry device stops
receiving registration messages from the PBX. The users cannot send or receive any new BlackBerry MVS calls until
the PBX is active again or until you associate the affected telephony connector with the standby PBX.
How the BlackBerry MVS determines the health of MVS Session Manager instances
The MVS Console determines the health of the MVS Session Manager instances by monitoring its connection to the
MVS Session Manager instances. If the active MVS Session Manager sends a network ping to the MVS Console at
regular intervals, the MVS Console keeps the MVS Session Manager active. If the active MVS Session Manager does
not send a network ping to the MVS Console every 60 seconds, the MVS Console promotes the standby MVS Session
Manager to be the active MVS Session Manager.
Conditions for failover to a standby MVS Session Manager
Failover from the active MVS Session Manager to the standby MVS Session Manager occurs when the MVS Console
stops receiving network pings from the active MVS Session Manager for 1 minute. If the MVS Console continues to
receive network pings from the standby MVS Session Manager, the MVS Console starts the failover process.
14
Page 17
Planning Guide
Scenario: What happens after the active MVS Session Manager stops responding
Scenario: What happens after the active MVS Session
Manager stops responding
If the active MVS Session Manager stops responding, the response of the MVS Console depends on the health of the
standby MVS Session Manager. If the standby MVS Session Manager is healthy, the MVS Console promotes it to be
the active MVS Session Manager.
The following scenario assumes that the MVS Console is available.
1. The MVS Console determines that the active MVS Session Manager stopped responding, demotes the active
MVS Session Manager, and promotes the standby MVS Session Manager to be the active instance.
2. The active MVS Session Manager connects to the active BlackBerry® Enterprise Server.
3. The active MVS Session Manager registers the BlackBerry devices with the PBX.
4. An error message appears on the MVS Console to indicate that a MVS Session Manager is unhealthy.
You must resolve any issues with the unhealthy MVS Session Manager before the MVS Console can promote it to be
the active instance again.
15
Page 18
Planning Guide
Glossary
Glossary
ANI
Automatic Number Identification
BlackBerry Domain
A BlackBerry Domain consists of the BlackBerry Configuration Database with its users and any BlackBerry®
Enterprise Server instances that connect to it.
BlackBerry MVS
BlackBerry® Mobile Voice System
CDMA
Code Division Multiple Access
DDI
Direct Dial In
DID
Direct Inward Dial
DTMF
Dual Tone Multiple-frequency
GSM
Global System for Mobile Communications®
7
IP
Internet Protocol
KPML
Key Press Markup Language
LAN
local area network
MWI
message waiting indicator
NDD
national direct dialing
PBX
Private Branch Exchange
16
Page 19
Planning Guide
PSTN
Public Switched Telephone Network
RAID
redundant array of independent (or inexpensive) disks
RFC
Request for Comments
SIP
Session Initiation Protocol
TCP/IP
Transmission Control Protocol/Internet Protocol (TCP/IP) is a set of communication protocols that is used to
transmit data over networks, such as the Internet.
VPN
virtual private network
Glossary
17
Page 20
Planning Guide
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.
8
18
Page 21
Planning Guide
Legal notice
Legal notice
©2011 Research In Motion Limited. All rights reserved. BlackBerry®, RIM®, Research In Motion®, 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. GSM and Global System for Mobile
Communications are trademarks of the GSM MOU Association. Intel and Xeon are trademarks of Intel Corporation.
IBM, Domino, and Lotus are trademarks of International Business Machines Corporation. Microsoft, Internet Explorer,
SQL Server, Windows, and Windows Server are trademarks of Microsoft Corporation. Mozilla and Firefox are
trademarks of Mozilla Foundation. Novell and GroupWise are trademarks of Novell, Inc. JavaScript is a trademark of
Oracle America, Inc. VMware and VMware ESX are trademarks 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 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.
9
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.
19
Page 22
Planning Guide
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.
20
Page 23
Planning Guide
Legal notice
Certain features outlined in this documentation require a minimum version of BlackBerry® Enterprise Server,
BlackBerry® Desktop Software, and/or BlackBerry® Device Software.
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
21
Loading...