New Features

Skip to end of metadata
Go to start of metadata

New Features in Oracle Communications Unified Communications Suite
Version 7.0.5.0.0

This document summarizes the features in Oracle Communications Unified Communications Suite 7.0.5.0.0 that are new or have been enhanced since Oracle Communications Suite Unified Communications Suite 7 Update 4 for the following components:

Oracle Communications Unified Communications Suite Products and Components Version 7.0.5.0.0

Product Version
Oracle Communications Messaging Server 7.0.5.29.0 (patch only)
Oracle Communications Instant Messaging Server 9.0.1.4.0
Convergence 3.0.0.0.0
Oracle Communications Calendar Server 7.0.4.14.0
Delegated Administrator for Oracle Communications Unified Communications Suite 7.0.0.8.0 (patch only)
Oracle Communications Connector for Microsoft Outlook 8.0.1.0.0
Indexing and Search Service for Oracle Communications Unified Communications Suite 1.0.5.18.0
Messaging Server HA Agent (MS_SCHA) 7
Instant Messaging HA Agent (IM_SCHA) 7.3
Dssetup for Oracle Communications Unified Communications Suite (comm_dssetup) 6.4.0.25.0

Check Communications Suite Component Patches for current patches that have shipped since the initial Communications Suite 7.0.5.0.0 release.

This document contains the following sections:

New Features in Messaging Server 7.0.5.29.0

Messaging Server 7.0.5.29.0 includes the following new features:

Access to Intermediate Address Information in Forward Mapping

Bit 7 (value 128) of USE_FORWARD_DATABASE, if set, now includes the initial address presented for alias processing in the FORWARD mapping probe. Bit 8 (value 256), if set, now includes the current intermediate address in the FORWARD mapping probe. These addresses appear immediately before the final recipient address.

New Destination-Channel Keyword for Reducing Message Headers to a Specified Number of Bytes

A new destination-channel keyword, headercut, has been added. If specified, headercut cuts the current message header down to no more than a specified number of bytes, using a heuristic algorithm that removes or truncates header fields based on their relative importance. headercut requires a single nonnegative integer argument. A value of 0, the default, disables header cutting.

New USE_REVERSE_DATABASE Bit Settings Allow Originator-Based Restrictions

Bits 13 (value 8192) and 14 (value 16384) in the USE_REVERSE_DATABASE MTA option have been defined so that, if set, they disable source block and recipient limit settings and capture actions based on the envelope from (MAIL FROM) address (bit 13) and authenticated sender address (bit 14).

Logging Has Been Enhanced to Include Individual Conversion Tags in Filter Log Entries

If the LOG_FILTER MTA option is set, a conversion tag added with either the setconversiontag or the addconversiontag Sieve action is now logged in mail.log*.

New Features in Convergence 3.0.0.0.0

Convergence 3.0.0.0.0 includes the following changes and new features:

Oracle Glassfish Server 3 Support

Convergence 3.0.0.0.0 supports GlassFish Server 3 as its web container. You cannot use GlassFish Server 2.1.1 with Convergence 3.0.0.0.0. See Product Version Compatibility Requirements for more information on supported web containers in Unified Communications Suite 7.0.5.0.0.

S/MIME Support for Firefox

Convergence 3.0.0.0.0 provides S/MIME support for Firefox. For more information, see Software and Hardware Requirements for Convergence with S/MIME.

iwcadmin Security Updates

Beginning in Convergence 3.0.0.0.0, you no longer use the -w passwd flag with the iwcadmin command. Instead, iwcadmin prompts you for the password after entering iwcadmin and the command-line options. For automated scripts, you can continue to use the -W passwdfile flag as long as the passwdfile is encrypted. To do so, use the iwcadmin -o admin.adminpwd command. For more information, see Setting Up and Managing Convergence Security.

Theme Updates

Beginning in Convergence 3.0.0.0.0, theme customization has been updated. Specifically, you can add an image to the thumbnailColor property so that there are images in the background instead of just a solid background. A new theme selector has been added to the Convergence UI, and new themes with images have been added to the theme selector.

