Master Network Interconnection and Resale Agreement [Part F-J] - Liberty Telecom LLC and Central Telephone Co.-Nevada d/b/a Sprint of Nevada
PART F – INTERCONNECTION
| 59. | LOCAL INTERCONNECTION TRUNK ARRANGEMENT |
| 59.1. | The Parties shall initially reciprocally terminate Local Traffic and IntraLATA/InterLATA toll calls originating on the other Party’s network as follows: |
| 59.1.1. | The Parties shall make available to each other two-way trunks for the reciprocal exchange of combined Local Traffic, and non-equal access IntraLATA toll traffic. Neither Party is obligated under this Agreement to order reciprocal trunks or build facilities in the establishment of interconnection arrangements for the delivery of Internet traffic. The Party serving the Internet service provider shall order trunks or facilities from the appropriate tariff of the other Party for such purposes and will be obligated to pay the full cost of such facility. |
| 59.1.1.1. | The Parties agree to initially use two-way trunks (one-way directionalized) for an interim period. The Parties shall transition from directionalized two-way trunks upon mutual agreement, absent engineering or billing issues. The Parties shall transition all one-way trunks established under this Agreement. |
| 59.2. | Separate two-way trunks will be made available for the exchange of equal-access InterLATA or IntraLATA interexchange traffic that transits Sprint’s network. |
| 59.3. | Separate trunks will be utilized for connecting CLEC’s switch to each 911/E911 tandem. |
| 59.4. | Points of Interconnection |
| 59.4.1. | Physical Point of Interconnection. CLEC must establish a minimum of one Physical POI within in each LATA, at any technically feasible point, on Sprint’s network. Sprint reserves the right to establish its own Physical POI if CLEC elects to file, and the Commission approves, CLEC’s cost studies for transport. |
85
| 59.4.1.1. | CLEC will be responsible for engineering and maintaining its network on its side of the Physical POI. Sprint will be responsible for engineering and maintaining its network on its side of the Physical POI. |
| 59.4.1.2. | For construction of new facilities when the Parties choose to interconnect at a mid-span meet, CLEC and Sprint will jointly provision the facilities that connect the two networks. Sprint will be the “controlling carrier” for purposes of MECOD guidelines, as described in the joint implementation plan. Sprint will provide fifty percent (50%) of the facilities or to its exchange boundary, whichever is less. |
| 59.4.1.3. | If third party (i.e. Competitive Access Provider or “CAP”) leased facilities are used for interconnection, the Physical POI will be defined as the Sprint office in which the third party’s leased circuit terminates. |
| 59.4.1.4. | If CLEC utilizes leased facilities under a meet point arrangement between Sprint and a third party (i.e. a connecting ILEC) the Physical POI will be Sprint office where the leased facility terminates. |
| 59.4.2. | Virtual Point of Interconnection. The CLEC must establish a Virtual POI within each of Sprint’s mandatory local calling areas, different from the local calling area where the Physical POI resides, for those local calling areas in which the CLEC wants to receive local calls. CLEC may lease unbundled dedicated transport from Sprint between the Physical and Virtual POIs. If the local calling area is served by a Remote Switch Sprint will assess CLEC for unbundled transport between the host Central Office Switch and the Remote Switch at dedicated transport rates based on their proportionate share of the volume of traffic between the host and remote. |
| 59.4.3. | Sprint is responsible for transport to the Physical POI when the Physical POI is within the same local calling area where the call originates. |
| 59.4.4. | Where Virtual POIs are required, the CLEC is responsible for dedicated transport between the Virtual POIs and Physical POI. Sprint is responsible for transport to the Virtual POI when the Virtual POI is within the same local calling area where the call originates. |
| 60. | SIGNALING |
| 60.1. | Signaling protocol. The parties will interconnect their networks using SS7 signaling where technically feasible and available as defined in FR 905 Telcordia Standards including ISDN user part (ISUP) for trunk signaling and TCAP for CCS-based features in the interconnection of their networks. All Network Operations Forum (NOF) adopted standards shall be adhered to. |
86
| 60.2. | Standard interconnection facilities shall be extended superframe (ESF) with B8ZS line code. Where ESF/B8ZS is not available, CLEC will agree to use other interconnection protocols on an interim basis until the standard ESF/B8ZS is available. Sprint will provide anticipated dates of availability for those areas not currently ESF/B8ZS compatible. |
| 60.2.1. | Where CLEC is unwilling to utilize an alternate interconnection protocol, CLEC will provide Sprint an initial forecast of 64 Kbps clear channel capability (“64K CCC”) trunk quantities within thirty (30) days of the Effective Date consistent with the forecasting agreements between the parties. Upon receipt of this forecast, the parties will begin joint planning for the engineering, procurement, and installation of the segregated 64K CCC Local Interconnection Trunk Groups, and the associated ESF facilities, for the sole purpose of transmitting 64K CCC data calls between CLEC and Sprint. Where additional equipment is required, such equipment would be obtained, engineered, and installed on the same basis and with the same intervals as any similar growth job for IXC, CLEC, or Sprint internal customer demand for 64K CCC trunks. |
| 61. | NETWORK SERVICING |
| 61.1. | Trunk Forecasting |
| 61.1.1. | The Parties shall work towards the development of joint forecasting responsibilities for traffic utilization over trunk groups. Orders for trunks that exceed forecasted quantities for forecasted locations will be accommodated as facilities and or equipment are available. The Parties shall make all reasonable efforts and cooperate in good faith to develop alternative solutions to accommodate orders when facilities are not available. Intercompany forecast information must be provided by the Parties to each other twice a year. The initial trunk forecast meeting should take place soon after the first implementation meeting. A forecast should be provided at or prior to the first implementation meeting. The semi-annual forecasts shall project trunk gain/loss on a monthly basis for the forecast period, and shall include: |
| 61.1.1.1. | Semi-annual forecasted trunk quantities (which include baseline data that reflect actual Tandem and end office Local Interconnection and meet point trunks and Tandem-subtending Local Interconnection end office equivalent trunk requirements) for no more than two years (current plus one year); |
| 61.1.1.2. | The use of Common Language Location Identifier (CLLI-MSG), which are described in Telcordia documents BR 795-100-100 and BR 795-400-100; |
87
| 61.1.1.3. | Description of major network projects that affect the other Party will be provided in the semi-annual forecasts. Major network projects include but are not limited to trunking or network rearrangements, shifts in anticipated traffic patterns, or other activities by either party that are reflected by a significant increase or decrease in trunking demand for the following forecasting period. |
| 61.1.2. | Parties shall meet to review and reconcile their forecasts if forecasts vary significantly. |
| 61.1.3. | Each Party shall provide a specified point of contact for planning forecasting and trunk servicing purposes. |
| 61.1.4. | Trunking can be established to Tandems or end offices or a combination of both via either one-way or two-way trunks. Trunking will be at the DS-0, DS-1, DS-3/OC-3 level, or higher, as agreed upon by CLEC and Sprint. |
| 61.1.5. | The parties agree to abide by the following if a forecast cannot be agreed to: local interconnection trunk groups will be provisioned to the higher forecast. A blocking standard of one percent (1%) during the average busy hour shall be maintained. Should the Parties not agree upon the forecast, and the Parties engineer facilities at the higher forecast, the Parties agree to abide by the following: |
| 61.1.5.1. | In the event that one Party over-forecasts its trunking requirements by twenty percent (20%) or more, and the other Party acts upon this forecast to its detriment, the other Party may recoup any actual and reasonable expense it incurs. |
| 61.1.5.2. | The calculation of the twenty percent (20%) over-forecast will be based on the number of DS-1 equivalents for the total traffic volume to Sprint. |
| 61.1.5.3. | Expenses will only be recouped for non-recoverable facilities that cannot otherwise be used at any time within twelve (12) months after the initial installation for another purpose including but not limited to: other traffic growth between the Parties, internal use, or use with another party. |
| 61.2. | Grade of Service. A blocking standard of one percent (1%) during the average busy hour, as defined by each Party’s standards, for final trunk groups between a CLEC end office and a Sprint access Tandem carrying meet point traffic shall be maintained. All other final trunk groups are to be engineered with a blocking standard of one percent (1%). Direct end office trunk groups are to be engineered with a blocking standard of one percent (1%). |
| 61.3. | Trunk Servicing. Orders between the Parties to establish, add, change or disconnect trunks shall be processed by use of an ASR, or another industry standard eventually adopted to replace the ASR for trunk ordering. |
88
| 62. | NETWORK MANAGEMENT |
| 62.1. | Protective Protocols. Either Party may use protective network traffic management controls such as 7-digit and 10-digit code gaps on traffic toward each other’s network, when required to protect the public switched network from congestion due to facility failures, switch congestion or failure or focused overload. CLEC and Sprint will immediately notify each other of any protective control action planned or executed. |
| 62.2. | Expansive Protocols. Where the capability exists, originating or terminating traffic reroutes may be implemented by either party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes will not be used to circumvent normal trunk servicing. Expansive controls will only be used when mutually agreed to by the parties. |
| 62.3. | Mass Calling. CLEC and Sprint shall cooperate and share pre-planning information, where available, regarding cross-network call-ins expected to generate large or focused temporary increases in call volumes, to prevent or mitigate the impact of these events on the public switched network. Mass calling numbers are not cannot be used in conjunction with INP. |
| 63. | USAGE MEASUREMENT |
| 63.1. | Each Party shall calculate terminating interconnection minutes of use based on standard AMA recordings made within each Party’s network, these recordings being necessary for each Party to generate bills to the other Party. In the event either Party cannot measure minutes terminating on its network where technically feasible, the other Party shall provide the measuring mechanism or the Parties shall otherwise agree on an alternate arrangement. |
| 63.2. | Measurement of minutes of use over Local Interconnection trunk groups shall be in actual conversation seconds. The total conversation seconds over each individual Local Interconnection trunk group will be totaled for the entire monthly bill period and then rounded to the next whole minute. |
| 63.3. | Prior to the commencement of billing for interconnection, each Party shall provide to the other, the PLU of the traffic terminated to each other over the Local Interconnection trunk groups. |
| 63.3.1. | The Parties agree to review the accuracy of the PLU on a regular basis. If the initial PLU is determined to be inaccurate by more than twenty percent (20%), the Parties agree to implement the new PLU retroactively to the Effective Date of the contract. |
| 64. | TRANSIT TRAFFIC |
| 64.1. |
Transit Traffic means the delivery of local traffic by CLEC or Sprint originated by the end user of one Party and terminated to a third party LEC, ILEC, or CMRS provider over the local/intraLATA interconnection trunks. The following traffic |
89
|
types will be delivered by either Party: local traffic and intraLATA toll and switched traffic originated from CLEC or Sprint and delivered to such third party LEC, ILEC or CMRS; and intraLATA 800 traffic. |
| 64.2. | Terms and Conditions |
| 64.2.1. | Each Party acknowledges that it is the originating Party’s responsibility to enter into arrangements with each third party LEC, ILEC, or CMRS provider for the exchange of transit traffic to that third party, unless the Parties agree otherwise in writing. |
| 64.2.2. | Each Party acknowledges that the transiting Party does not have any responsibility to pay any third party LEC, ILEC, or CMRS provider charges for termination or any identifiable transit traffic from the originating Party. Both Parties reserve the right not to pay such charges on behalf of the originating Party. |
| 64.3. | Payment Terms and Conditions |
| 64.3.1. | In addition to the payment terms and conditions contained in other sections of this Agreement, the Parties shall compensate each other for transit service as follows: |
| 64.3.1.1. | The originating Party shall pay to the transiting Party a transit service charge as set forth in the Pricing Schedule; and |
| 64.3.1.2. | If the terminating Party requests, and the transiting Party does not provide, the terminating Party with the originating record in order for the terminating Party to bill the originating Party, the terminating Party shall default bill the transiting Party for transited traffic which does not identify the originating Party. |
| 64.4. | Billing Records and Exchange of Data |
| 64.4.1. | Parties will use the best efforts to convert all networks transporting transit traffic to deliver each call to the other Party’s network with SS7 Common Channel Interoffice Signaling (CCIS) and other appropriate TCAP messages in order to facilitate full interoperability and billing functions. The Parties agree to send all message indicators, including originating telephone number, local routing number and CIC. |
| 64.4.2. | The transiting Party agrees to provide the terminating Party information on traffic originated by a third party CLEC, ILEC, or CMRS provider. To the extent Sprint incurs additional cost in providing this billing information, CLEC agrees to reimburse Sprint for its direct costs of providing this information. |
| 64.4.3. | To the extent that the industry adopts a standard record format for recording originating and/or terminating transit calls, both Parties agree to comply with the industry-adopted format to exchange records. |
90
| 65. | INDIRECT TRAFFIC |
| 65.1. | Interconnection |
| 65.1.1. | For purposes of exchanging Indirect Traffic there is no physical or direct point of interconnection between the Parties, therefore neither Party is required to construct new facilities or make mid-span meet arrangements available to the other Party for Indirect Traffic. |
| 65.1.2. | Interconnection to a Carrier location within a tandem serving area will provide Sprint with access to the Carrier’s facilities within that MTA and to other companies which are likewise connected to Carrier within that tandem serving area for local and toll service purposes. |
| 65.2. | Exchange Of Traffic |
| 65.2.1. | The Parties will send each other Indirect Traffic, and may also send each other Transit Traffic. |
| 65.2.2. | Each Party acknowledges that it is the originating Party’s responsibility to enter into transiting arrangements with the third party providing the transit services. Each Party acknowledges that the transiting Party does not have any responsibility to pay any third party Telecommunications Carrier charges for termination of any identifiable Transit Traffic from the originating Party. |
| 65.2.3. | Each Party is responsible for the transport of originating calls from its network to its point of interconnection with the transiting Party. |
| 65.2.4. | Sprint reserves the right to require development and reporting of a jurisdictional usage factor indicating local/EAS, intrastate toll (access/toll) interstate access usage and CMRS, if applicable or CLEC’s actual usage reporting. Sprint and CLEC reserve the right to measure and audit all traffic to ensure that proper rates are being applied. CLEC agrees to work with Sprint to insure the necessary traffic data required for sampling purposes is available for such audit. |
| 65.3. | Compensation for Indirect Traffic |
| 65.3.1. | Non-Local and Non-Information Access Indirect Traffic |
| 65.3.1.1. | Compensation for the termination of non-Local traffic, non-Information Access Traffic and the origination of 800 traffic between the interconnecting Parties shall be based on the applicable access charges in accordance with FCC and Commission Rules and Regulations. |
| 65.3.1.2. |
Toll traffic, switched access, and special access traffic, if separately chargeable, shall be charged the appropriate rate out of the terminating Carrier’s tariff or via other appropriate meet point access arrangements. Where exact transport mileage is not |
91
|
available, an average, arrived at by mutual agreement of the Parties, will be used. |
| 65.3.2. | Local Traffic and Information Access Traffic. The rates set forth on Table 1 shall apply, in accordance with 36. |
| 65.3.2.1. | Indirect Traffic Terminating to Sprint |
| 65.3.2.1.1. | Each rate element utilized in completing a call shall be charged for completion of that call. For example, a call terminating from Carrier through the transiting party, and the over Sprint facilities through a Sprint Tandem Switch to a Sprint End Office Switch would include charges from Sprint to Carrier for Common Transport to the Tandem Switch, Tandem Switching, Common Transport to the End Office Switch and End Office switching. A call terminating from Carrier though the transiting party, and then over Sprint facilities through a Sprint End Office Switch to a Sprint Remote Switch would include charges from Sprint to Carrier for Common Transport to the End Office Switch (except where the transiting party is collocated in the Sprint End Office), End Office switching, and Common Transport to the Remote Switch. |
| 65.3.2.2. | Indirect Traffic Terminating to Carrier: |
| 65.3.2.2.1. | For Indirect Traffic terminating on Carrier’s network, Carrier will bill Sprint the same rates as Sprint charges Carrier for Indirect Local Traffic terminating on Sprint’s network. |
| 65.3.3. | Transit Traffic. The originating Party shall pay the transiting Party for the rate elements used, including Common Transport and Tandem Switching rate elements. |
| 66. | RESPONSIBILITIES OF THE PARTIES |
| 66.1. | Sprint and CLEC will review engineering requirements consistent with the Implementation Plan described in Part B, Section 31 and Part C, Part F, Section 61 and otherwise as set forth in this Agreement. |
| 66.2. | CLEC and Sprint shall share responsibility for all Control Office functions for Local Interconnection Trunks and Trunk Groups, and both parties shall share the overall coordination, installation, and maintenance responsibilities for these trunks and trunk groups. |
| 66.3. | CLEC and Sprint shall: |
| 66.3.1. | Provide trained personnel with adequate and compatible test equipment to work with each other’s technicians |
92
| 66.3.2. | Notify each other when there is any change affecting the service requested, including the due date. |
| 66.3.3. | Coordinate and schedule testing activities of their own personnel, and others as applicable, to ensure its interconnection trunks/trunk groups are installed per the interconnection order, meet agreed-upon acceptance test requirements, and are placed in service by the due date. |
| 66.3.4. | Perform sectionalization to determine if a trouble is located in its facility or its portion of the interconnection trunks prior to referring the trouble to each other. |
| 66.3.5. | Advise each other’s Control Office if there is an equipment failure which may affect the interconnection trunks. |
| 66.3.6. | Provide each other with a trouble reporting/repair contact number that is readily accessible and available twenty-four (24) hours/seven (7) days a week. Any changes to this contact arrangement must be immediately provided to the other party. |
| 66.3.7. | Provide to each other test-line numbers and access to test lines. |
| 66.3.8. | Cooperatively plan and implement coordinated repair procedures for the meet point and Local Interconnection trunks and facilities to ensure trouble reports are resolved in a timely and appropriate manner. |
93
PART G – INTERIM NUMBER PORTABILITY
| 67. | SPRINT PROVISION OF INTERIM NUMBER PORTABILITY |
| 67.1. | Sprint shall provide INP in accordance with requirements of the Act and FCC Rules and Regulations. INP shall be provided with minimum impairment of functionality, quality, reliability and convenience to subscribers of CLEC services until such time as LNP service is offered in the Sprint rate center, in which case INP will be discontinued. Beginning on the date LNP is available in an area, INP orders will no longer be processed, and the Parties will work together to convert the existing INP lines to LNP. |
| 68. | INTERIM NUMBER PORTABILITY |
| 68.1. | Interim Number Portability (INP) shall be provided to the extent technical capabilities allow, by a Sprint directed Remote Call Forwarding (RCF). In the event RCF is a purchased feature of the CLEC end user, there is no relationship between RCF and INP. Once LNP is generally available in Sprint’s serving area, RCF will be provided only as a retail service offering by Sprint. |
| 68.2. | Remote Call Forwarding (RCF) is an INP method to provide subscribers with service-provider portability by redirecting calls within the telephone network. When RCF is used to provide interim number portability, calls to the ported number will first route to the Sprint switch to which the ported number was previously assigned. The Sprint switch will then forward the call to a number associated with the CLEC designated switch to which the number is ported. CLEC may order any additional paths to handle multiple simultaneous calls to the same ported telephone number. |
| 68.3. | The trunking requirements will be agreed upon by Sprint and CLEC resultant from application of sound engineering principles. These trunking options may include SS7 signaling, in-band signaling, and may be one-way or two-way. The trunks used may be the same as those used for exchange of other Local Traffic and toll traffic between Sprint and CLEC. |
| 68.4. | Local Exchange Routing Guide (LERG) Reassignment. Portability for an entire NXX shall be provided by utilizing reassignment of the block to CLEC through the LERG. Updates to translations in the Sprint switching office from which the telephone number is ported will be made by Sprint prior to the date on which LERG changes become effective, in order to redirect calls to the CLEC switch via route indexing. |
| 68.5. | Other Currently Available Number Portability Provisions: |
| 68.5.1. | Where SS7 is available. Sprint shall exchange with CLEC, SS7 TCAP messages as required for the implementation CLASS or other features available in the Sprint network, if technically feasible. |
94
| 68.5.2. | Upon notification that CLEC will be initiating INP, Sprint shall disclose to CLEC any technical or capacity limitations that would prevent use of the requested INP in the affected switching office. Sprint and CLEC shall cooperate in the process of porting numbers to minimize subscriber out-of-service time, including promptly updating switch translations, where necessary, after notification that physical cut-over has been completed (or initiated), as CLEC may designate. |
| 68.5.3. | For INP, CLEC shall have the right to use the existing Sprint 911 infrastructure for all 911 capabilities. When RCF is used for CLEC subscribers, both the ported numbers and shadow numbers shall be stored in ALI databases. CLEC shall have the right to verify the accuracy of the information in the ALI databases. |
| 68.5.3.1. | When any INP method is used to port a subscriber, the donor provider must maintain the LIDB record for that number to reflect appropriate conditions as reported to it by the porting service provider. The donor must outclear call records to CLEC for billing and collection from the subscriber. Until such time as Sprint’s LIDB has the software capability to recognize a ported number as CLEC’s, Sprint shall store the ported number in its LIDB at no charge and shall retain revenue for LIDB look-ups to the ported number. At such time as Sprint’s LIDB has the software capability to recognize that the ported number is CLEC’s then, if CLEC desires to store numbers on Sprint’s LIDB, the parties shall negotiate a separate LIDB database storage and look-up agreement. |
| 68.5.4. | Sprint will send a CARE transaction 2231 to notify IXC that access is now provided by a new CLEC for that number. |
| 69. | REQUIREMENTS FOR INP |
| 69.1. | Cut-Over Process |
| 69.1.1. | Sprint and CLEC shall cooperate in the process of porting numbers from one carrier to another so as to limit service outage for the ported subscriber. |
| 69.1.1.1. | For a Coordinated Cutover Environment, Sprint and CLEC will coordinate the disconnect and switch translations as close to the requested time as possible. The coordination shall be pre-specified by CLEC and agreed to by both parties and in no case shall begin more than thirty (30) minutes after the agreed upon time. |
| 69.1.1.2. |
For a Non-Coordinated Cutover Environment, the Parties will agree to a mutually satisfactory cutover time and Sprint shall schedule an update of disconnect and switch translations at the agreed upon cutover time. Such updates will be available to CLEC at Parity with Sprint’s own availability for such activity. Sprint |
95
|
and CLEC shall each provide an appropriate operations contact with whom the Parties can contact in the event manual intervention is needed to complete the cutover. In the event of manual intervention, and if Sprint is unable to resolve the issue within sixty (60) minutes, Sprint shall notify CLEC of the issue and CLEC and Sprint shall determine the plan to resolve it. |
| 69.2. | Testing. Sprint and CLEC shall cooperate in conducting CLEC’s testing to ensure interconnectivity between systems. Sprint shall inform CLEC of any system updates that may affect the CLEC network and Sprint shall, at CLEC’s request, perform tests to validate the operation of the network. Additional testing requirements may apply as specified by this Agreement. |
| 69.3. | Installation Timeframes |
| 69.3.1. | Installation Time Frames for RCF INP, where no other work is required, will be completed using Sprint’s standard interval for service installation of complex services. |
| 69.3.2. | If a subscriber elects to move its Telephone Exchange Service back to Sprint while on an INP arrangement, Sprint shall notify CLEC of the Subscriber’s termination of service with CLEC and the Subscriber’s instructions regarding its telephone number(s) at Parity with what is offered to other Sprint customers. |
| 69.4. | Call Referral Announcements. Should CLEC direct Sprint to terminate INP measures, Sprint shall allow CLEC to order a referral announcement available in that switch. |
| 69.5. | Engineering and Maintenance. Sprint and CLEC will cooperate to ensure that performance of trunking and signaling capacity is engineered and managed at levels which are at Parity with that provided by Sprint to its subscribers and to ensure effective maintenance testing through activities such as routine testing practices, network trouble isolation processes and review of operational elements for translations, routing and network fault isolation. |
| 69.6. | Operator Services and Directory Assistance |
| 69.6.1. | With respect to operator services and directory assistance associated with INP for CLEC subscribers, Sprint shall provide the following: |
| 69.6.1.1. | While INP is deployed: |
| 69.6.1.1.1. | Sprint shall allow CLEC to order provisioning of Telephone Line Number (TLN) calling cards and Billed Number Screening (BNS), in its LIDB, for ported numbers, as specified by CLEC. Sprint shall continue to allow CLEC access to its LIDB. Other LIDB provisions are specified in this Agreement. |
96
| 69.6.1.1.2. | Where Sprint has control of directory listings for NXX codes containing ported numbers. Sprint shall maintain entries for ported numbers as specified by CLEC |
| 69.6.2. | Sprint OSS shall meet all requirements specified in “Generic Operator Services Switching Requirements for Number Portability.” Issue 1.00, Final Draft, April 12, 1996. Editor-Nortel. |
| 69.7. | Number Reservation. When a subscriber ports to another service provider and has previously secured, via a tariffed offering, a reservation of line numbers from the donor provider for possible activation at some future point, these reserved but inactive numbers shall “port” along with the active numbers being ported by the subscriber in order to ensure that the end user subscriber will be permitted to expand its service using the same number range it could use if it remained with the donor provider. However, Sprint will not port vacant numbers. |
97
PART H – LOCAL NUMBER PORTABILITY
| 70. | INTRODUCTION |
| 70.1. | Upon implementation of LNP, both Parties agree to conform and provide such LNP pursuant to FCC regulations and compliance with the Industry Forum. To the extent consistent with the FCC and Industry rules as amended from time to time, the requirements for LNP shall include the following: |
| 70.1.1. | Subscribers must be able to change local service providers and retain the same telephone number(s) within the serving wire center utilizing the portability method in effect within the porting MSA, as offered by the porting carrier, and within the area of portability as defined by the FCC or state commission having jurisdiction over this Agreement. |
| 70.1.2. | The LNP network architecture shall not subject Parties to any degradation of service in any relevant measure, including transmission quality, switching and transport costs, increased call set-up time and post-dial delay. |
| 70.1.3. | Parties agree that when an NXX is defined as portable, it shall also be defined as portable in all LNP capable offices which have direct trunks to the given switch. |
| 70.1.4. | When a subscriber ports to another service provider and has previously secured a reservation of line numbers from the donor provider for possible activation at some future point, these reserved but inactive numbers shall port along with the active numbers being ported by the subscriber only in states where appropriate charges from Sprint tariffs are executed for reserved numbers. |
| 70.1.5. | NXX Availability. Not all NXXs in each CO may be available for porting. |
| 70.1.6. | LERG Reassignment. Portability for an entire NXX shall be provided by utilizing reassignment of the NXX to CLEC through the LERG. |
| 70.1.7. | Coordination of service order work outside normal business hours (8:00AM to 5:00PM) shall be at requesting Party’s expense. Premium rates will apply for service order work performed outside normal business hours, weekends, and holidays. |
| 70.1.8. | Mass Calling Events. Parties will notify each other at least seven (7) days in advance where ported numbers are utilized. Parties will only port mass calling numbers using switch translations and a choke network for call routing. Porting on mass calling numbers will be handled outside the normal porting process and comply with any applicable state or federal regulatory requirements developed for mass calling numbers. |
98
| 71. | TRANSITION FROM INP TO LNP |
| 71.1. | Existing INP Arrangements. As Sprint provisions LNP according to the industry schedule in a Wire Center/Central Office, there will be a maximum of a ninety (90) day transition from INP to LNP. At that time, the CLEC will be required to fully implement LNP according to industry standards |
| 71.2. | Once LNP is available in an area, all new portability will be LNP and INP will no longer be offered. |
| 72. | TESTING |
| 72.1. | An Interconnection Agreement (or Memorandum of Understanding, or Porting Agreement) detailing conditions for LNP must be in effect between the Parties prior to testing. |
| 72.2. | Testing and operational issues will be addressed in the implementation plans as described in Part B, §31 of the agreement. |
| 72.3. | CLEC must be NPAC certified and have met Sprint testing parameters prior to activating LNP. If LNP implementation by a CLEC/CMRS provider occurs past the FCC activation date, testing and porting will be done at CLEC’s expense. |
| 72.4. | Parties will cooperate to ensure effective maintenance testing through activities such as routine testing practices, network trouble isolation processes and review of operational elements for translations, routing and network fault isolation. |
| 72.5. | Parties shall cooperate in testing performed to ensure interconnectivity between systems. All LNP providers shall notify each connected provider of any system updates that may affect the CLEC or Sprint network. Each LNP provider shall, at each other’s request, jointly perform tests to validate the operation of the network. Additional testing requirements may apply as specified by this Agreement or in the Implementation Plan. |
| 73. | ENGINEERING AND MAINTENANCE |
| 73.1. | Each LNP provider will monitor and perform effective maintenance through testing and the performance of proactive maintenance activities such as routine testing, development of and adherence to appropriate network trouble isolation processes and periodic review of operational elements for translations, routing and network faults. |
| 73.2. | It will be the responsibility of the Parties to ensure that the network is stable and maintenance and performance levels are maintained in accordance with state commission requirements. It will be the responsibility of the Parties to perform fault isolation in their network before involving other providers. |
| 73.3. | Additional engineering and maintenance requirements shall apply as specified in this Agreement or the Implementation Plan. |
99
| 74. | E911/911 |
| 74.1. | When a subscriber ports to another service provider, the donor provider shall unlock the information in the 911/ALI database. The porting provider is responsible for updating the 911 tandem switch routing tables and 91l/ALI database to correctly route, and provide accurate information to PSAP call centers. |
| 74.2. | Prior to implementation of LNP, the Parties agree to develop, implement, and maintain efficient methods to maintain 911 database integrity when a subscriber ports to another service provider. The Parties agree that the customer shall not be dropped from the 911 database during the transition. |
| 75. | BILLING |
| 75.1. | When an IXC terminates an InterLATA or IntraLATA toll call to either party’s local exchange customer whose telephone number has been ported from one party to the other, the parties agree that the party to whom the number has been ported shall receive revenues from those IXC access charges associated with end office switching, local transport, RIC, and CCL, as appropriate, and such other applicable charges. The party from whom the number has been ported shall be entitled only to receive any entrance facility fees, access tandem fees and appropriate local transport charges as set forth in this Agreement. Such access charge payments will be adjusted to the extent that the paying party has already paid Reciprocal Compensation for the same minutes of use. When a call for which access charges are not applicable is terminated to a party’s local exchange customer whose telephone number has been ported from the other party, the parties agree that the Reciprocal compensation arrangements described in this Agreement shall apply. |
| 75.2. | Non-Payment. Customers lose the right to the ported telephone number upon non-payment of charges. Sprint will not port telephone numbers of customers who have bills in default. |
100
PART I – GENERAL BUSINESS REQUIREMENTS
| 76. | PROCEDURES |
| 76.1. | Contact with Subscribers |
| 76.1.1. | Each Party at all times shall be the primary contact and account control for all interactions with its subscribers, except as specified by that Party. Subscribers include active subscribers as well as those for whom service orders are pending. |
| 76.1.2. | Each Party shall ensure that any of its personnel who may receive subscriber inquiries, or otherwise have opportunity for subscriber contact from the other Party’s subscribers regarding the other Party’s services: (i) provide appropriate referrals to subscribers who inquire about the other Party’s services or products; (ii) do not in any way disparage or discriminate against the other Party, or its products or services; and (iii) do not provide information about its products or services during that same inquiry or subscriber contact. |
| 76.1.3. | Sprint shall not use CLEC’s request for subscriber information, order submission, or any other aspect of CLEC’s processes or services to aid Sprint’s marketing or sales efforts. |
| 76.2. | Expedite and Escalation Procedures |
| 76.2.1. | Sprint and CLEC shall develop mutually acceptable escalation and expedite procedures which may be invoked at any point in the Service Ordering, Provisioning, Maintenance, and Subscriber Usage Data transfer processes to facilitate rapid and timely resolution of disputes. In addition, Sprint and CLEC will establish intercompany contacts lists for purposes of handling subscriber and other matters which require attention/resolution outside of normal business procedures within thirty (30) days after CLEC’s request. Each party shall notify the other party of any changes to its escalation contact list as soon as practicable before such changes are effective. |
| 76.2.2. | No later than thirty (30) days after CLEC’s request Sprint shall provide CLEC with contingency plans for those cases in which normal Service Ordering, Provisioning, Maintenance, Billing, and other procedures for Sprint’s unbundled Network Elements, features, functions, and resale services are inoperable. |
| 76.3. | Subscriber of Record. Sprint shall recognize CLEC as the Subscriber of Record for all Network Elements or services for resale ordered by CLEC and shall send all notices, invoices, and information which pertain to such ordered services directly to CLEC. CLEC will provide Sprint with addresses to which Sprint shall send all such notices, invoices, and information. |
| 76.4. | Service Offerings |
101
| 76.4.1. | Sprint shall provide CLEC with access to new services, features and functions concurrent with Sprint’s notice to CLEC of such changes, if such service, feature or function is installed and available in the network or as soon thereafter as it is installed and available in the network, so that CLEC may conduct market testing. |
| 76.4.2. | Essential Services. For purposes of service restoral, Sprint shall designate a CLEC access line as an Essential Service Line (ESL) at Parity with Sprint’s treatment of its own subscribers and applicable state law or regulation, if any. |
| 76.4.3. | Blocking Services. Upon request from CLEC, employing Sprint-approved LSR documentation, Sprint shall provide blocking of 700, 900, and 976 services, or other services of similar type as may now exist or be developed in the future, and shall provide Billed Number Screening (BNS), including required LIDB updates, or equivalent service for blocking completion of bill-to-third party and collect calls, on a line, PBX, or individual service basis. Blocking shall be provided the extent (a) it is an available option for the Telecommunications Service resold by CLEC, or (b) it is technically feasible when requested by CLEC as a function of unbundled Network Elements. |
| 76.4.4. | Training Support. Sprint shall provide training, on a non-discriminatory basis, for all Sprint employees who may communicate, either by telephone or face-to-face, with CLEC subscribers. Such training shall include compliance with the branding requirements of this Agreement including without limitation provisions of forms, and unbranded “Not at Home’ notices. |
| 77. | ORDERING AND PROVISIONING |
| 77.1. | Ordering and Provisioning Parity. Sprint shall provide necessary ordering and provisioning business process support as well as those technical and systems interfaces as may be required to enable CLEC to provide the same level and quality of service for all resale services, functions, features, capabilities and unbundled Network Elements at Parity. |
| 77.2. | National Exchange Access Center (NEAC) |
| 77.2.1. | Sprint shall provide a NEAC or equivalent which shall serve as CLEC’s point of contact for all activities involved in the ordering and provisioning of Sprint’s unbundled Network Elements, features, functions, and resale services. |
| 77.2.2. |
The NEAC shall provide to CLEC a nationwide telephone number (available from 6:00 a.m. to 8:00 p.m. Eastern Standard Time, Monday through Friday, and 8:00 am through 5:00 P.M. Eastern Standard Time on Saturday) answered by competent, knowledgeable personnel and trained to answer questions and resolve problems in connection with the ordering |
102
|
and provisioning of unbundled Network Elements (except those associated with local trunking interconnection), features, functions, capabilities, and resale services. |
| 77.2.3. | Sprint shall provide, as requested by CLEC, through the NEAC, provisioning and premises visit installation support in the form of coordinated scheduling, status, and dispatch capabilities during Sprint’s standard business hours and at other times as agreed upon by the parties to meet subscriber demand. |
| 77.3. | Street Index Guide (SIG). Within thirty (30) days of CLEC’s written request, Sprint shall provide to CLEC the SIG data, or its equivalent, in an electronic format mutually agreeable to the parties. All changes and updates to the SIG shall be provided to in a mutually agreed format and timeframe. |
| 77.4. | CLASS and Custom Features. Where generally available in Sprint’s serving area, CLEC, at the tariff rate, may order the entire set of CLASS, CENTREX and Custom features and functions, or a subset of any one of such features. |
| 77.5. | Number Administration/Number Reservation |
| 77.5.1. | Sprint shall provide testing and loading of CLEC’s NXX on the same basis as Sprint provides itself or its affiliates. Further, Sprint shall provide CLEC with access to abbreviated dialing codes, and the ability to obtain telephone numbers, including vanity numbers, while a subscriber is on the phone with CLEC. When CLEC uses numbers from a Sprint NXX, Sprint shall provide the same range of number choices to CLEC, including choice of exchange number, as Sprint provides its own subscribers. Reservation and aging of Sprint NXX’s shall remain Sprint’s responsibility. |
| 77.5.2. | In conjunction with an order for service, Sprint shall accept CLEC orders for vanity numbers and blocks of numbers for use with complex services including, but not limited to, DID, CENTREX, and Hunting arrangements, as requested by CLEC. |
| 77.5.3. | For simple services number reservations and aging of Sprint’s numbers, Sprint shall provide real-time confirmation of the number reservation when the Electronic Interface has been implemented. For number reservations associated with complex services, Sprint shall provide confirmation of the number reservation within twenty-four (24) hours of CLEC’s request. Consistent with the manner in which Sprint provides numbers to its own subscribers, no telephone number assignment is guaranteed until service has been installed. |
103
| 77.6. | Service Order Process Requirements |
| 77.6.1. | Service Migrations and New Subscriber Additions |
| 77.6.1.1. | For resale services, other than for a CLEC order to convert “as is” a CLEC subscriber, Sprint shall not disconnect any subscriber service or existing features at any time during the migration of that subscriber to CLEC service without prior CLEC agreement. |
| 77.6.1.2. | For services provided through UNEs, Sprint shall recognize CLEC as an agent, in accordance with OBF developed processes, for the subscriber in coordinating the disconnection of services provided by another CLEC or Sprint. In addition, Sprint and CLEC will work cooperatively to minimize service interruptions during the conversion. |
| 77.6.1.3. | Unless otherwise directed by CLEC and when technically capable, when CLEC orders resale Telecommunications Services or UNEs all trunk or telephone numbers currently associated with existing services shall be retained without loss of feature capability and without loss of associated ancillary services including, but not limited to, Directory Assistance and 911/E911 capability. |
| 77.6.1.4. | For subscriber conversions requiring coordinated cut-over activities, on a per order basis, Sprint, to the extent resources are readily available, and CLEC will agree on a scheduled conversion time, which will be a designated time period within a designated date. |
| 77.6.1.4.1. | Any request made by CLEC to coordinate conversions after normal working hours, or on Saturday’s or Sunday’s or Sprint holidays shall be performed at CLEC’s expense. |
| 77.6.1.5. | A general Letter of Agency (LOA) initiated by CLEC or Sprint will be required to process a PLC or PIC change order. Providing the LOA, or a copy of the LOA, signed by the end user will not be required to process a PLC or PIC change ordered by CLEC or Sprint. CLEC and Sprint agree that PLC and PIC change orders will be supported with appropriate documentation and verification as required by FCC and Commission rules. In the event of a subscriber complaint of an unauthorized PLC record change where the Party that ordered such change is unable to produce appropriate documentation and verification as required by FCC and Commission rules (or, if there are no rules applicable to PLC record changes, then such rules as are applicable to changes in long distance carriers of record), such Party shall be liable to pay and shall pay all nonrecurring and/or other charges associated with reestablishing the subscriber’s local service with the original local carrier. |
| 77.6.2. |
Intercept Treatment and Transfer Service Announcements. Sprint shall provide unbranded intercept treatment and transfer of service |
104
|
announcements to CLEC’s subscribers. Sprint shall provide such treatment and transfer of service announcement in accordance with local tariffs and as provided to similarly situated Sprint subscribers for all service disconnects, suspensions, or transfers. |
| 77.6.3. | Due Date |
| 77.6.3.1. | Sprint shall supply CLEC with due date intervals to be used by CLEC personnel to determine service installation dates. |
| 77.6.3.2. | Sprint shall use best efforts to complete orders by the CLEC requested DDD within agreed upon intervals. |
| 77.6.4. | Subscriber Premises Inspections and Installations |
| 77.6.4.1. | CLEC shall perform or contract for all CLEC’s needs assessments, including equipment and installation requirements required beyond the Demarcation/NID, located at the subscriber premises. |
| 77.6.4.2. | Sprint shall provide CLEC with the ability to schedule subscriber premises installations at the same morning and evening commitment level of service offered Sprint’s own customers. The parties shall mutually agree on an interim process to provide this functionality during the implementation planning process. |
| 77.6.5. | Firm Order Confirmation (FOC) |
| 77.6.5.1. | Sprint shall provide to CLEC, a Firm Order Confirmation (FOC) for each CLEC order. The FOC shall contain the appropriate data elements as defined by the OBF standards. |
| 77.6.5.2. | For a revised FOC, Sprint shall provide standard detail as defined by the OBF standards. |
| 77.6.5.3. | Sprint shall provide to CLEC the date that service is scheduled to be installed. |
| 77.6.6. | Order Rejections |
| 77.6.6.1. | Sprint shall reject and return to CLEC any order that Sprint cannot provision, due to technical reasons, missing information, or jeopardy conditions resulting from CLEC ordering service at less than the standard order interval. When an order is rejected, Sprint shall, in its reject notification, specifically describe all of the reasons for which the order was rejected. Sprint shall reject any orders on account of the customer Desired Due Date conflicts with published Sprint order provisioning interval requirements. |
| 77.6.7. | Service Order Changes |
105
| 77.6.7.1. | In no event will Sprint change a CLEC initiated service order without a new service order directing said change. If an installation or other CLEC ordered work requires a change from the original CLEC service order in any manner, CLEC shall initiate a revised service order. If requested by CLEC, Sprint shall then provide CLEC an estimate of additional labor hours and/or materials. |
| 77.6.7.1.1. | When a service order is completed, the cost of the work performed will be reported promptly to CLEC. |
| 77.6.7.2. | If a CLEC subscriber requests a service change at the time of installation or other work being performed by Sprint on behalf of CLEC, Sprint, while at the subscriber premises, shall direct the CLEC subscriber to contact CLEC, and CLEC will initiate a new service order. |
| 77.7. | Network Testing. Sprint shall perform all its standard pre-service testing prior to the completion of the service order. |
| 77.8. | Service Suspensions/Restorations. Upon CLEC’s request through an Industry Standard, OBF, Suspend/Restore Order, or mutually agreed upon interim procedure, Sprint shall suspend or restore the functionality of any Network Element, feature, function, or resale service to which suspend/restore is applicable. Sprint shall provide restoration priority on a per network element basis in a manner that conforms with any applicable regulatory Rules and Regulations or government requirements. |
| 77.9. | Order Completion Notification. Upon completion of the requests submitted by CLEC, Sprint shall provide to CLEC a completion notification in an industry standard, OBF, or in a mutually agreed format. The completion notification shall include detail of the work performed, to the extent this is defined within OBF guidelines, and in an interim method until such standards are defined. |
| 77.10. | Specific Unbundling Requirements. CLEC may order and Sprint shall provision unbundled Network Elements. However, it is CLEC’s responsibility to combine the individual network elements should it desire to do so. |
| 77.11. | Systems Interfaces and Information Exchanges |
| 77.11.1. | General Requirements |
| 77.11.1.1. | Sprint shall provide to CLEC Electronic Interface(s) for transferring and receiving information and executing transactions for all business functions directly or indirectly related to Service Ordering and Provisioning of Network Elements, features, functions and Telecommunications Services, to the extent available. |
| 77.11.1.2. | Until the Electronic Interface is available, Sprint agrees that the |
106
|
NEAC or similar function will accept CLEC orders. Orders will be transmitted to the NEAC via an interface or method agreed upon by CLEC and Sprint. |
| 77.11.2. | For any CLEC subscriber Sprint shall provide, subject to applicable rules, orders, and decisions, CLEC with access CPNI without requiring CLEC to produce a signed LOA, based on CLEC’s blanket representation that subscriber has authorized CLEC to obtain such CPNI. |
| 77.11.2.1. | The preordering Electronic Interface includes the provisioning of CPNI from Sprint to CLEC. The Parties agree to execute a LOA agreement with the Sprint end user prior to requesting CPNI for that Sprint end user, and to request end user CPNI only when the end user has specifically given permission to receive CPNI. The Parties agree that they will conform to FCC and/or state regulations regarding the provisioning of CPNI between the parties, and regarding the use of that information by the requesting party. |
| 77.11.2.2. | The requesting Party will document end user permission obtained to receive CPNI, whether or not the end user has agreed to change local service providers. For end users changing service from one party to the other, specific end user LOAs may be requested by the Party receiving CPNI requests to investigate possible slamming incidents, and for other reasons agreed to by the Parties. |
| 77.11.2.3. | The receiving Party may also request documentation of an LOA if CPNI is requested and a subsequent service order for the change of local service is not received. On a schedule to be determined by Sprint, Sprint will perform a comparison of requests for CPNI to service orders received for the change of Local Service to CLEC. Sprint will produce a report of unmatched requests for CPNI, and may require an LOA from CLEC for each unmatched request. CLEC agrees to provide evidence of end user permission for receipt of CPNI for all end users in the request by Sprint within three (3) business days of receipt of a request from Sprint. Should Sprint determine that there has been a substantial percentage of unmatched LOA requests, Sprint reserves the right to immediately disconnect the preordering Electronic Interface. |
| 77.11.2.4. | If CLEC is not able to provide the LOA for ninety-five percent (95%) of the end users requested by Sprint, or if Sprint determines that an LOA is inadequate, CLEC will be considered in breach of the agreement. CLEC can cure the breach by submitting to Sprint evidence of an LOA for each inadequate or omitted LOA within three (3) business days of notification of the breach. |
107
| 77.11.2.5. | Should CLEC not be able to cure the breach in the timeframe noted above. Sprint will discontinue processing new service orders until, in Sprint’s determination, CLEC has corrected the problem that caused the breach. |
| 77.11.2.6. | Sprint will resume processing new service orders upon Sprint’s timely review and acceptance of evidence provided by CLEC to correct the problem that caused the breach. |
| 77.11.2.7. | If CLEC and Sprint do not agree that CLEC requested CPNI for a specific end user, or that Sprint has erred in not accepting proof of an LOA, the Parties may immediately request dispute resolution in accordance with Part B. Sprint will not disconnect the preordering Electronic Interface during the Alternate Dispute Resolution process. |
| 77.11.2.8. | When available per Electronic Interface Implementation Plan, Sprint shall provide to CLEC Electronic Interface to Sprint information systems to allow CLEC to assign telephone number(s) (if the subscriber does not already have a telephone number or requests a change of telephone number) at Parity. |
| 77.11.2.9. | When available per Electronic Interface Implementation Plan, Sprint shall provide to CLEC an Electronic Interface to schedule dispatch and installation appointments at Parity. |
| 77.11.2.10. | When available per Electronic Interface Implementation Plan, Sprint shall provide to CLEC an Electronic Interface to Sprint subscriber information systems which will allow CLEC to determine if a service call is needed to install the line or service at Parity. |
| 77.11.2.11. | When available per Electronic Interface Implementation Plan, Sprint shall provide to CLEC an Electronic Interface to Sprint information systems which will allow CLEC to provide service availability dates at Parity. |
| 77.11.2.12. | When available per Electronic Interface Implementation Plan, Sprint shall provide to CLEC an Electronic Interface which transmits status information on service orders at Parity. Until an Electronic Interface is available, Sprint agrees that Sprint will provide proactive status on service orders at the following critical intervals: acknowledgment, firm order confirmation, and completion according to interim procedures to be mutually developed. |
| 77.12. | Standards |
| 77.12.1. |
General Requirements. CLEC and Sprint shall agree upon the appropriate ordering and provisioning codes to be used for UNEs. These codes shall apply to all aspects of the unbundling of that element and shall |
108
|
be known as data elements as defined by the Telecommunications Industry Forum Electronic Data Interchange Service Order Subcommittee (TCIF EDI-SOSC). |
| 78. | BILLING |
| 78.1. | Sprint shall comply with various industry, OBF, and other standards referred to throughout this Agreement. Sprint will review any changes to industry standards and implement the changes within the industry-defined window. Sprint will notify CLEC of any deviations to the standards. |
| 78.2. | Sprint shall bill CLEC for each service supplied by Sprint to CLEC pursuant to this Agreement at the rates set forth in this Agreement. |
| 78.3. | Sprint shall provide to CLEC a single point of contact for interconnection at the National Access Service Center (NASC), and Network Elements and resale at Sprint’s NEAC, to handle any Connectivity Billing questions or problems that may arise during the implementation and performance of the terms and conditions of this Agreement. |
| 78.4. | Sprint shall provide a single point of contact for handling of any data exchange questions or problems that may arise during the implementation and performance of the terms and conditions of this Agreement. |
| 78.5. | Subject to the terms of this Agreement, CLEC shall pay Sprint within thirty (30) days from the Bill Date. If the payment due date is a Saturday, Sunday or has been designated a bank holiday payment shall be made the next business day. |
109
| 78.6. | Billed amounts for which written, itemized disputes or claims have been filed shall be handled in accordance with the procedures set forth in Part B, Section 23 of this Agreement. |
| 78.7. | Sprint will assess late payment charges to CLEC in accordance with Part B, §6 of this Agreement. |
| 78.8. | Sprint shall credit CLEC for incorrect Connectivity Billing charges including without limitation: overcharges, services ordered or requested but not delivered, interrupted services, services of poor quality and installation problems if caused by Sprint. Such reimbursements shall be set forth in the appropriate section of the Connectivity Bill pursuant to CABS, or SECAB standards. |
| 78.9. | Where Parties have established interconnection, Sprint and the CLEC agree to conform to MECAB and MECOD guidelines. They will exchange Billing Account Reference and Bill Account Cross Reference information and will coordinate Initial Billing Company/Subsequent Billing Company billing cycles. Sprint and CLEC will exchange the appropriate records to bill exchange access charges to the IXC. Sprint and CLEC agree to capture EMI records for inward terminating and outward originating calls and send them to the other, as appropriate, in daily or other agreed upon interval, via and agreed upon media (e.g.: Connect Direct or cartridge). |
| 78.10. | Revenue Protection. Sprint shall make available to CLEC, at Parity with what Sprint provides to itself, its Affiliates and other local telecommunications CLECs, all present and future fraud prevention or revenue protection features, including prevention, detection, or control functionality embedded within any of the Network Elements. These features include, but are not limited to screening codes, information digits assigned such as information digits ‘29’ and ‘70’ which indicate prison and Public Telephone Access Line pay phone originating line types respectively, call blocking of domestic, international, 800, 888, 900, NPA- 976, 700, 500 and specific line numbers, and the capability to require end-user entry of an authorization code for dial tone. Sprint shall, when technically capable and consistent with the implementation schedule for Operations Support Systems (OSS), additionally provide partitioned access to fraud prevention, detection and control functionality within pertinent OSS. |
| 79. | PROVISION OF SUBSCRIBER USAGE DATA |
| 79.1. |
This Section 79 sets forth the terms and conditions for Sprint’s provision of Recorded Usage Data (as defined in this Part) to CLEC and for information exchange regarding long distance billing. The parties agree to record call information for interconnection in accordance with this Section. To the extent technically feasible, each party shall record all call detail information associated with completed calls originated by or terminated to the other Party’s local exchange subscriber. Sprint shall record for CLEC the messages that Sprint records for and bills to its end users. These records shall be provided at a party’s request and shall be formatted pursuant to Telcordia’s EMI standards and the |
110
|
terms and conditions of this Agreement. These records shall be transmitted to the other party on non-holiday business days in EMI format via CDN, or provided __ a cartridge. Sprint and CLEC agree that they shall retain, at each party’s sole expense, copies of all EMI records transmitted to the other party for at least forty five (45) calendar days after transmission to the other party. |
| 79.2. | General Procedures |
| 79.2.1. | Sprint shall comply with various industry and OBF standards referred to throughout this Agreement. |
| 79.2.2. | Sprint shall comply with OBF standards when recording and transmitting Usage Data. |
| 79.2.3. | Sprint shall record all usage originating from CLEC subscribers using resold services ordered by CLEC, where Sprint records those same services for Sprint subscribers. Recorded Usage Data includes, but is not limited to, the following categories of information: |
| 79.2.3.1. | Use of CLASS/LASS/Custom Features that Sprint records and bills for its subscribers on a per usage basis. |
| 79.2.3.2. | Calls to Information Providers (IP) reached via Sprint facilities will be provided in accordance with §79.2.7 |
| 79.2.3.3. | Calls to Directory Assistance where Sprint provides such service to a CLEC subscriber. |
| 79.2.3.4. | Calls completed via Sprint-provided Operator Services where Sprint provides such service to CLEC’s local service subscriber and where Sprint records such usage for its subscribers using Industry Standard Telcordia EMI billing records. |
| 79.2.3.5. | For Sprint-provided Centrex Service, station level detail. |
| 79.2.4. | Retention of Records. Sprint shall maintain a machine-readable back-up copy of the message detail provided to CLEC for a minimum of forty-five (45) calendar days. During the forty-five (45) day period. Sprint shall provide any data back-up to CLEC upon the request of CLEC. If the forty-five (45) day has expired, Sprint may provide the data back-up at CLEC’s expense. |
| 79.2.5. | Sprint shall provide to CLEC Recorded Usage Data for CLEC subscribers. Sprint shall not submit other CLEC local usage data as part of the CLEC Recorded Usage Data. |
111
| 79.2.6. | Sprint shall not bill directly to CLEC subscribers any recurring or non recurring charges for CLEC’s services to the subscriber except where explicitly permitted to do so within a written agreement between Sprint and CLEC. |
| 79.2.7. | Sprint will record 976/N11 calls and transmit them to the IP for billing. Sprint will not bill these calls to either the CLEC or the CLEC’s end user. |
| 79.2.8. | Sprint shall provide Recorded Usage Data to CLEC billing locations as agreed to by the Parties. |
| 79.2.9. | Sprint shall provide a single point of contact to respond to CLEC call usage, data error, and record transmission inquiries. |
| 79.2.10. | Sprint shall provide CLEC with a single point of contact and remote identifiers (IDs) for each sending location. |
| 79.2.11. | CLEC shall provide a single point of contact responsible for receiving usage transmitted by Sprint and receiving usage tapes from a courier service in the event of a facility outage. |
| 79.2.12. | Sprint shall bill and CLEC shall pay the charges for Recorded Usage Data. Billing and payment shall be in accordance with the applicable terms and conditions set forth herein. |
| 79.3. | Charges |
| 79.3.1. | Access services, including revenues associated therewith, provided in connection with the resale of services hereunder shall be the responsibility of Sprint and Sprint shall directly bill and receive payment on its own behalf from an IXC for access related to interexchange calls generated by resold or rebranded customers. |
| 79.3.2. | Sprint will be responsible for returning EMI records to IXCs with the proper EMI Return Code along with the Operating Company Number (OCN) of the associated ANI, (i.e., Billing Number). |
| 79.3.3. | Sprint will deliver a monthly statement for wholesale services in the medium (e.g.: NDM, paper, cartridge or CD-ROM) requested by CLEC as follows: |
| 79.3.3.1. | Invoices will be provided in a standard Carrier Access Billing format or other such format as Sprint may determine; |
| 79.3.3.2. | Where local usage charges apply and message detail is created to support available services, the originating local usage at the call detail level in standard EMI industry format will be exchanged daily or at other mutually agreed upon intervals, and CLEC will pay Sprint for providing such call detail; |
112
| 79.3.3.3. | The Parties will work cooperatively to exchange information to facilitate the billing of in and out collect and inter/intra-region alternately billed messages; |
| 79.3.3.4. | Sprint agrees to provide information on the end-user’s selection of special features where Sprint maintains such information (e.g billing method, special language) when CLEC places the order for service; |
| 79.3.3.5. | Monthly recurring charges for Telecommunications Services sold pursuant to this Agreement shall be billed monthly in advance. |
| 79.3.3.6. | Sprint shall bill for message provisioning and, if applicable data tape charges, related to the provision of usage records. Sprint shall also bill CLEC for additional copies of the monthly invoice. |
| 79.3.4. | For billing purposes, and except as otherwise specifically agreed to in writing, the Telecommunications Services provided hereunder are furnished for a minimum term of one month. Each month is presumed to have thirty (30) days. |
| 79.4. | Central Clearinghouse & Settlement |
| 79.4.1. | Sprint and CLEC shall agree upon Clearinghouse and Incollect/Outcollect procedures. |
| 79.4.2. | Sprint shall settle with CLEC for both intra-region and inter-region billing exchanges of calling card, bill-to-third party, and collect calls under separately negotiated settlement arrangements. |
| 79.5. | Lost Data |
| 79.5.1. | Loss of Recorded Usage Data. CLEC Recorded Usage Data determined to have been lost, damaged or destroyed as a result of an error or omission by Sprint in its performance of the recording function shall be recovered by Sprint at no charge to CLEC. In the event the data cannot be recovered by Sprint, Sprint shall estimate the messages and associated revenue, with assistance from CLEC, based upon the method described below. This method shall be applied on a consistent basis, subject to modifications agreed to by Sprint and CLEC. This estimate shall be used to adjust amounts CLEC owes Sprint for services Sprint provides in conjunction with the provision of Recorded Usage Data. |
113
| 79.5.2. | Partial Loss. Sprint shall review its daily controls to determine if data has been lost. When there has been a partial loss, actual message and minute volumes shall be reported, if possible through recovery as discussed in §79.5.1 above. Where actual data are not available, a full day shall be estimated for the recording entity, as outlined in the following paragraphs. The amount of the partial loss is then determined by subtracting the data actually recorded for such day from the estimated total for such day. |
| 79.5.3. | Complete Loss. When Sprint is unable to recover data as discussed in §79.5.1 above estimated message and minute volumes for each loss consisting of an entire AMA tape or entire data volume due to its loss prior to or during processing, lost after receipt, degaussed before processing, receipt of a blank or unreadable tape, or lost for other causes, shall be reported. |
| 79.5.4. | Estimated Volumes. From message and minute volume reports for the entity experiencing the loss, Sprint shall secure message/minute counts for the four (4) corresponding days of the weeks preceding that in which the loss occurred and compute an average of these volumes. Sprint shall apply the appropriate average revenue per message (“arpm”) agreed to by CLEC and Sprint to the estimated message volume for messages for which usage charges apply to the subscriber to arrive at the estimated lost revenue. |
| 79.5.5. | If the day of loss is not a holiday but one (1) (or more) of the preceding corresponding days is a holiday, use additional preceding weeks in order to procure volumes for two (2) non-holidays in the previous two (2) weeks that correspond to the day of the week that is the day of the loss. |
| 79.5.6. | If the loss occurs on a weekday that is a holiday (except Christmas and Mother’s day), Sprint shall use volumes from the two (2) preceding Sundays. |
| 79.5.7. | If the loss occurs on Mother’s day or Christmas day, Sprint shall use volumes from that day in the preceding year multiplied by a growth factor derived from an average of CLEC’s most recent three (3) month message volume growth. If a previous year’s message volumes are not available, a settlement shall be negotiated. |
| 79.6. | Testing, Changes and Controls |
| 79.6.1. | The Recorded Usage Data, EMI format, content, and transmission process shall be tested as agreed upon by CLEC and Sprint. |
| 79.6.2. | Control procedures for all usage transferred between Sprint and CLEC shall be available for periodic review. This review may be included as part of an Audit of Sprint by CLEC or as part of the normal production interface management function. Breakdowns which impact the flow of usage between Sprint and CLEC must be identified and jointly resolved as they occur. The resolution may include changes to control procedures, so similar problems would be avoided in the future. Any changes to control procedures would need to be mutually agreed upon by CLEC and Sprint. |
114
| 79.6.3. | Sprint Software Changes |
| 79.6.3.1. | When Sprint plans to introduce any software changes which impact the format or content structure of the usage data feed to CLEC, designated Sprint personnel shall notify CLEC no less than ninety (90) calendar days before such changes are implemented. |
| 79.6.3.2. | Sprint shall communicate the projected changes to CLEC’s single point of contact so that potential impacts on CLEC processing can be determined. |
| 79.6.3.3. | CLEC personnel shall review the impact of the change on the entire control structure. CLEC shall negotiate any perceived problems with Sprint and shall arrange to have the data tested utilizing the modified software if required. |
| 79.6.3.4. | If it is necessary for Sprint to request changes in the schedule, content or format of usage data transmitted to CLEC, Sprint shall notify CLEC. |
| 79.6.4. | CLEC Requested Changes: |
| 79.6.4.1. | CLEC may submit a purchase order to negotiate and pay for changes in the content and format of the usage data transmitted by Sprint. |
| 79.6.4.2. | When the negotiated changes are to be implemented, CLEC and/or Sprint shall arrange for testing of the modified data. |
| 79.7. | Information Exchange and Interfaces |
| 79.7.1. | Product/Service Specific. Sprint shall provide a Telcordia standard 42-50-01 miscellaneous charge record to support the Special Features Star Services if these features are part of Sprint’s offering and are provided for Sprint’s subscribers on a per usage basis. |
| 79.7.2. | Rejected Recorded Usage Data |
| 79.7.2.1. | Upon agreement between CLEC and Sprint, messages that cannot be rated and/or billed by CLEC may be returned to Sprint via CDN or other medium as agreed by the Parties. Returned messages shall be sent directly to Sprint in their original EMI format utilizing standard EMI return codes. |
| 79.7.2.2. | Sprint may correct and resubmit to CLEC any messages returned to Sprint. Sprint will not be liable for any records determined by Sprint to be billable to a CLEC end user. CLEC will not return a message that has been corrected and resubmitted by Sprint. Sprint will only assume liability for errors and unguideables caused by Sprint. |
115
| 80. | GENERAL NETWORK REQUIREMENTS |
| 80.1. | Sprint shall provide repair, maintenance and testing for all resold Telecommunications Services and such UNEs that Sprint is able to test, in accordance with the terms and conditions of this Agreement. |
| 80.2 | During the term of this Agreement, Sprint shall provide necessary maintenance business process support as well as those technical and systems interfaces at Parity. Sprint shall provide CLEC with maintenance support at Parity. |
| 80.3. | Sprint shall provide on a regional basis, a point of contact for CLEC to report vital telephone maintenance issues and trouble reports twenty four (24) hours and seven (7) days a week. |
| 80.4. | Sprint shall provide CLEC maintenance dispatch personnel on the same schedule that it provides its own subscribers. |
| 80.5. | Sprint shall cooperate with CLEC to meet maintenance standards for all Telecommunications Services and unbundled network elements ordered under this Agreement. Such maintenance standards shall include, without limitation, standards for testing, network management, call gapping, and notification of upgrades as they become available. |
| 80.6. | All Sprint employees or contractors who perform repair service for CLEC subscribers shall follow Sprint standard procedures in all their communications with CLEC subscribers. These procedures and protocols shall ensure that: |
| 80.6.1. | Sprint employees or contractors shall perform repair service that is equal in quality to that provided to Sprint subscribers; and |
| 80.6.2. | Trouble calls from CLEC shall receive response time priority that is equal to that of Sprint subscribers and shall be handled on a “first come first served” basis regardless of whether the subscriber is a CLEC subscriber or a Sprint subscriber. |
| 80.7. | Sprint shall provide CLEC with scheduled maintenance for resold lines, including, without limitation, required and recommended maintenance intervals and procedures, for all Telecommunications Services and network elements provided to CLEC under this Agreement equal in quality to that currently provided by Sprint in the maintenance of its own network. CLEC shall perform its own testing for UNEs. |
| 80.8. | Sprint shall give maximum advanced notice to CLEC of all non-scheduled maintenance or other planned network activities to be performed by Sprint on any network element, including any hardware, equipment, software, or system, providing service functionality of which CLEC has advised Sprint may potentially impact CLEC subscribers. |
| 80.9. | Notice of Network Event. Each party has the duty to alert the other of any network events that can result or have resulted in service interruption, blocked calls, or negative changes in network performance. |
116
| 80.10. | On all misdirected calls from CLEC subscribers requesting repair, Sprint shall provide such CLEC subscriber with the correct CLEC repair telephone number as such number is provided to Sprint by CLEC. Once the Electronic Interface is established between Sprint and CLEC, Sprint agrees that CLEC may report troubles directly to a single Sprint repair/maintenance center for both residential and small business subscribers, unless otherwise agreed to by CLEC. |
| 80.11. | Upon establishment of an Electronic Interface, Sprint shall notify CLEC via such electronic interface upon completion of trouble report. The report shall not be considered closed until such notification is made. CLEC will contact its subscriber to determine if repairs were completed and confirm the trouble no longer exists. |
| 80.12. | Sprint shall perform all testing for resold Telecommunications Services. |
| 80.13. | Sprint shall provide test results to CLEC, if appropriate, for trouble clearance. In all instances, Sprint shall provide CLEC with the disposition of the trouble. |
| 80.14. | If Sprint initiates trouble handling procedures, it will bear all costs associated with that activity. If CLEC requests the trouble dispatch, and either there is no trouble found, or the trouble is determined to be beyond the end user demarcation point, then CLEC will bear the cost. |
| 80.15. | When a CLEC customer reports trouble to CLEC, and after testing CLEC’s network and the customer’s wiring, CLEC shall submit a Trouble ticket to Sprint. In the event that Sprint responds that the trouble is not in Sprint’s facility, and CLEC subsequently dispatches a technician that reveals information that allows Sprint and CLEC to determine that the trouble is on Sprint’s network, then CLEC will charge Sprint the trouble isolation charge as set forth in Table 1. |
| 81. | MISCELLANEOUS SERVICES AND FUNCTIONS |
| 81.1. | General |
| 81.1.1. | To the extent that Sprint does not provide the services described in this Section 81 to itself, Sprint will use reasonable efforts to facilitate the acquisition of such services for or by CLEC through the existing service provider. CLEC must contract directly with the service provider for such services. |
| 81.1.2. | Basic 911 and E911 General Requirements |
| 81.1.2.1. | Basic 911 and E911 provides a caller access to the appropriate emergency service bureau by dialing a 3-digit universal telephone number (911). Basic 911 and E911 access from Local Switching shall be provided to CLEC in accordance with the following: |
| 81.1.2.2. | E911 shall provide additional routing flexibility for 911 calls. E911 shall use subscriber data, contained in the ALI/DMS, to determine to which PSAP to route the call. |
117
| 81.1.2.3. | Basic 911 and E911 functions provided to CLEC shall be __ Parity with the support and services that Sprint provides to its subscribers for such similar functionality. |
| 81.1.2.4. | Basic 911 and E911 access when CLEC purchases Local Switching shall be provided to CLEC in accordance with the following: |
| 81.1.2.4.1. | Sprint shall conform to all state regulations concerning emergency services. |
| 81.1.2.4.2. | For E911, Sprint shall use its service order process to update and maintain subscriber information in the ALI/DMS. Through this process, Sprint shall provide and validate CLEC subscriber information resident or entered into the ALI/DMS. |
| 81.1.2.4.3. | Sprint shall provide for overflow 911 traffic to be routed to Sprint Operator Services or, at CLEC’s discretion, directly to CLEC operator services. |
| 81.1.3. | Basic 911 and E911 access from the CLEC local switch shall be provided to CLEC in accordance with the following: |
| 81.1.3.1. | If required by CLEC, Sprint, at CLEC’s sole expense, shall interconnect direct trunks from the CLEC network to the E911 PSAP, or the E911 Tandems as designated by CLEC. Such trunks may alternatively be provided by CLEC. |
| 81.1.3.2. | In government jurisdictions where Sprint has obligations under existing agreements as the primary provider of the 911 System to the county (Host SPRINT), CLEC shall participate in the provision of the 911 System as follows: |
| 81.1.3.2.1. | Each party shall be responsible for those portions of the 911 System for which it has control, including any necessary maintenance to each party’s portion of the 911 System. |
| 81.1.3.2.2. | Host SPRINT shall be responsible for maintaining the E-911 database. Sprint shall be responsible for maintaining the E-911 routing database. |
| 81.1.4. | If a third party is the primary service provider to a government agency, CLEC shall negotiate separately with such third party with regard to the provision of 911 service to the agency. All relations between such third party and CLEC are totally separate from this Agreement and Sprint makes no representations on behalf or the third party. |
118
| 81.1.5. | If CLEC or its Affiliate is the primary service provider to a government agency, CLEC and Sprint shall negotiate the specific provisions necessary for providing 911 service to the agency and shall include such provisions in an amendment to this Agreement. |
| 81.1.6. | Interconnection and database access shall be priced as specified in Part C. |
| 81.1.7. | Sprint shall comply with established, competitively neutral intervals for installation of facilities, including any collocation facilities, diversity requirements, etc. |
| 81.1.8. | In a resale situation, where it may be appropriate for Sprint to update the ALI database, Sprint shall update such database with CLEC data in an interval at Parity with that experienced by Sprint subscribers. |
| 81.1.9. | Sprint shall transmit to CLEC daily all changes, alterations, modifications, and updates to the emergency public agency telephone numbers linked to all NPA NXX’s. This transmission shall be electronic and be a separate feed from the subscriber listing feed. |
| 81.1.10. | Sprint shall provide to CLEC the necessary UNEs for CLEC to provide E911/911 services to government agencies. If such elements are not available from Sprint, Sprint shall offer E911/911 service for resale by CLEC to government agencies. |
| 81.1.11. | The following are Basic 911 and E911 Database Requirements |
| 81.1.11.1. | The ALI database shall be managed by Sprint, but is the property of Sprint and CLEC for those records provided by CLEC. |
| 81.1.11.2. | To the extent allowed by the governmental agency, and where available, copies of the SIG shall be provided within three business days from the time requested and provided on diskette, or in a format suitable for use with desktop computers. |
| 81.1.11.3. | CLEC shall be solely responsible for providing CLEC database records to Sprint for inclusion in Sprint’s ALI database on a timely basis. |
| 81.1.11.4. | Sprint and CLEC shall arrange for the automated input and periodic updating of the E911 database information related to CLEC end users. Sprint shall work cooperatively with CLEC to ensure the accuracy of the data transfer by verifying it against the SIG. Sprint shall accept electronically transmitted files that conform to NENA Version #2 format. |
119
| 81.1.11.5. | CLEC shall assign an E911 database coordinator charged with the responsibility of forwarding CLEC end user ALI record information to Sprint or via a third-party entity, charged with the responsibility of ALI record transfer. CLEC assumes all responsibility for the accuracy of the data that CLEC provides to Sprint. |
| 81.1.11.6. | CLEC shall provide information on new subscribers to Sprint within one (1) business day of the order completion. Sprint shall update the database within two (2) business days of receiving the data from CLEC. If Sprint detects an error in the CLEC provided data, the data shall be returned to CLEC within two (2) business days from when it was provided to Sprint. CLEC shall respond to requests from Sprint to make corrections to database record errors by uploading corrected records within two (2) business days. Manual entry shall be allowed only in the event that the system is not functioning properly. |
| 81.1.11.7. | Sprint agrees to treat all data on CLEC subscribers provided under this Agreement as confidential and to use data on CLEC subscribers only for the purpose of providing E911 services. |
| 81.1.11.8. | Sprint shall adopt use of a CLEC Code (NENA standard five-character field) on all ALI records received from CLEC. The CLEC Code will be used to identify the CLEC of record in LNP/INP configurations. |
| 81.1.11.9. | Sprint shall identify which ALI databases cover which states, counties or parts thereof, and identify and communicate a Point of Contact for each. |
| 81.1.12. | The following are basic 911 and E911 Network Requirements |
| 81.1.12.1. | Sprint, at CLEC’s option, shall provide a minimum of two (2) E911 trunks per 911 switching entity, or that quantity which will maintain P.01 transmission grade of service, whichever is the higher grade of service. Where applicable these trunks will be dedicated to routing 911 calls from CLEC’s switch to a Sprint selective router. |
| 81.1.12.2. | Sprint shall provide the selective routing of E911 calls received from CLEC’s switching office. This includes the ability to receive the ANI of CLEC’s subscriber, selectively route the call to the appropriate PSAP, and forward the subscriber’s ANI to the PSAP. Sprint shall provide CLEC with the appropriate CLLI codes and specifications regarding the Tandem serving area associated addresses and meet-points in the network. |
120
| 81.1.12.3. | CLEC shall ensure that its switch provides an eight-digit ANI consisting of an information digit and the seven-digit exchange code. CLEC shall also ensure that its switch provides the line number of the calling station. Where applicable, CLEC shall send a ten-digit ANI to Sprint when there is an ANI failure the CLEC shall send the Central Office Trunk Group number in the Emergency Service Central Office (ESCO) format. |
| 81.1.12.4. | Each ALI discrepancy report shall be jointly researched by Sprint and CLEC. Corrective action shall be taken immediately by the responsible party. |
| 81.1.12.5. | Where Sprint controls the 911 network, Sprint should provide CLEC with a detailed written description of, but not limited to, the following information: |
| 81.1.12.5.1. | Geographic boundaries of the government entities, PSAPs, and exchanges as necessary. |
| 81.1.12.5.2. | LECs rate centers/exchanges, where “Rate Center” is defined as a geographically specified area used for determining mileage dependent rates in the Public Switched Telephone Network. |
| 81.1.12.5.3. | Technical specifications for network interface, Technical specifications for database loading and maintenance. |
| 81.1.12.5.4. | Sprint shall identify special routing arrangements to complete overflow. |
| 81.1.12.5.5. | Sprint shall begin restoration of E911 and/or E911 trunking facilities immediately upon notification of failure or outage. Sprint must provide priority restoration of trunks or networks outages on the same terms/conditions it provides itself and without the imposition of Telecommunications Service Priority (TSP). |
| 81.1.12.5.6. | Repair service shall begin immediately upon receipt of a report of a malfunction. Repair service includes testing and diagnostic service from a remote location, dispatch of or in-person visit(s) of personnel. Technicians will be dispatched without delay. |
| 81.1.12.6. | Sprint shall identify any special operator-assisted calling requirements to support 911. |
121
| 81.1.12.7. | Trunking shall be arranged to minimize the likelihood of central office isolation due to cable cuts or other equipment failures. There will be an alternate means of transmitting a 911 call to a PSAP in the event of failures. |
| 81.1.12.8. | Circuits shall have interoffice, loop and CLEC system diversity when such diversity can be achieved using existing facilities. Circuits will be divided as equally as possible across available CLEC systems. Diversity will be maintained or upgraded to utilize the highest level of diversity available in the network. |
| 81.1.12.9. | All 911 trunks must be capable of transmitting and receiving Baudot code or ASII necessary to support the use of Telecommunications Devices for the Deaf (TTY/TDDs). |
| 81.1.13. | Basic 911 and E911 Additional Requirements |
| 81.1.13.1. | All CLEC lines that have been ported via INP shall reach the correct PSAP when 911 is dialed. Sprint shall send both the ported number and the CLEC number (if both are received from CLEC). The PSAP attendant shall see both numbers where the PSAP is using a standard ALI display screen and the PSAP extracts both numbers from the data that is sent. |
| 81.1.13.2. | Sprint shall work with the appropriate government agency to provide CLEC the ten-digit POTS number of each PSAP which sub-tends each Sprint selective router/911 Tandem to which CLEC is interconnected. |
| 81.1.13.3. | Sprint shall notify CLEC 48 hours in advance of any scheduled testing or maintenance affecting CLEC 911 service, and provide notification as soon as possible of any unscheduled outage affecting CLEC 911 service. |
| 81.1.13.4. | CLEC shall be responsible for reporting all errors, defects and malfunctions to Sprint. Sprint shall provide CLEC with the point of contact for reporting errors, defects, and malfunctions in the service and shall also provide escalation contacts. |
| 81.1.13.5. | CLEC may enter into subcontracts with third parties, including CLEC Affiliates, for the performance of any of CLEC’s duties and obligations stated herein. |
| 81.1.13.6. | Sprint shall provide sufficient planning information regarding anticipated moves to SS7 signaling, for 911 services, for the next twelve (12) months. |
| 81.1.13.7. | Sprint shall provide notification of any impacts to the 911 services provided by Sprint to CLEC resulting from of any pending Tandem moves, NPA splits, or scheduled maintenance outages, with enough time to react. |
122
| 81.1.13.8. | Sprint shall identify process for handling of reverse ALI inquiries by public safety entities. |
| 81.1.13.9. | Sprint shall establish a process for the management of NPA splits by populating the ALI database with the appropriate new NPA codes. |
| 81.2. | Directory Listings Service Requests |
| 81.2.1. | These requirements pertain to Sprint’s Listings Service Request process that enables CLEC to (a) submit CLEC subscriber information for inclusion in Directory Listings databases; (b) submit CLEC subscriber information for inclusion in published directories; and (c) provide CLEC subscriber delivery address information to enable Sprint to fulfill directory distribution obligations. |
| 81.2.2. | When implemented by the Parties, Sprint shall accept orders on a real-time basis via electronic interface in accordance with OBF Directory Service Request standards within three (3) months of the effective date of this Agreement. In the interim, Sprint shall create a standard format and order process by which CLEC can place an order with a single point of contact within Sprint. |
| 81.2.3. | Sprint will provide to CLEC the following Directory Listing Migration Options, valid under all access methods, including but not limited to, Resale, UNEs and Facilities-Based: |
| 81.2.3.1. | Migrate with no Changes. Retain all white page listings for the subscriber in both DA and DL. Transfer ownership and billing for white page listings to CLEC. |
| 81.2.3.2. | Migrate with Additions. Retain all white page listings for the subscriber in DL. Incorporate the specified additional listings order. Transfer ownership and billing for the white page listings to CLEC. |
| 81.2.3.3. | Migrate with Deletions. Retain all white page listings for the subscriber in DL. Delete the specified listings from the listing order. Transfer ownership and billing for the white page listings to CLEC. |
| 81.2.3.4. | To ensure accurate order processing, Sprint or its directory publisher shall provide to CLEC the following information, with updates promptly upon changes: |
| 81.2.3.4.1. | A matrix of NXX to central office; |
| 81.2.3.4.2. | Geographical maps if available of Sprint service area; |
123
| 81.2.3.4.3. | A description of calling areas covered by each directory, including but not limited to maps of calling areas and matrices depicting calling privileges within and between calling areas: |
| 81.2.3.4.4. | Listing format rules, |
| 81.2.3.4.5. | Standard abbreviations acceptable for use in listings and addresses; |
| 81.2.3.4.6. | Titles and designations; and |
| 81.2.3.4.7. | A list of all available directories and their Business Office close dates |
| 81.2.4. | Based on changes submitted by CLEC, Sprint shall update and maintain directory listings data for CLEC subscribers who: |
| 81.2.4.1. | Disconnect Service; |
| 81.2.4.2. | Change CLEC; |
| 81.2.4.3. | Install Service; |
| 81.2.4.4. | Change any service which affects DA information; |
| 81.2.4.5. | Specify Non-Solicitation; and |
| 81.2.4.6. | Are Non-Published, Non-Listed, or Listed. |
| 81.2.5. | Sprint shall not charge for storage of CLEC subscriber information in the DL systems. |
| 81.2.6. | CLEC shall not charge for storage of Sprint subscriber information in the DL systems. |
| 81.3. | Directory Listings General Requirements. CLEC acknowledges that many directory functions including but not limited to yellow page listings, enhanced white page listings, information pages, directory proofing, and directory distribution are not performed by Sprint but rather are performed by and are under the control of the directory publisher. CLEC acknowledges that for a CLEC subscriber’s name to appear in a directory, CLEC must submit a Directory Service Request (DSR). Sprint shall use reasonable efforts to assist CLEC in obtaining an agreement with the directory publisher that treats CLEC at Parity with the publisher’s treatment of Sprint. |
| 81.3.1. | This § 81.3 pertains to listings requirements published in the traditional white pages. |
124
| 81.3.2. | Sprint shall include in its master subscriber system database all white pages listing information for CLEC subscribers in Sprint territories where CLEC is providing local telephone exchange services and has submitted a DSR. |
| 81.3.3. | Sprint agrees to include one basic White pages listing for each CLEC customer located within the geographic scope of its White Page directories, at no additional charge to CLEC. A basic White Pages listing is defined as a customer name, address and either the CLEC assigned number for a customer or the number for which number portability is provided, but not both numbers. Basic White Pages listings of CLEC customers will be interfiled with listings of Sprint and other LEC customers. |
| 81.3.4. | CLEC agrees to provide CLEC customer listing information, including without limitation directory distribution information, to Sprint, at no charge. Sprint will provide CLEC with the appropriate format for provision of CLEC customer listing information to Sprint. The parties agree to adopt a mutually acceptable electronic format for the provision of such information as soon as practicable. In the event OBF adopts an industry-standard format for the provision of such information, the parties agree to adopt such format. |
| 81.3.5. | Sprint agrees to provide White Pages database maintenance services to CLEC. CLEC will be charged a Service Order entry fee upon submission of Service Orders into Sprint’s Service Order Entry (SOE) System, which will include compensation for such database maintenance services. Service Order entry fees apply when Service Orders containing directory records are entered into Sprint’s SOE System initially, and when Service Orders are entered in order to process a requested change to directory records. |
| 81.3.6. | CLEC customer listing information will be used solely for the provision of directory services, including the sale of directory advertising to CLEC customers. |
| 81.3.7. | In addition to a basic White Pages listing, Sprint will provide tariffed White Pages listings (e.g.: additional, alternate, foreign and non-published listings) for CLEC to offer for resale to CLEC’s customers. |
| 81.3.8. | Sprint, or its directory publisher, agree to provide White Pages distribution services to CLEC customers within Sprint’s service territory at no additional charge to CLEC. Sprint represents that the quality, timeliness, and manner of such distribution services will be at Parity with those provided to Sprint and to other CLEC customers. |
| 81.3.9. |
Sprint agrees to include critical contact information pertaining to CLEC in the “Information Pages” of those of its White Pages directories containing information pages, provided that CLEC meets criteria established by its directory publisher. Critical contact information includes CLEC’s |
125
|
business office number, repair number, billing information number, and any other information required to comply with applicable regulations, but not advertising or purely promotional material. CLEC will not be charged for inclusion of its critical contact information. The format, content and appearance of CLEC’s critical contact information will conform to applicable Sprint directory publisher’s guidelines and will be consistent with the format, content and appearance of critical contact information pertaining to all CLECs in a directory. |
| 81.3.10. | Sprint will accord CLEC customer listing information the same level of confidentiality that Sprint accords its own proprietary customer listing information. Sprint shall ensure that access to CLEC customer proprietary listing information will be limited solely to those of Sprint and Sprint’s directory publisher’s employees, agents and contractors that are directly involved in the preparation of listings, the production and distribution of directories, and the sale of directory advertising. Sprint will advise its own employees, agents and contractors and its directory publisher of the existence of this confidentiality obligation and will take appropriate measures to ensure their compliance with this obligation. Notwithstanding any provision herein to the contrary, the furnishing of White Pages proofs to a CLEC that contains customer listings of both Sprint and CLEC will not be deemed a violation of this confidentiality provision. |
| 81.3.11. | Sprint will sell or license CLEC’s customer listing information to any third parties unless CLEC submits written requests that Sprint refrain from doing so. Sprint and CLEC will work cooperatively to share any payments for the sale or license of CLEC customer listing information to third parties. Any payments due to CLEC for its customer listing information will be net of administrative expenses incurred by Sprint in providing such information to third parties. The parties acknowledge that the release of CLEC’s customer listing to Sprint’s directory publisher will not constitute the sale or license of CLEC’s customer listing information causing any payment obligation to arise pursuant to this § 81.3.11. |
| 81.4. | Other Directory Services. Sprint will exercise reasonable efforts to cause its directory publisher to enter into a separate agreement with CLEC which will address other directory services desired by CLEC as described in this § 81.4. Both parties acknowledge that Sprint’s directory publisher is not a party to this Agreement and that the provisions contained in this § 81.4 are not binding upon Sprint’s directory publisher. |
| 81.4.1. | Sprint’s directory publisher will negotiate with CLEC concerning the provision of a basic Yellow Pages listing to CLEC customers located within the geographic scope of publisher’s Yellow Pages directories and distribution of Yellow Pages directories to CLEC customers. |
126
| 81.4.2. | Directory advertising will be offered to CLEC customers on a nondiscriminatory basis and subject to the same terms and conditions that such advertising is offered to Sprint and other CLEC customers. Directory advertising will be billed to CLEC customers by directory publisher. |
| 81.4.3. | Directory publisher will use commercially reasonable efforts to ensure that directory advertising purchased by customers who switch their service to CLEC is maintained without interruption. |
| 81.4.4. | Information pages, in addition to any information page or portion of an information page containing critical contact information as described above in § 81.3.9 may be purchased from Sprint’s directory publisher, subject to applicable directory publisher guidelines, criteria, and regulatory requirements. |
| 81.4.5. | Directory publisher maintains full authority as publisher over its publishing policies, standards and practices, including decisions regarding directory coverage area, directory issue period, compilation, headings, covers, design, content or format of directories, and directory advertising sales. |
| 81.5. | Directory Assistance Data. This section refers to the residential, business, and government subscriber records used by Sprint to create and maintain databases for the provision of live or automated operator assisted Directory Assistance. Directory Assistance Data is information that enables telephone exchange CLECs to swiftly and accurately respond to requests for directory information, including, but not limited to name, address and phone numbers. Under the provisions of the Act and the FCC’s Interconnection order, Sprint shall provide unbundled and non-discriminatory access to the residential, business and government subscriber records used by Sprint to create and maintain databases for the provision of live or automated operator assisted Directory Assistance. This access shall be provided under separate contract. |
| 81.6. | Systems Interfaces and Exchanges |
| 81.6.1. | Directory Assistance Data Information Exchanges and Interfaces |
| 81.6.1.1. | Subscriber List Information |
| 81.6.1.1.1. |
Sprint shall provide to CLEC, within sixty (60) days after the Approval Date of this Agreement, or at CLEC’s request, all published Subscriber List Information (including such information that resides in Sprint’s master subscriber system/accounts master file for the purpose of publishing directories in any format as specified by the Act) via an electronic data transfer medium and in a mutually agreed to format, on the same terms and conditions and at the same rates that the Sprint provides Subscriber List Information to itself or to other third parties. All changes to the Subscriber List Information |
127
|
shall be provided to CLEC pursuant to a mutually agreed format and schedule. Both the initial List and all subsequent Lists shall indicate for each subscriber whether the subscriber is classified as residence or business class of service. |
| 81.6.1.1.2. | CLEC shall provide directory listings to Sprint pursuant to the directory listing and delivery requirements in the approved OBF format, at a mutually agreed upon timeframe. Other formats and requirements shall not be used unless mutually agreed to by the parties. |
| 81.7. | Listing Types |
|
LISTED | The listing information is available for all directory requirements. | |
|
NON-LISTED | The listing information is available to all directory requirements, but the information does not appear in the published street directory. | |
|
NON-PUBLISHED | A directory service may confirm, by name and address, the presence of a listing, but the telephone number is not available. The listing information is not available in either the published directory or directory assistance. | |
128
PART J - REPORTING STANDARDS
| 82. | GENERAL |
| 82.1. | Sprint shall satisfy all service standards, intervals, measurements, specifications, performance requirements, technical requirements, and performance standards and will pay any penalties for violation of the performance standards that are required by law or regulation. In addition, Sprint’s performance under this agreement shall be provided to CLEC at parity with the performance Sprint provides itself for like service(s). |
129