TAC should be able to direct it. I believe each local theater handles
their own dial plans so they should hopefully be familiar with the change.
On Fri, Sep 1, 2017 at 10:53 AM, Gary Parker wrote:
>
> > On 1 Sep 2017, at 15:43, Scott Voll wrote:
>
> On 1 Sep 2017, at 15:43, Scott Voll wrote:
>
> Gary--
>
>> Pattern:0+1[2-9][02-9]X+[2-9]X
>>
>> Failing number: 0 1 908 0 67000
>> ^ this is where the match fails, it’s not a
>> digit between 2-9
>
> could it be
Gary--
Pattern:0+1[2-9][02-9]X+[2-9]X
Failing number: 0 1 908 0 67000
^ this is where the match fails, it’s not
a digit between 2-9
could it be the 0 between the 8 and 6?
On Fri, Sep 1, 2017 at 6:55 AM, Gary Parker
> On 1 Sep 2017, at 14:44, Scott Voll wrote:
>
> have you used DNA to confirm it's not matching something else?
>
> Scott
Yes, definitely. DNA came back with “unallocated number”.
Gary
___
cisco-voip mailing list
have you used DNA to confirm it's not matching something else?
Scott
On Fri, Sep 1, 2017 at 3:01 AM, Gary Parker wrote:
> Morning all, I came across a significant block of numbers in the UK that
> can’t be called by our cucm (11.5.1(SU2) with the 3.1.34-GB dialplan)
Morning all, I came across a significant block of numbers in the UK that can’t
be called by our cucm (11.5.1(SU2) with the 3.1.34-GB dialplan) due to them not
being recognised as valid NATIONAL calls.
Milton Keynes numbers (01908) hit the following rule:
Pattern: