| Release Number | AIX | HP-UX | Linux | Solaris | Tru64 UNIX | Windows |
|---|---|---|---|---|---|---|
| 8.0.101.15 [06/29/12] – Hot Fix | X | |||||
| 8.0.101.12 [02/28/11] – Hot Fix | X | |||||
| 8.0.101.11 [02/16/11] – Hot Fix | X | |||||
| 8.0.101.09 [10/14/10] – Hot Fix | X | X | ||||
| 8.0.101.06 [09/24/10] – Hot Fix | X | X | ||||
| 8.0.101.05 [08/04/10] – General | X | X | X | X | X | X |
| 8.0.101.02 [05/25/10] – General | X | X | X | X | X | X |
| 8.0.006.01 [01/14/10] – General | X | X | X | X | X | X |
| 8.0.006.00 [11/09/09] – Hot Fix | X | |||||
| 8.0.005.02 [09/22/09] – General | X | X | X | X | X | X |
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.genesyslab.com for more details.
This release note applies to all 8.0 releases of T-Server for Nortel Communication Server 2000/2100.
Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information on third-party software used in this product, see the Read Me. Please contact your technical support representative if you have any questions.
Supported Operating Systems
New in This Release
Corrections and Modifications
This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.101.20. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.
This is a hot fix for this product. This release contains the following new features or functionality:
T-Server now supports the restricted configuration option call-state-old-overflowed, which specifies AttributeCallState as CallStateRedirected in an EventReleased message for an agent that is released by the switch due to no answer (switch release reason: Overflowed.) This option is set in the TServer section of the T-Server Application object.
call-state-old-overflowed
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
If this option is set to true, T-Server specifies AttributeCallState as CallStateOverflowed in an EventReleased message for an agent. If this option is set to false, T-Server specifies AttributeCallState as CallStateRedirected in the EventReleased message for an agent.
Warning! Use this option only when requested by Genesys Technical Support.
(ER# 303168288)
T-Server now supports the restricted configuration option use-notready-request-workmode, which causes T-Server to use AttributeAgentWorkMode from the TAgentNotReady request in the EventAgentNotReady event, even if the work mode is different from the switch. This option is set in the TServer section of the T-Server Application object.
use-notready-request-workmode
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
If this option is set to true, T-Server uses the AttributeAgentWorkMode attribute from the TAgentNotReady request to set the work mode of the agent. If this option is set to false, T-Server uses the switch work mode to set the work mode of the agent.
Warning! Use this option only when requested by Genesys Technical Support.
(ER# 303202058)
T-Server now supports the restricted configuration option ignore-notready-to-notready-switch, which causes T-Server to ignore the DV-AGENT-NOT-READY switch messages, if the agent state is already one of the NotReady states. This option is set in the TServer section of the T-Server Application object.
ignore-notready-to-notready-switch
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
If this option is set to true, T-Server ignores the DV-AGENT-NOT-READY switch messages, if the agent state is already in one of the NotReady states. If this option is set to false, T-Server processes the DV-AGENT-NOT-READY messages sent from the switch even if the agent state is already in one of the NotReady states.
Warning! Use this option only when requested by Genesys Technical Support.
(ER# 303202058)
T-Server now supports the restricted configuration option notready-before-logged-out, which causes T-Server to distribute the EventAgentNotReady event before the EventAgentLoggedOut event, if the agent is not already in the NotReady state. This option is set in the TServer section of the T-Server Application object.
notready-before-logged-out
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
If this option is set to true, T-Server distributes the EventAgentNotReady event before distributing the EventAgentLoggedOut event, if the agent is not already in one of the NotReady states. If this option is set to false, T-Server only distributes the EventAgentLoggedOut event.
Warning! Use this option only when requested by Genesys Technical Support.
(ER# 303202051)
This release includes the following correction and modification:
T-Server now correctly acquires Control Directory Numbers (CDN) Routing Points when the flow control mechanism is activated. Previously, T-Server would neglect the acquisition of these DNs and would avoid distributing the EventLinkConnected message, if the flow control was activated during registration. (ER# 303168118)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.101.09. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction and modification:
The resource-allocation-mode configuration option, when it is set to circular, now works as documented. This configuration option specifies the manner in which T-Server allocates resources (that is, DNs of the External Routing Point type and Access Resources with the Resource Type set to dnis) for multi-site transaction requests. Previously, external routing resources were not allocated in a circular manner. (ER# 268161020)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.101.06. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
T-Server now correctly default routes a call when the target address is empty, regardless of the AttributeRouteType attribute specified in the TRouteCall request. Previously, call routing worked only when the AttributeRouteType attribute had RouteTypeDefault as the value. (ER# 262670652)
T-Server now takes the agent out of the after call work (ACW) state, if the DV_AGENT_NOT_READY message is received while still in wrap-up mode. Previously, T-Server left the agent in the ACW state even if the DV_AGENT_NOT_READY message was received. (ER# 262462504)
T-Server now correctly releases all InvokeIDs regardless of how the Routing Points are configured. Previously, T-Server did not release all of the InvokeIDs when agents attempted to register non-CDN Routing Points that were incorrectly configured as CDN Routing Points. (ER# 260461431)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.101.04. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction and modification:
T-Server now stops Soft Agent wrap-up if a switch message indicating the agent is in a NotReady state is received before the wrap-up is complete. Previously in this scenario, T-Server may have ignored the DV_AGENT_NOT_READY message. (ER# 261374281)
The resource-allocation-mode option, when it is set to circular, now works as documented. This option specifies the manner in which T-Server allocates resources (that is, DNs of the External Routing Point type and Access Resources with the Resource Type set to dnis) for multi-site transaction requests. Previously, external routing resources were not allocated in a circular manner. (ER# 261529782)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.101.01. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
T-Server now automatically sets the throttling according to the number of invokeIds for the specific configuration option service-version. Previously, T-Server reset the throttle limit when a configuration change takes place. (ER# 260015105)
This release of T-Server now supports the use of the configuration option dialing-from-make-call to generate an EventDialing event from a DV-MAKE-CALL request return result.
dialing-from-make-call
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
If set to true, T-Server generates an EventDialing event from the DV-MAKE-CALL request return result instead of waiting for DV-CALL-PROGRESS or DV-CALL-OFFERED messages, which provides backward compatibility with the 7.5 T-Server. This feature is useful if the origDeviceDN in the DV-CALL-PROGRESS CTI message is modified by the switch. In such cases, the ignore-different-orig configuration option must also be set to true and either the new-call-for-unknown-dest configuration option or set-call-type-with-dialing configuration option must be set to false, otherwise T-Server might create a new call for the DV-CALL-PROGRESS message that is ringing.
Note: Use this option only when directed by Genesys Technical Support.
(ER# 257083141)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.101.01. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.
There are no restrictions for this release. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
T-Server now correctly processes switch messages that include the DeviceAddressType attribute. Previously, T-Server interpreted the value of the DeviceAddressType attribute as dialed digits. (ER# 256168497)
T-Server no longer distributes the EventDiverted and EventRouteUsed events after the EventRinging event when routing from a supplementary Routing Point to an ACD Position. Previously, the out-of-sequence events were a result of the switch including an incorrect ACD Group value in the DV-CALL-RELEASED request for a supplementary Routing Point. (ER# 255940995)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.101.01. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.
There are no restrictions for this release. This section describes new features that were introduced in the initial 8.0.1 release of T-Server for Nortel Communication Server 2000/2100.
Flexible call matching has been enhanced to resolve race conditions that previously could interfere with Inter Server Call Control/Call Overflow (ISCC/COF).
This release includes the following corrections and modifications:
The Call Overflow (COF) match-callid method now works for T-Server. Previously, only the match-ani method worked. (ER# 227189621)
T-Server now distributes the EventDiverted event immediately when routing from a supplementary Routing Point. (ER# 243709811)
T-Server no longer abandons a call when it is routed from a supplementary Routing Point to the primary Routing Point or Queue. (ER# 247403941)
The new-call-for-unknown-dest option, when set to true, has been modified to create a new call and ConnID for a call that leaves and later returns to T-Server's environment. (ER# 250986751)
T-Server now retrieves the correct leg of a consultation call from an ACD Position in IP Call Recording scenarios or other similar scenarios. (ER# 122870887)
T-Server no longer creates duplicate calls when an outbound call returns to T-Server. (ER# 249492363)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.001.17. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.
There are no restrictions for this release. This release contains the following new feature or functionality:
T-Server now supports EventDNBackInService and EventDNOutOfService for supplementary Queues and Routing Points. Two new options have been introduced to turn these events on and off.
primary-qrp
Default Value: blank string
Valid Values: Any valid Queue or Routing Point number
Changes Take Effect: Immediately
Section: TServer in the DN object Annex tab
This option specifies the primary Queues and Routing Points to which the supplementary Queues and Routing Points belong.
Note: Use this option only for supplementary Queues and Routing Points DNs. Also see option relate-primary-supp-qrp.
relate-primary-supp-qrp
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
Section: TServer in T-Server Application object
If this option is set to true, the supplementary Queues and Routing Points are taken in and out of service based on their corresponding primary Queues and Routing Points. Each supplementary Queue and Routing Point must specify the primary Queue or Routing Point to which it belongs by using the primary-qrp option in the TServer section of its DN Annex. If this option is set to false, all supplementary Queues and Routing Points are in service regardless of whether their primary Queues and Routing Points are in service.
(ER# 238336508)
This release includes the following corrections and modifications:
T-Server now sets the DNIS attribute using the dialed digits from the DV_CALL_CONSULT_U message for a consultation call. (ER# 241793802)
T-Server now sets the call type to External and distributes the EventNetworkReached in response to the DV-CALL-PROGRESS farEndAnswered message. (ER# 240484297)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.001.17. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.
This is a hot fix for this product. This release does not contain any new features or functionality.
This release includes the following corrections and modifications:
T-Server now supports X.25 on Solaris. (ER# 236070661)
T-Server no longer loses memory when agent state messages are received for agents that are already in the destination state. (ER# 239421481)
Supported Operating Systems
New in This Release
Corrections and Modifications
This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.001.15. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.
There are no restrictions for this release. This section describes new features that were introduced in the initial 8.0 release of T-Server for Nortel Communication Server 2000/2100.
T-Server now supports call management. The agent-no-answer-action option has been introduced to manage calls that are not answered.
agent-no-answer-action
Default Value: none
Valid Values: none, notready, walkaway, logout
Changes Take Effect: Immediately
This option instructs T-Server to set the agent state to agent-no-answer-action when an agent receives a call, and that call is not answered. The agent state is set to this state following the agent-no-answer-timeout period.
T-Server now supports call management. The agent-no-answer-overflow option has been introduced to manage calls that are not answered.
agent-no-answer-overflow
Default Value: none
Valid Values: none, recall, any destination digits
Changes Take Effect: Immediately
Indicates where to send a call when an agent receives a call, and that call is not answered.
T-Server now supports call management. The agent-no-answer-timeout option has been introduced to manage calls that are not answered.
agent-no-answer-timeout
Default Value: 0
Valid Values: 0 to 600
Changes Take Effect: Immediately
Specifies the number of seconds that an agent�s phone will ring before the agent state is changed to the agent-no-answer-action value. This option is disabled when set to a value of 0 (zero).
T-Server now supports Emulated Agent States. The soft-login-support option has been introduced to turn on or off the Emulated Agent States (also known as the Soft Agent) feature.
soft-login-support
Default Value: false
Valid Values: true, false
Changes Take Effect: After T-Server is restarted
If set to true, T-Server processes all agent-related requests (TAgentLogin/TAgentLogout/TAgentSetReady/TAgentNotReady) internally, without interacting with the CTI link.
T-Server now supports Soft Agent wrap-up time. The soft-wrap-up-time option has been introduced to enable the default wrap-up time for the Soft Agent feature.
soft-wrap-up-time
Default Value: 0
Valid Values: See Timeout Value Format on page 231 of the Framework 8.0 T-Server for Nortel Communication Server 2000/2100 Deployment Guide
Changes Take Effect: After agent logs out and then logs in again
Sets the default wrap-up time for the Emulated Agent States (also known as Soft Agent) feature (you can also specify a wrap-up time for each AgentID in the AgentLogin Properties dialog box); however, it does not affect the state of the agents logged in on the PBX. If the wrap-up time is set to a non-zero value, T-Server emulates the AfterCallWork state after each call that was released when the agent was in the Ready state.
T-Server now supports PVC channel. The pvc-channel option has been introduced to specify the Permanent Virtual Circuit (PVC) channel for the X.25 connection.
pvc-channel
Default Value: true
Valid Values: true, false
Changes Take Effect: After T-Server is restarted
Specifies the Permanent Virtual Circuit (PVC) channel for the X.25 connection.
The new option create-addr-on-register has been introduced to enable clients to register and send requests for DNs that do not have an entry in Configuration Manager. This option can also be used to deny clients the ability to register and send requests for DNs that do not have an entry in Configuration Manager, if necessary.
create-addr-on-register
Default Value: true
Valid Values: true, false
Changes Take Effect: Immediately
When set to true, clients can register and send requests for DNs that do not have an entry in Configuration Manager. If set to false, clients registering for DNs not found in Configuration Manager will see the following error message: DN is not configured in CME.
The new option link-alarm-high has been introduced to trigger the Link-alarm-high LMS message when flow control is required.
link-alarm-high
Default Value: 0
Valid Values: unsigned integer
Changes Take Effect: Immediately
flow-control-rate option that will trigger the Link-alarm-high LMS message. This alarm is raised to warn that the link bandwidth is approaching an unsafe level. A value of 0 (zero) turns the alarm off.
Note: The value for this option is measured as a percentage, for example 90. This option is set when flow control is required.
This release includes the following corrections and modifications:
T-Server now distributes an EventOffHook message when OFF_HOOK is received within time limit specified by release-party-matching-delay after releasing a call. (ER# 220384053)
T-Server now populates the LastForwardingDN in AttributeExtensions with the same value as ForwardingDN if there is no lastForwarding information contained in the switch message. (ER# 217643435)
T-Server will now include the walkaway reason code within DV-SET-FEATURE notReady, if a ReasonCode is included in the Extensions attribute of the RequestAgentNotReady request. Previously, T-Server included the walkaway reason code if any extension was included in the request. (ER# 228973958)
T-Server now displays the correct status in the Extensions attribute of an EventRegistered event. Previously, it displayed -1 (unknown) even though the state was known. (ER# 233263071)
T-Server now ignores DV-CALL-RELEASED messages if no calls with a relevant callId are found. (ER# 230798782)
T-Server now uses both callId and networkNodeId to determine the uniqueness of a call. Previously, in rare cases, a call from another switch may have had the same callId as an existing call on the the local switch. In this scenario, the networkNodeId was required to distinguish between the calls. (ER# 219051694)
In hot standby redundancy mode, the backup T-Server will now distribute an EventLinkConnected event only after being informed by the primary T-Server. Previously in some cases, the backup T-Server would distribute this event prematurely, causing errors in response to client requests after becoming the primary T-Server. (ER# 212425561)
This section provides the latest information on known issues and recommendations associated with this product.
If a switchover from primary to backup T-Server occurs, T-Server might create an extra call after receiving the CALL-PROGRESS message if the values for the set-call-type-with-dialing and new-call-for-unknown-dest configuration options are both set to true.
Workaround: To prevent an extra call, set the value for the set-call-type-with-dialing configuration option to false.
(ER# 268185141)
| Found In: 8.0.101.11 | Fixed In: 8.1.000.06 |
The Framework 8.0 T-Server for Nortel Communication Server 2000/2100 Deployment Guide omits the following information:
agent-state-return-result
Default Value: true
Valid Values: true, false
Changes Take Effect: Immediately
If this option is set to true, when the agent is on a call, T-Server changes the agent state based on the return result of the DV_SET_FEATURE message. If the agent is not on a call, then the return result is not used. If this configuration option is set to false, agent requests may timeout if the call lasts longer than the duration specified by the request-timeout configuration option.
Note: Use this option only when requested by Genesys Technical Support.
(ER# 240452039)
| Found In: Document version 80fr_dep-ts_ncs2000_09-2009_v8.001.00 | Fixed In: |
T-Server created duplicate calls when an outbound call returned to T-Server. This may have occured when both the set-call-type-with-dialing and new-call-for-unknown-dest configuration options were set to true. (ER# 249492363)
| Found In: 8.0.006.01 | Fixed In: 8.0.101.02 |
The distribution of EventDiverted may be delayed when a call is diverted from a supplementary queue or routing point. (ER# 243709811)
| Found In: 8.0.006.01 | Fixed In: 8.0.101.02 |
X.25 links will not start on Solaris for release 8.0. As a workaround, T-Server can be configured to connect to the link through an X.25 HA Proxy. (ER# 236070661)
| Found In: 8.0.005.02 | Fixed In: 8.0.006.00 |
The match-callid Call Overflow (COF) method does not work. As a workaround, the match-ani method can be used instead. (ER# 227189621)
| Found In: 8.0.005.02 | Fixed In: 8.0.101.02 |
Setting the option agent-no-answer-overflow to any value other than none may result in EventHardwareError. T-Server only supports a value of none for this option. (ER# 225440797)
| Found In: 8.0.005.02 | Fixed In: |
When running a high-availability pair of pre-7.6 T-Servers in hot-standby mode, upgrading only the backup T-Server to a 7.6 version with a rolling upgrade prevents the backup T-Server from starting and it remains in a Service Unavailable state. A pre-7.6 T-Server and a 7.6 T-Server cannot run as a hot-standby pair. (ER# 200067043)
| Found In: 7.6.006.01 | Fixed In: |
If an agent goes NotReady while on call using a CTI (RequestAgentNotReady) request, and then manually changes the agent state to Ready, T-Server will remain in NotReady state after the call ends. Genesys recommends not changing agent state with both CTI and manually on the telephone set. (ER# 155483699)
| Found In: 7.6.006.01 | Fixed In: |
T-Server may not hold or retrieve the correct leg of a consultation call from an ACD Position due to a problem in the CALL-HELD and CALL-UNHELD switch messages. This may affect IP Call Recording scenarios or other similar scenarios. (ER# 122870887)
| Found In: 7.5.015.03 | Fixed In: 8.0.101.02 |
Due to a switch problem, T-Server may receive an invalidCallState error in response to a DV-CALL-RECORD message on a position when initiating a call transfer or a conference call.
The following is an example of a scenario that can cause this issue:
DV-CALL-RECORD message for Position1. The switch responds with an invalidCallState error.
DV-CALL-RECORD message.
(ER# 122871014)
| Found In: 7.5.015.03 | Fixed In: |
For Windows only: T-Server may be unable to connect to an X.25 link. As a workaround, the following parameter should be added to the command line when starting T-Server:
-conn-provider select
(ER# 107803398)
| Found In: 7.5.014.00 | Fixed In: |
In an AlternateCall scenario where one branch of a consultation call is released, there is no messaging from the switch to indicate the state of the controlling party (held, connected, or ringing). The switch vendor has provided rules for determining the state, specifically, that after the release, the controlling party is in the:
held state if the consultation call was done manually, or
connected state if the consultation call was done via CTI and the controller did not itself cause the release by manually releasing, or
ringing state if the consultation call was done via CTI and the controller itself did cause the release by manually releasing.
To determine the correct state after the release, T-Server follows rules (1) and (2) but not (3). This is a limitation caused by the fact that it is difficult or impossible to determine if it was the controller that manually released the call branch. Therefore, in cases where the controller manually releases one branch of a CTI consulted call, T-Server will incorrectly place the controlling party in the connected state, instead of the ringing state. That is, it will distribute EventRetrieved (if necessary), but not EventRinging.
| Found In: | Fixed In: |
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.
HP-UX 11.00 is no longer supported.
| Discontinued As Of: 8.0.005.02 |
Solaris 7 is no longer supported.
| Discontinued As Of: 8.0.005.02 |
Windows 2000 is no longer supported.
| Discontinued As Of: 8.0.005.02 |
Information in this section is included for international customers. There are no known internationalization issues for this product.
Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Technical Support website. The following documentation also contains information about this software. Please consult the Deployment Guide first.
Framework 8.0 T-Server for Nortel Communication Server 2000/2100 Deployment Guide contains detailed reference information for the Genesys Framework 8.0 T-Server for Nortel Communication Server 2000/2100 including configuration options and specific functionality.
Framework 8.0 Deployment Guide helps you configure, install, start, and stop Framework components.
Voice Platform SDK 8.0 .NET (or Java) API Reference and Genesys 7 Events and Models Reference Manual contains the T-Library API, information on TEvents, and an extensive collection of call models.
Genesys Migration Guide contains a documented migration strategy for each software release. Please refer to the applicable portion of this guide or contact Genesys Technical Support for additional information.
Genesys Licensing Guide contains information about the licensing requirements for this software. Please refer to the applicable portion of this guide or contact Genesys Technical Support for additional information.
Product documentation is provided on the Technical Support website, the Genesys Documentation wiki, and the Documentation Library DVD (produced monthly) or the Developer Documentation CD.
Note: For the DVD/CD, the New Documents on this DVD/CD page indicates the production date for that disc. Due to disc production schedules, documentation on the Technical Support 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.