IP Office Technical Tip (Region: Global)

206: Avaya one-X Mobile and Mobile Call Control for IP Office

11th August 2008 - Full PDF Text Version

This document provides information on how to configure one-X Mobile and Mobile Call Control for IP Office.

Avaya one-X Mobile

Avaya one-X Mobile is a client and server solution that provides users with IP Office telephony features in their mobile phones. one-X Mobile client software installed in supported mobile phones work with the IP500 acting as a feature server to provide desktop features to the mobile phone user.

Requirements for implementing one-X Mobile

1. one-X mobile is supported on IP500 running release 4.2 or above.

2. A Mobility license required for each configured user. It is the same license as the Mobile Twinning license in 4.1 and earlier.

3. Trunks that support clearing supervision required. Supported trunk types are:

• IP500 Universal PRI (Not supported on legacy PRI on a carrier card)

• IP500 BRI

• SIP (RFC2833)

4. Available DID/DDI numbers equal to the number of features to implement.

5. one-X Mobile Client application downloadable from http://support.avaya.com

6. IP Office release 4.2 supports Windows Mobile (5 or 6) and Symbian (Single Mode) devices only.

Verify support for your Mobile Phone

Please refer to the list of IP Office supported phones and operating system versions to verify support for your mobile phone.

• To find out the Windows Mobile version go to Start>Settings>System>About.

• To display Symbian (Nokia) firmware version enter *#0000# on the keypad.

Feature Name Extension (FNE)

A Feature Name Extension is a number you can dial that allows you to access an Avaya IP Office feature from your mobile phone. All FNEs that the administrator would like to activate must be associated to a DID/DDI that comes in over a supported trunk type. This is done in the IP Office configuration shown later. Additionally, the DID/DDI number must be configured in the configuration file for the one-X Mobile client.

The table below lists the supported IP Office FNEs, the corresponding FNE number and tag name. The FNE numbers are entered in the telephone number field when creating FNE Service short codes in the IP Office configuration. The tag names are used in the client configuration files to enable and disable a specific feature. The feature is enabled by populating a valid DID/DDI number in the associated tag. An empty tag does not enable the feature.

Configuration File

The configuration file sets up system information and specifies the features available to the mobile user. It is prepared by the administrator and usually deployed to the end user for installation. For a Windows Mobile device the configuration file must have the file extension of ".ini", whereas Symbian devices need to have a file extension of ".1xme".

A configuration file consists of 3 types of tags.

1. Prefixes and codes - These are either mandatory or optional tags that specify system information. Most of these tags are common to both Windows Mobile and Symbian configurations files except for the LOCATION_NAME tag.

2. FNE tags - These are feature name extension tags shown above. They are common to both Windows Mobile and Symbian configuration files.

3. Enterprise Settings - Additional settings to provide sub-menus to the client application.

An example configuration file is included in your downloaded package from the Avaya support web site. It contains all the tags that will need to be configured by the administrator.

The following is a brief description of all the tags for prefixes and codes. The values you enter for these tags depend on your country and the settings of your IP Office system. Examples of values for the United States are provided in the tags listed below.

• LOCATION_NAME = ;
  e.g LOCATION_NAME = Boston;
  This is a required tag for Windows Mobile .ini settings file only. It is not present or required for a Symbian configuration file. The string defines the location name of the one-X Mobile server and it will be displayed in the Avaya one-X Mobile menu on the mobile phone. If you have multiple locations, each location must have a unique LOCATION_NAME value.

• PRE_IMS = ;
  This tag is not used by IP Office

• DID_PREFIX = ;
  e.g DID_PREFIX = 173255512;
  This required tag defines the DID/DDI prefix that is used to specify the FNE features in the IP Office. For example, if you are using 73255512XX as DID/DDI numbers to activate your FNEs, the DID_PREFIX as shown above would be set intentionally short 2 digits since the FNE tag will be populated with the last 2 digits (e.g. IDLE_APPEARANCE_SELECT = 85;). The DID_PREFIX and the FNE digits when put together must equal the full DID/DDI number like in this example.

• INTERNATIONAL_DIRECT_DIAL_PREFIX = ;
  e.g INTERNATIONAL_DIRECT_DIAL_PREFIX = 011;
  This required tag specifies the international call prefix for your country.

