Common use of Trunking Requirements Clause in Contracts

Trunking Requirements. To the extent that ILEC is serving its own switches and wishes to direct trunk to AT&T’s OS/DA switches, then the Parties’ physical trunking requirements are described in this section. All OS/DA trunking arrangements shall be subject to the mutual agreement of the Parties. Any unresolved differences in the OS/DA trunking arrangements shall be handled pursuant to the Dispute Resolution provisions in Section 7.10 below. 3.1 The demarcation point for OS/DA traffic between the Parties’ networks at a minimum must be within the LATA in which the ILEC’s OS/DA traffic originates. 3.1.1 Because ILEC’s switch may serve end users in more than one LATA, the Parties agree that, for purposes of this Appendix OS/DA only, ILEC’s OS/DA traffic originates from the physical location of the end user dialing “0” or “411”, and not the physical location of ILEC’s switch. 3.1.2 To the extent ILEC is serving via circuit-switched wireless technology, the physical location of the end user dialing “0” or “411” shall be deemed the end user’s physical billing address, regardless of whether the end user may be roaming at the time of placing the OS/DA call. 3.2 The Parties’ general preference would be to establish an OS/DA demarcation point at the AT&T OS/DA switch in that LATA , but the Parties recognize that the demarcation point for OS/DA traffic between the Parties’ networks could depend on a variety of engineering and location-specific factors which include, but are not limited to, 3.2.1 The size and type of facilities needed to carry ILEC’s switch-based OS/DA traffic 3.2.2 Whether ILEC wishes to direct trunk for both OS and DA, or just OS, or just DA 3.2.3 Whether ILEC or ILEC’s affiliate already has existing OS/DA facilities in place to the AT&T OS/DA platforms. 3.3 ILEC shall provide the necessary facilities to direct trunk traffic to AT&T’s OS/DA switch(es) at a mutually- agreeable demarcation point between the Parties’ networks. ILEC may self-provision these OS/DA facilities, lease them from third parties, or lease them from AT&T’s intrastate Special Access Tariff. ILEC will be financially responsible for the OS/DA facilities on its side of the demarcation point, and AT&T will be financially responsible for the OS/DA facilities on its side of the demarcation point. 3.4 General OS/DA Trunking Requirements 3.4.1 ILEC will initiate a request to the AT&T Account Manager for all OS/DA trunk groups from its switch to the appropriate AT&T OS/DA switches as a segregated one-way trunk group utilizing Multi-Frequency (MF) signaling. 3.4.2 ILEC will employ Exchange Access Operator Services Signaling (EAOSS) from its switches to the AT&T OS/DA switches that are equipped to accept 10 Digit Signaling for Automatic Number Identification (ANI). 3.4.3 If EAOSS is not technically feasible, Modified Operator Services Signaling (XXXX) will be utilized, and a segregated one-way trunk group with MF signaling will be established from ILEC to each AT&T OS/DA switch for each served NPA in the LATA. 3.5 Specific OS/DA Trunk Groups, and their Requirements 3.5.1 Operator Service (OS) Trunks: ILEC shall establish a one-way trunk group from ILEC’s switch to the AT&T Operator Services switch serving OS end users in that LATA. An OS only trunk group will be designated with the appropriate OS traffic use code and modifier. If the trunk group transports combined OS/DA/DACC over the same trunk group, then the group will be designated with a different traffic use code and modifier for combined services. ILEC will have administrative control for the purpose of issuing a request to the AT&T Account Manager on this one-way trunk group.

