SMGR Dial Patterns - approach to changing multiple entries in 1 day

[learningSkype]

morning all. I have to change a few Dial Patterns in SMGR today. while reviewing I realized that the best approach is to duplicate my Dial Pattern, give it a different pattern label and then change the original dial pattern label so that I can now make the new Dial Pattern the effective pattern.

thinking something along the lines of this:

current dial pattern is 91
duplicate this dial pattern and label new dial pattern 91234
change old dial pattern from 91 to 91567
change new dial pattern from 91234 to just 91
task is complete, move on to other dial pattern changes

does that make sense? anyone done this before and has a better approach?

 

[ZeroZeroOne]

If I follow, you are working through these steps. I'm assuming you're changing the Routing Policy to use a different SBC or something:

Original Dial Pattern:   91 ---> Routing Policy "To Old Server"
New Dial Pattern:     91234 ---> Routing Policy "To Old Server"
Edit Original to be:  91567 ---> Routing Policy "To New Server"
Edit New to be:          91 ---> Routing Policy "To New Server"

You're left with two Dial Patterns:

New:                  91567 ---> Routing Policy "To New Server"
Edited Old:              91 ---> Routing Policy "To New Server"

Why not just add the "91567" and edit the "91"?

Perhaps I'm missing something?

 

[learningSkype]

no, maybe I didn't explain it clearly enough:

current dial pattern label is 91 and it's used for calls that start with a 91.
duplicate dial pattern 91 and label the new dial pattern as 91234.

I now have 2 identical dial patterns, 91 and 91234, both patterns use same Routing Policy to Old...

simple so far.

Now:
change old dial pattern label from 91 to 91567 so that 91 is now available/freed as a pattern that can be re-assigned.
change new dial pattern 91234 to use Routing Policy to New Server and re-label this dial pattern as the new 91.

I now have old dial pattern 91567 (which is the original 91) and an updated 91 dial pattern pointing to new Routing Policy. 91234 no longer exists.

task is complete, move on to other dial pattern changes

 

[ZeroZeroOne]

Huh. Well, if that works then OK.

Guess I would just duplicate 91 to 91567, then edit 91 to use the new Routing Policy. To me it seems to save a step since you end up with the same result.

 

[learningSkype]

yeah that's another approach. the reason I want to duplicate and keep a Dial Pattern of 91567 is that I want something to revert to if there's a failure or next day something doesn't work.

but I think this is good. thanks for the feedback/input.

 

[kyle555]

You can't have 2 of the same dial patterns. You'll match on 1 and 1 only and do what the routing policy says.

You'll take the most exact. So, if you have something that matches 91567 and the routing policy is to 1 entity and that's down, SM isn't going to try dial pattern 91.

It will try another sip entity in the same routing policy with a higher number "rank"

Conceptualizing CM/ARS/Route pattern to SM/dial pattern/routing policy takes some time to get your head around

 

[learningSkype]

what if I duplicate 91 and make the new Dial Pattern 919999999999? in theory, someone would have to dial all 9's to match this Dial Pattern and that would never happen.

I think 919999999999 would be a better option and then I would have:
the new 91 Dial Pattern w/a new Routing Policy
as well as 919999999999 (the old 91).

 

[kyle555]

you could just add sip domain "nowhere.com" and change the dial pattern to match only that domain.

no dicking around with numbers then

 

[learningSkype]

ok, you're saying take the copy or duplicate Dial Pattern and create a new SIP domain called "nowhere" so that it never gets used by ASM. correct?

 

[kyle555]

yup