SIST-TS ETSI/TS 102 253 V1.1.1:2005
(Main)Private Integrated Services Network (PISN); Use of QSIG for Message Centre Access (MCA) Profile Standard
- Abstract
New service
- Status
- Published
- Publication Date
- 28-Feb-2005
- Technical Committee
- SPN - Services and Protocols for Networks
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Mar-2005
- Due Date
- 01-Mar-2005
- Completion Date
- 01-Mar-2005
SIST-TS ETSI/TS 102 253 V1.1.1:2005 is the Slovenian adoption of ETSI TS 102 253, Private Integrated Services Network (PISN); Use of QSIG for Message Centre Access (MCA) Profile Standard. It specifies how QSIG/PSS1 is used in a PISN for Message Centre Access procedures, including message deposit, Message Centre Monitoring, browsing, retrieval, and transfer. The standard also defines four MCA profiles so implementers can choose a consistent set of supplementary services and interworking rules.
What does SIST-TS ETSI/TS 102 253 V1.1.1:2005 specify?
SIST-TS ETSI/TS 102 253 V1.1.1:2005 specifies the combination of base standards, selected options, and parameter values needed to use QSIG/PSS1 for MCA in a PISN. In practice, it tells a system designer which service procedures belong together and how the Message Centre, Served User, and Originator interact.
The document is organized into:
- Clause 1 - Scope
- Clause 2 - Conformance
- Clause 3 - Normative references
- Clause 4 - Definitions
- Clause 5 - Acronyms
- Clause 6 - Specification framework
- Clause 7 - Profiles
- Annex A - Requirements List (RL)
- Annex B - Profile specific ICS proforma
- Annex C - Example Message Flows
| Annex | What it covers |
|---|---|
| Annex A | Requirements List for the profile tables and conformance status |
| Annex B | Profile specific Implementation Conformance Statement (ICS) proformas for Profiles 1 to 4 |
| Annex C | Example message flows for Profiles 1 to 4 |
What are the key requirements of SIST-TS ETSI/TS 102 253 V1.1.1:2005?
Conformance and profile selection
Clause 2 says a system conforms when it supports all mandatory capabilities defined in one or more Requirement List (RL) items and one or more profile-specific ICS proformas. Annex A uses the ISO/IEC 9646-7 status notation such as mandatory, optional, not applicable, excluded, and qualified optional.
For implementers, this means conformance is not just about supporting the base standards. You have to check the profile-specific RL and complete the matching ICS in Annex B so the supported feature set is explicit.
MCA service framework
Clause 6.1 frames MCA as the coordinated use of basic and supplementary services for accessing a Message Centre. The document groups MCA into five practical functions: message deposit, Message Centre Monitoring, message browsing, message retrieval, and Message Centre transfer.
That matters because the standard is not a single call flow. It is a profile framework that limits the combinations of supplementary services so different systems can interwork and migrate from older service sets to newer ones.
Profile 1: MWI, Call Diversion and Call Transfer
Clause 7.1 defines MCA-Profile-1 as the profile using Message Waiting Indication (MWI), Call Diversion, and Call Transfer. In direct message deposit, the message type is identified from the Bearer Capability and High Layer Compatibility Information Elements in the SETUP message, and after a new message is deposited the Message Centre PINX sends an mwiActivate invoke APDU to the Served User PINX.
In Annex A, Profile 1 also fixes the required APDU coding and timer support for MWI, Call Diversion, and Call Transfer. In practice, this is the profile to choose when message waiting indication is the key mailbox notification mechanism.
Profile 2: Simple Dialog and Single Step Call Transfer added
Clause 7.2 extends Profile 1 with Simple Dialog and Single Step Call Transfer. The document says Simple Dialog replaces the procedures that use DTMF and announcements in clause 7.1, while still requiring DTMF and announcements capability for interoperability with Profile 1 systems.
For a supplier, this means Profile 2 supports a more structured mailbox interaction while still preserving backward compatibility. Annex A also adds the RL items for Single Step Call Transfer and its coding and timers.
Profile 3: Message Centre Monitoring and Mailbox Identification
Clause 7.3 replaces Message Waiting Indication with Message Centre Monitoring (MCM) and adds Mailbox Identification (MID). Simple Dialog still applies, and DTMF and announcements remain available for interoperability when Simple Dialog is absent at the Originator side.
A key operational point is that if a Served User owns more than one mailbox, the Message Centre PINX identifies the mailbox using an mIDMailboxID invoke APDU and then sends the mCMNewMsg invoke APDU after the return result. That matters in multi-mailbox environments because the Message Centre must target the correct mailbox before notifying new messages.
Profile 4: Make Call Request for dynamic B-channel use
Clause 7.4 adds Make Call Request (MCR) to Profile 3. The document states that this lets the Message Centre and Served User PINX communicate using only a Call Independent Signalling Connection (CISC), while the B-channel needed for retrieval can be allocated dynamically and on demand.
The practical effect is resource efficiency: the Message Centre can clear the B-channel after use, and the CISC may stay up for further communication such as message browsing. Annex A gives the MCR procedures and APDU coding that implementers must support.
What terms does SIST-TS ETSI/TS 102 253 V1.1.1:2005 define?
- Message Centre Access (MCA) - The profile framework for using QSIG in a PISN to reach a Message Centre for mailbox-related services.
- Message Centre (MC) - The message-handling entity used in MCA, which is either an MCM Message Centre or an MWI Message Centre depending on the profile.
- Served User - The user whose mailbox is being monitored, browsed, retrieved, or transferred to/from by MCA procedures.
- Message Deposit - The MCA function where an Originator places a message into a Served User's mailbox at the Message Centre.
- Message Centre Monitoring (MCM) - The function where the Message Centre informs the Served User about message status and status changes.
- Message Browsing - The function that lets a Served User access the mailbox for configuration update, browsing, or deletion of messages.
- Message Centre Transfer - The function that connects the Served User to the Originator of a message or another destination.
Who uses SIST-TS ETSI/TS 102 253 V1.1.1:2005?
This standard is used by PISN and PINX equipment manufacturers, protocol implementers, network integrators, and test teams working on QSIG-based voice and messaging systems. It is also relevant to buyers and quality managers who need to compare supported MCA profiles across products.
In practice, they use it to:
- select the right MCA profile for an implementation
- map supported features into an ICS statement
- test message deposit, monitoring, browsing, retrieval, and transfer behavior
- verify interworking between older and newer supplementary services
Which standards are used with SIST-TS ETSI/TS 102 253 V1.1.1:2005?
The document relies on these normative references and companion service parts:
| Reference | Contribution |
|---|---|
| ECMA-133, ECMA-155, ECMA-142, ECMA-143, ECMA-165 | PISN reference configuration, addressing, bearer services, QSIG-BC, and QSIG-GF foundation |
| ECMA-173, ECMA-174 | Call Diversion service description and signalling |
| ECMA-177, ECMA-178 | Call Transfer service description and signalling |
| ECMA-241, ECMA-242 | Message Waiting Indication service description and signalling |
| ECMA-299, ECMA-300 | Single Step Call Transfer service description and signalling |
| ECMA-310, ECMA-311 | Simple Dialog service description and signalling |
| ECMA-343, ECMA-344 | Make Call Request service description and signalling |
| ECMA-346, ECMA-347 | Message Centre Monitoring and Mailbox Identification service description and signalling |
| ECMA TR/76 | Architecture and scenarios for private integrated services networking |
| ISO/IEC 9646-7 | ICS-based conformance testing framework used for Annex B |
| ITU-T Recommendation E.164 | International public telecommunication numbering plan used for numbering context |
What does the SIST-TS ETSI/TS 102 253 V1.1.1:2005 document contain?
The document contains the profile framework, the RL tables, the profile-specific ICS proformas, and example message flows. Annex A is especially detailed: it lists the supported procedures, coding items, and timers for each profile, including APDUs such as mwiActivate, mCMNewMessage, mIDMailboxID, and mCRequest.
Annex B gives the questionnaire-style ICS forms for Profiles 1 to 4 so a supplier can declare exactly what has been implemented. Annex C provides worked message flows for typical cases such as message deposit after diversion, message retrieval, browsing, MCM, and Message Centre transfer, which helps with implementation design and testing.
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-TS ETSI/TS 102 253 V1.1.1:2005 is a technical specification published by the Slovenian Institute for Standardization (SIST). Its full title is "Private Integrated Services Network (PISN); Use of QSIG for Message Centre Access (MCA) Profile Standard". This standard covers: New service
New service
SIST-TS ETSI/TS 102 253 V1.1.1:2005 is classified under the following ICS (International Classification for Standards) categories: 33.040.35 - Telephone networks. The ICS classification helps identify the subject area and facilitates finding related standards.
SIST-TS ETSI/TS 102 253 V1.1.1:2005 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)
SLOVENSKI STANDARD
01-marec-2005
=DVHEQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL3,618SRUDED46,*]DGRVWRSGR
VSRURþLOQHJDFHQWUD0&$3URILOVWDQGDUGD
Private Integrated Services Network (PISN); Use of QSIG for Message Centre Access
(MCA) Profile Standard
Ta slovenski standard je istoveten z: TS 102 253 Version 1.1.1
ICS:
33.040.35 Telefonska omrežja Telephone networks
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
Technical Specification
Private Integrated Services Network (PISN);
Use of QSIG for Message Centre Access (MCA)
Profile Standard
2 ETSI TS 102 253 V1.1.1 (2003-08)
Reference
DTS/ECMA-00223
Keywords
PISN, profile
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, send your comment to:
editor@etsi.org
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 2003.
All rights reserved.
TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI TS 102 253 V1.1.1 (2003-08)
Contents
Intellectual Property Rights.7
Foreword.7
Brief History.7
1 Scope.8
2 Conformance.8
3 References (normative).8
4 Definitions.10
4.1 External definitions.10
4.2 Served user.11
4.3 Served user PINX.11
4.4 Message Centre (MC) .11
4.4.1 MCM Message Centre (MC) .11
4.4.2 MWI Message Centre (MC) .11
4.5 MCA-Profile-1.12
4.6 MCA-Profile-2.12
4.7 MCA-Profile-3.12
4.8 MCA-Profile-4.12
4.9 Message Deposit.12
4.9.1 Direct Message Deposit .12
4.9.2 Message Deposit after Diversion.12
4.9.3 Message Deposit after Transfer .12
4.10 Message Centre Monitoring (MCM).12
4.11 Message Browsing.12
4.12 Message Retrieval.13
4.13 Message Centre (MC) Transfer.13
5 Acronyms.13
6 Specification framework.13
6.1 General description.13
6.2 Scenarios.14
6.2.1 Message Deposit.14
6.2.1.1 Direct Message Deposit .14
6.2.1.2 Message Deposit after Diversion .14
6.2.1.3 Message Deposit after Transfer.14
6.2.2 Message Centre Monitoring (MCM) .15
6.2.3 Message Browsing.15
6.2.4 Message Retrieval.15
6.2.5 Message Centre (MC) Transfer .15
7 Profiles.15
7.1 MCA-Profile-1.15
7.1.1 Message Deposit.15
7.1.1.1 Direct Message Deposit .15
7.1.1.2 Message Deposit after Diversion .16
7.1.1.3 Message Deposit after Transfer.16
7.1.2 Message Centre Monitoring (MCM) .16
7.1.3 Message Browsing.16
7.1.4 Message Retrieval.16
7.1.5 Message Centre (MC) Transfer .17
7.2 MCA-Profile-2.17
7.2.1 Message Deposit.17
7.2.1.1 Message Deposit after Single-Step Call Transfer .17
7.2.2 Message Centre Monitoring (MCM) .17
ETSI
4 ETSI TS 102 253 V1.1.1 (2003-08)
7.2.3 Message Browsing.17
7.2.4 Message retrieval.18
7.2.5 Message Centre (MC) Transfer .18
7.2.5.1 Message Centre (MC) Transfer Using Single Step Call Transfer .18
7.2.5.2 Message Centre (MC) Transfer Using Call Transfer .18
7.3 MCA-Profile-3.18
7.3.1 Message Deposit.18
7.3.2 Message Centre Monitoring (MCM) .19
7.3.3 Message Browsing.19
7.3.4 Message retrieval.19
7.3.5 Message Centre (MC) Transfer .19
7.4 MCA-Profile-4.20
7.4.1 Message Deposit.20
7.4.2 Message Centre Monitoring (MCM) .20
7.4.3 Message Browsing.20
7.4.4 Message Retrieval.20
7.4.5 Message Centre (MC) Transfer .21
7.4.5.1 Message Centre Transfer Using Make Call Request.21
Annex A (normative): Requirements List (RL).22
A.1 General.22
A.2 Relationship between RL and corresponding PICS proformas.22
A.3 Requirement List (RL).22
A.3.1 Tables for Profile 1.22
A.3.1.1 Support of Supplementary Services (SS).23
A.3.1.2 Supplementary Service Message Waiting Indication .23
A.3.1.2.1 General.23
A.3.1.2.2 Procedures.23
A.3.1.2.3 Coding.24
A.3.1.2.4 Timers.24
A.3.1.3 Supplementary Service Call Diversion.24
A.3.1.3.1 General.24
A.3.1.3.2 Procedures.25
A.3.1.3.3 Coding.26
A.3.1.3.4 Timers.27
A.3.1.4 Supplementary Service Call Transfer .27
A.3.1.4.1 General.27
A.3.1.4.2 Procedures for SS-CT-Join .27
A.3.1.4.3 Additional procedures for SS-CT-Rerouteing.28
A.3.1.4.4 Coding.28
A.3.2 Tables for Profile 2.28
A.3.2.1 Support of Supplementary Services.29
A.3.2.2 Supplementary Service Message Waiting Indication .29
A.3.2.3 Supplementary Service Simple Dialog .29
A.3.2.3.1 General.29
A.3.2.3.2 Procedures.29
A.3.2.3.3 Coding.30
A.3.2.4 Supplementary Service Call Diversion.30
A.3.2.5 Supplementary Service Call Transfer .30
A.3.2.6 Supplementary Service Single-Step Call Transfer.30
A.3.2.6.1 General.30
A.3.2.6.2 Procedures.30
A.3.2.6.3 Coding.31
A.3.2.6.4 Timers.31
A.3.3 Tables for Profile 3.31
A.3.3.1 Support of Supplementary Services.32
A.3.3.2 Supplementary Service Simple Dialog .32
A.3.3.3 Supplementary Service Message Centre Monitoring.32
A.3.3.3.1 General.32
A.3.3.3.2 Procedures.33
ETSI
5 ETSI TS 102 253 V1.1.1 (2003-08)
A.3.3.3.3 Coding.34
A.3.3.3.4 Timers.34
A.3.3.4 Supplementary Service Message Centre Identification .34
A.3.3.4.1 General.34
A.3.3.4.2 Procedures.35
A.3.3.4.3 Coding.35
A.3.3.4.4 Timers.35
A.3.3.5 Supplementary Service Call Diversion.35
A.3.3.6 Supplementary Service Call Transfer .35
A.3.3.7 Supplementary Service Single-Step Call Transfer.35
A.3.4 Tables for Profile 4.36
A.3.4.1 Support of Supplementary Services.36
A.3.4.2 Supplementary Service Simple Dialog .36
A.3.4.3 Supplementary Service Message Centre Monitoring.36
A.3.4.4 Supplementary Service Message Centre Identification .36
A.3.4.5 Supplementary Service Make Call Request.36
A.3.4.5.1 General.36
A.3.4.5.2 Procedures.37
A.3.4.5.3 Coding.37
A.3.4.5.4 Timers.37
A.3.4.6 Supplementary Service Call Diversion.37
A.3.4.7 Supplementary Service Call Transfer .37
A.3.4.8 Supplementary Service Single-Step Call Transfer.38
Annex B (normative): Profile specific ICS proforma.39
B.1 General.39
B.2 Instruction for completing the ICS proforma .39
B.2.1 General structure of the ICS proforma .39
B.2.2 Additional Information.40
B.2.3 Exception Information.40
B.3 ICS proforma for Profile 1 .40
B.3.1 Implementation Identification.40
B.3.2 General.40
B.3.3 Message Deposit.41
B.3.4 Message Centre Monitoring .41
B.3.5 Message Browsing.41
B.3.6 Message Retrieval.41
B.3.7 Message Centre Transfer.41
B.4 ICS proforma for Profile 2 .42
B.4.1 Implementation Identification.42
B.4.2 General.42
B.4.3 Message Deposit.42
B.4.4 Message Centre Monitoring .42
B.4.5 Message Browsing.43
B.4.6 Message Retrieval.43
B.4.7 Message Centre Transfer.43
B.5 ICS proforma for Profile 3 .44
B.5.1 Implementation Identification.44
B.5.2 General.44
B.5.3 Message Deposit.44
B.5.4 Message Centre Monitoring .44
B.5.5 Message Browsing.45
B.5.6 Message Retrieval.45
B.5.7 Message Centre Transfer.45
B.6 ICS proforma for Profile 4 .45
B.6.1 Implementation Identification.45
B.6.2 General.46
B.6.3 Message Deposit.46
ETSI
6 ETSI TS 102 253 V1.1.1 (2003-08)
B.6.4 Message Centre Monitoring .46
B.6.5 Message Browsing.46
B.6.6 Message Retrieval.46
B.6.7 Message Centre Transfer.47
Annex C (normative): Example Message Flows .48
C.1 Example Message Flows for Profile 1 .48
C.1.1 Message Deposit after Diversion.48
C.1.2 Message retrieval.49
C.1.3 Message Centre Transfer.50
C.2 Example Message Flows for Profile 2 .51
C.2.1 Message retrieval.51
C.2.2 Message Centre Single Step Transfer.52
C.3 Example Message Flows for Profile 3 .53
C.3.1 Message Deposit after Diversion.53
C.3.2 Message Centre Monitoring .54
C.3.3 Message Centre Browsing.55
C.4 Example Message Flows for Profile 4 .56
C.4.1 Message retrieval.56
C.4.2 Message Centre Transfer.57
History .58
ETSI
7 ETSI TS 102 253 V1.1.1 (2003-08)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ECMA on behalf of its members and those of the European
Telecommunications Standards Institute (ETSI).
Brief History
The present document is one of a series of ECMA Standards defining services and signalling protocols applicable to
Private Integrated Services Networks (PISNs). The series uses ISDN concepts as developed by ITU-T and conforms to
the framework of International Standards for Open Systems Interconnection as defined by ISO/IEC. It has been
produced under ETSI work item DTS/ECMA-00223.
The present documents based upon the practical experience of ECMA member companies and the results of their active
and continuous participation in the work of ISO/IEC JTC1, ITU-T, ETSI and other international and regional
standardization bodies. It represents a pragmatic and widely based consensus.
ETSI
8 ETSI TS 102 253 V1.1.1 (2003-08)
1 Scope
The present document specifies the combination of base standards, together with the selection of appropriate options
and parameter values, necessary to specify how QSIG / PSS1 can be used for Message Centre Access (MCA)
procedures.
The present document identifies the necessary or optional employment of particular functions, procedures and services
for:
• a Calling User to deposit messages for a Served User at a Message Centre;
• a Served User to monitor the Served User's Mailbox for new messages;
• a Served User to browse through the messages saved in the Served User's Mailbox;
• a Served User to retrieve the messages saved in the Served User's Mailbox; and
• a Served User to get connected to the Originator of a message or any other destination.
2 Conformance
A system conforms to the present document if it correctly performs all the mandatory capabilities defined in one or
more of the requirement list (RL) (annex A) and one or more of the profile specific ICS (annex B).
NOTE: For the purpose of the present document capabilities marked as optional in the base standards may be
mandatory or excluded.
3 References (normative)
The following standards contain provisions which, through reference in this text, constitute provisions of the present
document. All standards are subject to revision, and parties to agreements based on the present document are
encouraged to investigate the possibility of applying the most recent editions of the standards indicated below.
In the case of references to ECMA Standards that are aligned with ISO/IEC International Standards, the number of the
appropriate ISO/IEC International Standard is given in brackets after the ECMA reference.
[1] ECMA -133: "Private Integrated Services Network (PISN) - Reference Configuration for PISN
Exchanges (PINX) (International Standard ISO/IEC 11579-1)".
[2] ECMA-142: "Private Integrated Services Network (PISN) - Circuit Mode 64kbit/s Bearer
Services - Service Description, Functional Capabilities and Information Flows (International
Standard ISO/IEC 11574)".
[3] ECMA-143: "Private Integrated Services Network (PISN) - Circuit Mode Bearer Services -
Inter-Exchange Signalling Procedures and Protocol (QSIG-BC) (International Standard
ISO/IEC 11572)".
[4] ECMA-155: "Private Integrated Services Network - Addressing (International Standard
ISO/IEC 11571)".
[5] ECMA-165: "Private Integrated Services Network (PISN) - Generic Functional Protocol for the
Support of Supplementary Services - Inter-Exchange Signalling Procedures and Protocol
(QSIG-GF) (International Standard ISO/IEC 11582)".
[6] ECMA-173: "Private Integrated Services Network (PISN) - Specification, Functional Model and
Information Flows - Call Diversion Supplementary Services (CFSD) (International Standard
ISO/IEC 13872)".
ETSI
9 ETSI TS 102 253 V1.1.1 (2003-08)
[7] ECMA-174: "Private Integrated Services Network (PISN) - Inter-Exchange Signalling
Protocol - Call Diversion Supplementary Services (QSIG-CF) (International Standard
ISO/IEC 13873)".
[8] ECMA-177: "Private Integrated Services Network (PISN) - Specification, Functional Model and
Information Flows - Call Transfer Supplementary Service (CTSD) (International Standard
ISO/IEC 13865)".
[9] ECMA-178: "Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol -
Call Transfer Supplementary Service (QSIG-CT) (International Standard ISO/IEC 13869)".
[10] ECMA-241: "Private Integrated Services Network (PISN) - Specification, Functional Model and
Information Flows - Message Waiting Indication Supplementary Service (MWISD) (International
Standard ISO/IEC 15505)".
[11] ECMA-242: "Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol -
Message Waiting Indication Supplementary Service (QSIG-MWI) (International Standard
ISO/IEC 15506)".
[12] ECMA-299: "Private Integrated Services Network (PISN) - Specification, Functional Model and
Information Flows - Single Step Call Transfer Supplementary Service (SSCT-SD) (International
Standard ISO/IEC 19459)".
[13] ECMA-300: "Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol -
Single Step Call Transfer Supplementary Service (QSIG-SSCT) (International Standard
ISO/IEC 19460)".
[14] ECMA-310: "Private Integrated Services Network (PISN) - Specification, Functional Model and
Information Flows - Simple Dialog Supplementary Service (SDSD) (International Standard
ISO/IEC 21407)".
[15] ECMA-311: "Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol -
Simple Dialog Supplementary Service (QSIG-SD) (International Standard ISO/IEC 21408)".
[16] ECMA-343: "Private Integrated Services Network (PISN) - Specification, Functional Model and
Information Flows - Make Call Request Supplementary Service (MCRSD)".
[17] ECMA-344: "Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol -
Make Call Request Supplementary Service (QSIG-MCR)".
[18] ECMA-346: "Private Integrated Services Network (PISN) - Specification, Functional Model and
Information Flows - Message Centre Monitoring and Mailbox Identification Supplementary
Services (MCM-SD/MID-SD)".
[19] ECMA-347: "Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol -
Message Centre Monitoring and Mailbox Identification Supplementary Services
(QSIG-MCM/QSIG-MID)".
[20] ECMA TR/76: "Private Integrated Services Network (PISN) - Architecture and Scenarios for
Private Integrated Services Networking (ISO/IEC TR 14475)".
[21] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing
methodology and framework - Part 7: Implementation Conformance statements".
[22] ITU-T Recommendation E.164: "The international public telecommunication numbering plan".
ETSI
10 ETSI TS 102 253 V1.1.1 (2003-08)
4 Definitions
4.1 External definitions
For the purposes of the present document, the following terms and definitions given other documents apply:
Basic Call (BC): See ECMA-165 [5].
call: See ECMA-165 [5].
Call Independent Signalling Connection (CISC): See ECMA-165 [5].
call related: See ECMA-165 [5].
complete number: See ECMA-155 [4].
compressed information: See ECMA-346 [18].
display information: See ECMA-310 [14].
diverted-to PINX: See ECMA-174 [7].
keypad information: See ECMA-310 [14].
mailbox: See ECMA-346 [18].
Mailbox IDentification (MID): See ECMA-346 [18].
Make Call Request (MCR): See ECMA-343 [16].
Message Centre (MC): See ECMA-346 [18].
Message Centre (MC) PINX: See ECMA-347 [19].
message type: See ECMA-346 [18].
message status: See ECMA-346 [18].
MCR co-operating PINX: See ECMA-344 [17].
MCR co-operating user: See ECMA-343 [16].
MCR destination PINX: See ECMA-344 [17].
MCR destination user: See ECMA-343 [16].
MCR requesting PINX: See ECMA-344 [17].
MCR requesting user: See ECMA-343 [16].
new message: See ECMA-346 [18].
original call: See ECMA-343 [16].
originator: See ECMA-346 [18].
Private Integrated Services Network (PISN): See ECMA-133.
Private Integrated services Network eXchange (PINX): See ECMA-133.
requested call: See ECMA-343 [16].
rerouting PINX: See ECMA-174 [7].
retrieved message: See ECMA-346 [18].
ETSI
11 ETSI TS 102 253 V1.1.1 (2003-08)
secondary call: See ECMA-178 [9].
served user: See ECMA-173 [6], ECMA-346 [18]
server user: See ECMA-310 [14].
served user PINX: See ECMA-174 [7], ECMA-347 [19].
server user PINX: See ECMA-311 [15].
transferred user: See ECMA-299 [12].
transferring user: See ECMA-178 [9].
telecommunication service: See ECMA-142 [2].
user: See ECMA-142 [2].
user b: See ECMA-177 [8].
Q reference point: See ECMA-133 [1].
4.2 Served user
The Served User as defined in Message Centre Monitoring (ECMA-346 [18]). For MCA, the Served User may also act
as Served User in Call Diversion (as defined in ECMA-173 [6]), as a User B in Call Transfer (as defined in
ECMA-177 [8]), as a Client User in Simple Dialog (as defined in ECMA-310 [14]), as a Transferred User in Single
Step Call Transfer (as defined in ECMA-299 [12]) and as a Co-operating User in Make Call Request (as defined in
ECMA-343 [16]).
4.3 Served user PINX
The Served User PINX as defined in ECMA-347 [19]. For MCA, the Served User PINX may also act as Served User
PINX or Rerouting PINX for Call Diversion (as defined in ECMA-173 [6]), as a Primary PINX for Call Transfer (as
defined in ECMA-177 [8]), as a Client User PINX for Simple Dialog (as defined in ECMA-311 [15]), as a Transferred
PINX for Single Step Call Transfer (as defined in ECMA-300 [13]) and as a Co-operating PINX for Make Call Request
(as defined in ECMA-344 [17]).
4.4 Message Centre (MC)
Depending on the MCA-Profile, either the MCM or the MWI Message Centre.
4.4.1 MCM Message Centre (MC)
The Message Centre as defined in ECMA-346 [18]. This definition is used in MCA-Profile-3 and MCA-Profile-4. For
MCA, the MCM Message Centre may also act as Diverted-to PINX for Call Diversion (as defined in ECMA-174 [7]),
as a Server User PINX for Simple Dialog (as defined in ECMA-311 [15]), a Transferring PINX for Call Transfer (as
defined in ECMA-178 [9]), a Transferring PINX for Single Step Call Transfer (as defined in ECMA-300 [13]), and a
Requesting PINX for Make Call Request (as defined in ECMA-344 [17]).
4.4.2 MWI Message Centre (MC)
The Message Centre as defined in ECMA-241 [10]. This definition is used in MCA-Profile-1 and MCA-Profile-2. For
MCA, the MWI Message Centre may also act as Diverted-to PINX for Call Diversion (as defined in ECMA-174 [7]), as
a Server User PINX for Simple Dialog (as defined in ECMA-311 [15]), as
...