Trunking Requirements. 3.1 To the extent that ILEC is serving its own switches and wishes to direct trunk to AT&T’s OS/DA switches, then the Parties’ physical trunking requirements are described in this section. All OS/DA trunking arrangements shall be subject to the mutual agreement of the Parties. Any unresolved differences in the OS/DA trunking arrangements shall be handled pursuant to the Dispute Resolution provisions in Section 7.10 below. 3.1 3.2 The demarcation point for OS/DA traffic between the Parties’ networks at a minimum must be within the LATA in which the ILEC’s OS/DA traffic originates. 3.1.1 3.2.1 Because ILEC’s switch may serve end users in more than one LATA, the Parties agree that, for purposes of this Appendix OS/DA onlyAgreement, ILEC’s OS/DA traffic originates from the physical location of the end user dialing “0” or “411”, and not the physical location of ILEC’s switch. 3.1.2 To the extent ILEC is serving via circuit-switched wireless technology, the physical location of the end user dialing “0” or “411” shall be deemed the end user’s physical billing address, regardless of whether the end user may be roaming at the time of placing the OS/DA call. 3.2 3.3 The Parties’ general preference would be Parties agree to establish an OS/DA demarcation meet point at the AT&T OS/DA switch in that LATA LATA, but unless after consideration of the Parties recognize that the demarcation point for OS/DA traffic between the Parties’ networks could depend on a variety of following engineering and location-specific locations factors which includeor other relevant factors, but are a meet point at the AT&T switch is not limited to,economically feasible or practical: 3.2.1 The 3.3.1 the size and type of facilities needed to carry ILEC’s switch-based OS/DA traffic; 3.2.2 Whether 3.3.2 whether ILEC wishes to direct trunk for both OS and DA, or just OS, or just DA; 3.2.3 Whether 3.3.3 whether ILEC or ILEC’s affiliate already has existing OS/DA facilities in place to the AT&T OS/DA platforms. 3.3 3.4 ILEC shall provide the necessary facilities to direct trunk traffic to AT&T’s OS/DA switch(es) at a mutually- agreeable demarcation the meet point between the Parties’ networks. ILEC may self-provision these OS/DA facilities, lease them from third parties, or lease them from AT&T’s intrastate Special Access Tariff. ILEC will be financially responsible for the OS/DA facilities on its side of the demarcation meet point, and AT&T will be financially responsible for the OS/DA facilities on its side of the demarcation meet point. 3.4 3.5 General OS/DA Trunking Requirements 3.4.1 3.5.1 ILEC will initiate a request to the AT&T Account Manager for all OS/DA trunk groups from its switch to the appropriate AT&T OS/DA switches as a segregated one-way trunk group utilizing Multi-Frequency (MF) signaling. 3.4.2 ILEC will employ 3.5.2 Exchange Access Operator Services Signaling (EAOSS) will be utilized, and a segregated one-way trunk group with MF signaling will be established from its switches ILEC to the each AT&T OS/DA switches that are equipped to accept 10 Digit Signaling for switch. EAOSS signaling requires 10-digit Automatic Number Identification (ANI). 3.4.3 If 3.5.3 Where EAOSS is not technically feasibleavailable, Modified Operator Services Signaling (XXXX) will be utilized, and a segregated one-way trunk group with MF signaling will be established from ILEC to each AT&T OS/DA switch for each NPA served NPA in the LATA. XXXX signaling requires 7-digit ANI. 3.5 3.6 Specific OS/DA Trunk Groups, and their Requirements 3.5.1 3.6.1 Operator Service (OS) Trunks: ILEC shall establish a one-way trunk group from ILEC’s switch to the AT&T Operator Services OS switch serving OS end users in that LATA. An OS only trunk group will be designated with the appropriate OS traffic use code and modifier. If ILEC will have administrative control for the purpose of issuing a request to AT&T on this one-way trunk group. 3.6.2 Directory Assistance (DA)/Directory Assistance Call Completion (DACC) Trunks: ILEC shall establish a one-way trunk group transports combined OS/from ILEC’s switch to the AT&T DA switch serving DA end users in that LATA. This trunk group will transport DA/DACC over the same trunk group, only and then the trunk group will be designated with a different the appropriate DA traffic use code and modifier for combined servicesmodifier. ILEC will have administrative control for the purpose of issuing a request to the AT&T Account Manager on this one-way trunk group. 3.6.3 Where available, if OS/DA/DACC is transported together on a combined trunk group, then the group will be designated with a different, appropriate traffic use code and modifier.

