SIST ETS 300 243-1 E1:2003
(Main)Terminal Equipment (TE); Programmable Communication Interface (PCI) APPLI/COM for facsimile group 3, facsimile group 4, teletex and telex services; Part 1: CCITT Recommendation T.611 (1992) [modified]
Terminal Equipment (TE); Programmable Communication Interface (PCI) APPLI/COM for facsimile group 3, facsimile group 4, teletex and telex services; Part 1: CCITT Recommendation T.611 (1992) [modified]
Easy access from local applications to communication applications & vice versa.
Terminalska oprema (TE) – Programirljivi komunikacijski vmesnik (PCI) – APPLI/COM za faksimilno skupino 3, faksimilno skupino 4 ter storitve teletex in telex – 1. del: Priporočilo CCITT T.611 (1992) [spremenjeno]
General Information
Standards Content (Sample)
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
Recommendation T.611 (1992) [modified]
Ta slovenski standard je istoveten z: ETS 300 243-1 Edition 1
ICS:
33.050.30 Oprema za teleks, teletekst, Equipment for telex, teletext,
telefaks telefax
35.180 Terminalska in druga IT Terminal and other
periferna oprema IT peripheral equipment
SIST ETS 300 243-1 E1:2003 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST ETS 300 243-1 E1:2003
---------------------- Page: 2 ----------------------
SIST ETS 300 243-1 E1:2003
EUROPEAN ETS 300 243-1
TELECOMMUNICATION November 1995
STANDARD
Source: ETSI TC-TE Reference: DE/TE-02015-1
ICS: 35.180, 33
PCI, APPLI/COM, facsimile, teletex, telex
Key words:
Terminal Equipment (TE);
Programmable Communication Interface (PCI) APPLI/COM for
facsimile group 3, facsimile group 4, teletex and telex services
Part 1: CCITT Recommendation T.611 (1992) [modified]
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
F-06921 Sophia Antipolis CEDEX - FRANCE
Postal address:
650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Office address:
c=fr, a=atlas, p=etsi, s=secretariat - secretariat@etsi.fr
X.400: Internet:
Tel.: +33 92 94 42 00 - Fax: +33 93 65 47 16
*
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1995. All rights reserved.
---------------------- Page: 3 ----------------------
SIST ETS 300 243-1 E1:2003
Page 2
ETS 300 243-1: November 1995
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.
---------------------- Page: 4 ----------------------
SIST ETS 300 243-1 E1:2003
Page 3
ETS 300 243-1: November 1995
Foreword
This European Telecommunication Standard (ETS) was produced by the Terminal Equipment (TE)
Technical Committee of the European Telecommunications Standards Institute (ETSI).
This ETS comprises two parts:
"Terminal Equipment (TE); Programming Communication Interface (PCI) APPLI/COM for facsimile group
3, facsimile group 4, teletex and telex services;
Part 1: CCITT Recommendation T.611 (1992) [modified],
Part 2: Conformance testing".
Transposition dates
Date of adoption of this ETS: 10 November 1995
Date of latest announcement of this ETS (doa): 29 February 1996
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 August 1996
Date of withdrawal of any conflicting National Standard (dow): 31 August 1996
Endorsement Notice
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
modifications as given below.
NOTE: New or modified text is indicated using side bars.
Normative references
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
edition of the publication referred to applies:
[1] CCITT Recommendation T.611 (1992): "Programmable Communication
Interface (PCI) APPLI/COM for facsimile group 3, facsimile group 4, teletex and
telex services".
---------------------- Page: 5 ----------------------
SIST ETS 300 243-1 E1:2003
Page 4
ETS 300 243-1: November 1995
Application guidelines and common modifications to CCITT Recommendation
T.611
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
to CCITT Recommendation T.611 [1].
1) Delete the scope statement (clause 2) and insert the following:
2 Scope
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)
and the Communication Application (CA).
The technical description of the APPLI/COM interface is contained in CCITT Recommendation
T.611 (1992) [1].
For the application of Part 2, this ETS contains application guidelines and amendments to be applied to
CCITT Recommendation T.611 [1] to fulfil the requirements of ETS 300 243-2.
2) Page 1, clause 1, replace 3rd paragraph starting with "The APPLI/COM interface can be
used." by the following:
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
dialogue facility.
3) Page 1, subclause 1.1, replace the headline "1.1 Normative References" by:
1.1 Informative references.
4) Page 1, subclause 1.1, add the following two informative references:
- 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
..." by the following:
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.
---------------------- Page: 6 ----------------------
SIST ETS 300 243-1 E1:2003
Page 5
ETS 300 243-1: November 1995
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.
However, the structure shown as follows makes their use more evident:
Table 1: CA-Descriptor information items independent of operating system or exchange
mechanism
1)
Keyword Parameter Interpretation
APPLICOM String Shall be the first definition of a CA-Descriptor. The keyword is
followed by any string, in order to identify the manufacturer of the
CA, for instance.
DRF "yes" | "no" States whether the CA supports the “Dispatch Received Files”
facility.
EM "file" | "primitive" Exchange Method used to interchange TDDs between LAs and
CAs. "file" and "primitive" are the supported values (see annex 5 for
further details).
CODING* Code-ID Specifies which TDD encoding scheme is supported by the CA. See
annex C for the supported values that can be specified.
COUNTRY String Specifies the country for which the CA is configured. Used to
register country specific features like gaining access to the
conversion facility or accessing the black list of dialling numbers.
The value to be placed in the parameter is to be taken from CCITT
Recommendation T.35. It shall be presented as a decimal counted,
numeric string, i.e. "154" for the Seychelles.
FC "A" | "B" States which Functional Class the CA supports.
TLX "STD" Used only if the CA offers the Telex service. In this case, the value
“STD” shall be specified.
TX "STD" Used only if the CA offers the Telex service through a Teletex
gateway. In this case, the value “STD” shall be specified.
TTX* "STD", "OPD", Used only if the CA offers the Teletex service. In this case, in the
"MD", "CTL", minimum the value “STD” shall be specified.
"DTM", "BFT", "EDI"
FX3* "STD", "BTM", Used only if the CA offers the Facsimile Group 3 service. In this
"DTM", "BFT", "EDI" case, in the minimum the value “STD” shall be specified.
FX4* "STD", "OPD", Used only if the CA offers the Facsimile Group 4 service. In this
"MD", "CTL", case, in the minimum the value “STD” shall be specified.
"DTM", "BFT", "EDI"
(continued)
1)
A '*' (star) at the end of a keyword indicates that this keyword may be repeated.
---------------------- Page: 7 ----------------------
SIST ETS 300 243-1 E1:2003
Page 6
ETS 300 243-1: November 1995
Table 1 (concluded): CA-Descriptor information items independent of operating system or
exchange mechanism
Keyword Parameter Interpretation
ADDKEYS* keyword Lists all the additional keywords supported by the CA. Only
keywords classified as “+” in the TDD tables of clause 7 may be
specified here.
EXTEND* keyword Provides the possibility for extensions to the Recommendation. Can
only be implemented as formal changes to the Recommendation. All
the CA-supported keywords shall be listed.
NATIONAL* keyword Provides the possibility for national extensions to the
Recommendation. Can only be implemented with the approval of
national administrations. (All supported keywords shall be listed).
PRIVATE* keyword Provides the possibility for private extensions to the
Recommendation. (All supported keywords shall be listed).
SUBMIT* "PRINT", Declares which functions are supported in the Submit TDD function.
"CONVERT", This keyword shall be repeated as many times as required.
"CHECK"
CONVCHK* Convert-ID Declares which transfer formats are supported in the Submit TDD
function CONVERT and/or CHECK.
PRINT* Print-ID Declares which printers could be addressed by the CA in the Submit
TDD function PRINT.
CODEPAGE* string Specifies the additional code pages for the extended ASCII
character sets the CA supports. String indicates the number of the
code page (e.g. "850").
RECORD* keyword, integer Gives the complete list of CA-Record field names supported by the
CA, in the order they are found in the file resulting from the
TRACE:COPY function. The CA shall state the keyword followed by
- and separated by comma - the length the field will have in the
resulting file.
ENVIRON* "MSDOS", This keyword specifies the operating environment of the CA. If a CA
"WINDOWS", supports several environments, the ICE shall contain as many
"UNIX", "OS2", ENVIRON keyword instances as the number of different operating
"MacOS" systems supported.
Table 1a: CA-Descriptor information items applying for the file exchange mechanism
Keyword Parameter Interpretation
SYNC "yes" | "no" Indicates whether the CA is “sync-driven”. See annex E for further
details.
F_JOB_Q Path Specifies the path of the TDD request files. See annex E for further
details.
F_ACK_Q Path Specifies the path of the TDD response files. See annex E for
further details.
ERROR_Q Path Specifies the path of the TDD response files relating to errors. See
annex E for further details.
Table 1b: CA-Descriptor information items applying to the primitive exchange mechanism,
any operating system
Keyword Parameter Interpretation
ALARM "yes" | "no" States whether the CA supports the SetAlarm function.
---------------------- Page: 8 ----------------------
SIST ETS 300 243-1 E1:2003
Page 7
ETS 300 243-1: November 1995
Table 1c: CA-Descriptor information items applying to the primitive exchange mechanism,
MS/DOS operating system
Keyword Parameter Interpretation
DRIVER Path Name of the driver that shall be opened to initiate dialogues with the
CA. See annex E for further details.
2)
INT hex,hex Indicates the interrupt number. Two hexadecimal numbers; the first
specifies the multiplex number, the second the program code
number. If the interrupt is not multiplexed, then the second hex
number shall not be specified.
LIB "yes" | "no" CA is a static library (LA shall be linked to it).
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,
WINDOWS system
Keyword Parameter Interpretation
3)
INT hex,hex Indicates the interrupt number. Two hexadecimal numbers; the first
specifies the multiplex number, the second the program code
number. If the interrupt is not multiplexed, then the second hex
number shall not be specified.
LIB "yes" | "no" CA is a static library (LA shall be linked to it).
LIB-NAME* Path Path(s) of the library(ies) (used in conjunction with the LIB keyword).
DLL "yes" | "no" Dynamic Link Library. See annex E. The ‘DLL-NAME’ keyword shall
be supported only if the DLL exchange mechanism is supported.
DLL-NAME* Path Path(s) of the DLL file(s) (used in conjunction with the DLL
keyword).
DDE "yes" | "no" Dynamic Data Exchange mechanism. In the WINDOWS
environment if the application supports the DDE exchange
mechanism, it shall specify "yes". See annex E. The next three
keywords shall be included in the ICE if the DDE mechanism is
used.
WIN-APP String Application Name (MsDos format) XXXXXXXX.XXX.
SUBJECT* String All CA "Subjects" shall be mentioned (if any) otherwise leave empty
(to be used with the DDE keyword).
ITEM* String All CA "Items" shall be mentioned (if any) otherwise leave empty (to
be used with the DDE keyword).
Table 1e: CA-Descriptor information items applying to the primitive exchange mechanism,
OS/2 operating system
Keyword Parameter Interpretation
For Further Study
Table 1f: CA-Descriptor information items applying to the primitive exchange mechanism,
UNIX operating system
Keyword Parameter Interpretation
For Further Study
2)
Note that the syntax has changed from the original i.e. the original syntax stated "hex-hex", and it reads "hex,hex" now.
3)
Note that the syntax has changed from the original i.e. the original syntax stated "hex-hex", and it reads "hex,hex" now.
---------------------- Page: 9 ----------------------
SIST ETS 300 243-1 E1:2003
Page 8
ETS 300 243-1: November 1995
Table 1g: CA-Descriptor information items applying to the primitive exchange mechanism,
MacOS operating system
Keyword Parameter Interpretation
For Further Study
7) Page 19, subclause 7.4.1, 1st paragraph, add the following text just in front of last sentence
("For clarification purposes .") of the 1st paragraph:
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
subclause 7.4.3).
NOTE: The TRACE functionality is available through CAs conforming to functional class B
(FCB).
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
also table 21/T.611 [1]):
"+" document successfully and completely transmitted;
" - " transmission failed, all attempts to transmit are given up by CA;
"+-" transmission partially failed, parts are already transmitted, but no complete transmission
could be achieved!.
9) Page
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.