For Telephone Service Providers
Access Request Form for Intrado Unified Portal
For PS/ALI customers
Accessing Intrado’s 9-1-1 NET Portal
SYSTEM REQUIREMENTS
The following list identifies general requirements for IUP/911NET access:
-
Users access the server over a secured network.
-
The software is designed for use with Internet Explorer version 7.0 or higher. Compatibility with other browsers is not guaranteed.
SECURITY
Overall Security Requirements
-
All users will receive an entrust token from the Intrado/Verizon support team
-
Users are instructed to contact Intrado at 855-820-8108 to activate the token
-
Logins and passwords to the Intrado Portal will be provided to you by Intrado at the same time you contact them to activate your token.
-
System functionality and information retrieval is determined by the user’s profile.
.
Accessing the Intrado Unified Portal/911NET
When a carrier is ready to access the system for the first time, they should contact the
E 9-1-1 System Administration Team. Verizon will provide detailed instructions required to access the system. Intrado will provide the appropriate URL and an initial user name and password. User documentation can be obtained in the Document Library on the Intrado Unified Portal (IUP)
Options for transmitting files
-
The file transfer tool (FTT) accessed through the Intrado Unified Portal (IUP). The FFF is similar to the tool found in 9-1-1 IM.
-
A sFTP connection. This connection is accessed outside of the IUP using a SSH/sFTP client and an internet connection.
-
A HTTP connection. This connection is accessed outside of the IUP and uses a Secure ID Token and an internet connection.
-
Dial Up. If you currently use a dial up connection. You can continue to use dial up. However, Intrado and Verizon recommend that your company considers upgrading to one of the 3 methods listed above
File Names
The file names for your input/SOI files will be provided to you by Intrado/Verizon Support team.
Naming conventions for all methods of file transfer (HTTP, sFTP and FTT) with header and trailer are:
• Must start with the 4 character file name
• Can not be more than 20 characters
• Must have a file extension
• 4 files are returned: _pp, _sp, _err_, _sta
Naming conventions for all methods of file transfer (HTTP, sFTP and FTT) with NO header or trailer are:
• Must start with the 4 character file name
• Can not be more than 8 characters
• Can not have a file extension
• Only _err and _sta files will be returned
Modified NENA 2.1 Format for Data Exchange
This Section displays the unique differences that exist in several of the East states within Verizon that must be recognized when inputting data into the E 9-1-1 database. NENA Version 2.1 Format for Data Exchange is displayed in Section 6 of this document.
FIELD NAME
|
POS
|
BYTES
|
IMPORTANT INFO TO REVIEW
|
HOUSE NUMBER SUFFIX
|
22-25
|
4
|
NOTE: IN THE MID-ATLANTIC STATES
(PA, DE, VA, DC, MD) THE 1ST CHARACTER OF THIS FIELD MUST CONTAIN A HYPHEN (FOR EX: -1/2 OR –A
|
STREET SUFFIX
|
88-91
|
4
|
NEED TO DISCUSS
NEED TO COMPLY WITH STATE REQUIREMENTS
|
FIELD NAME POS BYTES IMPORTANT NOTES TO DISCUSS
LOCATION 128-187 60
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTE 1: THE LOCATION FIELD IN THE MASSACHUSETTS & NEW YORK DATABASE IS LISTED AS THE TN Comment FIELD. IT IS 30 BYTES IN LENGTH AND IS FOUND IN POSITIONS 128-157. THIS IS WHERE LOCATION INFORMATION SUCH AS APARTMENT, FLOOR AND BUILDING SHOULD BE ENTERED.
NOTE 2: THE LOCATION FIELD IN PA, VA, MD and DC IS LISTED AS THE ADDRESS EXTENSION FIELD.
|
Disability Information Massachusetts Database
In Massachusetts disability information is populated in the ‘location’ field using the following specific ‘disability indicators’.
DISABILITY INDICATORS
|
USED FOR:
|
LSS
|
LIFE SUPPORT SYSTEM
|
MI
|
MOBILITY IMPAIRED
|
B
|
BLIND
|
DHH
|
DEAF & HARD OF HEARING
|
TTY
|
TELETYPWRITER
|
SI
|
SPEECH IMPAIRED
|
DD
|
DEVELOPMENTALLY DISABLED
|
CI
|
COGNITIVELY IMPAIRED
|
NOTE: In New York, there are no specific procedures or indicators used to reference disability information in the database. Handicapped information may be entered within the “location” field as a ‘free floating’ remark and is entered at the discretion of the telephone company provider.
NENA 2.1 Data Record Specifications
The following section contains the Data Record, Header Record, and Trailer Record specifications based on the National Emergency Number Association (NENA) recommended format for data exchange - Version 2. This version can also be found on the Internet at http://www.nena.org/9-1-1TechStandards/nena_recommended_standards.htm.
Field Name
|
Positions
|
Bytes
|
Type
|
Req’d
|
Description
|
Function Code
|
1
|
1
|
A
|
R
|
The type of activity the record is being submitted for. Valid entries are:
C = Change, D= Delete, I = Insert
U= Unlock, M=Migrate
|
NPA
|
2 - 4
|
3
|
N
|
R
|
The three-digit area code of the Calling/Working Number.
|
Calling Number
|
5 - 11
|
7
|
N
|
R
|
The seven-digit telephone number of the Calling/Working Number.
|
House Number
|
12 - 21
|
10
|
AN
|
R/SF
|
The house number. This field should be spaced filled if no house number is available.
|
House Suffix Number
|
22 - 25
|
4
|
AN
|
R/SF
|
***NEED TO DISCUSS WITH VERIZON***
The house number extension. (e.g. 1/2) This field should be space filled if no suffix applies.
|
Prefix Directional
|
26 - 27
|
2
|
A
|
R/SF
|
The leading street direction prefix. Valid entries are: N, S, E, W, NE, NW, SE, and SW. This field should be space filled if no prefix applies.
|
Street Name
|
28 - 87
|
60
|
AN
|
R
|
***NEED TO DISCUSS WITH VERIZON***
The service address of the Calling Number.
|
Street Suffix
|
88 - 91
|
4
|
A
|
R/SF
|
***NEED TO DISCUSS***
The street abbreviation, as defined by the U. S. Postal Service Publication 28. (e.g. AVE) This field should be space filled if no suffix applies.
|
Post Directional
|
92 - 93
|
2
|
A
|
R/SF
|
The trailing street direction suffix. Valid entries are: N, S, E, W, NE, NW, SE, and SW. This field should be space filled if no suffix applies.
|
Community Name
|
94 - 125
|
32
|
A
|
R
|
The service community name of the street / house number as assigned by
The Municipal Street Address Guide.
|
State
|
126 - 127
|
2
|
A
|
R
|
The alphabetic state abbreviation as defined by the U. S. Postal Service. (e.g. PA)
|
Location
|
128 - 187
|
60
|
AN
|
R/SF
|
**NEED TO DISCUSS in MA and NY**
The additional address information describing the exact location of the Calling Number. (e.g. SUITE 2002, APT 706A) This field should be space filled if no location applies. See Notes for additional information on the use this field.
|
Customer Name
|
188 - 219
|
32
|
AN
|
R
|
The subscriber name associated with the Calling Number.
|
Class of Service
|
220
|
1
|
AN
|
R
|
Valid entries are:
1 = Residence
2 = Business
3 = Residence Private Branch Exchange (PBX)
4 = Business PBX
5 = CENTREX
6 = Coin 1 way out
7 = Coin 2 way
8 = Mobile
9 = Residence Off Premise Extension (OPX)
0 = Business OPX
A= Customer Owned Coin Telephone
G= Wireless Phase 1
H= Wireless Phase 2
V= VOIP
|
Type of Service
|
221
|
1
|
N
|
R
|
Valid entries are:
0 = Not Foreign Exchange (FX) or Non Published (Non Pub)
1 = FX in 9-1-1 serving area
2 = FX outside 9-1-1 serving area
3 = Non Pub
4 = Non Pub FX in 9-1-1 serving area
5 = Non Pub FX outside 9-1-1 serving area
Note: The only valid entries for FX service is
1 and 4.
|
Exchange
|
222 - 225
|
4
|
AN
|
R/SF
|
***NEED TO DISCUSS***
Required in NY, MD, DC VA,NJ and PA. The county code taken from the MSAG for MD, DC, VA and PA. For NY populate the exchange field taken from the MSAG.
|
ESN
|
226 - 230
|
5
|
AN
|
N/SF
|
Field not used, space fill.
|
Main NPA
|
231 - 233
|
3
|
N
|
R +/or SF
|
The three-digit area code of the Main Number associated with the Calling Number.
***NEED TO DISCUSS WITH VERIZON***
|
Main Number
|
234 - 240
|
7
|
N
|
R +/or
SF
|
The seven digit telephone number of the Main Number associated with the Calling Number
***NEED TO DISCUSS***
|
Order Number
|
241 - 250
|
10
|
AN
|
R/SF
|
The service order number for the activity establishing this record.
|
Extract Date
|
251 - 256
|
6
|
N
|
R +/or
SF
|
The date on which the record was created in month, day, year, format (e.g. MMDDYY).
|
County ID
|
257 - 260
|
4
|
AN
|
N/SF
|
***NEED TO DISCUSS***
Required in MD, DC, VA and PA
|
Company ID
|
261 - 265
|
5
|
AN
|
N/SF
|
The Telephone Company Identification code. This field is to be populated using the NENA Company Code.
|
Source ID
|
266
|
1
|
AN
|
R +/or
SF
|
A code that indicates whether the data is part of an initial data load or re-load or part of a daily update process. Valid values are:
Space = Daily Update, C = Load
|
Zip Code
|
267 - 271
|
5
|
AN
|
N/SF
|
The five digit Postal Zip Code.
Field not used
|
Zip + 4
|
272 - 275
|
4
|
AN
|
N/SF
|
Field not used, space fill.
|
General Use
|
276 - 286
|
11
|
AN
|
N/SF
|
Field not used, space fill.
|
Customer Code
|
287 - 289
|
3
|
AN
|
N/SF
|
Field not used, space fill.
Need to discuss in the West
|
Comments
|
290 - 319
|
30
|
AN
|
N/SF
|
Required in NY and MA. Location information such as APT and FLR.
|
X Coordinate
|
320 - 328
|
9
|
N
|
N/SF
|
Field not used, space fill.
|
Y Coordinate
|
329 - 337
|
9
|
N
|
N/SF
|
Field not used, space fill.
|
Z Coordinate
|
338 - 342
|
5
|
N
|
N/SF
|
Field not used, space fill.
|
Cell ID
|
343 - 348
|
6
|
AN
|
N/SF
|
Field not used, space fill.
|
Sector ID
|
349
|
1
|
AN
|
N/SF
|
Field not used, space fill.
|
TAR code
|
350 - 355
|
6
|
AN
|
R
|
***NEED TO DISCUSS***
Field not used, space fill..
|
Reserved
|
356-376
|
21
|
AN
|
N/SF
|
This field is reserved for the Database Management Systems provider’s use.
|
Alternate Number
|
377-386
|
10
|
N
|
R/SF
|
Customer Number being remote call forwarded in Interim Number Portability service.
|
Expanded Extract Date
|
387-394
|
8
|
N
|
R/SF
|
Date on which the record was created in the format YYYYMMDD
|
NENA reserved
|
395-480
|
86
|
AN
|
N
|
This field is reserved for NENA Data Technical Committee Assignment.
|
Reserved
|
481-511
|
31
|
AN
|
N/SF
|
This field is reserved for the Data Base Management Systems Provider’s use.
|
End of Record
|
512
|
1
|
AN
|
R
|
End of record indicator. Always contains an asterisk (*).
|
Notes:
1. Req’d (required) column
R = Required field. Must be populated for every subscriber’s record spaces not
permitted.
R/SF = Required field. Must be populated if present in subscriber’s record otherwise space
fill.
N/SF = Not required field. Space fill.
2. All fields are left justified with trailing spaces.
3. The actual lengths of some fields on the 9-1-1 systems (e.g. Street, Community, Location, et al) are shorter than the NENA-2 defined length and vary by system, which may result in truncation of rightmost data. The most significant information should always be left justified in these and all fields.
4. All alphanumeric (AN) fields may contain upper case letters, numbers and punctuation characters. Lower case and control characters are not permitted.
ASCII characters used in alpha only and alpha/numeric fields should be limited to
A thru Z, a thru z, 0 thru 9, comma ‘, ’,forward slash ‘ / ’, semi colon ‘; ‘, ampersand ‘&’,
and apostrophe ‘ ’ ’.
Spaces are allowed with one exception----the first character of a field may not be a space.
Other characters may impact the accurate processing of data.
Do NOT use the accent mark (for ex. Café) as it will fail data file processing.
NENA Header and Trailer format for data exchange
NENA Recommended Header Format for Data Exchange
Field Name
|
Position
|
Bytes
|
Type
|
Header Indicator
|
1-5
|
5
|
UHL
|
Extract Date
|
6-11
|
6
|
MMDDYY
for ex 030300
|
Company Name
|
12-61
|
50
|
CWT
|
Cycle Counter
|
62-67
|
6
|
Numeric field
|
County Id
|
68-71
|
4
|
Alpha Numeric field
|
State
|
72-73
|
2
|
NY
|
General Use
|
74-93
|
20
|
Alpha Numeric field
|
Release Number
|
94-96
|
3
|
Numeric field
|
Format Version
|
97
|
1
|
Numeric field
|
Expanded Extract Date
|
98-105
|
8
|
Numeric field
|
Reserved
|
106-511
|
406
|
Alpha Numeric field
|
End of Record
|
512
|
1
|
*
|
Note: All fields are Left-justified with trailing spaces, EXCEPT for the Cycle Counter;
This is Right-justified with leading spaces.
NENA Recommended Trailer Format for Data Exchange
Field Name
|
Position
|
Bytes
|
Type
|
Trailer Indicator
|
1-5
|
5
|
UTL
|
Extract Date
|
6-11
|
6
|
MMDDYY
for ex 030300
|
Company Name
|
12-61
|
50
|
CWT
|
Record Count
|
62-70
|
9
|
Numeric Field
|
Expanded Extract Date
|
71-78
|
8
|
Numeric Field
|
Reserved
|
79-511
|
433
|
Alpha Numeric field
|
End of Record
|
512
|
1
|
*
|
Note: All fields are Left-justified with trailing spaces, EXCEPT for the Record count;
This is Right-justified with leading spaces.
|
Yüklə 2.42 Mb.