How does OneX Portal resiliency work?

[JayNEC]

You have to set the XMPP domain name and it has to be resolvable, eg you are pointing it to an IP address. In the event of a failure, how does the client connect to the secondary OneX portal? The Client still has the XMPP domain name configured but now that DNS entry is pointing at a server that's down.

New England Communications

http://www.necomm.com

 

[nitinbh]

From IP Office Web Manager (or IP Office Manager):
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. Repeat the step above for the IP Office line from the secondary to the primary IP Office system.
e. Save the configuration changes.

Then from One-X Admin:
Enable Resiliency
If selected, enables portal resiliency and displays the additional fields required to define the addresses of the other servers in the resiliency setup and the role of the servers. If resiliency is not enabled, then the portal service on secondary server is automatically stopped and cannot be manually restarted.
- This one-X Portal: Define the role of this server.
- Primary:
Select if this server is intended to act as the primary portal server.
- Secondary
Select if this server is intended to act as the backup/fallback portal server if the primary portal is not available.
- FQDN/IP Address
Use this table to enter the fully qualified domain names or IP addresses of the all the portals and IP Office servers in the resiliency set.


Also the Central CTI Link should be enabled from one-X Admun-> Configuration.


The change to any of the above one-X settings require restart of both One-X Portal systems. The change from Web Manager requires reboot of IP office (both Primary and Secondary).

 

[JayNEC]

Yeah, I've got access to the docs too. This still doesn't explain the discrepancy on the client side unless I'm misunderstanding something.

I have to have a single XMPP domain name defined in the OneX Portal. I use that XMPP domain to login, and that XMPP domain name (FQDN) resolves to the OneX Portal server.

Right now, to get to a different OneX Portal I have to use a different FQDN which then doesn't match the XMPP domain name anymore.

Does the primary OneX portal server tell the client about the alternate FQDN's available to register to? And then (in the event of losing the primary) the client tries the other available OneX portal servers but with the original XMPP domain name? If that's the case (sort of like alternate gatekeepers with IP Phones), what if you restart the client and the original OneX portal isn't there anymore?