Product: Predictive Dialing Version: 2.02.01 Package Name: pdlw1724.exe Size: 1732611 (1692Kb) Level: 1724 How to install: download the self extracting file, pdlw1724.exe, to a temporary directory. Run it from any command line and follow the prompts. This will start an InstallShield Wizard to guide you through the installation process. Fixes: IC25710 Abstract: Symptom/Impact - In Predictive Dialer using a VDN to dial outbound calls, the agents would move from the WORK_NOT_READY state to the UNAVAILABLE state for seemingly no reason. A side effect to this problem was that it would appear that the Predicitve Dialer does not dial all calls queued for a particular campaign. In actuality the dialer has performed all calls, however this is not reflected in the campaign queue in the dialer, as a query for the ACD will show calls in queue and agents available. Problem - Design Problem. Workaround - None. Solution - The Predictive Dialer was placing the outbound dialing line in IDLE state prematurely causing the callID of the previous call to be overwritten by the dialer using the IDLE line for it's next call. When events for the first call were received, the callID in the event could not be matched to the associated physical call. Thus, the call was assumed to of come from a source other than the Predictive Dialer and the agent was placed in UNAVAILABLE state, or in the case of a DISCONNECTED event the call was not removed from the campaign (skill queue) giving the illusion that calls remained in the campaign after all calls were processed. 8153 Abstract: Symptom/Impact - The Predictive Dialer code would trap upon servicing a TadsQueryACDRequest(CALL_DETAILS) if the number of calls in the queue was more than 396. This is a limitation in the CPE API design where the TADS_MAXLEN_DATA is defined as 0xFF00. If the amount of data to be returned to the application exceeds this size, the API cannot tell the application the actual size of the data as it can only return a unsigned short return type. The maximum value that can be returned in a USHORT data type is 65535. Problem - Design Problem. Workaround - None. Solution - Return new return code (585 - TADS_BUFFER_CAPACITY_EXCEEDED) to requests that the data exceeds the TADS_MAXLEN_DATA limit. In the case of a TadsQueryACDStatus(with details) if the entire data structure cannot fit into a TADS_MAXLEN_DATA buffer the 585 rc is returned and the data returned to the application is the same as defined for TadsQueryACDStatus(no details). IC25429 Abstract: Symptom/Impact - When an agent requests to go UNAVAILABLE from the WORK_NOT_READY state, the Predictive Dialer was assigning a call to that agent prior to the agent going AVAILABLE state. The Predictive Dialer should have allowed the agent to transistion to the UNAVAILABLE state. Problem - Design Problem. Workaround - None. Solution - Indicate to the Pacing Engine that the agent is going UNAVAILABLE prior to indicating that the previous call has been completed. 7287 Abstract: Symptom/Impact - In the previous versions of CPE Predictive Dialer, the Predictive Dialer daemon would fail to start with an error that no skills were defined in the TADSSKBR_SKILLS section of the INI. This is not a required field for the Predictive Dialer. Problem - Code Error. Workaround - Define a dummy skill in the TADSSKBR_SKILLS section. Solution - Change the code to not look for skills definitions in this section of the INI file for Predictive Dialer. Files in service: csespdlr.txt csespdlr.txt bin\csesskbr.exe bin\skbrtool.exe bin\dialer.exe bin\pdialer.dat