SIST ES 202 391-3 V1.3.1:2008

• Abstract:

  Update of ES 202 391 to become Parlay X 2.2, to cover maintenance updates.The present document is part 3 of the Stage 3 Parlay X 2 Web Services specification for Open Service Access (OSA).; The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs.; The present document specifies the Call Notification Web Service. The following are defined here:; • Name spaces.; • Sequence diagrams.; • Data definitions.; • Interface specification plus detailed method descriptions.; • Fault definitions.; • Service Policies.; • WSDL Description of the interfaces.

• Status: Published
• Publication Date: 15-Jul-2008
• ICS: 35.100.01 - Open systems interconnection in general
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 19-Jun-2008
• Due Date: 24-Aug-2008
• Completion Date: 16-Jul-2008
• Ref Project: ETSI ES 202 391-3 V1.3.1 (2008-05) - Open Service Access (OSA); Parlay X Web Services; Part 3: Call Notification (Parlay X 2)

SIST ES 202 391-3 V1.3.1:2008 is the ETSI standard for the Parlay X Web Services Call Notification part of Open Service Access (OSA). It specifies how a Parlay X 2 gateway reports call events such as busy, not reachable, no answer and called number, and how an application can decide the call treatment when that control is exposed through the web service. The document is aimed at application developers and telecom platform teams that need standard web service access to call control functions.

What does SIST ES 202 391-3 V1.3.1:2008 specify?

SIST ES 202 391-3 V1.3.1:2008 specifies the Call Notification Web Service for OSA. Clause 1 states the scope, clauses 4 to 10 cover the service description, namespaces, sequence diagrams, XML Schema data types, web service interfaces, faults and service policies, and Annex A provides the normative WSDL.

Annex	What it covers
A	Normative WSDL for Call Notification
B	Bibliography

The document is organized so that the service behavior appears first, then the wire-level interface definition. That matters in practice because implementers can read the call handling model before mapping it to WSDL and XML types.

What are the key requirements of SIST ES 202 391-3 V1.3.1:2008?

The standard separates two service styles: CallDirection for cases where the application decides how the call should be handled, and CallNotification for cases where the application only receives event reports. In practice, that is the main design choice for an implementation.

• Clause 4 explains the service model for handling subscriber-initiated calls. A third-party application can route, end or continue a call, or simply be informed that a call event occurred.
• Clause 5 assigns namespaces to the interfaces and data types. Implementations need the exact namespaces to interoperate across gateway and application systems.
• Clause 6 shows an SMS notification scenario for a missed call. It uses CallNotification together with the Short Messaging Web Service from Part 4, which is useful when the application reacts after the call event rather than steering the call.
• Clause 7 defines the core data model. ActionValues offers Route, Continue and EndCall, Action can also carry a routing address and charging information, and CallEvents covers Busy, NotReachable, NoAnswer and CalledNumber.
• Clause 8.1 defines handleBusy, handleNotReachable, handleNoAnswer and handleCalledNumber. These are synchronous requests from the gateway to the application, and the returned Action tells the gateway what to do next.
• Clause 8.2 defines notifyBusy, notifyNotReachable, notifyNoAnswer and notifyCalledNumber. These notifications inform the application, but they do not let it influence the ongoing call.
• Clauses 8.3 and 8.4 define the manager operations for starting and stopping notifications. The reference carries the notification endpoint, addresses selects the called parties, criteria narrows the event set, and the correlator must be unique when the subscription starts.
• Clauses 9 and 10 keep the common error and policy model unchanged. No new faults or service policies are added here, so implementations rely on ES 202 391-1 for shared exceptions.

What terms does SIST ES 202 391-3 V1.3.1:2008 define?

The document uses a small set of recurring terms that shape the service model.

• OSA - Open Service Access, the architecture that lets applications use network functions through an open standardized interface.
• API - The standard interface exposed to application developers for accessing network functionality.
• WSDL - Web Service Description Language; Annex A gives the document/literal WSDL for the service.
• ActionValues - The enumeration that tells the gateway whether to Route, Continue or EndCall.
• Action - The response structure that carries the selected action, optional routing address, and optional charging information.
• CallEvents - The enumeration for the event types Busy, NotReachable, NoAnswer and CalledNumber.
• correlator - The identifier used to manage a notification request when starting or stopping notifications.

