This chapter describes the known problems and workarounds in Oracle Communications Convergence 3.0.2.
This section groups together the general known issues for Convergence.
Patch set: 3.0.2.2.0
Bug number: 29853011
Convergence login fails in GlassFish 5.0 setups when initial configuration is used with LDAP over SSL.
To workaround this issue, use the GlassFish Server version 5.0.1.
Release: 3.0.2.0.0
Bug number: 21058516
Convergence cannot be integrated with Oracle Communications Calendar Server 6.3 anymore. However, when you run the init-config script to configure Convergence, you are presented with the option to select Calendar Server 6.3 as the provider of the calendar service in Convergence.
To work around this issue, do not select Calendar Server 6.3 when you configure Convergence using the init-config script.
Release: 3.0.2.0.0
Bug number: 28210471
The Convergence initial configuration script (init-config) cannot be run with JDK8 for Oracle Solaris on SPARC. However, the init-config script can be run with JDK8 for other supported operating systems. See Convergence Installation and Configuration Guide for the information on supported operating systems.
To work around this issue, Oracle Solaris on SPARC should use JDK7 to run the init-config script while configuring Convergence.
Release: 3.0.2.0.0
Bug number: 28175736
In Convergence, when HTTPOnly cookies are set, the Secure/Multipurpose Internet Mail Extension (S/MIME) applet is not working.
To work around this issue, it is recommended to set HTTPOnly settings to false when S/MIME is enabled in the deployment.
Release: 3.0.2.0.0
Bug number: 27590679
Log4j upgrade to version 2.9+ causes ArrayIndexOutOfBoundsException to be shown in GlassFish Server logs during configuration, upgrade of Convergence and restart of GlassFish Server 3.1.2. However, there is no functionality loss noticed because of the exception.
Release: 3.0.2.0.0
Bug number: 28184033
For Solaris 10, when Convergence is configured using LDAPS and OpenLDAP clients, upgrade fails.
To workaround this issue, use Oracle Directory Server Enterprise Edition (ODSEE) based LDAP client for convergence upgrade by setting LDAP_SERVER_HOME to ODSEE location as appropriate.
Release: 3.0.2.0.0
Bug number: 28245213
The filename for 'Default Value' of log location parameter for the HTTPBIND, HTTPBIND_XFER, and HTTPBIND_AVATAR components is incorrectly displayed in iwcadmin help command in console.
Instead the 'Current Value' attribute in the output of iwcadmin help command refers to the correct names of the log files for all the HTTPBIND components.
Release: 3.0.2.0.0
Bug number: NA
This release of Convergence does not include support for smart phones.
Release: 3.0.2.0.0
Bug number: 18234184
Java HotSpot Server VM warning: You have loaded library /opt/sun/comms/iwc/lib/libsetupSDKJNI.so which might have disabled stack guard. The VM will try to fix the stack guard now. It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'. Finished Loading Default Properties...
This section groups together the known issues pertaining to the messaging service in Convergence.
Patch set: 3.0.2.2.0
Bug number: 29960010
When you configure Convergence with Messaging Server 8.1, Mail Attachment search does not work from Mail > Attachments.
To work around this issue, use elastic search. If elastic search is notconfigured, by default, bruteforce is used.
Release: 3.0.2.0.0
Bug number: 28625579
This issue is seen with tablets only. In the two-pane layout, when a user moves email messages across folders, an error is displayed in the Move Message dialog box on clicking OK. However, the message is moved to the selected folder and the error can be ignored.
Release: 3.0.2.0.0
Bug number: 28643608
This issue is seen with tablets only. In the two-pane layout, when a user deletes an email, the email list is not automatically refreshed. However, the email list is getting refreshed when a user clicks on the Get Mail icon.
This section groups together the known issues pertaining to the calendar service in Convergence.
Release: 3.0.2.0.0
Bug number: 20968603
Oracle Communications Calendar Server can be configured to send event alarms to Oracle Communications Instant Messaging Server release 9.x. Convergence does not display instant messages for event alarms.
Release: 3.0.2.0.0
Bug number: 18760552
When a user receives an iMIP/iTIP event notification email from Yahoo, the details are not properly displayed. The UI message format is broken, and RSVP options are not correctly displayed. In addition, the event isn't added to the calendar.
To work around this issue, add the channel option wrapsmtplonglines to control the Message Transfer Agent (MTA) behavior when it sees illegally long lines in incoming SMTP messages as per Editing MTA Channel Options. Also, manually add the event to your calendar.
See the Oracle wiki for more information:
https://wikis.oracle.com/display/CommSuite/Editing+MTA+Channel+Options
Release: 3.0.2.0.0
Bug number: 17388807, 16773937
When a Yahoo user has been invited to an event and that Yahoo user has replied to the invitation, the organizer of the event is likely to have problems viewing the Yahoo user's response in the calendar event.
To work around this issue, refer to the email with the Yahoo user's response to the invitation.
This section groups together the known issues pertaining to the address book service in Convergence.
Release: 3.0.2.0.0
Bug number: 12813939
Convergence login fails if user has large number of piStore entries.
To work around this issue, reset following convergence parameters to accommodate long LDAP command delay:
ugldap.timeout
ab.storeentrieslimit
ab.pstore.lookthrulimit
Wait for ugldap.timeout to expire then refresh the Convergence login screen.
This section groups together the known issues pertaining to the instant messaging service in Convergence.
There are no known issues pertaining to Convergence user options.
This section groups together the known issues pertaining to the Web real-time communication (WebRTC) service in Convergence.
Release: 3.0.2.0.0
Bug number: 28183713
The public switched telephone network (PSTN) calls may not work when used with Convergence 3.0.2 and Oracle WebRTC Session Controller 7.2 or 7.1.
Release: 3.0.2.0.0
Bug number: 20303154, 20211855
When Convergence is integrated with Oracle WebRTC Session Controller, which is installed with Media Engine 7.0, Convergence cannot make outgoing calls to the public switched telephone network (PSTN), or outgoing PSTN calls get disconnected.
Release: 3.0.2.0.0
Bug number: 20302366
In some cases, peer-to-peer video and voice calls do not work when Convergence is open in Firefox version 34 or 36.
To work around this issue, use an earlier or later version of Firefox, or use a different browser.
Release: 3.0.2.0.0
Bug number: 18676752
If user1 is on a call and is sharing his screen with user2, then places the call on hold and accepts a video conference from another user, user2 continues to see the screen from user1.
Release: 3.0.2.0.0
Bug number: 18670858
When Firefox with a valid Convergence session in progress terminates and the browser is restarted, the Convergence session is displayed and mail/calendar/AB/IM works as expected. But, a login popup to the Webrtc Session Controller (WSC) server is also displayed. Even when the user is not in the Convergence window and the popup had been dismissed previously, the popup keeps reappearing.
To work around this issue, the user should logout of Convergence and login again.
Release: 3.0.2.0.0
Bug number: 18497072
If invitations are sent to multiple users at the same time to participate in a video conference, the joining participants cannot see the video conference.
To work around this issue, send out invitations one at a time and wait for each user to accept or decline the invitation before inviting another user.
Release: 3.0.2.0.0
Bug number: 18379769
In Firefox, in a video conference that has lasted more than five minutes, switching the video mode to filmstrip fails to load.
To work around this issue, do not switch to the film strip view after five minutes of video conferencing.
Release: 3.0.2.0.0
Bug number: 17072512
If you have customized the location of the Convergence main.html page, the WIT Server does not work.
To work around this issue, copy the webcom.swf directory from Convergence_Domain/docroot/iwc_static/layout/ to the same directory as your main.html page.
This section groups together the known issues for Convergence Oracle WebLogic Server.
Patch set: 3.0.2.2.0
Bug number: 29719615
When you use Oracle WebLogic Server, Convergence configuration script fails to deploy Convergence on Solaris 10. Oracle Solaris 10 is not a certified platform for Oracle WebLogic Server 12.2.1.3.0.
Patch set: 3.0.2.2.0
Bug number: 29993895
Instant Messaging Service and other services such as SMS and WSC integration are not supported in Convergence 3.0.2.2.0 setup that is deployed on Oracle WebLogic Server.
To workaround this issue, use GlassFish Server deployments.
Patch set: 3.0.2.2.0
Bug number: 31028618
When you configure Convergence on Oracle WebLogic Server, it deploys two applications, Convergence and Convergence_Client. By default, the context root for Convergence is /iwc. You can modify this context root during the initial configuration.
The context root for Convergence_Client is /iwc_static and you cannot modify this option during the initial configuration.
There are no known issues pertaining to the advertising module in Convergence.
This section groups together the known issues for Convergence customizations.
Release: 3.0.2.0.0
Bug number: 12807684
Response of invalid commands with explicit fmt-out=text/json only return XML.
SR number: 1-473996841, 1-584006005, 1-622051802
Bug number: 12247522 (SUNBT6745772)
This issue occurs if you enable customization and perform the steps to add a custom language to Convergence, then log in as a user created in LDAP with a language preference set to the custom language (for example, Arabic). The UI displays text and aligns widgets left-to-right instead of right-to-left.
Release: 3.0.2.0.0
Bug number: 12247514 (SUNBT6745757)
This issue occurs if you enable customization and perform the steps to add a custom language to Convergence, creating a directory structure as shown in this example:
c11n_Home/allDomain/nls/new_language/resources.js
Convergence does not load the directory and the Convergence UI never appears.
To work around this issue, create an empty resources.js file in the c11n_Home/allDomain/nls directory (in addition to the resources.js file in the new_language directory).