Configuration settings

Using both internal and mobile twinning

• 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.

Simultaneous

Internal Twinning

Mobility Features

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. When used to make a call from the IP Office system, the number is subject to short code processing and must include any external dialing prefix necessary. The IP Office also uses this number to control access to mobile call control and FNE functions. The IP Office allows access only if the caller ID matches the Twinned Mobile Number of an IP Office user. If matched, the user settings control operation of the mobile call control/FNE features.
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: If the twinning number is a switched off mobile device, the mobile service provider may immediately answer the call using their voicemail service. That creates a scenario where the user's main extension does not ring or rings 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 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: Mobile Dial Delay is not applied. Hunt group calls (all types) are twinned if Hunt group calls eligible for mobile twinning is enabled. The user's idle time is reset for each externally twinned call answered. Note the IP Office automatically treats calls twinned over analog and analog emulation trunks as answered. When the user's Mobile Time Profile is not active, calls are treated the same as the user was logged out user with no twinning. Callback calls initiated by the user will ring the twinned number. Other users can set automatic callback to the user. The twinned user's busy/free state is tracked for all calls through the IP Office system. The user's bridged appearance buttons do not alert. Their coverage appearance buttons will continue to operate. The BLF/user button status shown for the user is: For calls alerting or in progress through the IP Office system to the twin, the user status shows alerting or in-use. The user shows as busy/in-use if they such a call on hold and they have Busy on Held enabled. If the user enables DND through Mobile Call Control, their status shows as DND/busy. Calls from the IP Office system dialed direct to the user's twinned destination rather than redirected by twinning do not change the user's status.
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: The user calls the IP Office system and then hangs up. The IP Office system calls the user's caller ID number. When answered, the IP Office provide dial tone for the user to make a call.