Who uses SIST ES 202 391-3 V1.3.1:2008?

Telecom application developers use this standard when they want to handle calls through web services instead of proprietary call-control protocols. Network operators and gateway implementers use it to expose call events and call routing decisions through a standard OSA interface.

It is also relevant to teams building missed-call SMS services, service-number routing applications, and call-screening or rerouting logic based on status or location. The examples in Clause 4 show those practical uses.

What changed in SIST ES 202 391-3 V1.3.1:2008 from the previous edition?

The document updates ES 202 391 to Parlay X 2.2 and includes maintenance updates. The foreword also states that it is part of the Parlay X 2.2 set and equivalent to 3GPP TS 29.199-03 V6.6.0 (Release 6).

Which standards are used with SIST ES 202 391-3 V1.3.1:2008?

Standard	What it contributes
W3C Recommendation, XML Schema Part 2: Datatypes	The XML datatypes used by the schema definitions and the xsd namespace
ETSI ES 202 391-1, Open Service Access (OSA); Parlay X Web Services; Part 1: Common (Parlay X 2)	Shared definitions, abbreviations, common types, faults and policies used by this part
Parlay X Web Services, Part 4: Short Messaging	The companion service used in the missed-call SMS sequence diagram

What does the SIST ES 202 391-3 V1.3.1:2008 document contain?

The document contains a detailed service description, namespace declarations, a missed-call sequence diagram, XML Schema data type definitions, and the full web service interface model. Clause 8 covers the call-direction and call-notification operations, including their request and response messages and referenced faults.

Annex A provides the WSDL representation in accompanying text files, which is the practical starting point for implementation and interoperability work. Annex B is a bibliography for background reading.

Final draft ETSI ES 202 391-3 V1.3.1 (2008-02)
ETSI Standard
Open Service Access (OSA);
Parlay X Web Services;
Part 3: Call Notification
(Parlay X 2)
�
2 Final draft ETSI ES 202 391-3 V1.3.1 (2008-02)

Reference
RES/TISPAN-01056-03-OSA
Keywords
API, OSA, service
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
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 2008.
© The Parlay Group 2008.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
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 Final draft ETSI ES 202 391-3 V1.3.1 (2008-02)
Contents
Intellectual Property Rights.5
Foreword.5
1 Scope.6
2 References.6
2.1 Normative references.6
3 Definitions and abbreviations.7
3.1 Definitions.7
3.2 Abbreviations.7
4 Detailed service description .7
5 Namespaces.7
6 Sequence diagrams.8
6.1 SMS notification of a missed call.8
7 XML Schema data type definition .8
7.1 ActionValues enumeration.8
7.2 Action structure.9
7.3 CallEvents enumeration.9
8 Web Service interface definition.9
8.1 Interface: CallDirection.9
8.1.1 Operation: handleBusy.10
8.1.1.1 Input message: handleBusyRequest .10
8.1.1.2 Output message: handleBusyResponse.10
8.1.1.3 Referenced faults.10
8.1.2 Operation: handleNotReachable.10
8.1.2.1 Input message: handleNotReachableRequest.10
8.1.2.2 Output message: handleNotReachableResponse.11
8.1.2.3 Referenced faults.11
8.1.3 Operation: handleNoAnswer.11
8.1.3.1 Input message: handleNoAnswerRequest .11
8.1.3.2 Output message: handleNoAnswerResponse.11
8.1.3.3 Referenced faults.11
8.1.4 Operation: handleCalledNumber.11
8.1.4.1 Input message: handleCalledNumberRequest.12
8.1.4.2 Output message: handleCalledNumberResponse.12
8.1.4.3 Referenced faults.12
8.2 Interface: CallNotification.12
8.2.1 Operation: notifyBusy.12
8.2.1.1 Input message: notifyBusyRequest .12
8.2.1.2 Output message: notifyBusyResponse.12
8.2.1.3 Referenced faults.12
8.2.2 Operation: notifyNotReachable.12
8.2.2.1 Input message: notifyNotReachableRequest.13
8.2.2.2 Output message: notifyNotReachableResponse.13
8.2.2.3 Referenced faults.13
8.2.3 Operation: notifyNoAnswer.13
8.2.3.1 Input message: notifyNoAnswerRequest .13
8.2.3.2 Output message: notifyNoAnswerResponse.13
8.2.3.3 Referenced faults.13
8.2.4 Operation: notifyCalledNumber.13
8.2.4.1 Input message: notifyCalledNumberRequest.13
8.2.4.2 Output message: notifyCalledNumberResponse.14
8.2.4.3 Referenced faults.14
ETSI
4 Final draft ETSI ES 202 391-3 V1.3.1 (2008-02)
8.3 Interface: CallDirectionManager.14
8.3.1 Operation: startCallDirectionNotification.14
8.3.1.1 Input message: startCallDirectionNotificationRequest .14
8.3.1.2 Output message: startCallDirectionNotificationResponse .14
8.3.1.3 Referenced Faults.14
8.3.2 Operation: stopCallDirectionNotification.15
8.3.2.1 Input message: stopCallDirectionNotificationRequest .15
8.3.2.2 Output message: stopCallDirectionNotificationResponse .15
8.3.2.3 Referenced Faults.15
8.4 Interface: CallNotificationManager.15
8.4.1 Operation: StartCallNotification.15
8.4.1.1 Input message: startCallNotificationRequest .15
8.4.1.2 Output message: startCallNotificationResponse.15
8.4.1.3 Referenced Faults.16
8.4.2 Operation: stopCallNotification.16
8.4.2.1 Input message: stopCallNotificationRequest .16
8.4.2.2 Output message: stopCallNotificationResponse .16
8.4.2.3 Referenced Faults.16
9 Fault definitions.16
10 Service policies .16
Annex A (normative): WSDL for Call Notification .17
Annex B (informative): Bibliography.18
History .19

ETSI
5 Final draft ETSI ES 202 391-3 V1.3.1 (2008-02)
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 ETSI Standard (ES) has been produced by ETSI Technical Committee Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN), and is now submitted for the ETSI standards
Membership Approval Procedure.
The present document is part 3 of a multi-part deliverable covering Open Service Access (OSA); Parlay X
Web Services, as identified below:
Part 1: "Common";
Part 2: "Third Party Call";
Part 3: "Call Notification";
Part 4: "Short Messaging";
Part 5: "Multimedia Messaging";
Part 6: "Payment";
Part 7: "Account Management";
Part 8: "Terminal Status";
Part 9: "Terminal Location";
Part 10: "Call Handling";
Part 11: "Audio Call";
Part 12: "Multimedia Conference";
Part 13: "Address List Management";
Part 14: "Presence".
The present document has been defined jointly between ETSI, The Parlay Group (http://www.parlay.org) and the 3GPP.
The present document forms part of the Parlay X 2.2 set of specifications.
The present document is equivalent to 3GPP TS 29.199-03 V6.6.0 (Release 6).
ETSI
6 Final draft ETSI ES 202 391-3 V1.3.1 (2008-02)
1 Scope
The present document is part 3 of the Stage 3 Parlay X 2 Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality
through an open standardized interface, i.e. the OSA APIs.
The present document specifies the Call Notification Web Service. The following are defined here:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service Policies.
• WSDL Description of the interfaces.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,
the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the
reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the
method of access to the referenced document and the full network address, with the same punctuation and use of upper
case and lower case letters.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] W3C Recommendation (2 May 2001): "XML Schema Part 2: Datatypes".
NOTE: Available at: http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/.
ETSI
7 Final draft ETSI ES 202 391-3 V1.3.1 (2008-02)
[2] ETSI ES 202 391-1: "Open Service Access (OSA); Parlay X Web Services; Part 1: Common
(Parlay X 2)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ES 202 391-1 [2] apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ES 202 391-1 [2] apply.
4 Detailed service description
Currently, in order to determine the handling of a subscriber initiated call in telecommunication networks we have to
write applications using specific protocols to access Call Control functions provided by network elements. This
approach requires a high degree of network expertise. We can also use the OSA gateway approach, invoking standard
interfaces to gain access to call control capabilities, but these interfaces are usually perceived to be quite complex by
application IT developers. Developers must have advanced telecommunication skills to use Call Control OSA
interfaces.
In this clause we will describe a Parlay X 2 Web Service, Call Notification, for handling calls initiated by a subscriber
in the network. A (third party) application determines how the call should be treated. The overall scope of this Web
Service is to provide simple functions to application developers to determine how a call should be treated. Using the
Web Services, application developers can perform simple handling of network-initiated calls without specific Telco
knowledge.
Examples of usage include the following:
Incoming call handling: A subscriber receives a call while he is logged-on to the Internet. Since this occupies his
telephone connection, he is regarded as busy by the network. The subscriber has an application that is invoked when
somebody tries to call him while he is busy. The application provides the subscriber with a list of choices on how to
handle the call (e.g. route the call to voicemail, redirect the call to a secretary, reject the call). Based on the response of
the subscriber the call is handled in the network. Alternatively, the call is re-routed or released depending on the
preferences of the subscr
...

