New In This Release

AE Services release 6.1 includes the following new and enhanced features:

DMCC Service And SDKs

Unified DMCC Service: the DMCC API has been enhanced to support advanced third party call control, supplementing existing device, media and call control capabilities. The API has also been updated to support additional capability exchange, monitoring and logical device feature services, and new routing services. The enhancements are supported by all of the existing DMCC SDKs, but in particular enable .Net developers to use AE Services for their CTI-based applications. The DMCC Dashboard, included in the DMCC .Net SDK, has been updated to exercise and demonstrate the new capabilities. For details of enhancements to the DMCC Service, see:

• Avaya Aura® AE Services Release 6.1, New Unified DMCC Service Capabilities (66 KB .pdf)

• .Net DMCC clients support the following operating systems:
  - Windows 7 Professional (32-bit and 64-bit in 32-bit compatibility mode)
  - Windows 7 Enterprise (32-bit and 64-bit in 32-bit compatibility mode)
  - Windows 7 Ultimate (32-bit and 64-bit in 32-bit compatibility mode)
  - Windows Server 2008 R2 (64-bit in 32-bit compatibility mode)
  - Windows XP Professional (32-bit)
  - Windows 2003 Server Standard Edition (32-bit)
• IPv6 addressing supported: client and switch side interfaces can be configured for IPv4 only, IPv6 only, or both simultaneously.
• Gatekeeper allocation: DMCC client applications no longer have to specify a gatekeeper for first-party call control devices at the time of the GetDeviceID requests: instead, an in-service gatekeeper is automatically assigned when each device is registered.

System Management Service (SMS) Web Service and SDK

• IPv6 addressing support.
• Enhanced SMS schema enables Forced Agent Logout Time to be administered by an SMS Web application.
• TCP Keepalives added to the outbound ossicm socket.
• getpeername() call removed from ossicm on outbound TCP sockets that use IP addresses.
• Default OSSI protocol changed to "ossiz".

JTAPI Service and SDK

• Private Data version 9 support adds private data to the CSTA Held event, and augments private data for the CSTA Originated, CSTA Service Initiated and ATT Single Step Transfer Confirmation events.
• IPv6 addressing support.
• New API method enables JTAPI applications to determine whether or not a device is on a given switch.
• New Click2Call sample application included in the JTAPI SDK.

TSAPI Service, SDKs and Clients

• Private Data version 9 support.
• IPv6 addressing support.
• Silent (unattended) TSAPI Client installation support.
• TSAPI Spy trace enhancements: TSAPI Client TS SPY can now report a TSAPI application's send and receive message queue status.
• SDB authorization update: the TSAPI service now verifies that the user has SDB permission to control the subject device for the following service requests: cstaQueryMsgWaitingInd(), cstaQueryDoNotDisturb(), cstaQueryForwarding(), cstaQueryAgentState(), cstaQueryLastNumber(), cstaQueryDeviceInfo(), attQueryACDSplit(), attQueryAgentLogin(), attQueryDeviceName().
• TSAPI clients support the following operation systems:
  - Red Hat Enterprise Linux (RHEL) 5 (32-bit and 64-bit in 32-bit compatibility mode)
  - RHEL 4 (32-bit)
  - Windows 7 Professional (32-bit and 64-bit in 32-bit compatibility mode)
  - Windows 7 Enterprise (32-bit and 64-bit in 32-bit compatibility mode)
  - Windows 7 Ultimate (32-bit and 64-bit in 32-bit compatibility mode)
  - Windows Server 2008 R2 (64-bit in 32-bit compatibility mode)
  - Windows XP Professional (32-bit)
  - Windows 2003 Server Standard Edition (32-bit)
  Note that Windows Vista is no longer supported.

Other New Features

• Avaya Aura Contact Center 6.1 support: DMCC, TSAPI and associated API and client enhancements have been made to support conference and transfer by deskphones and soft clients.
• Link Core Survivability: processor ethernet connections can be utilized in Enterprise Survivable Server (ESS) and Local Survivable Processor (LSP) environments.
• Historical Metric Data Collector: enables collection, storage and viewing of AE Services metrics.
• IBM Sametime 8.5.0/8.5.1 integration can operate in the following configurations:
  - Sametime community cluster with multiplexer co-resident on the server
  - Sametime community cluster with multiplexer on separate servers
  - Multiple Sametime community clusters with multiplexers on separate servers
  - Load balancer in front of Sametime community cluster.
• SIP stack changes: A new parameter called "cmapi.nist_max_server_transactions" has been added to the/opt/mvap/user-configuration.properties. The recommended setting for this parameter is 1.25 times the number of SIP users expected to use the AE Services server with a default value of 5,000. The SIP stack uses this parameter to establish a low threshold for dropping messages under heavy traffic conditions.
• Dell® PowerEdge R610 Server support.

• Avaya Aura Application Enablement Services Release 6.1 Server and Client Release Notes - February 2011 (559 KB .pdf)

Compatibility Information

Compatibility with AE Services Release 4.2 and 5.2 Applications

All DMCC, Web Services, JTAPI and TSAPI applications created with the AE Services Release 4.2.x or 5.2.x SDKs and client libraries will work seamlessly on AE Services Release 6.1 without the need to recompile code and without the need to replace any third-party library components.

Note: AE Services 4.2 and 5.2 DMCC applications must specify the appropriate protocol version. If a protocol version is not specified, the server will default to 6.1 and the application may receive unexpected XML messages with added elements and/or receive new XML messages.

Compatibility With Communication Manager Releases

AE Services release 6.1 is compatible with the following Communication Manger releases:

• Communication Manager 4.x (until "End of Manufacturing Support")
• Communication Manager 5.x
• Avaya Aura Communication Manager 6.0.x Evolution Server