one-X Mobile Client

$Show\Hide Navigation$ Manager: Telephone Features

one-X Mobile Client

IP500 systems running IP Office 4.2+ support the Avaya one-X Mobile Client on Windows and Symbian mobile cell phones. This uses DID numbers (one for each feature required) to activate and use various one-X Mobile features supported by the IP Office system.

The IP Office is configured to route incoming calls on those DID numbers to short codes for each feature. The caller's incoming CLI is then checked for a match against the mobile twinning and forwarding numbers of those users configured for one-X Mobile operation. If a match is found access to the one-X feature is allowed using the identity of that user as if they were now dialing from an extension on the IP Office system.

•

WARNING
This feature allows external callers to use features on your phone system and to make calls from the phone system for which you may be charged. The only security available to the system is to check whether the incoming caller ID matches a configured users' Twinned Mobile Number setting. The IP Office cannot prevent use of these features by caller's who present a false caller ID that matching that of a user configured for this feature.

Example

Stage

Events

Setup the User's Mobile Cell Phone for one-X Mobile

1.	The one-X Mobile client application has been loaded onto a user's mobile cell phone.

A configuration file for the IP Office one-X functions is also loaded. Within this the DDI numbers allocated for one-X mobile features are split into two parts; a shared DDI prefix for IP Office system and then a DDI suffix for each require one-X feature. Whenever a one-X feature is selected by the user, the prefix and the appropriate suffix for the feature are combined into a number dialled by the users mobile cell phone.

User selects a one-X Mobile feature on their phone

1.	Within the one-X Mobile client application on their phone, the user selects the 'dial tone' feature.

2.	The DDI prefix and the DDI suffix in the phone's one-X Mobile configuration file are combined to dial the appropriate DDI number. For this example 555 776 9900.

The DDI call is received by the IP Office

1.	The call is received by the IP Office along with the number of DDI digits that the line provider passes through. For this example the four digits 9900.

2.	On the IP Office an Incoming Call Route has been added with the Incoming Number field set to 99XX. This will match the 9900 digits just received.

3.	The Incoming Call Route is set with the Destination of 777#. The # will be replaced by the XX part of the DDI number matched above. For this example 00 will set the destination as 77700.

Check the CLI received with the call for a one-X mobile user match

1.	The IP Office system has a system short code 777XX. Its settings are 777XX / N / FNE.

The short code uses the FNE feature. This causes the IP Office system to check that it has received an incoming CLI number with the call. The last 6 to 10 digits of that number are checked for a match against the Twinned Mobile Number or Forward Number of those users on the system who have been configured as Can have one-X Mobile Client.

3.	Once a match occurs the call proceeds using the identity of the user matched.

The appropriate one-X Mobile feature is provided to the user.

1.	The short code takes 777XX and then passes the value N to the FNE feature. Therefore in our example 77700 will pass the value 00.

2.	The value 00 matches the FNE feature Dial Tone (also called Idle Appearance Select). This feature causes the IP Office to return system dial tone to the user so that they can now dial the number they require as a call from the IP Office system.

Restrictions

•

Supported Phones and Phone Client Software
IP Office 4.2+ supports Avaya one-X Mobile Client on mobile cell phones that run Windows Mobile V5/V6 and Symbian Single-Mode (V4.0). For the regularly updated list refer to the Avaya one-X Mobile section of the Avaya support website (support.avaya.com). This same site is also the location of the client software files that need to be installed on the phone and how to transfer those files to the phone.

•	Each phone requires a settings file. That file is used to configure the features the user can access and the DID number that the phone should dial in order to access the feature.

•	Trunk Restrictions This feature is only supported on the IP500 and only on the following trunk types:

•	IP500 Universal PRI (Not on T1 robbed-bit and E1R2 channels set to Loop Start emulation).

•	IP500 BRI.

•	IP500 SIP (RFC2833).

•	Routing via trunks that do not support clearing supervision (disconnect detection) should not be used.

•

Users

•	One-X Mobile is an IP Office licensed feature using a Mobility Features license for each user.

•	It is only useable by users who have Can use one-X Mobile Client and Mobility Features enabled in the IP Office configuration.

•	The CLI provided on calls from their mobile cell phone to the IP Office must match the Twinned Mobile Number or Forwarding number set on the IP Office. At least 6 digits are required.

•

