Where AT&T. 13STATE manages the 911 and E911 Databases, and Carrier deploys an NCAS solution:
3.4.2.1 Carriers designated third-party provider shall perform the above database functions.
Where AT&T. 13STATE is the 911 System Service Provider, Carrier will route 911 calls from Xxxxxxx’s MSC to the AT&T-13STATE SR office of the 911 system.
Where AT&T. 22STATE has any ownership or ROW to buildings or building complexes, or within buildings or building complexes, AT&T-22STATE shall offer to CLEC through a License or other attachment:
3.4.5.1 The right to use any available space owned or controlled by AT&T-22STATE in the building or building complex to install CLEC equipment and Facilities; and
3.4.5.2 Ingress and egress to such space.
Where AT&T. 22STATE notifies CLEC that AT&T-22STATE’s Agreement with a Third Party does not expressly or impliedly grant AT&T-22STATE the ability to provide such access and use rights to others, upon CLEC’s request, AT&T-22STATE will use its best efforts to obtain the owner’s consent and to otherwise secure such rights for CLEC. CLEC agrees to reimburse AT&T-22STATE for the reasonable and demonstrable Costs incurred by AT&T-22STATE in obtaining such rights for CLEC.
Where AT&T. 13STATE is the 911 System Service Provider, and Carrier deploys an NCAS solution:
4.3.2.1 Carrier’s designated third-party provider shall perform the above database functions.
4.3.2.2 Carrier’s designated third party shall be responsible for ensuring Carrier's Shell Records for XXX are submitted to AT&T-13STATE, for inclusion in AT&T-13STATE’s 911 DBMS, on a timely basis, once E911 trunking has been established and tested between Carrier’s MSC and all appropriate SRs.
4.3.2.3 Carrier’s third-party provider shall provide initial and ongoing updates of Carrier's Shell Records for ALI that are in electronic format based upon established NENA standards.
Where AT&T. 13STATE is the 911 System Service Provider, and Carrier deploys an NCAS solution:
4.3.2.1 Carrier’s designated third-party provider shall perform the above database functions.
4.3.2.2 Carrier’s designated third party shall be responsible for ensuring Carrier's Shell Records for XXX are submitted to AT&T-13STATE, for inclusion in AT&T-13STATE’s 911 DBMS, on a timely basis, once E911 trunking has been established and tested between Carrier’s MSC and all appropriate SRs.
Where AT&T. 13STATE is the 911/E911 Database Provider,
Where AT&T. 22STATE manages the 911 and E911 Databases and WSP deploys a CAS or Hybrid-CAS Solution, and also NCAS in AT&T-22STATE, utilizing AT&T-22STATE E911 DBMS:
Where AT&T. ILLINOIS is only providing DA on behalf of MCIm, the calls will be branded. When the same trunk group is used to provide OS and DA services to MCIm, calls will be branded at MCIm’s request with the same brand. There may be separate brands where separate trunk groups are utilized.
Where AT&T. 22STATE manages the DBMS, AT&T-22STATE shall establish a process for the management of NPA splits by populating the DBMS with the appropriate NPA codes.
