[ previous ] [ next ] [ threads ]
 From:  "Michael Graves" <mgraves at mstvp dot com>
 To:  "m0n0wall at lists dot m0n0 dot ch" <m0n0wall at lists dot m0n0 dot ch>, "Chuck Mariotti" <cmariotti at xunity dot com>
 Subject:  RE: [m0n0wall] VOIP setup
 Date:  Thu, 17 Aug 2006 09:55:45 -0500
Sure. Although it helps to know what protocols you run through m0n0. My
Asterisk server places outgoing calls via IAX2 and accepts incomming
calls via both IAX2 and SIP.

You absolutely have to start with a real world measurment of your
connect speeds up and down. Your traffic shapping must not saturate
either of those or the benefit will be lost.

The use the Magic Shaper Wizard on the Traffic Shaping tool. This will
setup basic rules, pipes and queues. You should have two pipes;
Total_upload & Total_download.

Here's where I change the setup a little. I add a third pipe called
Dedicated_IAX_upload. I split my upload data rate between Total_upload
and Dedicated_IAX_upload. In my case on Covad ADSL with a measured
650kbps upload I set my total upload speed for only 600kbps. I then
assign 384kbps to pipe 2 (Total_upload) and 256kbps to pipe 3

In essence, I full time assign about 40% of my outbound bandwidth to
the voip stuff.

Then in the rules section of traffic shaper I add two rules for my
Asterisk traffic. All UDP traffic from the servers IP to the wan is
driected to pipe3. All UDP traffic from the wan to the server is
assigned to Queue 8 which is High_priority_download.

Of course you need firewall NAT and port forwarding settings in place
as well. The traffic shaping isn't port specific in my arrangement.

I've had my Asterisk & m0n0 system in use for about 2 years. You need
to understand that traffic shaping won't cure bandwidth issues, but it
will make some situation more acceptable. I found that adding G.729
codecs to my server was also very helpfull in reducing the demand for

Also, I don't use any p2p stuff beyond Skype...which I'd rather not use
but many of my overseas coworkers are addicted.

Michael Graves

On Thu, 17 Aug 2006 01:19:18 -0400, Chuck Mariotti wrote:

>Interesting... Can anyone tell me then how to prioritize packets from my
>Asterisk box with dedicate static public IP address NATed to private
>behind Monowall, to be the most important traffic and give it priority
>(so FTP, Http, etc... doesn't crap out my VoIP)?
>What's shape rules or other tricks are they using?
>Below sounds interesting. Anything from public/private IP address is the
>priority above everything else, no matter the ports... How do you do
>this exactly?
>-----Original Message-----
>From: Lee B. [mailto:leeb00 at gmail dot com] 
>Sent: Thursday, August 17, 2006 12:57 AM
>To: m0n0wall at lists dot m0n0 dot ch
>Subject: Re: [m0n0wall] VOIP setup
>On 8/16/2006 8:52 PM, JP Vossen wrote:
>> On 8/16/06, Walter PC <walterpc at mchsi dot com> asked some stuff about 
>> VoIP, and Don Munyak wrote:
>>> IMHO...VOIP sucks, atleast with Vonage on a Comcast broadband 
>>> connection. Then again maybe it was all the kids in my neighborhood. 
>>> I could never get a good connection. Too many symptons to list. I 
>>> tried different cable modems, firewall appliances and even tweaked 
>>> the settings from the Vonage account manager. Then again maybe it's 
>>> just me. So I dropped them . No regrets :)
>> For whatever it's worth, my Vonage over Comcast in SE PA has worked 
>> fine, except when I was running P2P crap.  When I had the Vonage 
>> adapter
>> *outside* the M0n0wall, it was fine, since it could do its own traffic
>> shaping.  However, that was unacceptable because every time they 
>> update the box they nuke the config, which then deletes my incoming 
>> rules and cuts off my network so I can't get in from the outside.  Not
>I've had great results with M0n0wall and Vonage. In fact that's the
>reason I moved from IPCop to M0n0wall in the first place, as IPCop's
>QOS/traffic shaping didn't work very well. I don't prioritize ports in
>m0n0, but instead use a fixed lease on the Vonage device and prioritize
>the IP address. Very clean.
>First I ran the traffic shaping wizard, then added a VOIP entry for
>upload and one for download, below all the small packet stuff.
>As for devices, after my Linksys Vonage adapter/router died after less
>than a year I got one of the new D-Link Vonage adapters. The Linksys
>worked fine behind the M0n0wall, and I had nothing but the phones and
>M0n0wall plugged into it. The advantage of the new D-Link adapters is
>they are only $49 and they don't have routers, etc built in. Its just a
>VOIP adapter, nothing else. Perfect for putting behind a M0n0wall. They
>seem higher quality than the other D-Link networking junk I've seen. 
>Made in Taiwan rather than China could be why, not sure.
>My experience using the Vonage routers' QOS is that it didn't work very
>well. M0n0wall does this pretty well in my experience. Your VOIP calls
>sound better! Its critical to get your pipe speeds set right however
>(not too high).
>To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
>For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
>To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
>For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch

Michael Graves                           mgraves at pixelpower dot com
Sr. Product Specialist                          www.pixelpower.com
Pixel Power Inc.                                 mgraves at mstvp dot com

fwd 54245