Our Customers ...

 

Implementation and Ongoing Maintenance for E911

Any organization considering the administration of E911 in house should take into account the following:

  • Complicated and time-consuming implementation
  • A full time employee dedicated to regular E911 maintenance
  • Employee turn-over and training
  • Possible liability risk for unresolved errors

911 ETC provides:

  • Full time customer support with a trouble ticketing process
  • Ongoing scheduled database management services
  • Synchronized error correction and status reconciliation
  • Data reports available upon request
  • Full data back-ups
  • Data file processing logs and notifications
  • Interface support with telco contacts for routing issues
  • Testing support
  • E911 database design consulting
  • Custom data loaders to accommodate your database needs

Our solution is never in a “box”. We are constantly making improvements to our product based on individual customer requests. Each one of these improvements and upgrades require no action on the part of our customers because the solution is hosted by us. We welcome and encourage suggestions from our customers to improve upon our service and our product. We recognize also that our customer’s business is always changing and that its needs might change. Our service is available to adapt to the customer’s needs when change affects E911.

Status and Error Reconciliation

911 ETC not only has developed error filters for customer submitted location data, but we have also developed a status and error file processor which matches status and error files coming back by cycle count to the original NENA file submitted to the ALI database. Any errors reported back are processed and exported into a report which is attached to a workable ticket with a ticket number and is assigned to a 911 ETC data analyst for resolution. Each ticket is monitored by date for closed out status.

Maintenance

A major part of E911 is the maintenance that is required whenever a telephone extension is activated, deactivated or changes location. 911 ETC has gained many new customers who have tried to administer E911 changes in house and discovered that the task was overwhelming and frustrating. 911 ETC has never lost a customer to a competitor, and yet we’ve gained numerous customers who previously had a competitor’s box installed without realizing the ongoing need for E911 data maintenance. While making the changes may seem fairly straightforward, there are numerous points of failure when it comes to submitting a proper record to the ALI database. The following is a sampling of potential error codes that may be returned when submitting records to ALI along with the vague descriptions that accompany them:

100

CUS CODE NOT NUMERIC

  

730

REC IN DISC NOT < COMPLETE DATE

101

NPANXX RECORD NOT FOUND

  

731

REC EXISTS LATER OR = CMPLT DATE

102

UNKNOWN ERROR

  

732

REC IN DISC WITH > CMPLT DATE

103

PILOT NUMBER NOT NUMERIC

  

733

NEW NUMBER ALREADY EXISTS

104

UNKNOWN ERROR

  

734

LINE DEL OF PILOT WITH SUBLINE

105

NAME MISSING

  

735

NO DELETE SAME COMPLETION DATE

106

LAD OR SAD IS IN BAD FORMAT

  

736

PILOT IS SLA CANT USE ADDR

107

HOUSE NUMBER IS INVALID

  

737

LOC FLAG IS ON NO ADDR UPDATE

108

HOUSE NUMBER TOO LONG

  

738

MSAG UPDATE CAUSED ERROR

109

STREET DIR TOO LONG

  

739

INVALID HOUSE FORMAT

110

STREET DIR IS INVALID

  

740

STREET NAME IS TOO LONG

111

STREET NAME TOO LONG

  

741

PSALI/ACM LOCKED RECORD

112

STREET NAME IS INVALID

  

742

SERVICE CLASS DOESNT MATCH PILOT

113

CITY NAME IS TOO LONG

  

743

SERVICE TYPE DOESNT MATCH PILOT

114

CITY NAME IS MISSING OR INVALID

  

744

CUS NAME DOES NOT MATCH PILOT

115

USOC/CLASS OF SERVICE NOT IN TBL

  

745

RANGE FITS IN MUTILPLE CITY EXCH

116

HOUSE SUFFIX INVALID

  

746

COMMUNITY AND EXCH ARE BLANK

117

ILLEGAL ACTION ON PILOT

  

747

CLLI DOES NOT MATCH MSAG CLLI

118

N OR T ORDER HAS NO PILOT ACTION

  

748

LOCATION DOESNT MATCH PILOT

119

TN / DX / PX INVALID FORMAT

  

749

CUS CODE DOESNT MATCH PILOT

120

TN,CX OR PX INCORRECTLY FORMATED

  

750

TAR CODE DOESNT MATCH PILOT

121

LOC INFO ERROR (CLASS SVC=5)

  

751

INVALID FUNCTION CODE

122

MULTIPLE ACTIONS FOR TN

  

752

INVALID COMPANY CODE

123

SLA FORMAT IS INCORRECT

  

753

NO RECORD EXISTS ON UNLOCK

124

TWO TN'S ON S&E LINE (TN,CX,PX)

  

754

NO RECORD EXISTS ON LOCK

125

MISSING TN FOR USOC

  

755

UNABLE TO MIGRATE LOCKED REC

126

INVALID TYPE OF SERVICE

  

756

COMPANY CODE MISMATCH ON CHANGE

127

LANGUAGE INFORMATION INVALID

  

757

COMPANY CODE MISMATCH ON DELETE

128

MEDICAL INFORMATION REQUEST

  

758

COMPANY CODE MISMATCH ON UNLOCK

129

LANGUAGE INFORMATION REQUEST

  

759

COMPANY CODE MISMATCH ON LOCK

701

RANGE NOT FOUND

  

760

LOCK EXCEED NUMBER OF RETRIES

702

RECORD EXISTS NO INSERT

  

761

PILOT COMPANY CODE MISMATCH

703

PILOT RECORD NOT FOUND

  

762

LNP REQUIRED ON U OR M FUNCTION

704

NO RECORD EXISTS FOR DELETE

  

763

PILOT DELETE ORPHANED SUBLINES

705

PILOT NOT FOUND FOR DELETE

  

764

PILOT AND SUBLINE REQUIRE VERF

707

PILOT CUS CODE MISSING ON INSERT

  

765

INVALID CLLI

708

INVALID CLLI CODE

  

777

MISSING COMPANY CODE

709

STREET NOT FOUND

  

778

CUSTOMER DESIGNATOR NOT SET UP

710

CUS CODE MISMATCH ON CHANGE

  

781

DELETE-ERROR RECORD NO TN MATCH

711

CUS CODE MISMATCH ON DELETE

  

782

DELETE-ERROR RECORD NO COMPANY MATCH

712

RECORD DOES NOT EXIST FOR CHANGE

  

783

UNLOCK FOR PILOT WITH SUBLINES

713

TN AND PILOT NUMBER MISMATCH

  

784

PILOT SPLIT INSERT FAILED

729

CD ERROR DATE CONFLICT

  

792

REC EXISTS FOR ANOTHER COMPANY