On Wed, 2008-08-20 at 13:43 -0400, Carolyn Beeton wrote: > I've attached a prototype of an alarm generated when a dialed number is > matched by an Emergency Dial Rule. Actually in the attachment I'm just > logging, but this is where an alarm could be generated. > > I've added a "notify" field to the xml for the rule, which is only set > to true for Emergency rules (but could conceptually be set for any rule > type). When the rule is matched, if "notify" is true then something > like the following is generated: > > "Emergency dial rule 'cb Emergency dialing plan' was invoked by > '<sip:[EMAIL PROTECTED]>' Contact: > <sip:[EMAIL PROTECTED]:5060>" > > So, what do you think? I'm not sure I have all the right bits and > pieces displayed, but I am more concerned right now with finding out > whether this approach has any merit whatsoever.
One possible problem with implementing the notification in the dial rule redirector itself is that at that point we don't know that we're actually going to make that call. A redirector provides contacts, but subsequent redirectors can modify or override those contacts or even turn the response into an error. In addition, there are many other redirectors that might well be used to provide the contact that is an 'emergency' call. A better place to put detection/notification might be on the outbound side of the proxy in an AuthPlugin. At that point we know that the call is actually being made, and it's not sensitive to what other things might have happened in the redirector chain. _______________________________________________ sipx-dev mailing list sipx-dev@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
