Signaling Requirements Sample Clauses

Signaling Requirements. SS7 Signaling is required for the provision of SPNP services. SPNP-DID is available from BellSouth on a per DS0, DS1, or DS3 basis. Where SPNP-DID is technically feasible and is provided on a DS1 or a DS3 basis, the applicable channelization rates are those specified in Section E6 in BellSouth’s Intrastate Access Tariffs, incorporated herein by this reference. SPNP is available only for basic local exchange service.
Sample 1Sample 2Sample 3See All (6)
AutoNDA by SimpleDocs
Signaling Requirements. ‌ 3.1 Signaling protocol. The Parties will interconnect their networks using SS7 signaling where technically feasible and available as defined in FR 905 Bellcore Standards including ISDN user part ("ISUP") for trunk signaling and Transaction Capabilities Application Part ("TCAP") for CCS-based features in the interconnection of their networks. All Network Interoperability Interface Forum (NIIF) adopted standards shall be adhered to. 3.2 Where available, CCS signaling shall be used by the Parties to set up calls between the Parties' Telephone Exchange Service networks. If CCS signaling is unavailable, the Parties shall use MF (Multi-Frequency) signaling. 3.3 The following list of publications describe the practices, procedures and specifications generally utilized by the industry for signaling purposes and are listed herein to assist the Parties in meeting their respective interconnection responsibilities related to signaling: GR-000246-CORE, Xxxx Communications Research Specifications of Signaling System 7 (“SS7”) GR-000317-CORE, Switching System Requirements for Call Control Using the Integrated Services Digital Network User Part GR-000394-CORE, Switching System Requirements for Interexchange Carrier Interconnection Using the Integrated Services Digital Network User Part GR-000606-CORE, LATA Switching Systems Generic Requirements- Common Channel Signaling-§6.5 GR-000905-CORE, Common Channel Signaling Network Interface Specification Supporting Network Interconnection Message Transfer Part (“MTP”) and Integrated Digital Services Network User Part (“ISDNUP”) 3.4 The Parties will cooperate on the exchange of Transactional Capabilities Application Part (TCAP) messages to facilitate interoperability of CCS-based features between their respective networks, including all CLASS features and functions, to the extent each Party offers such features and functions to its end users. All CCS signaling parameters will be provided including, without limitation, Calling Party Number (CPN), Originating Line Information (“OLI”), calling party category and charge number. 3.5 Where available each Party shall cooperate to ensure that all of its trunk groups are configured utilizing the B8ZS ESF protocol for 64 kbps clear channel transmission to allow for ISDN interoperability between the Parties' respective networks. 3.6 The Parties shall jointly develop a grooming plan (the "Joint Grooming Plan") which shall define and detail, inter alia, 3.6.1 disaster recovery provisions and...
Sample 1Sample 2Sample 3See All (6)
Signaling Requirements. 3.1 Signaling Parameters. Windstream and Alliance Connect are required to provide each other the proper signaling information as required by Applicable Law and further clarified by the FCC Order to enable each Party to issue bills in a complete and timely fashion. All CCS signaling parameters will be provided unchanged including CPN, calling party category, ChN (Charge Number) and Originating Line Information Parameter (OLIP) on all calls. All privacy indicators will be honored. The ChN is to be passed unaltered in SS7 signaling fields where it is different than CPN; ChN must not be populated with a number associated with an intermediate switch, platform, or gateway, or other number that designates anything other than a calling party’s charge number; and if MF signaling is used by Alliance Connect then the ChN must be included in the ANI field if different from the CPN. Where SS7 connections exist, each Party shall pass all CCS signaling parameters, where available, on each call carried over interconnection trunks. If either Party fails to provide valid originating information, such traffic will be billed as Intrastate Switched Access when the calls traverse an interconnection trunk. The Parties will coordinate and exchange data as necessary to determine the cause of the CPN/ChN failure to assist its correction. 3.2 Where available each Party shall cooperate to ensure that all of its trunk groups are configured utilizing the B8ZS ESF protocol for 64 kbps clear channel transmission to allow for ISDN interoperability between the Parties' respective networks. 3.3 The Parties shall jointly develop a grooming plan (the "Joint Grooming Plan") which shall define and detail, inter alia, 3.3.1 disaster recovery provisions and escalations; 3.3.2 direct/high usage trunk engineering guidelines; and 3.3.3 such other matters as the Parties may agree. 3.4 If a Party makes a change in its network, which it believes will materially affect the interoperability of its network with the other Party, the Party making the change shall provide thirty (30) days advance written notice of such change to the other Party.
Sample 1See All (5)
Signaling Requirements. 3.1 Signaling Parameters. Windstream and Service Electric are required to provide each other the proper signaling information as required by Applicable Law and further clarified by FCC Order (FCC 11-161) to enable each Party to issue bills in a complete and timely fashion. All CCS signaling parameters will be provided unchanged including CPN, calling party category and ChN (Charge Number) on all calls. All privacy indicators will be honored. The ChN is to be passed unaltered in SS7 signaling fields where it is different than CPN; ChN must not be populated with a number associated with an intermediate switch, platform, or gateway, or other number that designates anything other than a calling party’s charge number; and if MF signaling is used then the ChN must be included in the ANI field if different from the CPN. Where SS7 connections exist, each Party shall pass all CCS signaling parameters, where available, on each call carried over interconnection trunks, including CLASS features and functions to the extent each Party offers such features and functions to its end users. If either Party fails to provide valid originating information, such traffic without the valid originating information will be billed by the terminating Party as Intrastate Switched Access when the calls traverse an interconnection trunk. Notwithstanding the preceding, if five percent (5%) or less of the traffic originated by a Party fails to include the proper signaling information as defined herein, such traffic will be treated by the terminating Party as having the same jurisdictional ratio as the traffic that includes the proper signaling information. The Parties will coordinate and exchange data as necessary to determine the cause of the CPN/ChN failure if/when the amount of traffic does not include the proper signaling information exceeds five percent (5%) and assist in its correction. In the event that technical malfunctions result in lack of transmission of CPN/ChN, the Parties will cooperate in attempting to resolve such technical malfunctions and the Parties will develop and utilize mutually agreeable surrogate methods for determining compensation that shall be utilized until the technical malfunctions are resolved.
Sample 1

