On Fri, 2010-05-07 at 13:51 -0400, Mossman, Paul (Paul) wrote: > Hi all, > > The only special behaviour of Emergency rules is that they trigger an > Alarm. > > I propose that this type be removed and replaced with an "Emergency" > boolean property on the basic dial rule type. "Emergency" can only be > enabled on rules with a Gateway (routing rules), and only when there > are no required permissions.
Why do you assume that emergency rules are always to a gateway? I can't set up an internal emergency number that calls corporate security? > 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. _______________________________________________ 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/
