[PREV][NEXT]CG-IEIK-001
Issue 4-August 1, 2005

CHAPTER 7.0 - TN Database Conversion and Updates

7.13 TN Conversion Load / Daily Updates Header and Trailer (512 Format)


If using the 512 record format, INTRADO can accept an initial load and ongoing daily updates with the same specifications as shown:

7.13.1 Update File Header Record - BellSouth 512 Character Format for Data Exchange

Field Name   Position   Bytes   Type   BellSouth Description  
Header Indicator   1 - 5   5   A   Always "UHL"  
Extract Date   6 - 11   6   N   Date formatted as MMDDYY  
Company Name   12 - 61   50   AN  
 
Cycle Counter   62 - 67   6   N   New customers start at 000001; each subsequent file cycle is incremented by one(1) until reaching 999999  
County Identifier   68 - 71   4   AN  
 
State   72 - 73   2   A  
 
General Use   74 - 93   20   AN  
 
Release Number   94 - 96   3   N  
 
Format Version   97   1   N  
 
Reserved   98 - 511   414   AN  
 
End of Record   512   1  
 		 Always "*"  

7.13.2 Update File Trailer Record - BellSouth 512 Character Format for Data Exchange

Field Name   Position   Bytes   Type   BellSouth Description  
Trailer Indicator   1 - 5   5   A   Always "UTL"  
Extract Date   6 - 11   6   N   Date formatted as MMDDYY  
Company Name   12 - 61   50   AN  
 
Record Count   62 - 67   9   N   Does not include header and trailer record  
Reserved   71 - 5111   441   AN  
 
End of Record   512   1   AN   Always "*"  

7.13.3 Update File Data Record - BellSouth 512 Character Format for Data Exchange


Table G. Update File Data Record (Required fields are bolded in the Field Name column)

