@BE1'50UTH*
`
`TeMeSSee
`
`NOl'1h~lln1
`
`BellSouth Enhanced 911
`File Transfer System (FTS)
`Data base Activity Update Service
`for PBX User/ALI Customers
`l\letwork Interface Specifications
`
`Technical
`Reference
`
`Intrado Ex. 1038 - 1
`
`

`

`TR 73577
`
`NOTICE
`
`This Technical Reference is published by BellSouth Telecommunications, Inc. and
`describes the Network Interface specifications for BellSouth Enhanced 911 File Transfer
`System (FTS) Database Activity Update Service for PBX customers with Automatic
`Location Identification (ALI) functionality. The offering of this service, in whole or in
`part, is subject to approval by the appropriate regulatory bodies.
`
`BellSouth Telecommunications, Inc. reserves the right to revise this document for any
`reason, including but not limited to, conformity with standards promulgated by various
`governmental or regulatory agencies, utilization of advances in the state of the technical
`arts, or the reflection of changes in the design of any equipment, techniques, or
`procedures described or referred to herein. Liability to anyone arising out of use or
`reliance upon any information set forth herein is expressly disclaimed, and no
`representations of warranties, expressed or implied, are made with respect to the accuracy
`or utility of any information set forth herein.
`
`This document is not to be construed as a suggestion to any manufacturer to modify or
`change any of it products, nor does this document represent any commitment by
`BellSouth Telecommunications, Inc. to purchase any product whether or not it provides
`the described characteristics.
`
`Nothing contained herein shall be construed as conferring by implication, estoppel or
`otherwise, any license or right under any patent, whether or not the use of any information
`herein necessarily employs an invention of any existing or later issued patent.
`
`If further information is required, please contact:
`
`Director - Transport Systems Engineering
`BellSouth Telecommunications, Inc.
`1884 Data Drive
`Birmingham, Alabama 35244
`
`Copyright© 1993 BellSouth Telecommunications. All Rights Reserved
`Printed in the U.S.A.
`
`Intrado Ex. 1038 - 2
`
`

`

`TR 73577
`Issue A, June, 1993
`
`BELLSOUTH ENHANCED 911
`FILE TRANSFER SYSTEM (FTS) DATABASE
`ACTIVITY UPDATE SERVICE FOR PBX USER/ALI CUSTOMERS
`NETWORK INTERFACE SPECIFICATIONS
`
`CONTENTS
`
`1.
`
`2.
`
`3.
`4.
`
`5.
`
`6.
`
`GENERAL DESCRIPTION OF E911 SERVICE FOR PBX/ALI USERS
`FIGURE 1 - PBX/ALI DATABASE UPDATE CONFIGURATION...................
`
`DEFINITIONS, ABBREVIATIONS, ACRONYMS AND SYMBOLS . . . . . . . . . . . . . . . . . . . . . . .
`
`TECHNICAL SPECIFICATIONS FOR ALI DATABASE UPDATE . . . . . . . . . . . . . . . . . . . . . . . .
`FILE TRANSFER SYSTEM (FTS) RECORD FORMAT
`
`1
`2
`
`2
`
`3
`
`FIGURE 2 - FTS RECORD FORMAT
`FILE TRANSFER SYSTEM (FTS) RECORDS DESCRIPTION
`
`REFERENCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
`
`Intrado Ex. 1038 - 3
`
`

