[quagga-users 12925] Re: voip application with bounty

Ralph Mondegar ralph at ipsecure.com.br
Thu Jul 5 19:55:49 BST 2012

Hello there,

   You can't exactly do what you want to but there are some workarrounds
that should work for you. The easiest way to do so is to route the traffic
for your sip carrier thru the first link and everything else (data in
general) using the second link. To achieve that, do the following:

- Set up a linux box (you could do that in other OS but lets assume you are
looking for an open source solution);
- Create a static route to the sip carrier IP(s) pointing to the router
used in the first link;
- Set the default gateway using the second link's router;
- Create a NAT to the sip carrier IP(s) using the IP of the first link;
- Create a MASQUERADE NAT for everything else.

   If you have another services hosted using the first link IP, you will
have to use mangle, specific PREROUTING NATs and its recommended to use QoS
to ensure VoIP's bandwidth, i'm just assuming that is not the case.

Hope it helps,

   Ralph Mondegar

On Thu, Jul 5, 2012 at 3:15 PM, copycall <dave at copycall.com> wrote:

> hello,
> i operate a voicemail service bureau and i am looking for some router
> help, hence the bounty.
> i have jitter and latency under heavy loads with my current business cable
> isp connection, it's 15 down and 2 up.
> but, this connection provides the ip address for my sip carrier to direct
> traffic to.
> i have added a consumer cable isp connection that is 30 down and 5 up, but
> it is only dhcp.
> i would like to aggregate these connections to solve the problem.
> i have looked at click, xorp, pfsense, proprietary boxes and now quagga.
> i'd be interested if anyone has any ideas about solving the problem.
> you can contact me offlist at: dave at copycall.com
> thank you,
> dave
> _______________________________________________
> Quagga-users mailing list
> Quagga-users at lists.quagga.net
> http://lists.quagga.net/mailman/listinfo/quagga-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quagga.net/pipermail/quagga-users/attachments/20120705/f3b5caff/attachment.html>

More information about the Quagga-users mailing list