7.2 County / City / Parish Responsibility for TN Database Conversion
- Determine if all streets within the county / city / parish have been
named / numbered.
- Determine the proper handling of subscriber accounts with unnamed /
unnumbered street addresses as negotiated with the Telco.
- Provide INTRADO with MSAG ledgers identifying streets and ranges with
the correct ESN once the initial MSAG has been loaded into the E911 host database.
- Provide the ICO and other carriers with specific address information
for each account.
There are several situations that cause Telco subscriber data not to
have street names and numbers:
- The street hasn't been named or numbered by the proper authority (i.e.,
county / city / parish, Department of Transportation, etc.). Therefore, the
Telco has not been furnished with the official street names / numbers.
- The street has been named / numbered but the information has not been
furnished to the Telco. Therefore, the Telco has not updated their subscriber
records.
- The street has been named / numbered and the county / city / parish
(DOT, etc.) has furnished the information to the appropriate Telco. However,
the Telco has not updated their subscriber records with the new address.
Subscriber records that do not have MSAG valid addresses, will go to
an E911 host system error file and will not display if the subscriber calls
911. The PSAP attendant will see "No Record Found".
There are two ways the accounts in the error file may be entered into
the TN database:
- The MSAG valid address must be added to the subscriber's record OR
- A MSAG entry may be made using a Community Name only when a customer
does not live on a named or state maintained road as agreed upon by the county
/ city / parish.
It is the ICO's responsibility to review account errors sent by INTRADO
for the ICO service area and make corrections as appropriate. Error codes
and the corrective action are listing in section of this guide entitled
"Error Resolution".