IP Office Server Edition R11 Resiliency

[Travis Harper]

I am attempting to setup IP Office resiliency.

Both Primary and Secondary servers are online.
Failover is working, but none of the users/groups/shortcodes etc.. from he primary are on the secondary.
When devices failover, I get dalton, but can not place any calls as the secondary does not have any replication from the primary.

Under Resiliency Administration, I checked the box to Backup Primary server IP phones, hunt groups, voicemail and one-X Portal on the Secondary server.

When I press save I get the following error.
System resiliency update has failed. Reason: null: null, 401:UnAuthorized: 192.168.x.x

I must have missed a step someplace.
When I was first adding the secondary, it was asking for a web socket password along with the server IP.
I assumed that field was asking me to supply or create a password... perhaps I was supposed to have created a user ahead of time and enter that password in the field instead?

Any suggestions would be appreciated.

 

[IPOLackey]

Right, a little bit of the theory may help.

So your secondary server shouldn't show any users/groups in a config as these should all be homed on the Primary. checking the Back-up my phones takes care of this part.

However you do need to configure SIP trunks, ShortCodes, ARS and ICR's on the secondary. This all depends on what you have for your SIP trunks and whether your provider can route the traffic in the event of a failover.

The reason why these are not duplicated from the Primary is because the secondary may have a different SIP provider for resiliency and hence may need different routing/shortcodes. IE in a DR scenario you may want inbound calls to go to a different IVR message stating there are technical difficulties.

 

[Travis Harper]

Thank you IPOLackey.

That explains a lot, and it makes sense.

I guess, now all I have to do is sort out that error I'm getting when I attempt to enable Resiliency.

Travis

 

[IPOLackey]

Just make sure your passwords match on each end of the line, assuming that the Primary has transport type of WebSocket Server, and the Secondary is WebSocket Client.

 

[snowman50]

Are they showing Bothway on the solution display field when you select Solution.

Also look at monitor.
Look at SCN community network and you should see the other system as GREEN.
It should show the system name as Fallback.

You can do the resilience from the solution page instead of WEB interface.
Try that.

When you say you can’t make calls..is that external calls or you can’t make internal calls as well.
Make sure the 2 systems have the same user rights name on both servers

You should have line 99999 and 99998 between the servers

Secondary voicemail set as Centralised and 99999

Monitor on the Secondary will show the extension as Guest licence and R on phones

 

[Travis Harper]

Thank you Snowman50.

Yes, under Solution I see Bothway, and Green
Line 1 on Primary Server is set to WebSocket, with Outgoing GroupID 99998 with Gateway Address set to IP of Secondary Server

Secondary server only has Line 1 as it is set to WebSocket, with Outgoing Group ID 99999 with Gateway IP off Primary Server.


When Failover is takes place ( I unplug the ethernet from Primary Server ), the phones fail over to secondary, and I get dialtone, and can place extension to extension calls. I can not place outbound calls when failed over. Obviously since the other outgoing sip lines are on the Primary server.

Also the shortcodes created on the Primary for outbound dialling are not present on the secondary server.

I am thinking this is because I have had the Primary server for a year, before I added the secondary, and those shortcakes were not configured as common shortcodes.

I guess I expected that the Lines, and Shortcodes would replicate on the secondary, but as IPOLackey explained, I will have to manually add those items to the secondary server.

All in all, I suppose it's working as intended.