BlackBerry Mobile Voice System Client fails to register due to missing or incorrect Cisco Options Package file

Article ID: KB28621

Type: Support Content

Last Modified: 12-14-2011

 

Product(s) Affected:

  • BlackBerry MVS for Cisco Integration
CollapseEnvironment
  • BlackBerry® Mobile Voice System 5.x (MVS)
  • Cisco® Unified Communications Manager (UCM)
CollapseOverview

Cisco® requires a Cisco Options Package (COP) file support for BlackBerry® MVS integration with Cisco Unified Communications Manager (CUCM). An incorrect or missing COP file will cause BlackBerry MVS client registration failures. 

The following COP files are available:

  • cmterm-rim_409_8.6v1-sip.cop.sgn, which uses 6 Device Licence Units (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.

Phones that use a 3 DLU COP file will show the phone type as BlackBerry MVS Client, and shall register successfully with the PBX only if the Default Network for BlackBerry MVS Calls is set to Mobile Only. While the phones that use a 6 DLU COP file will show the phone type as BlackBerry MVS Client with voice over Wi-Fi, and shall register successfully with the PBX if the Default Network setting is set to either Wi-Fi or Mobile.

CollapseCause

A missing or incorrect COP file will result in a 485 Ambiguous response from the UCM for a Registration request.

[ Thread-59 ]<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[ Thread-59 ]<<<                            485 Ambiguous                                  <<<
[ Thread-59 ]<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[ Thread-59 ]60c69ac8 SipRegManager::RegClientMsgReceivedEvHandler
[ Thread-59 ]SIP/2.0 485 Ambiguous
[ Thread-59 ]From: <sip:85202@10.xxx.xxx.xxx>;tag=5b6cc590-b5baf0a-13c4-50029-b804-6b9f3adc-b804
[ Thread-59 ]To: <sip:85202@10.10.xxx.xxx.xxx>;tag=276306942
[ Thread-59 ]Call-ID:
af222715fac0f75108e64b68ce65fd62@10.xxx.xxx.xxx
[ Thread-59 ]CSeq: 1 REGISTER
[ Thread-59 ]Date: Wed, 12 Oct 2011 03:01:38 GMT
[ Thread-59 ]
Warning: 399 UCXXXXXXXXX "Device type mismatch"
[ Thread-59 ]Via: SIP/2.0/UDP 10.xxx.xxx.xxx:5060;branch=z9hG4bK-b804-2ced326-59c656fe
[ Thread-59 ]Content-Length: 0
[ Thread-59 ]SipRegManager::RegClientStateChangedEvHandler() state Failed Reason 4
[ Thread-59 ]SipRegManager::RegClientStateChangedEvHandler()
[ Thread-59 ] Terminate the register-client due to failure, reason 4
[ Thread-59 ]SipRegManager::RegClientStateChangedEvHandler() state Terminated Reason 0
[ Thread-59 ]SipRegManager::RegClientStateChangedEvHandler()
[ Thread-59 ] RegClient 60c69ac8 - state changed to Terminated: reason 0

 

CollapseResolution

If an existing phone is configured as a BlackBerry MVS Client phone type and one wishes to change it to BlackBerry MVS Client with Voice over Wi-Fi phone type to support Voice over Wi-Fi calling, perform the following task:

Verify that correct COP files are installed in the UCM.

  1. Log in to the Cisco Unified Operating System Administration console
  2. Click Show > Software
  3. Under the Installed Software Options, the corresponding Option Name and Status should be displayed.

If the required COP files are missing, download the files from the Software Download for BlackBerry Mobile Voice System page. Install the COP file on the Cisco Unified Communications Manager. For more information, see the Cisco documentation for the Cisco Unified Communications Manager.

Finally, in the UCM delete the existing phone and re-create it as a BlackBerry MVS Client with Voice over Wi-Fi phone type.

Disclaimer

By downloading, accessing or otherwise using the Knowledge Base documents you agree:

   (a) that the terms of use for the documents found at www.blackberry.com/legal/knowledgebase apply to your use or reference to these documents; and

   (b) not to copy, distribute, disclose or reproduce, in full or in part any of the documents without the express written consent of RIM.


Visit the BlackBerry Technical Solution Center at www.blackberry.com/btsc.