• NATIONAL_DIRECT_DIAL_PREFIX = ;
  e.g NATIONAL_DIRECT_DIAL_PREFIX = 1;
  This optional tag specifies the prefix for dialing national numbers.

• HOME_COUNTRY_DIAL_CODE = ;
  e.g HOME_COUNTRY_DIAL_CODE = 1;
  This required tag is the home country code.

• ARS_CODE = ;
  e.g ARS_CODE = 9;
  This optional tag set the ARS access code.

• EXTENSION_LENGTH = ;
  e.g EXTENSION_LENGTH = 5;
  This required tag sets the dial plan length of the IP Office.

• NATIONAL_NUMBER_LENGTH = ;
  e.g NATIONAL_NUMBER_LENGTH = 9, 10;
  This required tag specifies the number of digits for a national number. This field accepts multiple numbers separated by commas for countries that have different number lengths.

• USERS_EMERGENCY_NUMBERS = ;
  e.g USERS_EMERGENCY_NUMBERS = 911;
  This is a required tag and it specifies the numbers dialed for emergency.

• SETTINGS_PIN = ;
  e.g SETTINGS_PIN = 1234;
  This is an optional tag. When set, the client will prompt for this pin when installing or modifying the configuration.

Below are some general guidelines for modifying the configuration file.

• Fill in the values for the tags you want to use.

• Do not modify the tag name or equal sign (=) for a tag.

• Do not remove the terminating semi-colon (;) for a tag. The client application will ignore any characters after the semi-colon so description text can be added after the semi-colon.

• Do not remove any tag rows. If tag values are unavailable or not provided, leave the value position blank (for example, CALL_PICKUP_DIRECTED = ;)

• Enter all tag values between the equal sign (=) and the semi-colon (;) (for example, CALL_PICKUP_GROUP_EXTENDED = 5512;)

Note: The example settings file usually include the "+" character in front of the prefixes. In some cases a mobile device does not recognize the "+" and the call will not complete. It is recommended that the "+" is not in the prefixes as shown in the example settings file.

Installing and Configuring the one-X Mobile Client on Windows Mobile

Note: one-X Mobile client application will require up to 20 megabytes of free memory.

Note: The application must be installed on the phone main memory. It must not be installed on the memory card (Flash) drives.

1. Download the Avaya one-X Mobile installation package and the configuration (.ini) file to the phone and note the location of these files.

2. Before installing the application, stop all programs, such as Push Email applications, that are actively running on your mobile phone.

3. Run the Avaya one-X Mobile installer and follow the prompts provided by Microsoft

4. After the software is installed, reboot your mobile phone.

5. Access the Avaya one-X Mobile client on your mobile phone. If it is not in the foreground, press the Send button.

6. Select Menu > Settings > Options.

7. Select the Admin tab.

8. If prompted, enter your PIN and select the Enter soft key.

9. Select Install Configuration File.

10. Select the Select soft key.

11. Select the configuration (.ini) file. The file installs and configures the Avaya one-X Mobile client.

12. Select the Done soft key.

13. If this device is to support multiple locations, repeat this procedure for the settings file for each location.

Installing and Configuring the one-X Mobile Client on Symbian Phones

Please refer to the user documentation that came with your device for instructions on using desktop software, USB, infra-red, or Bluetooth connectivity to install Avaya one-X Mobile.

To install the Avaya one-X Mobile software using the Nokia PC Suite application, perform the following steps:

1. Install the Nokia PC Suite software on your computer. This software is packaged with your mobile device.

2. Install the Avaya one-X Mobile software using the Install Applications menu in the Nokia PC Suite software.

3. During the installation, you can select the language that you want to use for the Avaya one-X Mobile software.

4. Complete the installation by installing the software on the phone memory.
   Note: Do not install the Avaya one-X Mobile software on the Memory Card/Flash.

5. Copy your ".1xme" configuration file to the phone and note the location of the file.

6. Open the Avaya one-X Mobile application on the mobile phone.

7. Select Menu > Settings.

8. Select the Download Config File option.

9. Select Menu and the Select file option.

10. Choose Phone Memory or Memory Card (wherever you put the .1xme configuration file from step 5).

11. Select your ".1xme" configuration file and it will be loaded into the Avaya one-X Mobile client.

Configuring the IP Office

