ETSI ETS 300 243-1 ed.1 (1995-11)

SLOVENSKI STANDARD
SIST ETS 300 243-1 E1:2003
01-december-2003
7HUPLQDOVNDRSUHPD7(±3URJUDPLUOMLYLNRPXQLNDFLMVNLYPHVQLN3&,±
$33/,&20]DIDNVLPLOQRVNXSLQRIDNVLPLOQRVNXSLQRWHUVWRULWYHWHOHWH[LQ
WHOH[±GHO3ULSRURþLOR&&,777>VSUHPHQMHQR@
Terminal Equipment (TE); Programmable Communication Interface (PCI) APPLI/COM

for facsimile group 3, facsimile group 4, teletex and telex services; Part 1: CCITT

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the

Whilst every care has been taken in the preparation and publication of this document, errors in content,

typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to

"ETSI Editing and Committee Support Dept." at the address shown on the title page.

This European Telecommunication Standard (ETS) was produced by the Terminal Equipment (TE)

Technical Committee of the European Telecommunications Standards Institute (ETSI).

"Terminal Equipment (TE); Programming Communication Interface (PCI) APPLI/COM for facsimile group

CCITT Recommendation T.611 (1992) [1] provides the technical description of the APPLI/COM interface.

The text of CCITT Recommendation T.611 (1992) [1] was approved by ETSI as an ETS with the agreed

Part 1 of this ETS incorporates by dated or undated reference, provisions from an other publication. This

normative reference is cited at the appropriate places in the text and the publication is listed hereafter. For

dated references, subsequent amendments to or revisions of any of these publications apply to this Part

of the ETS only when incorporated in it by amendment or revision. For undated references the latest

The following modifications define how CCITT Recommendation T.611 [1] shall be interpreted. Areas

which may be ambiguous are addressed and clarified. All remarks, references and comments are related

Part 1 of this European Telecommunication Standard (ETS) describes the high layer software interface

APPLI/COM, located inside a terminal equipment between two logical entities, the Local Application (LA)

The technical description of the APPLI/COM interface is contained in CCITT Recommendation

For the application of Part 2, this ETS contains application guidelines and amendments to be applied to

2) Page 1, clause 1, replace 3rd paragraph starting with "The APPLI/COM interface can be

The APPLI/COM interface can be used in communication equipment to give access to the facsimile group

3, facsimile group 4, teletex and telex services. The access to the telex services does not include the

- Recommendation F.59, General characteristics of the international telex service.

- Recommendation F.60, Operational provisions for the international telex service.

5) Page 12, subclause 6.3.2, replace complete subclause, starting with "This section describes

This section describes the syntax of the ICE. The first syntax element in the ICE is always the APPLI/COM

Header. No other elements, including SPACE and TABULATION format effectors are allowed before.

Following are the CA-Descriptors. A CA-Descriptor is introduced by a single line containing a '#'

(NUMBER SIGN) as first element. The detailed syntax is described in BNF-based grammar in annex A.

6) Pages 13, 14, 15 and subclause 6.3.3, table 1, describing the ICE components shall be

replaced by the text and tables shown below. These tables contain the same information as

the table provided by CCITT Recommendation T.611 [1] with minor editorial corrections.

Table 1: CA-Descriptor information items independent of operating system or exchange

TTX* "STD", "OPD", Used only if the CA offers the Teletex service. In this case, in the

FX3* "STD", "BTM", Used only if the CA offers the Facsimile Group 3 service. In this

FX4* "STD", "OPD", Used only if the CA offers the Facsimile Group 4 service. In this

A '*' (star) at the end of a keyword indicates that this keyword may be repeated.

Table 1 (concluded): CA-Descriptor information items independent of operating system or

EXTEND* keyword Provides the possibility for extensions to the Recommendation. Can

SUBMIT* "PRINT", Declares which functions are supported in the Submit TDD function.

CONVCHK* Convert-ID Declares which transfer formats are supported in the Submit TDD

PRINT* Print-ID Declares which printers could be addressed by the CA in the Submit

RECORD* keyword, integer Gives the complete list of CA-Record field names supported by the

ENVIRON* "MSDOS", This keyword specifies the operating environment of the CA. If a CA

Table 1a: CA-Descriptor information items applying for the file exchange mechanism

SYNC "yes" | "no" Indicates whether the CA is “sync-driven”. See annex E for further

F_JOB_Q Path Specifies the path of the TDD request files. See annex E for further

ERROR_Q Path Specifies the path of the TDD response files relating to errors. See

Table 1b: CA-Descriptor information items applying to the primitive exchange mechanism,

Table 1c: CA-Descriptor information items applying to the primitive exchange mechanism,

DRIVER Path Name of the driver that shall be opened to initiate dialogues with the

LIB-NAME* Path Path(s) of the library(ies) (used in conjunction with the LIB keyword).

Table 1d: CA-Descriptor information items applying to the primitive exchange mechanism,

LIB-NAME* Path Path(s) of the library(ies) (used in conjunction with the LIB keyword).

SUBJECT* String All CA "Subjects" shall be mentioned (if any) otherwise leave empty

ITEM* String All CA "Items" shall be mentioned (if any) otherwise leave empty (to

Table 1e: CA-Descriptor information items applying to the primitive exchange mechanism,

Table 1f: CA-Descriptor information items applying to the primitive exchange mechanism,

Note that the syntax has changed from the original i.e. the original syntax stated "hex-hex", and it reads "hex,hex" now.

Note that the syntax has changed from the original i.e. the original syntax stated "hex-hex", and it reads "hex,hex" now.

Table 1g: CA-Descriptor information items applying to the primitive exchange mechanism,

7) Page 19, subclause 7.4.1, 1st paragraph, add the following text just in front of last sentence

If an LA wants to send to a list of recipients it shall use the SEND functionality (using the ADDRLIST

keyword. The transmission status is not available through this function (there is no Response-TDD

generated). However, the status of the transmission can be obtained using the TRACE functionality (see

NOTE: The TRACE functionality is available through CAs conforming to functional class B

8) Page 19, subclause 7.4.1, 2nd paragraph, add following text to the end of the 2nd paragraph:

So, whenever the Response-TDD is available, the LA can relay definitely on contents of the status

parameter showing the result of the transmission. The status parameter will indicate the following (see

"+-" transmission partially failed, parts are already transmitted, but no complete transmission