Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
One-x mobile
- Thread starter oldtimers
- Start date
IPOfficeIreland
Technical User
straight from the manual...
IP500 systems running IP Office 4.2+ support the Avaya one-X Mobile Client on Windows and Symbian mobile cell phones. Using a range of DID numbers preprogrammed against phone controls, they can then activate and use various IP Office functions. The caller's incoming CLI is checked against the mobile twinning or forwarding number of users configured for one-X Mobile operation.
· 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 following trunk types:
· IP500 Universal PRI (Not on T1 robbed-bit and E1R2 channels set to Loop Start emulation).
· IP500 BRI.
· SIP (RFC2833)
· Routing via trunks that do not support clearing supervision (disconnect detection) should not be used.
· 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.
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.
03
Automatic Callback Cancel (DISABLE_AUTO_CALL_BACK_TOGGLE) - Cancels a pending automatic callback if set.
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 01 - 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.
30
Single DDI - Not supported.
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
1. 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: *77XX
· 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: *77#
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
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.
Windows Mobile settings.ini File
Symbian settings.1xme File
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;
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;
SUB_MENU_NAME = My Company;
<Voicemail> = *17;
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;
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;
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;
© 2008 AVAYA
15-601011 Issue 22.k.-
09:12, 09 September 2008
(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.
mk
MSITStore:C:\PROGRA~1\AVAYA\IPOFFI~1\MANAGER\Manager.chm::/one_x_mobile_client.htm
Last Modified: 07/05/2008
IP500 systems running IP Office 4.2+ support the Avaya one-X Mobile Client on Windows and Symbian mobile cell phones. Using a range of DID numbers preprogrammed against phone controls, they can then activate and use various IP Office functions. The caller's incoming CLI is checked against the mobile twinning or forwarding number of users configured for one-X Mobile operation.
· 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 following trunk types:
· IP500 Universal PRI (Not on T1 robbed-bit and E1R2 channels set to Loop Start emulation).
· IP500 BRI.
· SIP (RFC2833)
· Routing via trunks that do not support clearing supervision (disconnect detection) should not be used.
· 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.
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.
03
Automatic Callback Cancel (DISABLE_AUTO_CALL_BACK_TOGGLE) - Cancels a pending automatic callback if set.
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 01 - 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.
30
Single DDI - Not supported.
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
1. 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: *77XX
· 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: *77#
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
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.
Windows Mobile settings.ini File
Symbian settings.1xme File
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;
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;
SUB_MENU_NAME = My Company;
<Voicemail> = *17;
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;
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;
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;
© 2008 AVAYA
15-601011 Issue 22.k.-
09:12, 09 September 2008
(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.
mk
MSITStore:C:\PROGRA~1\AVAYA\IPOFFI~1\MANAGER\Manager.chm::/one_x_mobile_client.htmLast Modified: 07/05/2008
mattKnight
Programmer
Oldtimers
You can't. Onex is only supported on the IP500 platform, largely to do with the codec on the new ISDN cards
TT
That's a very long cut and paste, just to say "you can't"
Take Care
Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
You can't. Onex is only supported on the IP500 platform, largely to do with the codec on the new ISDN cards
TT
That's a very long cut and paste, just to say "you can't"
Take Care
Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
IPOfficeIreland
Technical User
I know Matt, just making the point that if Oldtimers simply pressed Help the info is right there in front of him.
This site used to be for issues and workarounds but seems to be getting more and more like an alternative to a manual.
This site used to be for issues and workarounds but seems to be getting more and more like an alternative to a manual.
mattKnight
Programmer
TT
fair comment!
Take Care
Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
fair comment!
Take Care
Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
I think that TheTaker did not see it ACA - Implement IP Office
ACS - Implement IP Office
ACA - Implement IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
IPOfficeIreland
Technical User
ha ha tlpeter, sure how oculd i miss it - the 1st line says "IP500 Systems..."
greginchina
Technical User
- Jan 7, 2009
- 7
Hi All,
first time on tek-tips.
We have just set up Avaya IP office and have only yesterday set up one-x mobile client on my phone.
I have encountered a problem and wondered if anyone had a solution.
In China all mobile numbers begin with a 1 (eg, 13000000000). If calling from a mobile you just need to dial that number or of course you can add the international prefix +86 infront. However if calling from a landline you can only dial the number directly if it is a local mobile. If it is from another city or province you have to add a leading zero. There is no indication in the number itself if it is a local mobile number.
I tried calling a non-local mobile through one-x mobile and was given the network message "please add a zero". If I add zeros to these numbers in my mobile phonebook I am unable to dial without using one-x mobile and am unable to send SMS messages at all.
Other than creating 2 entries for each mobile number in my phonebook is there some way for the IP office to add a zero to non-local mobile numbers (some number or code that I can add as a prefix or suffix to the number in the phonebook that the IP office will pick up on and realise its a non-local mobile but the mobile network will ignore and dial the correct number as normal)?
Thanks in advance.
Greg.
first time on tek-tips.
We have just set up Avaya IP office and have only yesterday set up one-x mobile client on my phone.
I have encountered a problem and wondered if anyone had a solution.
In China all mobile numbers begin with a 1 (eg, 13000000000). If calling from a mobile you just need to dial that number or of course you can add the international prefix +86 infront. However if calling from a landline you can only dial the number directly if it is a local mobile. If it is from another city or province you have to add a leading zero. There is no indication in the number itself if it is a local mobile number.
I tried calling a non-local mobile through one-x mobile and was given the network message "please add a zero". If I add zeros to these numbers in my mobile phonebook I am unable to dial without using one-x mobile and am unable to send SMS messages at all.
Other than creating 2 entries for each mobile number in my phonebook is there some way for the IP office to add a zero to non-local mobile numbers (some number or code that I can add as a prefix or suffix to the number in the phonebook that the IP office will pick up on and realise its a non-local mobile but the mobile network will ignore and dial the correct number as normal)?
Thanks in advance.
Greg.
intrigrant
Systems Engineer
One-X does not work on a 406:
Avaya one-X Mobile Client Support
IP Office 4.2 supports release 4.0 of the Avaya one-X Mobile Client “Single Mode” operation, in conjunction with mobile technology Symbian Single-Mode Version 4.0 and Windows Mobile 6 technology. This provides a graphical interface for call control and allows a one-number service for both incoming and outgoing calls.
Avaya one-X Mobile builds on the functionality of the IP Office 4.2 by providing a family of mobile clients designed to further enhance the productivity of mobile workers. The family of Avaya one-X Mobile clients provides quick access to office phone functionality via an intuitive graphical user interface. The clients support devices ranging from high end smart phones to lower end feature phones to support most business environments, independent of the mobile devices deployed.
This feature is only supported through the following trunk types on an IP Office 500:
• IP500 PRI-U (single or dual) daughter cards
• IP500 Dual or Quad BRI daughter cards
• SIP trunks (RFC 2833)
• This feature requires one instance of the Mobility License as described below for each configured user.
Avaya one-X Mobile Client Support
IP Office 4.2 supports release 4.0 of the Avaya one-X Mobile Client “Single Mode” operation, in conjunction with mobile technology Symbian Single-Mode Version 4.0 and Windows Mobile 6 technology. This provides a graphical interface for call control and allows a one-number service for both incoming and outgoing calls.
Avaya one-X Mobile builds on the functionality of the IP Office 4.2 by providing a family of mobile clients designed to further enhance the productivity of mobile workers. The family of Avaya one-X Mobile clients provides quick access to office phone functionality via an intuitive graphical user interface. The clients support devices ranging from high end smart phones to lower end feature phones to support most business environments, independent of the mobile devices deployed.
This feature is only supported through the following trunk types on an IP Office 500:
• IP500 PRI-U (single or dual) daughter cards
• IP500 Dual or Quad BRI daughter cards
• SIP trunks (RFC 2833)
• This feature requires one instance of the Mobility License as described below for each configured user.
greginchina
Technical User
- Jan 7, 2009
- 7
Sorry, but I don't really get the reply. We are using IP office 500 and one-x does work as i am currently using it. was just wondering if there was a way to add a zero to non-local mobile numbers when calling through the one-x mobile client.
@oldtimers
You could get a QuesCom Q300/Q400 for the IPO406
___________________________________________
It works! Now if only I could remember what I did...
___________________________________________
You could get a QuesCom Q300/Q400 for the IPO406
___________________________________________
It works! Now if only I could remember what I did...
___________________________________________
- Status
Similar threads
- Locked
- Question