Additional Switching System Hierarchy and Trunking Requirements. For purposes of routing Covad traffic to BA, the subtending arrangements between BA Tandem Switches and BA End Office Switches shall be the same as the Tandem/End Office subtending arrangements BA maintains for the routing of its own or other carriers' traffic. For purposes of routing BA traffic to Covad, the subtending arrangements between Covad Tandem Switches (or functional equivalent) and Covad End Office Switches (or functional equivalent) shall be the same as the Tandem/End Office subtending arrangements (or functional equivalent) which Covad maintains for the routing of its own or other carriers' traffic.
Additional Switching System Hierarchy and Trunking Requirements. 5.3.1 For purposes of routing Focal traffic to BA, the subtending arrangements between BA Access Tandem Switches and BA End Office Switches shall be the same as the Access Tandem/End Office subtending arrangements BA maintains for the routing of its own or other carriers' traffic. For purposes of routing BA traffic to Focal, the subtending arrangements between Focal Access Tandem Switches (or functional equivalent) and Focal End Office Switches (or functional equivalent) shall be the same as the Access Tandem/End Office subtending arrangements (or functional equivalent) which Focal maintains for the routing of its own or other carriers' traffic.
Additional Switching System Hierarchy and Trunking Requirements. For purposes of routing traffic to the other Party, both Parties agree to use the Local Exchange Routing Guide (LERG).
Additional Switching System Hierarchy and Trunking Requirements. 5.3.1 For purposes of routing ETC traffic to BA, the subtending arrangements between BA Access Tandem Switches and BA End Office Switches shall be the same as the Access Tandem/End Office subtending arrangements BA maintains for the routing of its own or other carriers’ traffic. For purposes of routing BA traffic to ETC, the subtending arrangements between ETC Access Tandem Switches (or functional equivalent) and ETC End Office Switches (or functional equivalent) shall be the same as the Access Tandem/End Office subtending arrangements (or functional equivalent) which ETC maintains for the routing of its own or other carriers’ traffic.
Additional Switching System Hierarchy and Trunking Requirements. 5.3.1 For purposes of routing TCG traffic to BA, the subtending arrangements between BA Tandem Switches and BA End Office Switches shall be the same as the Tandem/End Office subtending arrangements BA maintains for the routing of its own or other carriers’ traffic. For purposes of routing BA traffic to TCG, the subtending arrangements between TCG Tandem Switches (or functional equivalent) and TCG End Office Switches (or functional equivalent) shall be the same as the Tandem/End Office subtending arrangements (or functional equivalent) which TCG maintains for the routing of its own or other carriers’ traffic.
Additional Switching System Hierarchy and Trunking Requirements. For purposes of routing ACI traffic to BA, the subtending arrangements between BA Tandem Switches and BA End Office Switches shall be the same as the Tandem/End Office subtending arrangements BA maintains for the routing of its own or other carriers' traffic. For purposes of routing BA traffic to ACI, the subtending arrangements between ACI Tandem Switches (or functional equivalent) and ACI End Office Switches (or functional equivalent) shall be the same as the Tandem/End Office subtending arrangements (or functional equivalent) which ACI maintains for the routing of its own or other carriers' traffic.
Additional Switching System Hierarchy and Trunking Requirements. 4.3 Additional Switching System Hierarchy and Trunking Requirements4.3 Additional Switching System Hierarchy and Trunking Requirements4.3 Additional Switching System Hierarchy and Trunking Requirements4.3 Additional Switching System Hierarchy and Trunking Requirements4.3 Additional Switching System Hierarchy and Trunking Requirements4.3
Additional Switching System Hierarchy and Trunking Requirements. For purposes of routing PageNet traffic to BA, the subtending arrangements between BA Access Tandem Switches and BA End Office Switches shall be the same as the Access Tandem/End Office subtending arrangements BA maintains for the routing of its own or other carriers’ traffic. For purposes of routing BA traffic to PageNet, the subtending arrangements between PageNet Access Tandem Switches (or functional equivalent) and PageNet End Office Switches (or functional equivalent) shall be the same as the Access Tandem/End Office subtending arrangements (or functional equivalent) which PageNet maintains for the routing of its own or other carriers’ traffic.
Additional Switching System Hierarchy and Trunking Requirements. For purposes of routing Cox traffic to Pac-West, the subtending arrangements between Pac-West Tandem Switches (or functional equivalent) and Pac-West End Office Switches (or functional equivalent) shall be the same as the Tandem/End Office subtending arrangements Pac-West maintains for the routing of its own or other carriers' traffic. For purposes of routing Pac-West traffic to Cox, the subtending arrangements between Cox Tandem Switches (or functional equivalent) and Cox End Office Switches (or functional equivalent) shall be the same as the Tandem/End Office subtending arrangements (or functional equivalent) which Cox maintains for the routing of its own or other carriers' traffic.
Additional Switching System Hierarchy and Trunking Requirements. 5.3.1 For purposes of routing MFS traffic to BA, the subtending arrangements between BA Access Tandem Switches and BA End Office Switches shall be the same as the Access Tandem/End Office subtending arrangements BA maintains for the routing of its own or other carriers' traffic. For purposes of routing BA traffic to MFS, the subtending arrangements between MFS Access Tandem Switches (or functional equivalent and MFS End Office Switches (or functional equivalent) shall be the same as the Access Tandem/End Office subtending arrangements (or functional equivalent) which MFS maintains for the routing of its own or other carriers' traffic.