`

`TR 73577
`Issue A, June, 1993
`
`BELLSOUTH ENHANCED 911
`FILE TRANSFER SYSTEM (FTS) DATABASE
`ACTIVITY UPDATE SERVICE FOR PBX USER/ALI CUSTOMERS
`NETWORK INTERFACE SPECIFICATIONS
`
`1.
`
`GENERAL DESCRIPTION OF E911 SERVICE FOR PBX/ALI USERS
`
`1.1
`
`1.2
`
`1.3
`
`1.4
`
`1.5
`
`1.6
`
`The E911 Private Branch Exchange/Automatic Location Identification (PBX/ALI) Service provides a
`PBX customer, located in an E911 serving area, with the ability to offer full E911 service to it's station
`users. Ordinarily, the location identification information displayed on a Public Service Answering Point
`(PSAP) attendant screen for a caller from a PBX not equipped with this service will be a billing or ser(cid:173)
`vice number and address of the PBX (the station may be extended to a different premises, normally
`referred to as off-premise extensions). This information may not indicate the actual physical location
`from which the call is placed. With the PBX/ALI service the "off premise" location identification infor(cid:173)
`mation is available to the PSAP when a caller, using a connecting station of the PBX, dials 911.
`
`PBX/ALI service provides the PBX customer with private E911 trunks from their PBX (i.e., private
`switch) to the E911 Tandem. To utilize this service, the PBX must be capable of sending the calling sta(cid:173)
`tion's telephone number to the BellSouth E911 network in a specified Multifrequency (MF) Address
`Signaling "protocol". This "addressing protocol" information is known as Automatic Number Identifi(cid:173)
`cation (ANI), and when received, is routed by the BellSouth E911 Tandem to the appropriate PSAP.
`At the PSAP the data specific to the calling station is accessed from Automatic Location Identification
`(ALI) databases maintained by BellSouth.
`
`This critical data associated with the calling location, including the telephone number, name, address,
`and the nearest responding emergency agencies, greatly enhances the speed and efficiency of the PSAP
`dispatch operation.
`
`Updates to this station data are supplied to BellSouth by the customer as required by moves and
`changes in a dial-up access basis. The manner and frequency in which these updates are accomplished
`is negotiated between the customer and BellSouth.
`
`This document describes the network interface specifications for the ALI database update service for
`the BellSouth E911 FTS computer system. It describes the dial up access procedures.
`
`This document is intended as a guide for PBX customers requiring an understanding of the technical
`aspects of the PBX/ALI service and the need for having an accurate and up-to-date ALI database
`for E911.
`
`Page 1
`
`Intrado Ex. 1038 - 4
`
`

`

`TR 73577
`
`1.7
`
`Figure 1 below illustrates the PBX/ALI database update configuration.
`
`Customer Network Interface
`
`ALI
`Database
`
`Customer
`PBX
`
`Daily Moves
`
`and Changes
`
`PC with
`Modem
`
`BellSouth
`Modem
`Interface
`
`BellSouth
`
`E911
`
`Computer
`
`FIGURE 1 - PBX/ALI DATABASE UPDATE CONFIGURATION
`
`2.
`
`DEFINITIONS, ABBREVIATIONS, ACRONYMS AND SYMBOLS
`
`AUTOMATIC LOCATION
`IDENTIFICATION (ALI)
`
`with ALI capabilities.
`
`CENTRALIZED
`AUTOMATIC MESSAGE
`ACCOUNTING (CAMA)
`
`system, etc.
`
`CUSTOMER
`
`The term denotes the automatic location identification of
`the calling station (i.e., directory number) that dialed
`911. This party is presumed to be an end user of a PBX
`
`The term is an arrangement that provides for the
`recording of detailed billing information at a centralized
`location other than an end office, usually a tandem office.
`CAMA equipment also may be associated with operator
`
`The term is the party which has contracted with BellSouth
`to purchase Enhanced 911 capabilities for use with a PBX.
`
`The term refers to the information communicated over
`MF PULSING
`telephone trunks by various combinations of two of five
`frequencies in the voiceband. Signals for control
`functions are provided by combinations using a sixth
`frequency.
`
`Page2
`
`Intrado Ex. 1038 - 5
`
`

`

