By more flexible, you mean, you have less control over it? I agree with Ashar, more specific is always better. Use ^ and $ when possible and include the digits you know are not going to change.
On Fri, Jul 2, 2010 at 1:35 AM, Ashar Siddiqui <siddas...@gmail.com> wrote: > There is no drawback in first option but I would like to be as specific > as possible. > > > > The 2nd rule should be like this: > > > > voice translation-rule 1 > rule 1 /^3214\(3...\)$/ /\1/ > > > > This way only calls for your DDI range will be entertained by the gateway > and rest will be rejected. > > At commercial level, you will never find rule like the first one. > > > > Hth > > Ash> > > > > > > *From:* ccie_voice-boun...@onlinestudylist.com [mailto: > ccie_voice-boun...@onlinestudylist.com] *On Behalf Of *Erwan Erwan > *Sent:* 02 July 2010 02:37 > *To:* ccie_voice@onlinestudylist.com > *Subject:* [OSL | CCIE_Voice] Translation pattern H.323 > > > > hi all, > > > > Can we specify the TP like this in exam ? For incoming call to our H.323 > gateway,so we do not need to worry what it send from PSTN, as long as it is > for 3xxx > > > > *voice translation-rule 1** > rule 1 /.*\(3...\)$/ /\1/ * > > > > or have to be specific ,like this : > > > > voice translation-rule 1 > rule 1 /3214\(3...\)$/ /\1/ > > > > As I think 1st one more flexible, but what is the drawback using 1st > option ? > > > > tks > > > > _______________________________________________ > 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
