SIST ETS 300 325 E1:2003
(Main)Integrated Services Digital Network (ISDN); Programming Communication Interface (PCI) for Euro-ISDN
- Abstract
To specify a PCI that may be used by application to access Euro ISDN, including binding to the most common operating systems
- Status
- Published
- Publication Date
- 30-Nov-2003
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Dec-2003
- Due Date
- 01-Dec-2003
- Completion Date
- 01-Dec-2003
- Mandate
- T-235/1
SIST ETS 300 325 E1:2003 is the Slovenian adoption of ETS 300 325 Edition 1, published by ETSI. It specifies the Integrated Services Digital Network (ISDN) Programming Communication Interface (PCI) for Euro-ISDN, a software interface for application access to ISDN services and administration, with bindings for common operating systems. It is written for application developers, ISDN adapter and system software implementors, and people choosing or integrating ISDN equipment.
What does SIST ETS 300 325 E1:2003 specify?
SIST ETS 300 325 E1:2003 specifies the ISDN PCI for accessing and administering Euro-ISDN bearer services, supplementary services, and Virtual Circuit (VC) or Permanent Virtual Circuit (PVC) bearer services on the B- and D-channels. The standard covers both Basic and Primary rate ISDN access and defines a platform-independent interface with operating system and language bindings for common environments.
The document is organized around the interface model, message definitions, the exchange mechanism, and security. Its main structure is:
| Annex | What it covers |
|---|---|
| Annex A | Bibliography |
| Annex B | Mapping between ISDN PCI messages and supported protocols |
| Annex C | Telephony and external equipment support |
| Annex D | CCITT Recommendation X.25 usage |
| Annex E | NAF development guidelines |
| Annex F | Operating system-specific implementation |
| Annex G | PCI ICS proforma |
| Annex H | Static attribute content |
| Annex J | Sample operating system-specific C code |
| Annex K | TLV coder/decoder sample |
What are the key requirements of SIST ETS 300 325 E1:2003?
SIST ETS 300 325 E1:2003 is built around three planes and a message-based exchange between the PCI User Facility (PUF) and the Network Access Facility (NAF). In practice, that means software must create a connection object, exchange the right plane-specific messages, and manage identifiers so requests and responses stay linked.
The three-plane model
Clause 5 separates the interface into the Administration Plane, Control Plane, and User Plane. The Administration Plane manages attribute sets, addresses, Network Connection Objects (NCOs), security, and manufacturer-specific features; the Control Plane handles call control and related signalling; the User Plane carries user data and protocol traffic.
Connection control through NCOs
The PUF creates an NCO before it can use signalling or data transfer. Clause 5 explains two ways to configure an NCO: by referencing a standardized attribute set or by supplying the full configuration at creation time. This matters because it determines whether an implementor uses predefined profiles from Annex H or assembles parameters explicitly.
Control Plane and supplementary services
The Control Plane provides connection establishment, breakdown, user-to-user information transfer, adjournment of calls, facility invocation, and external equipment indications. The standard identifies supplementary services such as MSN, DDI, CLIP, CLIR, SUB, AOC-D, AOC-E, CW, COLP, and COLR, and notes that transparent coding is available as an optional feature. For a buyer or integrator, this shows which ISDN call features a product can expose through the interface.
User Plane access modes
Clause 5 defines two User Plane accesses: Network layer Message Access (NMA) and Transparent Message Access (TMA). NMA supports connection-mode services such as CCITT Recommendation X.213 based operation, while TMA gives byte-synchronized transparent access to the physical layer. The practical difference is whether the application wants protocol-managed data transport or direct channel access.
Exchange mechanism and operating system bindings
Clause 7 defines the exchange phases and functions: PciGetHandles, PciGetProperty, PciRegister, PciDeregister, PciPutMessage, PciGetMessage, and PciSetSignal. Annex F adapts these functions for DOS, Windows, and Unix. In practice, this is the part developers use to bind an application to a specific NAF and move messages in a portable way.
Error handling and selection rules
Clause 5.8 and Clause 6 define function return codes, message errors, and selection criteria when multiple NCOs match an incoming call. The standard also defines how mandatory, conditional, and optional parameters are treated, and how repeated parameters are handled. This matters because implementations must validate messages consistently and report failures through the specified plane and code paths.
What terms does SIST ETS 300 325 E1:2003 define?
- PUF - PCI User Facility, the local application or higher-layer entity using the ISDN PCI.
- NAF - Network Access Facility, the provider side that gives the PUF access to ISDN services.
- NCO - Network Connection Object, the abstract object that holds the configuration for one user connection.
- NCOID - the identifier returned for an NCO and used in later operations on that connection.
- NMA - Network layer Message Access, the User Plane access for network-layer protocol traffic.
- TMA - Transparent Message Access, the User Plane access for transparent byte-stream communication.
- SMA - Signalling Message Access, the control-side access to ISDN signalling.
Who uses SIST ETS 300 325 E1:2003?
SIST ETS 300 325 E1:2003 is used by software developers who need a standardized application interface to Euro-ISDN, by ISDN adapter and system software manufacturers, and by implementors who must map PCI messages onto a specific operating system. It is also useful to purchasers and technical managers who need to compare ISDN products by interface capability, supported planes, and supported protocols.
Which standards are used with SIST ETS 300 325 E1:2003?
| Standard | What it contributes |
|---|---|
| ETS 300 080 | ISDN lower layer protocols for telematic terminals |
| ETS 300 102-1 | Basic call control on the user-network interface layer 3 |
| ETS 300 196 | Supplementary services framework used with the PCI |
| ISO/IEC 8208 | X.25 Packet Layer Protocol |
| ISO 7776 | X.25 LAPB-compatible data link procedures |
| ISO/IEC 9646 | Conformance testing methodology and framework |
| ISO/IEC ISP 10609 | Connection-mode Transport Service profile |
| CCITT Recommendation X.213 | OSI Network Service Definition used by the User Plane |
| ISO/IEC 9899 | Programming Language-C |
| ETR 018 | Use of BC-, HLC- and LLC-information elements |
What does the SIST ETS 300 325 E1:2003 document contain?
The document contains a functional model, the message set for each plane, parameter conventions, and detailed definitions of identifiers used by the interface. It also includes message tables, selection criteria for incoming calls, and error codes for administration, control, and user-plane processing.
It further provides the exchange method between PUF and NAF, including registration, conversation, and deregistration phases, plus operating system-specific implementation guidance for DOS, Windows, and Unix. Annex C covers telephony-oriented external equipment, Annex D covers X.25 usage, Annex G provides the PCI ICS proforma, and Annex H lists static attribute content used to configure standardized connections.
Get Certified
Connect with accredited certification bodies for this standard
ANCE
Mexican certification and testing association.
Intertek Slovenia
Intertek testing, inspection, and certification services in Slovenia.
LNE (Laboratoire National de Métrologie et d'Essais)
French national laboratory for metrology and testing.
Sponsored listings
Frequently Asked Questions
SIST ETS 300 325 E1:2003 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Integrated Services Digital Network (ISDN); Programming Communication Interface (PCI) for Euro-ISDN". This standard covers: To specify a PCI that may be used by application to access Euro ISDN, including binding to the most common operating systems
To specify a PCI that may be used by application to access Euro ISDN, including binding to the most common operating systems
SIST ETS 300 325 E1:2003 is classified under the following ICS (International Classification for Standards) categories: 33.080 - Integrated Services Digital Network (ISDN). The ICS classification helps identify the subject area and facilitates finding related standards.
SIST ETS 300 325 E1:2003 is associated with the following European legislation: Standardization Mandates: T-235/1. When a standard is cited in the Official Journal of the European Union, products manufactured in conformity with it benefit from a presumption of conformity with the essential requirements of the corresponding EU directive or regulation.
SIST ETS 300 325 E1:2003 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Digitalno omrežje z integriranimi storitvami (ISDN) – Programirljivi telekomunikacijski vmesniki (PCI) za Euro-ISDNIntegrated Services Digital Network (ISDN); Programming Communication Interface (PCI) for Euro-ISDN33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:ETS 300 325 Edition 1SIST ETS 300 325 E1:2003en01-december-2003SIST ETS 300 325 E1:2003SLOVENSKI
STANDARD
EUROPEANETS 300 325TELECOMMUNICATIONMarch 1994STANDARDSource: ETSI TC-TEReference: DE/TE-02029ICS:33.080Key words:ISDN, PCIIntegrated Services Digital Network (ISDN);Programming Communication Interface (PCI) for Euro-ISDNETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.frTel.: +33 92 94 42 00 - Fax: +33 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1994. All rights reserved.SIST ETS 300 325 E1:2003New presentation - see History box
Page 2ETS 300 325: March 1994Whilst 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.SIST ETS 300 325 E1:2003
Page 3ETS 300 325: March 1994ContentsForeword.11Introduction.111Scope.132Normative references.133Definitions and abbreviations.143.1Definitions.143.2Abbreviations.154Reader's guidance and overview.164.1Reader's guide.164.2How to use this ETS.164.3Overview.174.3.1Background.174.3.2Functional overview.184.3.3Connection management.184.3.4The planes.184.3.5Properties.194.3.6External equipment (i.e. telephony).194.3.7ISDN accesses and the multi-applications environment.194.3.8Exchange Mechanism.195Functional model.205.1Introduction.205.2Architecture.205.2.1ISDN PCI and its components.205.2.2ISDN PCI architecture.215.2.3OSI location.225.2.4Co-ordination cases.235.3Functionality.255.3.1Introduction.255.3.2Resource management.265.3.2.1Attribute sets.265.3.2.2Network connection objects.265.3.2.3Support of external equipment.275.3.2.4Support of security features.295.3.2.5Support of manufacturer specific features.295.3.3Connection management.295.3.3.1Connection set-up and removal.295.3.3.2Support of supplementary services.305.3.4Data management.305.3.4.1Connection via the Network layer Message Access(NMA).315.3.4.2Connection via the Transparent Message Access (TMA).315.4Relating functionality to planes.315.4.1Optional features.315.4.2Administration Plane.325.4.3Control Plane.325.4.4User Plane.335.4.4.1The transparent access.335.4.4.2The network layer access.335.5PUF NAF interactions.345.6Total interaction overview.365.7Identifiers.38SIST ETS 300 325 E1:2003
Page 4ETS 300 325: March 19945.8Error handling.395.8.1Overview.395.8.2Function error handling.395.8.3Message error handling.396Description of ISDN PCI messages.406.1Conventions.406.1.1Address conventions.406.1.2Provision of information.406.1.3Message conventions.416.1.4Parameter conventions.416.1.4.1Parameter ordering.416.1.4.2Parameter repetition.416.1.4.3Parameter checking.416.1.5Default philosophy.416.2Administration Plane messages.426.2.1ACreateNCOReq.436.2.2NCOType and conditional parameter specification.446.2.3ACreateNCOCnf.456.2.4ADestroyNCOReq.456.2.5ADestroyNCOCnf.466.2.6AErrorInd.466.2.7AGetNCOInfoReq.466.2.8AGetNCOInfoCnf.476.2.9ASecurityReq.476.2.10ASecurityCnf.486.2.11AManufacturerReq.486.2.12AManufacturerInd.496.3Control Plane messages.496.3.1Sequencing of Control Plane messages.526.3.2CAlertReq.566.3.3CAlertInd.566.3.4CConnectReq.576.3.5CConnectInd.586.3.6CConnectRsp.596.3.7CConnectCnf.606.3.8CDisconnectReq.616.3.9CDisconnectInd.626.3.10CDisconnectRsp.636.3.11CDisconnectCnf.636.3.12CProgressInd.646.3.13CStatusInd.646.3.14CSetupAckInd.646.3.15CConnectInfoReq.656.3.16CProceedingInd.656.3.17CUserInformationReq.666.3.18CUserInformationInd.666.3.19CCongestionControlReq.676.3.20CCongestionControlInd.686.3.21CSuspendReq.696.3.22CSuspendCnf.696.3.23CResumeReq.706.3.24CResumeCnf.706.3.25CNotifyInd.716.3.26CFacilityReq.716.3.27CFacilityInd.726.3.28CExtEquipAvailabalityInd.726.3.29CExtEquipBlockDiallingInd.736.3.30CExtEquipKeyPressedInd.736.3.31CExtEquipOffHookInd.746.3.32CExtEquipOnHookInd.746.3.33User to User information exchange.746.3.34Implementation of supplementary services.75SIST ETS 300 325 E1:2003
Page 5ETS 300 325: March 19946.3.34.1Multiple Subscriber Number (MSN).756.3.34.2Direct Dialling In (DDI).766.3.34.3Calling Line Identification Presentation (CLIP).766.3.34.4Calling Line Identification Restriction (CLIR).766.3.34.5Subaddressing (SUB).776.3.34.6Advice of Charge during call (AOC-D).776.3.34.7Advice of Charge at end of call (AOC-E).776.3.34.8Call Waiting (CW).786.3.34.9Connected Line Identification Presentation (COLP).786.3.34.10Connected Line Identification Restriction (COLR).796.4User Plane messages.806.4.1Sequencing of User Plane messages.836.4.2Co-ordination function.846.4.3U3ConnectReq.856.4.4U3ConnectInd.866.4.5U3ConnectRsp.876.4.6U3ConnectCnf.886.4.7U3DisconnectReq.896.4.8U3DisconnectInd.906.4.9U3DataReq.916.4.10U3DataInd.926.4.11U3ExpeditedDataReq.926.4.12U3ExpeditedDataInd.936.4.13U3ResetReq.936.4.14U3ResetInd.946.4.15U3ResetRsp.946.4.16U3ResetCnf.956.4.17U3DataAcknowledgeReq.956.4.18U3DataAcknowledgeInd.966.4.19U3ReadyToReceiveReq.966.4.20U3ReadyToReceiveInd.976.4.21U3ErrorInd.986.4.22U1DataReq.986.4.23U1DataInd.996.4.24U1ErrorInd.996.5Information presentation.1006.6Message parameters.1016.6.1Algorithm.1026.6.2Bilateral closed user group (Bcug).1026.6.3BearerCap.1026.6.4Bit_DQM.1036.6.5CalledDTEAddress.1046.6.6CalledDTEAddressExt.1046.6.7CalledNumber.1056.6.8CalledSubaddress.1056.6.9CallingDTEAddress.1066.6.10CallingDTEAddressExt.1066.6.11CallingNumber.1076.6.12CallingSubaddress.1086.6.13CAttributeName.1086.6.14CauseToNAF.1086.6.15CauseToPUF.1096.6.16CDirection.1096.6.17ChannelIdentification.1106.6.18ChargingInfo.1106.6.19CompletionStatus.1116.6.20CongestionLevel.1116.6.21ConnectedNumber.1116.6.22ConnectedSubaddress.1126.6.23DateTime.1126.6.24Display.1126.6.25ExtEquipAvailability.1136.6.26ExtEquipBlockDialling.113SIST ETS 300 325 E1:2003
Page 6ETS 300 325: March 19946.6.27ExtEquipKeypressed.1136.6.28ExtEquipName.1146.6.29ExpeditedData.1146.6.30Facility.1156.6.31FacilityData.1176.6.32FastSelect.1176.6.33GroupID.1186.6.34High Layer Compatibility (HLC).1196.6.35IdleFlag.1206.6.36Key.1206.6.37Keypad.1206.6.38L2ConnectionMode.1206.6.39L2FrameSize.1216.6.40L2WindowSize.1216.6.41L2XID.1216.6.42L3ConnectionMode.1226.6.43L3IncomingVCCount.1226.6.44L3OutgoingVCCount.1226.6.45L3TwoWayVCCount.1236.6.46Low Layer Compatibility (LLC).1236.6.47ManufacturerCode.1236.6.48MoreData.1246.6.49NCOID.1246.6.50NCOType.1246.6.51NotificationIndicator.1246.6.52PacketSize.1256.6.53ProgressIndicator.1266.6.54QOSParameters.1276.6.55ReadyFlag.1286.6.56RequestID.1286.6.57ReceiptConfirm.1296.6.58RespondingDTEAddress.1296.6.59RespondingDTEAddressExt.1296.6.60SelectorID.1296.6.61TEI.1306.6.62U3Protocol.1306.6.63UAttributeName.1306.6.64UDirection.1306.6.65UserData.1316.6.66UserToUserInfo.1316.6.67WindowSize.1326.6.68X213Cause.1326.6.69X213Origin.1326.6.70X25Cause.1336.6.71X25Diagnostic.1336.6.72AttributeSet Parameters.1346.6.73Administration AttributeSet Parameters.1356.6.74AddressSet Parameter.1366.7Selection criteria.1366.7.1NCO selection.1366.7.1.1Control Plane information elements.1376.7.1.2User Plane information element (layer 3).1386.7.1.2.1Packet size negotiation.1386.7.1.2.2Window size negotiation.1386.7.1.2.3Effective packet size and window sizenegotiation.1386.7.2Action if no NCO available.1386.7.2.1Control Plane incoming call.1386.7.2.2User Plane incoming call.1386.8Error checking and codes.1396.8.1Administration Plane.1396.8.2Control Plane.1396.8.2.1Invalid state for message.139SIST ETS 300 325 E1:2003
Page 7ETS 300 325: March 19946.8.2.2Mandatory parameters.1396.8.2.3Optional Parameter Content Error.1396.8.3Errors in facility requests.1396.8.4User Plane (NMA).1396.8.4.1Invalid Use of Receipt Confirmation Service.1396.8.4.2Invalid Use of Confirmation request on U3DataReq.1406.8.4.3Invalid length of U3DataReq UserData parameter.1406.8.4.4Invalid Use of Expedited Data.1406.8.4.5Invalid Issuing of messages while in Reset state.1406.8.4.6Invalid Use of Bit_DQM (association between More andQualifier bits) parameters on subsequent U3DataReqmessages.1406.8.4.7Other errors.1406.8.5TMA User Plane.1406.8.5.1Mandatory Parameters Missing.1406.8.5.2Mandatory Parameter Content Error.1406.8.5.3Unrecognised Parameter.1406.8.5.4Overflow of Incoming Data.1406.8.6Function Return Codes.1406.8.7Administration Plane return code.1426.8.8Control Plane causes.1446.8.9User Plane causes.1476.8.10TMA User Plane causes.1487Exchange method.1497.1Registration phase.1497.1.1Overview.1497.1.2PciGetHandles.1517.1.3PciGetProperty.1517.1.4PciRegister.1537.2Deregistration phase.1537.2.1PciDeregister.1547.3Conversation phase.1547.3.1Sending messages.1547.3.2Receiving messages.1547.3.3Receiving messages using the polling method.1547.3.4Receiving messages using signal method.1557.3.5PCI Message Parameter Block (PciMPB).1567.3.6PciPutMessage.1577.3.7PciGetMessage.1587.3.8PciSetSignal.1598Security.1608.1General aspects of security in ISDN.1608.2Security in the ISDN PCI.1608.3Increasing security in the ISDN PCI.161Annex A (informative):Bibliography.162Annex B (normative):Mapping between ISDN PCI messages and Protocols supported.164B.1Control Plane messages.164B.2Control Plane parameters.166B.3User Plane messages.167Annex C (normative):Telephony.168C.1Type 1 external equipment.168C.2Type 2 external equipment.168SIST ETS 300 325 E1:2003
Page 8ETS 300 325: March 1994C.3Type 3 external equipment.168C.4Type 4 external equipment.169C.5Type 5 external equipment.169Annex D (normative):CCITT Recommendation X.25 Usage.170D.1Parameter Values for CCITT Recommendation X.25 Use.170D.2Disconnection of ISDN channel with established CCITT Recommendation X.25 Connections.170Annex E (informative):NAF development guidelines.171E.1NAF SDL diagrams.172E.2Information provided by the NAF.179E.3Co-ordination function - outgoing User Plane NMA call.180E.4Co-ordination function - incoming ISDN call.181E.5Suspending/resuming calls.182E.6Supplementary services.182E.7Error management.182E.7.1Function return codes.183E.7.2Administration Plane.183E.7.3Control Plane.185E.7.4NMA User Plane.189E.7.5TMA User Plane.190E.8NAF configuration.190E.8.1Global Configuration.190E.8.2System configuration parameters.190E.8.3Control Plane configuration.191E.8.4User Plane NMA configuration.192E.8.5User Plane TMA configuration.193E.9Buffer management.193E.10Extension of ISDN-PCI.194E.10.1Basic mechanism for extension.194E.10.2Manufacturer specific messages.194E.10.3Message coding.194E.10.4Extension of supported protocols.195E.10.4.1Support of new "CCITT Recommendation X.213" like protocols.195E.10.4.2Support of different type of protocols.195Annex F (normative):Operation system specific implementation.196F.1DOS.196F.1.1Mechanism.196F.1.2Mapping of generic types and constants.197F.1.3Description of functions.198F.1.3.1PciGetHandles.198F.1.3.2PciGetProperty.199F.1.3.3PciRegister.200F.1.3.4PciDeregister.203F.1.3.5PciPutMessage.204F.1.3.6PciGetMessage.204SIST ETS 300 325 E1:2003
Page 9ETS 300 325: March 1994F.1.3.7PciSetSignal.205F.2Windows.206F.2.1Mechanism.206F.2.2Implementation of basic type.207F.2.3C Function prototypes.207F.2.4Description of functions.208F.2.4.1PciGetHandles.208F.2.4.2PciGetProperty.209F.2.4.3PciRegister.209F.2.4.4PciDeregister.209F.2.4.5PciPutMessage.209F.2.4.6PciGetMessage.210F.2.4.7PciSetSignal.210F.2.4.7.1Signal mechanism procedure.210F.2.4.7.2User message mechanism procedure.210F.2.4.7.3De-activation mechanism.211F.3Unix.211F.3.1Mechanism.211F.3.2Implementation of basic types.211F.3.3Parameter passing conventions.212F.3.4Definition of types, constants and function-prototypes.212F.3.5Adaptation to the STREAMS kernel mechanism.213F.3.5.1General.213F.3.5.2Communication between PUF exchange functions and NAF stream driver213F.3.5.3Special considerations.215F.3.6Description of functions.215F.3.6.1PciGetHandles.217F.3.6.2PciGetProperty.218F.3.6.3PciRegister.220F.3.6.4PciDeregister.222F.3.6.5PciPutMessage.223F.3.6.6PciGetMessage.224F.3.6.7PciSetSignal.226F.4Availability of NAF's PCI_HANDLE.228F.4.1DOS.228F.4.1.1Declaration action.228F.4.1.2Extraction action.228F.4.2Windows.229F.4.2.1Declaration action.229F.4.2.2Extraction action.230F.4.3UNIX.230F.4.3.1Declaration action.230F.4.3.2Extraction action.230Annex G (normative):PCI ICS Proforma.231G.1C
...