one-X Mobile relies on the Twinned Mobile Number of the user device (circled below) to be present in the IP Office configuration to identify the one-X user.

When a one-X client calls into the IP Office to use the FNE services, the mobile Caller ID is matched to the Twinned Mobile Number to identify the IP Office user. Therefore, it is important that a one-X user does not turn off mobile twinning using existing methods (e.g. Twinning button desk phone or Phone Manage Pro), because doing so will remove the Twinned Mobile Number from the IP Office configuration and one-X calls will not function.

If one-X users want to enable or disable mobile twinning functionality, they must use the ExtToCellular Enable/Disable feature in their one-X client application. ExtToCellular Disable will turn mobile twinning functionality off while retaining the Twinned Mobile Number in the IP Office configuration. This allows one-X mobile to continue to work even when the user chooses to turn mobile twinning functionality off.

It is also important to note that turning the mobile twinning functionality off using ExtToCellular Disable is independent of turning mobile twinning off via the Twinning button on the desk phone or through Phone Manage Pro. If a user invokes ExtToCelluar Disable on the mobile client application, the user’s desk phone Twinning button will still be illuminated.

Configuring the User

Once the Mobility license has been installed, users can be configured for one-X Mobile. In IP Office release 4.2 the "Twinning" tab has been renamed to "Mobility". To set up a user for one-X Mobile

1. Navigate to the user’s Mobility tab

2. Check the "Mobility Features" checkbox

3. Check the "Mobile Twinning" checkbox

4. Fill in the "Twinned Mobile Number"

5. Check the "one-X Mobile Client" checkbox

Creating FNE Short Codes

A short code feature called "FNE Service" is used to implement the FNE behavior required for one-X Mobile client support. The Telephone Number field will be the FNE feature number. One way to program the short code is shown below.

• Code - 777XX
  The short code can be any number. In this example, 777 is an arbitrary prefix used.

• Feature - FNE Service
  Must have FNE Service selected as a short code feature.

• Telephone Number - N

Setting the Incoming Call Route

The incoming call route (ICR) is used to tie the DID/DDI number to a particular FNE feature. If the Blind Transfer feature (FNE 26) DID/DDI was set to 7175521981 in the client configuration file, then the ICR destination must be set to the 77726. This will activate the Blind Transfer FNE feature by setting the Telephone Number field to 26 when the 777XX short code is invoked.

Mobile Call Control

Mobile Call Control (MCC) is a mobility feature similar to but independent of one-X Mobile. MCC allows any mobile phone user to access IP Office features without using the one-X Mobile client application. It uses FNE 31 (Star Star Service) to provide dial tone to the mobile phone user. "Star Star Service" is implemented using the same underlying methods as the one-X mobile FNE service but has no relationship to it.

A Mobility Feature license is required for an MCC user. One instance of the Mobility license provides a user with all the mobility features including MCC, one-X Mobile and Mobile Twinning.

MCC users can gain access to the "Star Star Service" dial tone when they receive a twinned call. After receiving a twinned call, the mobile user can dial ** to place that call on hold and get dial tone from the IP Office. Once the mobile user receives IP Office dial tone, any subsequent dialing done is interpreted as if the user is logged into an analog extension on the IP Office.

To gain access to the "Star Star Service" dial tone, the mobile user can dial the FNE 31 DID/DDI that has been programmed in the IP Office. Similarly, once dial tone is heard, the user can dial numbers and short codes as if the user is logged into an analog extension on the IP Office.

The trunk requirements for the "Star Star Service" FNE are the same as for the one-X Mobile. That is, trunks that support clearing supervision are required. Supported trunk types are:

1. IP500 Universal PRI (Not supported on legacy PRI on a carrier card)

2. IP500 BRI

3. SIP (RFC2833)

Configuring a Mobile Call Control User

Like one-X Mobile, IP Office identifies the MCC user by matching the mobile Caller ID to the Twinned Mobile Number setting. "Star Star Service" FNE is programmed in IP Office the same way as other one-X Mobile FNEs.

To set up a Mobile Call Control user

1. Navigate to the user’s Mobility tab

2. Check the "Mobility Features" checkbox

3. Check the "Mobile Twinning" checkbox

4. Fill in the "Twinned Mobile Number"

5. Check the "Mobile Call Control" checkbox