2 May
2007
2 May
'07
2:33 a.m.
Hi Alex!
Without having done this: You can configure the SIP proxies as load
balancers too which distribute the load over all the proxy/registrars
(including itself).
Another solution requires a new feature, which should be easily
implemented: Openser already stores the socket on which the request was
received. Then, during lookup, this socket will be forced with an
implicit force_send_socket().
If either
- the forced send socket is accessIble via a pseudo variable
- during lookup() the socket info is exported as AVP
the request can be forwarded to the proxy which has the NAT binding.
regards
klaus
Alex Hermann wrote:
Hello list members,
I'd like to use multiple proxies/registrars in a SRV managed
failover/load-balancing situation. For NAT purposes I could use a couple of
dedicated load-balancers with path support to store the NAT enabled route in
the location table. The registrars have a shared location table on a database
server. This situation works, but....
Is there a possibility to skip the load-balancers?
I want the proxy/registrar to store the NAT-route somehow in the location
table, so that when the contact needs to be contacted, the proxy can
determine if it can send the request itself, or it needs to forward it via
one of the other proxies (the one with which the contact has the NAT
relation).
I hope you understand the topology, otherwise I might need to create some
ascii-art.