[cisco-voip] Application Dial Rule with variable length

[Anthony Holloway]

Evgeny already answered, but I'd like to respond nevertheless.

In your screenshot, it shows that you are looking for globalized patterns
(begins with + in your case) and are then changing them to localized
patterns (begins with 9, 91, and 9011 in your case).

If you consider the design approach of "globalize on ingress and localize
on egress" then you should trying to catch non-normalized global format
numbers from endpoints/client/3rd parties and normalizing them to a global
format in CUCM prior to making a routing decision.  Then, all of your
routing decisions are based on globalized numbers.  Followed of course by
picking the correct route out of the system (say the PSTN), and then
localizing the number for that particular connection (say they needed 00
for international calls).

Back you your case, I cannot say for certain that you are routing based on
global patterns, but considering you are turning typical global patterns
(begins with + in your case) into typical local patterns (begins with 9011
for example, is local to North America), tells me that you might have had
to work around not having globalized route patterns to support Jabber users
clicking on global formatted numbers.  Hence my comment about you doing it
backwards: localizing on ingress.

Anyway, I put the smiley face in there because it really doesn't matter.
It's not the the dial plan police are going to lock you up or anything.
You may however find your name on https://dialplansofshame.com/ though. ;)


On Wed, Apr 3, 2019 at 10:51 PM Lelio Fulgenzi <lelio at uoguelph.ca> wrote:

>
> Ok. Now I’m intrigued.
>
> My goal was to allow people to click on someone’s telephone number that is
> written with only country codes and have Jabber append the appropriate
> access code and international access.
>
> All this without having to worry about their actual long distance access.
> If they don’t have the access, the call doesn’t go through.
>
> I always thought that was what ADRs were for.
>
> Was there another way to accomplish this?
>
> Are we talking adding route patterns with the ‘+’ in it?
>
>
>
> *-sent from mobile device-*
>
>
> *Lelio Fulgenzi, B.A.* | Senior Analyst
>
> Computing and Communications Services | University of Guelph
>
> Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON |
> N1G 2W1
>
> 519-824-4120 Ext. 56354 <519-824-4120;56354> | lelio at uoguelph.ca
>
>
>
> www.uoguelph.ca/ccs | @UofGCCS on Instagram, Twitter and Facebook
>
>
>
> [image: University of Guelph Cornerstone with Improve Life tagline]
>
> On Apr 3, 2019, at 10:59 PM, Anthony Holloway <
> avholloway+cisco-voip at gmail.com> wrote:
>
> Huh, I have never noticed this before. I just checked a few different
> environments I have access to, and none of them address international
> patterns.  Good catch though.  It seems like you already know it, and Lelio
> confirmed the solution.  Though, I'd argue that Lelio's configuration is
> backwards; you should be globalizing the number, not localizing it, but
> that's none of my business. ;)
>
> Could you just avoid using these rules all together and implement your
> dialing habit support in the CUCM dial plan?  E.g., xlates and xforms?
>
> On Wed, Apr 3, 2019 at 7:51 AM Reto Gassmann <voip at mrga.ch> wrote:
>
>> Hallo group
>>
>> I have to configure Application Dial Rules on a CUCM 10.5 to prefix
>> numbers for Click to call (eg Firefox, Chrome,...) with Jabber 12.5.
>> Our national numbers are all 10 digits long. So one ADR is enough.
>> But how about international numbers. They all differ in lenght.
>> It is true to build a ADR for every length? So that would result in many
>> rules from 9 to 20 or more Number of Digits.
>>
>> Any other ideas, how I could handle the Click 2 Call issue on jabber?
>> Regard Reto
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20190404/1811ba9f/attachment.html>