Help Center

Local Navigation

Instant messaging process flows

Process flow: Starting an instant messaging session using the BlackBerry Client for use with Microsoft Office Live Communications Server 2005 (Microsoft Office Communicator)

This diagram shows the components that are described in the following text.
  1. A user logs in to a collaboration client on a BlackBerry® device.
  2. The BlackBerry device compresses and encrypts the user ID and password, and sends them through the BlackBerry Router to the BlackBerry Dispatcher over port 3101.
  3. The BlackBerry Dispatcher sends the request to the BlackBerry Collaboration Service over port 3201. If the BlackBerry Collaboration Service is located on a remote computer, the request remains encrypted using a Research In Motion proprietary protocol.
  4. The BlackBerry Collaboration Service checks the BlackBerry Configuration Database to find out if the maximum number of sessions has been reached, and performs one of the following actions:
    • If the maximum number of sessions has been reached and a timeout limit is set, the BlackBerry Collaboration Service logs out any instant messaging sessions on BlackBerry devices that are out of coverage, and any instant messaging sessions that are no longer sending status messages to the BlackBerry Collaboration Service.
    • If no idle sessions exist, the BlackBerry Collaboration Service sends a "Server Busy" status message to the BlackBerry device and rejects the login request.
    • If the maximum number of sessions is not set and the number of sessions equals the total number that the HTTP persistent connection supports, the BlackBerry Collaboration Service sends a "Failed" status message to the BlackBerry device and rejects the login request.

    The BlackBerry Collaboration Service checks the BlackBerry Configuration Database to verify that the user has permission to use the collaboration client, and tries to authenticate the user using Integrated Windows® Authentication. If the authentication is not successful, the BlackBerry Collaboration Service tries a forms-based login process instead. The BlackBerry Collaboration Service sends a login request in JSON, a lightweight data-interchange format, to the Microsoft® Office Communicator Web Access server.

    The BlackBerry Collaboration Service opens the connection using HTTPS over port 443. You can also configure the connection to use HTTP, the transport protocol that the AJAX service uses, or a custom port number.

  5. The Microsoft Office Communicator Web Access server formats the request using a Microsoft API and sends the request to the Microsoft® Office Live Communications Server over an MTLS connection.
  6. The Microsoft Office Live Communications Server accepts the request, processes the login information, and sends the acceptance to the Microsoft Office Communicator Web Access server.
  7. The Microsoft Office Communicator Web Access server sends the acceptance to the BlackBerry Collaboration Service.
  8. The BlackBerry Collaboration Service sends the acceptance, in encrypted and compressed format, through the BlackBerry Dispatcher to the BlackBerry device, and creates a cache of the connectivity information to maintain the instant messaging session.
  9. The collaboration client on the BlackBerry device starts the session using an open GET request over the HTTPS persistent connection.

The BlackBerry Collaboration Service receives events that the server initiates from the Microsoft Office Communicator Web Access server using an HTTP GET or HTTPS GET request, and sends the events to the collaboration client over the session. The BlackBerry Collaboration Service sends events that the BlackBerry device initiates to the Microsoft Office Communicator Web Access server using an HTTP POST or HTTPS POST request.

Process flow: Starting an instant messaging session using the BlackBerry Client for use with Microsoft Office Communications Server 2007

This diagram shows the components that are described in the following text.
  1. A user logs in to a collaboration client on a BlackBerry® device.
  2. The BlackBerry device compresses and encrypts the user ID and password, and sends them through the BlackBerry Router to the BlackBerry Dispatcher over port 3101.
  3. The BlackBerry Dispatcher sends the request to the BlackBerry Collaboration Service over port 3201. If the BlackBerry Collaboration Service is located on a remote computer, the request remains encrypted using a Research In Motion proprietary protocol.
  4. The BlackBerry Collaboration Service checks the BlackBerry Configuration Database to find out if the maximum number of sessions has been reached, and performs one of the following actions:
    • If the maximum number of sessions has been reached and a timeout limit is set, the BlackBerry Collaboration Service logs out any instant messaging sessions on BlackBerry devices that are out of coverage, and any instant messaging sessions that are no longer sending status messages to the BlackBerry Collaboration Service.
    • If no idle sessions exist, the BlackBerry Collaboration Service sends a "Server Busy" status message to the BlackBerry device and rejects the login request.
    • If the maximum number of sessions is not set and the number of sessions equals the total number that the HTTP persistent connection supports, the BlackBerry Collaboration Service sends a "Failed" status message to the BlackBerry device and rejects the login request.

    The BlackBerry Collaboration Service checks the BlackBerry Configuration Database to verify that the user has permission to use the collaboration client, and tries to authenticate the user using Integrated Windows® Authentication. If the authentication is not successful, the BlackBerry Collaboration Service tries a forms-based login process instead. The BlackBerry Collaboration Service sends a login request in XML format to the Microsoft® Office Communicator Web Access server.

    The BlackBerry Collaboration Service opens the connection using HTTPS over port 443. You can also configure the connection to use HTTP, the transport protocol that the AJAX service uses, or a custom port number.

  5. The Microsoft Office Communicator Web Access server formats the request using a Microsoft API and sends the request to the Microsoft® Office Communications Server 2007 over an MTLS connection.
  6. The Microsoft Office Communications Server 2007 accepts the request, processes the login information, and sends the acceptance to the Microsoft Office Communicator Web Access server.
  7. The Microsoft Office Communicator Web Access server sends the acceptance to the BlackBerry Collaboration Service.
  8. The BlackBerry Collaboration Service sends the acceptance, in encrypted and compressed format, through the BlackBerry Dispatcher to the BlackBerry device, and creates a cache of the connectivity information to maintain the instant messaging session.
  9. The collaboration client on the BlackBerry device starts the session using an open GET request over the HTTPS persistent connection.

