TFNRegistry UI: What are the Fields, their Descriptions and Valid Values for the ICR Page?

Toll-Free Number

Data entry field for retrieving the Toll-Free Number (TFN) for the Responsible Organization (Resp Org).

10 alpha numeric characters. Format is NPA-NXX-XXXX.

Effective Date

Required. The Effective Date identifies the date the record needs to be sent to the Service Control Points (SCPs) and activated. This field can be entered manually or by using the Calendar pop-up.

MM/DD/YYYY Format. When “Now” is checked, this field will be disabled.

Please Note: To use the “High Priority” check box, Effective Date must be today’s date or “Now” check box is selected.

Effective Time

Optional. The Effective Time identifies the time and the record should be sent to the SCPs and activated. This field can be entered manually.

HH:MM AM/PM. When “Now” is checked, this field will be disabled.

Now

Optional. Current date and time will be used during creation of the Customer Record (CAD) (also known as a CR) when Now is selected.

Check box.

Resp Org

Required. Populated by the TFNRegistry based on the Resp Org for the current Login ID according to the SUD page for the Resp Org.

Resp Org is 5 alphanumeric characters.

Pre-filled field and editable.

Customer ID

Optional. Indicates a subscriber who has online access to the TFNRegistry. This field is referred to as a Customer ID or Subscriber ID.

5 alphanumeric character unique code for each subscriber. The first 4 characters of the Customer ID must match the Telco field.

Agent ID

Optional. Identifies an ID identifying an authorized agent for the TFNs with update capability for the associated record (CAD, Call Processing Record (CPR) and Label Definitions (LAD)) or for the CPR/LAD depending on the type of user in the party’s security record. Can also identify a user with view only permissions for the entire CR.

The TFNRegistry removes the value in the Agent ID field during a Resp Org change to a different Resp Org Entity. During any Resp Org Change, it is the responsibility of the new Resp Org to update the value in the Agent ID field.

5 alphanumeric. A unique code for each agent.

Telco

Optional. The Telco on a CR is automatically populated with the first 4 characters of the user’s Resp Org ID when creating a new CR. The value in the Telco field is compared by TFNRegistry to security data to determine if a Subscriber user (reference the Customer ID field) is allowed access to the CR.

4 alphanumeric or may be empty.

End Subscriber Name

Optional. The End Subscriber Name for directory assistance, specified by the customer.

Text string. Up to 75 alphanumeric characters. A “text string” entry can contain any of the following characters: Letters, digits, standard keyboard special characters listed below: ‘ ’ ! @ # $ % & * ( ) - + = { [ } ] \ : ; < , > . ? / .

The following characters are not permitted: ~ Tilde, “Double Quotation Mark, | Vertical Bar (Pipe), ^ Circumflex (Hat) and other special characters not listed above.

End Subscriber Address

Optional. The address for the directory assistance listing.

Text string. Up to 75 alphanumeric characters. A “text string” entry can contain any of the following characters: Letters, digits, standard keyboard special characters listed below: ‘ ’ ! @ # $ % & * ( ) - + = { [ } ] \ : ; < , > . ? / .

The following characters are not permitted: ~ Tilde, “Double Quotation Mark, | Vertical Bar (Pipe), ^ Circumflex (Hat) and other special characters not listed above.

Service Order

Required if the Supplemental Form field is not provided.

The Service Order type and number. Either of Service Order or Supplemental form field must be provided.

4 to 13 alphanumeric characters. The first character must be alphabetic. The 2nd to 12th characters can be alphanumeric. If there is a 13th character it must be alphabetic.

Supplemental Form

Required if the Service Order field is not provided. Number associated with the Supplemental Form.

Up to 6 alphanumeric.

Primary Fully Qualified Domain Name

Required field and Fully Qualified Domain Name to route.

test.somos.com, Test.cor.in

Fully Qualified Domain Name

Optional field

test.somos.com, Test.cor.in

Contact Name/Contact Name (IP Routing)

Optional field.

Two fields will be displayed.

The name of the contact person auto-populated from the CR page.

The name of the contact person who initiated the IP Routing Service. The name can be modified, if necessary.

Text string. Up to 30 alphanumeric characters. A “text string” entry can contain any of the following characters: Letters, digits, standard keyboard special characters listed below: ‘ ’ ! @ # $ % & * ( ) - + = { [ } ] \ : ; < , > . ? / .

The following characters are not permitted: ~ Tilde, “Double Quotation Mark, | Vertical Bar (Pipe), ^ Circumflex (Hat) and other special characters not listed above.

Contact Number/Contact Number (IP Routing)

Optional field.

Two fields will be displayed.

The phone number of the contact person auto-populated from the CR page.

The phone number of the contact person who initiated the IP Routing Service. The name can be modified, if necessary.

NPA-NXX-XXXX (NPA optional). Requires 10 digits -- when the number is populated by the TFNRegistry and the record does not contain a 10 Digit value, the TFNRegistry will display leading zeros (e.g., 000-699-2000).

Notes

Optional field.

Any notes on the SO or SF which need to be stored and for which no specific fields exist for the CAD. The notes from the NUS page are carried over by default and may be modified, if necessary. Notes field is in the contact information for a user to view and edit.

Text string. Up to 151 alphanumeric characters. A “text string” entry can contain any of the following characters: Letters, digits, standard keyboard special characters listed below: ‘ ’ ! @ # $ % & * ( ) - + = { [ } ] \ : ; < , > . ? / .

The following characters are not permitted: ~ Tilde, “Double Quotation Mark, | Vertical Bar (Pipe), ^ Circumflex (Hat) and other special characters not listed above.