• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1826
  • Last Modified:

Softphone Traffic Routing

Hi,

We have been asked to integrate around 25 softphones into our environment. Currently VOIP and Data is split into separate VLANs.

We are going to attach a second USB NIC to the PC's that need softphones. NIC 1 will be on the data VLAN and the USB NIC can be tagged to the VOIP VLAN.  

In testing this works to a degree. The USB NIC gets assigned to the VOIP VLAN and given the correct IP Etc.. I was planning on blocking all traffic apart from VOIP and allow access to the external TFTP server on our firewall on the VOIP VLAN.

When I do this I run into problems. Essentially... I need the USB NIC to only send VOIP traffic to the VOIP VLAN from the softphone, therefore not flooding our VOIP WAN connection with data traffic. NIC 1 should always handle any data traffic out of the data VLAN.

Is this possible to do? it seems that I need to do this at the source? NIC metrics and bindings seem to make no difference...

We are using a mixture of HP ProCurve 2520 POE  and 2910 switches.

Any ideas appreciated... Let me know if you need more info on the setup?

Cheers :)
0
jfreckeltom
Asked:
jfreckeltom
2 Solutions
 
TimotiStCommented:
You could setup your VOIP NIC without a gateway, and add a static route towards the callmanager/sip server/other voice device to your routing table.

But all in all, it seems like a bad idea to me: dual cables to all workstations, prone to errors...

Why not just use the data vlan for voice? Those switches can do QoS based on layer3 DSCP, no real need for a separate vlan for voice. And the router/firewall can decide, based on the destionation address, which WAN to use: data or voice.
A separate voice vlan for hard voip phones is a good thing, but not necessary for you, IMHO.

Tamas
0
 
pwindellCommented:
Running a machine with two nics is a disaster in the making.  The problems you are seeing are just the tip of the iceburg.

If your LAN is not overloaded just run the softphone over the normal Nic on the normal LAN segment.

As long as there are less than 250 or so devices on the segment you'll be ok.  It is all "ones and zeros" and far as the cabling routing and switching are concerned,...the protocol is irrelevant.   QoS, as has been mentioned, is fine but it can also slow the normal LAN Traffic more than you might want.  Try without QoS first,...if the softphones start to "stutter" too much then add QoS.   But never make subnets bigger than /24bit segments,...keep them efficient,...keep them below 250 devices.

Here's a sample list of the multihoming disasters.  Not all these apply to you, but the intention is to reveal that,...as a general rule,...is just plain "bad".

157025 – Default Gateway Configuration for Multihomed Computers
http://support.microsoft.com/default.aspx?scid=kb;en-us;157025&Product=win2000

Default gateways
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/6c7c7ab2-cfdc-4dfe-8560-570d3859f5b1.mspx

Default Gateway Behavior for Windows TCP/IP
http://www.microsoft.com/technet/community/columns/cableguy/cg0903.mspx

159168 – Multiple Default Gateways Can Cause Connectivity Problems
http://support.microsoft.com/kb/159168/EN-US/

272294 – Active Directory Communication Fails on Multihomed Domain
Controllers
http://support.microsoft.com/default.aspx?scid=kb;en-us;272294

191611 – Symptoms of Multihomed Browsers
http://support.microsoft.com/default.aspx?scid=kb;EN-US;191611

Microsoft Windows XP – Multihoming Considerations
http://www.microsoft.com/resources/documentation/windows/xp/all/reskit/en-us/prcc_tcp_qpzj.asp?
0
 
jfreckeltomAuthor Commented:
Thanks for the comments. As you both suggested I decided to leave the dual NIC idea and run the softphones over the Data VLAN. No problems yet :)
0

Featured Post

Reclaim your office - Try the MB 660 headset now!

High level of background noise often makes it difficult for employees to concentrate fully on their jobs – or to communicate clearly on calls. The MB 660 headset helps you create a disruption free workspace.  

Tackle projects and never again get stuck behind a technical roadblock.
Join Now