Find answers to your technical questions and learn how to use our products
Search suggestions:
Find answers to your technical questions and learn how to use our products
Search suggestions:
Navigation: User | Mobility
The
symbol indicates that the setting can also be set by the user rights with which the user is associated. The user rights can be controlled by a time profile selected as the user's Working Hours Time Profile setting.
These settings are mergeable. Changes to these settings do not require a reboot of the system.
Twinning allows the IP Office to present a user's calls to both their main phone and another extension or number. The IP Office system supports two modes of twinning:
Internal |
Mobile |
|
|---|---|---|
Twinning Destination |
Internal extensions on the same IP Office. |
External numbers only. |
Supported in |
All locales. |
All locales. |
License Required |
The primary phone user must be a licensed user. |
Yes |
For IP Office R11.1.3 and higher, you can configure both Internal Twinning and Mobile Twinning for Avaya Workplace Client users:
The Avaya Workplace Client users can switch between internal and mobile twinning using the client's Incoming Call Features menu.
When the Avaya Workplace Client user selects mobile twinning, the internal twinning extension temporarily reverts to its original extension number. Therefore, Avaya recommend restricting the internal twin extension to internal calls when not twinned.
These settings apply to the operation of simultaneous clients.
Field |
Description |
|---|---|
Coverage Delay (secs) |
Default = 0 seconds. Range= minimum 0 seconds to maximum 15 seconds. Sets the delay between calls alerting on the user's main telephony device/client and then also alerting their MS Teams client. |
MS Teams URI |
The user's telephony URI for MS Teams. The maximum length of the URI is 161 characters. For more details, see the Deploying MS Teams Direct Routing with IP Office manual. This field is read-only if the Auto Populate MS Teams Data setting (System > Telephony > MS Teams) is enabled. |
Select this option to enable internal twinning for a user. Internal twinning is not supported during resilience.
Field |
Description |
|---|---|
Twinned Handset |
Default = Blank. This drop-down list is used to select twinned phone. Supported internal twining destinations must:
If the list is grayed out, the user is a twinning destination and the main phone to which it is twinned is displayed. All User | Mobility fields are grayed out for unlicensed users. |
Maximum Number of Calls |
Default = 1. Sets the number of calls the user can have internally twinned at the same time:
|
Twin Bridge Appearances |
Default = Off. Set whether calls alerting on bridged appearance buttons on the main phone also alert on the twinned phone. |
Twin Coverage Appearances |
Default = Off. Set whether calls alerting on coverage appearance buttons on the main phone also alert on the twinned phone. |
Twin Line Appearances |
Default = Off. Set whether calls alerting on line appearance buttons on the main phone also alert on the twinned phone. |
If enabled, this option allows any of the mobility features to be enabled for the user.
Field |
Description |
|---|---|
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. |
Fallback Twinning |
Default = Disabled When enabled, if the user’s main extension is unreachable, the IP Office redirects their calls to the Twinned Mobile Number even if Mobile Twinning is disabled. Fallback Twinning does not use the Mobile Dial Delay. |
Twinned Mobile Number |
Default = Blank. This field sets the external destination number for mobile twinned calls.
|
Twinning Time Profile |
Default = <None> (Any time) This field allows selection of a time profile during which mobile twinning is used. |
Mobile Dial Delay |
Default = 2 seconds This setting controls how long calls alert at the user's main extension before also alerting at the twinned number. You can use this setting at the user's request, however you may also need to use it in some scenarios. For example:
|
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 |
Twin When Logged Out |
Default = Off. If enabled, if the user logs off their main extension, calls to that extension will still alert at their twinned number rather than immediately going to voicemail or busy. When logged out but twinned:
|
one-X Mobile Client |
Default = Off. Not supported with R11.1 and higher. |
Mobile Call Control |
Default = Off. This feature 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. See Mobile Call Control. |
Mobile Callback |
Default = Off. Mobile callback allows the user to make calls from the twinned number using the IP Office to route the calls. See Mobile Call Control. When used:
|