EMS in details

Overview

The Enterprise Mobility Gateway (EMG) is the server component of the Enterprise Mobility Solution (EMS). It works in conjunction with the client component : the Smart Mobile Client. The EMS extends the features available to a mobile phone user.

• Single identity: A mobile phone user can provide one phone number to all contacts. Other people can dial that phone number – their “EMG phone number” and reach the user on the user’s Smart Mobile Client softphone, mobile phone, desk phone, or even another phone number such as the user’s home phone. Similarly, the user can make a phone call from any of these endpoints and the other party will see the call as coming from the single EMG phone number.

• A mobile phone user works as if on the PBX and has access to the features of the PBX:

• Access the corporate directory.

• Place calls to extensions on the PBX by entering the extension number.

• Quickly transfer calls to extensions on the PBX.

• See the online status of people in the directory.

• Connect to the enterprise voicemail with one click.

• A mobile phone user can send and receive instant messages (and can look up addresses in the corporate directory).

• A mobile phone user can create a conference call from two established calls.

• A Nokia mobile phone user can place VoIP phone calls when using the phone in a WiFi zone, thereby reducing the costs incurred by use of the cellular network.

How Enterprise Mobility Solution Works

The EMS involves the following components:

• The PBX, which must be either an IP-PBX or a PBX with an IP gateway.

• The enterprise LAN or LANs.

• The Enterprise Mobility Gateway (EMG) server.

• Phone extensions in the enterprise. These extensions can be VoIP extensions such as computers running Smart Mobile Client or IP deskphones, or they can be traditional deskphones. Phone extensions are not really a required part of the EMS, but they can be used by the EMS to extend the user’s options in placing and receiving calls.

• Mobile phones with a Smart Mobile Client client (the EMS client) installed. These are referred to as Smart Mobile Client phones and the mobile phone users are referred to as Smart Mobile Client Mobile users.

• Mobile phones that are being used by Smart Mobile Client web client users. Calls made by these users are referred to as EMG calls.

The EMG mediates calls between the Smart Mobile Client user and the PBX.

Smart Mobile Client Clients

Single- and Dual-mode Clients

There are four Smart Mobile Client clients:

• Smart Mobile Client for BlackBerry

• Smart Mobile Client for Windows Mobile

• Smart Mobile Client for Nokia

• Smart Mobile Client for Android

• Smart Mobile Client for iPhone

A single-mode client makes cellular phone calls using the mobile phone’s native dialer.

A dual-mode client makes VoIP calls over the WiFi network whenever possible, using the mobile phone’s native VoIP functionality. When the client cannot make a WiFi call, it makes a cellular call using the mobile phone’s native dialer. The dual-mode client has automatic and manual handoff capability.

Logging in and Registration with the EMG

When the Smart Mobile Client user logs into the EMG, the mobile phone connects (via a data connection) to the EMG IP address, sending the Smart Mobile Client user ID and password, and the user’s mobile phone number. The EMG then registers with the PBX for this user ID.Incoming calls to the Smart Mobile Client user’s DID or extension will be mapped to this user ID and thus directed to the EMG. The EMG notes the association between the user ID and the mobile phone number, so that whenever it is handling phone calls for this user ID, it knows which mobile phone number to call. When the user logs out of Smart Mobile Client, the user ID becomes unregistered. EMG calls can no longer be made or received using that mobile phone.

The Smart Mobile Client Web Client

The Smart Mobile Client web client is intended for users who have a mobile phone for which there is no “regular” Smart Mobile Client Mobile client. The web client lets the user set up their mobile phone number on the EMG so that they can place calls and receive calls at their mobile phone. The web client does not include presence or IM.

Signing in and Registration with the EMG

When the web client user loads the web page on a browser and signs in for the first time, the user ID is registered with the EMG. The user then configures a phone number, which creates a binding between the registered user ID and the phone number. When the user signs out, their user ID does not get unregistered: it remains active in the EMG. This means that the user can still receive phone calls at the currently bound number. The user ID only becomes unregistered if:

• A regular Smart Mobile Client Mobile logs in using that user ID and then logs out.

• You log the user out on the User Info screen

How Outgoing Calls Are Handled

Here is one way that an outgoing call is placed:

• When the Smart Mobile Client user places a call, the user’s mobile phone number and the other party’s phone number (the target) are sent to the EMG via HTTP.

• A call (the “first call”) is then placed from the mobile phone to the EMG’s service number.

• On the PBX, the EMG’s service number is mapped to the EMG’s extension. The EMG answers the call and puts it on hold: call A is now established. The user hears the message “Please wait while your call is established”.

• The EMG matches up the call to the HTTP information by matching the user’s mobile phone number; it then gets the target from that HTTP information and makes a call to that target.

• When the target answers, call B is established.

• The EMG bridges call A and call B.

How Incoming Calls Are Handled

Here is one way that an incoming call is placed:

• The PBX receives a phone call for the user. The caller may phone the user on the user’s DID (which maps on the PBX to the user’s extension), or may phone the enterprise phone number and then connect to the user’s internal extension.

• The PBX routes the phone call to the user’s extension. Both the user’s deskphone and the EMG are registered against this extension on the PBX. Therefore, the call is routed to both the deskphone and the EMG’s extension.

• The EMG sends an HTTP alert to the Smart Mobile Client user.

• Smart Mobile Client displays the alert and provides the user with options of places to take the call: for example, the mobile phone, the deskphone, the user’s home phone. The user chooses one of these options (the default option is to take the call on the mobile phone) and this response is sent back to the EMG via HTTP.

• When this response is received, the EMG answers the incoming call. The PBX will cancel ringing on the user’s extension.

• Call A is now established. EMG immediately puts this call on hold.

• The EMG then places a call from its own extension to the selected device.

• The user picks up the call at the selected device. The EMG bridges call A and call B.

How the User’s Phone Identity Is Published

The other party sees the Smart Mobile Client user’s phone identity as follows:

• If the other party is on an internal extension, they see the user’s local extension.

• If the other party is outside the enterprise, they see the enterprise phone number.