Well I know we are doing both on one wire and no issues. We do use separate vlans for voice versus data.
QOS is configured also, We run our IP camera system on the same network also, I see constant 45mbit traffic to the server doing the camera recording. We also use Altiris to image up to 25 workstations at the same time and I've yet to have any issues with voice call quality. We have about 175 voip phones so I for one think this recommendation is at least inefficient. Would require double the switch ports and wiring. At the risk of offending, sounds like something isn't configured properly if you need two separate wires, just to support VOIP. I also know of several colleges much larger than us that are doing the exact same thing and having great success. In fact, I just came from a video conference where one of the techs said they had just deployed 500+ voip phones and related pcs and infrastructure and it is working great. From: Philip Brothwell [mailto:[email protected]] Sent: Monday, January 25, 2010 5:28 PM To: NT System Admin Issues Subject: Re: Managed Switches... +1 Whenever possible you should run VoIP on separate wiring. The networking requirements for VoIP are very different than the requirements for most data networks. VoIP cares about jitter and latency, data networks care about speed. The typical VoIP call uses less than 1Kbps of bandwidth but it wants that bandwidth NOW. Yes, you can (and should) use QoS and VLANS to help with VoIP but if your network is heavily utilised you will still have issues. And since the bandwidth requirement for VoIP is low you can in many cases reuse the existing PBX wiring for VoIP. I have actually seen enterprise-level VoIP run over CAT 3 cable. (Something I do not recommend other than as a stop-gap.) On Mon, Jan 25, 2010 at 5:19 PM, Kurt Buff <[email protected]> wrote: You can do this with QoS, and I've seen nothing to indicate that HP is anything less than stellar in this regard. But if memory serves (it's been a few years) switches with QoS cost a bit more. Perhaps that's no longer true. At the very least, it simplifies configuration and troubleshooting. Also, I don't know what the cost of phones would be for this system, but cost of switches is not that much, and cost of cabling is ~&75.00/drop, depending on location. OP didn't specify, but I find the use of phones as two-port switches to which the workstations are appended to be yucky, and fraught with problems - might as well run the cable separately, because QoS doesn't do much for you in those situations. At the very least, he should consider separate VLANs for VoIP vs. everything else, along with QoS. Kurt On Mon, Jan 25, 2010 at 13:27, Brian Desmond <[email protected]> wrote: > Why? You might as well just buy a new PBX or upgrade the existing one and run it on the existing infrastructure if you're going to do that. Doesn't get you any cost savings... > > Thanks, > Brian Desmond > [email protected] > > c - 312.731.3132 > >> -----Original Message----- >> From: Kurt Buff [mailto:[email protected]] >> Sent: Monday, January 25, 2010 3:16 PM >> To: NT System Admin Issues >> Subject: Re: Managed Switches... >> >> +1 on the HP switches. >> >> Further recommendation (which I know won't fly, but I'll make it >> anyway): Pull the cable needed to keep VoIP separate from everything else, >> and get VoIP its own infrastructure. >> >> Kurt >> >> On Mon, Jan 25, 2010 at 11:05, Reimer, Mark <[email protected]> >> wrote: >> > Hi folks, >> > >> > >> > >> > I need some opinions. >> > >> > >> > >> > Up until now (don't laugh), we have been using unmanaged switches, and >> > it's been working. But we hope to implement a VOIP system (probably >> > based on Asterix software), and there are other factors (VLAN's for >> > one) that will require us to install managed switches. >> > >> > >> > >> > I know Cisco is the cream of the crop, and the most expensive. I've >> > heard that HP is quite good as well. >> > >> > >> > >> > So, without starting too many flame wars, can people make a >> > recommendation, (or a "unrecommendation")? >> > >> > >> > >> > This would be for one physical location, looking at 150-200 drops >> > scattered throughout campus (we are an educational institution). We >> > are planning to use the current Ethernet wiring (CAT 5 or better in >> > all places), with the phone and computer using the same physical wire. >> > >> > >> > >> > Thanks in advance. >> > >> > >> > >> > >> > >> > Mark Reimer, A+, MCSA >> > >> > Windows Servers & Networking >> > >> > Prairie Bible Institute >> > >> > Box 4000 >> > >> > Three Hills, AB T0M-2N0 >> > >> > Canada >> > >> > Tel: 403-443-5511, Ext. 3476 >> > >> > Fax: 403-443-5540 >> > >> > Email: [email protected] >> > >> > www.prairie.edu >> > >> > >> > >> > >> > >> > >> > >> > >> >> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ >> <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ >> > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
