Avaya SBC HA failover once primary SM down for Remote worker

[Avaya newbie]

Hi all,

I got a question about the solution as below,

Normally remote worker registration to SM-A is working fine, but once SM-A down, the remote worker registration message keeps sending to SM-A when tracing SBC, although got the SM-B as the second priority setting in the SBC routing profile (SM-A is first priority in the same profile) in SBC. it`s possible to send it to SM-B once A is down? and how to achieve. Thank everyone.

 

[kyle555]

Use 2 IPs on the outside for B1 and 2 inside for A1 with flows to sm1 and 2

You want Avaya phones simultaneously registered to both and when SM1 times out, the phone will failover to SM2 to which it is already registered.

 

[Avaya newbie]

i tried to set up 2 pairs of connections.
sample. 1.2.3.4:5071 NAT to B1, 1.2.3.4:5072 NAT to B2.
and 46xxsettings.txt
SET SIP_CONTROLLER_LIST "1.2.3.4:5071;transport=TLS,1.2.3.4:5072;transport=TLS"

but doesn`t see the workplace registered to second SM.

 

[kyle555]

Yeah, but what does PPM say? Phone's going to follow that.

Do you have PPM mapping to accommodate?

 

[Avaya newbie]

compare with both SBC and SM sent out PPM: getHomeCapabilitiesResponse, the primary SM has both SM 1 & SM2 inside PPM, but the PPM sent out via SBC only has SM 1. I already set up 2 x PPM mapping and reverse proxy with the corresponding interface in SBC.

 

[kyle555]

And there's your problem.

I've always done it with SM1 at data center 1, SM2 and data center 2, so each SBC has PPM mapping profiles for SM1 in PPM translates to PubIPDC1, SM2 to PubIPDC2

The best I could imagine is that your SM listen port on SM1 is 5061 and SM2 is 5071 and try having the PPM mapping profiles that way.

The problem you'll run into is with PPM which has to be on the SM's IP address and on port 443. I've tried to get 2 SMs on a single IP. Never successfully.

In the reverse proxies, you can specify a "listen domain". So, if that reverse proxy was on sm1-sm100.yourlab.com, then only https requests to that FQDN would trigger that proxy. I do that with breeze, AADS, Presence, etc and get them all to work on port 443 on a single IP.

The problem with that approach is it breaks as soon as you have any reverse proxy on that port without a listen domain - it overrules all the ones that do have listen domains.

So, if you could get the phones to request

https://sm1-sm100.yourlab.com/ppm

and

https://sm2-sm100.yourlab.com/ppm,

then I think you could use listen domains on 443 for PPM to have the SBC route it to the right SM.

Maybe if you tried FQDN/IP maps in the settings files it'd work. You'd probably need to not use PPM mapping because you're using FQDNs and probably disable ENABLE_PPM_SOURCED_SIPPROXYSRVR to ignore the PPM values of the SM IPs to get it to work.

I've just always found that the phones - possibly just the 9600s - tend to be stupid and demand PPM from an IP address and not an FQDN.

Though, I haven't been too bothered to make a config like yours work, that's what I'd try if a spare IP is such a hassle.

I'd just get another IP