Trunking Requirements. To the extent that ILEC is serving its own switches and wishes to direct trunk to AT&T’s OS/DA switches, then the Parties’ physical trunking requirements are described in this section. All OS/DA trunking arrangements shall be subject to the mutual agreement of the Parties. Any unresolved differences in the OS/DA trunking arrangements shall be handled pursuant to the Dispute Resolution provisions in Section 7.10 below. 3.1 The demarcation point for OS/DA traffic between the Parties’ networks at a minimum must be within the LATA in which the ILEC’s OS/DA traffic originates. 3.1.1 Because ILEC’s switch may serve end users in more than one LATA, the Parties agree that, for purposes of this Appendix OS/DA only, ILEC’s OS/DA traffic originates from the physical location of the end user dialing “0” or “411”, and not the physical location of ILEC’s switch. 3.1.2 To the extent ILEC is serving via circuit-switched wireless technology, the physical location of the end user dialing “0” or “411” shall be deemed the end user’s physical billing address, regardless of whether the end user may be roaming at the time of placing the OS/DA call. 3.2 The Parties’ general preference would be to establish an OS/DA demarcation point at the AT&T OS/DA switch in that LATA , but the Parties recognize that the demarcation point for OS/DA traffic between the Parties’ networks could depend on a variety of engineering and location-specific factors which include, but are not limited to,: 3.2.1 The the size and type of facilities needed to carry ILEC’s switch-based OS/DA traffic; 3.2.2 Whether whether ILEC wishes to direct trunk for both OS and DA, or just OS, or just DA; and 3.2.3 Whether whether ILEC or ILEC’s affiliate already has existing OS/DA facilities in place to the AT&T OS/DA platforms. 3.3 ILEC shall provide the necessary facilities to direct trunk traffic to AT&T’s OS/DA switch(es) at a mutually- agreeable demarcation point between the Parties’ networks. ILEC may self-provision these OS/DA facilities, lease them from third parties, or lease them from AT&T’s intrastate Special Access Tariff. ILEC will be financially responsible for the OS/DA facilities on its side of the demarcation point, and AT&T will be financially responsible for the OS/DA facilities on its side of the demarcation point. 3.4 General OS/DA Trunking Requirements 3.4.1 ILEC will initiate a request to the AT&T Account Manager for all OS/DA trunk groups from its switch to the appropriate AT&T OS/DA switches as a segregated one-way trunk group utilizing Multi-Frequency (MF) signaling. 3.4.2 ILEC will employ Exchange Access Operator Services Signaling (EAOSS) from its switches to the AT&T OS/DA switches that are equipped to accept 10 Digit Signaling for Automatic Number Identification (ANI). 3.4.3 If EAOSS is not technically feasible, Modified Operator Services Signaling (XXXX) will be utilized, and a segregated one-way trunk group with MF signaling will be established from ILEC to each AT&T OS/DA switch for each served NPA in the LATA. 3.5 Specific OS/DA Trunk Groups, and their Requirements 3.5.1 Operator Service (OS) Trunks: ILEC shall establish a one-way trunk group from ILEC’s switch to the AT&T Operator Services switch serving OS end users in that LATA. An OS only trunk group will be designated with the appropriate OS traffic use code and modifier. If the trunk group transports combined OS/DA/DACC over the same trunk group, then the group will be designated with a different traffic use code and modifier for combined services. ILEC will have administrative control for the purpose of issuing a request to the AT&T Account Manager on this one-way trunk group.

Trunking Requirements. To the extent that ILEC is serving its own switches and wishes to direct trunk to AT&T’s OS/DA switches, then the Parties’ physical trunking requirements are described in this section. All OS/DA trunking arrangements shall be subject to the mutual agreement of the Parties. Any unresolved differences in the OS/DA trunking arrangements shall be handled pursuant to the Dispute Resolution provisions in Section 7.10 below. 3.1 The demarcation point for OS/DA traffic between the Parties’ networks at a minimum must be within the LATA in which the ILEC’s OS/DA traffic originates. 3.1.1 Because ILEC’s switch may serve end users in more than one LATA, the Parties agree that, for purposes of this Appendix OS/DA only, ILEC’s OS/DA traffic originates from the physical location of the end user dialing “0” or “411”, and not the physical location of ILEC’s switch. 3.1.2 To the extent ILEC is serving via circuit-switched wireless technology, the physical location of the end user dialing “0” or “411” shall be deemed the end user’s physical billing address, regardless of whether the end user may be roaming at the time of placing the OS/DA call. 3.2 The Parties’ general preference would be to establish an OS/DA demarcation point at the AT&T OS/DA switch in that LATA , but the Parties recognize that the demarcation point for OS/DA traffic between the Parties’ networks could depend on a variety of engineering and location-specific factors which include, but are not limited to, 3.2.1 The size and type of facilities needed to carry ILEC’s switch-based OS/DA traffic. 3.2.2 Whether ILEC wishes to direct trunk for both OS and DA, or just OS, or just DA. 3.2.3 Whether ILEC or ILEC’s affiliate already has existing OS/DA facilities in place to the AT&T OS/DA platforms. 3.3 ILEC shall provide the necessary facilities to direct trunk traffic to AT&T’s OS/DA switch(es) at a mutually- agreeable demarcation point between the Parties’ networks. ILEC may self-provision these OS/DA facilities, lease them from third parties, or lease them from AT&T’s intrastate Special Access Tariff. ILEC will be financially responsible for the OS/DA facilities on its side of the demarcation point, and AT&T will be financially responsible for the OS/DA facilities on its side of the demarcation point. 3.4 General OS/DA Trunking Requirements 3.4.1 ILEC will initiate a request to the AT&T Account Manager for all OS/DA trunk groups from its switch to the appropriate AT&T OS/DA switches as a segregated one-way trunk group utilizing Multi-Frequency (MF) signaling. 3.4.2 ILEC will employ Exchange Access Operator Services Signaling (EAOSS) from its switches to the AT&T OS/DA switches that are equipped to accept 10 Digit Signaling for Automatic Number Identification (ANI). 3.4.3 If EAOSS is not technically feasible, Modified Operator Services Signaling (XXXX) will be utilized, and a segregated one-way trunk group with MF signaling will be established from ILEC to each AT&T OS/DA switch for each served NPA in the LATA. 3.5 Specific OS/DA Trunk Groups, and their Requirements 3.5.1 Operator Service (OS) Trunks: ILEC shall establish a one-way trunk group from ILEC’s switch to the AT&T Operator Services switch serving OS end users in that LATA. An OS only trunk group will be designated with the appropriate OS traffic use code and modifier. If the trunk group transports combined OS/DA/DACC over the same trunk group, then the group will be designated with a different traffic use code and modifier for combined services. ILEC will have administrative control for the purpose of issuing a request to the AT&T Account Manager on this one-way trunk group.

