I haven't been able to get CER to reliably display the switchport description from 3750 switches, do you happen to use CER with that model? Just curious.. I've noticed it does show the descriptions correctly for 4500's, would love to get the 3750 port desc in there too.<br>
<br><div class="gmail_quote">On Thu, Sep 24, 2009 at 2:40 PM, Andrew Dorsett <span dir="ltr"><<a href="mailto:vtadorsett@gmail.com">vtadorsett@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
CER can read in the switchport description and will provide that as a part of the internal emergency alert. If you only have one open front door with a receptionist it might not make sense to divide the ERL's into exact locations. Just pass the building address with the front door to 911 and then send the specific cube location to your internal emergency staff. <div>
<br></div><div>As with everything, it's a trade-off calculation you have to make for each deployment.<br><font color="#888888"><div><br></div><div>Andrew</div></font><div><div></div><div class="h5"><div><br></div><div>
<br><br><div class="gmail_quote">On Thu, Sep 24, 2009 at 2:01 PM, Ed Leatherman <span dir="ltr"><<a href="mailto:ealeatherman@gmail.com" target="_blank">ealeatherman@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">using CER here. Each switchport has its own location, so its not a problem for example to have part of the switch service one floor/area, and the other part service a difference location. It does mean that your network support staff must be aware that if they change where a port is patched to, a change may also need to be made to the CER configuration for that port.<div>
<br></div><div>Would be fantastic if CER were smart enough to read in the switchport description and glean the ERL from that. <br><br><div class="gmail_quote"><div><div></div><div>On Thu, Sep 24, 2009 at 1:53 PM, Lelio Fulgenzi <span dir="ltr"><<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div><div><div><div style="font-family:Verdana;font-size:10pt;color:#000000">Just wondering...for those of you who have enabled E911, either using Cisco ER or 911Enable, can a switch and/or switch-stack have different "locations" associated with it? In our current layer 1 model, we install a switch stack in a particular space which services both horizontal and vertical space. For example, a switch stack in one corner of the building could service half the desks on each of four floors, and a switch stack in another corner of the building could service the other half on each of four floors.<br>
<br>How will that complicate things going forward if we want to do E911?<br><br>---<br><font color="#888888">Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>"Bad grammar makes me [sic]" - Tshirt<br><br></font></div></div><br></div></div>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Ed Leatherman<br><br>
</div>
<br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div></div></div></div>
</blockquote></div><br><br clear="all"><br>-- <br>Ed Leatherman<br><br>