Oracle® Communications Service Broker Processing Domain Configuration Guide Release 6.0 Part Number E23525-02 |
|
|
View PDF |
This chapter describes how to configure IM-ASF SAL using the Service Broker Administration Console and Java MBeans.
This section describes how to configure the IM-ASF SAL module using the Service Broker Administration Console. This section assumes that you have already created and activated an IM-ASF SAL instance.
SAL is an Oracle proprietary protocol used by Oracle Communications Service Broker to communicate with SAL-based applications such as SVC and VPN, and applications that you implement using the SAL API. SAL is closely related to the SIP protocol and contains many of the same parameters, such as the SIP timers.
To access the IM-ASF SAL configuration screen:
In the Administration Console domain navigation pane, expand OCSB.
Expand Processing Tier.
Expand Interworking Modules.
A list of the currently deployed Interworking Modules is displayed.
From the module list, select the IM-ASF SAL module instance to configure.
Table 24-1 shows the IM-ASF SAL Configuration pane subtabs. The following sections explain the configuration parameters in each of the subtabs.
Subtab | Description |
---|---|
Application Server |
Defines a SAL Application Server for IM-ASF SAL to interact with. See "Configuring Application Server Parameters" for more information. |
Session Keep Alive |
Defines the keep-alive mechanism that IM-ASF SAL uses to test session existence. See "Configuring Session Keep Alive Parameters" for more information. |
SAL |
Use to configure the SAL interface attributes of this IM. |
Monitoring |
Use to define how Runtime MBeans and notifications should operate. See "Configuring Monitoring Parameters" for more information. |
Each IM-ASF SAL instance interacts with one SAL-based application. You specify this server using the Application Server subtab.
Table 24-2 describes configuration parameters on the Application Server subtab.
Table 24-2 Application Server Configuration Parameters
Name | Data Type | Description |
---|---|---|
SAL Application Address |
String |
Specifies the SIP URI address of the Service Broker Feature Module application to connect this IM-ASF -SAL to. The syntax is sip:Applicaton_Name@Hostname.com. Where: Application_Name is be one of the following:
Hostname is the system hosting the application. |
SAL Mode |
String |
Specifies the SAL mode. The Session Keep Alive Parameters and SAL Parameters are only valid for EXTERNAL mode. Can be one of the following:
|
These parameters are only valid in EXTERNAL mode.
IM-ASF SAL performs regular checks of SAL sessions using the keep-alive mechanism. This mechanism enables IM-ASF SAL to check whether or not a session is still in progress by periodically sending INFO requests to the SAL application server and checking the responses. A 200 OK response indicates that the session is still in progress. Any other response, or no response at all indicates that the session was dropped.
Table 24-3 describes configuration parameters on the Session Keep Alive subtab.
Table 24-3 Session Keep Alive Configuration Parameters
Name | Data Type | Description |
---|---|---|
Info Keep Alive Interval in Seconds |
Integer |
Specifies the interval, in seconds, between INFO requests. To disable the keep-alive mechanism, set this parameter to -1. If no parameter is present the keep-alive mechanism is disabled. |
Info Keep Alive Time to Die |
Integer |
Specifies the interval, in seconds, that the IM-ASF SAL waits for a response to keep-alive messages. If there is no response within the time specified, the session is ended. |
These parameters are only valid in EXTERNAL mode.
Enables you to configure standard SAL protocol parameters. These SAL parameters are equivalent to their SIP counterparts.
Table 24-4 describes configuration parameters on the SAL subtab.
Table 24-4 SAL Configuration Parameters
Name | Data Type | Description |
---|---|---|
Retransmission Interval Limit (T2 Timeout) |
Integer |
Specifies a maximum retransmission interval for non-INVITE requests and INVITE responses. Default value: 20 seconds |
T7 Timeout Interval in Seconds |
Integer |
Specifies the time period in seconds that IM-ASF SAL waits for the first SAL provisional response (except for 100) after sending an INVITE request. Default value: 40 seconds. |
T9 Timeout Interval in Seconds |
Integer |
Specifies the time period in seconds for IM-ASF SAL to wait for an OK response or any call release response (for example, ERROR) in response to an INVITE request. Default value: 90 seconds |
Max Call Duration Timeout Interval in Minutes |
Integer |
Specifies the maximum duration of established calls in minutes, which are measured from OK to BYE. When this timer expires, IM-ASF SAL releases the session. Default value: 60 minutes |
The Monitoring tab enables you to define how Runtime MBeans and notifications operate for an IM-ASF SAL. For more information about configuring monitoring, see "Configuring Monitoring with the Administration Console".
Service Broker provides a set of MBeans that provide attributes and operations for configuring the IM-ASF SAL through JMX. You can change these using the Service Broker Java Monitoring and Management Console or another JMX editor. Figure 24-0 shows the hierarchy of the IM-ASF SAL MBeans.
The following sections provide reference information for the IM-ASF SAL configuration MBeans.
Note:
MBeans described in this guide may include additional advanced attributes, which are not described in the guide. Advanced attributes are reserved for internal use. Do not change these attributes.The following MBeans are common for all components of Service Broker. See "Configuring Monitoring with Java MBeans" for details:
MonitoringGeneralMBean
ThresholdCrossedNotificationRulesMBean
ThresholdCrossedNotificationRuleMBean
StateChangedNotificationRulesMBean
StateChangedNotificationRuleMBean
ImasfMBean is the root MBean for the IM-ASF -SAL configuration.
Created automatically
Modulename: This attribute is reserved for internal use. Do not change this attribute.
Version: This attribute is reserved for internal use. Do not change this attribute.
Name: This attribute is reserved for internal use. Do not change this attribute.
TsterTimeoutIntervalSeconds: This attribute is reserved for internal use. Do not change this attribute.
TcterTimeoutIntervalSeconds: This attribute is reserved for internal use. Do not change this attribute.
TspTimeoutIntervalSeconds: This attribute is reserved for internal use. Do not change this attribute.
TcpTimeoutIntervalSeconds: This attribute is reserved for internal use. Do not change this attribute.
TcaTimeoutIntervalSeconds: This attribute is reserved for internal use. Do not change this attribute.
MinSubscriptionDurationSeconds: This attribute is reserved for internal use. Do not change this attribute.
MaxSubscriptionDurationSeconds: This attribute is reserved for internal use. Do not change this attribute.
DefaultSubscriptionDurationSeconds: This attribute is reserved for internal use. Do not change this attribute.
Rel100DefaultMode: This attribute is reserved for internal use. Do not change this attribute.
DeploymentName: The module instance name of the module this MBean configures.
None
Use ApplicationServerMBean to define the SAL Application Server that IM-ASF SAL interacts with.
Created automatically
AppAddress: For details see Table 24-2.
DeploymentName: The module instance name of the module this MBean configures.
None.
Use SipMBean to configure standard SIP protocol parameters.
Created automatically
T2TimeoutIntervalSeconds.
T7TimeoutIntervalSeconds.
T9TimeoutIntervalSeconds.
MaxCallDurationTimeoutIntervalInMinutes.
DeploymentName: The module instance name of the module this MBean configures.
For details on these attributes see Table 24-4
None
Use SessionKeepAliveMBean to define the keep-alive mechanism that IM-ASF SAL uses to test session existence with SIP Application Servers.
Created automatically.
InfoKeepAliveInterval.
InfoKeepAliveTimeToDie.
DeploymentName: The module instance name that this MBean configures.
For details on these attibutes, see Table 24-3.
None
Oracle recommends that you have a special instance of IM-ASF, a default IM-ASF instance named IMASF_default in every system.
To understand why you should create a default IM-ASF module instance, see "Supporting Orchestration with Non-Configured Application".
For information on defining a default IM-ASF module, see "Defining a Default IM-ASF Module".