`Iss A, TR 73577
`
`PRIVATE BRANCH
`EXCHANGE (PBX)
`
`The term refers to an assemblage of equipment that allows
`an individual within a community of users to originate and
`answer calls to and from the public network (via CO
`trunks, Wide Area Telephone Service (WATS) trunks,
`and Foreign Exchange (FX) trunks), a private network,
`another PBX (tie trunks), special service trunks, and
`other users (PBX lines) within the community. In the case
`of PBX/ALI service the PBX would use special
`"CAMA'.' trunks to the E911 Tandem.
`
`The term refers to an agency or facility that is designated
`PUBLIC SAFETY
`and authorized to receive and respond to emergency 911
`ANSWERING POINT
`calls requiring one or more public services such as police,
`(PSAP)
`fire, and/or ambulance services. Any agency, or a group
`of agencies, may be designated a PSAP.
`
`TRUNK
`This term in a telecommunications network, refers to a
`communication path connecting two switching systems
`used in the establishment of an end-to-end connection.
`
`3.
`
`TECHNICAL SPECIFICATIONS FOR ALI DATABASE UPDATE
`
`3.1
`
`3.2
`
`3.3
`
`3.4
`
`3.5
`
`3.6
`
`3.7
`
`GENERAL DESCRIPTION OF E911 DATABASE UPDATE SERVICE
`
`Traditionally once a PBX user (either on-premise or off-premise) dials "911'', the information (i.e.,
`telephone number and address) reported to their designated Public Safety Answering Point (PSAP) has
`been the one of the main PBX. However, with the Automatic Location Identification (ALI) service
`PBX station emergency information, particularly the off-premise's telephone number and location,
`can be automatically identified.
`
`There are many ways by which a PBX administrator/customer can administer the profile of PBX users.
`If properly done, the PSAP attendant's screen should have enough information displayed to identify
`the physical location of the station dialing "911".
`
`With PBX/ALI service, the PBX theoretically is equipped with a feature that identifies the location of
`"all" stations behind the PBX. This location identification of off-premise stations is either "exact" (if
`that PBX station has Direct In Dial (DID) service) or "approximate" (if the calling PBX station is near
`another PBX station that has DID service).
`
`BellSouth is willing to offer assistance to these PBX customers. However, it is the ultimate responsibil(cid:173)
`ity of the PBX administrator/customer to determine the need for DID service, their location (either
`on-premise or off-premise) identification and associated administration of their PBX database.
`
`TECHNICAL REQUIREMENTS FOR DIAL-UP ACCESS AND UPDATE
`
`The procedure to access the FTS system (i.e., telephone number, etc.) will be provided by BellSouth
`during the testing period. The following technical requirements are required in order to update the ALI
`database on a dial-up basis:
`
`A 4800 bits per second synchronous modem. This modem must be compatible with the Bell
`208NB modem.
`
`A communications software package capable of supporting the 3780 communication protocol.
`
`A personal computer (or main frame) able to run the hardware and software described above.
`
`Page3
`
`Intrado Ex. 1038 - 6
`
`

`

`TR 73577
`
`3.8
`
`The following options of IBM 3780 protocol (described in the IBM publications GA27 -3063, Compo(cid:173)
`nent Infonnation for IBM Data Communications Tenninals) are supported in the mechanized transfer
`of E911 activity:
`
`Transmission Code
`Transmission Blocksize
`Multiple Records per Block
`Blank Compression
`Transparency
`Extended ID
`Line Type
`First Speaker/Bidder
`Line Speed
`
`EBCDIC
`512 Maximum
`Yes (optional)
`No
`Required
`No
`Switched
`Caller
`4.8 KBPS
`
`3.9
`
`TECHNICAL REQUIREMENTS FOR TAPE UPDATE
`
`3.10
`
`The initial load of the customer's PBX/ALI database records are to be done on a tape update basis.
`Following are the technical requirements:
`
`TAPE SPECIFICATIONS
`
`ENCODING:
`RECORD LENGTH:
`BLOCK SIZE:
`TAPE:
`LABELS:
`SORTING:
`
`ASCII
`232 Characters
`16 Records per block (3712 characters)
`1600 BPI/9 Track
`Standard IBM (SL Option on JCL)
`The
`file
`should be sorted m
`(TN) order (i.e., increasing numerical order).
`
`telephone number
`
`NOTE:
`
`ALL ALPHA CHARACTERS/DATA MUST BE PROVIDED IN UPPER CASE
`LETTERS ONLY.
`
`Page 4
`
`Intrado Ex. 1038 - 7
`
`

`

`4.
`
`FILE TRANSFER SYSTEM (FTS) RECORD FORMAT
`
`4.1
`
`Figure 2, shown below, represents the format of the entire File Transfer System (FTS) record/file layout
`to be transmitted to BellSouth for PBX/ALI database updates.
`
`Iss A, TR 73577
`
`232 CHARS.
`
`$$ddddddddffffpppppppp
`FTSHEADER
`(see sections 5.1 - 5.4)
`
`SIGN-ON
`
`232 CHARS.
`
`User Data
`E911HEADER
`(see sections 5.5 - 5.6)
`
`232 CHARS.
`
`User Data
`E911 DATA RECORD
`(see sections 5.7 - 5.10)
`
`USER FILE
`
`232 CHARS.
`
`User Data
`E911 TRAILER
`(see sections 5.11 - 5.12)
`
`FIGURE 2 - FTS RECORD FORMAT
`
`5.
`
`FILE TRANSFER SYSTEM (FTS) RECORDS DESCRIPTION
`
`The FTS Record layout has been designed in a series of four records. The first record is the FTS Head(cid:173)
`er, the second record is the E911 Header, the third record is the E911 Data and the fourth and last is
`the E911 Trailer. These four FTS records must be transmitted in order (i.e., first record, second, etc.)
`to establish a successful session to the E911 data transfer update.
`
`5.1
`
`FTS HEADER RECORD
`
`Page 5
`
`Intrado Ex. 1038 - 8
`
`

`

`TR 73577
`
`5.2
`
`The first record is the File Transfer System (FTS) header record and it must be in the following format:
`
`232 characters long, space-filled, FTS header information as follows:
`
`$$ddddddddft1Tpppppppp "followed by 210 spaces"
`
`where:
`
`'$$'is the FTS Header Entry code of two"$$" symbols,
`
`'dddddddd' is the eight (8) alphanumeric Destination ID code,
`
`'ftlY is the four ( 4) alphanumeric Input File Type code which for PBX/ALI is "INPT",
`
`'pppppppp' is the eight (8) alphanumeric Password code, followed by two hundred ten (210) spaces.
`
`The Destination ID and the Password codes will be provided to the customer by BellSouth personnel
`during the testing period.
`
`This first record, as well as the other three following records, are depicted as the FTS record layout
`shown in section 4 entitled "FTS RECORD FORMAT".
`
`E911 HEADER RECORD
`
`The second FTS record is the E911 Header record and it basically provides the E911 database system
`with the identification of the PBX customer that is updating their ALI information. Following is the
`layout of this record:
`
`5.3
`
`5.4
`
`5.5
`
`5.6
`
`CHARACTER
`
`LENGTH
`
`FIELD NAME
`
`000
`
`001-011
`
`012-014
`
`015-020
`
`021
`
`022
`
`023
`
`053-057
`
`1
`
`11
`
`3
`
`6
`
`1
`
`1
`
`30
`
`5
`
`Space
`
`Zeros
`
`DESCRIPTION
`
`For internal use
`
`For internal use
`
`Cycle Number
`
`To be coordinated with BellSouth
`
`Date
`
`Calendar Date (MMDDYY)
`
`Reserved for other use
`
`Insert a space.
`
`Other use
`
`Customer Name
`
`PBX/ALI ID
`
`Insert a space. This field is for other
`uses.
`Customer Name (up to 30 alphanumer(cid:173)
`ic characters.
`This field contains the PBX/ ALI user
`ID. The first character of this field is
`numeric and represents the State Code.
`These are:
`"1" - NC
`"2" - SC
`"3" - FL
`"4" - GA
`"5" - AL
`"6" - MS
`"7" - TN
`"8" - KY
`"9" - LA
`
`NOTE: The remaining four characters in this field are unique to each customer. These four char(cid:173)
`acters will be provided by BellSouth during the testing phase.
`
`Page 6
`
`Intrado Ex. 1038 - 9
`
`

`

`Iss A, TR 73577
`
`CHARACTER
`
`LENGTH
`
`FIELD NAME
`
`058-175
`
`176
`
`177
`
`178-231
`
`118
`
`1
`
`1
`
`54
`
`E911 DATA RECORD
`
`Spaces
`
`Zero
`
`Zero
`
`Spaces
`
`DESCRIPTION
`
`For future use.
`
`For internal use.
`
`For internal use.
`
`For future use.
`
`The third FTS record is the E911 data record and it provides the PBX/ALI information, namely the
`232-character user data record(s).
`
`Following are the "CUSTOMER RECORD LAYOUT AND FIELD DESCRIPTIONS" fields for this
`customer record layout:
`
`CHARACTER
`
`LENGTH
`
`FIELD NAME
`
`5.7
`
`5.8
`
`5.9
`
`0
`1-10
`11-13
`14-21
`22-25
`26-27
`28-75
`76-107
`108-109
`110-129
`130-161
`162
`163
`164-167
`168-174
`175
`176-177
`178-181
`
`182-191
`192-198
`199-222
`223-228
`229-231
`
`1
`10
`3
`8
`4
`2
`48
`32
`2
`20
`32
`1
`1
`4
`7
`1
`2
`4
`
`10
`7
`24
`6
`3
`
`Function Name
`Telephone Number
`Customer Code
`House Number
`House Number Suffix
`Directional
`Street Name
`Community Name
`State
`Location
`Customer Name
`Class of Service
`Type of Service
`Exchange Name
`Reserved
`ESN Priority
`System ID Code
`Main Account
`Line Number
`Error Indicators
`Order Number
`Reserved
`Extract Date
`AccountNNX
`
`NOTE:
`
`All of the above fields are required unless otherwise noted.
`
`5.10
`
`Following are the definitions of each of the FIELD NAMEs:
`
`COLUMN
`
`FIELD NAME
`
`DESCRIPTION
`
`000
`
`FUNCTION NAME
`
`the record. For initial loads is "I". For updates
`
`A one (1) alphabetic character code which
`specifies the type of activity to be performed by
`is: "T" for insert,
`
`Page 7
`
`Intrado Ex. 1038 - 10
`
`

`

`TR 73577
`
`"C" for change or "D" for
`
`delete.
`
`COLUMN
`
`FIELD NAME
`
`DESCRIPTION
`
`001-010
`
`TELEPHONE
`NUMBER
`
`011-013
`
`CUSTOMER CODE
`
`014-021
`
`HOUSE NUMBER
`
`The ten (10) character numeric telephone
`number consisting of a three (3) digit NPA, a
`three (3) digit NNX and a four ( 4) digit line
`number (i.e., NPA- NNX - XXXX).
`
`A three (3) character numeric code will be
`provided by BellSouth during the training phase.
`
`An eight (8) character field that contains the
`numeric house number and which is right justified
`with leading spaces. If the customer has no house
`number, this field should be spaces.
`
`A four ( 4) character house number suffix field
`022-025
`HOUSE NUMBER
`which is appended to the house number. This
`SUFFIX
`field is left justified beginning with the hyphen.
`apartment number, building
`
`(Examples:
`
`number, or fraction portion of a house number).
`
`If there is no house number suffix -
`should be spaces.
`
`this field
`
`026-027
`
`DIRECTIONAL
`
`and "SW". If there is no directional prefix, this
`spaces.
`
`028-075
`STREET NAME
`left justified field containing the address of the
`ciated with the line number in the
`vice address should be used. If
`the listed address should be
`sidiary lines a secondary or
`
`secondary addresses, the main address should be
`
`A two (2) character left justified directional prefix
`which precedes the street name. Valid entries
`are: "E", "N", "S", "W", "NE", "NW, "SE",
`field should be
`
`A forty-eight ( 48) alphanumeric character field
`equipment asso(cid:173)
`record. The ser(cid:173)
`it is not available
`used. For sub-
`
`subsidiary key system address or a different
`premises address should be used. If there are no
`used.
`
`076-107
`NAME
`
`A thirty-two (32) alphanumeric character field
`COMMUNITY
`left justified containing the community name,
`spelled in full, associated with the street address.
`
`108-109
`STATE
`indicating the state where this line resides. The
`codes are: '~', "F~', "GA",
`"MS", "NC", "SC", and "TN".
`
`A two (2) alphabetic character field state code
`BellSouth's state
`"KY",
`"Lt\'',
`
`Page 8
`
`Intrado Ex. 1038 - 11
`
`

`

`Iss A, TR 73577
`
`COLUMN
`
`FIELD NAME
`
`DESCRIPTION
`
`110-129
`LOCATION
`justified field which contains additional
`
`A twenty (20) alphanumeric character field left
`
`information describing the precise location of the
`equipment associated with the telephone number.
`(Example, building number, suite number or
`apartment number).
`
`130-161
`
`account.
`
`162
`SERVICE
`PBX/ALI are:
`
`CUSTOMER
`NAME
`
`A thirty-two character left justified field
`containing the listed name (LN) of the customer
`
`A one (1) numeric character code identifying the
`CLASS OF
`account basic class of service. Valid codes for
`
`1 = Residence
`2 =BUSINESS
`4 = BUSINESS PBX
`
`163
`
`TYPE OF
`SERVICE
`name of this customer. The valid code is:
`
`A one (1) numeric character code which
`describes the type of service and type of account
`
`6 =PBX/ALI
`
`Up to four characters which identify the name
`EXCHANGE
`164-167
`of the exchange. This code will be provided by
`NAME
`BellSouth personnel during the training phase.
`
`168-174
`
`RESERVED
`
`For future use. Fill with spaces.
`
`175
`
`ESN PRIORITY
`
`Enter the digit "7" in this field.
`
`176-177
`
`SYSTEM ID
`CODE
`PBX customer/administrator by BellSouth during
`
`A two (2) character field which identifies the
`E911 system. This code will be provided to the
`training.
`
`178-181
`
`MAIN ACCOUNT
`LINE NUMBER
`
`The four ( 4) digit line number of the main
`account.
`
`182-191
`ERROR INDICATORS
`the E911 Source Data Management system to
`identify specific update error conditions. This
`field should be left blank by the PBX customer.
`
`A ten (10) alphanumeric character field used by
`
`192-198
`
`PBX/ALI
`
`Enter "PBX -ALI" in this field.
`
`199-222
`
`RESERVED
`
`Reserved for future use. To be filled with spaces.
`
`223-228
`EXTRACT
`which the file was created (MMDDYY).
`
`229-231
`
`ACCOUNTNXX
`
`The six (6) character numeric date of the day on
`
`The first three (3) numbers of the account
`telephone number.
`
`Page 9
`
`Intrado Ex. 1038 - 12
`
`

`

`TR 73577
`
`5.11
`
`E911 TRAILER RECORD
`
`5.12
`
`The fourth and final FTS record is the Trailer record. This record provides the number of records trans(cid:173)
`mitted in each file. Following is the format:
`
`COLUMN
`
`FIELD NAME
`
`LENGTH
`
`DESCRIPTION
`
`000-001
`
`System ID
`
`2
`
`002-006
`
`5
`Record Total
`header and trailer records.
`
`007-174
`
`168
`Spaces
`the Local BellSouth Representative. If
`not, this field should be space filled.
`
`Identification code unique to the PBX/
`ALI customer.
`
`Record total for system. Do not include
`
`If multiple system ID's are used, contact
`
`175
`
`176
`
`177
`
`Space
`
`Equal
`
`Equal
`
`6.
`
`REFERENCES
`
`1
`
`1
`
`1
`
`Insert a space.
`
`Insert an equal sign. That is"=".
`
`Insert an equal sign. That is,"=".
`
`6.1
`
`References which support BellSouth E911 File Transfer System (FTS) Database services are shown be(cid:173)
`low, as well as referenced within the text of this document.
`
`BellSouth published document:
`
`(1)
`
`BellSouth Technical Reference (TR) 73576 - "BellSouth Enhanced 911 for PBX/ALI
`Service Network Interface Specifications" Issue A, June 1993.
`
`Page 10
`
`Intrado Ex. 1038 - 13
`
`

`

`BellSouth Practices
`BellSouth Telecommunications Standard
`
`Section TR73577BT
`Issue
`
`Customer Network Interface
`
`ALI
`Database
`
`Customer
`PBX
`
`Daily Moves
`
`and Changes
`
`PC with
`Modem
`
`BellSouth
`Modem
`Interface
`
`BellSouth
`
`E911
`
`Computer
`
`FIGUREl
`
`NOTICE
`Not for use or disclosure outside BellSouth or
`any of its subsidiaries except under written agreement
`
`Printed in LI. S. A.
`
`Page 1
`
`Intrado Ex. 1038 - 14
`
`

`

`Section TR73577BT
`
`232 CHARS.
`
`232 CHARS.
`
`232 CHARS.
`
`232 CHARS.
`
`$$ddddddddffffpppppppp
`FTSHEADER
`(see section 5.1)
`
`SIGN-ON
`
`User Data
`E911HEADER
`(see section 5.2)
`
`User Data
`E911 DATA RECORD
`(see section 5.3)
`
`User Data
`E911 TRAILER
`(see section 5.4)
`
`USER FILE
`
`Page2
`
`FIGURE2
`
`NOTICE
`Not for use or disclosure outside BellSouth or
`any of its subsidiaries except under written agreement
`
`Printed in LI. S. A.
`
`Intrado Ex. 1038 - 15
`
`

`

`~
`'<
`!l. z
`;::::;.: g_
`
`Customer Network Interface
`
`Customer
`
`PBX
`
`Daily Moves
`
`and Changes
`
`PC with
`Modem
`
`BellSouth
`Modem
`Interface
`
`BellSouth
`
`E911
`
`Computer
`
`ALI
`Database
`
`:;;'
`
`"' ,?'
`"' " &.
`0 =
`;:;l
`"' I
`""" 0
`0
`I
`0
`:':;
`~
`
`-
`00
`00 0
`c ~
`~c
`00 00
`Q; ~
`~ ~
`" ~.
`~- Q,
`00 00
`3
`CD Q_ Z
`m
`~ ~ 0
`"-
`s· ~s;-1
`~ ;; ~ n
`6- ~ m
`m -·
`~ "-
`~ m a gi m -
`(Cl " ' " " mo
`
`~ rn
`~ 0
`
`3 ~
`m
`3
`
`rn
`)>
`
`~
`""
`
`Intrado Ex. 1038 - 16
`
`

`

`(JO
`
`;;,;;
`...
`"
`
`~
`~
`'<
`!l. z
`;::::;.: g_
`
`~.
`
`"
`2.
`m
`"-
`s·
`c
`rn
`)>
`
`;; 0 ()
`
`-
`00
`00 0
`c ~
`~c
`00 00
`Q; ~
`~ ~
`~- Q,
`00 00
`CD Q_ Z
`~ ~ 0
`m c -I
`-am -
`6- ~ m
`m -·
`~ "-
`~ m a gi
`(Cl " ' " "
`
`m ~
`~ rn
`~ 0
`
`mo
`3 ~
`m
`2.
`
`Q;
`
`"' "
`"
`0 = ...,
`~
`"" "'
`.....
`..... = ...,
`
`232 CHARS. I
`
`$$ddddddddffffpppppppp
`FTSHEADER
`(see section 5.1)
`
`SIGN-ON
`
`232 CHARS.
`
`232 CHARS.
`
`User Data
`E911HEADER
`(see section 5.2)
`
`User Data
`E911 DATA RECORD
`(see section 5.3)
`
`232 CHARS. I
`
`User Data
`E911 TRAILER
`(see section 5.4)
`
`I
`
`) USERFILE
`
`Intrado Ex. 1038 - 17
`
`