ETSI Standard
Open Service Access (OSA);
Parlay X Web Services;
Part 3: Call Notification
(Parlay X 2)
�
2 ETSI ES 202 391-3 V1.3.1 (2008-05)

Reference
RES/TISPAN-01056-03-OSA
Keywords
API, OSA, service
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
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 2008.
© The Parlay Group 2008.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
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 ES 202 391-3 V1.3.1 (2008-05)
Contents
Intellectual Property Rights.5
Foreword.5
1 Scope.6
2 References.6
2.1 Normative references.6
3 Definitions and abbreviations.7
3.1 Definitions.7
3.2 Abbreviations.7
4 Detailed service description .7
5 Namespaces.7
6 Sequence diagrams.8
6.1 SMS notification of a missed call.8
7 XML Schema data type definition .8
7.1 ActionValues enumeration.8
7.2 Action structure.9
7.3 CallEvents enumeration.9
8 Web Service interface definition.9
8.1 Interface: CallDirection.9
8.1.1 Operation: handleBusy.10
8.1.1.1 Input message: handleBusyRequest .10
8.1.1.2 Output message: handleBusyResponse.10
8.1.1.3 Referenced faults.10
8.1.2 Operation: handleNotReachable.10
8.1.2.1 Input message: handleNotReachableRequest.10
8.1.2.2 Output message: handleNotReachableResponse.11
8.1.2.3 Referenced faults.11
8.1.3 Operation: handleNoAnswer.11
8.1.3.1 Input message: handleNoAnswerRequest .11
8.1.3.2 Output message: handleNoAnswerResponse.11
8.1.3.3 Referenced faults.11
8.1.4 Operation: handleCalledNumber.11
8.1.4.1 Input message: handleCalledNumberRequest.12
8.1.4.2 Output message: handleCalledNumberResponse.12
8.1.4.3 Referenced faults.12
8.2 Interface: CallNotification.12
8.2.1 Operation: notifyBusy.12
8.2.1.1 Input message: notifyBusyRequest .12
8.2.1.2 Output message: notifyBusyResponse.12
8.2.1.3 Referenced faults.12
8.2.2 Operation: notifyNotReachable.12
8.2.2.1 Input message: notifyNotReachableRequest.13
8.2.2.2 Output message: notifyNotReachableResponse.13
8.2.2.3 Referenced faults.13
8.2.3 Operation: notifyNoAnswer.13
8.2.3.1 Input message: notifyNoAnswerRequest .13
8.2.3.2 Output message: notifyNoAnswerResponse.13
8.2.3.3 Referenced faults.13
8.2.4 Operation: notifyCalledNumber.13
8.2.4.1 Input message: notifyCalledNumberRequest.13
8.2.4.2 Output message: notifyCalledNumberResponse.14
8.2.4.3 Referenced faults.14
ETSI
4 ETSI ES 202 391-3 V1.3.1 (2008-05)
8.3 Interface: CallDirectionManager.14
8.3.1 Operation: startCallDirectionNotification.14
8.3.1.1 Input message: startCallDirectionNotificationRequest .14
8.3.1.2 Output message: startCallDirectionNotificationResponse .14
8.3.1.3 Referenced Faults.14
8.3.2 Operation: stopCallDirectionNotification.15
8.3.2.1 Input message: stopCallDirectionNotificationRequest .15
8.3.2.2 Output message: stopCallDirectionNotificationResponse .15
8.3.2.3 Referenced Faults.15
8.4 Interface: CallNotificationManager.15
8.4.1 Operation: StartCallNotification.15
8.4.1.1 Input message: startCallNotificationRequest .15
8.4.1.2 Output message: startCallNotificationResponse.15
8.4.1.3 Referenced Faults.16
8.4.2 Operation: stopCallNotification.16
8.4.2.1 Input message: stopCallNotificationRequest .16
8.4.2.2 Output message: stopCallNotificationResponse .16
8.4.2.3 Referenced Faults.16
9 Fault definitions.16
10 Service policies .16
Annex A (normative): WSDL for Call Notification .17
Annex B (informative): Bibliography.18
History .19

