6 Sep
2007
6 Sep
'07
10:06 a.m.
Hi Andreas,
thank you very much for you answer! I thought the same way, but not sure
if it is the best way how to do it :-)
So, you mean, I have to detect NAT for all messages/replays going
throught LB, insert some proprietary headers (P-NAT:
received=1.2.3.4:5060) and fix contact header and force/unforce rtpproxy
on proxy servers? It is a lot of processing :-)
Isn't be better to mangle conatct and manage rtpproxy directly from LB?
I really don't have any experiences in loadbalancing, so I will be happy
to gather up all possible informations and experiences from the others.
Tanks!
kokoska.rokoska
Andreas Granig napsal(a):
Hi,
You can detect NAT at the LB and set a proprietary header, like "P-Nat:
1", which can be processed at the proxy.
Cheers,
Andreas
kokoska rokoska wrote:
Hi all,
I'm currently succesfully running OpenSER, but user population grow up
and I'm affraid I need laod balancing :-)
The projected scenario is:
USERS <-> (NAT) <-> LB <-> P1 <-> GWs
<-> P2
<-> R1
<-> R2
Where LB is Load Balancer (OpenSER with Dispatcher & Path module), and
P1-P2 is proxies (OpenSER) and R1-R2 registrars (OpenSER)
And the problem I need to solve is NAT handling.
I can correctly process registrations with help of Path module on LB and
enabling of using it on R1,R2.
But, what should I do with calls? My idea is to process NAT handling on
P1-P2, but I don't know how. Both proxies are unable (I mean) detect
correct user IP address.
Could you tell me, please, what to do? Do NAT handling on LB? It is
unnecessary added load to LB...
Thanx in advance!
kokoska.rokoska