The BlackBerry Collaboration Service receives events that the server initates from the Microsoft Office Communicator Web Access server using an HTTP GET or HTTPS GET request, and sends the events to the collaboration client over the session. The BlackBerry Collaboration Service sends events that the BlackBerry device initiates to the Microsoft Office Communicator Web Access server using an HTTP POST or HTTPS POST request.

Process flow: Starting an instant messaging session using the BlackBerry Client for IBM Lotus Sametime

This diagram shows the components that are described in the following text.
  1. A user logs in to a collaboration client on a BlackBerry® device.
  2. The BlackBerry device compresses and encrypts the user ID and password, and sends them through the BlackBerry Router to the BlackBerry Dispatcher over port 3101.
  3. The BlackBerry Dispatcher sends the request to the BlackBerry Collaboration Service over port 3201. If the BlackBerry Collaboration Service is located on a remote computer, the request remains encrypted using a Research In Motion proprietary protocol.
  4. The BlackBerry Collaboration Service checks the BlackBerry Configuration Database to find out if the maximum number of sessions has been reached, and performs one of the following actions:
    • If the maximum number of sessions has been reached and a timeout limit is set, the BlackBerry Collaboration Service logs out any instant messaging sessions on BlackBerry devices that are out of coverage, and any instant messaging sessions that are no longer sending status messages to the BlackBerry Collaboration Service.
    • If no idle sessions exist, the BlackBerry Configuration Database sends a "Server Busy" status message to the BlackBerry device and rejects the login request.
    • If the maximum number of sessions is not set and the number of sessions equals the total number that the IBM® Lotus® Sametime® API supports, the BlackBerry Configuration Database sends a "Failed" status message to the BlackBerry device and rejects the login request.

    The BlackBerry Collaboration Service checks the BlackBerry Configuration Database to verify that the user has permission to use the collaboration client, and connects to the IBM Lotus Sametime server. The BlackBerry Collaboration Service starts an encrypted proxy connection over TCP/IP using the IBM Lotus Sametime API, reformats the request from the RIM proprietary protocol format into one that the IBM Lotus Sametime API supports, and sends the request.

    By default, the BlackBerry Collaboration Service starts the connection over port 1533 unless you specify a custom port number.

  5. The IBM Lotus Sametime server accepts the login request from the BlackBerry device, starts a dedicated TCP/IP connection for the session, and listens for requests from the BlackBerry device for the session.
  6. The BlackBerry Collaboration Service sends the acceptance, in encrypted and compressed format, through the BlackBerry Dispatcher to the BlackBerry device, and creates a cache of the connectivity information to maintain the instant messaging session.

Process flow: Starting an instant messaging session using the BlackBerry Client for Novell GroupWise Messenger