Trunking Requirements. To the extent that ILEC is serving its own switches and wishes to direct trunk to AT&T’s OS/DA switches, then the Parties’ physical trunking requirements are described in this section. All OS/DA trunking arrangements shall be subject to the mutual agreement of the Parties. Any unresolved differences in the OS/DA trunking arrangements shall be handled pursuant to the Dispute Resolution provisions in Section 7.10 below. 3.1 The demarcation point for OS/DA traffic between the Parties’ networks at a minimum must be within the LATA in which the ILEC’s OS/DA traffic originates. 3.1.1 Because ILEC’s switch may serve end users in more than one LATA, the Parties agree that, for purposes of this Appendix OS/DA only, ILEC’s OS/DA traffic originates from the physical location of the end user dialing “0” or “411”, and not the physical location of ILEC’s switch... 3.1.2 To the extent ILEC is serving via circuit-switched wireless technology, the physical location of the end user dialing “0” or “411” shall be deemed the end user’s physical billing address, regardless of whether the end user may be roaming at the time of placing the OS/DA call. 3.2 The Parties’ general preference would be to establish an OS/DA demarcation point at the AT&T OS/DA switch in that LATA , but the Parties recognize that the demarcation point for OS/DA traffic between the Parties’ networks could depend on a variety of engineering and location-specific factors which include, but are not limited to, 3.2.1 The size and type of facilities needed to carry ILEC’s switch-based OS/DA traffic 3.2.2 Whether ILEC wishes to direct trunk for both OS and DA, or just OS, or just DA 3.2.3 Whether ILEC or ILEC’s affiliate already has existing OS/DA facilities in place to the AT&T OS/DA platforms. 3.3 ILEC shall provide the necessary facilities to direct trunk traffic to AT&T’s OS/DA switch(es) at a mutually- agreeable demarcation point between the Parties’ networks. ILEC may self-provision these OS/DA facilities, lease them from third parties, or lease them from AT&T’s intrastate Special Access Tariff. ILEC will be financially responsible for the OS/DA facilities on its side of the demarcation point, and AT&T will be financially responsible for the OS/DA facilities on its side of the demarcation point. 3.4 General OS/DA Trunking Requirements 3.4.1 ILEC will initiate a request to the AT&T Account Manager for all OS/DA trunk groups from its switch to the appropriate AT&T OS/DA switches as a segregated one-way trunk group utilizing Multi-Frequency (MF) signaling. 3.4.2 ILEC will employ Exchange Access Operator Services Signaling (EAOSS) from its switches to the AT&T OS/DA switches that are equipped to accept 10 Digit Signaling for Automatic Number Identification (ANI). 3.4.3 If EAOSS is not technically feasible, Modified Operator Services Signaling (XXXX) will be utilized, and a segregated one-way trunk group with MF signaling will be established from ILEC to each AT&T OS/DA switch for each served NPA in the LATA. 3.5 Specific OS/DA Trunk Groups, and their Requirements 3.5.1 Operator Service (OS) Trunks: ILEC shall establish a one-way trunk group from ILEC’s switch to the AT&T Operator Services switch serving OS end users in that LATA. An OS only trunk group will be designated with the appropriate OS traffic use code and modifier. If the trunk group transports combined OS/DA/DACC over the same trunk group, then the group will be designated with a different traffic use code and modifier for combined services. ILEC will have administrative control for the purpose of issuing a request to the AT&T Account Manager on this one-way trunk group.