Related to Signaling Requirements

  • Staffing Requirements Licensee will be in full compliance with the main studio staff requirements as specified by the FCC.

  • Screening Requirements Practitioner shall ensure that all prospective and current Covered Persons are not Ineligible Persons, by implementing the following screening requirements. a. Practitioner shall screen all prospective Covered Persons against the Exclusion List prior to engaging their services and, as part of the hiring or contracting process, shall require such Covered Persons to disclose whether they are Ineligible Persons.‌ b. Practitioner shall screen all current Covered Persons against the Exclusion List within 30 days after the Effective Date and on a monthly basis thereafter.‌ c. Practitioner shall require all Covered Persons to disclose immediately if they become an Ineligible Person.‌ Practitioner shall maintain documentation in order to demonstrate that Practitioner: (1) has checked the Exclusion List (i.e., a print screen of the search results) and determined that its Covered Persons are not Ineligible Persons; and (2) has required its Covered Persons to disclose if they are an Ineligible Person. Nothing in this Section III.D affects Practitioner’s responsibility to refrain from (and liability for) billing Federal health care programs for items or services furnished, ordered, or prescribed by an excluded person. Practitioner understands that items or services furnished by excluded persons are not payable by Federal health care programs and that Practitioner may be liable for overpayments and/or criminal, civil, and administrative sanctions for employing or contracting with an excluded person regardless of whether Practitioner meets the requirements of Section III.D.

  • Monitoring Requirements This Schedule sets out the contract management requirements which are applicable to the delivery of the Services.

  • Trunking Requirements The Parties will provide designed Interconnection facilities that meet the same technical criteria and service standards, such as probability of blocking in peak hours and transmission standards, in accordance with current industry standards.

  • Testing Requirements 12.1. Workplaces - 12.2. On workplaces where the value of the Commonwealth’s contribution to the project that includes the building work is at least $5,000,000, and represents at least 50% of the total construction project value or the Commonwealth’s contribution to the project that includes the building work is at least $10,000,000 (irrespective of its proportion of the total construction project value) the following minimum testing requirements must be adhered to.

  • Filing Requirements Escrow securities will not be released under this Part until the Issuer does the following: (a) at least 20 days before the date of the first release of escrow securities under the new release schedule, files with the securities regulators in the jurisdictions in which it is a reporting issuer (i) a certificate signed by a director or officer of the Issuer authorized to sign stating (A) that the Issuer has become an established issuer by satisfying one of the conditions in section 3.1 and specifying the condition, and (B) the number of escrow securities to be released on the first release date under the new release schedule, and (ii) a copy of a letter or other evidence from the exchange or quotation service confirming that the Issuer has satisfied the condition to become an established issuer; and (b) at least 10 days before the date of the first release of escrow securities under the new release schedule, issues and files with the securities regulators in the jurisdictions in which it is a reporting issuer a news release disclosing details of the first release of the escrow securities and the change in the release schedule, and sends a copy of such filing to the Escrow Agent.

  • Training Requirements Grantee shall: A. Authorize and require staff (including volunteers) to attend training, conferences, and meetings as directed by DSHS; B. Appropriately budget funds in order to meet training requirements in a timely manner, and ensure that staff and volunteers are trained as specified in the training requirements listed at xxxxx://xxx.xxxx.xxxxx.xxx/hivstd/training/ and as otherwise specified by DSHS. Grantee shall document that these training requirements are met; and C. Ensure that staff hired for HIV and syphilis testing are trained to perform blood draws within three (3) months of employment.

  • Forecasting Requirements 19.5.1 The Parties shall exchange technical descriptions and forecasts of their Interconnection and traffic requirements in sufficient detail necessary to establish the Interconnections necessary for traffic completion to and from all Customers in their respective designated service areas.

  • ORDERING REQUIREMENTS Eligible Purchasers shall order Goods and/or Services from this Contract, consistent with the terms hereof and by using any ordering mechanism agreeable both to Contractor and Purchaser but including, at a minimum, a purchase order. When practicable, Contractor and Purchaser also shall use telephone orders, email orders, web- based orders, and similar procurement methods (collectively “Purchaser Order”). All Purchase Orders must reference the Contract number. The terms of this Contract shall apply to any Purchase Order and, in the event of any conflict, the terms of this Contract shall prevail. Notwithstanding any provision to the contrary, in no event shall any ‘click-agreement,’ software or web-based application terms and conditions, or any other agreement modify the terms and conditions of this Contract.

  • Operating Requirements Any operating and technical requirements that may be applicable due to Regional Transmission Organization, Independent System Operator, control area, or the Connecting Transmission Owner’s requirements, including those set forth in the Small Generator Interconnection Agreement. Operating Requirements shall include Applicable Reliability Standards.

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