Address TTY Call Handling at LNG and LPG

i3 v3 Work Items:

TTY
Address TTY call handling at LNG and LPG
Need to address “silent” calls to the PSAP
Callback with media other than voice (i.e., Butt Calls: PSAPs would like to initiate a text back advising a call was received by 9-1-1 – if you need help call 9-1-1 or text back)
Align w/ATIS on RTT

Emergency Call Transfer
STA-010.2 indicates 3 options; there has been a request to reduce the choices
Have been able to agree on 2, but they have different impacts on PSAP and need to be fully described in v3

Location URI Expiration
Secondary PSAPs must have the ability to de-reference a location reference that may have come from an EIDD
Location URIs need to be active for as long as Standard Operating Procedures require location associated with an emergency call to be available - currently thinking minimum of 30 min. – max of 24 hrs.
V3 should describe how long a location URI should be maintained by a LIS
Should the location be available only during a call – technical issue?? – legal issue??

Test Calls & Testing of Policy Rules
V2 discussed need for PSAP to support a test call interface
Support for testing Policy Rules needs to be done in v3
Test call generator that the PSAP can control with an interface consisting of a web service – PSAP programs the test generator – an automated test process (nena-prr-test)

MSAG Conversion Service
Further specification of this service is needed
MCS text in draft i3v3 specification is short – is it sufficient
MCS will need to be able to re-create ESN info for use by LSRGs
Association between street address information and ESN
Add ESNs in the MSAG Street Number Exception table in Appendix B to identify the ESN associated with a specific HNO, ST NAME & Community Name.

Callback Call Handling
Address callback call handling that includes media other than voice
Map Database Service
Need is for out of area PSAPs to view the local area’s map during a disaster or call processing change
Would a web service function work

Service Locator
Define a way to discover the address (interface) to file a discrepancy report on a service
Proposal for a ‘service locator’ which works much like the ‘agency locator’
Comment received that since they work the same, why not make them 1

i3 v3 Work Items
Minimum standards for PCA
Specify interworking between MSRP & TTY to support SMS Text to 9-1-1
Specify the value should be populated as the MF “TTT” value delivered to legacy PSAPs via LPGs
PSAP call control features
Data mappings
Define specific policy document structures for each of the policy instances defined for the ESRP
Operational considerations regarding the ESRP
Clarify term “near real time
Reorganization of i3 material into multiple smaller documents – break sections out to make it easier
Gateways
Logging
Additional Data
Discrepancy Reporting
Security
Data Mappings
Very controversial as there are a lot of cross references and would require opening another document
The WG does not want to break up this document as there are too many cross-references within the document.
Rate of making updates would not be an issue as it’s the same people working on this document and it would require them to attend more calls.
Searching 1 document is much easier – if things are in multiple docs I could miss something
Session participants voiced support for leaving the i3 material in a single document; suggestion to consider some kind of indexing to the various topics covered in the i3 standard

What’s Next / Action Items: