Scott wrote:
> Why do you assume that emergency rules are always to a gateway?
Because the existing GUI won't let you enable an Emergency dial rule unless it
has at least one Gateway.
> I can't set up an internal emergency number that calls
> corporate security?
Not that I can see with the existing GUI. Sounds like a reasonable Improvement
though.
But a transformation-only dial plan rule seems like an odd place to configure
the Emergency alarm for and internal number. Maybe it's because I'm still
getting used to the fact that transformations can subsequently hit internal
numbers. But I also feel that you should be able to do it without a requiring
a transformation.
I digress though. If you can't do it today, then it's outside the scope of
XX-7822.
> > An 'Emergency dialing wizard' should by default create two rules:
> >
> > 1. A routing rule, with "Emergency" enabled. e.g. "911".
> >
> > 2. A transformation rule for stripping the Local PSTN Prefix. e.g.
> > "9911" -> "911". The Local PSTN Prefix should be prompted for, but
> > should default to the value used in a 'Local dialing wizard'. The
> > Local PSTN Prefix should be optional, and if not provided
> will simply
> > result in no transformation rule.
>
> 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?
-Paul
[email protected]
_______________________________________________
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/