For more information, see Customizing Themes and Banner in Convergence 3.0.0.0.0.

Add-on Services

Third-party software and services that can integrate with Convergence are called add-on services.
Add-on services are:

  • optional
  • easy to add or remove
  • configured differently from the core mail, calendar, IM, and address book services. They do not require server-side changes for each add-on service.

In Convergence 3.0.0.0.0, the following add-on services are available:

  • advertising
  • Click-to-Call
  • multinetwork IM
  • SMS (one-way and two-way)
  • social media such as Facebook, Twitter, and Flickr
  • voice and video call

For more information on the add-on services framework, see Configuring Add-on Services in Convergence.

Social Media Integration: Facebook, Twitter, and Flickr

Convergence tightly integrates with social media services in the UI.
The following services have been integrated into the new Social Tab of the Convergence client:

  • Facebook through Convergence allows the user to:
    • securely authenticate to Facebook
    • access Facebook timeline and feed
    • update status
    • post messages
    • comment on friends' statuses.
  • Facebook through Convergence does not yet allow for the following:
    • posting images
    • sharing posts
    • automatic loading of Facebook feed
  • Twitter through Convergence allows the user to:
    • securely authenticate to Twitter
    • access home_timeline (Twitter Feed), the collection of the most recent Tweets and retweets posted by the authenticating user and the users he follows.
    • update profile
    • post Tweets
    • stay logged in. This feature is configurable in the Options tab of the Convergence UI. The user's access token is stored in LDAP upon login to Twitter and is not required to login again from within Convergence.
  • Twitter through Convergence does not yet allow for the following:
    • direct message (private message) to a follower
    • there is a rate limit imposed by the Twitter API, which only allows for 15 GET requests to fetch the home_timeline per 15 minute window. If rate limit is exceeded, the user will see a warning message on the home_timeline, and it will not be updated for 15 minutes. However, the user can still send tweets.
  • Flickr through Convergence allows the user to:
    • access public photos
    • view photos as thumbnail, filmstrip, or full screen with slideshow capability

Facebook, Twitter, and Flickr are enabled by default on the Convergence Social Tab. To administer or to change configuration options, see Configuring the Social Add-On Services in Convergence.

Short Message Service (SMS)

Convergence now supports Short Message Service (SMS). Convergence users can send one-way SMS messages, or if configured, they can send and receive two-way SMS messages through the Convergence UI. SMS requires Messaging Server configuration prior to setting up the Convergence configuration. For more information, see Configuring One-Way SMS for Convergence and Configuring Two-Way SMS for Convergence.

Advertising

You can now integrate advertising into the Convergence UI, which includes ads in Skyscraper and Message Ad (box) formats. To set up advertising in Convergence, you need to configure it as an add-on service. The administrator has the flexibility to determine how to host and to provide the ads at configurable designated areas inside Convergence. Convergence allows an administrator to choose the events which trigger new ads and also provides the message content when requesting ads from the ad server. For more information, see Configuring the Advertising Add-On Service in Convergence.

Voice and Video Call

Convergence now integrates with WIT Software to provide VoIP and video capability in the Convergence UI. To set up voice and video call, you need to set them up as add-on services, and you also need to configure trusted circle SSO. For more information, see Configuring Audio and Video Add-On Services in Convergence.

Click-to-Call

If WIT Software is installed, you can enable calls to PSTN and mobile phone numbers that can be initiated from a user's Address Book and from the user's IM buddy list. For more information, see Configuring Audio and Video Add-On Services in Convergence.

Multinetwork Instant Messaging

Multinetwork Instant Messaging is an add-on service, which allows your users to consolidate and interact with their buddies from other instant messaging networks within the Convergence UI. At this time, users can register their Facebook accounts to view and chat with Facebook buddies. For more information, see Configuring Multinetwork Instant Messaging Add-On Services.

iMIP/iTIP Support

iMIP/iTIP support in Convergence allows users to accept or decline calendar invitations through email. To configure iMIP and iTIP processing, you need to set up Messaging Server and Calendar Server to handle these requests. See Configuring iMIP Messages and Using Calendar Server Notifications. There is no additional Convergence configuration needed to enable iMIP and iTIP processing.

