1 / 10

NG911 – Development plans

NG911 – Development plans. Henning Schulzrinne Columbia University. Overview. Web interface Responder bridging Geo-based call routing Video insertion Redundancy and reliability Event classification External information display Automated caller information. Web interface.

frederique
Download Presentation

NG911 – Development plans

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NG911 – Development plans Henning Schulzrinne Columbia University

  2. Overview • Web interface • Responder bridging • Geo-based call routing • Video insertion • Redundancy and reliability • Event classification • External information display • Automated caller information

  3. Web interface • Show call log by time/date, call taker, incident type, … • Show details about each call (duration, location, incident) • including link to recording • Show incidents – all related calls • Statistics and graphs: • current call volume • call volume per hour • call volume over time

  4. Responder bridging • Add responders to bridging and transfer buttons • based on caller location • stored in DNS record (PSAP internal?) • includes fixed ones, like language line and poison control center

  5. Geo-based call routing • Route based on long/lat • Initially DNS, possibly IRIS as query protocol later DNS PTR (.us) get list of URLs AK, AL, …, WV, WY boundary (XML) boundary (XML) boundary (XML) boundary (XML) boundary (XML)

  6. Video (media) insertion media store • Call taker can insert video streams into call conference • full VCR control • talk over video • e.g., first-aid or CPR video RTSP

  7. Redundancy and reliability • No single point of failure • SIP proxy, SIP controller, SIP conference server • Use DNS SRV to pick alternate • No mid-call recovery for SIP controller, SIP conference server • Call controller: automated overload redirection to other PSAP

  8. Event classification • Call taker classify incidents with admin-definable table of events and associate with existing events • e.g., “car accident on 5th and Main” • Present most common incident types • Present event log: all calls associated with incident • Later: use for automatic overload response

  9. External information display • Associate calls with external information • Floor plan • Medical information • Render in browser at call taker • Use SIP Call-Info header • Call-Info: <http://example.com/map.html>;purpose=map • Initially, link to web pages • inserted at in-bound proxy derived from database • inserted by caller (or his outbound proxy)

  10. Automated caller information • During heavy load, synthesize incident information • “All call takers are busy right now. If you’re calling about the car accident on 5th and Main, please note that help has been dispatched. If you are calling about another incident, please stay on the line.” • Is this useful? Alternative is busy signal or redirect to secondary PSAP.

More Related