Blackberry Release Notes User Manual

BlackBerry Mobile Voice System

Version: 5.2

Release Notes

SWD-1944926-0629091605-001

Contents

1 Functional changes........................................................................................................................................... 2

2 Using the Cisco Options Package (COP) file...................................................................................................... 4

Install the COP file for the BlackBerry MVS...................................................................................................... 4

Upgrade existing BlackBerry MVS users to use a new COP file........................................................................ 5

Update BlackBerry MVS users in the MVS Console to use Voice over Wi-Fi calling......................................... 7

3 Upgrading the BlackBerry MVS software.......................................................................................................... 8

Upgrade from an earlier version of the BlackBerry MVS software................................................................... 8

4 Configure a communication password............................................................................................................. 11

5 Fixed issues....................................................................................................................................................... 12

BlackBerry MVS Server..................................................................................................................................... 12

BlackBerry MVS Client...................................................................................................................................... 12

6 Known issues.................................................................................................................................................... 14

BlackBerry MVS Server..................................................................................................................................... 14

BlackBerry MVS Client...................................................................................................................................... 15

7 Legal notice....................................................................................................................................................... 19

Release Notes

Functional changes

The following table lists the functional changes for BlackBerry Mobile Voice System 5.2.

Item Description

Call forwarding If the BlackBerry MVS administrator enables call forwarding, a BlackBerry MVS user

can forward incoming BlackBerry MVS calls to an internal extension or an external phone. This feature is not available if your organization routes call through a SIP

gateway. Optional ANI Numbers Available for Identifying BlackBerry MVS Calls list

Roaming status and network name in CDR reports BlackBerry MVS Only Calling update Validation of caller identification for PBXinitiated calls

The device can fall back to use the no data coverage number to make outgoing calls

If you are configuring your organization's BlackBerry MVS for PBX-initiated calling, you

can define optional ANI numbers. Some wireless networks that allow roaming might

not support the additional calling party number field. You specify additional numbers

in this list for PBX trunks that route calls to BlackBerry devices. The BlackBerry MVS

Client uses a combination of the caller identification number and the numbers in the

Optional ANI numbers list to identify BlackBerry MVS calls.

When you generate a CDR report you can now see if users were roaming and the name

of the network that they were on.

You can turn off MVS Only Calling for incoming or outgoing calls when a user is roaming

or is not roaming.

During normal call setup some wireless networks might alter the number in the calling

party number field of the INVITE. If the BlackBerry MVS Client does not recognize the

calling party number in a PBX-initiated call it will reject the call because it is expecting

the calling party number to be the Caller Identification Number that you have set in

the MVS Console. To avoid this, you can permit the BlackBerry MVS Client to ignore

the entry in the calling party number field of the INVITE. When you do this, the

BlackBerry MVS Client considers the call to be from the PBX and accepts the call. When

this feature is enabled, users cannot move calls from Voice over Wi-Fi to Voice over

Mobile or move calls from Voice over Mobile to Voice over Wi-Fi.

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. When the PBX takes too long to initiate an outgoing call, the BlackBerry device

will use the no data coverage number to initiate the call. This option is enabled by

default, however your organization might not need to use it for several reasons:

• Your organization's data calls set up successfully

• You do not want to disable 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

Release Notes

Item Description

Support for Cisco Unified Communications

BlackBerry MVS supports routing calls through the Cisco Unified Communications

Manager 8.6.2. Manager 8.6.2 Support for BlackBerry

7.1

BlackBerry MVS now supports BlackBerry 7.1 for the following smartphones:

• BlackBerry Curve 9350

• BlackBerry Curve 9360

• BlackBerry Curve 9380

• BlackBerry Torch 9810

• BlackBerry Torch 9850

• BlackBerry Torch 9860

• BlackBerry Bold 9790

• BlackBerry Bold 9900

• BlackBerry Bold 9930

• Porsche Design P'9981

Functional changes

Release Notes

