http://www.ibm.com/wsdl/soa/pxcd/v1_0/interface
The CallDirection Port Type

This subclause describes an initial set of capabilities in terms of message invocations, parameters and data types. The message-based invocations are:

  • handleBusy.
  • handleNotReachable.
  • handleNoAnswer.
  • handleCalledNumber.

These messages are initiated by the Call Notification Web Service (running in a Parlay X Gateway) and invoke an application Web Service(s), as a result of activity in the network. The result of the invocation of a handle<Event> operation is used as an indication on how the call should be handled in the network. The application can not keep control over the call after handling the event; every event handling is a separate occurrence.

Note that because the results of the invocations of the application Web Service(s) determine call handling in the network, the names of the methods are prefixed with 'handle', rather than 'notify'. The prefix 'notify' would imply a more asynchronous behaviour, whereas 'handle' shows the synchronous nature of these invocations.

The criteria for which the application Web Service(s) should be invoked, such as type of events (busy, answer, etc.), a URI to the Web Service and triggered addresses should be provisioned by the operator in an off-line process.

This interface is part of the collection of Parlay X outbound notifications supported by the PX Notification common component.

 Collapse Operations
CallDirection_handleBusyResponse  handleBusy (handleBusy parameters) [faults:  ServiceException  PolicyException  InvocationException  ]

The invocation of handleBusy requests the application to inform the gateway how to handle the call between two addresses, the callingParty and the calledParty, where the calledParty is busy when the call is received. Optionally, the callers name is provided. The application returns the action, which directs the gateway to perform one of the following actions:

  • "Continue", resulting in normal handling of the busy event in the network, e.g. playing of a busy tone to the callingParty.
  • "EndCall", resulting in the call being terminated; the exact tone or announcement that will be played to the callingParty is operator-specific.
  • "Route", resulting in the call being re-routed to a calledParty specified by the application.

Optionally, in the action parameter, the application can also indicate the charging information.


CallDirection_handleCalledNumberResponse  handleCalledNumber (handleCalledNumber parameters) [faults:  ServiceException  PolicyException  InvocationException  ]

The invocation of handleCalledNumber requests the application to inform the gateway how to handle the call between two addresses, the callingParty and the calledParty. The method is invoked when the callingParty tries to call the calledParty, but before the network routes the call to the calledParty. For example, the calledParty does not have to refer to a real end user, i.e., it could be a service number. Optionally, the callers name is provided. The application returns the action, which directs the gateway to perform one of the following actions:

  • "Continue", resulting in normal handling in the network, i.e. the call will be routed to the calledParty number, as originally dialled.
  • "EndCall", resulting in the call being terminated; the exact tone or announcement that will be played to the callingParty is operator-specific.
  • "Route", resulting in the call being re-routed to a calledParty specified by the application.

Optionally, in the action parameter, the application can also indicate the charging information.


CallDirection_handleNoAnswerResponse  handleNoAnswer (handleNoAnswer parameters) [faults:  ServiceException  PolicyException  InvocationException  ]

The invocation of handleNoAnswer requests the application to inform the gateway how to handle the call between two addresses, the callingParty and the calledParty, where the calledParty does not answer the received call. Optionally, the callers name is provided. The application returns the action, which directs the gateway to perform one of the following actions:

  • "Continue", resulting in normal handling of the 'no answer' event in the network, e.g. playing of a busy tone to the callingParty.
  • "EndCall", resulting in the call being terminated; the exact tone or announcement that will be played to the callingParty is operator-specific.
  • "Route", resulting in the call being re-routed to a calledParty specified by the application.

Optionally, in the action parameter, the application can also indicate the charging information.


CallDirection_handleNotReachableResponse  handleNotReachable (handleNotReachable parameters) [faults:  ServiceException  PolicyException  InvocationException  ]

The invocation of handleNotReachable requests the application to inform the gateway how to handle the call between two addresses, the callingParty and the calledParty, where the calledParty is not reachable when the call is received. Optionally, the callers name is provided. The application returns the action, which directs the gateway to perform one of the following actions:

  • "Continue", resulting in normal handling of the 'not reachable' event in the network, e.g. playing of a busy tone to the callingParty.
  • "EndCall", resulting in the call being terminated; the exact tone or announcement that will be played to the callingParty is operator-specific.
  • "Route", resulting in the call being re-routed to a calledParty specified by the application.

Optionally, in the action parameter, the application can also indicate the charging information.


 Collapse XML
