| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index |
| Rob, you should describe in more detail your load balancer/firewall. If it is possible, you should use your firewall to NAT the approriate ports for the "PUBLIC" ip address sipxbridge is asserting. (5060, 30000-31000 UDP). You should also allow those ports outbound. If your ITSP allows it, you should send signalling "out" port 5080, and they should send signalling back on 5060. What links you use probably wouldn't matter if your firewall can handle the public IP address PAT/NAT and this way your 3 uplinks wouldn't matter. If my assumptions are correct (they may not be, but do correct me if I am wrong), then your configuration questions/issues center around your firewall/load balancer. >>> Rob Hicks Thanks for your response. My experience with sipx is that it binds only to one ip address, eth0 for some reason. The sipx box would run a firewall, iptables configured to only let through the sip traffic. There are two reasons why this seems desirable: 1) we can dedicate a specific high quality internet connection to the sip trunk (back 2 back user agent, right?) and 2) we're using load-balanced, bonded Ethernet connections (3 of them) through our main firewall, which means that the ip address may and does change based upon load and changing ip addresses tend to cause problems at the ITSP or sipx. Would you recommend other ways of doing this? Rob On Thu, Jul 2, 2009 at 3:59 PM, Tony Graziano <tgraziano@xxxxxxxxxxxxxxxxxx> wrote: Assuming a private and public address? o, it will not work. Two nic's is not supported yet and there is no way to bind specific services to a specific interface. Sipx binds to all. |