Wireless E911 Guide CG-EWCG-001
TN Errors and Corrective Action Issue 3, January 6, 2004
Table H Error Codes and Corrective Action (continued)
Error Code Error Message Occurs when. . . Corrective Action for . . .
783 Unlock failed; main
account has sublines
The incoming U FOC TN is in the
database as a main account with other
TNs shown as sublines but no U FOC
was received on the sublines(Note: Since
the main account and Calling number TN
are to be the same TN, this error would
be received only if the TN in the database
had been submitted with a different main
account on a previous SOIR.)
There are two possible corrective actions:
1. If all accounts shown with the main
account are to be unlocked submit a
U FOC for each TN associated with
the original main account.
2. If all accounts are not to be unlocked
submit a D FOC for the existing
subline showing the erroneous main
account and then resubmit an I FOC
for the TN shown with the Calling
number TN as the main account.
792 I FOC record exists
with a different
Company ID
The TN shown on the I FOC SOIR has
a different NENA Company ID than the
existing TN in the database
Verify the TN on the errored record:
• If the TN is correct and is to be
migrated, submit an E FOC on the
error record SOIR and then resubmit
a corrective SOIR with appropriate
record changes as a M FOC
• If the TN on the error record is
incorrect, submit an E FOC to delete
the error record.
6.5 Compiled Error Report
As stated earlier in this tab, it is imperative that all errors must be corrected as soon as possible. Until
an error is corrected, the information will either be in the database incorrectly or not in the database at
all. This could result in E911 calls being directed to the wrong PSAP and having to be transferred to
the appropriate PSAP.
In addition to sending the daily errors, a compiled error report will be forwarded to each Carrier on
a monthly basis in an effort to ensure that the Carrier is aware of all unresolved daily errors. The error
report is sorted in street name order to aid in resolving address errors.
Page 58