-<wsdl:portType  name="CallDirection">
-<wsdl:documentation>
<xhtml:p>This subclause describes an initial set of capabilities in terms of message invocations, parameters and data types. The message-based invocations are:</xhtml:p>
-<xhtml:ul>
<xhtml:li>handleBusy.</xhtml:li>
<xhtml:li>handleNotReachable.</xhtml:li>
<xhtml:li>handleNoAnswer.</xhtml:li>
<xhtml:li>handleCalledNumber.</xhtml:li>
</xhtml:ul>
<xhtml:p>These messages are initiated by the Call Notification Web Service (running in a Parlay X Gateway) and invoke an application Web Service(s), as a result of activity in the network. The result of the invocation of a handle<Event> operation is used as an indication on how the call should be handled in the network. The application can not keep control over the call after handling the event; every event handling is a separate occurrence.</xhtml:p>
<xhtml:p>Note that because the results of the invocations of the application Web Service(s) determine call handling in the network, the names of the methods are prefixed with 'handle', rather than 'notify'. The prefix 'notify' would imply a more asynchronous behaviour, whereas 'handle' shows the synchronous nature of these invocations.</xhtml:p>
<xhtml:p>The criteria for which the application Web Service(s) should be invoked, such as type of events (busy, answer, etc.), a URI to the Web Service and triggered addresses should be provisioned by the operator in an off-line process.</xhtml:p>
-<xhtml:p>
-<xhtml:b>
<xhtml:i>This interface is part of the collection of Parlay X outbound notifications supported by the PX Notification common component.</xhtml:i>
</xhtml:b>
</xhtml:p>
</wsdl:documentation>
-<wsdl:operation  name="handleBusy">
-<wsdl:documentation>
<xhtml:p>The invocation of handleBusy requests the application to inform the gateway how to handle the call between two addresses, the callingParty and the calledParty, where the calledParty is busy when the call is received. Optionally, the callers name is provided. The application returns the action, which directs the gateway to perform one of the following actions:</xhtml:p>
-<xhtml:ul>
<xhtml:li>"Continue", resulting in normal handling of the busy event in the network, e.g. playing of a busy tone to the callingParty.</xhtml:li>
<xhtml:li>"EndCall", resulting in the call being terminated; the exact tone or announcement that will be played to the callingParty is operator-specific.</xhtml:li>
<xhtml:li>"Route", resulting in the call being re-routed to a calledParty specified by the application.</xhtml:li>
</xhtml:ul>
<xhtml:p>Optionally, in the action parameter, the application can also indicate the charging information.</xhtml:p>
</wsdl:documentation>
<wsdl:fault  message="parlayx_common_faults:ServiceException"  name="ServiceException" />
<wsdl:fault  message="parlayx_common_faults:PolicyException"  name="PolicyException" />
<wsdl:fault  message="soa_pxnotify_faults:InvocationException"  name="InvocationException" />
</wsdl:operation>
-<wsdl:operation  name="handleNotReachable">
-<wsdl:documentation>
<xhtml:p>The invocation of handleNotReachable requests the application to inform the gateway how to handle the call between two addresses, the callingParty and the calledParty, where the calledParty is not reachable when the call is received. Optionally, the callers name is provided. The application returns the action, which directs the gateway to perform one of the following actions:</xhtml:p>
-<xhtml:ul>
<xhtml:li>"Continue", resulting in normal handling of the 'not reachable' event in the network, e.g. playing of a busy tone to the callingParty.</xhtml:li>
<xhtml:li>"EndCall", resulting in the call being terminated; the exact tone or announcement that will be played to the callingParty is operator-specific.</xhtml:li>
<xhtml:li>"Route", resulting in the call being re-routed to a calledParty specified by the application.</xhtml:li>
</xhtml:ul>
<xhtml:p>Optionally, in the action parameter, the application can also indicate the charging information.</xhtml:p>
</wsdl:documentation>
<wsdl:fault  message="parlayx_common_faults:ServiceException"  name="ServiceException" />
<wsdl:fault  message="parlayx_common_faults:PolicyException"  name="PolicyException" />
<wsdl:fault  message="soa_pxnotify_faults:InvocationException"  name="InvocationException" />
</wsdl:operation>
-<wsdl:operation  name="handleNoAnswer">
-<wsdl:documentation>
<xhtml:p>The invocation of handleNoAnswer requests the application to inform the gateway how to handle the call between two addresses, the callingParty and the calledParty, where the calledParty does not answer the received call. Optionally, the callers name is provided. The application returns the action, which directs the gateway to perform one of the following actions:</xhtml:p>
-<xhtml:ul>
<xhtml:li>"Continue", resulting in normal handling of the 'no answer' event in the network, e.g. playing of a busy tone to the callingParty.</xhtml:li>
<xhtml:li>"EndCall", resulting in the call being terminated; the exact tone or announcement that will be played to the callingParty is operator-specific.</xhtml:li>
<xhtml:li>"Route", resulting in the call being re-routed to a calledParty specified by the application.</xhtml:li>
</xhtml:ul>
<xhtml:p>Optionally, in the action parameter, the application can also indicate the charging information.</xhtml:p>
</wsdl:documentation>
<wsdl:fault  message="parlayx_common_faults:ServiceException"  name="ServiceException" />
<wsdl:fault  message="parlayx_common_faults:PolicyException"  name="PolicyException" />
<wsdl:fault  message="soa_pxnotify_faults:InvocationException"  name="InvocationException" />
</wsdl:operation>
-<wsdl:operation  name="handleCalledNumber">
-<wsdl:documentation>
<xhtml:p>The invocation of handleCalledNumber requests the application to inform the gateway how to handle the call between two addresses, the callingParty and the calledParty. The method is invoked when the callingParty tries to call the calledParty, but before the network routes the call to the calledParty. For example, the calledParty does not have to refer to a real end user, i.e., it could be a service number. Optionally, the callers name is provided. The application returns the action, which directs the gateway to perform one of the following actions:</xhtml:p>
-<xhtml:ul>
<xhtml:li>"Continue", resulting in normal handling in the network, i.e. the call will be routed to the calledParty number, as originally dialled.</xhtml:li>
<xhtml:li>"EndCall", resulting in the call being terminated; the exact tone or announcement that will be played to the callingParty is operator-specific.</xhtml:li>
<xhtml:li>"Route", resulting in the call being re-routed to a calledParty specified by the application.</xhtml:li>
</xhtml:ul>
<xhtml:p>Optionally, in the action parameter, the application can also indicate the charging information.</xhtml:p>
</wsdl:documentation>
<wsdl:fault  message="parlayx_common_faults:ServiceException"  name="ServiceException" />
<wsdl:fault  message="parlayx_common_faults:PolicyException"  name="PolicyException" />
<wsdl:fault  message="soa_pxnotify_faults:InvocationException"  name="InvocationException" />
</wsdl:operation>
</wsdl:portType>
 Collapse Used-By
Service Port Binding
CallDirectionService CallDirection CallDirectionBinding
Generated by WSDLdoc ©