Avaya Session Manager Call Load Balancing:

[hardybacon]

I see the Failover Groups, but I don't see any load balancing on System Manger for the Session Manger Servers. I seem to remember it was possible using local Host Name Resolution but I can't seem to get that to function. Perhaps I stood too close to 4:20 guy this morning. If anyone can help point me in the right direction, I would appreciate it.

 

[kyle555]

Yeah, so failover groups will ( i think) retain call state across a pair of SMs. So, if you have data center East and West and all calls come in your East SBC to your East SM to your East CM and your East SM dies, the West SM will know about all those calls currently up, so when 100 people on a conference bridge on the SIP trunks are up for another hour and the session refresh messages come from CM or the SBC, the West SM will know about them and pass them where they need to go.

In LHNR, you've got weight and priority. So, with hosts A,B,C,D and A&B have Priority 100 and weight 50/50 and C&D have priority 200 and weight 50/50, SM would distribute half to A&B until they can't take anymore before trying C&D at a 50/50 split as well.

 

[hardybacon]

Thank you. When I tried to remove and re-add those entries, I get the warning below. I guess someone did something. At least, I know what the general problem is.

Warning: the following 2 FQDN and Transport entries have no matching Routing Entity Link(s). If SIP entities, they require an Entity Link for call completion

 

[kyle555]

Right, so for the following example to work:

FQDN=potato, IP = 1.2.3.4, port=5060, transport=tcp, priority=100, weight=50
FQDN=potato, IP = 1.2.3.5, port=5060, transport=tcp, priority=100, weight=50

You'd need a SIP entity with fqdn potato, and a tcp link on 5060 to it from some SM, and a routing policy that selects that sip entity as destination for something - like when people dial 1-800-GOT-FRIES or something.