Pre-dot madness

[sterdnotshaken]

Howdy,

I was wondering if any of you have a good explination for the issue I am having... This is the senerio:

9.[2-9]xxxxxx route pattern is striping the predot and pointing to a site specific route list...

The route list has 3 route groups referenced... 1 of the 3 route groups requires the 9 while the other 2 do not...

Logic would suggest that I leave the predot at the route pattern level and simpily do a prefix digit of 9 in the one route group within the route list that requires a 9... but this doesnt seem to be working... ...

If I configure it this way and then do a DNA, it show's the predot working (stripping) @ the route pattern level and then within the route list section, it shows the different route group call treatments and the 9 is back!... so if I prefix the 9 in the one route group within the route list that needs it, it ends up having 2 9's in the called # shown by DNA.

Any idea's?

[Joseph Martini · Accepted solution]

The digit manipulation will occur at the lowest level so in this order from top down (less to more specific) route pattern, route group/list, device (gateway port).  If you have a manipulation on the route group/list then the route pattern will be ignored.  You'll want to skip the step on the route pattern and just set your prefix or discard on the route groups or route list.

[sterdnotshaken]

Hey joemar2,

I was afraid that would be the answer... ahh well, it is good to know! I really appreciate you taking time to answer this question for me!

Thanks!