BellSouth E911 - Manual (Page 58)

Wireless E911 Guide CG-EWCG-001
TN Errors and Corrective Action Issue 3, January 6, 2004
to Intrado Connect, (2) click on the transfer key, and (3) click on the download key and automatically
retrieve your reports.
6.2.4 TN Error Deletion
When a SOIR is processed, a check is made to determine if an error record exists in the error file with the
same TN on the SOIR. If an error record other than a U (Unlock) or M (Migrate) exists, the error record
will be deleted and the TN will be processed to the E911 Database if the subsequent SOIR is successful. If
an error other than for a U (Unlock) or M (Migrate) SOIR occurs while processing the subsequent SOIR, a
new error record will be written to the error file, thus only one SOIR record should ever be present in the
error file for any given TN.
TN error records requiring deletion will be deleted by issuing a subsequent SOIR with an FOC = "E".
When the FOC = "E" on the subsequent SOIR, the error file will be searched for a match on TN and, if
found, the error will be deleted from the error file. SOIRs sent with a FOC of "E" are used ONLY to
delete a TN from the error file and are not processed to a matching TN embedded record in the E911
database. An example of a situation where an "E" FOC might be used is to delete a TN error record where
the original SOIR had been with an invalid TN.
6.3 Error Codes and Error Descriptions
The following error codes may be generated and sent via fax.
Note: If an error code is received that is not reflected in this guide, please refer to the BellSouth
Wireless E911 Implementation Manager.
Table G Error Codes and Error Descriptions
ERROR DESCRIPTION
100 Customer Code not numeric
101 NPA/NXX not valid
103 Main TN not numeric
105 Name Missing
106 Address Missing
107 House number contains invalid characters
108 House number is too long
109 Street direction is too long
110 Street Direction is invalid
111 Street name is too long
- continued -
Page 48