|
||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
See:
Description
Interface Summary | |
---|---|
CallNotification | When a call events occur in the network, the application may be notified of these events. |
CallNotification_RI | |
CallNotificationHome | |
CallNotificationManager | The call notification manager enables applications to set up and tear down notifications for calls online. |
CallNotificationManager_RI | |
CallNotificationManagerHome | |
CallNotificationManagerService | |
CallNotificationService |
Class Summary | |
---|---|
Action | The Action data type is a structure containing the following parameters. |
Action_Deser | |
Action_Helper | |
Action_Ser | |
ActionValues | The ActionValues data type is an enumeration with the following values. |
CallEvents | The CallEvents data type is an enumeration with the following values. |
CallNotificationBindingStub | |
CallNotificationManagerBindingStub | |
CallNotificationManagerProxy | |
CallNotificationManagerServiceInformation | |
CallNotificationManagerServiceLocator | |
CallNotificationProxy | |
CallNotificationServiceInformation | |
CallNotificationServiceLocator |
Call Notification.
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, for example, 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.
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
* References are either specific (identified by date of publication and/or edition number or version number) or nonspecific.
* For a specific reference, subsequent revisions do not apply.
* For a non-specific reference, the latest version applies.
Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference.
[1] W3C Recommendation (2 May 2001): "XML Schema Part 2: Datatypes".
NOTE: Available at http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/. [2] ETSI ES 202 391-1: "Open Service Access (OSA); Parlay X 2 Web Services;
Part 1: Common".
For the purposes of the present document, the terms and definitions given in ES 202 391-1 [2] apply.
For the purposes of the present document, the abbreviations defined in ES 202 391-1 [2] apply.
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 (for example, 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 information (for example, based on the status or location of the subscriber).
Service numbers: An application is triggered whenever a certain service number is dialled. This number is used to connect the caller to one of the maintenance personnel. The application redirects the call to the appropriate maintenance person based on, for example, calling party number, time, location and availability of the maintenance personnel.
SMS notification of missed calls: An application offers the subscriber the possibility to be notified via SMS whenever he misses a call. The application registers to be notified when calls to its subscribers encounter busy, no-answer or notreachable. The application does not influence the call treatment, but sends an SMS containing the calling party number, the time and reason why the call was missed.
The CallDirection interface uses the namespace: http://www.csapi.org/wsdl/parlayx/call_direction/v2_12
The CallDirectionNotificationManager interface uses the namespace: http://www.csapi.org/wsdl/parlayx/call_direction/notification_manager/v2_23
The CallNotification interface uses the namespace: http://www.csapi.org/wsdl/parlayx/call_notification/v2_12
The CallNotificationManager interface uses the namespace: http://www.csapi.org/wsdl/parlayx/call_notification/notification_manager/v2_23
The data types are defined in the namespace: http://www.csapi.org/schema/parlayx/call_notification/v2_12
The 'xsd' namespace is used in the present document to refer to the XML Schema data types defined in XML Schema [1]. The use of the name 'xsd' is not semantically significant.
Showing the use of the CallNotification and Short Messaging Web Services, an SMS is sent to a person who misses a call (no answer). This sequence assumes that the provisioning of the “no answer” call notification has occurred independently.
The ActionValues data type is an enumeration with the following values.
Route
Request to (re-)route the call to the address indicated with routingAddress.
Continue
Request to continue the call without any changes. This will result in normal handling of the event in the network.
EndCall
Request to end the call. This will result in termination of the call. The callingParty will receive a tone or announcement.
The Action data type is a structure containing the following parameters.
actionToPerform
ActionValues
Indicates the action as described below
routingAddress
xsd:anyURI
NoYes
The address to be used in case the action indicates 'Route'
charging
common:ChargingInformation
Charge to apply to this call
The CallEvents data type is an enumeration with the following values.
Busy
Called party is busy.
NotReachable
Called party is not reachable. NoAnswer
Called party doesn’t answer.
CalledNumber
A call between two parties is being attempted.
No new faults are defined for this service.
No service policies are defined for this service.
|
||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |