BellSouth E911 - Manual (Page 77)

CG-EWCG-001 Wireless E911 Guide
Issue 3, January 6, 2004 No Record Found (NRF) Processing
• If the TN should be in the database, a SOIR should be submitted to insert the TN record or to
resolve an outstanding error in the error file.
• Research why the record was not in the database and take action to prevent further NRF
occurrences.
• Advise INTRADO to close the NRF if the TN has been disconnected or not needed in the
database
When all NRFs on a report have been resolved, the Wireless carrier should file the NRF report and retain
for a period of one(1) year from the date of the 911 call that resulted in the NRF.
Status codes are assigned to each TN on the No Record Found Report. All NRFs are initially assigned as
“OPENED”. The status can be changed by the INTRADO Data Analyst as resolutions are completed.
“CLOSED” will be assigned as soon as the investigation is complete and the E911 database is updated.
The Analyst will assign “REF — LEC” when the investigation cannot be completed in the time frame
which the Analyst began their work. This status would be typical when additional information or action
is required from the Carrier.
The STATUS notations are described as:
Pending — In Error File (PENDERR) — Telephone number was found in the error file and has been
referred to Wireless Carrier for resolution of the error condition.
Referred to LEC (REF — LEC) — The NRF has been referred to the Carrier for resolution. The
Telephone number is not in the TN database or the error file.
If the record is found in the E911 database, the event will be “CLOSED” and the NRF will not be
forwarded to the Carrier. If the TN is found in the error file, the status will be changed to “PENDERR” and
will be included in the NRF report. The Carrier should resolve the outstanding error to prevent further
NRFs from occurring. If the record is not found in the E911 database or error file, the status will be
changed to REF — LEC and the report provided to the Carrier for resolution.
Page 67