USED FOR PROGRAMMING THE DATA PORT Clause Samples

USED FOR PROGRAMMING THE DATA PORT. If the CV is assigned as data then it can be related to a number of parameters which can be downloaded to a SOPHO-SET, SOPHO-▇▇▇ or ▇▇▇. The parameters are used for programming the data port of the SOPHO-SET, SOPHO-▇▇▇ or ▇▇▇. The SOPHO-SET, SOPHO-▇▇▇ or ▇▇▇ is connected to a DLC port via a 2B+D line. Each DLC port comprises 2 circuits which correspond to the user channels in the 2B+D line. - For a SOPHO-SET the second user channel (corresponding to an odd DLC-circuit) corresponds with the data port. - For a SOPHO-▇▇▇ either user channel (corresponding to the even and odd DLC-circuit) corresponds with the data port. - For a ▇▇▇ both user channels (corresponding to both the even and odd DLC-circuits) correspond with the data port. The DLC-circuit corresponding to a data port is assigned a DNR. A CV is assigned to the DNR as described above. This CV must be for data and subsequently have the additional interface parameters. The parameters are downloaded to the data port in the following circumstances: - Manual request with OM-command DOWNLD. - If the DLC-circuit is transferred to the service condition INS. - Whenever the SOPHO-SET, SOPHO-▇▇▇ or ▇▇▇ is connected to the telephone line. - Upon manual request of the user. - If the OM-command CHAGCV is used. Downloading involves sending the parameters of the CV to the SOPHO-SET, SOPHO-▇▇▇ or ▇▇▇ using the 2B+D protocol. The SOPHO-SET, SOPHO-▇▇▇ or ▇▇▇ interprets the values and programs the setting of the data port accordingly. The CV is created or changed using the OM-command CRCVAL or CHCVAL. It is assigned as either data (D) or voice (V). If the CV is assigned as data then the additional parameters can be defined. These additional parameters are separated into 4 groups: <V.24-circuits>, <speed+mode>, <miscellaneous>, <guard 1 + guard 2>. The parameters and their ranges for the SOPHO-SET 308, SOPHO-SET S375 D, SOPHO- SET P375 D, SOPHO-SET P370 D, SOPHO-▇▇▇ P375 and ▇▇▇ 308 are not all the same.
View Source

Related to USED FOR PROGRAMMING THE DATA PORT

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

  • Why We Collect Information and For How Long We are collecting your data for several reasons: · To better understand your needs and provide you with the services you have requested; · To fulfill our legitimate interest in improving our services and products; · To send you promotional emails containing information we think you may like when we have your consent to do so; · To contact you to fill out surveys or participate in other types of market research, when we have your consent to do so; · To customize our website according to your online behavior and personal preferences. The data we collect from you will be stored for no longer than necessary. The length of time we retain said information will be determined based upon the following criteria: the length of time your personal information remains relevant; the length of time it is reasonable to keep records to demonstrate that we have fulfilled our duties and obligations; any limitation periods within which claims might be made; any retention periods prescribed by law or recommended by regulators, professional bodies or associations; the type of contract we have with you, the existence of your consent, and our legitimate interest in keeping such information as stated in this Policy.

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

  • Availability of Verizon Telecommunications Services 3.1 Verizon will provide a Verizon Telecommunications Service to PNG for resale pursuant to this Attachment where and to the same extent, but only where and to the same extent that such Verizon Telecommunications Service is provided to Verizon’s Customers. 3.2 Except as otherwise required by Applicable Law, subject to Section 3.1 of this Attachment, Verizon shall have the right to add, modify, grandfather, discontinue or withdraw Verizon Telecommunications Services at any time, without the consent of PNG. 3.3 To the extent required by Applicable Law, the Verizon Telecommunications Services to be provided to PNG for resale pursuant to this Attachment will include a Verizon Telecommunications Service customer-specific contract service arrangement (“CSA”) (such as a customer specific pricing arrangement or individual case based pricing arrangement) that Verizon is providing to a Verizon Customer at the time the CSA is requested by PNG.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with ▇▇▇ ▇▇▇▇, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry. 1.1. The format of responses shall follow a semi-­‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.