> > 
> > Hi Nikolay,
> > 
> > It seems to have problems in some specific dial plan scenerios, e.g.
> >   Dial Number:
> >     Prefix = 9[3-4] and 6 digits
> >   Resulting call:
> >     Dial = 63 and matched suffix
> > Call to 93932738 fails "Not found" (expect it to call 63932738)
> > 
> > The authrules.xml shows:
> >    <userPattern>63[3-4]xxxxxx</userPattern>
> > which doesn't seem right, I would have expected 6[3-4]xxxxxx.
> > 
> > Dave
> 
> 
> I looked at your *rules files.
> What's easy to forget is that if you use expressions like 
> [3-4] they become a part of "Variable part of the dialed 
> number" a.k.a. {vdigits}.
> 
> >
> > In the attached rules:
> > Ottawa:
> >   Dial Number:
> >     Prefix = 9[3-4] and 6 digits
> >   Resulting call:
> >     Dial = 63 and matched suffix
> > Call to 93932738 fails "Not found" (expect it to call 63932738)
> 
> Your 'Ottawa' rule looks like this:
> 
>       <!--Ottawa-->
>       <userPattern>9[3-4]xxxxxx</userPattern>
>       <transform>
>         <user>63{vdigits}</user>
>         <host>XXX.XXX.XXX.XXX</host>
>         <headerparams>expires=60</headerparams>
>         <fieldparams>q=0.9</fieldparams>
>       </transform>
> 
> Which means that dialing 93932738 will give you 633932738 - 
> note that you have 3 as a part of 63 prefix *and* as a part 
> of "variable digits".
> This is why the call fails.
> 
> 

The problem with this is that the GUI shows the Prefix=9[3-4],
and the resulting call is configured to dial 6 plus the suffix. 
The current functionality is that part of the prefix 
gets included in the suffix, which really doesn't make sense
from the GUI point of view. 

If the [3-4] is not part of the prefix I would think that it 
shouldn't be shown in the prefix field, otherwise how's the 
installer supposed to know what the real prefix is?

The page itself says:
  Prefixes can be integers (e.g. 2), ranges (e.g. 1-5),or lists (e.g.
2,3,4)

There's no mention that ranges and lists will be treated differently.
(Note: the page comment is missing the [] around the ranges and lists)

Dave.


_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev

Reply via email to