For user's setup for one-X Mobile Client, changes to their Mobile Twinning status made through the IP Office configuration or using a Twinning button are not reflected in the status of the Extension to Cellular icon on their mobile client. However, changes to the Extension to Cellular status made from the mobile client are reflected by the Mobile Twinning field in the IP Office configuration. Therefore for one-X Mobile Client users it is recommended that they control their Mobile Twinning status through the one-X Mobile Client rather than through a Twinning button.

Additional Documentation

The following guides include details of how to install and configure the software on the phones. These documents are available from the one-X Mobile client section of the Avaya support website (support.avaya.com).

Document	Doc Code
Avaya one-X Mobile Edition Device Compatibility List	327824
Avaya one-X Mobile Edition for S60 User Documentation	16-601288
Avaya one-X Mobile Edition for Windows Mobile 5 Pocket PC and Treo Edition Install, Admin and User Guide R4.0	16-601613
Avaya one-X Mobile Edition for Windows Mobile 5 Smartphone Edition User Guide	16-602323

Feature Name Extension (FNE) Features

The one-X Mobile client accesses IP Office features using DID numbers routed to IP Office short codes set to the FNE feature. The number set in the short code indicates the particular FNE feature required.

The table below lists the FNE features supported by IP Office. The settings file tag is the string used in the phone software settings file to associate a feature with a DID number.

Value	Function (Setting File Tag)
00	Dial Tone (IDLE_APPEARANCE_SELECT) - Provide IP Office dial tone to the user. Similar to Mobile Call Control.
01	Active Appearance Call Select (ACTIVE_APPEARANCE_SELECT) - Attempt a call acquire (steal) on the user's primary extension. If there is no active or ringing call to acquire, give IP Office dial tone.
02	Automatic Callback (AUTO_CALL_BACK_TOGGLE) - Set a ringback when free when calling an IP Office extension number that does not answer or returns busy.
04	Call Forwarding All Calls (CALL_FORWARDING_ALL_ACTIVATION) - Switch forward unconditional on.
05	Call Forwarding Busy (CALL_FORWARDING_BUSY_NO_ANSWER_ACTIVATION) - Switch forward on busy and forward on no answer on.
06	Call Forwarding Deactivation (CALL_FORWARDING_DISABLE) - Switch all forwarding off.
07	Call Park (CALL_PARK) - Park call on the IP Office using the user's extension ID.
08	Call Unpark (CALL_UNPARK) - Unpark a call parked using the user's extension ID.
09	Call Pickup Group (CALL_PICKUP_GROUP) - Call Pickup Any
10	Call Pickup Directed (CALL_PICKUP_DIRECTED) - Directed Call Pickup using the entered user or hunt group number.
12	Calling Party Number Block (CALLING_PARTY_NUMBER_BLOCK) - Make a call from IP Office with CLI withheld.
13	Calling Party Number Unblock (CALLING_PARTY_NUMBER_UNBLOCK) - Make a call from the IP Office with CLI allowed.
14	Conference on Answer (CONFERENCE_ON_ANSWER) - Make an additional call and add them to a conference.
15	Drop (DROP_LAST_ADDED_PARTY) - Drop last party added to a conference.
16	Exclusion (EXCLUSION) - Make the existing call private. Repeat to remove privacy from existing call.
17	Held Appearance Select (HELD_APPEARANCE_SELECT) - Pickup a held call on the user's primary extension.
18	Dial Tone (IDLE_APPEARANCE_SELECT) - Same as 00 - Dial Tone.
19	Off PBX Call Enable (OFF_PBX_ENABLE) - Switch the user's Mobile Twinning on.
20	Off PBX Call Disable (OFF_PBX_DISABLE) - Switch the user's Mobile Twinning off.
24	Send All Calls Enable (SEND_ALL_CALLS_ENABLE) - Do Not Disturb On.
25	Send All Calls Disable (SEND_ALL_CALLS_DISABLE) - Do Not Disturb Off.
26	Transfer On Hang Up (TRANSFER_ON_HANGUP) - Unsupervised transfer.
27	Transfer to Voicemail (TRANSFER_TO_COVERAGE) - Transfer the held IP Office call to the user's voicemail mailbox.
31	Used for Mobile Call Control.
32	Used for Mobile Direct Access.

Example Configuration Overview

In this example, two DID numbers are going to be used to allowed one-X Mobile users to access the FNE functions 00, 01 and 26. This will allows those users respectively to obtain IP Office dial tone, to acquire a call alerting on their normal extension and to transfer a call.

