Thanks folk - I am more educated already. For you Mitel folks, what sort of VLAN/QoS did you configure on your switches. Looking at my switches, I see there are already a number of VIOP vendors built in for QoS, but not Mitel, so I'd need to add it.
>>> "Stringham, Steven" <[email protected]> 5/2/2011 1:21 PM >>> Tom We have a Mitel 3300mxe phone network with 5340 phones on the desks. We put this in about 4 years ago. I replaced the older switches with 3560 POE switches and have the PCs behind the phones. We are able to put microswitches behind these (so you could have a PC and a printer, etc.). We have had some issues with phones acting up, so that we got bad throughput at the PC. Replacing the phone takes care of that. Spares are important. Getting phones with a completely digital display is wonderfull. I am so glad not to have to print out templates for phones anymore, because it is all on the display. Select your phone carefully. We have 8 sites across our MPLS network. Some smaller sites (across T1s or even DSL VPNs) are being hosted by a 3300mxe on the other side of the wan. Communication is great. Max latency is about 40-50, sometimes as high as 100ms when in high traffic. Voice is still good. One of the capabilities of Mitel is having a phone across the internet (for example - having a phone at home on your main switch). This works very, very well. I absolutely agree - get good POE switches, and put decent UPS units supporting those switches. Also be very careful on your switch/phone selection. Different POE devices support different power draws. There are several standard levels of power draw. Some POE switches will support a maximum power draw. For example, the 5340s take about 6.1 watts. The ports on my 3560 support 15.4 watts. However, my 48 port switches will only support 24 ports at the full 15.4 watts. But, it can take the full 48 ports at 6.1 watts. If I put GigE phones in, they would take the 15.4 watts level - so I could not put a full compliment of phones on my 48 ports switches. Good Luck From: Tom Miller [mailto:[email protected]] Sent: Monday, May 02, 2011 6: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 [email protected] with the body: unsubscribe ntsysadmin For more information about Lewis and Roca LLP, please go to www.lewisandroca.com. Phoenix (602)262-5311 Minden (775)586-9500 Tucson (520)622-2090 Albuquerque (505)764-5400 Las Vegas (702)949-8200 Silicon Valley (650)391-1380 Reno (775)823-2900 This message is intended only for the use of the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender of this E-Mail by return E-Mail or by telephone. In accordance with Internal Revenue Service Circular 230, we advise you that if this email contains any tax advice, such tax advice was not intended or written to be used, and it cannot be used, by any taxpayer for the purpose of avoiding penalties that may be imposed on the taxpayer. ~ 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 [email protected] with the body: unsubscribe ntsysadmin 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 [email protected] with the body: unsubscribe ntsysadmin
