User's Manual

Avaya Branch Gateway Manager 10.0 Page 705
15-601011 Issue 29r (Friday, November 02, 2012)B5800 Branch Gateway
Telephone Features: User Directory Access
9.3 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.
· Trunk Restrictions
This feature is only supported on the systems on the following trunk types:
· IP500 Universal PRI (Not on T1 robbed-bit and E1R2 channels set to a Type/Line Signalling Type that do
not support disconnect clear detection. For example, not on a T1 robbed-bit channel 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.
· 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.
· 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.
Mobile Call Control Features and FNE Services
Mobile call control uses a short code set to invoke an FNE service. See one-X Mobile Client for the full list of the
codes, the code relevant to mobile call control are summarized below.
· FNE 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.
· FNE 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 .
· FNE 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.
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.
709
707
708
436