AVAYA DOCUMENTATION CENTER
Find answers to your technical questions and learn how to use our products
Administering Avaya IP Office with Web Manager
Mobile Call Control
Mobile call control is only supported on digital trunks, including SIP trunks. It allows a user receiving a call on their twinned device to access system dial tone and then perform dialing action including making calls and activating short codes.
After answering a twinned call, the Mobile Call Control user can dial ** (within 1 second of each other) to place that call on hold and instead get dial tone from the system. Any dialing is now interpreted as if the user is logged into a basic single line extension on the system using their user settings. That also include user BLF status indication.
To use these features the user must be configured to support mobile call control.
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 system cannot prevent use of these features by caller's who present a false caller ID that matching that of a user configured for access to this feature.
Trunk Restrictions
Mobile call control is only supported on systems with trunk types that can give information on whether the call is answered. Therefore, mobile call control is not supported on analog or T1 analog trunks. All other trunk types are supported (ISDN PRI and BRI, SIP (RFC2388), H323).
Routing via trunks that do not support clearing supervision (disconnect detection) should not be used.
DTMF detection is applied to twinned calls to a user configured for this feature. This will have the following effects:
DTMF dialing is muted though short chirps may be heard at the start of any DTMF dialing.
DTMF dialed by the user will not be passed through to other connected equipment such as IVR or Voicemail.
Mobile Call Control Features and FNE Services
Mobile call control uses a short code set to invoke an FNE service. The codes relevant to mobile call control are summarized below.
FNE |
Description |
|---|---|
31 |
Mobile Call Control This code allows a user called or calling the system to invoke mobile call control and to then handle and make calls as if they were at their system extension. |
32 |
Mobile Direct Access Mobile direct access FNE32 immediately redials on switch the DDI digits received with the call rather than returning dial tone and waiting for DTMF digits as with FNE31 . |
33 |
Mobile Callback Mobile callback allows the user to call the system and then hang up. The system will then make a call to the user's CLI and when answered, provide them with dial tone from the system to make calls. |
35 |
Simplified Mobile Call Control In addition to the Mobile Call Control feature that enables your mobile to make and handle calls as if your are using your extension, this Simplified Mobile Call Control FNE 35 clears the dial tone when the call recipient ends the call. The dial tone is provided on the mobile phone for fresh calls after the current call is cleared. |
36 |
Simplified Mobile Direct Access In addition to the Mobile Direct Access feature, the Simplified Mobile Direct Access FNE36 clears the dial tone when the call recipient ends the call. |
37 |
Simplified Mobile Callback In addition to the Mobile Callback feature that enables your mobile to get call back from the system and lets you use the dial tone for making and handling calls, this Simplified Mobile Callback FNE 37 clears the dial tone when the call recipient ends the call. The dial tone is provided on the mobile phone for fresh calls after the current call is cleared. |
The codes relevant to mobility are summarized in the table.
FNE Number |
Feature |
|---|---|
00 |
System Dial Tone |
01 |
Steal Call |
02 |
Auto Call Back |
04 |
Forward All Calls |
05 |
Forward Busy and No Answer Calls |
06 |
Call Forward Disable |
07 |
Park Call |
08 |
Call UnPark |
09 |
Pick Up Group |
10 |
Directed Call Pick Up |
12 |
Withheld CLI (To External Calls off IPO) |
13 |
Enable CLI (To External Calls off IPO) |
14 |
Conference Add |
15 |
Drop Call |
16 |
Private Call (cannot be intruded or recorded) |
17 |
Held Appearance Select |
18 |
Same as FNE 00–Dial Tone Appearance (a=) |
19 |
Enable Twinning |
20 |
Disable Twinning |
24 |
DND On |
25 |
DND Off |
26 |
Blind Transfer |
27 |
Transfer to Voicemail |
Using Mobile Call Control
In addition to using ** to access mobile call control, the user has access to the following additional controls:
Clearing a Call: *52 It may be necessary to clear a connected call, for example after attempting a transfer and hearing voicemail or ringing instead. To do this dial ** for dial tone and then *52 (this is a default system short code and can be changed if required).
Return to Dial Tone: ## Return to dial tone after getting busy, number unobtainable or short code confirmation tones from the system.
Enabling Outgoing Mobile Call Control
Configure the user for Mobile Twinning and Mobile Call Control On the User | Mobility tab do the following:
Enable Mobility Features for the user.
Set the Twinned Mobile Number for the user's twinned calls destination.
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. Manager will warn against configuration where such a conflict may exist.
Select Can do Mobile Call Control.
On systems with some unsupported trunk types, further changes such as Outgoing Group ID, system shorts codes and ARS may be necessary to ensure that calls to the mobile twinned numbers are only routed via trunks that support mobile call control.
Incoming Mobile Call Control
The system can be configured to allow Mobile Call Control users to use this function when making an incoming call to the system. This requires the user to make the incoming call from the same CLI as their Mobile Twinning Number (even if they do not actually use Mobile Twinning).
The call will be rejected:
If the caller ID is blank or withheld.
If the caller ID does not match a Twinned Mobile Number of a user with Can do Mobile Call Control enabled.
If the call is received on a trunk type that does not support Mobile Call Control.
Enabling Incoming Mobile Call Control
On the User | Mobility tab do the following:
Enable Mobility Features for the user.
Set the Twinned Mobile Number to match the CLI of the device from which the user will be making calls.
Select Can do Mobile Call Control.
Add a FNE Short Code In the system short codes section of the configuration add a short code similar to the following. Key points are the use of the FNE Service feature and the Telephone Number value 31.
Short Code: *89
Feature: FNE Service
Telephone Number: 31
Add an Incoming Call Route for the user Create an incoming call route that matches the user's CLI and with the FNE short code created above as its destination.
On systems with some unsupported trunk types, further changes such as Incoming Group ID changes may be necessary to ensure that only calls received on trunks that support Mobile Call Control are routed to this short code.