Release Note

Contents

Introduction

As of February 1, 2012, Genesys is no longer an affiliate of Alcatel-Lucent; any indication of such affiliation within Genesys products or packaging is no longer applicable. Please see the Genesys website at http://www.genesys.com for more details.

This release note applies to all 8.1 releases of SMS Server.

• Links in the Contents section enable you to access information regarding a specific release. Releases are listed by version number rather than in date order. For this reason, a recent release may be listed after earlier releases, if the version number is lower. Except when otherwise noted in the information for a specific release, each release includes all of the features and corrections that were introduced for the applicable operating system at earlier dates, regardless of the version numbering.
• The Release Number table lists the supported operating systems for each release at a high level. For more detailed information, see the Genesys Supported Operating Environment Reference Guide.
• The Known Issues and Recommendations section is a cumulative list. It includes information on when individual items were found and, if applicable, corrected.
• The Corrections and Modifications section for each release may list additional issues that were corrected without first being documented as Known Issues.
• The Discontinued Support section is cumulative. It lists functionality that is no longer supported and the release number of the version in which support was discontinued.

Use of Third-Party Software

Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information about third-party software used in this product, see the Read Me. Please contact your Genesys Customer Care representative if you have any questions.

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release contains the following correction and modification:

SMS Server now submits inbound MMS interactions with the media type mms. Previously it failed to submit such interactions.

Note: The _mmsSubject key is no longer provided in the User Data when submitting MMS interactions. Business Processes must use the Subject key instead. (ESR-9237)

SMS Server now correctly encodes source phone numbers in the GSM-03.38 character set, so that source numbers that include the _ (underscore) character are no longer corrupted.

For this functionality, the x-smpp-cstring-ascii-only option must be set to true. (ESR-9334)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release contains the following new features or functionality.

• The following mandatory option has been added to the settings section:

  workspace-location
  Valid values: Local or network path; for example, c:\sms-workspace\ or \\remote-box\shared-folder\
  Default: (none)
  Takes effect: Upon restart

  Specifies the location of the workspace for SMS Server. The workspace is a dedicated folder in a file system that is used by primary and backup instances to store and retrieve its data. This helps ensure proper behavior during recovery after failover or switchover.

  Notes:

  • You must create this folder and assign create/delete/write/read access permissions to it for both primary and backup instances of SMS Server.
  • The path must include the final slash (\), as in the examples.
  • If the option is automatically synchronized between primary and backup servers, the value must be a network path.

Corrections and Modifications

This release contains the following correction and modification:

The criterion for closing chat sessions has been corrected. The new criterion does not close the chat session when all agents leave the session. Previously, SMS Server incorrectly closed the session when a transfer occurred. (ESR-8182)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release contains the following new features or functionality.

• The following option has been added to the channel-<any name> section:
  x-smpp-validity-period
  Valid values: String (see below for format)
  Default: (none)
  Takes effect: Upon restart

  Specifies a default expiration time for all outbound messages sent from this channel. The format is defined in the SMPP specification. The time can be relative or absolute, as described in the SMPP specification just referenced. The SMS center deletes the message if it is not delivered before the specified expiration time,

  This default expiration time can be overridden for individual messages by specifying a different expiration time in a Business Process, using the _smsValidityPeriod attribute (next item) in the user data.

• This release adds the ESP request attribute _smsValidityPeriod, which specifies the expiration time for an individual outbound message. The value of this attribute follows the same format as that of the x-smpp-validity-period option.
• The following log message has been added:
  Std 42125 (channel-<name>).(PU).(umsResponseGeneric): failed execution of request to channel... errorCode <error code>, <error description>, requestId= <request id>

  For example:
  Std 42125 (channel-smsmms-opensmpp).(PU).(umsResponseGeneric): failed execution of request to channel... errorCode 904, incorrect value of 'validity period', requestId= 1

Corrections and Modifications

This release contains no corrections or modifications.

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release contains the following new features or functionality.

• SMS Server now submits multipart inbound messages as single interactions. Previously, SMS Server submitted the parts of a multipart message as separate interactions that might be routed to separate agents.
• The maximum value of the session-shutdown-timeout option is changed from 1800 to 604800.

