Please enable JavaScript to view this site.

one-X Portal for IP Office Admin

For IP Office Release 10 and higher, the portal service is also installed by default on the IP Office Server Edition secondary server. This allows that secondary server to act as the portal server for users when, for some reason, the primary server is not available.

Portal resilience is supported in IP Office Server Edition Select mode. Portal resilience can also be configured when using an IP Office Application Server in place of the primary or secondary server's portal service.

On existing non-IP Office Server Edition Select mode systems that have then been switched to IP Office Server Edition Select mode, it may be necessary to restart the portal services for resiliency settings to become available. Similarly it may be necessary to restart the portal services after first configuring portal resiliency in the IP Office system configuration.

Resilience is only supported between primary and secondary servers running the same version of portal software.

During normal operation (both servers running and connected), user and administrator changes made on the primary server are automatically synchronized to the secondary server. However, during resilience, changes made on either server are not synchronized and may be lost when the servers return to normal operation.

Scheduled conferences are currently an exception to the above. Conferences scheduled on the primary do not occur when running in failover. Conferences scheduled on the secondary are lost when failback occurs.

Within the platform view (web control panel) of each server:

the active portal server is displayed as 'Available' (a green icon).

the passive portal server is displayed as 'Starting' (an amber icon).

Portal client applications such as one-X Portal Call Assistant are not automatically redirected. The user has to enter the address of the secondary server in order to login.

When portal resilience is configured:

On primary server portal failure
If the primary server's portal service stops for some reason, the portal service on the secondary server automatically becomes available.

Users who were logged into the portal on the primary are able to login again on the secondary server.

If the primary IP Office service is still running, those portal users are automatically redirected.

If the user has not previously accessed the secondary portal server, they may need to accept the security certificate or create an exception which will interrupt automatic re-connection.

The same applies for users who were logged into one of the portal clients such as the Outlook Plug-in

New users wanting to login will have to use the address of the secondary server.

On primary server IP Office failure:
If the primary server's IP Office service stops for some reason, portal services are automatically transferred to the secondary server as above.

When IP Office core is not up, users belonging to that IP Office core cannot update or delete personal contacts from the portal directory gadget.

On network failure:
If the network connection between the primary and secondary server fails for some reason, both portal servers become active and can be logged into. Again user and admin changes on secondary portal server are not copied to primary when the network connection recovers. This is referred as "Standalone Mode".

On primary server portal recovery:
When the primary server's portal service is available again, the portal service on the secondary server stops supporting login.

Users who were logged into the portal on the secondary are automatically re-directed to login again on the primary server.

Users who were logged into one of the portal clients such as the Outlook Plug-in are automatically connected to the primary server.

New users wanting to log in are redirected to the primary.

On primary server IP Office recovery:
When the primary server's IP Office service is available again, portal service support also returns to the primary server as above.

 

To configure resilience:

1.Enable Centralized CTI Link Mode
Both portal servers must be set to use centralized CTI link mode. That is the default for a new installation but must be manually enabled for existing systems upgraded to IP Office Release 10 or higher.

a.Centralized CTI link mode is enabled through the Central CTI Link menu.

b.If the setting is changed, the portal service must be restarted for the change to take effect.

c.The setting must be enabled on both the primary and secondary servers.

2.Enable Portal Server Resilience
The primary portal server needs to be configured for resiliency through its Resilience Configuration menus.

3.Restart the Portal Services
If any changes are made in the steps above.

4.Enable Portal Backup on Network Trunks
The SCN trunks between the primary and secondary IP Office severs need to have the setting for portal backup enabled.

a.Using IP Office Manager, load the configuration from the IP Office Server Edition IP Office systems.

b.In the settings of the primary, locate the IP Office line from the primary to the secondary IP Office system.

c.On the Line tab, in the SCN Resiliency Options, check that Supports Resiliency and Backs up my one-X Portal are selected.

d.Save the configuration changes.

 

 

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.

© 2021 AVAYA
Issue 17.a.-
Friday, October 29, 2021