The DID numbers requested were 555 76769900, 555 76769901 and 555 76769926 with 4 digits being passed by the provided to the IP Office, ie. 9900, 9901 and 9926.

•	This example is made much simpler by using both a continuous DID range and one where the last two digits of the DID numbers match the IP Office FNE short code features required. This allows implementation using an single short code and a single incoming call route.

IP Office Configuration

IP Office one-X Mobile Client Licensing
Mobility Features licenses are required in the IP Office configuration for all the users that will be configured for any of the IP Office mobility features including one-X Mobile Client usage. The same single license also allows the user to use mobile twinning and mobile call control if required. Check that the configuration contain valid Mobility Features licenses.

2.	IP Office User Configuration For each user, the following must be set on the User \| Mobility tab.

•	Select Mobility Features.

•	Select Can have one-X Mobile Client.

•	Set their Twinned Mobile Number to match the CLI of calls from the device on which they will be using the one-X Mobile Client software. This match is used to determine the user for the FNE feature.

•	Digits are matched from right to left.

•	The match must be at least 6 digits. If either the CLI or the Mobile Twinned Number is less than 6 digits no match will occur.

•	Matching is done for up to 10 digits. Further digits are ignored. If either the CLI or Mobile Twinned Number is less than 10 digits, matching stops at that shorter length.

•	If multiple matches occur the first user in the configuration is used. IP Office Manager will warn against configuration where such a conflict may exist.

3.	FNE System Short Code This short code is used as the destination for calls received on the DID numbers requested for one-X Mobile usage.

•	Short Code: 777XX

•

Number: N

•	Feature: FNE

4.	Incoming Call Route An incoming call route is required to send the DID calls to the FNE short code. Since a continuous range of DID numbers has been requested, with end digits that match the feature required, this can be done with a single incoming call route entry in the IP Office configuration.

•	Incoming Number: 99XX

•	Destination: 777# The # matches any digits received for the XX part of the incoming number.

•	Other fields can be configured as required. For example using line group ID's to restrict one-X Mobile client access to those trunks known to support this feature.

one-X Mobile Client Configuration File

During installation of the one-X Mobile software, a settings files is installed on the phone. For Windows phones, the file is called settings.ini file, for Symbian single-mode phones the file is called setting.1xme file. For some phones, once the software has been installed, the settings file values can be changed through the phone interface.

Example Settings Files

Windows Mobile 'settings.ini'

Symbian 'settings.1xme'

Dialing Prefixes and Codes

PRE_IMS=Dial;

DID_PREFIX = 1555776;

INTERNATIONAL_DIRECT_DIAL_PREFIX = 011;

NATIONAL_DIRECT_DIAL_PREFIX = 1;

HOME_COUNTRY_DIAL_CODE = +1;

ARS_CODE = ;

EXTENSION_LENGTH = 3;

NATIONAL_NUMBER_LENGTH = 10;

USERS_EMERGENCY_NUMBERS = 112,999,911;

SETTINGS_PIN = 1234;

DID_PREFIX = 1555776;

INTERNATIONAL_DIRECT_DIAL_PREFIX = 011;

NATIONAL_DIRECT_DIAL_PREFIX = 1;

HOME_COUNTRY_DIAL_CODE = +1;

ARS_CODE = ;

EXTENSION_LENGTH = 3;

NATIONAL_NUMBER_LENGTH = 10;

USERS_EMERGENCY_NUMBERS = 112,999,911;

SETTINGS_PIN = 1234;

DDI Suffixes for Features

These are used with the DDI_Prefix above to complete the DDI number for a particular FNE feature (see the table of possible features above).

IDLE_APPEARANCE_SELECT = 9900;

ACTIVE_APPEARANCE_SELECT = 9901;

AUTO_CALL_BACK_TOGGLE = 9902;

DISABLE_AUTO_CALL_BACK_TOGGLE = 9903;

CALL_FORWARDING_ALL_ACTIVATION = 9904;

CALL_FORWARDING_BUSY_NO_ANSWER_ACTIVATION = 9905;

CALL_FORWARDING_DISABLE = 9906;

CALL_PARK = 9907;

CALL_UNPARK = 9908;

CALL_PICKUP_GROUP = 9909;

CALL_PICKUP_DIRECTED = 9910;

CALL_PICKUP_GROUP_EXTENDED = ;

CALLING_PARTY_NUMBER_BLOCK = 9912;

