I have an IP phone registered to each subscriber on the cluster in our test lab. After a maintenance task I have a set of feature tests I do on each phone depending on what I did to the cluster. <br><br>Aside from test calls, I make sure call forward all, conferencing, transfering, MoH, etc are working between subscribers. If I do patches on Unity I test some callhandlers and make sure forwarding around within them is working OK.
<br><br>I also call 911 and make sure the CER server is working properly after any maintenance task that touchs the callmanagers - including having them call me back to make sure the call gets back to the right phone. The folks at the local PSAP are always cooperative to help me test it out.
<br><br><div><span class="gmail_quote">On 8/11/06, <b class="gmail_sendername"><a href="mailto:tomlemay@adelphia.net">tomlemay@adelphia.net</a></b> <<a href="mailto:tomlemay@adelphia.net">tomlemay@adelphia.net</a>> wrote:
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I am interested in hearing about the various test plans that are being used by members of this list for testing new Call Manager OS releases, patches and versions of Call Manager application releases. Outside of making test phone calls (
i.e toll free, long distance, local, leaving voice mail messages and such) what else can one do to test or verify the stability of the new release?<br><br>thanks,<br><br>Tom<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">https://puck.nether.net/mailman/listinfo/cisco-voip
</a><br></blockquote></div><br><br clear="all"><br>-- <br>Ed Leatherman<br>Senior Voice Engineer<br>West Virginia University<br>Telecommunications and Network Operations