This chapter describes issues associated with Oracle WebLogic Communication Services (OWLCS). It includes the following topics:
This section describes general issue and workarounds. It includes the following topics:
In the Administration Console, the Monitoring -> General tab displays Undefined for the Active SIP Session Count and Active Application Session Count attributes when monitoring a replicated WebLogic SIP Server deployment. There is currently no workaround for this problem.
The Pack/Unpack tool in Oracle WebLogic Server does not work in this OWLCS release. There is no workaround currently available.
The Cloning tool in Oracle WebLogic Server does not work in this OWLCS release. There is no workaround currently available.
When no metric data is found, for example when no messages have been sent or received after server setup, the Metrics Performance page will display Unavailable. This is not a problem with the software, and the Performance reporting is operating properly. As soon as Send and Receive traffic exists, the Performance page will display results normally.
This section describes configuration issues and their workarounds. It includes the following topics:
An error has been reported when using the
launch_sash command with the
-e option. For example:
MW_HOME/user_projects/domains/base_domain/bin/launch_sash.sh -p 8001 -n weblogic -w welcome1 -a presenceapplication -e "xcap appusage list"
does not properly process the
xcap appusage list argument because the double quote (") is mishandled.
To work around this problem, issue the command at the
sash prompt directly.
In order to perform a clean uninstall, ensure that the same user (privileges) who accomplished the install also accomplishes the uninstall.
When a user is created with an uppercase username, then the following occurs:
Initial registration progresses normally, resulting in successful registration with Oracle Communicator.
Presence subscriptions fails.
After a few minutes, Oracle Communicator displays
Server Refused Registration (403).
User's account is locked and sign-in is blocked for 30 minutes.
To work around this issue, set Trusted Authentication Hosts for the SIP Container by doing the following (from the Administration Console):
Click SipServer in the left pane.
Click the SIP Security tab.
In Trusted Authentication Hosts, add the IP address of your server (that is running OWLCS).
Save and restart OWLCS.
Note:Using this workaround, presence functionality will fail for clients running on the same machine as the OWLCS server. Such cases (both Oracle Communicator and server running on the same machine) are mostly for demonstration and development environments. For these cases, ensure you create users with lowercase usernames.
Reregistration and presence subscription failures can also occur when users are created with
privateId being different than the username part of the
For example, if privateId is test.user1 and publicId is sip:email@example.com, everything works because test.user1 is the username part of the publicId sip:firstname.lastname@example.org.
But if privateId is tuser1 and publicId is sip:email@example.com, the username part of the publicId is not the same as privateId. In this case, the first registration succeeds with Oracle Communicator, but reregistrations and presence subscriptions fail. Apply the same workaround (configure trusted host as described above) to resolve this issue.
Perform uninstallation using the Administration Console to ensure that all components are uninstalled. Ensure that you use the same user privilege as when you installed.
When using the F5 Networks BigIP load balancer for a cluster of SIP engines and the SIP monitor in BigIP is used for failure detection, it must be configured to operate (sending OPTIONS requests) over TCP and not UDP. UDP mode will not work (the pool will indicate that the servers are down).
Due to limitations in the Windows IPv6 stack, the SIP Container cannot bind to IPv6 sockets for listening.
Due to an issue with the OWLCS Core Platform CIE-based installer, the JAWS tool cannot correctly read the installation screens. To work around this issue, you must run the installer in silent mode. For information on Silent Mode installation, see Oracle WebLogic Communication Services Installation Guide.
In a clustered (high-availability) environment with Oracle HTTP Server (OHS) configured, do not use the OHS port to configure the VoiceXML Driver Receive URLs. Using the OHS port to configure the VoiceXML Driver Receive URLs will cause a conflict with the drivers.
Each Voice XML Driver must be configured with its own WLS server's port (as described in the parameters' documentation).
This section details changes to the documentation since the last release. Topics include:
Directions for creating a basic SIP Domain have changed slightly in this release. Please ensure that you follow these steps:
Start the configuration wizard located at
WLS_HOME/wlserver_10.3/common/bin/config.sh. This location has changed since the last release.
Select Create a New WebLogic Domain, and click Next.
Select Basic WebLogic SIP Server Domain, and click Next.
The rest of the process remains the same as before when creating a WLS Domain.
Follow these steps to create custom AUIDs:
The file contains the following:
Name of the application (pres-rules)
List of schemas associated with the application's XML files
Create a similar file for the new application usage
For all the XSD files listed in the XML file above, create the XSD files and copy them to the XCAP config location mentioned in Step 1 above.
./launch_sash.sh -a presenceapplication
Provide admin credentials. At the sash prompt enter:
xcap appusage create applicationUsage=<new application usage name> configurationFilename=<name of application usage XML file>
For instance, this command was run to create the pres-rules application usage:
xcap appusage create applicationUsage=pres-rules configurationFilename=presrules_au.xml
To provision users for the new application usage, at the sash prompt enter:
xcap user add userName=<string> applicationUsage=<new application usage name> . <string> is of the form firstname.lastname@example.org (replace example.com with domain for the deployment)
config.sh for SIP Server domain configuration, you can choose whether to use WebLogic Platform Components or a Custom Template. The default for Select Domain Source is to use WebLogic Platform Components. In previous releases, this selection worked, but does not in this release. You must select Custom Template in order to create a SIP Server domain.