Oracle® Communications Service Broker Processing Domain Configuration Guide Release 6.0 Part Number E23525-02 |
|
|
View PDF |
The following sections describe how to configure IM-ASF using the Service Broker Administration Console and Java MBeans.
This section describes how to configure IM-ASF SIP module instances using the Service Broker Administration Console.
To access the IM-ASF SIP configuration screen:
In the domain navigation pane, expand OCSB.
Expand Processing Tier.
Select Interworking Modules.
A list of currently deployed Interworking Modules is displayed.
From the module list, select the module instance that you want to configure.
The IM-ASF SIP configuration pane contains the subtabs described in Table 22-1.
Table 22-1 IM-ASF Configuration Subtabs
Subtab | Description |
---|---|
Application Server |
Enables you to define the SIP Application Server that IM-ASF SIP interact with. See "Configuring Application Server Parameters" for more information. |
Session Keep Alive |
Enables you to define the keep-alive mechanism that is used to test session existence with SIP Application Servers. See "Configuring Session Keep Alive Parameters" for more information. |
SIP |
Enables you to configure standard SIP protocol parameters. See "Configuring SIP Parameters" for more information. |
Monitoring |
Enables you to define how Runtime MBeans and notifications operate. See "Configuring Monitoring Parameters" for more information. |
An IM-ASF SIP module instance interacts with one SIP Application Server. The Application Server subtab enables you to define an alias for this Application Server.
Table 22-2 describes configuration parameters on the Application Server subtab.
IM-ASF SIP performs regular checks of SIP sessions using a mechanism known as keep-alive mechanism. This mechanism enables the IM-ASF SIP to check whether or not a session is still in progress by periodically sending INFO requests to the SIP AS and checking the response. 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 22-3 describes configuration parameters on the Session Keep Alive subtab.
Table 22-3 Session Keep Alive Parameters
Name | Type | Description |
---|---|---|
INFO Keep Alive Interval in Seconds |
INT |
Specifies the interval, in seconds, between consecutive invocations of INFO requests. To disable the keep-alive mechanism, set this parameter to -1. When this parameter is not defined, then the keep-alive mechanism is disabled. |
INFO Keep Alive Time to Die |
INT |
Specifies the interval, in seconds, that the IM-ASF SIP waits for a response to keep-alive messages. If there is no response within the time specified in this parameter, the session is ended. |
Enables you to configure standard SIP protocol parameters.
Table 22-4 describes configuration parameters on the SIP subtab.
Name | Type | Description |
---|---|---|
Max Call Duration Timeout Interval in Minutes |
INT |
Specifies the maximum duration of established calls which are measured from OK to BYE. When this timer expires, IM-ASF SIP releases the session. Default value: 60 minutes |
Retransmission Interval Limit |
INT |
Specifies a maximum retransmission interval for non-INVITE requests and INVITE responses. Default value: 20 seconds |
T7 Timeout Interval in Seconds |
INT |
Specifies the time period in seconds during which the IM-ASF SIP waits for the first SIP provisional response (except for 100) after sending an INVITE request. Default value: 40 seconds. |
T9 Timeout Interval in Seconds |
INT |
Specifies the time period in seconds during which the IM-ASF SIP waits for an OK response or any call release response (for example, ERROR) after sending an INVITE request. Default value: 90 seconds |
The Monitoring tab enables you to define how Runtime MBeans and notifications operate for an IM-ASF. 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 SIP through JMX. Figure 22-1 shows the hierarchy of the IM-ASF SIP MBeans.
The following sections provide reference information for the IM-ASF SIP 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 and described in "Configuring Monitoring with Java MBeans":
MonitoringGeneralMBean
ThresholdCrossedNotificationRulesMBean
ThresholdCrossedNotificationRuleMBean
StateChangedNotificationRulesMBean
StateChangedNotificationRuleMBean
ImasfMBean is a root MBean for the IM-ASF SIP configuration.
Created automatically
None
ObjectName getApplicationServer()
Gets a reference to the instance of ApplicationServerMBean
ObjectName getSip()
Gets a reference to the instance of SipMBean
ObjectName getSessionKeepAlive()
Gets a reference to the instance of SessionKeepAliveMBean
ObjectName getMonitoringGeneral()
Gets a reference to the instance of MonitoringGeneralMBean
ObjectName getThresholdCrossedNotificationRules()
Gets a reference to the instance of ThresholdCrossedNotificationRulesMBean
ObjectName getStateChangedNotificationRules()
Gets a reference to the instance of StateChangedNotificationRulesMBean
ObjectName getAdvanced()
Gets a reference to the instance of AdvancedMBean
ApplicationServerMBean enables you to define the SIP Application Server that IM-ASF SIP interact with.
Created automatically
AsAddressAlias
For more information on these attributes, see Table 22-2.
None
SipMBean enables you to configure standard SIP protocol parameters.
Created automatically
MaxCallDurationTimeoutIntervalInMinutes
RetransmissionIntervalLimit
t7TimeoutIntervalInSeconds
t9TimeoutIntervalInSeconds
For more information on these attributes, see Table 22-4.
None
SessionKeepAliveMBean enables you to define the keep-alive mechanism that IM-ASF SIP use to test session existence with SIP Application Servers.
Created automatically
InfoKeepAliveInterval
InfoKeepAliveTimeToDie
For more information on these attributes, see Table 22-3.
None
It is recommended to 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".