ETSI
5 ETSI ES 202 391-3 V1.3.1 (2008-05)
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 ETSI Standard (ES) has been produced by ETSI Technical Committee Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN).
The present document is part 3 of a multi-part deliverable covering Open Service Access (OSA); Parlay X
Web Services, as identified below:
Part 1: "Common";
Part 2: "Third Party Call";
Part 3: "Call Notification";
Part 4: "Short Messaging";
Part 5: "Multimedia Messaging";
Part 6: "Payment";
Part 7: "Account Management";
Part 8: "Terminal Status";
Part 9: "Terminal Location";
Part 10: "Call Handling";
Part 11: "Audio Call";
Part 12: "Multimedia Conference";
Part 13: "Address List Management";
Part 14: "Presence".
The present document has been defined jointly between ETSI, The Parlay Group (http://www.parlay.org) and the 3GPP.
The present document forms part of the Parlay X 2.2 set of specifications.
The present document is equivalent to 3GPP TS 29.199-03 V6.6.0 (Release 6).
ETSI
6 ETSI ES 202 391-3 V1.3.1 (2008-05)
1 Scope
The present document is part 3 of the Stage 3 Parlay X 2 Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality
through an open standardized interface, i.e. the OSA APIs.
The present document specifies the Call Notification Web Service. The following are defined here:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service Policies.
• WSDL Description of the interfaces.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,
the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the
reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the
method of access to the referenced document and the full network address, with the same punctuation and use of upper
case and lower case letters.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] W3C Recommendation (2 May 2001): "XML Schema Part 2: Datatypes".
NOTE: Available at: http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/.
ETSI
7 ETSI ES 202 391-3 V1.3.1 (2008-05)
[2] ETSI ES 202 391-1: "Open Service Access (OSA); Parlay X Web Services; Part 1: Common
(Parlay X 2)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ES 202 391-1 [2] apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ES 202 391-1 [2] apply.
4 Detailed service description
Currently, in order to determine the handling of a subscriber initiated call in telecommunication networks we have to
write applications using specific protocols to access Call Control functions provided by network elements. This
approach requires a high degree of network expertise. We can also use the OSA gateway approach, invoking standard
interfaces to gain access to call control capabilities, but these interfaces are usually perceived to be quite complex by
application IT developers. Developers must have advanced telecommunication skills to use Call Control OSA
interfaces.
In this clause we will describe a Parlay X 2 Web Service, Call Notification, for handling calls initiated by a subscriber
in the network. A (third party) application determines how the call should be treated. The overall scope of this Web
Service is to provide simple functions to application developers to determine how a call should be treated. Using the
Web Services, application developers can perform simple handling of network-initiated calls without specific Telco
knowledge.
Examples of usage include the following:
Incoming call handling: A subscriber receives a call while he is logged-on to the Internet. Since this occupies his
telephone connection, he is regarded as busy by the network. The subscriber has an application that is invoked when
somebody tries to call him while he is busy. The application provides the subscriber with a list of choices on how to
handle the call (e.g. route the call to voicemail, redirect the call to a secretary, reject the call). Based on the response of
the subscriber the call is handled in the network. Alternatively, the call is re-routed or released depending on the
preferences of the subscriber and some context
...

