|
[
Permalink
| « Hide
]
Jesse Becker added a comment - 2008-07-26 22:53
I believe this option is definitely worth pursuing. Most of the competitive systems allow advanced E911 with locations. I believe it would be a good idea to add a 'location' field to both users and phones. When someone calls 911 an email message can be assigned to assigned personnel containing the extension (or URI) that called 911 as well as the location fields fulled from the user and registered phone (user agent).
I would also suggest that several 911 dial plans can be created so you can manipulate the external caller ID on emergency calls only. We currently use a product called Cisco Emergency Responder. This allows you to create emergency zones and emergency lines. You then assign phones to these zones. When someone calls 911 the external caller id is masked with the emergency lines number. This allows the E911 PSAP to full up specific location information from there database on the emergency line. At our site, each building and floor is assigned a different zone/emergency line. This option would allow the user/extension to have it's regular caller id when making normal local and long distance calls, however, have a special E911 caller id when dialing 911.
I would be glad to work with anyone interested in developing and testing this feature. I am note good with the coding side, however, I could help out with functional ideas and testing. There are repeated requests for this feature and I therefore suggest this as a candidate for 4.0
Can you look at this and compare it to the work you had done.
Attaching patches for review by sipXproxy (patch 0001-) and sipXconfig (0002-) reviewers (the config patch generates a new emergencyrules.xml file which contains all the configured emergency numbers).
These patches create an auth plugin to generate an alarm when an emergency dial rule is matched. The alarm includes the SIP user and contact address of the caller. Please comment. Freshening up both patches.
Replaced patches with a version that extends authrules.xml with a <ruleType> tag to identify Emergency rules. At this time, other rule types are not identified. The function UrlMapping::getUserMatchContainerMatchingRequestURI is modified to check first for the specified ruleType if given (other plugins using authrules.xml do not specify a ruleType).
Done reviewing changes; assigning issue back to fixer.
Code was committed in r14629.
As a first pass at emergency notification, an alarm email will be sent when an Emergency dial rule is matched. The email includes the username and IP address from which the call was made. This new feature is verified as per the following steps:
1.Create an emergency dial plan. 2.Navigate to Alarms tab in diagnostics menu. 3.Enter your e-mail address in 'To email addresses' edit box. 4.Ensure Emergency number dialed under Alarm title is enabled and apply the changes. 5.Make a call to the emergency number(911),gateway phone rings.Call is established between these 2 phones. 6.Immediately an alarm mail is sent to your e-mail address. The mail snippet is as follows: Message from sipXecs Alarm: SPX00012 Reported on: sun.qantom.int Reported at: 2009-02-03T10:18:47.278238Z Severity: CRIT Alarm Text: Emergency dial rule 'Emergency (Emergency dialing plan)' was invoked by '"S A"<sip:143@sun.qantom.int>' contact sip:143@176.25.2.193;x-sipX-nonat Suggested Resolution: A user has dialed a number which is configured as an Emergency number. The user name and contact address of the phone is given. Hence,this feature is working fine under the following build. sipxproxy 3.11.9-014635 2009-02-03T02:13:24 oem-centos5 sipxconfig 3.11.9-014635 2009-02-03T02:30:00 oem-centos5 Therefore,this issue can be closed. |
||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Closed
Minor
Emergency call notification
