Section 64.615 - TRS User Registration Database and administrator(a)TRS User Registration Database.(1)VRS users call validation. VRS providers shall validate the eligibility of the party on the video side of each call by querying the TRS User Registration Database or the TRS Numbering Directory, as directed by the Commission, the TRS Fund administrator, or the TRS Numbering Administrator, on a per-call basis. Emergency 911 calls are excepted from the requirement in this paragraph (a)(1). (i) Validation shall occur during the call setup process, prior to the placement of the call.(ii) If the eligibility of at least one party to the call is not validated using the TRS User Registration Database, the call shall not be completed, and the VRS provider shall either terminate the call or, if appropriate, offer to register the user if they are able to demonstrate eligibility.(iii) Calls that VRS providers are prohibited from completing because the user's eligibility cannot be validated shall not be included in speed of answer calculations and shall not be eligible for compensation from the TRS Fund.(2)Enterprise and public videophone call validation.(i) VRS providers shall validate the registration of an enterprise or public videophone used for a VRS call by querying the designated database in accordance with paragraph (a)(1) of this section.(iii) VRS providers shall require their CAs to terminate any call which does not include a registered enterprise or public videophone or, pursuant to the provider's policies, the call does not appear to be a legitimate VRS call, and VRS providers may not seek compensation for such calls from the TRS Fund.(iv) Emergency 911 calls from enterprise and public videophones shall be exempt from the videophone validation requirements of paragraph (a)(2)(i) of this section.(3) The administrator of the TRS User Registration Database shall assign a unique identifier to each user in the TRS User Registration Database.(4)Data integrity.(i) Each VRS and IP CTS provider shall request that the administrator of the TRS User Registration Database remove from the TRS User Registration Database user information for any registered user or hearing point-to-point user: (A) Who informs its default VRS provider or its IP CTS provider that it no longer wants use of a ten-digit number for TRS or (in the case of a hearing point-to-point video user) for point-to-point video service; or(B) For whom the provider obtains information that the user is not eligible to use the service.(ii) The administrator of the TRS User Registration Database shall remove the data of: (A) Any VRS user that has neither placed nor received a VRS or point-to-point call in a one-year period; and(B) Any user for which a VRS or IP CTS provider makes a request under paragraph (a)(3)(i) of this section.(5) A VRS or IP CTS provider may query the TRS User Registration Database only for the purposes provided in this subpart, and to determine whether information with respect to its registered users already in the database is correct and complete.(6)User verification.(i) The TRS User Registration Database shall have the capability of performing an identification verification check when a VRS provider, IP CTS provider, or other party submits a query to the database about an existing or potential user or an enterprise or public videophone.(ii) VRS and IP CTS providers shall not register individuals or enterprise or public videophones that do not pass the identification verification check conducted through the TRS User Registration Database.(iii) VRS providers shall not seek compensation for calls placed by individuals or for calls placed to or from enterprise or public videophones that do not pass the identification verification check conducted through the TRS User Registration Database.(iv) IP CTS providers shall not seek compensation for calls placed to or from individuals that do not pass the identification verification check conducted through the TRS User Registration Database.(v) Notwithstanding paragraphs (a)(6)(ii) through (iv) of this section, VRS and IP CTS providers may provide service to a new or porting user for up to two weeks after the user's registration information has been submitted to the TRS User Registration Database, pending verification of the user's identity. After such user's identity is verified by the Database administrator, a TRS provider may seek TRS Fund compensation for calls handled during such pre-verification period.(vi) If a VRS provider submits registration information for a TRS telephone number that is being ported from another VRS provider, and user's identity cannot be immediately verified, then the porting-in provider's routing information for that telephone number shall be provisionally entered in the TRS Numbering Directory for up to two weeks to allow the routing of calls to the porting-in VRS provider pursuant to paragraph (a)(6)(v) of this section. If the user's identity is not verified by the TRS User Registration Database administrator within the allowed two-week period, the porting-out provider's routing information shall be re-entered in the TRS Number Directory.(b)Administration - (1)Terms of administration. The administrator of the TRS User Registration Database shall administer the TRS User Registration Database pursuant to the terms of its contract.(2)Compensation. The TRS Fund, as defined by § 64.604(a)(5)(iii) of this subpart, may be used to compensate the administrator of the TRS User Registration Database for the reasonable costs of administration pursuant to the terms of its contract. 78 FR 40609 , July 5, 2013, as amended at 82 FR 17764 , Apr. 13, 2017; 84 FR 8463 , Mar. 8, 2019; 84 FR 26372 , June 6, 2019; 85 FR 26858 , May 6, 2020; 87 FR 57648 , Sept. 21, 2022 82 FR 17764 , 5/15/2017; 82 FR 48203 , 10/17/2017; 84 FR 8463 , 4/8/2019; 84 FR 26372 , 6/6/2019; 85 FR 26858 , 5/6/2020; 85 FR 26858 , 5/6/2020; 87 FR 57648 , 9/21/2022; 88 FR 14251 , 3/8/2023 At 84 FR 26372, June 6, 2019, § 64.615 was amended by revising paragraph (a)(1) introductory text, redesignating paragraphs (a)(2) through (5) as paragraphs (a)(3) through (6), adding new paragraph (a)(2), and revising newly redesignated paragraph (a)(6). These paragraphs contain information collection and recordkeeping requirements and will not become effective until approval has been given by the Office of Management and Budget.