This chapter describes how to set up an IM-ASF interworking module.
The process of IM-ASF setup requires the following:
Adding an IM-ASF to your Oracle Communications Service Controller deployment. You can add as many modules of type IM-ASF as you need. See "Adding an IM-ASF to the Service Controller Deployment" for more information.
Configuring the IM-ASF. See "Configuring an IM-ASF" for more information.
To add an IM-ASF:
In the domain navigation pane, expand the OCSB node.
Expand the Processing Tier node.
Expand the Interworking Modules node.
Select IM Management.
On the bottom of the IM Management pane, click New.
In the New window, fill out the fields as follows:
In the Type list, select IMASF.
In the Version list, select the required version.
In the Name field, enter a name for this module as it should appear in the list of modules. In this field, you can only use lower case letters (a-z), upper case letters (A-Z), numbers (0-9), and underscores (_). If you attempt to use a character which is not allowed, Service Controller displays the error message and prompts you to enter a different name.
Click OK.
In the notification window that reminds you to commit the changes, click OK.
To add the new IM-ASF to your deployment, in the Change Center pane, click Commit.
A new module of type IM-ASF is now added to your Service Controller deployment. The new module is displayed in the domain navigation pane under the Interworking Modules node.
To configure an IM-ASF:
In the Change Center, click Lock & Edit.
In the domain navigation pane, under the Interworking Modules node, select the newly added IM-ASF.
The IM-ASF SIP configuration pane contains the subtabs described in Table 18-1.
Table 18-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 18-2 describes the configuration parameter 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 18-3 describes configuration parameters on the Session Keep Alive subtab.
Table 18-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 18-4 describes configuration parameters on the SIP subtab.
Name | Type | Description |
---|---|---|
Retransmission Interval Limit |
INT |
Specifies a maximum retransmission interval for non-INVITE requests and INVITE responses. Default value: 20 seconds |
T7 Timeout Interval 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. You need to set the T7 timer in the IM-SCF CAP configuration using the following MBean: com.convergin.wcs.osgi.im.scf.CAP_Version > MBean_Version > IMSCFCAPCAP_Verion > ModuleInstance[ModuleInstance_Number] > Sip > t7TimeoutIntervalSeconds. The T7 timer in the IM-ASF and IM-SCF configuration must be set to the same value. Default value: 40 seconds |
T9 Timeout Interval 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. You need to set the T9 timer in the IM-SCF CAP configuration using the following MBean: com.convergin.wcs.osgi.im.scf.CAP_Version > MBean_Version > IMSCFCAPCAP_Verion > ModuleInstance[ModuleInstance_Number] > Sip > t9TimeoutIntervalSeconds. The T9 timer in the IM-ASF and IM-SCF configuration must be set to the same value. Default value: 90 seconds |
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 |
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 Service Controller Monitoring" in "Monitoring Service Controller Using Runtime MBeans" in Service Controller System Administrator's Guide.