+100. Cisco shop with 200+ phone, pc connected into every one of the phones. 500+ workstations, student labs, printers, ip cameras, you name it and the phone system has been the most reliable of all the systems we run. Separate voice clan with QOS and call quality is super. Almost all the community colleges in VA have similar setups and they are all doing the same "converged network" and we are one of the smaller composes. Take your vendors advice, especially if they have a few installations that you can verify. Good luck.
From: Mayo, Bill [mailto:bem...@pittcountync.gov] Sent: Monday, May 02, 2011 10:51 AM To: NT System Admin Issues Subject: RE: VOIP design questions Agreed. We have been using Cisco-based VOIP for nearly 10 years. I had some concerns about the bandwidth and putting the phones between the computers and switches in the beginning, but it has really been a non-issue. We do use a different VLAN for the voice traffic and have all POE switches. We use all Cisco gear (phones, switches, call manager), so I can't speak for other vendors, but our stuff has been very solid. Bill Mayo From: Kevin Lundy [mailto:klu...@gmail.com] Sent: Monday, May 02, 2011 10:00 AM To: NT System Admin Issues Subject: Re: VOIP design questions Tom, We do everything the vendor recommends. Have been for about 8 years. One of the benefits of VoIP is the collapsing of your infrastructure. If you keep everything isolated, you still have full double infrastructure. As Jim suggests, certainly segregate via VLAN. We use the port on the back of the phone. Keeping a couple of phones as spare in each physical location is a lot cheaper than doubling your port count. We have over 1200 phones deployed, and in 8 years I think 10 have failed. 10 spares is a lot cheaper than 1200 more network ports and cabling. We are a Cisco shop, so can't speak to the reliability of Mitel. On our new offices, we have saved quite a bit of money by only doing a single cable plant. On Mon, May 2, 2011 at 9:45 AM, Kennedy, Jim <kennedy...@elyriaschools.org<mailto:kennedy...@elyriaschools.org>> wrote: If you have the unused bandwidth then your current network can do it. VIOP data is not as much as you think. I would however segregate with VLAN's and prioritize the voice packets. I am not a big fan of plugging the computers into the phones, I would re-patch if you can budget for that. What about POE for the phones?...if you don't go that route then you have to plug power bricks in for every phone. From: Tom Miller [mailto:tmil...@hnncsb.org<mailto:tmil...@hnncsb.org>] Sent: Monday, May 02, 2011 9:39 AM To: NT System Admin Issues Subject: VOIP design questions Folks, We are planning to retire our current phone system and move to a Mitel VOIP system. Not having implemented VOIP before, I have some questions for those of you that have: - our vendor claims our current data network can easily handle VOIP traffic since it's a small amount of traffic (don't know exact amount yet, still awaiting vendor response). As such, they tell it is possible to use our current network to accommodate voice and data. I'm not sure if I"m comfortable with this. I was thinking of a more segregated approach: different network and voice and data never intersect. - our vendor claims we can use the existing data jack for the phones, and plug the desktop PCs/laptops into the phone as a sort of switch. I'm thinking this would add another level of complexity: phone is broke and by the way you can't get on the network now. - the reason the vendor suggests the above is that the current voice drops (cat5) terminate to phone patch panels (in most cases). Those cables would need to be cut and re-terminated to switches. So I have some concerns about our vendor claims. The dollar figure they propose does not include network changes, new switches, etc. Looking at the cost proposal, I am thinking there are quite a few hardware and man-hours costs missing. What do you folks do for VOIP? Thanks, Tom Confidentiality Notice: This e-mail message, including attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
