Semi Complex VOIP qestion with other hardware
mechanicalmetal last edited by
I have been running Pfsense flawlessly for about a year now. I am wanderng how I could go about traffic shaping my firewall so I can allow my VOIP to pass. I am a compete noob when it comes to traffic shaping so fulfill what I need to do to accomplish this. I requre little to know speed to run my VOIP. Right now I have my vonage box connected to my main internet connection and then out to my WAN for pfsense. What I would like to do is have my pfsense controlling my VOIP box. How would I go about doing this?
Also I have a cisco IP phone I would like to use, would this be at all possible to use with pfsense?
Thank you so much for your time!
joebobcooter last edited by
Don't know if this helps, but I have an Avaya VPN phone that connects via an internal VPN client on the phone (I think its IPSec) client back to my corporate network. My only intent was to prioritize VOIP traffic from this phone, and have a goal of 0% packet loss on the phone, and packetization delay of 25msecs, and one-way network delay less than 25 msecs and network jitter of 0msecs. I can view these values directly on the phone while on a call.
I simply went through the traffic shaping wizard, selected the IP address of the phone (its internal IP), and entered max and min values for my broadband (used www.speedtest.net). Phone uses G.729, so I conservatively allocated 1500 kbps for up and down. http://en.wikipedia.org/wiki/G.729This is way more than is needed for this encoding, but, again, I wanted to make 100% sure calls were as clean as possible. I selected the defaults for everything, and did not penalize any other traffic.
This provided two queues that I care about; qVOIPup and qVOIPdown. I also went into each of these queues, and selected Early Random Detected, Random Early Detection In and Out, and Explicit Congestion notification. I left all other settings as the wizard had provided. I re-loaded the states on pfsense.
My testing included the following;
1. Initiating a call from Avaya VPN Phone
2. Running multiple speedtest sessions from multiple computers
3. Watched a movie (Full Metal Jacket) ondemand from Netflix
4. Loaded up 3 bittorrent downloads from
I watched the quality stats on the Avaya phone, and all parameters were within acceptable ranges. Also, I could see that the queues were being populated by the VOIP call. (Used Status–>RRD Graph-->Queues).
Platform is a MSI mini-itx (http://www.newegg.com/Product/Product.aspx?Item=N82E16813130109) with 1GB RAM, running from a 8GB USB stick. Running pfsense 1.2.1.
I haven't gotten into fine tuning of the parameters in the queues, as it seems to work. My sense is that there are likely items in the service queue that could be tweaked to provide additional performance benefits, but until I experience problems, I am keeping this as it is.
If I were you, I would try to add the Vonage and Cisco phone inner IPs (the Ip addresses they use on your network), and use the wizard. Then load it up, and see if the traffic is being sent to the queues, and if you experience quality problems on the calls.
xbipin last edited by
if u tick the following
Early Random Detected, Random Early Detection In and Out, and Explicit Congestion notification
then doesnt it mean that it will start bufferring packets and thats not good for voip, it needs to send the packet without dropping or bufferring.
blue.angel last edited by
These specialists require the specific knowledge and skills to design and support complex VoIP solutions in Wide Area Network (WAN) and Local Area Network,
eri-- last edited by
No those algorithms do their jobs when the queue is overloaded and the way ALTQ works it makes it magics only when network is congested.
So make sure you do not overload you VoIP queue.