Corrections and Modifications

This release contains no corrections or modifications.

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. This release contains the following new features or functionality.

• Support for the AIX, Solaris, and Linux operating systems was added September 19, 2013.

Corrections and Modifications

This release contains the following correction and modification:

SMS Server can now process any number of outbound SMS messages. Previously, SMS Server would respond with the Event3rdServerFault message after sending 21,475 outbound SMS messages. (ESR-7491)

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in this release of SMS Server.

• Additional encoding support: GSM 03.38 7-bit packing and Latin1.
• Ability to request and process delivery reports.
• Support for Java 7.
• Support for Red Hat Enterprise Linux 6.0 64-bit native.

Corrections and Modifications

This release contains the following corrections and modifications:

SMS Server now supports a primary-backup configuration of Chat Server. (ER# 289413033)

SMS Server now closes active Chat sessions while switching to backup mode. Previously, when a switch happened while there were active SMS sessions, SMS Server did not notify Chat Server about closing the session. As a result, Agents were unaware that the session had ended. (ER# 289117933)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix release of this product. This release contains no new features or functionality.

Corrections and Modifications

This release contains the following correction and modification:

SMS Server splits large outbound messages into several parts and sends them as a sequence of separate SMPP requests. In accordance with the SMPP specification, SMS Server now assigns a unique sequence number to each separately-sent part. Previously SMS Server assigned the same sequence number to all such parts. (ER# 315584711)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix release of this product. This section describes new features that were introduced in this release of SMS Server.

• x-smpp-bind-mode
  Default value:  auto
  

  Valid values:	auto	The behavior is as in previous releases: SMS Server tries to bind with SMSC using a duplex transceiver connection. If that fails, it tries two simplex connections, one transmitter and one receiver.
  	trx	SMS Server tries to bind with SMSC using a duplex transceiver connection only
  	txrx	SMS Server tries to bind with SMSC using two simplex connections, one transmitter and one receiver.

  Changes take effect: After restart

  Specifies the mode that SMS Server uses to bind with the SMSC.

• x-smpp-src-addr-ton
  Default value:  1
  

  Valid values:	0	Unknown
  	1	International
  	2	National
  	3	Network-specific
  	4	Subscriber number
  	5	Alphanumeric
  	6	Abbreviated
  	Note: These values are specified in SMPP Protocol v3.4.

  Changes take effect: After restart
  

  Specifies the type of number (TON) used in the source address.
  

• x-smpp-dest-addr-ton
  Default value: 1
  Valid values: As for x-smpp-src-addr-ton
  Changes take effect: After restart
  

  Specifies the type of number (TON) used in the destination address.
  

• x-smpp-src-addr-npi
  Default value:  1
  

  Valid values:	0	Unknown
  	1	ISDN (E163/E164)
  	3	Data (X.121)
  	4	Telex (F.69)
  	6	Land Mobile (E.212)
  	8	National
  	9	Private
  	10	ERMES
  	14	Internet (IP)
  	18	WAP Client ID (to be defined by WAP Forum)
  	Note: These values are specified in SMPP Protocol v3.4.

  Changes take effect: After restart
  

  Specifies the numbering plan indicator (NPI) used in the source address.
  

• x-smpp-dest-addr-npi
  Default value: 1
  Valid values: As for x-smpp-src-addr-npi
  Changes take effect: After restart
  

  Specifies the numbering plan indicator (NPI) used in the destination address.
  

Note: The parameters that are set by the preceding four options are dynamically overridden by the ESP request for an individual message if it contains different settings.
• The following four attributes have been added to the user data of submitted interactions. They correspond to the parameters that are set by the preceding four configuration options:
  _smsSrcAddrTon
_smsSrcAddrNpi
_smsDestAddrTon
_smsDestAddrNpi

Corrections and Modifications

There are no corrections and modifications for this release of SMS Server.

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix release of this product. This release contains no new features or functionality.

Corrections and Modifications

This release contains the following correction and modification:

SMS Server now sends the required SMPP response when it receives an enquire_link request from a short message service center (SMSC). (ER# 311311582)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix release of this product. This section describes new features that were introduced in this release of SMS Server.

• The SMS Server now has the following new configuration option:

  channel-<any name>\x-smpp-ucs2-enc-schema
  Default Value: UCS-2BE
  Valid Values: UCS-2BE (Big Endian, Byte Order Mark [BOM] is not used); UCS-2LE (Little Endian, BOM is not used); and UCS-2 (BOM is used)
  Changes take effect: After restart

  Specifies the encoding scheme that the SMS Server uses for UCS-2 encoding.

Corrections and Modifications

This release contains the following correction and modification:

SMS Server no longer unconditionally adds a Byte Order Mark (BOM) to the UCS-2 encoded data. Previously, SMS Server always added a BOM to the UCS-2 encoded data in SMPP data units, which might cause distortion in messages. (ER# 298293610)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix release of this product. This release contains no new features or functionality.

Corrections and Modifications

This release contains the following correction and modification:

SMS Server now correctly handles outgoing messages containing certain characters as the last character of a message. (ER# 297839898)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix release of this product. This release contains no new features or functionality.

Corrections and Modifications

This release contains the following corrections and modifications:

SMS Server now sends outbound messages correctly when in session mode. Previously, it switched the source and destination numbers, and the message could not be delivered. (ER# 296260287)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix release of this product. This release contains no new features or functionality.

Corrections and Modifications

This release contains the following corrections and modifications:

SMS Server now supports the use of the IRD Create SMS Out object. This Known Issue below provides further information related to this item. (ER# 293971157)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix release of this product. This release contains no new features or functionality.

Corrections and Modifications

This release contains the following corrections and modifications:

When operating in session mode, SMS Server now:

• Sends a positive DELIVER_SM_RESP for an inbound SMS message when the message has been successfully transferred to Chat Server.
• Sends a negative DELIVER_SM_RESP for an inbound SMS message when it is impossible to create a chat session (for example, there is no Chat Server available).

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in the initial 8.1 release of SMS Server.

• Support for BIND_TRANSMITTER/BIND_RECEIVER messages.
• Additional operating system support:
  • Red Hat Enterprise Linux 5 64-bit compatibility
  • Red Hat Enterprise Linux 5 64-bit native
  • Windows Server 2008 64-bit native
    

Corrections and Modifications

There are no corrections and modifications for this release of SMS Server.

Top of Page

Known Issues and Recommendations

This section provides the latest information on known issues and recommendations associated with this product.

The following replaces and extends the information on Java version support given in the "Deploying SMS Server" section of the "Manual Deployment—UCS Proxy, Interaction Server Proxy, and SMS Server" chapter of the eServices 8.1 Deployment Guide:

• In release 8.1.300.14 and later,
  • Windows: JDK 1.7
  • UNIX: JRE 1.7
• In release 8.1.3 prior to 8.1.300.14,
  • Windows: JDK 1.6 or JDK 1.7
  • UNIX: JRE 1.6 or JRE 1.7
• In releases prior to 8.1.3, JDK 1.6 on Windows and JRE 1.6 on UNIX

This information relates to ER# 293971157, for which a Correction was issued in release 8.1.000.09.

SMS server does not support a primary-backup configuration of Chat Server. (ER# 289413033)

With SMS Server running in session mode, if a switchover happens while there are active SMS sessions, SMS Server unbinds from SMSC but does not notify Chat Server about the change. As a result, agents are unaware that sessions have ended, and may continue to send messages to clients, which will be lost. That situation lasts until the inactive session timeout expires, at which point the session is closed on the SMS Server side, and agents receive notification that the client has left the session. (ER# 289117933)

When the system is seriously overloaded, SMS Server may fail to connect to SMSC while launching. There are two possible workarounds:

• Switch SMS Server to backup execution mode, then return it to primary mode.
• Restart SMS Server.

The primary/backup SMS Server switches from primary to backup mode and becomes unavailable for clients each time dynamic changes are made to its application settings or to settings for applications in its connection in CME. (ER# 284024191)

The SMS Server installation process on AIX does not check the Java update number. In this release, SMS Server is supported with Java 1.6.0_26 or higher (within the 1.6 family). The 64-bit version is required for 64-bit Windows. For Oracle, Java version 1.6.0_26 or higher (within the 1.6 family) is supported. For IBM, Java (OS AIX) version 1.6.0 build pap6460sr9fp2-20110627_03(SR9 FP2) for AIX or higher is supported.

Note: The eServices 8.1 Deployment Guide also lists the required Java versions.

Top of Page

Discontinued Support

This section documents features that are no longer supported in this software. This cumulative list is in release-number order with the most recently discontinued features at the top of the list.

Java 1.6 is no longer supported.

AIX 5.1, AIX 5.2, and Solaris 8 are no longer supported.

Top of Page

Internationalization

Information in this section is included for international customers.

There are no internationalization issues for this product.

Top of Page

Additional Information

Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Customer Care website.The following documentation also contains information about this software. Please consult the Deployment Guide first.

The following are accessible directly from the eServices product page on the Genesys Documentation website:

• eServices 8.1 Deployment Guide describes deployment procedures for all eServices components. It also contains a high-level description of the eServices system, its architecture, and a list of new features in the current release.

• eServices Administrator's Guide presents recommendations for monitoring and adjusting your eServices configuration, plus detailed explanations of procedures to use for selected special purposes.

• eServices Knowledge Manager User's Guide provides information about Genesys Knowledge Management, including category structures, standard responses, and screening rules, as well as the natural language processing functionality optionally available as Genesys Content Analyzer.

• eServices Interaction Properties Reference Manual provides information about the key-value pairs that represent properties of eServices interactions.

• eServices Integrated Capture Points Guide provides information on configuring and using integrated capture points, which are a feature of Interaction Server providing a mechanism for capturing new interactions from external source systems, and for issuing requests to existing interactions.

• eServices Multi-tenancy and Load Balancing Guide provides information on configuring multi-tenant environments and on load balancing among multiple instances of certain eServices servers.

• eServices Social Media Solution Guide describes deployment and use of the Genesys Social Messaging product.

• eServices 8.1 Reference Manual provides a reference listing of all configuration options and of field codes used in standard responses.

• eServices 8.1 Web API Client Developer's Guide describes the structure of the Web API, explains the Simple Samples, and describes procedures for customizing them.

• eServices (Multimedia) 8.0 Selected Conceptual Data Models for the UCS Database describes a portion of the Universal Contact Server (UCS) database.

• 8.1 Universal Contact Server Manager Help is a guide to the Universal Contact Server Manager user interface.

• eServices 8.1 Knowledge Manager Help is a guide to the Knowledge Manager user interface.

The following are accessible on the Genesys Documentation website:

• For a listing of classes, methods, fields, and constants of the Web API portion of the Web API Server component, see:

  • eServices 8.1 .NET Web API Reference for the .NET Web API
  • The API References of the Platform SDK for the Java-based Web API

• Universal Routing 8.1 Interaction Routing Designer Help is a guide to Interaction Routing Designer, including the portion of it that designs interaction workflows and business processes for eServices.

• Universal Routing 8.1 Business Process User's Guide contains step-by-step instructions for using Interaction Routing Designer to design interaction workflows. It also describes the sample business processes supplied with eServices.

• Genesys Events and Models Reference Manual includes a set of basic interaction models, showing the components involved and the event messages sent among them. For authoritative description of the event messages, see the next item.

• Genesys 8.1 Security Deployment Guide describes the deployment and configuration of some of the security features provided in Genesys software.

Product documentation is provided on the Customer Care website, the Genesys Documentation website, and the Documentation Library DVD (produced monthly).

Note: For the DVD, the New Documents on this DVD page indicates the production date for that disc. Due to disc production schedules, documentation on the Genesys Documentation website may be more up-to-date than what is available on disc immediately after a product is released or updated. To determine the version of a document, check the version number that is located on the second page in PDFs or on the About This File topic in Help files.

Top of Page