Google Maps Integration, Map Hover, and Directions

If address details have been entered for any contacts in a user's Personal Address Book or Corporate Address Book, a user can now view a Google map of the address location within the address books. Hovering over an address displays a thumbnail map view. In addition, directions allow a user to get driving, biking, and walking directions.

Sharing Mail Folders via Email Address

Users can now use email addresses instead of userIDs to view, to grant access privileges, and to subscribe to shared mail folders and calendars. Since userIDs can be any combination of numbers and characters, they are difficult to remember and often bear no relation to the user to whom they are assigned. Email addresses are familiar to users, and in many cases, are formatted to easily align with a user's name. As a result, it is much more likely that a user knows a contact's email address rather than his userID.

In addition to sharing folders amongst users in your Global Address List, a user's Personal Address Book is enabled for sharing mail folders or for sharing calendars.

The following Convergence UI widgets have been modified to accommodate email addresses in shared mail folders and calendars:

  • Access Control widget
    • Email address is displayed instead of the UID in the textbox
    • Email address textbox is no longer editable. Previously, a user could enter a string in the textbox.
    • Similar default behavior for mail and calendar sharing.
    • A hidden UID for each entry is supplied to back-end servers. For example: Mail uid; Calendar Server 6 uid@domain; Calendar Server 7 email address
  • Add from Address Book widget
    • Enhanced error handling if the selected contact has neither an email address or a UID.
Note
Calendar sharing has not changed: when subscribing to a calendar, you search an email address or name to find available shared calendars.

New Features in Calendar Server 7.0.4.14.0

Calendar Server 7.0.4.14.0 includes the following changes and new features:

Ability for Administrators to Add Calendars to Subscription List

Starting with Calendar Server 7.0.4.14.0, Calendar Server administrators can subscribe or unsubscribe calendars for a user by using the davadmin account command with subscribe or unsubscribe actions. This feature can be used to auto-subscribe certain calendars on creation of the user account itself or to unsubscribe no longer existing calendars.

Ability to Customize Date Formats in Notification Emails

Calendar Server 7.0.4.14.0 enables you to use the Java SimpleDateFormat syntax to define how date, time, and time zone information should appear in notification emails. You can specify 12 or 24 hour time representation, choose the order in month, day, or year representation, and format the time zone representation. You specify the format itself in the server configuration which the notification template files then recognize. When you make a format change to the configuration, you must restart Calendar Server for the change to take effect.

The date, time, and time zone pattern strings are as follows:

  • Date: Specify the date format pattern for notification, for example, EEE MMMMM dd, yyyy, where EEE is the short (text) date, MMMM is the short (text) month, dd is the two-digit date, and yyyy is the four-digit year.
  • Time: Specify the time format pattern for notification. Use 'a' for AM/PM marker, for example, hh:mm:ss aaa. Precision of second is mandatory.
  • Time zone: Specify the timezone format pattern for notification. Use 'z' for general timezone, or 'Z' for RFC822 timezone.

For complete usage of the Java data format syntax, see Java doc for java.text.SimpleDateFormat.

Ability to Set Instant Messaging Presence Based on Calendar Availability

Calendar Server 7.0.4.14.0 publishes a JMS message containing event start and end information for all public events that are marked as busy. Calendar Server publishes this JMS message through its existing JMS infrastructure, which is also used to publish reminders and notifications for database changes. For more information, see Using Calendar Server 7 Notifications. Presence clients, such as Oracle Communications Suite Instant Messaging Server, can consume that information to automatically modify the user's status message. For more information, see Instant-Messaging Availability Based on Calendar Entries.

Changes to davadmin Command

