CMA Semantics Sample Clauses

CMA Semantics. The following chapter defines the functional and data semantics of the Call Management Agent. The data maintained by a Call Management Agent consists of the following: • One or more CMAAs (Call Management Agent Addresses) which distinguish this agent from all other agents. • If this Call Management Agent is simply a redirection pointer or Soft Link to another CMA, the CMA contains the CMAA of the target being redirected to. This allows a user to gracefully change his Call Management Agent. For example, this capability would be used to leave a forwarding pointer for a user who changes his E.164 telephone number, or his provider-based E-mail address. • If this is a terminal Call Management Agent representing a callee, the CMA contains a set of Communication Terminal Specifiers (CTSPECs), one for each of the communication devices a VoIP client operating on behalf of this user’s CMA has registered with the Call Management Agent Server.
AutoNDA by SimpleDocs

Related to CMA Semantics

  • Project Team Cooperation Partnering 1.1.3 Constitutional Principles Applicable to State Public Works Projects.

  • Development Services During the term of this Agreement, the Provider agrees to provide to or on behalf of the Port the professional services and related items described in Exhibit A (collectively, the “Development Services”) in accordance with the terms and conditions of this Agreement. The Provider specifically agrees to include at least one Port representative in any economic development negotiations or discussions in which the Provider is involved concerning (i) a port-related business prospect or (ii) a business transaction which will ultimately require Port involvement, financial or otherwise.

  • Collaboration We believe joint effort toward common goals achieves trust and produces greater impact for L.A. County’s youngest children and their families.

  • OVATIONS FOOD SERVICES, L.P. dba SPECTRA All food and beverage service must be discussed with and approved by Spectra, the OCFEC Master Concessionaire. FORM F-31 AGREEMENT NO. R-026-18 DATE May 16, 2018 REVIEWED APPROVED RENTAL AGREEMENT FAIRTIME INTERIM XX THIS AGREEMENT by and between the 32nd District Agricultural Association dba OC Fair & Event Center, hereinafter called the Association, and B & L Productions, Inc. hereinafter, called the Rentor

  • Supply Chain Monitoring A copy of the supply chain monitoring process, which should include details of the process for monitoring the financial viability of the supply chain (including timing), together with any known risks to supply chain stability and material changes to the supply chain. This should include extracts from Board level meetings, risk registers etc where any of the above items have been discussed. Annex 1 1 Information from Contractors who are not required to submit form AR01 to Companies House

  • Secondary Systems The Developer and Connecting Transmission Owner shall each cooperate with the other in the inspection, maintenance, and testing of control or power circuits that operate below 600 volts, AC or DC, including, but not limited to, any hardware, control or protective devices, cables, conductors, electric raceways, secondary equipment panels, transducers, batteries, chargers, and voltage and current transformers that directly affect the operation of Developer or Connecting Transmission Owner’s facilities and equipment which may reasonably be expected to impact the other Party. The Developer and Connecting Transmission Owner shall each provide advance notice to the other Party, and to NYISO, before undertaking any work on such circuits, especially on electrical circuits involving circuit breaker trip and close contacts, current transformers, or potential transformers.

  • Program Monitoring The Contractor will make all records and documents required under this Agreement as outlined here, in OEC Policies and NHECC Policies available to the SRO or its designee, the SR Fiscal Officer or their designee and the OEC. Scheduled monitoring visits will take place twice a year. The SRO and OEC reserve the right to make unannounced visits.

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity

  • 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.

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