Please enable JavaScript to view this site.

Using one-X Portal

When making and answering calls using the one-X Call Assistant, you can use this feature to automatically pop the full one-X Portal client in a browser window. This may be useful to carry out further actions on the call or get additional information.

The screen pop uses a minimal version of your default browser. That is, a browser window without the usual toolbars and buttons so more compact that normal.

Outlook Popping

You can also set the system to pop the Outlook address book contact cards depending on the caller line identity of the caller and/or the number that you dial. This feature requires Outlook to be running.

The system supports the Outlook contact pop feature for the following platforms:

Outlook Versions:

Outlook 2016, Outlook 2109, Office 365 thick client.

Operating Systems:  

Windows 10, Windows 11

To configure screen popping:

1.In the notification area, right-click the ca icon connected icon and select Settings.

2.Select Screen Popping. Enable the settings that you would like to set.

Fields

Description

Enable CA Popping

Enables screen popping when selected. The options below are then used to select when popping occurs and the type of popping.

Pop on caller line identity

Pop the one-X Portal window for incoming calls. If Pop Outlook is also selected, the Outlook contact card is popped if the caller ID of the caller matches an Outlook Address Book contact.

Pop on Outdial

Pop the one-X Portal window for outgoing calls. If Pop Outlook is also selected, the Outlook contact card is popped if the number you dial matches an Outlook Address Book contact.

Pop Outlook

Pop Outlook address book contacts using the settings above. This feature requires Outlook to be running.

3.Click OK.

 

 

Performance figures, data and operation quoted in this document are typical and must be specifically confirmed in writing by Avaya before they become applicable to any particular order or contract. The company reserves the right to make alterations or amendments at its own discretion. The publication of information in this document does not imply freedom from patent or any other protective rights of Avaya or others. All trademarks identified by ™, ® or © are registered trademarks or trademarks respectively are the property of their respective owners.

Use of this site indicates acceptance of its cookies and analytics, and acceptance of the Avaya privacy policy.

© 2023 AVAYA
Issue 18.a.-
Wednesday, January 4, 2023