What is CCE Named Licensing?
Named Licensing is a feature of AES that allows Contact Center Express 4.0 to monitor devices via the AES TSAPI interface without incurring TSAPI license usage, meaning that TSAPI Basic and TSAPI Advanced Licenses are not required in AES WebLM, and that TSAPI basic licenses are not consumed when a device is monitored by CCE
Named licensing is NOT required for CCE to operate, however using “XML Server” and “Interaction Data Server – Voice and Presence” and "Call Routing Server" without named licensing enabled will incur TSAPI license usage.
Refer to the AES documentation for more details about TSAPI licensing.
XML Server, Interaction Data Server - Voice and Presence and Call Routing Server
The CCE “XML Server”, “Interaction Data Server – Voice and Presence” and "Call Routing Server" can each perform a Named Licensing Challenge to AES to confirm the presence of the CCE Named License - If this challenge fails, then the applications will default back to using TSAPI licensing if that is available. If No TSAPI licenses are installed and Named License Challenge fails, then no devices will be monitored.
CCE Supervisor
The CCE Supervisor 4.0 application DOES NOT use the CCE Named Licensing feature, this means that normal TSAPI Licensing would still be required for operation of this component
Requirements
There are 3 requirements for Named Licensing Operation:
- CCE Named License to exist in WebLM on the AES Server
- An encrypted TLINK
- AES Client 4.2.1 or later on the CCE Server
Configuring and Troubleshooting AES
Firstly the CCE Named License must exist on the AES Server. This can be verified using the WebLM interface to AES and reviewing the installed license for the following license "CCE_001, BasicUnrestricted, AdvancedUnrestricted"
Secondly, the TLINK providing the interface to Contact Center Express must be encrypted. This is configured in AES in the CTI Adminstration section under the TSAPI Links node. The required configuration parameter is either Encrypted or Both (Both will provide an Encrypted and un-encrypted Link)
Once configured, the secure TLINK will be denoted with a CSTA-S in the TLINK Name
Thirdly, AES Client 4.2.1 or later must be used on the CCE Server to take advantage of the Named Licensing feature. This is the minimum required version of AES and any attempt to install “XML Server” and “Interaction Data Server – Voice and Presence” or "Call Routing Server" without first installing this (or a later) version of AES client will fail with the following message
AES Client 4.2.1 can be found on the CCE 4.0 DVD or ISO in the Utilities Folder under "Avaya AES Client" folder
Configuring and Troubleshooting CCE Components
Once AES has been correctly administered for Named Licensing, then the CCE components can be configured to take advantage of it
XML Server: XML Server has a configuration parameter "Perform Named Licensing Challenge", setting this value to True will cause the XML Server to query the AES server for the existence of the Named Licensing.
Once the configuration has been saved and the XML Server has issued the challenge, the result can be confirmed using the CCE Control Panel by reviewing the Summary page of the TLINK for the status of the "Named Licensing State:".
Interaction Data Server – Voice and Presence: The Interaction Data Server – Voice and Presence has a configuration parameter "Perform Named Licensing Challenge", setting this value to True (1) will cause the Interaction Data Server – Voice and Presence to query the AES server for the existence of the Named Licensing.
Once the configuration has been saved and the Interaction Data Server – Voice and Presence service has been started , the result can be confirmed by reviewing the IDSError Log file after start-up and confirming that Named Licensing has Succeeded.
Call Routing Server: The Call Routing Server also has a configuration parameter "Perform Named Licensing Challenge", setting this value to True (1) will cause the Call Routing Server to query the AES server for the existence of the Named Licensing.
Once the configuration has been saved and the Call Routing Server service has been started , the result can be confirmed by reviewing the ACRS Log file after start-up and confirming that Named Licensing has Succeeded.
Considerations
The TS-Test application included with AES Client is currently not configured to be able to take advantage of the CCE Named Licensing feature, this means that an AES system correctly configured with CCE Named Licensing but with NO TSAPI Basic licensing will fail during a TS-TEST.
This issue has been raised with Avaya and is currently awaiting resolution.
In this instance, a CCE XML Test would correctly work to identify that successfully communication has been achieved between the XML Server and CM using the configured TLINK
TS-SPY traces however can still be used when CCE components are using the Named Licensing feature.
More Information
More information about AES licensing and features can be found in the AES administration Guides
Keywords Named Licensing, Named License, TSAPI, CCE 4.0, Installation, XML Server, IDS, Call Routing Server