<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
100MB should be fine. The only high b/w demands are media features
provides by the IPVMS service including: Music on Hold, Annunciator,
Media Termination Point, Conference bridge.<br>
<br>
Most important is avoiding speed/duplex mismatch and improper cable
runs. You want clean stats as much as possible.<br>
<br>
Regards,<br>
Wes<br>
<br>
On 6/13/2011 1:11 PM, David Zhars wrote:
<blockquote
cite="mid:BANLkTi=DrEzbf2NAJ-6nq1aJgc+-Q8EJqg@mail.gmail.com"
type="cite">Doing a setup for a smaller company, about 180
phones. Generally I would see CM plugged into a gig port on a
switch but they don't have a gig port. <br>
Do you think I'll run into any trouble with using a 100M port,
maybe dual speed, so I will get close to 200M? <br>
My understanding has always been that there is not a lot of work
between the phones and CM once the system is up, some initial
signalling at the start and end of each call, then it is all
handed off to the switches.<br>
<br>
Appreciate any thoughts!<br>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
</body>
</html>