Oracle® Communications Service Broker Orchestration Studio User's Guide Release 6.0 Part Number E23532-02 |
|
|
View PDF |
This chapter describes how to use the Orchestration Studio to define the OE behavior depending on the response that the OE received from an application.
You can define whether the OE continues or terminates the session depending on the response that the OE received from an application. You can specify the following:
Whether or not the OE continues the session when receiving an error from the application. See "Defining the OE Behavior on Receiving an Error from an Application" for more information.
Whether or not the OE continues the session when receiving a response with the specified code from the application. See "Defining the OE Behavior on Receiving a Response from an Application" for more information.
If an application returns an error, such as a 400 Bad Response to an INVITE message, you can specify whether the OE forwards the message to the next application in the chain or terminates the session.
To specify the OE behavior:
In the orchestration logic flow, select the IM for which you want to specify default handling.
By default, Default Handling is set to 0 to continue the session.
Click the Actions tab.
In the Default Handling field, type one of the following:
To continue the session, type 0
To terminate the session, type 1
You can configure the OE to forward the session to the next application whose conditions are met, when the OE receives a specific response from an application. The ability of the OE to forward the session to the next application is known as Forced Back to Back (FB2B).
To set Back to Back response codes:
In the orchestration logic flow, select the IM whose responses are to be forwarded Back to Back.
Click the Actions tab.
Select the Back to Back checkbox.
The Response field becomes available.
In the Response field, type the response codes according to which the OE continues the session.
You can add as many response codes as required, separated by a comma and a space.
See "Forcing Back to Back" for an example of a use case using FB2B.