Summary
This article provides guidelines for using Bulk Data Import to create covered hotline records in the Orig-Term Number table in Admin Console. This extends the functionality delivered in the IDI platform 24.10 release to support privacy of calls and texts to covered hotline numbers (FCC mandate 23-96). The 24.10 release provided the ability to bypass/omit calls and text messages to and from covered hotlines during core usage processing, and required manually entering covered hotline numbers into the Orig-Term Number table in Admin Console. The Covered Hotline bulk import provides an alternative method for populating the Orig-Term Number table by importing the FCC covered hotline numbers file.
The Bulk Data application supports both an initial load of the file and subsequent loads. Loading a file after the initial load will do a full replacement of the covered hotlines loaded through a file import. Covered hotlines configured manually will be preserved (not overwritten).
Notes:
- This specification does not include a header row with a list of fields as is required by other bulk data import specifications.
- Submit a covered hotline file automation request if you need to automate the file feed. The file automation request must be set up with a format parameter to indicate the import is for covered hotlines: format:IDI/CostGuardBulkData/CoveredHotline
This parameter is not required to run the import via the Bulk Import web module.
File Format
General Format
The following general rules apply to device import files:
- File naming convention must be *.csv.
- All fields are required.
Record Layout
| Field | Data Type | Description |
| ID | Integer | Seven-digit unique identifier with leading zeros as necessary. |
| Number | Integer | Ten digit covered hotline number (xxxyyyzzzz). |
| Date | Integer | Date the number was entered into the FCC file – eight digits: yyyymmdd |