Procedures for Providing LNP ( Sample Clauses

Procedures for Providing LNP (. “Long-term Number Portability”). The Parties will follow the LNP provisioning process recommended by the North American Numbering Council (NANC) and adopted by the FCC. In addition, the Parties agree to follow the LNP ordering procedures established at the OBF. The Parties shall provide LNP on a reciprocal basis. 15.2.1 A Customer of one Party ("Party A") elects to become a Customer of the other Party ("Party B"). The Customer elects to utilize the original telephone number(s) corresponding to the Telephone Exchange Service(s) it previously received from Party A, in conjunction with the Telephone Exchange Service(s) it will now receive from Party B. After Party B has received authorization from the Customer in accordance with Applicable Law and sends an LSR to Party A, Parties A and B will work together to port the Customer’s telephone number(s) from Party A’s network to Party B’s network. 15.2.2 When a telephone number is ported out of Party A’s network, Party A will remove any non-proprietary line based calling card(s) associated with the ported number(s) from its Line Information Database (LIDB). Reactivation of the line-based calling card in another LIDB, if desired, is the responsibility of Party B or Party B’s Customer. 15.2.3 When a Customer of Party A ports their telephone numbers to Party B and the Customer has previously secured a reservation of line numbers from Party A for possible activation at a future point, these reserved but inactive numbers may be ported along with the active numbers to be ported provided the numbers have been reserved for the Customer. Party B may request that Party A port all reserved numbers assigned to the Customer or that Party A port only those numbers listed by Party B. As long as Party B maintains reserved but inactive numbers ported for the Customer, Party A shall not reassign those numbers. Party B shall not reassign the reserved numbers to another Customer. 15.2.4 When a Customer of Party A ports their telephone numbers to Party B, in the process of porting the Customer’s telephone numbers, Party A shall implement the ten-digit trigger feature where it is available. When Party A receives the porting request, the unconditional trigger shall be applied to the Customer’s line before the due date of the porting activity. When the ten-digit unconditional trigger is not available, Party A and Party B must coordinate the disconnect activity. 15.2.5 The Parties shall furnish each other with the Jurisdiction Information...
Sample 1Sample 2Sample 3See All (79)
AutoNDA by SimpleDocs
Procedures for Providing LNP (. The Parties shall follow the Local Number Portability provisioning process recommended by the North American Numbering Council (“NANC”) and adopted by the FCC. In addition, the Parties agree to follow the Local Number Portability ordering procedures established at the Ordering and Billing Forum (“OBF”). 13.2.1 The Parties shall work cooperatively to port customer’s telephone number(s) using LNP. 13.2.2 When a telephone number is ported from Party A’s network using LNP, Party A shall remove any non-proprietary line-based calling cards associated with the ported number(s) from its LIDB. Reactivation of the line-based calling card in another LIDB, if desired, is the responsibility of Party B or the customer. 13.2.3 When a customer of Party A ports their telephone number(s) to Party B, in the process of porting the customer’s telephone numbers, Party A shall implement the ten-digit trigger feature where it’s available. When Party A receives the porting request, the unconditional trigger shall be applied to the customer’s line prior to the due date of the porting activity. When the ten digit unconditional trigger is not available, the Parties must coordinate the disconnect activity. 13.2.4 The Parties shall include the Jurisdictional Information Parameter (“JIP”) in the Initial Address Message (“IAM”) that contains the LERG-assigned NPA-NXX (6 digits) identifying the originating switch on calls originating from LNP capable switches.
Sample 1Sample 2Sample 3See All (21)
Procedures for Providing LNP (. The Parties will follow the long-term Number Portability provisioning process recommended by the North American Numbering Council (NANC) and adopted by the FCC. In addition, the Parties agree to follow the long-term Number Portability ordering procedures established at the Ordering And Billing Forum (OBF).
Sample 1Sample 2Sample 3See All (8)
Procedures for Providing LNP (. “Local Number Portability”). The Parties will follow the LNP provisioning process recommended by the North American Numbering Council (NANC) and adopted by the FCC. The Parties shall provide LNP on a reciprocal basis.
Sample 1Sample 2
Procedures for Providing LNP (. (“Long-term Number Portability”) 20.2.1 The following steps shall apply: (1) a Customer of one Party ("Party A") elects to become a Customer of the other Party ("Party B"); (2) the Customer elects to utilize the original telephone number(s) corresponding to the Telephone Exchange Service(s) it previously received from Party A, in conjunction with the Telephone Exchange Service(s) it will now receive from Party B; (3) after Party B has received authorization from an end user Customer, and sent an LSR to Party A, Parties A and B will work together to port the Customer’s telephone number(s) from Party A’s network to Party B’s network.
Sample 1Sample 2
Procedures for Providing LNP (. The Parties shall follow the Local Number Portability provisioning process recommended by the North American Numbering Council (“NANC”) and adopted by the FCC. In addition, the Parties agree to follow the Local Number Portability ordering procedures established at the Ordering and Billing Forum (“OBF”). 13.2.1 The Parties shall work cooperatively to port customer’s telephone number(s) using LNP. 13.2.2 Party B will provide Party A with a Firm Order Confirmation (“FOC”) for each port order by 5:00 p.m. of the next Business Day after Party B’s receipt of that order. The FOC must contain Party B’s commitment date for order completion (“Committed Due Date”), which shall be within three (3) days after issuance of the FOC, or within a different time interval agreed upon by the Implementation Team, unless Party A requested a longer interval.
Sample 1Sample 2
Procedures for Providing LNP (. (“Long-term Number Portability”) 20.2.1 The following steps shall apply: (1) a Customer of one Party ("Party A") elects to become a Customer of the other Party ("Party B"); (2) the Customer elects to utilize the original telephone number(s) corresponding to the Telephone Exchange Service(s) it previously received from Party A, in conjunction with the Telephone Exchange Service(s) it will now receive from Party B; (3) after Party B has received authorization from an end user Customer, and sent an LSR to Party A, Parties A and B will work together to port the Customer’s telephone number(s) from Party A’s network to Party B’s network. 20.2.2 When a telephone number is ported out of Party A’s network, Party A will remove any non-proprietary line based calling card(s) associated with the ported number(s) from its Line Information Database ("LIDB"). Reactivation of the line-based calling card in another LIDB, if desired, is the responsibility of Party B or Party B’s Customer. 20.2.3 When a Customer of Party A ports their telephone number(s) to Party B and the Customer has previously secured a reservation of line number(s) from Party A for possible activation at a future point, these reserved but inactive number(s) may be ported along with the active number(s) to be ported provided the number(s) have been reserved for the Customer. Reserved telephone numbers are non-working telephone numbers assigned to a specific Customer to be used at a later time. The numbers are assigned to the Customer either via Tariff or other contractual arrangement between the Customer and the service provider. Party B may request that Party A port all reserved number(s) assigned to the Customer or that Party A port only those number(s) listed by Party
Sample 1
AutoNDA by SimpleDocs
Procedures for Providing LNP (. 13.2.1 The Parties shall follow the Local Number Portability provisioning process recommended by the North American Numbering Council (“NANC”) and adopted by the FCC. In addition, the Parties agree to follow the Local Number Portability ordering procedures established at the Ordering and Billing Forum (“OBF”). 13.2.1.1 The Parties shall work cooperatively to port customer’s telephone number(s) using LNP. 13.2.1.2 When a telephone number is ported from Party A’s network using LNP, Party A shall remove any non-proprietary line-based calling cards associated with the ported number(s) from its LIDB. Reactivation of the line-based calling card in another LIDB, if desired, is the responsibility of Party B or the customer. 13.2.1.3 When a customer of Party A ports their telephone number(s) to Party B, in the process of porting the customer’s telephone numbers, Party A shall implement the ten-digit trigger feature where it’s available. When Party A receives the porting request, the unconditional trigger shall be applied to the customer’s line prior to the due date of the porting activity. When the ten digit unconditional trigger is not available, the Parties must coordinate the disconnect activity. The Parties shall include the Jurisdictional Information Parameter (“JIP”) in the Initial Address Message (“IAM”) that contains the LERG-assigned NPA-NXX (6 digits) identifying the originating switch on calls originating from LNP capable switches. The switch’s LRN software determines if the called party is in a portable NXX. If the called party is in a portable NXX, a query is launched to the LNP database to determine whether or not the called number is ported. When the called number with a portable NXX is ported, an LRN is returned to the switch that launched the query. Per industry standards, the LRN appears in the CdPN (Called Party Number) field of the SS7 message and the called number then appears in the GAP (Generic Address Parameter) field. When the called number with a portable NXX is not ported, the call is completed as in the pre-LNP environment. The FCI (Forward Call Identifier) field’s entry is changed from 0 to 1 by the switch triggering the query when a query is made, regardless of whether the called number is ported or not. The N-1 carrier (N carrier is the responsible Party for terminating call to the End User) has the responsibility to determine if a query is required, to launch the query, and to route the call to the switch or network in which the tele...
Sample 1

Related to Procedures for Providing LNP (

  • Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.

  • Procedures for LNP Request The Parties shall provide for the requesting of End Office LNP capability on a reciprocal basis through a written request. The Parties acknowledge that Verizon has deployed LNP throughout its network in compliance with FCC 96-286 and other applicable FCC Regulations. 15.4.1 If Party B desires to have LNP capability deployed in an End Office of Party A, which is not currently capable, Party B shall issue a LNP request to Party A. Party A will respond to the Party B, within ten (10) days of receipt of the request, with a date for which LNP will be available in the requested End Office. Party A shall proceed to provide for LNP in compliance with the procedures and timelines set forth in FCC 00-000, Xxxxxxxxx 80, and FCC 97-74, Paragraphs 65 through 67. 15.4.2 The Parties acknowledge that each can determine the LNP-capable End Offices of the other through the Local Exchange Routing Guide (LERG). In addition, the Parties shall make information available upon request showing their respective LNP-capable End Offices, as set forth in this Section 15.4.

  • Procedures for Advances (a) In the case of the making of any Advance, the repayment of any Advance, or any termination, increase or reduction of the Facility Amount and prepayments of Advances, the Borrower shall give the Administrative Agent a Borrower Notice. Each Borrower Notice shall specify the amount (subject to Section 2.1 hereof) of Advances to be borrowed or repaid and the Funding Date or repayment date (which, in all cases, shall be a Business Day) and whether such Advance is a Revolver Advance or a Swing Advance. (b) Subject to the conditions described in Section 2.1, the Borrower may request an Advance from the Lenders by delivering to the Administrative Agent at certain times the information and documents set forth in this Section 2.2. (c) No later than 12:00 noon (New York, New York time) five (5) Business Days prior to the proposed Funding Date for a Revolver Advance (or such shorter period of time or later date as may be agreed to by the Required Lenders), the Borrower shall notify (i) the Collateral Custodian by delivery to the Collateral Custodian of written notice of such proposed Funding Date, and (ii) the Administrative Agent by delivery to the Administrative Agent of a credit report and transaction summary for each Loan that is the subject of the proposed Advance setting forth the credit underwriting by the Originator of such Loan, including without limitation a description of the Obligor and the proposed loan transaction in the form of Exhibit M hereto; provided that, in the case of Advances funding Revolver Loans, the requirements of this Section 2.2(c) shall apply only with respect to the first Advance to be made with respect to each such Revolver Loan. By 5:00 p.m. (New York, New York time) on the next Business Day, the Administrative Agent shall use its best efforts to confirm to the Borrower the receipt of such items and whether it has reviewed such items and found them to be complete and in proper form. If the Administrative Agent makes a determination that the items are incomplete or not in proper form, it will communicate such determination to the Borrower. Failure by the Administrative Agent to respond to the Borrower by 5:00 p.m. (New York, New York time) on the day the related Funding Request is delivered by the Borrower shall constitute an implied determination that the items are incomplete or not in proper form. The Borrower will take such steps requested by the Administrative Agent to correct the problem(s). In the event of a delay in the actual Funding Date due to the need to correct any such problems, the Funding Date shall be no earlier than two (2) Business Days after the day on which the Administrative Agent confirms to the Borrower that the problems have been corrected. (d) No later than 1:00 p.m. (New York, New York time) one (1) Business Day prior to the proposed Funding Date for a Revolver Advance (or such shorter period of time or later date as may be agreed to by the Required Lenders), the Administrative Agent, each Managing Agent and the Collateral Custodian, as applicable, shall receive or shall have previously received the following: (i) a Funding Request in the form of Exhibit A; (ii) a wire disbursement and authorization form shall be delivered to the Administrative Agent; and (iii) a certification substantially in the form of Exhibit H concerning the Collateral Custodian’s receipt of certain documentation relating to the Eligible Loan(s) related to such Advance shall be delivered to the Administrative Agent, which may be delivered either as a separate document or incorporated in the Monthly Report. Each Funding Request for a Revolver Advance shall specify the aggregate amount of the requested Advance, which shall be in an amount equal to at least $500,000. (e) No later than 12:00 noon (New York, New York time) on the Business Day proposed for a Swing Advance, the Administrative Agent shall receive or shall have previously received the following: (i) a Funding Request in the form of Exhibit A; and (ii) a wire disbursement and authorization form. (f) Each Funding Request shall be accompanied by (i) a Borrower Notice, depicting the outstanding amount of Advances under this Agreement and representing that all conditions precedent for a funding have been met, including a representation by the Borrower that the requested Advance shall not, on the Funding Date thereof, exceed the Availability on such day, (ii) a calculation of the Borrowing Base as of the applicable Funding Date (which calculation may, for avoidance of doubt, take into account (A) Loans which will become Transferred Loans on or prior to such Funding Date and (B) an updated Loan List including each Loan that is subject to the requested Advance, (C) the proposed Funding Date, and (D) wire transfer instructions for the Advance; provided, however, the Funding Request for a Swing Advance shall be required to contain only the information described in Section 2.2(e)(i) and (ii) above. A Funding Request shall be irrevocable when delivered; provided however, that if the Borrowing Base calculation delivered pursuant to clause (ii) above includes a Loan which does not become a Transferred Loan on or before the applicable Funding Date as anticipated, and the Borrower cannot otherwise make the representations required pursuant to clause (i) above, the Borrower shall revise the Funding Request accordingly, and shall pay any loss, cost or expense incurred by any Lender in connection with the broken funding evidenced by such revised Funding Request. (g) On the Funding Date following the satisfaction of the applicable conditions set forth in this Section 2.2 and Article III, the Lenders shall make available to the Administrative Agent at its address listed beneath its signature on its signature page to this Agreement (or on the signature page to the Joinder Agreement pursuant to which it became a party hereto), for deposit to the account of the Borrower or its designee in same day funds, at the account specified in the Funding Request, an amount equal to such Lender’s ratable share of the Advance then being made (except that in the case of a Swing Advance, the Swingline Lender will make available to the Borrower the amount of any such Swing Advance). Each wire transfer of an Advance to the Borrower shall be initiated by the applicable Lender no later than 3:00 p.m. (New York, New York time) on the applicable Funding Date.

  • New Procedures New procedures as to who shall provide certain of these services in Section 1 may be established in writing from time to time by agreement between the Fund and the Transfer Agent. The Transfer Agent may at times perform only a portion of these services and the Fund or its agent may perform these services on the Fund's behalf;

  • Hiring Procedures Nothing contained in this Article 4 shall impair any of the rights of the Employer to hire new or additional employees to meet the employment needs of the Employer, in accordance with the terms and provisions of this collective bargaining Agreement or to meet the obligations of the Employer under Article 2, Section H of this Agreement or to take affirmative steps to comply with any requirements under any applicable Federal or State law prohibiting discrimination in employment.

  • ORDERING PROCEDURES All task orders under OASIS SB must: 1. Be awarded by an OCO with a Delegation of Procurement Authority (DPA) or by a Contractor authorized to use the OASIS SB Contracts as a Government Source of Supply 2. Be within the scope of Section C and all other terms and conditions of the OASIS SBcontract 3. Be solicited and awarded under the proper NAICS Code and corresponding OASIS SB MA-IDIQ Contract Number (See Section H.4.) 4. Identify the proper Product Service Code (See Section H.5.) and, 5. Comply with the OASIS SB Contract, OASIS SB DPA Training, OASIS SB Ordering Guide, the Ordering Procedures in FAR Subpart 16.505, Ordering, and other applicable agency specific regulatorysupplements

  • Mechanisms for Cooperation Pursuant to Article 149 (Objectives), the Parties hereby establish a Committee on Cooperation comprising representatives of each Party.

  • Proposed Policies and Procedures Regarding New Online Content and Functionality By October 31, 2017, the School will submit to OCR for its review and approval proposed policies and procedures (“the Plan for New Content”) to ensure that all new, newly-added, or modified online content and functionality will be accessible to people with disabilities as measured by conformance to the Benchmarks for Measuring Accessibility set forth above, except where doing so would impose a fundamental alteration or undue burden. a) When fundamental alteration or undue burden defenses apply, the Plan for New Content will require the School to provide equally effective alternative access. The Plan for New Content will require the School, in providing equally effective alternate access, to take any actions that do not result in a fundamental alteration or undue financial and administrative burdens, but nevertheless ensure that, to the maximum extent possible, individuals with disabilities receive the same benefits or services as their nondisabled peers. To provide equally effective alternate access, alternates are not required to produce the identical result or level of achievement for persons with and without disabilities, but must afford persons with disabilities equal opportunity to obtain the same result, to gain the same benefit, or to reach the same level of achievement, in the most integrated setting appropriate to the person’s needs. b) The Plan for New Content must include sufficient quality assurance procedures, backed by adequate personnel and financial resources, for full implementation. This provision also applies to the School’s online content and functionality developed by, maintained by, or offered through a third-party vendor or by using open sources. c) Within thirty (30) days of receiving OCR’s approval of the Plan for New Content, the School will officially adopt, and fully implement the amended policies and procedures.

  • Billing Procedures The Supporting Party will xxxx the Protecting Party for actual costs incurred for Assistance by Hire. Reimbursements will be limited to the provisions of the Agreement and the applicable OP, regardless of whether or not it is authorized on the Resource Order or other documentation produced by the incident. Reimbursable costs may include transportation, salary, overtime, per diem and other approved expenses of Supporting agency personnel. Rates and conditions of use for the equipment and personnel are documented in the OP. Parties shall submit a xxxx within 90 days of the incident. Parties must use their own invoice form for billing under this Agreement to avoid any confusion with other services that may have been ordered under other agreements. Invoices must identify Supporting Party’s name, address, and Taxpayer Identification Number (Department only), fire name, order and request number, and xxxx number and amount. Invoice supporting documentation must include description of services performed, period of services performed, and any applicable cost share agreements. Supporting documentation will itemize details of billing, listing personnel, equipment, travel and per diem, aircraft, supplies and purchases as approved in the attached AOP. It will also include itemized deductions for maintenance and repair of equipment. Department invoices will include “Record of Activities” (FSLA-5) and U.S. Forest Service invoices will include transaction register. Invoices for services under this agreement must be sent to: Name: Xxxx Xxxxxx-Xxxxx, ECC Manager Address: 0000 Xxxxxxxxx Xxxxx Xxxx, Xxxxx, Xxx: Xxxxxxxxxx, XX 00000 Telephone: (000) 000-0000 FAX: (000) 000-0000 Email: xxxxxxxxxxxx@xx.xxx.xx Name: Spalding Community Service District Address: 000-000 Xxxxxxxx Xxx Xxxx, Xxxxx, Xxx: Xxxxxxxxxx, XX 00000 Telephone: (000) 000-0000 FAX: (000) 000-0000 Email: xxxxxxxxxxxxx@xxxxxxx.xxx All bills will have a payment due date 30 days upon receipt. Contested Xxxxxxxx: Written notice that a xxxx is contested will be mailed to the Party within 30 days of receipt of the invoice and will fully explain the contested items. Contested items should be resolved no later than 60 days following receipt of the written notice. Parties are responsible for facilitating resolution of contested xxxxxxxx. Billing requirements and rates are documented in the attached OP.

  • Impasse Procedures The Parties shall seek to reach agreement relative to the appointment of a mediator not later than the sixtieth (60) day preceding the budget submission date. The Parties shall seek to reach agreement relative to the appointment of a fact finder not later than the forty-fifth (45) day preceding the budget submission date. The Parties shall consider but not be limited to the service of the Federal Mediation and Conciliation Service and the American Arbitration Association for a mediator and fact finder respectively. If the Parties fail to reach an agreement on the choice of a mediator or fact finder, the PELRB shall be petitioned under the provisions of 273-A: 12.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!