The davadmin commands have been enhanced for Calendar Server 7.0.4.14.0 in the following ways:

  • The -v option to davadmin account list displays the details of each account at the same time.
  • The davadmin account command takes subscribe and unsubscribe actions, so that a Calendar Server administrator can subscribe or unsubscribe calendars for a user. The subscribe and unsubscribe actions take either a single collection path on the command line, specified by -c, or a set of collection paths in a file, specified by -C.
  • The davadmin config list -M lists options whose values were changed from their default value only.
  • The davadmin config -d option sets the value to the default when used with the modify action. Additionally it lists the default value when used with the list action.
  • The davadmin account -y operation and davadmin -y calendar operation take the set-ace and remove-ace properties. This enables modification of access control without specifying the entire access control list which can be very long in certain cases.
  • The davadmin db -s operation supplies the path to the trustStore file that contains the SSL certificate for secure communications with the remote document store.
  • You can now set account properties with the enhanced -f option for the account operation. In previous releases, the -f option used to allow only one user name per line. Now it allows a user name followed by properties for that user.
  • The new davadmin account upgrade operation sets the next presence trigger for all existing events in the future. You must run davadmin account upgrade after upgrading from Calendar Server 7 Update 3 or prior releases for existing future events to have their presence triggers set.
  • The davadmin db backup, list, and restore commands now require that you specify the associated document store. You specify the document store by using the -A option, or the docstore option in the CLI file. This prevents issues with corrupted backups due to the remote document store not being found.
  • The davadmin passfile command was enhanced to add a password list option.

Database Changes

Calendar Server 7.0.4.14.0 has changed its database in the following ways:

  • Added support for MySQL's new utf8mb4 character set, to be able to store values with characters outside basic multilingual text.
  • Added a new queue to hold the trigger for start and end of events for which to publish presence information.

Enabling SSL Communication to All Calendar Server Back Ends

Starting with Calendar Server 7.0.4.14.0, you can configure the Secure Sockets Layer (SSL) protocol between the Calendar Server front ends and back ends, including the calendar store and the remote document store. For information on configuring SSL between the Calendar Server front ends and back ends, see Securing Communications to Calendar Server Back Ends.

Implemented Latest CalDAV Attachment Specification

Calendar Server 7.0.4.14.0 supports managed attachments, as described in CalDAV Managed Attachments.

New Configuration Parameters

Calendar Server 7.0.4.14.0 introduces the following new configuration parameters:

  • davcore.presence.advancepresencetriggerinterval - Specifies the number of seconds in advance to trigger for presence update.
  • davcore.presence.enable - Enables and disables the publication of presence information.
  • davcore.serverdefaults.jsonprefix - Specifies the default prefix to append to all JSON output.
  • davcore.serverlimits.maxischedulecontentlength - Specifies the maximum size when POSTING iSchedule requests. This affects iSchedule freebusy and scheduling requests.
  • service.dav.ischedulewhitelist - Displays a list of hosts that are allowed to send iScheduling POST requests.
  • notification.dav.dateformat - Specifies the date format pattern for notification.
  • notification.dav.timeformat - Specifies the time format pattern for notification.
  • notification.dav.timezoneformat - Specifies the time zone format pattern for notification.
  • store.document.usessl - Specifies to use SSL for communications with the remote document store server.
  • store.document.timeout - Specifies the HTTP(S) connection and read timeout value when connecting to remote document store.

Calendar Server 7.0.4.14.0 introduces the following new remote document store configuration parameters (set in the ashttpd.properties file):

  • store.sslkeystorepath - Specifies the path to the keystore for the document store server.
  • store.usessl - Specifies to use use SSL for the remote document store.

New Perl-based Configurator

Calendar Server 7.0.4.14.0 provides a rewritten initial configuration utility (init-config). Prior to Calendar Server 7.0.4.14.0, init-config was built using the InstallSDK framework, which is a Sun-developed SDK that has been obsoleted. The init-config utility in Calendar Server 7.0.4.14.0 is a simpler Perl-based command-line utility that removes the installSDK dependency. The new utility also makes it easier to support silent configuration in following releases.

Platform Support

Calendar Server 7.0.4.14.0 supports Oracle Solaris 11 and Oracle Enterprise Linux 6.x.

Security Enhancements for iSchedule

In addition to supporting the SSL protocol for all front-end and back-end communications, Calendar Server 7.0.4.14.0 also introduces other security enhancements. For iSchedule, you now have the ability to list hosts that are allowed to send iSchedule POST requests. You can also limit this list of hosts to just the SMTP server that would use iSchedule for automatic iMIP handling. Finally, you can also limit the maximum content length of such requests.