CALLING_PARTY_NUMBER_UNBLOCK = 9913;

CONFERENCE_ON_ANSWER = 9914;

DROP_LAST_ADDED_PARTY = 9915;

EXCLUSION = 9916;

HELD_APPEARANCE_SELECT = 9917;

OFF_PBX_ENABLE = 9919;

OFF_PBX_DISABLE = 9920;

SEND_ALL_CALLS_ENABLE = 9924;

SEND_ALL_CALLS_DISABLE = 9925;

TRANSFER_ON_HANGUP = 9926;

TRANSFER_TO_COVERAGE = 9927;

IDLE_APPEARANCE_SELECT = 9900;

ACTIVE_APPEARANCE_SELECT = 9901;

AUTO_CALL_BACK_TOGGLE = 9902;

DISABLE_AUTO_CALL_BACK_TOGGLE = 9903;

CALL_FORWARDING_ALL_ACTIVATION = 9904;

CALL_FORWARDING_BUSY_NO_ANSWER_ACTIVATION = 9905;

CALL_FORWARDING_DISABLE = 9906;

CALL_PARK = 9907;

CALL_UNPARK = 9908;

CALL_PICKUP_GROUP = 9909;

CALL_PICKUP_DIRECTED = 9910;

CALL_PICKUP_GROUP_EXTENDED = ;

CALLING_PARTY_NUMBER_BLOCK = 9912;

CALLING_PARTY_NUMBER_UNBLOCK = 9913;

CONFERENCE_ON_ANSWER = 9914;

DROP_LAST_ADDED_PARTY = 9915;

EXCLUSION = 9916;

HELD_APPEARANCE_SELECT = 9917;

OFF_PBX_ENABLE = 9919;

OFF_PBX_DISABLE = 9920;

SEND_ALL_CALLS_ENABLE = 9924;

SEND_ALL_CALLS_DISABLE = 9925;

TRANSFER_ON_HANGUP = 9926;

TRANSFER_TO_COVERAGE = 9927;

Enterprise Settings

SUB_MENU_NAME = My Company;

<Voicemail> = *17;

SUB_MENU_NAME = My Company;

<Voice Mail> = *17;

•	Do NOT modify the tag names shown before the equals signs.

•	Do NOT remove any tag rows. If a features is not being used or is unavailable leave the value between the '=' and ';' blank.

•	Do NOT remove the terminating semi-colon.

•	All values MUST go between the ‘=’ and ‘;’.

•	For those tags that match FNE features, the value should be the DID digits that will be passed to the IP Office for routing to the appropriate short code. This value is used in conjunction with the DID prefix to form the full telephone number.

•	The following tags MUST have values set (not necessarily those shown as examples below):

DDI_PREFIX = +1555776
INTERNATIONAL_DIRECT_DIAL_PREFIX = 011;

NATIONAL_DIRECT_DIAL_PREFIX = 1;

HOME_COUNTRY_DIAL_CODE = 1;

ARS_CODE = ;

EXTENSION_LENGTH = 3;

NATIONAL_NUMBER_LENGTH = 10;

USERS_EMERGENCY_NUMBERS = 112,999,911;

Configuration File Fields

•

LOCATION_NAME = ; for example 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 = ; for example 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 = ; for example INTERNATIONAL_DIRECT_DIAL_PREFIX = 011; This required tag specifies the international call prefix for your country.

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

•	HOME_COUNTRY_DIAL_CODE = ; for example HOME_COUNTRY_DIAL_CODE = 1; This required tag is the home country code.

•	ARS_CODE = ; for example ARS_CODE = 9; This optional tag set the ARS access code.

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

•	NATIONAL_NUMBER_LENGTH = ; for example 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 = ; for example USERS_EMERGENCY_NUMBERS = 911; This is a required tag and it specifies the numbers dialed for emergency.

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

© 2009 AVAYA
15-601011 Issue 23.p.-
07:07, 30 October 2009
(one_x_mobile_client.htm)

Performance figures, data and operation quoted in this document are typical and must be specifically confirmed in writing by Avaya before they become applicable to any particular order or contract. The company reserves the right to make alterations or amendments at its own discretion. The publication of information in this document does not imply freedom from patent or any other protective rights of Avaya or others. All trademarks identified by (R) or TM are registered trademarks or trademarks respectively of Avaya Inc. All other trademarks are the property of their respective owners.

Last Modified: 25/06/2009