ISO/IEC 20115:2004
(Main)Information technology — Telecommunications and information exchange between systems — Private Integrated Services Network — Use of QSIG for Message Centre Access (MCA) profile standard
Information technology — Telecommunications and information exchange between systems — Private Integrated Services Network — Use of QSIG for Message Centre Access (MCA) profile standard
ISO/IEC 20115:2004 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. ISO/IEC 20115:2004 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, Served User to monitor the Served User's Mailbox for new messages, Served User to browse through the messages saved in the Served User's Mailbox, Served User to retrieve the messages saved in the Served User's Mailbox, and Served User to get connected to the Originator of a message or any other destination.
Technologies de l'information — Télécommunications et échange d'information entre systèmes — Réseau privé à intégration de services — Emploi de QSIG pour une norme de profil pour accès au centre du message (MCA)
General Information
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 20115
First edition
2004-05-15
Information technology —
Telecommunications and information
exchange between systems — Private
Integrated Services Network — Use of
QSIG for Message Centre Access (MCA)
profile standard
Technologies de l'information — Télécommunications et échange
d'information entre systèmes — Réseau privé à intégration de
services — Emploi de QSIG pour une norme de profil pour accès au
centre du message (MCA)
Reference number
©
ISO/IEC 2004
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.
© ISO/IEC 2004
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2004 – All rights reserved
Contents Page
Foreword. iv
Introduction . v
1 Scope. 1
2 Conformance. 1
3 Normative references. 1
4 Terms and definitions. 3
4.1 External definitions. 3
5 Acronyms. 6
6 Specification framework. 7
6.1 General Description. 7
6.2 Scenarios. 8
7 Profiles. 9
7.1 MCA-Profile-1. 9
7.2 MCA-Profile-2. 11
7.3 MCA-Profile-3. 12
7.4 MCA-Profile-4. 14
Annex A (normative) Requirements List (RL). 16
A.1 General. 16
A.2 Relationship between RL and corresponding PICS proformas . 16
A.3 Requirement List. 17
Annex B (normative) Profile specific ICS proforma. 40
B.1 General. 40
B.2 Instruction for completing the ICS proforma . 40
B.3 ICS proforma for Profile 1 . 42
B.4 ICS proforma for Profile 2 . 44
B.5 ICS proforma for Profile 3 . 46
B.6 ICS proforma for Profile 4 . 49
Annex C (informative) Example Message Flows . 52
C.1 Example Message Flows for Profile 1. 52
C.2 Example Message Flows for Profile 2. 55
C.3 Example Message Flows for Profile 3. 57
C.4 Example Message Flows for Profile 4. 60
© ISO/IEC 2004 – All rights reserved iii
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees
established by the respective organization to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organizations, governmental
and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information
technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft International
Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as
an International Standard requires approval by at least 75 % of the national bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
ISO/IEC 20115 was prepared by ECMA (as ECMA-345) and was adopted, under a special “fast-track
procedure”, by Joint Technical Committee ISO/IEC JTC 1, Information technology, in parallel with its approval
by national bodies of ISO and IEC.
iv © ISO/IEC 2004 – All rights reserved
Introduction
This International Standard is one of a series 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.
This International Standard is 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.
© ISO/IEC 2004 – All rights reserved v
INTERNATIONAL STANDARD ISO/IEC 20115:2004(E)
Information technology — Telecommunications and information
exchange between systems — Private Integrated Services
Network — Use of QSIG for Message Centre Access (MCA)
profile standard
1 Scope
This Profile Standard 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.
This International Standard 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,
• Served User to monitor the Served User's Mailbox for new messages,
• Served User to browse through the messages saved in the Served User's Mailbox,
• Served User to retrieve the messages saved in the Served User's Mailbox, and
• Served User to get connected to the Originator of a message or any other destination.
2 Conformance
A system conforms to this International Standard 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 this International Standard capabilities marked as optional in the base standards may be
mandatory or excluded.
3 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO/IEC 9646-7:1994, Information technology — Open Systems Interconnection — Conformance testing
methodology and framework — Part 7: Implementation Conformance Statements
ISO/IEC 11571:1998, Information technology — Telecommunications and information exchange between
systems — Private Integrated Services Networks — Addressing
ISO/IEC 11572:2000, Information technology — Telecommunications and information exchange between
systems — Private Integrated Services Network — Circuit mode bearer services — Inter-exchange signalling
procedures and protocol
© ISO/IEC 2004 – All rights reserved 1
ISO/IEC 11574:2000, Information technology — Telecommunications and information exchange between
systems — Private Integrated Services Network — Circuit-mode 64 kbit/s bearer services — Service
description, functional capabilities and information flows
ISO/IEC 11579-1:1994, Information technology — Telecommunications and information exchange between
systems — Private integrated services network — Part 1: Reference configuration for PISN Exchanges (PINX)
ISO/IEC 11582:2002, Information technology — Telecommunications and information exchange between
systems — Private Integrated Services Network — Generic functional protocol for the support of
supplementary services — Inter-exchange signalling procedures and protocol
ISO/IEC 13865:2003, Information technology — Telecommunications and information exchange between
systems — Private Integrated Services Network — Specification, functional model and information flows —
Call Transfer supplementary service
ISO/IEC 13869:2003, Information technology — Telecommunications and information exchange between
systems — Private Integrated Services Network — Inter-exchange signalling protocol — Call Transfer
supplementary service
ISO/IEC 13872:2003, Information technology — Telecommunications and information exchange between
systems — Private Integrated Services Network — Specification, functional model and information flows —
Call Diversion supplementary services
ISO/IEC 13873:2003, Information technology — Telecommunications and information exchange between
systems — Private Integrated Services Network — Inter-exchange signalling protocol — Call Diversion
supplementary services
ISO/IEC 15505:2003, Information technology — Telecommunications and information exchange between
systems — Private Integrated Services Network — Specification, functional model and information flows —
Message Waiting Indication supplementary service
ISO/IEC 15506:2003, Information technology — Telecommunications and information exchange between
systems — Private Integrated Services Network — Inter-exchange signalling protocol — Message Waiting
Indication supplementary service
ISO/IEC 19459:2001, Information technology — Telecommunications and information exchange between
systems — Private Integrated Services Network — Specification, functional model and information flows —
Single Step Call Transfer Supplementary Service
ISO/IEC 19460:2003, Information technology — Telecommunications and information exchange between
systems — Private Integrated Services Network — Inter-exchange signalling protocol — Single Step Call
Transfer supplementary service
ISO/IEC 20113:2004, Information technology — Telecommunications and information exchange between
systems — Private Integrated Services Network — Specification, functional model and information flows —
Make call request supplementary service
ISO/IEC 20114:2004, Information technology — Telecommunications and information exchange between
systems — Private Integrated Services Network — Inter-exchange signalling protocol — Make call request
supplementary service
ISO/IEC 20116:2004, Information technology — Telecommunications and information exchange between
systems — Private Integrated Services Network — Specification, functional model and information flows —
Message centre monitoring and mailbox identification supplementary services
ISO/IEC 20117:2004, Information technology — Telecommunications and information exchange between
systems — Private Integrated Services Network — Inter-exchange signalling protocol — Message centre
monitoring and mailbox identification supplementary services
2 © ISO/IEC 2004 – All rights reserved
ISO/IEC 21407:2001, Information technology — Telecommunications and information exchange between
systems — Private Integrated Services Network — Specification, functional model and information flows —
Simple dialog supplementary service
ISO/IEC 21408:2003, Information technology — Telecommunications and information exchange between
systems — Private Integrated Services Network — Inter-exchange signalling protocol — Simple dialog
supplementary service
4 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
4.1 External definitions
This International Standard uses the following terms defined in other documents:
Basic Call (ISO/IEC 11582)
Call (ISO/IEC 11582)
Call Independent Signalling Connection (ISO/IEC 11582)
Call Related (ISO/IEC 11582)
Complete Number (ISO/IEC 11571)
Compressed Information (ISO/IEC 20116)
Display information (ISO/IEC 21407)
Diverted-to PINX (ISO/IEC 13873)
Keypad information (ISO/IEC 21407)
Mailbox (ISO/IEC 20116)
Mailbox Identification (ISO/IEC 20116)
Make Call Request (ISO/IEC 20113)
Message Centre (ISO/IEC 20116)
Message Centre PINX (ISO/IEC 20117)
Message Type (ISO/IEC 20116)
Message Status (ISO/IEC 20116)
MCR Co-operating PINX (ISO/IEC 20114)
MCR Co-operating User (ISO/IEC 20113)
MCR Destination PINX (ISO/IEC 20114)
MCR Destination User (ISO/IEC 20113)
© ISO/IEC 2004 – All rights reserved 3
MCR Requesting PINX (ISO/IEC 20114)
MCR Requesting User (ISO/IEC 20113)
New Message (ISO/IEC 20116)
Original Call (ISO/IEC 20113)
Originator (ISO/IEC 20116)
Private Integrated Services Network (PISN) (ISO/IEC 11579-1)
Private Integrated services Network eXchange (PINX) (ISO/IEC 11579-1)
Requested Call (ISO/IEC 20113)
Rerouting PINX (ISO/IEC 13873)
Retrieved Message (ISO/IEC 20116)
Secondary Call (ISO/IEC 13869)
Served User (ISO/IEC 13872, ISO/IEC 20116)
Server User (ISO/IEC 21407)
Served User PINX (ISO/IEC 13873, ISO/IEC 20117)
Server User PINX (ISO/IEC 21408)
Transferred User (ISO/IEC 19459)
Transferring User (ISO/IEC 13869)
Telecommunication Service (ISO/IEC 11574)
User (ISO/IEC 11574)
User B (ISO/IEC 13865)
Q reference point (ISO/IEC 11579-1)
4.2
Served User
The Served User as defined in Message Centre Monitoring (ISO/IEC 20116). For MCA, the Served User may
also act as Served User in Call Diversion (as defined in ISO/IEC 13872), as a User B in Call Transfer (as
defined in ISO/IEC 13865), as a Client User in Simple Dialog (as defined in ISO/IEC 21407), as a Transferred
User in Single Step Call Transfer (as defined in ISO/IEC 19459) and as a Co-operating User in Make Call
Request (as defined in ISO/IEC 20113).
4.3
Served User PINX
The Served User PINX as defined in ISO/IEC 20117. For MCA, the Served User PINX may also act as Served
User PINX or Rerouting PINX for Call Diversion (as defined in ISO/IEC 13872), as a Primary PINX for Call
Transfer (as defined in ISO/IEC 13865), as a Client User PINX for Simple Dialog (as defined in ISO/IEC
21408), as a Transferred PINX for Single Step Call Transfer (as defined in ISO/IEC 19460) and as a
Co-operating PINX for Make Call Request (as defined in ISO/IEC 20114).
4 © ISO/IEC 2004 – All rights reserved
4.4
Message Centre
Depending on the MCA-Profile, either the MCM or the MWI Message Centre.
4.4.1
MCM Message Centre
The Message Centre as defined in ISO/IEC 20116. 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
ISO/IEC 13873), as a Server User PINX for Simple Dialog (as defined in ISO/IEC 21408), a Transferring PINX
for Call Transfer (as defined in ISO/IEC 13869), a Transferring PINX for Single Step Call Transfer (as defined
in ISO/IEC 19460) and a Requesting PINX for Make Call Request (as defined in ISO/IEC 20114).
4.4.2
MWI Message Centre
The Message Centre as defined in ISO/IEC 15505. 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
ISO/IEC 13873), as a Server User PINX for Simple Dialog (as defined in ISO/IEC 21408), as a Transferring
PINX for Call Transfer (as defined in ISO/IEC 13869) and as a Transferring PINX for Single Step Call Transfer
(as defined in ISO/IEC 19460).
4.5
MCA-Profile-1
MCA-Profile-1 is a profile, which describes the interoperation of supplementary services for Message Centre
Access purposes. Supplementary services involved in MCA-Profile-1 are Call Diversion, Message Waiting
Indication and Call Transfer.
4.6
MCA-Profile-2
MCA-Profile-2 is a profile, which describes the interoperation of supplementary services for Message Centre
Access purposes. Supplementary services involved in MCA-Profile-2 are Call Diversion, Message Waiting
Indication, Call Transfer, Single Step Call Transfer and Simple Dialog.
4.7
MCA-Profile-3
MCA-Profile-3 is a profile, which describes the interoperation of supplementary services for Message Centre
Access purposes. Supplementary services involved in MCA-Profile-3 are Call Diversion, Call Transfer, Single
Step Call Transfer, Simple Dialog, Message Centre Monitoring and Mailbox Identification.
4.8
MCA-Profile-4
MCA-Profile-4 is a profile, which describes the interoperation of supplementary services for Message Centre
Access purposes. Supplementary services involved in MCA-Profile-4 are Call Diversion, Call Transfer, Single
Step Call Transfer, Simple Dialog, Message Centre Monitoring, Mailbox Identification and Make Call Request.
4.9
Message Deposit
The part of MCA describing how an Originator can deposit a Message in a Served User’s Mailbox at a
Message Centre.
4.9.1
Direct Message Deposit
The part of MCA describing how an Originator can deposit a Message in a Served User’s Mailbox by directly
calling the Message Centre, i.e. without a prior call to the Served User.
4.9.2
Message Deposit after Diversion
The part of MCA describing how an Originator can deposit a Message in a Served User’s Mailbox if the
Originator gets diverted to the Served User’s Mailbox.
© ISO/IEC 2004 – All rights reserved 5
4.9.3
Message Deposit after Transfer
The part of MCA describing how an Originator can deposit a Message in a Served User’s Mailbox if the
Originator gets transferred to the Served User’s Mailbox.
4.10
Message Centre Monitoring
The part of MCA describing how a Message Centre informs a Served User about the status and status
changes of Messages in the Served User’s Mailbox.
4.11
Message Browsing
The part of MCA describing how a Served User can contact a Message Centre to get access to the Served
User’s Mailbox, for example; configuration update, message browsing or message deletion purposes.
4.12
Message Retrieval
The part of MCA describing how a Served User can retrieve Messages from the Served User’s Mailbox.
4.13
Message Centre Transfer
The part of MCA describing how a Served User can request the Message Centre to get connected (e.g.
transferred) to the Originator of a specific Message or any other destination.
5 Acronyms
APDU Application Protocol Data Unit
ASN.1 Abstract Syntax Notation One
BC Basic Call
CF Supplementary Service Call Diversion
CISC Call Independent Signalling Connection
CN Corporate telecommunication Network
CT Supplementary Service Call Transfer
DTMF Dual Tone Multiple Frequency
GF Generic Functional protocol (for the support of supplementary services)
MCA Message Centre Access
MCM Supplementary Service Message Centre Monitoring
MCR Supplementary Service Make Call Request
MID Supplementary Service Mailbox Identification
MWI Supplementary Service Message Waiting Indication
NFE Network Facility Extension
PINX Private Integrated services Network eXchange
6 © ISO/IEC 2004 – All rights reserved
PISN Private Integrated Services Network
PNP Private Numbering Plan
QSIG Q reference point SIGnalling system
RL Requirements List
SD Supplementary Service Simple Dialog
SS Supplementary Service
SSCT Supplementary Service Single Step Call Transfer
6 Specification framework
6.1 General Description
This International Standard describes the usage and interoperability of basic and supplementary services
within a PISN for the purpose of Message Centre Access (MCA).
MCA incorporates functionality for the use of accessing a Message Centre due to the following reasons:
• an Originator deposits a Message in the Mailbox of a Served User (Message Deposit);
• a Message Centre informs a Served User about Messages in the Served User’s Mailbox (Message Centre
Monitoring);
• a Served User contacts the Message Centre to, for example, update configuration and browse or delete
messages (Message Browsing);
• a Served User contacts the Message Centre in order to retrieve messages stored in the Served User’s
Mailbox (Message Retrieval);
• a Served User contacts the Message Centre to request connection to the Originator of a Message or any
other destination (Message Centre Transfer).
To obtain the functionality needed for these procedures, different Supplementary Services were standardised
in the past. Some of these Supplementary Services have similar functionality (e.g. Message Waiting Indication
and Message Centre Monitoring or Call Transfer and Single Step Call Transfer) that leads to a variety of
different combinations of these services. To restrict the variety for interworking purposes and to allow a
smooth migration from older services to newer ones, four different profiles were defined for MCA:
• MCA-Profile-1 which makes use of Message Waiting Indication, Call Diversion and Call Transfer;
• MCA-Profile-2 which makes use of Message Waiting Indication, Call Diversion, Simple Dialog, Call
Transfer and Single Step Call Transfer;
• MCA-Profile-3 which makes use of Message Centre Monitoring, Mailbox Identification, Call Diversion,
Simple Dialog, Call Transfer and Single Step Call Transfer;
• MCA-Profile-4 which makes use of Message Centre Monitoring, Mailbox Identification, Call Diversion,
Simple Dialog, Make Call Request, Call Transfer, Single Step Call Transfer.
© ISO/IEC 2004 – All rights reserved 7
6.2 Scenarios
6.2.1 Message Deposit
6.2.1.1 Direct Message Deposit
An Originating User may directly call a specific Message Centre to deposit a Message of a telecommunication
service Message Type within the Mailbox of a specific Served User. Due to information received during call
establishment, the Message Centre will connect the Originator to the indicated Mailbox, which then will
provide further information either by means of B-Channel announcements or display information.
NOTE The signalling information provided during call establishment may not be sufficient to identify the required
Mailbox. In such cases the Message Centre will require more information from the Originator, e.g. the party number of the
Served User for whom a Message is to be deposited, in order to identify the mailbox.
After the Originator has deposited the Message, the Message Centre may either offer further services to the
Originator or release the connection.
Clearing of the connection is the responsibility of the Originator.
6.2.1.2 Message Deposit after Diversion
The call from an Originator to a Served User may be diverted to the Served User’s Mailbox, to allow the
Originator to deposit a Message for the Served User.
After the Originator has deposited the Message, the Message Centre may either offer further services to the
Originator or release the connection.
Clearing of the connection is the responsibility of the Originator.
6.2.1.3 Message Deposit after Transfer
The call from an Originator may be transferred, e.g. by an attendant using Call Transfer or Single Step Call
Transfer, to the Served User’s Mailbox to allow the Originator to deposit a Message for the Served User.
After the Originator has deposited the Message, the Message Centre may either offer further services to the
Originator or release the connection.
Clearing of the connection is the responsibility of the Originator.
6.2.2 Message Centre Monitoring
A Message Centre shall be able to inform the Served User about changes in the Served User’s Mailbox, e.g.
after the receipt of a New Message or after a Message has been retrieved.
The procedures needed for this functionality are defined in Message Waiting Indication and Message Centre
Monitoring.
6.2.3 Message Browsing
A Message Centre may be able to allow the Served User to browse through the messages in the Served
User's mailbox regardless whether the messages are new or already retrieved.
The procedures needed for this functionality are defined in Simple Dialog and Message Centre Monitoring.
NOTE Procedures using DTMF and announcements may be required for certain profiles or if Simple Dialog and
Message Centre Monitoring are not implemented.
8 © ISO/IEC 2004 – All rights reserved
6.2.4 Message Retrieval
A Message Centre shall be able to allow the Served User to retrieve messages from the Served User's
mailbox.
The procedures needed for this functionality are defined in Simple Dialog, Message Centre Monitoring and
Make Call Request.
NOTE Procedures using DTMF and announcements may be required for certain profiles or if Simple Dialog is not
implemented.
6.2.5 Message Centre Transfer
A Message Centre may be able to connect the Served User to the Originator of a Message or any other
destination.
The procedures related to this functionality are defined in Call Transfer, Single Step Call Transfer and Make
Call Request.
7 Profiles
7.1 MCA-Profile-1
7.1.1 Message Deposit
Various message types may be accepted depending on the capabilities of the Message Centre.
7.1.1.1 Direct Message Deposit
Two procedures may be used in order to access the mailbox of the Served User:
1. Direct Access: the Mailbox of the Served User is identified using the Served User's individual Party
Number (or a Message Centre Party Number in combination with an individual Subaddress).
NOTE The individual Party Number may consist of a prefix identifying the Message Centre and the Party
Number of the Served User, e.g. if the Message Centre is identified by 1234 and Served User's Party Number is 9876,
then a Called Party Number 12349876 may identify the Served User's mailbox at the Message Centre.
2. Indirect Access: the Originator sets up a call related connection to the Message Centre using the
Complete Number of the Message Centre. The Message Centre uses announcements and the Calling
User identifies the Served User's mailbox by sending DTMF.
After being connected to the Served User's Mailbox the Originator may deposit a message.
The type of message shall be identified by the encoding of the Bearer Capability and High Layer Compatibility
Information Elements in the SETUP message. After deposit of a new message the Message Centre PINX
shall send a mwiActivate invoke APDU to the Served User PINX according to ISO/IEC 15506.
7.1.1.2 Message Deposit after Diversion
After the Originator's call is diverted to the Message Centre, the Served User shall be identified using either
information provided in element divertingNr or, in case of multiple diversion, in element originalCalledNr of the
received divertingLegInformation2 invoke APDU. If both elements are present it is up to the implementation
and/or administration of the Message Centre which mailbox is appropriate.
© ISO/IEC 2004 – All rights reserved 9
After being connected to the Served User's Mailbox the Originator may deposit a message. The type of
message shall be identified by the encoding of the Bearer Capability and High Layer Compatibility Information
Elements in the SETUP message.
After deposit of a new message the Message Centre shall send a mwiActivate invoke APDU to the Served
User PINX according to ISO/IEC 15506.
7.1.1.3 Message Deposit after Transfer
In order to transfer the Originator to the Served User's mailbox the Transferring User establishes a Call to the
Message Centre. The Served User's mailbox shall be identified using either of the procedures as described in
7.1.1.1. In either case, on receipt of a ctComplete invoke APDU, the Message Centre PINX shall stop any
procedures for message deposit and/or announcements related to the call of the Transferring User and shall
start new procedures for message deposit and/or give new announcements related to the call of the Originator.
After being connected to the Served User's Mailbox the Originator may deposit a message. The type of
message shall be identified by the encoding of the Bearer Capability and High Layer Compatibility Information
Elements in the SETUP message.
After deposit of a new message the Message Centre shall send a mwiActivate invoke APDUto the Served
User PINX according to ISO/IEC 15506.
7.1.2 Message Centre Monitoring
The Message Centre and the Served User shall use procedures as described ISO/IEC 15506 for Message
Centre Monitoring purposes.
7.1.3 Message Browsing
In order to browse through messages the Served User shall establish a Basic Call (as defined in
ISO/IEC 11572) with the Message Centre. The Served User may be requested to provide authentication to the
Message Centre and shall then send the authentication using DTMF.
The Message Centre shall indicate available messages and browsing options for the Served User by
announcements.
For message browsing the Message Centre shall act on DTMF provided by the Served User.
7.1.4 Message Retrieval
The Served User indicates the request for retrieval of a message via DTMF provided by the Served User
using the already established Basic Call for Message Browsing.
The Message Centre introduces the retrieved messages of type Basic Service (as defined in ISO/IEC 15506)
in an appropriate form into the B-channel. The retrieval of other message types is out of the scope of this
International Standard.
NOTE Other messages may be converted in a way appropriate to be introduced into the B-Channel, e.g. email may
be announced to the Served User using an email-to-speech service.
7.1.5 Message Centre Transfer
The Served User may indicate the request for transfer to the Originator of a message or any other destination
via DTMF provided by the Served User using the already established Basic Call for Message Browsing.
If Address Information of the Originator is available, the Message Centre PINX shall set up the Secondary Call
and shall act according to the procedures described in Call Transfer on receipt of an ALERTING or a
CONNECT Message from the Originating PINX.
10 © ISO/IEC 2004 – All rights reserved
7.2 MCA-Profile-2
In addition to MCA-Profile-1, Simple Dialog shall be supported by the Message Centre PINX and the Served
User PINX. Simple Dialog shall replace the procedures using DTMF and announcements described in 7.1.
A Message Centre PINX and a Served User PINX complying with MCA-Profile-2 shall be capable of using
DTMF and announcements as described in 7.1. This provides interoperability, if a Served User PINX
complying with MCA-Profile-1 is connected to a Message Centre PINX complying with MCA-Profile-2, or vice
versa.
7.2.1 Message Deposit
The same procedures as described in 7.1.1 for Message Deposit in MCA-Profile-1 shall apply. If Simple
Dialog is supported by the Originating User PINX, then Simple Dialog shall replace the procedures using
DTMF and announcements described in 7.1.
NOTE Interworking between Simple Dialog and DTMF is not required and is outside the scope of this International
Standard.
7.2.1.1 Message Deposit after Single-Step Call Transfer
In order to transfer the Originator to the Served User's mailbox the Transferring User shall provide the
Complete Number to identify the Served User’s mailbox. This Number is transported in element
rerouteingNumber in the ssctInitiate invoke APDU, which is used for the Called Party Number IE in the
SETUP message sent to the Message Centre.
After being connected to the Served User's Mailbox the Originator may deposit a message.
After deposit of a new message the Message Centre shall send a mwiActivate invoke APDU to the Served
User PINX according to ISO/IEC 15506.
7.2.2 Message Centre Monitoring
The same procedures as described in 7.1.2 for Message Centre Monitoring in MCA-Profile-1 shall apply.
7.2.3 Message Browsing
The same procedures as described in 7.1.3 for Message Browsing in MCA-Profile-1 shall apply to connect the
Served User to the Message Centre.
The communication (including authentication) between Message Centre and Served User shall use Simple
Dialog on the call reference of the call between Message Centre and Served User, if both Served User PINX
and Message Centre PINX support MCA-Profile-2.
Optionally, the Message Centre may assist the Served User using announcements. If either the Message
Centre PINX or the Served User PINX supports only MCA-Profile-1 and does not support Simple Dialog, then
the PINX supporting MCA-Profile-2 shall fall back to procedures described in 7.1.3.
NOTE Using DTMF and announcements may also be required if the Served User accesses the Served User's
mailbox from the Public Network.
7.2.4 Message Retrieval
The Served User PINX shall indicate the request for retrieval of a message by sending an appropriate keypad
invoke APDU to the Message Centre PINX. The Message Centre delivers the retrieved message using the
Basic Call already established for Message Browsing.
© ISO/IEC 2004 – All rights reserved 11
The Message Centre introduces the retrieved messages of type Basic Service (as defined in ISO/IEC 15506)
in an appropriate form into the B-channel. The retrieval of other message types is outside the scope of this
International Standard.
NOTE Other messages may be converted in a way appropriate to be introduced into the B-Channel, e.g. email may
be announced to the Served User using an email-to-speech service.
If either the Message Centre PINX or the Served User PINX supports only MCA-Profile-1 and does not
support Simple Dialog, then the PINX supporting MCA-Profile-2 shall fall back to procedures as described in
7.1.4.
7.2.5 Message Centre Transfer
7.2.5.1 Message Centre Transfer using Single Step Call Transfer
After browsing through the Served User's mailbox the Served User may indicate the request for transfer to the
Originator of a message or any other destination via Simple Dialog using the already established call for
Message Browsing.
If Address Information of the Originator is available, the Message Centre PINX shall send a ssctInitiate invoke
APDU transporting the Party Number of the Originator of the Message in element rerouteingNumber towards
the Served User PINX. On receipt of a ssctInitiate.rej APDU from the Served User PINX the Message Centre
PINX shall fall back to Call Transfer procedures as described in 7.2.5.2.
7.2.5.2 Message Centre Transfer using Call Transfer
The same procedures as described in 7.1.5 for Message Centre Transfer in MCA-Profile-1 shall apply, except
that the communication between Message Centre and Served User shall use Simple Dialog, if both, Served
User PINX and Message Centre PINX support Profile 2.
If either the Message Centre PINX or the Served User PINX support only Profile 1, then the PINX supporting
Profile 2 shall use fall back to procedures as described in 7.1.5.
7.3 MCA-Profile-3
Message Waiting Indication shall be replaced by Message Centre Monitoring (ISO/IEC 20117) in
MCA-Profile-3. Mailbox Identification shall be supported at the Message Centre PINX and may be supported
at the Served User PINX. Simple Dialog shall be supported as described in 7.2.
A Message Centre PINX and a Served User PINX complying with MCA-Profile-3 shall be capable of using
DTMF and announcements as described in 7.1. This provides interoperability if Simple Dialog is not
implemented at the PINX where the Originator of a message is located.
Provision of DTMF and announcements may offer a reduced functionality if Served Users access their
mailbox from the public network (for example).
NOTE Interworking between Simple Dialog and DTMF is not required and therefore outside of scope of this
International Standard.
7.3.1 Message Deposit
The same procedures as described in 7.2.1 for Message Deposit in MCA-Profile-2 shall apply, despite that
Message Centre shall send a mCMNewMsg invoke APDU towards the Served User PINX according to
Message Centre Monitoring instead of a mwiActivate invoke APDU according to Message Waiting Indication.
If the Served User owns more than one mailbox at the Message Centre, the Message Centre PINX shall
identify the specific mailbox by sending a mIDMailboxID invoke APDU and shall send the mCMNewMsg
invoke APDU after receipt of the mIDMailboxID return result APDU.
12 © ISO/IEC 2004 – All rights reserved
7.3.2 Message Centre Monitoring
The Message Centre and the Served User shall use procedures as described in ISO/IEC 20117 for Message
Centre Monitoring purposes.
If a Served User owns more than one mailbox at a Message Centre:
the Message Centre PINX shall identify the specific mailbox by sending a mIDMailboxID invoke APDU.
On receipt of a mIDMailboxID return result APDU, the Message Centre PINX shall send the APDUs
defined in Message Centre Monitoring. Subsequent APDUs are related to the mailbox indicated in the
latest mIDMailboxID invoke APDU;
the Served User PINX shall identify the specific mailbox by sending a mIDMailboxAuth invoke APDU.
After sending of the mIDMailboxAuth return result APDU, the Message Centre PINX shall send the
APDUs defined in Message Centre Monitoring. Subsequent APDUs are related to the mailbox indicated
in the latest mIDMailboxAuth invoke APDU.
If an APDU refers to a new mailbox, then a mIDMailboxID/mIDMailboxAuth invoke APDU shall be sent before
this APDU and the APDUs defined in Message Centre Monitoring shall be sent after receipt of the
mIDMailboxID/mIDMailboxAuth return result APDU.
7.3.3 Message Browsing
The same procedures as described in Message Centre Monitoring (ISO/IEC 20117) shall apply.
Optionally, the Message Centre may assist the Served User using announcements. If either the Message
Centre PINX or the Served User PINX supports only MCA-Profile-1 and does not support Simple Dialog, then
the PINX supporting MCA-Profile-3 shall fall back to procedures described in 7.1.3.
NOTE Using DTMF and announcements may also be required if Served Users access their mailbox from the Public
Network (for example).
For authentication purposes the Served User shall use Mailbox Identification, if available at the Served User
PINX. If Mailbox Identification is not available at the Served User PINX, Simple Dialog may be used instead.
If a Served User owns more than one mailbox at a Message Centre:
the Message Centre PINX shall identify the specific mailbox by sending a mIDMailboxID invoke APDU.
On receipt of a mIDMailboxID return result APDU, the Message Centre PINX shall send the APDUs
defined in Message Centre Monitoring. Subsequent APDUs are related to the mailbox indicated in the
latest mIDMailboxID invoke APDU;
the Served User PINX shall identify the specific mailbox by sending a mIDMailboxAuth invoke APDU.
After sending of a mIDMailboxAuth return result APDU, the Message Centre PINX shall send the APDUs
defined in Message Centre Monitoring. Subsequent APDUs are related to the mailbox indicated in the
latest mIDMailboxAuth invoke APDU.
If an APDU refers to a new mailbox, then a mIDMailboxID/mIDMailboxAuth invoke APDU shall be sent before
this APDU and the APDUs defined in ISO/IEC 20117 shall be sent after receipt of the
mIDMailboxID/mIDMailboxAuth return result APDU.
7.3.4 Message Retrieval
The same procedures as described in 7.2.4 for Message Deposit in MCA-Profile-2 shall apply.
7.3.5 Message Centre Transfer
The same procedures as described in 7.2.5 for Message Centre Transfer in MCA-Profile-2 shall apply.
© ISO/IEC 2004 – All rights reserved 13
7.4 MCA-Profile-4
In addition to MCA-Profile-3, Make Call Request shall be supported by the Message Centre PINX and the
Served User PINX. This allows a communic
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.