This diagram shows the components that are described in the following text.
  1. A user logs in to a collaboration client on a BlackBerry® device.
  2. The BlackBerry device compresses and encrypts the user ID and password and sends them through the BlackBerry Router to the BlackBerry Dispatcher over port 3101.
  3. The BlackBerry Dispatcher sends the request to the BlackBerry Collaboration Service over port 3201. If the BlackBerry Collaboration Service is located on a remote computer, the request remains encrypted using a Research In Motion® proprietary protocol.
  4. The BlackBerry Collaboration Service checks the BlackBerry Configuration Database to find out if the maximum number of sessions has been reached, and performs one of the following actions:
    • If the maximum number of sessions has been reached and a timeout limit is set, the BlackBerry Collaboration Service logs out any instant messaging sessions on BlackBerry devices that are out of coverage, and any instant messaging sessions that are no longer sending status messages to the BlackBerry Collaboration Service.
    • If there are no idle sessions, the BlackBerry Configuration Database sends a "Server Busy" status message to the BlackBerry device and rejects the login request.
    • If the maximum number of sessions is not set and the number of sessions equals the total number that the Novell® GroupWise® protocol supports, the BlackBerry device sends a "Failed (300)" status message to the BlackBerry device and rejects the login request.

    The BlackBerry Collaboration Service checks the BlackBerry Configuration Database to verify that the user has permission to use the collaboration client, and connects to the Novell GroupWise Messenger server.

    The BlackBerry Collaboration Service starts an encrypted proxy (SSL) connection using the Novell GroupWise protocol and sends the request. By default, the BlackBerry Collaboration Service opens the connection over port 8300, but it can also open the connection over a custom port number.

  5. The Novell GroupWise Messenger server accepts the login request from the BlackBerry device, opens a dedicated SSL connection for the session, and listens for requests from the BlackBerry device.
  6. The BlackBerry Collaboration Service sends the acceptance, in encrypted and compressed format, through the BlackBerry Dispatcher to the BlackBerry device, and creates a cache of the connectivity information to maintain the instant messaging session.

Process flow: Sending a file to a contact using the BlackBerry Client for IBM Lotus Sametime

This diagram shows the components that are described in the following text.
  1. A user opens a conversation with a contact, clicks Send File on the menu, and selects a file to send to the contact.
  2. The BlackBerry® Client for IBM® Lotus® Sametime® creates an invitation request and sends it to the BlackBerry Collaboration Service.
  3. The BlackBerry Collaboration Service checks the size of the file to verify that it does not exceed the maximum file size that you configure on the BlackBerry® Enterprise Server, associates the file extension and the conversation ID with the invitation request, and sends the request to the IBM Lotus Sametime server.
  4. The IBM Lotus Sametime server checks the file size to verify that it does not exceed the maximum file size that you configured on the IBM Lotus Sametime server (by default, 1 MB), associates the file with the conversation that is open between the sender and recipient, and sends the request to the BlackBerry Collaboration Service.
  5. The BlackBerry Collaboration Service converts the request into an instant messaging invitation and sends it to the client on the recipient's BlackBerry device.
  6. In the conversation window on the recipient's client, the recipient receives a request to accept or decline the file. The recipient can also select an option to optimize the file for viewing on the BlackBerry device.

    The BlackBerry Collaboration Service can optimize files for viewing on the BlackBerry device only if it has access to the BlackBerry Attachment Service in your organization's environment.

  7. The recipient accepts the request.

    If the recipient selected the optimize option, the file will be downloaded to the memory of the BlackBerry device. If the recipient did not select the optimize option, the client prompts the recipient to save the file to a location in the file system on the BlackBerry device.

  8. The recipient's client sends a content request packet to the BlackBerry Collaboration Service.
  9. The BlackBerry Collaboration Service requests the file size from the IBM Lotus Sametime server, and sends data to the IBM Lotus Sametime server to begin the file transfer process.

    By default, the media transfer state on the BlackBerry Collaboration Service is set to transfer.

  10. The sender's client sends the data for the file in content message packets to the BlackBerry Collaboration Service.
  11. The BlackBerry Collaboration Service checks the order of the content message packets and sends them to the recipient's client using a BlackBerry instant messaging protocol.
  12. The recipient's client receives the first content message packet, sends an acknowledgement message to the BlackBerry Collaboration Service, and requests the next content message packet from the BlackBerry Collaboration Service. This continues until the client receives all of the content message packets.

    If the recipient selected the option to optimize the file for viewing, the BlackBerry Attachment Service converts the file into a format that is optimized for viewing on the BlackBerry device.

  13. When the BlackBerry Collaboration Service receives an acknowledgement message for the last content message packet from the recipient's client, it changes its media transfer state to done and stops the file transfer process on the IBM Lotus Sametime server.
  14. In the conversation window, the client notifies the recipient that the file has been received.

    The recipient can open the file from the conversation window or from the file system on the BlackBerry device. The BlackBerry device uses the BlackBerry® Browser to render supported files. If the recipient selected the option to optimize the file for viewing, the recipient can open and view supported files in the attachment viewer on the BlackBerry device. The recipient can also save the optimized file to a location in the file system on the BlackBerry device.


Was this information helpful? Send us your comments.