Call flow: Receiving a PBX-initiated call on a BlackBerry device from an external number

  1. An external user dials the work number of a BlackBerry Mobile Voice System user.
  2. The PBX sends the call through the Avaya Aura Session Manager to the SIP gateway.
  3. The SIP gateway creates a call establishment request and sends it to the MVS Session Manager over the SIP trunk.
  4. The MVS Session Manager filters the call establishment request through the BlackBerry MVS user's settings: unknown caller ID, call scheduling, allowed caller list, and blocked caller list. If the call is permitted, the MVS Session Manager sends the call establishment request to the BlackBerry Enterprise Server.
  5. The BlackBerry Enterprise Server compresses and encrypts the call establishment request, and sends it to the wireless network.

    The call establishment request contains the caller identification information and the phone number of the caller.

  6. One of the following events occurs:
    • If the BlackBerry device receives the incoming call request, the BlackBerry device decrypts and decompresses it. The BlackBerry device then encrypts and compresses a call establishment response, and sends the call establishment response to the BlackBerry Enterprise Server. The BlackBerry Enterprise Server decrypts and decompresses the call establishment response, and sends it to the MVS BlackBerry Enterprise Server Connector.
    • If the BlackBerry device does not receive the incoming call request, the MVS BlackBerry Enterprise Server Connector stops responding while it waits for the call establishment response.
  7. The MVS BlackBerry Enterprise Server Connector sends the request to the MVS Session Manager
  8. The MVS Session Manager using the SIP trunk, requests that SIP gateway establish a call through the Avaya Aura Session Manager to the PBX to the BlackBerry device using the mobile number.
  9. The PBX sends the call request to the BlackBerry device over the PSTN and wireless network.
  10. The BlackBerry device receives the call. The following events can occur:
    • If the BlackBerry device receives the call establishment request, the caller ID from the call establishment request appears on the BlackBerry device.
    • If the ANI matches the ANI in the Telephony Connector Caller Identification Number field of the MVS Console, the call appears on the BlackBerry device as a BlackBerry MVS call.
    • If the ANI matches an ANI in the Telephony Connector Optional ANI numbers available for identifying BlackBerry MVS calls fields of the MVS Console, the call appears on the BlackBerry device as a BlackBerry MVS call.
    • If the BlackBerry device does not receive the call establishment request, the call appears on the BlackBerry device as an unknown call.
  11. The BlackBerry MVS user accepts the call on the BlackBerry device.
  12. The BlackBerry MVS Client sends a verification code request to the MVS Session Manager using DTMF tones.
  13. If the incoming call has an empty ANI, the MVS Session Manager sends a verification code response to the BlackBerry device using DTMF tones. One of the following events occurs:
    • If no ANI exists in the received call, and the BlackBerry device receives the call establishment request, the call appears on the BlackBerry device as a BlackBerry MVS call with the caller ID from the call establishment request.
    • If no ANI exists in the received call, and the BlackBerry device did not receive the call establishment request, the call appears on the BlackBerry device as a wireless network call.
  14. If the incoming call has an empty ANI, and the BlackBerry MVS Client receives the verification code response from the MVS Session Manager, the BlackBerry MVS Client switches the call so that it appears as a BlackBerry MVS call.
  15. The MVS Session Manager instructs the SIP gateway to connect the two call legs, and voice communication can occur.

Was this information helpful? Send us your comments.