[cisco-voip] SRST Test Plan

[Lelio Fulgenzi]

oh, i could see the networking team taking away my enable access password very quickly after that happened. 

by the way, i put the ACLs on the local equipment rather than the remote equipment, so worse comes to worse, i just plug in a console cable and fix things. 

not like i haven't had to do that before. "debug IPX all" anyone? 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
"Bad grammar makes me [sic]" - Tshirt 


----- Original Message ----- 
From: "Jeff Garvas" <jeff at cia.net> 
To: "Lelio Fulgenzi" <lelio at uoguelph.ca> 
Cc: "svr file" <svr.file at gmail.com>, cisco-voip at puck.nether.net 
Sent: Friday, October 2, 2009 8:08:26 PM GMT -05:00 US/Canada Eastern 
Subject: Re: [cisco-voip] SRST Test Plan 


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. 

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 ;) 



On Fri, Oct 2, 2009 at 9:34 AM, Lelio Fulgenzi < lelio at uoguelph.ca > wrote: 




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. 


    • 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. 
    • See how long it takes for the router PSTN ports to register to the router. 
    • See how long it takes for the phone(s) to register to the router. 
    • 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. 
    • See that your COR lists allow and deny the appropriate off-net call patterns. 
    • See that you can make inbound calls to the appropriate PLAR or DID, whatever you are using. 
    • See that your CUE module registers to the router and continues to operate (if you have one installed). 
    • See that your CDRs are being cut or transferred correctly to your RADIUS server (if you have chosen to do so). 

I think that's about it, but I'm sure others will contribute. 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
"Bad grammar makes me [sic]" - Tshirt 





----- Original Message ----- 
From: "svr file" < svr.file at gmail.com > 
To: cisco-voip at puck.nether.net 
Sent: Thursday, October 1, 2009 10:57:48 PM GMT -05:00 US/Canada Eastern 
Subject: [cisco-voip] SRST Test Plan 

Hi All, 

I'm trying to put together a SRST test plan, does anyone already have one that they may want to share? 

Thanks. 

_______________________________________________ cisco-voip mailing list cisco-voip at puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip 
_______________________________________________ 
cisco-voip mailing list 
cisco-voip at puck.nether.net 
https://puck.nether.net/mailman/listinfo/cisco-voip 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20091002/a93c989e/attachment.html>