Sent to PSAP   Stored in Database   Field Name   Position   Bytes   Type   BellSouth Description  
No   No   Function Code   1   1   A   Type of activity the record is being submitted for. Valid entries:
  • C Change,
  • D Delete,
  • P Main account delete,
  • I Insert,
  • EDelete Error,
  • U Unlock (LNP),
  • M Migrate (LNP). (NOTE: Initial load will always be sent as an I function of change.
 
Yes   Yes   NPA   2 - 4   3   N   Three digit area code of the Calling Number or ESQK. Must be geographically correct for the E911 tandem used to route calls to the PSAP. (see RCF field for foreign numbers)  
Yes   Yes   Calling Number (TN)   5 - 11   7   N   Seven digit telephone number of the Calling Number or ESQK. Must be geographically correct for the E911 tandem used to route calls to the PSAP. (see RCF field for foreign numbers)  
Yes - Only eight(8) characters sent to PSAP.   Yes   Hose Number   12 - 21   10   AN   House number. The field should be space filled if no house number is available.  
Yes   Yes   House Number Suffix   22 - 25   4   AN   House number extension (e.g., 1/2). The field should be space filled if suffix does not apply. Do not lead with hyphen.  
Yes   Yes   Prefix Directional   26 - 27   2   A   Leading street direction prefix.The field should be space filled if no prefix applies. Valid entries: N, S, E, W, NE, NW, SE, SW.  
Yes - Only 48 characters sent to PSAP.EX: Main St NW   Yes   Street Name
Street Suffix
Post Directional  		 28 - 93   66   AN   MSAG valid service address of the Calling Number or ESQK. Include street name, street suffix (i.e.thoroughfare designation) and post directional. Street Suffixes must conform to BellSouth MSAG standards; valid Post Directional entries are: N, S, E, W, NE, NW, SE, SW.  
Yes - Only 18 characters sent to PSAP.   Yes   Community Name   94 - 125   32   A   Valid service community of the street name/house number as designated by the MSAG.  
Yes   Yes   State   126 - 127   2   A   Alpha postal state abbreviation (e.g., AL, FL, GA, KY, LA, MS, NC, SC, and TN).  
Yes - Only twenty(20) characters stored and sent to PSAP.   Yes   Location   28 - 187   60   AN   Additional address information (free formatted) describing the exact location of the Calling Number (e.g., Apt 718).  
Yes   Yes   Customer Name   188 - 219   32   AN   Subscriber name associated with the Calling Number.  
Yes - (4 character translated value)   Yes   Class of Service   220   1   AN   Value of:
  • 1=Residence
  • 2=Business
  • 5=Centrex/Essx
  • 6=Semi-Public Coin
  • 7= Public Coin
  • 8=Mobile (ICO only)
  • 9=DPA
  • Residence
  • 0=DPA Business
  • A=Outdial Semi-Public Customers
  • B=Outdial Public Customers
  • V=VoIP (ESQK shell records only)
 
No   Yes   Type of Service   221   1   N   Valid codes:
  • 0=Not Non-pub or FX
  • 1=FX not Non-pub
  • 2=Not used
  • 3=Non-pub, not FX
  • 4=Non-pub, FX
  • 5=Not used
 
No   Yes   Exchange   222 - 225   4   AN   Phone company exchange identifier for the serving telephone office of the customer; ALEC and Wireless may be blank.  
Yes - Only three(3) characters sent to PSAP.   Yes   ESN   226 - 230   5   AN   Emergency Service Number associated with the House Number and Street Name; this field is blank on input and derived from the MSAG validation process.  
No   No   Main NPA   231 - 233   3   N   Same area code as found in NPA field. Positions 2-4.  
Yes   Yes   Main Number   234 - 240   7   N   Same telephone number as found in Calling Number (TN) field. Positions 5-11. All TNs are pilots. Do not send sub / pilot relationships.  
No   Yes   Order Number   241 - 250   10   AN   Service order number for the activity establishing this record.  
No   Yes   Extract Date   251 - 256   6   N   Date on which the record was created in the format MMDDYY.  
No   Yes   County Identifier   257 - 260   4   AN   County Identification code (usually the FIPS code). Will be blank on input and derived from MSAG validation process.  
Yes   Yes   Company ID   261 - 265   5   AN   Telephone Company Identification code as assigned through NENA registration process.  
No   Yes   Source Identifier   266   1   AN   Code which indicates whether data is part of the initial database creation process or part of the daily update process.
  • Daily=Space,
  • Initial Load=C.
 
No   Yes   Zip Code   267 - 271   5   AN   Postal Zip Code.  
No   Yes   Zip + 4   272 - 275   4   AN   Postal Zip Code Extension.  
No   No   General Use   276 - 286   11   AN   This field is mutually used by data exchange partners to pass information not defined in previous fields.  
No   Yes   Customer Code   287 - 289   3   AN   Code used to uniquely identify a customer. For ICO, ALEC, and Wireless companies this code can be blank on input or filled with 999. TN processing will convert all blanks to 999.  
No   Yes   Comments   290 - 319   30   AN   Optional notes  
No   No   X Coordinate   320 - 328   9   AN   Reserved for future use. Longitude / X coordinate.  
No   No   Y Coordinate   329 - 337   9   AN   Reserved for future use. Latitude / Y coordinate.  
No   No   Z Coordinate   338 - 342   5   AN   Reserved for future use. Structure elevation.  
No   No   Cell Identifier   343 - 348   6   AN   Reserved for future use. Identification number indicating a geographic region of cellular coverage.  
No   No   Sector Identifier   349   1   AN   Reserved for future use. Subset / section of a cell.  
No   Yes   Tar Code   350 - 355   6   AN   Taxing Area Rate Code. ALEC and Wireless populate with zeros.  
Yes   Yes   Remote Call Forward Number (RCF)   356 - 365   10   N   Remote Call Forward Number; VoIP subscriber records may use this field for the subscriber's telephone number if it is not geographically correct for the E911 tandem that will route 911 calls to the PSAP. For ESQK shell records that will be updated dynamically, this field should contain spaces when sent in the SOIR file. This field will be populated dynamically with the subscriber's call back number via the E2 interface. This field will be sent to the PSAP following the field identifier of ALT#  
No   No   Reserved   366 - 511   146   AN   This field is reserved for the processing company's use.  
No   No   End of Record   512   1   AN   Always an asterisk (*)  





[PREV][NEXT]

© 2005 BellSouth Corp. All Rights Reserved. Legal Notices & Privacy Policy

Last Updated: August 1, 2005