SLOVENSKI STANDARD
01-september-2008
Odprti dostop do storitve (OSA) - Spletne storitve Parlay X - 3. del: Priglasitev klica
(Parlay X 2)
Open Service Access (OSA) - Parlay X Web Services - Part 3: Call Notification (Parlay X
2)
Ta slovenski standard je istoveten z: ES 202 391-3 Version 1.3.1
ICS:
35.100.01 Medsebojno povezovanje Open systems
odprtih sistemov na splošno interconnection in general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

ETSI Standard
Open Service Access (OSA);
Parlay X Web Services;
Part 3: Call Notification
(Parlay X 2)
�
2 ETSI ES 202 391-3 V1.3.1 (2008-05)

Reference
RES/TISPAN-01056-03-OSA
Keywords
API, OSA, service
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
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 2008.
© The Parlay Group 2008.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
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 ES 202 391-3 V1.3.1 (2008-05)
Contents
Intellectual Property Rights.5
Foreword.5
1 Scope.6
2 References.6
2.1 Normative references.6
3 Definitions and abbreviations.7
3.1 Definitions.7
3.2 Abbreviations.7
4 Detailed service description .7
5 Namespaces.7
6 Sequence diagrams.8
6.1 SMS notification of a missed call.8
7 XML Schema data type definition .8
7.1 ActionValues enumeration.8
7.2 Action structure.9
7.3 CallEvents enumeration.9
8 Web Service interface definition.9
8.1 Interface: CallDirection.9
8.1.1 Operation: handleBusy.10
8.1.1.1 Input message: handleBusyRequest .10
8.1.1.2 Output message: handleBusyResponse.10
8.1.1.3 Referenced faults.10
8.1.2 Operation: handleNotReachable.10
8.1.2.1 Input message: handleNotReachableRequest.10
8.1.2.2 Output message: handleNotReachableResponse.11
8.1.2.3 Referenced faults.11
8.1.3 Operation: handleNoAnswer.11
8.1.3.1 Input message: handleNoAnswerRequest .11
8.1.3.2 Output message: handleNoAnswerResponse.11
8.1.3.3 Referenced faults.11
8.1.4 Operation: handleCalledNumber.11
8.1.4.1 Input message: handleCalledNumberRequest.12
8.1.4.2 Output message: handleCalledNumberResponse.12
8.1.4.3 Referenced faults.12
8.2 Interface: CallNotification.12
8.2.1 Operation: notifyBusy.12
8.2.1.1 Input message: notifyBusyRequest .12
8.2.1.2 Output message: notifyBusyResponse.12
8.2.1.3 Referenced faults.12
8.2.2 Operation: notifyNotReachable.12
8.2.2.1 Input message: notifyNotReachableRequest.13
8.2.2.2 Output message: notifyNotReachableResponse.13
8.2.2.3 Referenced faults.13
8.2.3 Operation: notifyNoAnswer.13
8.2.3.1 Input message: notifyNoAnswerRequest .13
8.2.3.2 Output message: notifyNoAnswerResponse.13
8.2.3.3 Referenced faults.13
8.2.4 Operation: notifyCalledNumber.13
8.2.4.1 Input message: notifyCalledNumberRequest.13
8.2.4.2 Output message: notifyCalledNumberResponse.14
8.2.4.3 Referenced faults.14
ETSI
4 ETSI ES 202 391-3 V1.3.1 (2008-05)
8.3 Interface: CallDirectionManager.14
8.3.1 Operation: startCallDirectionNotification.14
8.3.1.1 Input message: startCallDirectionNotificationRequest .14
8.3.1.2 Output message: startCallDirectionNotificationResponse .14
8.3.1.3 Referenced Faults.14
8.3.2 Operation: stopCallDirectionNotification.15
8.3.2.1 Input message: stopCallDirectionNotificationRequest .15
8.3.2.2 Output message: stopCallDirectionNotificationResponse .15
8.3.2.3 Referenced Faults.15
8.4 Interface: CallNotificationManager.15
8.4.1 Operation: StartCallNotification.15
8.4.1.1 Input message: startCallNotificationRequest .15
8.4.1.2 Output message: startCallNotificationResponse.15
8.4.1.3 Referenced Faults.16
8.4.2 Operation: stopCallNotification.16
8.4.2.1 Input message: stopCallNotificationRequest .16
8.4.2.2 Output message: stopCallNotificationResponse .16
8.4.2.3 Referenced Faults.16
9 Fault definitions.16
10 Service policies .16
Annex A (normative): WSDL for Call Notification .17
Annex B (informative): Bibliography.18
History .19

