Routing and Provisioning. Each Party shall route Information Service Traffic originates on its own network to the appropriate information services platform(s) connected to the other Party's network. Where the FOCAL uses its own network facilities, the FOCAL will establish a direct trunk group to the BA information services tandem switch. This trunk group will be utilized to allow the FOCAL to route Information Service Traffic originated on its network to BA. Where BA routing plans permit a combination of POTS and IP traffic on such direct trunk groups, the FOCAL may route a combination of POTS and IP traffic without establishing a separate direct trunk group exclusively for IP data. However, where BA requires direct trunks dedicated to IP traffic, the FOCAL must establish direct, dedicated bunking for its IP traffic. Such determinations will be at the sole discretion of BA, on a par with its established routing requirements in each LATA, and are subject to change. Where the FOCAL utilizes the BA network through the purchase of unbundled network elements, Information Service Traffic may be routed over BA information service trunks on a shared basis.
Routing and Provisioning. Each Party shall route Information Service Traffic which originates on its own network to the appropriate information services platform(s) connected to the other Party’s network. Where Cox uses its own network facilities, Cox will establish a direct trunk group to the BA-RI information services tandem switch. This trunk group will be utilized to allow Cox to route Information Service Traffic originated on its network to BA-RI. Where BA-RI routing plans permit a combination of POTS and IP traffic on such direct trunk groups, Cox may route a combination of POTS and IP traffic without establishing a separate direct trunk group exclusively for IP data. However, where BA-RI requires direct trunks dedicated to IP traffic, Cox must establish direct, dedicated trunking for its IP traffic. Such determinations will be at the sole discretion of BA-RI, on a par with its established routing requirements in each LATA, and are subject to change. Where Cox utilizes the BA-RI network through the purchase of unbundled network elements, Information Service Traffic may be routed over BA-RI information service trunks on a shared basis.
Routing and Provisioning. Each Party shall route Information Service Traffic which originates on its own network to the appropriate information services platform(s) connected to the other Party's network. Where the NEFC uses its own network facilities, the NEFC will establish a direct trunk group to the NYNEX information services tandem switch. This trunk group will be utilized to allow the NEFC to route Information Service Traffic originated on its network to NYNEX. Where NYNEX routing plans permit a combination of POTS and IP traffic on such direct trunk groups, the NEFC may route a combination of POTS and IP traffic without establishing a separate direct trunk group exclusively for IP data. However, where NYNEX requires direct trunks dedicated to IP traffic, the NEFC must establish direct, dedicated trunking for its IP traffic. Such determinations will be at the sole discretion of NYNEX, on a par with its established routing requirements in each LATA, and are subject to change. Where NEFC utilizes the NYNEX network through the purchase of unbundled network elements, Information Service Traffic may be routed over NYNEX information service trunks on a shared basis.
Routing and Provisioning. Each Party shall route Information Service Traffic which originates on its own network to the appropriate information services platform(s) connected to the other Party's network. Where CLEC uses its own network facilities, CLEC will establish a direct trunk group to the Xxxx Atlantic information services tandem switch. This trunk group will be utilized to allow the CLEC to route Information Service Traffic originated on its network to BA. Where BA routing plans permit a combination of POTS and Information Provider traffic on such direct trunk groups, CLEC may route a combination of POTS and Information Provider traffic without establishing a separate direct trunk group exclusively for Information Provider data. However, in LATAs where BA requires direct trunks dedicated to Information Provider traffic, CLEC must establish direct, dedicated trunking for its Information Provider traffic. Such determinations will be at the sole discretion of Xxxx Atlantic, on a par with its established routing requirements in each LATA, and are subject to change. Where CLEC utilizes the BA network through the purchase of unbundled network elements, Information Service Traffic may be routed over BA information service trunks on a shared basis.
Routing and Provisioning. Each Party shall route Information Service Traffic which originates on its own network to the appropriate information services platform(s) connected to the other Party’s network. Where ANTC uses its own network facilities, ANTC will establish a dedicated trunk group to the NYNEX information services tandem switch. This trunk group will be utilized to allow ANTC to route Information Service Traffic originated on its network to NYNEX. Where ANTC utilizes the NYNEX network through the purchase of unbundled network elements, Information Service Traffic may be routed over NYNEX information service trunks on a shared basis.
