SIP gateway process flow: Holding and resuming a call on a BlackBerry device

  1. A BlackBerry Mobile Voice System user is on a call that uses the SIP trunk. On the BlackBerry device, the user presses the Menu key and clicks Hold.
  2. The BlackBerry MVS Client creates a hold request. One of the following events occurs:
    • If the user is in a wireless coverage area where data services are not available, the BlackBerry MVS Client sends a hold request as a DTMF tone sequencs to the PBX. The PBX forwards it to the SIP gateway and the SIP gateway converts the DTMF tones to SIP INFO method. The SIP INFO method carries the text translation in digit format of the tone. The SIP gateway sends it to the MVS Session Manager.
    • If the user is in a wireless coverage area where data services are available, the BlackBerry MVS Client compresses, encrypts, and sends the request to the wireless network. The BlackBerry Enterprise Server decrypts, decompresses, and sends the request to the MVS BlackBerry Enterprise Server Connector. The MVS BlackBerry Enterprise Server Connector sends the request to the MVS Session Manager.
  3. The MVS Session Manager places the SIP trunk call leg into a hold state through the SIP gateway. The hold state includes music on hold if your organization's telephony infrastructure is configured for music on hold. If the BlackBerry MVS user makes another call, the MVS Session Manager reuses the cellular leg to make the call.

  4. On the BlackBerry device, the BlackBerry MVS user presses the Menu key and clicks Resume.
  5. The BlackBerry MVS Client creates a resume request. One of the following events occurs:
    • If the user is in a wireless coverage area where data services are not available, the BlackBerry MVS Client uses DTMF tones to send the resume request to the SIP gateway over the wireless network. The SIP gateway converts the DTMF tones to SIP INFO and sends the SIP INFO to the MVS Session Manager. The MVS Session Manager, through the SIP gateway, removes the hold state from the SIP trunk call leg, and the call can continue.
    • If the user is in a wireless coverage area where data services are available, the BlackBerry MVS Client compresses, encrypts, and sends the request to the BlackBerry Enterprise Server over the wireless network. The BlackBerry Enterprise Server decrypts, decompresses, and sends the request to the MVS BlackBerry Enterprise Server Connector. the MVS BlackBerry Enterprise Server Connector sends the request to the MVS Session Manager. The MVS Session Manager, through the SIP gateway, removes the hold state from the SIP trunk call leg, and the call can continue.

Was this information helpful? Send us your comments.