[cisco-voip] variable-length translation pattern

[Bill Talley]

I would think it will always match 1! because of the urgent priority setting.   Keep in mind the example you gave from the SRND list three different translation patterns.  The two you have are the same as far as the first two digits, no?

Sent from an Apple iOS device with very tiny touchscreen input keys.  Please excude my typtos.

> On Dec 9, 2014, at 5:59 AM, daniele visaggio <visaggio.daniele at gmail.com> wrote:
> 
> Hi all,
> 
> I have two translation pattern within the same partition (cucm 9.x).
> 
> They are:
> 
> 1XXX
> 1!
> 
> When an incoming call from external sip gateway comes in with called number (say) 1234, the matched translation is 1!.
> 
> At first, I thought that 1!, being less specific than 1XXX, should not being matched.
> 
> Reading through Cisco Collaboration System 9.x Solution Reference Network Designs (SRND), I saw this:
> 
>> When determining the number of matched strings for a variable-length pattern, Unified CM takes into account only the number of matched  strings that are equal in length to the number of digits dialed. Assuming a user dials 1311 and we have patterns 1XXX, 1[2-3]XX, and 13!, the following table shows the number of matched strings of these potentially matching patterns....In this example the variable-length pattern 13! is selected as the best match.
> 
> Changing temporarily the translation pattern with a leading # and then going back to the original form, the pattern 1XXX started to be matched.
> 
> What do you think, guys? is this a bug or are 1! and 1XXX equal-precision matches from cucm point of view?
> 
> Thank you
> _______________________________________________
> 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/20141209/580d7a16/attachment.html>