DTMF/COLLECTION SPECIFICATION Sample Clauses

DTMF/COLLECTION SPECIFICATION. DOWNLOAD (0x20) For this command, the CMD_params field contains an ID of the Collection Specification, followed by all DTMF Collection Specification parameters. Upon receipt of this command, the DSP will copy the values to the default DTMF Collection Specification with this ID. Table 7-9 shows the format of the DTMF/COLLECTION SPECIFICATION DOWNLOAD command. 91 EVP-SRM (DSP) Software Design Specification 69 ------------------------------------------------------------------------ ----------------------------------------------------------------------------- Field Length Value Description ----------------------------------------------------------------------------- CMD _type 4 bits 0x2 DTMF DETECTION type ----------------------------------------------------------------------------- CMD _subtype 4 bits 0x1 Collection Specification Download ----------------------------------------------------------------------------- CMD _channel 1 byte 0x00 Command is not channel specific ----------------------------------------------------------------------------- CMD _length 1 byte 0x0E Length of this message ----------------------------------------------------------------------------- CMD _params 11 bytes * All Collection Specification values ----------------------------------------------------------------------------- Table 7-9: ASDF REMOVE CMD_CHANNEL DTMF/COLLECTION SPECIFICATION DOWNLOAD (0x20) Command
View Source

Related to DTMF/COLLECTION SPECIFICATION

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-▇▇▇▇▇-▇▇▇▇▇▇▇-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-▇▇▇▇▇-▇▇▇▇▇▇▇-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • Packing Specifications 7.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.