On Fri, 2010-05-07 at 14:43 -0400, Mossman, Paul (Paul) wrote:
>
> > Why treat any part of the dial string specially? Allow any
> > number of strings to be mapped using a normal rule
> > construction, and just add the 'emergency' bit you suggest.
> > It should prevent any permissions from being needed and
> > trigger the notification.
>
> Are you suggesting a single normal ("Custom") rule that matches both
> 911 and 9911?
>
> You mentioned to me last week that there's a syntax which could
> achieve this. My gut instinct is that we should not ask admins to
> learn this grammar. But, maybe it isn't too ugly?
Admins should not have to learn any syntax for creating any dial rule.
You can do rules that match multiple digit sequences now; that's what
the Add link (which should be a button, not a link, but that's a
different rant) to the right of the input specifier does. This
translates into multiple <userPattern> elements in the rules:
so
<userMatch>
<userPattern>9911</userPattern>
<userPattern>911</userPattern>
...
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
