[cisco-voip] Strange routing behavior cucm 10.5 and int'l pattern

[Andrew Grech]

Why do we include a # for international?
On 14/02/2015 8:06 AM, "Brian Meade" <bmeade90 at vt.edu> wrote:

> If your route pattern is 9.011!#, users have to dial the # at the end to
> match and your discard should be pre-dot trailing hash.  Usually you'll
> have 2 RPs for international (9.011! and 9.011!#).
>
> On Fri, Feb 13, 2015 at 3:29 PM, Ryan Huff <ryanhuff at outlook.com> wrote:
>
>> Try this one on;
>>
>> Was working fine ...
>>
>> Standard Int'l route pattern 9.011!# Discard set to PreDot (again, this
>> was working ... no issue on gateway ... etc)
>>
>> So today it stops working, just rings busy. I debug the ISDN and it shows
>> called party as the last 7 digits. I go over to DNA and use an int'l
>> pattern with the css I was using and it blocks pattern for unallocation.
>>
>> I create a new test partition with a new 9.011!# pattern in it and a new
>> css with only the new partition in it. I go back over to DNA and try the
>> int'l pattern with the new test css and it blocks for unallocated.
>>
>> Now I scratch my head, so I take off the octothorpe on the pattern
>> (9.011!) and BOOM, DNA routes and everything is happy. I move to production
>> and it works just fine without the octothorpe.
>>
>> What does this sound like? Do you think I may have competing patterns
>> somewhere in the dial plan?
>>
>> Thanks,
>>
>> Ryan
>>
>> _______________________________________________
>> 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/20150214/d0afd346/attachment.html>