Configuring the BlackBerry Collaboration Service settings

Article ID: KB04858

Type: Support Content

Last Modified: 11-12-2013

 

Product(s) Affected:

  • BlackBerry Enterprise Server 5
Jump to: Environment | Overview
CollapseEnvironment
  • BlackBerry Collaboration Service
  • BlackBerry Enterprise Server software 4.1
  • BlackBerry Instant Messaging for Microsoft Live Communications Server
CollapseOverview

This article provides information about configuring the following items for BlackBerry Collaboration Service:


Default Domain Name

The default domain name may need to be set, depending on whether the domain portion of the Microsoft Windows account user name is the same as the domain portion in the Session Initiation Protocol Uniform Resource Identifier (SIP URI) Sign-in name. For example, at Research In Motion, the Windows account user name is <user_ name>@rim.net. The SIP URI Sign-in name is <user_name>@rim.com. Therefore, the BlackBerry Enterprise Server administrator would set the default domain name. When the BlackBerry device user logs in, the User name field can be left blank.

If the domain portion is the same for both the Windows account user name and SIP URI Sign-in name, the default domain name in the service and the BlackBerry device user name in the login screen of the instant messaging client can both be left blank. When logging in, the BlackBerry device user can enter the SIP URI Sign-in name into the Sign-in Name field.


Log-in Credentials

 Scenario 1

If the SIP URI Sign-in name is different from the Windows account user name, the default domain name should be the Windows account user name and the Sign-in name should be the SIP URI Sign-in name, as shown in the image below.

Scenario 2

If the SIP URI Sign-in name (Internet domain address) is the same as the Windows login ID (Windows domain address), then the User name field can be left blank in Enterprise Messenger. For example, if a BlackBerry device user whose SIP URI sign-in name is first_last@rim.com and Windows login ID is first_last@rim.com, then type first_last@rim.com in the Sign-in name field in Enterprise Messenger and leave the User name fieldblank.

Scenario 3

If the SIP URI Sign-in name (Internet domain address) is different than Windows login ID (Windows domain address) but the alias is same, then define the Windows domain name in the Default Domain Name section from BlackBerry Collaboration Service properties to save typing the Windows login ID in the User name field. For example, if the SIP URI Sign-in name is user@rim.com but the Windows domain login is user@rim.net, this should be defined as rim.net in the Default Domain Name field section of the BlackBerry Collaboration Service properties.

From Enterprise Messenger on the BlackBerry device, type user@rim.com in the Sign-in name field and leave the User name field blank. The BlackBerry Collaboration Service will take the alias of the SIP URI Sign-in name and append it with whatever is defined in the Default Domain Name field section (for example, user@rim.com will become user@rim.net), as BlackBerry Instant Messenger uses the Windows login account to authenticate on the Live Communications Server.

Scenario 4

In some environments, the Windows domain login ID is completely different than the SIP URI Sign-in name (Internet domain address). For example, if the SIP URI Sign-in name is first.last@rim.com but Windows login ID is f_last@rim.net, then log in with both SIP URI Sign-in name and the User name from Enterprise Messenger to authenticate with the Live Communications Server. In this case defining the Default Domain Name field section as rim.net in the BlackBerry Collaboration Service properties will not work if  trying to log in without the User name from Enterprise Messenger. This is because the BlackBerry Collaboration Service will take the alias first.last from SIP URI Sign-in name and append it to the default domain name rim.net (which is defined in the BlackBerry Collaboration Service properties). Since first.last@rim.net is not the correct Windows login ID in this example, user will receive the following error:

User id and password is invalid; please contact your system administrator.

If there are BlackBerry device users in the above environment whose Windows domain login ID is also first.last@rim.net, then define rim.net in the Default Domain Name field from BlackBerry Collaboration Service properties, as in Scenario 2 above, and these BlackBerry device users do not have to type the User name from Enterprise Messenger.


Port Settings

Either Transport Layer Security (TLS) or Transmission Control Protocol (TCP) can be used as the communication protocol between the BlackBerry Instant Messaging Connector and the Live Communications Server. The BlackBerry Collaboration Service and the Live Communications Server must be configured with the same communication protocol and port.

TLS is the recommended communication protocol for the following reasons:

  • For each BlackBerry device user login, TLS requires only one socket connection to the Live Communication Server, while TCP requires three socket connections to the Live Communication Server.
  • Data is encrypted with a TLS connection.

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.