|
Call Processing Record (CPR) Field Descriptions | ||
| Field Name | Descriptions | Valid Values |
| IntraLATA Carrier | Carrier providing routing for IntraLATA traffic. | Available for choosing from a drop down menu. |
| InterLATA Carrier | Carrier providing routing for InterLATA traffic. | Available for choosing from a drop down menu. |
| Time Zone | Time Zone indicator. |
Valid values are:
Default value is CT. |
| Daylight Savings | Indication if the Time Zone is part of daylight savings time. | Check box |
| Section Name | Drop down. Identifies the section as Main or a subsection. | Must start with 'M'(MAIN) or 'S' (SUB) followed by 7 characters, ‘%’ or ‘#’ characters. |
| Search | Drop down list of possible column values to identify what column to search when the Search box is used. | Drop down |
| Search box | Text to use for searching. | Text Field |
| State |
Optional. State(s) or Province(s) from which calls originate (must be within the Template Record (TAD) (also known as a TR)’s AOS). Example: NJ |
Valid values include:
|
| Area Code | Text field. Optional. Area code(s) from which calls originate (must be within the TR’s AOS). |
Valid values include:
|
| LATA | Text field. Optional. LATA(s) from which calls originate (must be within the TR’s AOS). |
Valid values include:
|
| NXX | Text field. Optional. NXX(s) from which calls originate (must be within the TR’s AOS). |
Valid values include:
|
| 6 Digit | Text field. Optional. NPA-NXX(s) from which calls originate (must be within the TR’s AOS). |
Valid values include:
|
| 10 Digit | Text field. Specific 10 Digit telephone number(s) from which calls originate (must be within the TR’s AOS). |
Valid values include:
|
| Date | Text field. Date(s) on which calls are made. A maximum of 2 dates may be entered. |
Valid format/values include:
|
| Day | Text field. Day(s)-of-week on which calls are made. Abbreviations are allowed. |
Valid values include:
You can enter up to 5 days. |
| Time | Text field. Time of day when calls are made. A time range within the same day must be entered. |
Valid format/values include:
|
| Switch | Text field. Indicates whether or not a call routing path is activated. |
Valid values include:
|
| Percent | Text field. Indicates a percent allocation for routing calls. Entry must be a whole number. |
Valid values include:
The value “OTHER” is not allowed. May contain an optional one-character suffix. |
| Carrier | Text field. Inter-exchange carrier or Operating Telephone Company (OTC) name. In the TFNRegistry™, OTC is the ACNA name of the Carrier. |
The following are valid entries:
|
| Tel # |
Text field. The destination telephone number (a TFNs or a POTS number). A CPR subsection must contain Tel# or Announcement criteria as the last column. LAD Label is not allowed in the TEL# node for a TR, because a TR TEL# node only supports a value of “#DIAL“ unless it’s empty due to the call terminating to an Announcement node. The Tel# node cannot be the 1st node in a CPR main section, although can be the first node in a subsection that a Go To node points to. |
Valid values include:
In a Template’s CPR, Tel# field must be set to a value of “#DIAL” or leave it empty if allowed by the TFNRegistry when the Tel# node isn’t the last node. For a TR, the Resp Org enters the value “#DIAL” in the TEL# column and not the actual terminating TFN because a Template can be used by multiple PRs and the Resp Org identifies the terminating TFN on the PRs. |
| Announce | Text field. The type of recorded announcement that the caller will hear. A CPR subsection must contain Tel# or Announcement criteria as the last column. |
Valid values include:
|
| Go To | Used to reference a subsection of the CPR. |
Valid subsection must begin with “S”, followed by up to 7 alphanumeric characters (including % or #). The Go To subsection name can be up to 8 characters maximum. Example: SUB1 or SUBNOD |