[cisco-voip] jabber application/directory dial rules post-CUCMv8.6

[Ryan Ratliff]

Keep in mind that the purpose of ADRs are to act as the middle-layer between your enterprise dial plan and some external directory where the number formats may not always line up.  This can be everything from local contacts on your PC to Gmail contacts on your smartphone.   The ADR is like a translation that happens before any digit analysis and only for certain endpoints.   The goal of the ADR is to get that digit string into a format just as if the user had dialed it manually from an internal phone.  Once you get the number sent from the mobile device into a reliable format then the rest of the 100 different ways you can manipulate digits can be used.  

-Ryan

On Mar 5, 2012, at 3:34 PM, Lelio Fulgenzi wrote:

I guess in general, I have a difficult time understanding why these rules should be applied globally without the opportunity to apply them based on a group definition, such as profile. This could be based on anything from client interaction to corporate policy, etc. 

For some reason, you might have programmed a certain group of users to use a specific set of gateway resources that require different digit manipulation. Or you might actually want to test a a different way of doing things without having to do this on a separate cluster. Pretty much everything on CallManager is done this way, with the ability to override things on the phone level. The fact that we're now having this ability removed seems a bit backwards.

Again, I'm new at this, so I could be totally wrong, but the ability to configure things in a hierarchical structure, i.e. enterprise parameter, device pool, phone, is one of the strengths of CallManager. I would hope things would continue in that way.

Lelio

---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it. 
                              - LFJ (with apologies to Mr. Popeil)


From: "Ryan Ratliff" <rratliff at cisco.com>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca>
Cc: cisco-voip at puck.nether.net
Sent: Monday, March 5, 2012 1:52:59 PM
Subject: Re: [cisco-voip] jabber application/directory dial rules post-CUCMv8.6

It's just a matter of the number matching a dial rule, then it's applied.  Is there a particular use case you had in mind for using different rules with one app vs the other?

-Ryan

On Mar 5, 2012, at 10:37 AM, Lelio Fulgenzi wrote:

When looking through the jabber application admin guides, it talks about the directory lookup and application dial rule URLs in which you can load custom rules. It also says that with v8.6 the rules are applied by CUCM and not the client.

My goal was to create separate dial rules for the jabber clients to avoid messing with the default application dial rules in the event we wanted to make something different for those apps that use them, i.e. Communicator(?).

I want to make sure I'm not going down a path I can't maintain in the future.

For those of you with v8.6, can you comment on how the dial rules are created? Can you create different groups of dial rules for different targets? If so, how are those targets defined?

Thanks, Lelio


---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it. 
                              - LFJ (with apologies to Mr. Popeil)


_______________________________________________
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/20120305/2196f9e5/attachment.html>