Multiservice Switching Forum Sample Clauses

Multiservice Switching Forum. The goal of the MSF is to promote multi-vendor interoperability as part of a drive to accelerate the deployment of next generation networks. To this end the MSF looks to adopt pragmatic solutions in order to maximize the chances for early interoperability in real world networks. To date the MSF has defined a number of detailed Implementation Agreements and detailed Test Plans for the signaling protocols between network components and is developing additional Implementation Agreements and Test Plans addressing some of the other technical issues such as QoS and Security to assist vendors and operators in deploying interoperable solutions. In 2004, the MSF held a “Global MSF Interoperability 2004” (GMI 2004) event that tested interoperability between next generation network elements situated in Asia, Europe and North America. GMI 2004 validated the MSF release 2 architectural framework and Implementation Agreements by subjecting them to interoperability testing based on realistic network scenarios. Global MSF Interoperability 2004 (GMI 2004) demonstrated a deployable and operationally ready IP telephony network with Network Management, enhanced Quality-of-Service (QoS) and security features. GMI2004 also demonstrated a service layer with application server, media server, and service broker functionality. GMI2004 provided an industry showcase that: • Assist carriers achieve their goal: to deploy flexible, best of breed products. • Assist vendors achieve their goal: to market products more cost effectively. • Display the global interoperability of the MSF architecture as referenced in the Release 2 architecture document. • Demonstrate a network scenario that can be managed to specific quality standards. The MSF welcomes feedback and comment and would encourage interested parties to get involved in this work program. Information about the MSF and membership options can be found on the MSF website xxxx://xxx.xxxxxxx.xxx/
Sample 1
AutoNDA by SimpleDocs

