R10 Server Edition Select - 1100 Series resiliency

[MDoherty66]

R10 supports SIP resiliency, in the docs it states that the 1100 series sets need to be "manually configured" for failover server, but surely they can't mean you need to manually set the failover ip at the set itself can they? I've tested failover to the secondary server as it stands, and the 9600 series phones obviously fail over flawlessly, but nothing on the 1100 series sets at all.

Has anyone had any experience with this? Customer will be re-using around 200 1100 series sets, so manually configuring the phones at the set is a no go.

Thanks!

 

[sizbut]

Yeph, somewhere in the phone menus you can set two SIP gateway addresses and that's what you need to do. It might also be doable by DHCP options or settings file, but as you say such awful phones once converted to IP Office operation I've never looked any further than getting them working with one IP Office.

Stuck in a never ending cycle of file copying.

 

[sizbut]

Being a bit bored at watching the current file transfers, I dug out an old 1230 and plugged it in. If you go into Settings | Server Settings and select the Domain that the phone is currently using, you'll find that you can set two sets of SIP registrar information, S1 and S2.

So once you have IP phone resilience configured in your IP Office systems, you need to set the S1 to the phones normal registrar as per a normal install and then also configure the S2 fields but with the settings for whichever system is set to support the phone during failover.

[At least that's my impression, if time allows I'll get the 1230 off the Preferred Edition system its currently on and onto my Server Edition primary/secondary pair to see if that theory actually works]

Stuck in a never ending cycle of file copying.

 

[sizbut]

...and yes, tested it now and it works doing the above.

And unlike my 9620 that stayed registered with the secondary once the primary was reconnected to the network, the 1230 was still polling for its S1 server even though registered with S2 and went back to S1 (the primary) immediately it was available again rather than waiting the 10 minutes that the 9620 did.




Stuck in a never ending cycle of file copying.

 

[MDoherty66]

Thanks for the reply!

I too was able to get the phone to failover using S2 manually configured on the phone, just wondering if there is a way to do this in bulk, as I'm looking at needing to add it to roughly 200 phones.

 

[tlpeter]

Isn't that phone looking for some kind of settings file while it boots?

BAZINGA!

I'm not insane, my mother had me tested!

 

[MDoherty66]

Typically it would look for an 1120eSIP.cfg or 1140eSIP.cfg file from the TFTP Server, but in the case of using these phones on the IP Office (From what I've read), everything is auto-generated by the IP Office and can't (shouldn't?) be modified.

 

[sizbut]

Well said. From the 1120eSIP.cfg file (just point your browser at the IP Office's IP address and ask for the file) it also asks for 11xxsettings.txt and looking in that is contains all the settings for S1 and S2 fields. You can save those auto-generated files, edit them and then put them on the server. Yes it might put you in an 'unsupported' scenario but if it works it gives you an easier install to control and its very easy to undo if it doesn't work. Certainly worth a try for your 200 sets.

Let me know how it goes. I won't be back near my one 1230 till Friday when I'll give using a fixed file a try.

Stuck in a never ending cycle of file copying.

 

[sizbut]

Continued experimentation says you should be good with the auto-generated files.

I configured a SE Select primary and 500 V2 expansion to support each other for resiliency.

I then browsed to the primary to look at the auto-generated 11xxsettings.txt file it supplied and the S1/S2 settings of the two systems were in the auto-generated file. Vice versa when I looked at the auto-generated file from the 500 V2. So both would have been automatically providing the appropriate addresses to any 1100s/1200s that they were supporting.

And having just looked at the H175 and J129 auto-generated settings files they're done the same there. The only caution I need to raise is that I'm using the latest 10.1 Beta, so I can't tell whether this is true also for 9.1/10.0.

 

[MDoherty66]

Tested this in my lab as well, 10.0.3 Primary & Secondary, and once I had the SIP domain configured, they actually did fail over properly (faster than the H323 phones). I noticed the 11xxsettings.txt file had S1 and S2 configured (as Primary and Secondary) as well, which contradicts the Avaya Documentation that states you need to configure this manually, but WHEN DOES AVAYA DOCUMENTATION EVER LIE... RIGHT ????



Thank you for all of your help! (Where did you get the 10.1 Beta?)

 

[sizbut]

Using 10.1 is the price of being a triallist.

I certainly saw my 1200 go back to the primary the moment that server was reconnected to the network. Whilst that may seem good, it could potentially be a pain (constantly re-registering) in a real failover if the original cause of the problem is some repeating network glitch.


Stuck in a never ending cycle of file copying.

 

[edvy123]

Hi guys,
Any chance of Normal H.323 phones registering to their respective control units in case of Primary server failure??

rgds
edvy

 

[sizbut]

Yes, but that's an IP Office Select feature. Start a new thread if you're having a problem with that.

Stuck in a never ending cycle of file copying.