Hi all,
I try to use SER as a load balancer with the dispatcher module. All SIP/RTP request are load balanced and, in a LAN, it's working. With phone with a public address ip, it's work too.
But my problem it's with NATed phones... The ser change the source ip address and so, the nat=yes option in asterisk cannot work!! (I make registration on ser servers)
I wanted to change the "from header field" in the ser and put the IP source, but it seams impossible.
Do you have an idea for my problem?
Thanks a lot,
Thomas Deillon
Hello,
On 12/04/06 12:45, Thomas Deillon wrote:
Hi all,
I try to use SER as a load balancer with the dispatcher module. All SIP/RTP request are load balanced and, in a LAN, it's working. With phone with a public address ip, it's work too.
you cannot use a load balancer in front of natted clients unless you use the path extension (see the path module). There is another issue you have to take care of, the nat pinhole maintenance.
But my problem it's with NATed phones... The ser change the source ip address and so, the nat=yes option in asterisk cannot work!! (I make registration on ser servers)
OpenSER will cheange the source IP because is not working at IP level, but at application level.
I wanted to change the "from header field" in the ser and put the IP source, but it seams impossible.
have a look at uac module, there you can find uac_replace_from()
Cheers, Daniel
Do you have an idea for my problem?
Thanks a lot,
Thomas Deillon
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hi,
I don't know these modules, but here we solve this problem using a unique VIP (Virtual IP) for all openSER cluster nodes.
I'm using Keepalived with LVS, as I said in another thread.
Rgs.
On 12/5/06, Daniel-Constantin Mierla daniel@voice-system.ro wrote:
Hello,
On 12/04/06 12:45, Thomas Deillon wrote:
Hi all,
I try to use SER as a load balancer with the dispatcher module. All SIP/RTP request are load balanced and, in a LAN, it's working. With phone with a public address ip, it's work too.
you cannot use a load balancer in front of natted clients unless you use the path extension (see the path module). There is another issue you have to take care of, the nat pinhole maintenance.
But my problem it's with NATed phones... The ser change the source ip address and so, the nat=yes option in asterisk cannot work!! (I make registration on ser servers)
OpenSER will cheange the source IP because is not working at IP level, but at application level.
I wanted to change the "from header field" in the ser and put the IP source, but it seams impossible.
have a look at uac module, there you can find uac_replace_from()
Cheers, Daniel
Do you have an idea for my problem?
Thanks a lot,
Thomas Deillon
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Marcos Hack wrote:
I don't know these modules, but here we solve this problem using a unique VIP (Virtual IP) for all openSER cluster nodes.
How do you ensure that all messages belonging to one transaction are balanced to the same physical server? Is there now SIP support in LVS?
Andy
Sorry by mistake. I'm using only stateless proxy.
On 12/5/06, Andreas Granig andreas.granig@inode.info wrote:
Marcos Hack wrote:
I don't know these modules, but here we solve this problem using a unique VIP (Virtual IP) for all openSER cluster nodes.
How do you ensure that all messages belonging to one transaction are balanced to the same physical server? Is there now SIP support in LVS?
Andy
-
Andreas Granig -
Daniel-Constantin Mierla -
Marcos Hack -
Thomas Deillon