| Oracle® Communications Service Broker Configuration Guide Release 5.0 Part Number E15182-01 |
|
|
View PDF |
| Oracle® Communications Service Broker Configuration Guide Release 5.0 Part Number E15182-01 |
|
|
View PDF |
The following sections describe how to configure R-IM-ASF SIP using the Service Broker Administration Console and Java MBeans:
This section describes how to configure R-IM-ASF SIP module instances using the Service Broker Administration Console.
To access the R-IM-ASF SIP configuration screen:
In the Domain Navigation pane, select OCSB > Processing Tier > Interworking Modules. The list of currently deployed Interworking Modules is displayed.
In the list of the deployed modules, select the module instance that you want to configure. The module instance configuration screen is displayed in the Configuration pane.
The configuration screen of the R-IM-ASF SIP contains the subtabs described in Table 15-1.
Table 15-1 R-IM-ASF Configuration Subtabs
| Subtab | Description |
|---|---|
|
Session Keep Alive |
Enables you to define the keep-alive mechanism that R-IM-ASF SIP use to test session existence with the SIP network element. For more information, see "Configuring Session Keep Alive Parameters". |
|
SIP |
Enables you to configure standard SIP protocol parameters. For more information, see "Configuring SIP Parameters". |
|
Monitoring |
Enables you to define how Runtime MBeans and notifications should operate. For more information, see "Configuring Monitoring Parameters". |
R-IM-ASF SIP performs regular checks of SIP sessions using a mechanism known as keep-alive mechanism. This mechanism enables the R-IM-ASF SIP to check whether or not a session is still in progress by periodically sending INFO requests to the SIP network element 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 15-2 describes configuration parameters on the Session Keep Alive subtab.
Table 15-2 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 R-IM-ASF 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 15-3 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: 30 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 R-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 R-IM-ASF SIP through JMX. The hierarchy of the MBeans is shown on Figure 15-1.
The following sections provide reference information for the R-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
RimasfSipMBean is a root MBean for the R-IM-ASF configuration.
Created automatically
None
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
SipMBean enables you to configure standard SIP protocol parameters.
Created automatically
MaxCallDurationTimeoutIntervalInMinutes
RetransmissionIntervalLimit
t7TimeoutIntervalInSeconds
t9Timeout Interval in Seconds
For more information on these attributes, see Table 15-3.
None
SessionKeepAliveMBean enables you to configure the keep-alive mechanism that R-IM-ASF SIP uses to test session existence with the SIP network element.
Created automatically
InfoKeepAliveInterval
InfoKeepAliveTimeToDie
For more information on these attributes, see Table 15-2.
None
|
 Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