Related to Multiservice Switching Forum

  • Other Service Outages If there is a Service outage for any reason, such outage will prevent all Service, including 911 Dialing, from functioning. Such outages may occur for a variety of reasons, including, but not limited to, those reasons described elsewhere in this Agreement.

  • Packet Switching Capability 4.5.1 The packet switching capability network element is defined as the function of routing or forwarding packets, frames, cells or other data units based on address or other routing information contained in the packets, frames, cells or other data units.

  • Local Circuit Switching Capability, including Tandem Switching Capability 4.2.1 Local circuit switching capability is defined as: (A) line-side facilities, which include, but are not limited to, the connection between a loop termination at a main distribution frame and a switch line card; (B) trunk-side facilities, which include, but are not limited to, the connection between trunk termination at a trunk-side cross-connect panel and a switch trunk card; (C) switching provided by remote switching modules; and (D) all features, functions, and capabilities of the switch, which include, but are not limited to: (1) the basic switching function of connecting lines to lines, line to trunks, trunks to lines, and trunks to trunks, as well as the same basic capabilities made available to BellSouth’s customers, such as a telephone number, white page listings, and dial tone; and (2) all other features that the switch is capable of providing, including but not limited to customer calling, customer local area signaling service features, and Centrex, as well as any technically feasible customized routing functions provided by the switch. Any features that are not currently available but are technically feasible through the switch can be requested through the BFR/NBR process.

  • Tandem Switching 4.3.1 The Tandem Switching capability Network Element is defined as: (i) trunk- connect facilities, which include, but are not limited to, the connection between trunk termination at a cross connect panel and switch trunk card; (ii) the basic switch trunk function of connecting trunks to trunks; and (iii) the functions that are centralized in the Tandem Switches (as distinguished from separate end office switches), including but not limited to call recording, the routing of calls to operator services and signaling conversion features.

  • Service Outages (a) Service Outages Due to Power Failure or Disruption. 911 Dialing does not function in the event of a power failure or disruption. If there is an interruption in the power supply, the Service, including 911 Dialing, will not function until power is restored. Following a power failure or disruption, you may need to reset or reconfigure the Device prior to utilizing the Service, including 911 Dialing.

  • Provider Network The Panel of health service Providers with which the Contractor contracts for the provision of covered services to Members and Out-of-network Providers administering services to Members.

  • CLOUD SERVICE The Cloud Service offering, is described below and is specified in an Order Document for the selected entitled offerings. The Order Document will consist of the Quotation that is provided and the Proof of Entitlement (XxX) you will receive confirming the start date and term of the Cloud Services and when invoicing will commence.

  • AIN Selective Carrier Routing for Operator Services, Directory Assistance and Repair Centers 4.3.1 BellSouth will provide AIN Selective Carrier Routing at the request of <<customer_name>>. AIN Selective Carrier Routing will provide <<customer_name>> with the capability of routing operator calls, 0+ and 0- and 0+ NPA (LNPA) 555-1212 directory assistance, 1+411 directory assistance and 611 repair center calls to pre-selected destinations.

  • Service Levels Annex 1 to this Part A of this Call Off Schedule sets out the Service Levels the performance of which the Parties have agreed to measure. The Supplier shall monitor its performance of this Call Off Contract by reference to the relevant performance criteria for achieving the Service Levels shown in Annex 1 to this Part A of this Call Off Schedule (the Service Level Performance Criteria) and shall send the Customer a Performance Monitoring Report detailing the level of service which was achieved in accordance with the provisions of Part B (Performance Monitoring) of this Call Off Schedule. The Supplier shall, at all times, provide the Services in such a manner that the Service Levels Performance Measures are achieved. If the level of performance of the Supplier of any element of the provision by it of the Services during the Call Off Contract Period: is likely to or fails to meet any Service Level Performance Measure or is likely to cause or causes a Critical Service Failure to occur, the Supplier shall immediately notify the Customer in writing and the Customer, in its absolute discretion and without prejudice to any other of its rights howsoever arising including under Clause 12 of this Call Off Contract (Service Levels and Service Credits), may: require the Supplier to immediately take all remedial action that is reasonable to mitigate the impact on the Customer and to rectify or prevent a Service Level Failure or Critical Service Level Failure from taking place or recurring; and if the action taken under paragraph (a) above has not already prevented or remedied the Service Level Failure or Critical Service Level Failure, the Customer shall be entitled to instruct the Supplier to comply with the Rectification Plan Process; or if a Service Level Failure has occurred, deduct from the Call Off Contract Charges the applicable Service Level Credits payable by the Supplier to the Customer in accordance with the calculation formula set out in Annex 1 of this Part A of this Call Off Schedule; or if a Critical Service Level Failure has occurred, exercise its right to Compensation for Critical Service Level Failure in accordance with Clause 13 of this Call Off Contract (Critical Service Level Failure) (including subject, for the avoidance of doubt, the proviso in Clause 13.1.2 of this Call Off Contract in relation to Material Breach). Approval and implementation by the Customer of any Rectification Plan shall not relieve the Supplier of any continuing responsibility to achieve the Service Levels, or remedy any failure to do so, and no estoppels or waiver shall arise from any such Approval and/or implementation by the Customer. SERVICE CREDITS Annex 1 to this Part A of this Call Off Schedule sets out the formula used to calculate a Service Credit payable to the Customer as a result of a Service Level Failure in a given service period which, for the purpose of this Call Off Schedule, shall be a recurrent period of [one Month] during the Call Off Contract Period (the Service Period).

  • Scope of Service Interconnection Service shall be provided to the Interconnection Customer at the Point of Interconnection (a), in the case of interconnection of the Customer Facility of a Generation Interconnection Customer, up to the Maximum Facility Output, and (b), in the case of interconnection of the Customer Facility of a Transmission Interconnection Customer, up to the Nominal Rated Capability. The location of the Point of Interconnection shall be mutually agreed by the Interconnected Entities, provided, however, that if the Interconnected Entities are unable to agree on the Point of Interconnection, the Transmission Provider shall determine the Point of Interconnection, provided that Transmission Provider shall not select a Point of Interconnection that would impose excessive costs on either of the Interconnected Entities and shall take material system reliability considerations into account in such selection. Specifications for the Customer Facility and the location of the Point of Interconnection shall be set forth in an appendix to the Interconnection Service Agreement and shall conform to those stated in the Facilities Study.

Time is Money Join Law Insider Premium to draft better contracts faster.