Trunking Requirements. 3.1 To the extent that ILEC is serving its own switches and wishes to direct trunk to AT&T’s OS/DA switches, then the Parties’ physical trunking requirements are described in this section. All OS/DA trunking arrangements shall be subject to the mutual agreement of the Parties. Any unresolved differences in the OS/DA trunking arrangements shall be handled pursuant to the Dispute Resolution provisions in Section 7.10 below. 3.1 3.2 The demarcation point for OS/DA traffic between the Parties’ networks at a minimum must be within the LATA in which the ILEC’s OS/DA traffic originates. 3.1.1 3.2.1 Because ILEC’s switch may serve end users in more than one LATA, the Parties agree that, for purposes of this Appendix OS/DA only, ILEC’s OS/DA traffic originates from the physical location of the end user dialing “0” or “411”, and not the physical location of ILEC’s switch. 3.1.2 To the extent ILEC is serving via circuit-switched wireless technology, the physical location of the end user dialing “0” or “411” shall be deemed the end user’s physical billing address, regardless of whether the end user may be roaming at the time of placing the OS/DA call. 3.2 3.3 The Parties’ general preference would be Parties agree to establish an OS/DA demarcation meet point at the AT&T OS/DA switch in that LATA LATA, but unless after consideration of the Parties recognize that the demarcation point for OS/DA traffic between the Parties’ networks could depend on a variety of following engineering and location-specific locations factors which includeor other relevant factors, but are a meet point at the AT&T switch is not limited to,economically feasible or practical: 3.2.1 3.3.1 The size and type of facilities needed to carry ILEC’s switch-based OS/DA traffic. 3.2.2 3.3.2 Whether ILEC wishes to direct trunk for both OS and DA, or just OS, or just DA. 3.2.3 3.3.3 Whether ILEC or ILEC’s affiliate already has existing OS/DA facilities in place to the AT&T OS/DA platforms. 3.3 3.4 ILEC shall provide the necessary facilities to direct trunk traffic to AT&T’s OS/DA switch(es) at a mutually- agreeable demarcation the meet point between the Parties’ networks. ILEC may self-provision these OS/DA facilities, lease them from third parties, or lease them from AT&T’s intrastate Special Access Tariff. ILEC will be financially responsible for the OS/DA facilities on its side of the demarcation meet point, and AT&T will be financially responsible for the OS/DA facilities on its side of the demarcation meet point. 3.4 3.5 General OS/DA Trunking Requirements 3.4.1 3.5.1 ILEC will initiate a request to the AT&T Account Manager for all OS/DA trunk groups from its switch to the appropriate AT&T OS/DA switches as a segregated one-way trunk group utilizing Multi-Frequency (MF) signaling. 3.4.2 ILEC will employ 3.5.2 Exchange Access Operator Services Signaling (EAOSS) from its switches to the AT&T OS/DA switches that are equipped to accept 10 Digit Signaling for Automatic Number Identification (ANI). 3.4.3 If EAOSS is not technically feasible, Modified Operator Services Signaling (XXXX) will be utilized, and a segregated one-way trunk group with MF signaling will be established from ILEC to each AT&T OS/DA switch. EAOSS signaling requires 10-digit Automatic Number Identification (ANI). 3.5.3 Where EAOSS is not available, Modified Operator Services Signaling (XXXX) will be utilized, and a segregated one-way trunk group with MF Signaling will be established from ILEC to each AT&T OS/DA switch for each NPA served NPA in the LATA. XXXX signaling requires 7-digit ANI. 3.5 3.6 Specific OS/DA Trunk Groups, and their Requirements 3.5.1 3.6.1 Operator Service (OS) Trunks: ILEC shall establish a one-way trunk group from ILEC’s switch to the AT&T Operator Services switch serving OS end users in that LATA. An OS only trunk group will be designated with the appropriate OS traffic use code and modifier. If ILEC will have administrative control for the purpose of issuing a request to the AT&T Account Manager on this one-way trunk group. 3.6.2 Directory Assistance (DA)/ Directory Assistance Call Completion (DACC) Trunks: ILEC shall establish a one-way trunk group transports combined OS/from ILEC’s switch to the AT&T Directory Assistance switch serving DA end users in that LATA. This trunk group will transport DA/DACC over the same trunk group, only and then the trunk group will be designated with a different the appropriate DA traffic use code and modifier for combined servicesmodifier. ILEC will have administrative control for the purpose of issuing a request to the AT&T Account Manager on this one-way trunk group. 3.6.3 Where available, if OS/DA/DACC is transported together on a combined trunk group, then the group will be designated with a different, appropriate traffic use code and modifier.