I have a question on doing load balancing for registering endpoints. Consider a configuration where we want all the endpoints to be configured with a single well-known address (as the default outbound proxy). At registration time, I would like to redistribute the requests among a farm of registrars based on the current loading. The important detail is that all future requests from the UA should go directly to its owning registrar.
At a high level, it seems that this could be achieved by just 3xx the original register to get the UA to resend the register to the selected registrar. However, the 3xx responses are specific to a RURI and so while they might cover registration refreshes, they would not seem to cover, for example, an INVITE from that UA. A closer fit would seem to be the Service-Route header. However, while this seems to allow one to include the eventual registrar in the route list for future requests, it does not appear to allow bypassing the initial outbound proxy... dependent. For example, some devices will use locally-configured explicit loose routing to reach a next-hop proxy, and others will use a default outbound-proxy routing rule. However, for the result to function, the combination MUST provide valid routing in the local environment. In general, the service route set is appended to any locally configured route needed to egress the access proxy chain. Is my interpretation of the 3xx and the Service-Route semantics accurate? If so, can anyone suggest how one might achieve this load balancing? Thanks in advance for the information. Cheers, Shaun Shaun Bharrat Nothing witty to say ;-( _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