Support for Current Apple Clients

Calendar Server 7.0.4.14.0 supports the current Apple clients, including Mountain Lion (MacOS 10.8.4) and iOS 7.

Support for GlassFish Server 3

Calendar Server 7.0.4.14.0 supports GlassFish Server 3 as its web container. Note that starting with Calendar Server 7.0.4.14.0, support for GlassFish Server 2.1.1 is deprecated and may be removed in a future release. Calendar Server 7 deployments are strongly urged to upgrade to GlassFish Server 3.

Support for GlassFish Server 3 Denial of Service Prevention

Because Calendar Server 7.0.4.14.0 supports GlassFish Server 3 as its web container, you can take advantage of GlassFish Server's built-in protection against Denial of Service (DoS) attacks. To prevent some DoS attacks, you can restrict the size of a message as well as the maximum time it takes a message to arrive. For more information, see Configuring GlassFish Server 3 Denial of Service Prevention.

Calendar Server itself provides additional ways to protect against DoS attacks. For example, to limit the maximum size of POSTs made to the server, use the davcore.serverlimits.maxcontentlength configuration option.

Support for GlassFish Server 3 High Availability Solution

Calendar Server 7.0.4.14.0 can be deployed on GlassFish Server 3 in a cluster setup. See Deploying Calendar Server on a GlassFish Server Cluster for more information.

Support for Paging in WebDAV Sync

Calendar Server 7.0.4.14.0 enhances its support for the WebDAV Sync specification by adding support to the limit parameter. This specification provides a way that the server can limit the number of member URLs in a response as requested by a client. See Collection Synchronization for Web Distributed Authoring and Versioning RFC for more information.

Support for Alarm-Agent Property

This property specifies whether a client, server, both client and server, or none, is responsible for processing an alarm when it is triggered. This is in accordance with the Extended VALARM draft.

WCAP Enhancements

There are two new options for the set_accountprops and set_calprops WCAP commands: set-ace and remove-ace.

Starting with Calendar Server 7.0.4.14.0, users are able to get delegators' access rights before trying to schedule a meeting on their behalf. This ensures that the invite has a chance of succeeding. The WCAP get_accountprops command has been enhanced to to gather and return this information.

The alarms parameter in WCAP store command supports the new Alarm-Agent as a token.

All WCAP JSON formatted output is prefixed by "{}&&". This helps combat JSON hijacking. The prefix value can be changed by setting the davcore.serverdefaults.jsonprefix configuration parameter. The default value is "{}&&".

New Features in Indexing and Search Service 1.0.5.18.0

Indexing and Search Service 1.0.5.18.0 includes the following changes and new features:

Better Handling of Deleted or Moved Accounts

As user accounts are moved between message stores, the chance exists that the corresponding ISS account could be orphaned. Indexing and Search Service 1.0.5.18.0 addresses this situation by modifying the autosync loop to identify orphaned accounts, and to enable a configurable autodeletion of these accounts.

Improvements to Reducing Out-of-sync State and More Administrative Access to Out-of-sync State Information

In Indexing and Search Service 1.0.5.18.0, out-of-sync state issues are improved. The autosync process now shortens the amount of time an account is out-of-sync. Additionally, this version of Indexing and Search Service improves access to the out-of-sync information for accounts so that you can initiate manual intervention sooner.

Performance Improvement for dIndex

The dIndex is the global "directory index" that controls the Indexing and Search Service store. It can grow to a size where performance degrades, especially in large scale deployments. Indexing and Search Service 1.0.5.18.0 introduces a new format for the dIndex that distributes data for different accounts across multiple, smaller directories, enabling quicker updates in parallel for independent account transactions.

Platform Support

Indexing and Search Service 1.0.5.18.0 supports Oracle Solaris 11 and Oracle Enterprise Linux 6.x.

Security Enhancements

Indexing and Search Service 1.0.5.18.0 addresses some security compliance issues. For example, Indexing and Search Service now stores passwords in the Java KeyStore instead of in a specific text file that contained obfuscated password values. For more information, see Java KeyStore for Indexing and Search Service.

