OK...that makes sense. Thanks Matt
Mike
On Mon, May 17, 2010 at 5:31 PM, Matthew Hall 1.matt.h...@gmail.com wrote:
Mike, I used to just test at the end, but I found it to be counter
productive if I made several mistakes, I now test as I go, with the
exception of aar, it only takes a few minutes more to test each one as I go,
shutting down a voiceport takes only seconds, as does bringing back up. I
makes me more confident in my foundation I build the dial plan as well.
Test it all at the end was easier when I used to chart out my full dial
plan on notepad (as I did in V2), but now I just build as I go and it's much
harder to test the whole dialplan at the end without a table.
Matt
What is everyones thoughts on testing dialplan ?
If you have multiple paths for calls such backup gateways, or teho with
backups etc, would it make sense to get through dialplan and then just
test
at the end. Or test as you go, both the primary and backup path after
implementing each route pattern ? Testing as you go would involve
shutting
down the voice-port on the gateways after each pattern is implemented and
verifying it works before moving on to the next bullet/task.
Just curious what you all feel is the best approach.
Thx,
Mike
___
For more information regarding industry leading CCIE Lab training, please
visit www.ipexpert.com
___
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