ETSI
5 ETSI ES 202 391-3 V1.3.1 (2008-05)
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 ETSI Standard (ES) has been produced by ETSI Technical Committee Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN).
The present document is part 3 of a multi-part deliverable covering Open Service Access (OSA); Parlay X
Web Services, as identified below:
Part 1: "Common";
Part 2: "Third Party Call";
Part 3: "Call Notification";
Part 4: "Short Messaging";
Part 5: "Multimedia Messaging";
Part 6: "Payment";
Part 7: "Account Management";
Part 8: "Terminal Status";
Part 9: "Terminal Location";
Part 10: "Call Handling";
Part 11: "Audio Call";
Part 12: "Multimedia Conference";
Part 13: "Address List Management";
Part 14: "Presence".
The present document has been defined jointly between ETSI, The Parlay Group (http://www.parlay.org) and the 3GPP.
The present document forms part of the Parlay X 2.2 set of specifications.
The present document is equivalent to 3GPP TS 29.199-03 V6.6.0 (Release 6).
ETSI
6 ETSI ES 202 391-3 V1.3.1 (2008-05)
1 Scope
The present document is part 3 of the Stage 3 Parlay X 2 Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality
through an open standardized interface, i.e. the OSA APIs.
The present document specifies the Call Notification Web Service. The following are defined here:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service Policies.
• WSDL Description of the interfaces.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,
the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the
reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the
method of access to the referenced document and the full network address, with the same punctuation and use of upper
case and lower case letters.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] W3C Recommendation (2 May 2001): "XML Schema Part 2: Datatypes".
NOTE: Available at: http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/.
ETSI
7 ETSI ES 202 391-3 V1.3.1 (2008-05)
[2] ETSI ES 202 391-1: "Open Service Access (OSA); Parlay X Web Services; Part 1: Common
(Parlay X 2)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ES 202 391-1 [2] apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ES 202 391-1 [2] apply.
4 Detailed service description
Currently, in order to determine the handling of a subscriber initiated call in telecommunication networks we have to
write applications using specific protocols to access Call Control functions provided by network elements. This
approach requires a high degree of network expertise. We can also use the OSA gateway approach, invoking standard
interfaces to gain access to call control capabilities, but these interfaces are usually perceived to be quite complex by
application IT developers. Developers must have advanced telecommunication skills to use Call Control OSA
interfaces.
In this clause we will describe a Parlay X 2 Web Service, Call Notification, for handling calls initiated by a subscriber
in the network. A (third party) application determines how the call should be treated. The overall scope of this Web
Service is to provide simple functions to application developers to determine how a call should be treated. Using the
Web Services, application developers can perform simple handling of network-initiated calls without specific Telco
knowledge.
Examples of usage include the following:
Incoming call handling: A subscriber receives a call while he is logged-on to the Internet. Since this occupies his
telephone connection, he is regarded as busy by the network. The subscriber has an application that is invoked when
somebody tries to call him while he is busy. The application provides the subscriber with a list of choices on how to
handle the call (e.
...