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

2015-02-13 Thread Anthony Holloway
Andrew, It's an special indication from the user to the phone system that they have finished dialing the digits. Otherwise, the T.302 timer will have to expire before the call will be routed. An analogy would be like saying "over" on a walkie talkie. On Fri, Feb 13, 2015 at 5:24 PM, Andrew Grec

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

2015-02-13 Thread Ryan Huff
Andrew, Since international numbers are varying lengths, the # is used to signal the end of the number string. You can also just wait for the interdigit timeout to expire and then routing occurs. Usually as Brian mentioned, both are supported because it usually comes down to a user prefer

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

2015-02-13 Thread Ryan Huff
Brian, I suppose I wasn't clear on that. The octothorpe was dialed at the end of the international pattern in production and with DNA. Only when I removed the octothorpe from the pattern did routing occur. Thanks, Ryan Huff___ cisco-voip mailing l

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

2015-02-13 Thread Anthony Holloway
Brian, I agree with you on the trailing hash requirement. DNA will not make a match for you unless you typed the hash at the end. [image: Inline image 1] [image: Inline image 2] Also, the PreDot/Trailing # is only needed for Translation Patterns. Route Patterns strip the trailing hash automat

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

2015-02-13 Thread Andrew Grech
Why do we include a # for international? On 14/02/2015 8:06 AM, "Brian Meade" 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

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

2015-02-13 Thread Nick Thompson
Use 9.011![0-9#] and pre-dot trailing pound if you want a single route pattern. On Feb 13, 2015, at 3:56 PM, Brian Meade mailto:bmead...@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'

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

2015-02-13 Thread Jason Aarons (AM)
Use 9.011![0-9#] From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Brian Meade Sent: Friday, February 13, 2015 4:57 PM To: Ryan Huff Cc: cisco-voip@puck.nether.net Subject: Re: [cisco-voip] Strange routing behavior cucm 10.5 and int'l pattern If your route patte

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

2015-02-13 Thread Brian Meade
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 wrote: > Try this one on; > > Was working fine ... > > St

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

2015-02-13 Thread Ryan Huff
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 in