Control Interface Sample Clauses

Control Interface. There are two ways of a driver to control the behaviour of the cruise control system: (i) using the pedals to (temporarily) deactivate the cruise control system, and (ii) using the control elements provided by the operating lever. The control elements provided by the operating lever may vary slightly be- tween car manufacturers. However, the functions that can be controlled using
AutoNDA by SimpleDocs
Control Interface. XXX XXX is a signaling protocol but can be used for Media Server control through one key restriction -- that the Media Server always receives INVITES, never sends them -- and by some clean extensions to allow media processing operations to be requested and notified, e.g. [NETANN], [AU], [MSML/MOML], and [VoiceXML]. These key specifications for Media Server control are highlighted below. Specification "SIP MS IA" Restrictions SIP Signaling [ MSFCORE ] Implementation Agreement for CORE SIP Profile, for Voice over IP Version 2 The Media Server fulfills the role of UAS and UAC. UDP is mandatory, TCP is optional. INFO support is optional, depends on usage, e.g. MSML, MOML, AU package. Media Server SIP [NETANN] Basic Network Media Services with SIP Support is optional. [AU] IA for SIP Media Server Interface with MGCP AU Package Support is optional. See msf2004.120.02. [MSML] Media Sessions Markup Language (MSML) Support is optional. [MOML] Media Objects Markup Language (MOML) Support is optional. Other [VOICEXML] Voice Extensible Markup Language (VoiceXML) Support is optional. ASR and TTS are optional <transfer> element is optional (Note: VoiceXML is invoked using Netann or MSML) Legend and Notes Note 1: MSCML is another alternative Media Server SIP interface but not considered for MSF.
Control Interface. SDP Specification "SIP MS IA" Restrictions [SDP] Session Description Protocol (SDP) None [SDPOA] Offer/Answer Model with SDP None [RESMGMT] Resource management Support is optional.

Related to Control Interface

  • Technical Interfaces 3.2.6.1 The Interconnection facilities provided by each Party shall be formatted using either Alternate Xxxx Inversion (AMI) line code with Superframe format framing or Bipolar 8-Zero Substitution with Extended Superframe (B8ZS ESF) format framing or any mutually agreeable line coding and framing.

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • Network Interface Device (NID) 2.7.1 The NID is defined as any means of interconnection of end-user customer premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single-line termination device or that portion of a multiple-line termination device required to terminate a single line or circuit at the premises. The NID features two independent xxxxxxxx or divisions that separate the service provider’s network from the end user’s customer-premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the end user each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable.

  • Network Interface Device 2.7.1 The NID is defined as any means of interconnection of the End User’s customer premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single line termination device or that portion of a multiple line termination device required to terminate a single line or circuit at the premises. The NID features two independent xxxxxxxx or divisions that separate the service provider’s network from the End User’s premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the End User each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable.

  • Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.

  • Workstation Encryption Supplier will require hard disk encryption of at least 256-bit Advanced Encryption Standard (AES) on all workstations and/or laptops used by Personnel where such Personnel are accessing or processing Accenture Data.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Local Interconnection Data Exchange for Billing 7.7.1 There are certain types of calls or types of Interconnection that require exchange of Billing records between the Parties, including, for example, alternate billed and Toll Free Service calls. The Parties agree that all call types must be routed between the networks, accounted for, and settled among the Parties. Certain calls will be handled via the Parties' respective operator service platforms. The Parties agree to utilize, where possible and appropriate, existing accounting and settlement systems to xxxx, exchange records and settle revenue.

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

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