Mich. PSC gave Ameritech and Verizon until Jan. 24 to explain why...
Mich. PSC gave Ameritech and Verizon until Jan. 24 to explain why they couldn’t implement any relief plan for Pontiac 248 area code before mid-2002, year after code is projected to run out of numbers. Companies in Dec. told…
Sign up for a free preview to unlock the rest of this article
Timely, relevant coverage of court proceedings and agency rulings involving tariffs, classification, valuation, origin and antidumping and countervailing duties. Each day, Trade Law Daily subscribers receive a daily headline email, in-depth PDF edition and access to all relevant documents via our trade law source document library and website.
PSC they couldn’t address relief for 248 until they completed relief plans adopted for Lansing 517 and suburban Detroit 810 codes. PSC wants to know why companies can’t work concurrently on 3 code relief plans, hire outside contractors to handle one or more plans or implement interim code conservation measures such as rate center consolidation or number pooling. PSC said delay contemplated by 2 incumbents would lead to number shortage that would greatly inconvenience Pontiac customers and have “chilling effect” on development of local competition in city. In another matter, PSC approved amendment to Ameritech’s statement of generally available terms (SGAT) for local interconnection to offer CLECs several additional types of network element bundles. Ameritech agreed to incorporate amendment in its existing interconnection agreements with CLECs. It said it proposed change to meet Telecom Act requirement for nondiscriminatory access to network elements. However, PSC declined Ameritech request for finding that change would put company in full compliance with unbundled network element (UNE checklist requirement of Sec. 271. PSC said request was premature. Agency said it wanted to see effect of new UNE combinations on development of competition before making any UNE- related checklist finding.