Using the Cisco Options Package (COP) file

The BlackBerry Mobile Voice System COP file is a phone definition file from Cisco that provides native support for BlackBerry MVS devices in the Cisco Unified Communications Manager environment. The BlackBerry MVS is only supported when the BlackBerry MVS COP file is installed.

Installing the COP file requires a restart of all of the nodes in the cluster. Make sure that you schedule any Cisco Unified Communications Manager changes during a maintenance window.

The following COP files are available for new installs and upgrades:

• cmterm-rim_409_8.6v1-sip.cop.sgn, which uses 6 DLUs, permits your organization's users to make both Voice over Wi-Fi and Voice over Mobile calls.

• cmterm-rim_410_8.6v1-sip.cop.sgn, which uses 3 DLUs, permits your organization's users to make Voice over Mobile calls only.

To download the COP files, visit the Software Download for BlackBerry Mobile Voice System page.

If you have already configured your organization's users for Voice over Mobile calling only and do not want them to use Voice over Wi-Fi calling, you do not have to upgrade the COP file. Users that use a 3 DLU COP file will register successfully with the PBX and the Voice over Wi-Fi options will not be available to them.

If you have already configured your organization's users for Voice over Mobile calling and you want your users to use Voice over Wi-Fi calling, you must perform the following tasks:

• On the Cisco Unified Communications Manager you must install the new cmterm-rim_409_8.6v1-sip.cop.sgn COP file

• On the Cisco Unified Communications Manager you must remove the BlackBerry MVS Client instances that are using the old COP file and add the instances back using the new COP file

• On the BlackBerry MVS you must configure your organization's users for Voice over Wi-Fi calling

Install the COP file for the BlackBerry MVS

1. Upload the digitally-signed BlackBerry Mobile Voice System COP file to an SFTP server.

2. In the Cisco Unified Communications Manager UI, in the Navigation drop-down list , click Cisco Unified OS Administration.

3. Click GO.

4. Log in using the OS or Platform administration account.

5. Click Software Upgrades > Install/Upgrade.

6. In the Source list, select Remote Filesystem.

7. In the Directory field, enter the path to the directory on the SFTP server where you uploaded the BlackBerry MVS COP file.

8. In the Server field, enter the IP address or host name of the SFTP server.

9. In the User Name field, enter the user name for the SFTP sever.

Release Notes

10. In the User Password field, enter the password for the SFTP server.

11. In the Transfer Protocol list, select SFTP.

12. Click Next.

13. In the Options/Upgrades list, select the digitally-signed BlackBerry MVS COP file.

14. Click Next.

15. Verify the MD5 hash value for the digitally-signed BlackBerry MVS COP file against the Cisco website.

16. Click Next.

17. When the BlackBerry MVS COP file installation is finished, restart all Cisco Unified Communications Manager nodes in the cluster, starting with the Publisher server.

Upgrade existing BlackBerry MVS users to use a new COP file

You do not have to perform this procedure if you are installing the BlackBerry Mobile Voice System for the first time.

1. Log in to the Cisco Unified Communications Manager Administration webpage.

2. Navigate to Bulk Administration > Phones > Export Phones > All Details.

3. In the Select the Device Type field, select BlackBerry MVS Client.

4. In the File Name field type a name for the file.

5. Click the Run Immediately option.

6. Click Submit.

7. After the export completes, navigate to Bulk Administration > Upload/Download files and download the file.

8. Save the file with a .csv file name extension.

9. Navigate to Bulk Administration > Phones > Phone Template.

10. Create a template for the new BlackBerry MVS Client with Voice over Wi-Fi device type.

11. In the new template, complete the following fields:

• Template Name

• Description

• Device Pool

• Phone Button Template

• Device Security Profile

• SIP Profile

• Required DTMF Reception

12. Click Save.

13. Click Add a new DN.

14. In the Line 1 area, complete the following fields:

• Line Template Name

+ 16 hidden pages