User's Manual
Avaya Branch Gateway Manager 10.0 Page 301
15-601011 Issue 29r (Friday, November 02, 2012)B5800 Branch Gateway
Configuration Settings: User
Usability
· Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings
A symbol indicates that the setting can also be set and locked within a set of user rights with which the user is
associated using the Working Hour User Rights and Out of Hours User Rights settings. The user rights
applied can be controlled by a time profile selected as the user's Working Hours Time Profile setting. The effect
of the user rights can be displayed using the User Rights View control.
· Mobility Features:
If enabled this option allows any of the mobility features to be enabled for the user.
· Mobile Twinning:
If selected, the user is enable for mobile twinning. The user can control this option through a Twinning
programmable button on their a phone.
· For user's setup for one-X Mobile Client, changes to their Mobile Twinning status made through the
system 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 system 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.
· Twinned Mobile Number: Default = Blank.
This field sets the external destination number for mobile twinned calls. It is subject to normal short code
processing and should include any external dialing prefix if necessary. For users of one-X Mobile Client and
or Mobile Call Control the number in this field is used to match the users setting to the incoming CLI.
· Twinning Time Profile: Default = <None> (Any time)
This field allows selection of a time profile during which mobile twinning will be used.
· Mobile Dial Delay: Default = 2 seconds
This setting controls how long calls should ring at the user's primary extension before also being routed to
ring at the twinning destination number. This setting may be used at the user's choice, however it may also be
a necessary control. For example, if the twinning number is a mobile device that has been switched off, the
mobile service provider may immediately answer the call with their own voicemail service. This would create a
scenario where the user's primary extension does not ring or ring only briefly.
· Mobile Answer Guard: Default = 0 (Off). Range = 0 to 99 seconds.
This control can be used in situations where calls sent to the twinned destination are automatically answered
by a voicemail service or automatic message if the twinned device is not available. If a twinned call is
answered before the Mobile Answer Guard expires, the system will drop the call to the twin.
· Hunt group calls eligible for mobile twinning: Default = Off
This setting controls whether hunt group calls ringing the user's primary extension should also be presented to
the mobile twinning number.
· Forwarded calls eligible for mobile twinning: Default = Off
This setting controls whether calls forwarded to the user's primary extension should also be presented to the
mobile twinning number.
· Twin When Logged Out: Default = Off.
If enabled, if the user logs off their primary extension, calls to that extension will still alert at their twinned
device rather than going immediately to voicemail or busy.
· When logged out but twinned, Mobile Dial Delay is not applied.
· Hunt group calls (all types) will be twinned if Hunt group calls eligible for mobile twinning is
enabled. When this is the case the user's idle time is reset for each externally twinned call answered.
Note that calls twinned over analog and analog emulation trunks are automatically treated as answered.
· When the user's Mobile Time Profile, if configured, is not active they will not get twinning calls. Calls
will be treated the same as the user was logged out user with no twinning.
· Callback calls initiated by the user will mature to the Twinned Mobile Number. It will also be possible to
initiate Automatic Callback to the user with external twinning and their busy/free state will be tracked for
all calls via the system.
· Any Bridged Appearance set to the user will not alert. Coverage appearance buttons for the user will
continue to operate.
· The BLF/user button status shown for a logged out user with Logged Off Mobile Twinning is as follows:
389
271 271
369 271
271
642
709
705