Support for GlassFish Server 3

Indexing and Search Service 1.0.5.18.0 supports the use of GlassFish Server 3 as its web container.

New Features in Instant Messaging Server 9.0.1.4.0

Instant Messaging 9.0.1.4.0 includes the following changes and new features:

Instant Messaging Server Monitoring

Instant Messaging Server monitoring is a new feature that collects metrics and provides information on the usage and status of your implementation.For more information on the type of metrics collected, see Available Metrics.

An administrator can access the data through the Enterprise Manager Plug-in (see Enterprise Manager Plug-in for Monitoring Usage and Performance Metrics) or a JMX client such as JConsole. The data can be used for purposes such as:

  • Monitoring the health of the server and identifying quality of service issues.
  • Resource utilization and capacity planning.
  • Gathering per-domain usage data for billing purposes.

Enterprise Manager Plug-in for Monitoring Usage and Performance Metrics

A new plug-in for the Instant Messaging Enterprise Manager allows administrators to:

  • Monitor metrics for Instant Messaging Server instance and domain usage and performance.
  • Set thresholds for generating alerts and notifications on monitored metrics.

For information about using the plug-in, see Installing and Configuring the Enterprise Manager Plug-In for the Instant Messaging Server.

Web Presence API for Providing Presence Information to Web Applications

Instant Messaging 9.0.1.4.0 provides a new Web Presence API that makes it possible for a Web application to obtain presence information from the the Instant Messaging Server and display it to users, independent of whether they are instant-messaging contacts.

An example of how this feature can be useful applies to an enterprise application that lists employees and contains information such as employee name, department, title, location, and phone number. If the application provides availability information, a user can look up an employee and decide whether to make a phone call, send an email, or look for someone else to contact.

For more information, see Web Presence API for Providing Presence Information to Web Applications.

Password Tool for Encrypting Passwords Used in Configuration Files

Instant Messaging 9.0.1.4.0 provides a new password tool that makes it possible to encrypt a password for either the Instant Messaging HTTPBIND Web component or the Web Presence API and use the encrypted password in the component's configuration file (see Password Tool for Encrypting Passwords).

Instant-Messaging Availability Based on Calendar Entries

Instant Messaging 9.0.1.4.0 makes it possible to display a user's availability for instant messaging based on the user's calendar schedule. For example, if calendar availability is enabled and your calendar has you scheduled for a meeting from 2:00 PM to 3:00 PM, the Instant Messaging Server can inform other users during this time period that you are busy and not available. For more information on this feature, see Instant-Messaging Availability Based on Calendar Entries.

Facebook Gateway for Chat with Facebook Contacts

Instant Messaging 9.0.1.4.0 provides a new Facebook Gateway that enables chat between Instant Messaging Server users and their Facebook contacts. For more information, see Configuring the Instant Messaging Server 9 Facebook Gateway.

Platform Support for Oracle Solaris 11 and Oracle Enterprise Linux 6.x

Instant Messaging 9.0.1.4.0 adds support for Oracle Solaris 11 and Oracle Enterprise Linux 6.x.

New Features in Delegated Administrator 7.0.0.8.0

There are no new features in Delegated Administrator 7.0.0.8.0. It contains bug fixes, only.

New Features in Connector for Microsoft Outlook 8.0.1.0.0

There are no new features in Connector for Microsoft Outlook 8.0.1.0.0. However, Connector for Microsoft Outlook 8.0.1.0.0 adds support for Windows 8 and for 64-bit Microsoft Outlook.

New Features in DSsetup 6.4.0.25.0

Dssetup 6.4.0.25.0 includes the following new feature:

New Index for davUniqueId

(Bug: 17285547)

For Calendar Server, comm_dssetup now creates a Directory Server pres,eq index on the davUniqueId attribute.

Labels:
commsuite commsuite Delete
reference reference Delete
newfeatures newfeatures Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Oracle community and they might not be employed or in any way formally affiliated with Oracle. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Oracle nor any other party necessarily agrees with them.