<br>Another option I like is to add static /32 routes for the call manager subscribers that the phones wish to talk to and point them to null0. This is "cleaner" to me beacuse you don't have to apply an ACL to any of your interfaces, you just route the CMs to make them non-existent, and I find it easier to add/remove a static route. Especially if you have multiple egress paths. Sometimes the ACL approach, if you make a typo, could lock you out of the equipment.<br>
<br>Just be mindful of any redistribute-static commands or you could take a lot of production phones out of service. That is only funny the first time you do it ;)<br><br><br><div class="gmail_quote">On Fri, Oct 2, 2009 at 9:34 AM, Lelio Fulgenzi <span dir="ltr"><<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div style="font-family: Verdana; font-size: 10pt; color: rgb(0, 0, 0);">Not sure if this will cover everything, but here are some of the things I did in the past. And this didn't involve visiting the remote site, which was pretty cool too.<br>
<ul><li>Create an ACL that blocks the remote router and a local phone(s) from from reaching the CallManager servers. This will allow you to simulate a network down. You should still have remote access (telnet,ssh) to the router to view the logs.<br>
</li><li>See how long it takes for the router PSTN ports to register to the router.</li><li>See how long it takes for the phone(s) to register to the router.</li><li>See that your dial-plan continues to work and that you can make the appropriate off-net and on-net calls. This is of course one sentence to describe what will be the bulk of your work.</li>
<li>See that your COR lists allow and deny the appropriate off-net call patterns.</li><li>See that you can make inbound calls to the appropriate PLAR or DID, whatever you are using.</li><li>See that your CUE module registers to the router and continues to operate (if you have one installed).</li>
<li>See that your CDRs are being cut or transferred correctly to your RADIUS server (if you have chosen to do so).</li></ul>I think that's about it, but I'm sure others will contribute.<br><br>---<br>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<div>
<div></div><div class="h5"><br><br><br>----- Original Message -----<br>From: "svr file" <<a href="mailto:svr.file@gmail.com" target="_blank">svr.file@gmail.com</a>><br>To: <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
Sent: Thursday, October 1, 2009 10:57:48 PM GMT -05:00 US/Canada Eastern<br>Subject: [cisco-voip] SRST Test Plan<br><br>Hi All,<br><br>I'm trying to put together a SRST test plan, does anyone already have one that they may want to share?<br>
<br>Thanks.<br>
<br></div></div>_______________________________________________
cisco-voip mailing list
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</div></div><br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">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>