avaya12.pds

Avaya Predictive Dialing System12.0 Service Pack 5Upgrading to PDS 12.0 Service Pack 5

March 2007

© 2007 Avaya Inc. All Rights Reserved.

NoticeWhile reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document may be incorporated in future releases.

Documentation disclaimerAvaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya.

Link disclaimerAvaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this Documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all of the time and we have no control over the availability of the linked pages.

LicenseUSE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER'S ACCEPTANCE OF THE TERMS SET FORTH HEREIN AND THE GENERAL LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE AT http://support.avaya.com/LicenseInfo/ ("GENERAL LICENSE TERMS"). IF YOU DO NOT WISH TO BE BOUND BY THESE TERMS, YOU MUST RETURN THE PRODUCT(S) TO THE POINT OF PURCHASE WITHIN TEN (10) DAYS OF DELIVERY FOR A REFUND OR CREDIT.Avaya grants End User a license within the scope of the license types described below. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the Documentation or other materials available to End User. "Designated Processor" means a single stand-alone computing device. "Server" means a Designated Processor that hosts a software application to be accessed by multiple users. "Software" means the computer programs in object code, originally licensed by Avaya and ultimately utilized by End User, whether as stand-alone Products or pre-installed on Hardware. "Hardware" means the standard hardware Products, originally sold by Avaya and ultimately utilized by End User.

License Type(s)Designated System(s) License (DS). End User may install and use each copy of the Software on only one Designated Processor, unless a different number of Designated Processors is indicated in the Documentation or other materials available to End User. Avaya may require the Designated Processor(s) to be identified by type, serial number, feature key, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically for this purpose.Concurrent User License (CU). End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A "Unit" means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an e-mail or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Product that permits one user to interface with the Software. Units may be linked to a specific, identified Server.Database License (DL). Customer may install and use each copy of the Software on one Server or on multiple Servers provided that each of the Servers on which the Software is installed communicate with no more than a single instance of the same database. Shrinkwrap License (SR). With respect to Software that contains elements provided by third party suppliers, End user may install and use the Software in accordance with the terms and conditions of the "shrinkwrap" or "clickwrap" license accompanying the Software ("Shrinkwrap License"). The text of the Shrinkwrap License will be available from Avaya upon End User's request (see "Copyright" below for more information).

Copyright Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law.

Third-party ComponentsCertain software programs or portions thereof included in the Product may contain software distributed under third party agreements ("Third Party Components"), which may contain terms that expand or limit rights to use certain portions of the Product ("Third Party Terms"). Information identifying Third Party Components and the Third Party Terms that apply to them is available on Avaya's web site at: http://support.avaya.com/ThirdPartyLicense/

Avaya fraud interventionIf you suspect that you are being victimized by toll fraud and you need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at +1-800-643-2353 for the United States and Canada. Suspected

security vulnerabilities with Avaya Products should be reported to Avaya by sending mail to: [email protected]. Send comments or suggestions about this documentation to [email protected].

TrademarksAvaya is a trademark of Avaya Inc.Avaya MultiVantage Application Enablement Services, Avaya Proactive Contact, Avaya PG230 Proactive Contact Gateway, Avaya Communication Manager, and Avaya Computer Telephony are all trademarks of Avaya Inc. All non-Avaya trademarks are the property of their respective owners.

For the most current versions of documentation, go to the Avaya support Web site:http://support.avaya.com.

Avaya supportAvaya provides a telephone number for you to use to report problems or to ask questions about your contact center. The support telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Web site: http://support.avaya.com.

http://support.avaya.com/ThirdPartyLicense/

mailto:[email protected]

mailto:[email protected]

http://support.avaya.com


Upgrading to PDS 12.0 Service Pack 5 March 2007 3

What’s new in PDS 12.0 Service Pack 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Ordering information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Server software and database enhancements. . . . . . . . . . . . . . . . . . . . . 6Campaign Director 4.0 enhancements . . . . . . . . . . . . . . . . . . . . . . . . . 6

Microsoft Windows Firewall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Online help navigation with Microsoft Windows XP SP2 . . . . . . . . . . . . . 7

Patches and fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Campaign Director patches and fixes . . . . . . . . . . . . . . . . . . . . . . . . . 8Server and database patches and fixes . . . . . . . . . . . . . . . . . . . . . . . . 9PDS Agent patches and fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12HP-UX operation system patches and fixes . . . . . . . . . . . . . . . . . . . . . . 12

Discontinued features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Update HP-UX 11i software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Server operating system version . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Server hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Shutting down the application and log off users . . . . . . . . . . . . . . . . . . . 15Backing up the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Enabling large files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Cleaning up previous patch files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Determining CD/DVD device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Installing the HP-UX 11i update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Post installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Update HP-UX 11.0 software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Server operating system version . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Server hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Shutting down the application and log off users . . . . . . . . . . . . . . . . . . . 23Backing up the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Enabling large files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Cleaning up previous patch files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Determining CD/DVD device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Installing the HP-UX 11.00 upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Post installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Verifying installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Installing and verifying language support updates . . . . . . . . . . . . . . . . . . 31

Contents

Contents

4 Upgrading to PDS 12.0 Service Pack 5 March 2007

Update PDS 12.0 software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Stopping PDS and the mid-tier software . . . . . . . . . . . . . . . . . . . . . . . . 33Removing existing software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Installing PDS 12.0 Service Pack 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Post installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Modifying write tape parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Modifying pds_system and pds_extract users . . . . . . . . . . . . . . . . . . . . 38Modifying master.cfg parameter defaults . . . . . . . . . . . . . . . . . . . . . . . 38

Update PDS database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Installing PDS Database Service Pack 5 . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Update Campaign Director 4.0 software . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Installing Campaign Director 4.0 Service Pack 5 . . . . . . . . . . . . . . . . . . . . . 45Post installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Installing Campaign Director patches if available . . . . . . . . . . . . . . . . . . . 46Setting double-byte language settings. . . . . . . . . . . . . . . . . . . . . . . . . 46

Update PDS Agent 1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Installing PDS Agent 1.0 Service Pack 5 . . . . . . . . . . . . . . . . . . . . . . . . . . 47


What’s new in PDS 12.0 Service Pack 5

Avaya Predictive Dialing System 12.0 Service Pack 5 is the new Avaya PDS release. This Service Pack has been created to update system changes performed since the release of Avaya PDS release 12.0 Service Pack 4. This is a service pack is intended to be installed on top of an existing Avaya PDS release 12.0 version with or without any of the previous service packs (1 through 4).

This guide contains the following topics:

● Ordering information

● Enhancements

● Patches and fixes

● Discontinued features

Ordering informationOrdering information:

Contact your Avaya support representative to coordinate installation of this service pack. Use the following material codes to order PDS 12.0 SP5:

● 700427370 - APC SRK VERSION 12.0 SP5

● 700427388 - APC SRK DATABASE 1.0 SP5

● 700427396 - APC HPUX 11.0 UPDATE FOR B2000/B2600

● 700427404 - APC SRK CAMPAIGN DIRECTOR 4.0 SP5

● 700427412 - APC AGENT DESKTOP 1.0 SP5 SRK

● 700220270 - APC SRK AGT API ENG 3.0 LIC:CU (optional)

EnhancementsService Pack 5 includes updates to the server, database, Campaign Director 4.0, PDS Agent, Agent API and HP-UX operating system software. It includes all fixes and enhancements that were previously included in Service Packs 1, 2, 3, and 4. It can be installed on an Avaya PDS 12.0 system with or without any of those previous service packs.



The key enhancement in this service pack is simplification. All previously release patches and service packs have been combined into a single service pack for each of installation. See software component readme files for further information. Also, see Avaya Product Support Notice PSN001020U for more information.

Server software and database enhancementsThe following enhancements are included in this service pack:

● Trunk-to-trunk transfer calls can be tagged with the data from calling list (patch PDS12_645)

● OFCOM regulatory compliance feature (patch PDS12_742)

● On IVR and PDS with Predictive Agent Blending systems, PDS has been modified so that Inbound and PAB can co-exist.

Campaign Director 4.0 enhancementsCampaign Director 4.0 Service Pack 5 is the client application suite for use with Avaya Predictive Dialing System 12.0 Service Pack 5. This release supersedes Campaign Director 3.0 Service Pack 4. This Service Pack release includes the following enhancements:

● Product improvements and full support localization for Spanish, Korean, Japanese, and Chinese.

● Avaya Campaign Director software has been tested and approved with the following software:

- McAfee AntiVirus- Symantec AntiVirus- Microsoft Office Suite

Note:Note: Any additional third party software loaded on the Campaign Director PC may not

be compatible, and will not be supported.

● PC Analysis users can now export (FTP) all files in the export directory, not just prn files.

● You can now open Telnet from menu when a view is open.

● You can now select 0 attempts for retries in a call strategy.

http://support.avaya.com/elmodocs2/PSN/PSN1020u.pdf

Enhancements


! Important:Important: If you are upgrading from Campaign Director 4.0, follow the instructions in the

readme file to uninstall the applications prior to installing Service Pack 5. If you are upgrading from an earlier version of Campaign Director, your custom and personalized Monitor views will be upgraded automatically. If you have customized Analyst reports, those reports will not be upgraded.

Microsoft Windows Firewall

Avaya does not recommend that you turn on Windows Firewall on PCs running Proactive Contact Campaign Director. If you do, Windows Firewall will display a warning message each time you start any of the applications. Although this warning states that the firewall is blocking some application functionality, the applications will continue to run without causing any problem.

We recommend that you either turn the firewall off or enable it to allow application exceptions.

To disable the firewall:

● With administrator privileges on the PC, open each application. When the warning message appears, click Unblock.

This will add the application to the list of exceptions to firewall policy and allow all other users to access the application.

To add PDS applications to the firewall exceptions list:

1. Open Control Panel > Security Center > Windows Firewall. 2. On the Exceptions tab, click Add Program.

3. Select Analyst, Monitor, Editor, Health Manager, and System Telnet & PC Analysis.

4. Click OK once, then click OK again.

Online help navigation with Microsoft Windows XP SP2

By default, Windows XP SP2 prohibits active content from being run on your PC. This has the effect that all online help pages will display a message at the top of the page stating that Internet Explorer has restricted this file from showing active control that could be used to access your computer. This restricts your ability to navigate easily through the online help system.



Patches and fixes

Campaign Director patches and fixesThe following Campaign Director patches, and fixes are included in this service pack:

● PDS4_591 - Fixes a timing problem that prevented a supervisor from monitoring the first call that an agent made. Now, after the supervisor enters his/her headset ID, a message appears asking the supervisor to wait until the "Welcome to Avaya" message is complete, then click OK. At that point, the dialer will proceed with making the connection to the agent. English only.

● PDS4_596 - Resolved an issue where the Japanese version of the Blend Administration application displayed some double-byte characters incorrectly.

● PDS4_672 - This patch resolves the primary issue that Crystal Reports run-time engine will not pass the report SQL WHERE clause to the database server if a formula in the report selection criteria uses either a function or references a Crystal Dictionary formula name. If the report formula is directly referencing a Crystal Dictionary alias or table.column, or the report formula is being evaluated against a formula that results in the comparable data type to the report formula then the WHERE clause will be sent. The Analyst Dictionaries have been updated to include direct references to table.column names. The Analyst code now makes use of these table.column names when formulating the WHERE clause at run-time. In addition, the Analyst Wizard and Agent Activity report have been updated to allow grouping on all relevant fields for the Agent Activity report.

● PDS4_697 - Provide localized versions of the English-only patch PDS4_692.

● PDS4_705 - This patch is a customization of the Agent Completion Code Distribution report: The code count column has been widened to 7 characters.

● PDS4_706 - This patch resolves an issue where Analyst was not able to display a list of report titles.

● PDS4_707 - This patch contains the A4 paper reports distributed with international versions of Analyst 4.0. These reports can be installed on English versions of Analyst 4.0 where A4 paper is desired.

● PDS4_710 - This patch replaces PDS4_645 and adds the TRANSID parameter to the blend.edt and outbound.edt files. This parameter provides a way to tag trunk-to-trunk transfer calls with a field data from calling lists. The parameter syntax is:

TRANSID:Tagged TT Transfer data::YES:TEXTBOX:NO:OUTBOUND:24:20.

● PDS4_718 - When changing a runtime strategy in Campaign Monitor, the user was unable to set either the number of retries or the retry interval to 0. Similarly, the user was unable to define a strategy with these settings in Editor. In all cases, the minimum value has been changed to zero.

Patches and fixes


● PDS4_731 - This patch fixes a problem where data in the Agent Completion Code Distribution report is incorrect if agents have logged into a job multiple times during one job session and hierarchies are used.

● PDS4_736 - This patch fixes a problem where the Agent Completion Code Distribution report could not be printed after PDS4_731 was installed. This patch completely replaces PDS4_731.

● PDS4_601 - Resolves an issue where the Job Detail view in Campaign Monitor did not upgrade properly. When the Job Detail view was opened, then closed and reopened, the data fields grouped under the headings "Performance" and "Performance Detail" were no longer visible.

● PDS4_675 - In Campaign Monitor's Job Call Handling view, the ACD pie chart is the only pie chart displayed if there are ACD agents with no accumulated talk, idle, or update time.

Server and database patches and fixesThe following server and database patches, fixes, and enhancements are included in this service pack:

● On IVR and PDS with Predictive Agent Blending systems, the PDS has been modified so that Inbound and PAB can co-exist.

● PDS11_563 Agent API data truncation after event services

● PDS11_564 Trunt-to-Trunk Transfer call hangs after agent releases the line

● PDS12_566 Job monitor shows negative numbers in the outbound wait queue

● PDS12_569 Recall date adds one more day if phone is empty

● PDS12_571 Enserver spinup after Witness connection

● PDS12_573 PAB and simultaneous acquires POD

● PDS12_575 Telnet agents on inbound PAB do not link to next job

● PDS11_578 API E28921 generated with AGTListJobs

● PDS12_582 No stats based on units on Unit Work List jobs

● PDS12_583 PDS12 SP4: Super patch

● PDS12_589 Change jobmon so it doesn't display release code 0

● PDS12_592 Times off by one hour for systems located in Australia's Eastern time zone

● PDS12_593 Use the DISCONNECT instead of the RELEASE message for ISDN calls for AUTOWRAP

● PDS12_594 ISDN code 9F getting coded as a 04 instead of a 36

● PDS12_595 Stats Pump workaround for invalid RAC code data from enserver



● PDS12_597 StatsPump times off by one hour on systems located in Australia's Eastern timezone

● PDS12_598 Two AGTJobEnd msgs received when job shuts down

● PDS12_605 Custom Job Report View issue shows totals versus hourly incremental

● PDS12_607 Datapump autoreconnect on network failure CORBA exception

● PDS12_608 Double-clicking the Break button makes agent out-of-sync

● PDS12_610 Selecting >32 timezones in causes the DCCSERVER process to fail

● PDS12_611 Internet Monitor numbers no longer add up

● PDS12_613 Agents waiting for scheduled recalls at the end of Unit Work List jobs

● PDS12_615 Hot strategy ignored and calls aren't routed to agents quickly

● PDS12_618 Slow operations on a loaded database; datapump remains behind; high CPU usage

● PDS12_622 Change swif_mako to allow MFCR2 codes in India

● PDS12_623 ij_merge binary marks records duplicates when they are not

● PDS12_626 Fix problem with blend not starting on 11i HP-UX

● PDS12_628 Blend agent is taken off of break

● PDS12_629 Japan Display ACD stats

● PDS12_631 Datapump not populating update, talk time and mo_last_status

● PDS11_632 Semaphore error was seens in account file

● PDS12_634 chkentdt failing on large lists, gives core dump

● PDS12_639 Canada error handling with hosttopds

● PDS12_640 Super patch

● PDS12_641 SysAgents rollup mancount issue and rollup of MTS patches

● PDS12_642 Acquire calls fail to nail up agents and merge previous Blend patches

● PDS12_644 Inbound jobs have no time data in Analyst

● PDS12_645 Enhancement request to have TT transfer calls tagged with the data from calling list

● PDS12_647 soe_routed crashed if the hostanme from remote tcp connection is long

● PDS12_648 Super patch

● PDS12_649 SysAgents rollup mancount issue and rollup of MTS patches

● PDS12_650 Acquire calls fail to nail up agents and merge previous Blend patches

● PDS12_651 Internet Monitor displays garbage characters before Japanese text

● PDS11_653 Unit worklist selection will not select single digit numbers

Patches and fixes


● PDS12_656 API agent removed from menus unable to log back in

● PDS12_658 swif_mako failure

● PDS12_659 LASTTIME1,LASTDATE1,LASTSTAT1 fields erased when PHONECNT1 reaches

● PDS12_660 Add sysadm menu option for stop_mts & start_mts.

● PDS11_661 acctent processes associated with the agents and admin login taking up all CPU resources

● PDS12_662 prompts in /opt/avaya/pds/tools/ukswitch/prompts are saved as mu-Law and are poor sound quality

● PDS12_663 Incorrect agent stats (compcode cnt) for event service client

● PDS12_665 Fix to prevent ISDN phone lines from making calls on test job

● PDS12_667 library.jar had performance impact after must-have PDS12_649 installed

● PDS12_670 one extra record appended on infinity jobs

● PDS12_671 Problems with CONNECT ACKNOWLEDGEMENT message on ISDN lines

● PDS12_674 Customer calls records on PHONE1 then later on PHONE2, PHONESTAT for PHONE1 reve

● PDS11_677 acctent processes associated with the agents & admin login running wild and taking up all CPU resources

● PDS12_679 Allow shutdown of inbound job on STOPTIME

● PDS12_680 createop allows user to delete system accounts

● PDS12_682 compcodes from event service is not accurate

● PDS12_686 Application Delete removes postupdate.xfr

● PDS12_687 Manual Call called number display

● PDS12_688 Monthly detail data cleanup falis due to rollback segment too small

● PDS12_691 event_player: Unknown event error

● PDS12_693 Mismatch between system and midtier on number of cancelled managed calls

● PDS12_694 Unable to use Kanji characters in *.dat files

● PDS12_695 Linking between virtual jobs in Monitor gives error: "Linking between

● PDS12_698 PAB and IVR integration not working

● PDS12_709 Wrong JOBCLOCK time in msv_agent, when manually hanging up

● PDS12_710 Enhancement request to have TT transfer calls tagged with the data

● PDS12_712 Admin Manager not creating correct set of keys sequences for agent keys

● PDS12_713 List-sharing job in a pod was very slow and not responding to agent's login request



● PDS12_714 Increase the size of a pcanal extract criteria field

● PDS12_715 Add ability of record_ed to skip locked records.

● PDS12_721 Operator intercepts coded as 04 due to errors in handling ISDN events.

● PDS12_724 Need zip tone played in agents ear when customer hangs up

● PDS12_726 List-sharing jobs performance issues

● PDS12_737 Replace PDS12_626 with a new version

● PDS12_741 NVDT calls hang on receiving job transfer queue

● PDS12_742 OFCOM compliance feature enhancement

● PDS12_745 createop changes ownership of /home/pds_agent and .profile to agent

● PDS12_750 Add version of ZIPA.LPV file that plays 'A' tone 8 times

● PC3_752 lists_dl.xfr file causing downloads to stop looking has list1, list2, list3.

● PDS12_754 List5 is getting corrupted with list1 information from live NVDT jobs

● PDS12_756 Campaign Monitor stops refreshing

● PDS12_758 Change the way manually entered numbers for a recall are verified.

● PDS12_768 This patch fixes a problem introduced with PDS12_758 where the phone format was no longer referenced when placing manual calls. This patch restores the checking of the phone format information before placing a manual call and also keeps the functionality of PDS12_758.

PDS Agent patches and fixesThis release includes the following patches and fixes the following issues:

● PDS1_617: Telephone bar loses focus after hang up.

● PDS1_681: No recall allowed during preview time.

HP-UX operation system patches and fixesThis release contains of the following module updates:

● Quality Pack Bundle installation

● Additional patch installation

● Perl installation

● SYSTEM fileset installation

● Secure Shell installation (optional)

Discontinued features


● Verifications

Discontinued featuresLanguage support for French, German, Italian and Portuguese has been discontinued.


Update HP-UX 11i software

This section describes how to update an existing HP-UX 11i installation on an HP B2000, B2600, or C8000.

This section includes the following topics:

● Prerequisites

● Installing the HP-UX 11i update

● Post installation

Prerequisites

Server operating system versionThis procedure assumes that HP-UX 11.00, as delivered by the 12548-01 CD archive, is already installed and functioning. The software referenced in THIS document is for update purposes only and is labeled as HP-UX 11.00 Update for B2000/B2600.

Server hardwareThe assumption is that the system is an HP B2000 or B2600 workstation configured with at least a 36GB hard disk drive and a CD-ROM drive.

Shutting down the application and log off usersExecute

stop_pds

stop_mts

stop_db



Backing up the systemAvaya recommends that you create bootable backups, e.g. /opt/moimager before installing updates.

Enabling large filesEnable large files using SAM. The system does not come with Large File enabled.

1. Login as admin.

2. Execute

stop pds

stop mts

stop db

3. Logout as admin.

4. Login as root.

5. Open Sam.

6. Go into Disk and File systems.

7. Highlight the concerned file system.

8. Press Tab to move cursor to the menu bar. Go into Actions menu > Modify.

9. Tab to Allow large files. Use space bar key to show a x.

10. Tab to OK. Confirm reboot.

Cleaning up previous patch filesDepending on the extent of previous patching activity, ensure that excessive disk space is not taken up by older patches. To remove all superseded patches and thereby free up disk space, execute cleanup -c 1.

After an analysis phase and a listing of the superseded patches, you'll be asked if you'd like to commit the patches. Answer y and the superseded patches will be removed.

Installing the HP-UX 11i update


Determining CD/DVD deviceIf you do not know which block device file is associated with your CD/DVD drive, execute ioscan -fnd sdisk. Insert the proper name wherever you see <your drive> in the following procedures.


To install GOLDAPPS11i, GOLDBASE11i, and HWEnable11i:1. Insert the update media HP-UX 11i Update for B2000/B2600/C8000 CD and mount it by

executing mount /dev/dsk/<your drive>/CDROM.

2. Execute swinstall and select Local CD-ROM as the Source Depot Type.

3. After seeing that /CDROM is displayed on the Source Depot Path line, tab to OK and press Enter.

4. Highlight GOLDAPPS11i, GOLDBASE11i and HWEnable11i, then press Tab.

5. Use the right arrow key to position on Actions and press Enter.

6. Select Mark for Install and press Enter. Answer OK to the warning about dependencies.

7. Press Tab and use the right arrow key to select Actions. Press Enter.

8. Select Install and press Enter.

After the initial analysis phase, the system displays:

- Status is Ready - 90 of 402 products are scheduled (it is possible that fewer products will be

scheduled if your system has undergone selective patching).

9. Tab to OK and press Enter. Answer Yes to the confirm reboot.

10. Tab to Done and press Enter. Press Enter again to reboot.

To install additional patches:1. Insert the update media HP-UX 11i Update for B2000/B2600/C8000 CD and mount it by

executing mount /dev/dsk/<your drive>/CDROM (ff it is not already there).

2. Execute swinstall and select Local CDROM as the Source Depot Type.




4. Highlight the following 8 additional patches:

- PHCO_30778

- PHCO_33822

- PHCO_33967

- PHNE_31091

- PHNE_33412

- PHNE_33628

- PHNE_33704

- PHNE_33791)

5. Press Tab.






- Status is Ready - 8 of 21 products are scheduled

10. Tab to OK and press Enter. Answer Yes to the confirm reboot.

11. Tab to Done and press Enter. Press Enter again to reboot.

To install updated Ignite-UX-11-11, MoImager, and Perl:1. Insert the update media HP-UX 11i Update for B2000/B2600/C8000 CD and mount it by

executing mount /dev/dsk/<your drive>/CDROM (if it is not already there).



4. Highlight the following:

- Ignite-UX-11-11

- MoImager

- perl

5. Press Tab.









10. Tab to OK and press Enter.

11. Tab to Done and press Enter.

To install updated T1471AA Secure Shell (if applicable):

! WARNING:!

WARNING: Do not install or update this product until the PDS applications have been installed or it will cause uid/gid complications.

1. Insert the update media HP-UX 11i Update for B2000/B2600/C8000 CD and mount it by executing mount /dev/dsk/<your drive>/CDROM (if it is not already there).



4. Highlight T1471AA, then press Tab.







9. Tab to OK and press Enter. Answer Yes to both confirmations.


Note:Note: If Secure Shell has just been installed for the first time, see COMPAS 110454

Appendix C, paragraph 9.3.2 regarding verification steps.



Post installationTo verify the software upgrade:

1. Execute swlist -l bundle. Verify that the following bundles and version numbers appear (edited for brevity):

Bundle Version Description

B5725AA C.6.2.241 (HP-UX Installation Utilities)

B9073BA B.06.02 (HP-UX iCOD)

BUNDLE11i B.11.11.0306.1 (Required Patch Bundles)

Base-VXVM B.03.50.5 (Base VERITAS Volume Manager)

DVD+RW-TOOLS 5.18 (dvd write tools)

FEATURE11-11 B.11.11.0209.5 (Feature Enablement Patches)

GOLDAPPS11i B.11.11.0509.429 (Gold Apps Patches, Sept2005)

GOLDBASE11i B.11.11.0509.429 (Gold Base Patches, Sept 2005)

GigEther-00 B.11.11.19 (GigEther)

GigEther-01 B.11.11.15 (GigEther)

HPUXBase64 B.11.11 (HP-UX 64-bit Base OS)

HPUXBaseAux B.11.11.0406 (HP-UX Base OS Auxiliary)

HWEnable11i B.11.11.0509.430 (Hardware Enablement Patches)

Iether-00 B.11.11.05 (PCI Ethernet)

Ignite-UX-11-11 C.6.2.241 (HP-UX Installation Utilities)

J2559C D.06.21 (JetAdmin)

OnlineDiag B.11.11.14.15 (Support Tools Bundle)

OpenSSL A.00.09.07-d.002 (Secure Network Communication)

T1457AA 1.4.2.06.00 (Java2 1.4 RTE)

perl D.5.8.3.B (Perl Programming Language)

scsiU320-00 B.11.11.01 (PCI SCSI U320)

T1471AA A.04.10.004 (HP-UX Secure Shell, if installed)

Post installation


2. As the state of all software should be configured, there should be zero output from the following command:

swlist -l fileset -a state | grep installed


Update HP-UX 11.0 software

This section describes how to update an existing HP-UX 11.00 installation on an HP B2000, B2600, or C8000.

This section includes the following topics:

● Prerequisites

● Installing the HP-UX 11.00 upgrade


Prerequisites

Server operating system versionThis procedure assumes that HP-UX 11.00, as delivered by the 12548-01 CD archive, is already installed and functioning. The software referenced in THIS document is for update purposes only and is labeled as HP-UX 11.00 Update for B2000/B2600.

Server hardwareThe assumption is that the system is an HP B2000 or B2600 workstation configured with at least a 36GB hard disk drive and a CD-ROM drive.

Shutting down the application and log off usersExecute

stop_pds

stop_mts

stop_db



Backing up the systemAvaya recommends that you create bootable backups, e.g. /opt/moimager before installing updates.

Enabling large filesEnable large files using SAM. The system does not come with Large File enabled.

1. Login as admin.

2. Execute

stop pds

stop mts

stop db

3. Logout as admin.

4. Login as root.

5. Open Sam.

6. Go into Disk and File systems.

7. Highlight the concerned file system.

8. Press Tab to move cursor to the menu bar. Go into Actions menu > Modify.

9. Tab to Allow large files. Use space bar key to show a x.

10. Tab to OK. Confirm reboot.

Cleaning up previous patch filesDepending on the extent of previous patching activity, ensure that excessive disk space is not taken up by older patches. To remove all superseded patches and thereby free up disk space, execute cleanup -c 1.

After an analysis phase and a listing of the superseded patches, you'll be asked if you'd like to commit the patches. Answer y and the superseded patches will be removed.

Installing the HP-UX 11.00 upgrade


Determining CD/DVD deviceIf you do not know which block device file is associated with your CD/DVD drive, execute ioscan -fnd sdisk. Insert the proper name wherever you see <your drive> in the following procedures.


! Important:Important: Before continuing, determine if the previous version of this update (12649-04)

was installed to your system. Execute swlist -l bundle and look for the QPK1100 bundle. If the QPK1100 version is not B.11.00.64.4, begin with the PHSS_23485 upgrade to bring your system up to date. However, if the QPK1100 version is B.11.00.64.4, go directly to installing Perl on page 27.

To install the PHSS_23485 (Mitsumi firmware patch):1. Insert the HP-UX 11.00 Update for B2000/B2600 CD and mount it by executing mount /

dev/dsk/c0t0d0 /CDROM.

2. Execute swinstall and select Local CDROM as the Source Depot Type. Verify that /CDROM is displayed on the Source Depot Path line, Tab to OK and press Enter.

3. Highlight PHSS_23485.

4. Press Tab and use the right arrow key to select Actions and press Enter.

5. Select Mark for Install and press Enter.



During the analysis phase, it will be determined whether or not a Mitsumi FX4830 is present and, if so, what its firmware version is. It is likely that this patch will not need to be loaded.

If the analysis fails, cancel the installation and unmark the patch.

8. Tab to OK and press Enter. Answer Yes to the confirmation to reboot.

To install PHKL_27224 (IDE/ATAPI cumulative patch):1. Insert the HP-UX 11.00 Update for B2000/B2600 CD and mount it by executing mount /





3. Highlight QPK1100 (B.11.00.64.4) and press Enter.

4. Highlight PHKL_27224.



7. "Press Tab and use the right arrow key to select Actions and press Enter.


9. After the initial analysis phase, Tab to OK and press Enter. Answer Yes to confirm and reboot.

To install QPK1100:1. Insert the HP-UX 11.00 Update for B2000/B2600 CD and mount it by executing mount /



3. Highlight QPK1100 (B.11.00.64.4).



6. "Press Tab and use the right arrow key to select Actions and press Enter.


8. After the initial analysis phase, the system displays:

- Status is Ready or Ready with Errors- x of 437 products are scheduled. (The exact number of products will vary

depending on which updates have been run previously.)

9. Tab to OK and press Enter. Answer Yes to the confirm and reboot.

Note:Note: The load can take over 60 minutes to complete.

10. Tab to Done and press Enter. Press Enter again to confirm reboot.

Note:Note: Configuring all unconfigured software file sets can take a few minutes after

reboot.

To install additional patches:1. Insert the HP-UX 11.00 Update for B2000/B2600 CD and mount it by executing mount /





3. Highlight the following patches:

- PHKL_30508

- PHKL_30509

- PHNE_29473

- PHNE_29882

- PHSS_30048

- upgrade-bind812

4. Press Tab.

5. Use the right arrow key to select Actions and press Enter.





- Status as Ready- x of 7 products are scheduled. (The exact number of products will vary

depending on which patches have been previously installed.)

9. Tab to OK and press Enter. Press Enter again to reboot.

When the load is finished, tab to Done and press Enter. Press Enter to reboot.

To install Perl:1. Insert the HP-UX 11.00 Update for B2000/B2600 CD and mount it by executing mount /


2. The Perl product was packaged in a different manner than the other software on the update CD. To install it, execute the following on the command line:

swinstall -s /CDROM/perl.depot -x allow_multiple_versions=true

3. Highlight perl (D.5.8.7.A) then press Tab.

4. Use the right arrow key to select Actions and press Enter.





- Status as Ready with Warnings (because you are allowing mulitiple versions)



- 2 of 2 products are scheduled.


When the load is finished (after approximately 5 minutes), tab to Done and press Enter.

To remove a previous version of Perl:● Execute swremove perl,r=5.6.0.

To install the SYSTEM file set:1. Insert the HP-UX 11.00 Update for B2000/B2600 CD and mount it by executing mount /



3. Highlight SYSTEM (11.2.0.k02).






- Status as Ready- 1 of 1 products are scheduled.



To install SP5_OS_UPDATE:1. Insert the HP-UX 11.00 Update for B2000/B2600 CD and mount it by executing mount /



3. Highlight SP5_OS_UPDATE (1.1).






- Status as Ready

Post installation


- x of 33 products are scheduled. (The exact number of products may vary depending on which patches have been previously installed.)


When the load is finished, tab to Done and press Enter.

To install Secure Shell (optional):1. Insert the HP-UX 11.00 Update for B2000/B2600 CD and mount it by executing mount /



3. Highlight T1471AA (A.04.20.004).






- Status as Ready- 1 of 1 products are scheduled.



Post installation

Verifying installationTo verify the software upgrade:

1. Execute swlist -l bundle. Verify that the following bundles and version numbers appear (edited for brevity):


B5509BA B.11.00.05 (100BT/9000 PCI)

HPUXEng64RT B.11.00.01 (English HP-UX 64-bit Runtime Environment)



Note:Note: If any of the additional UxCoreMedia filesets were installed, you will see the

following for UxCoreMedia instead of what's shown above:

2. Execute swlist SYSTEM. Verify that the following bundles and versions appear (edited for brevity):

3. Execute swverify perl. The following message should appear:

Verification succeeded

4. As the state of all software should be configured, there should be zero output from the following command:

swlist -l fileset -a state | grep installed

5. (Optional) If you installed the Secure Shell, you can test the installation by starting a secure session on the command line of the machine you've just updated.

a. Enter ssh, followed by the hostname, for example, ssh cpu1. You'll receive a one-time warning regarding the hostname.

b. Enter yes.

c. You'll then be asked for a password. By doing this (logging in to yourself), you'll be proving that both the SSH client-side and server-side function properly.

d. Enter exit to return to your original login.

QPK1100 B.11.00.64.4 (Quality Pack for HP-UX 11.00, March 2004)

SP5_OS_UPDATE 1.1 (Misc. Security and Performance Patches)

UXCoreMedia B.11.00.01 (HP-UX Media Kit)

XSWGR1100 B.11.00.52.2 (HP-UX General Release Patches, 3/2001)

upgrade-bind812 1.4 (bind 8.1.2 special release upgrade)

T1471AA A.04.20.004 (HP-UX Secure Shell, if installed)

UXCoreMedia B.11.00.02 (HP-UX Media Kit)


SYSTEM 11.2.0.k02 Kernal/Service modifications

SYSTEM.SYSTEM 11.2.0.k02 Kernal/Service modifications


Post installation


Installing and verifying language support updatesThe HP-UX 11.0 Bootable Archive (12548-01) did not include the files to localize a system to Korean or Chinese. The necessary file sets may be found on the update CD under UXCoreMedia. Install them as necessary.

● Following installation of the Korean or Chinese file sets, verify their status by executing swverify().

For example:

swverify International.KOREAN

swverify International.CHINESES

swverify International.CHINESET


Update PDS 12.0 software

This section contains the following topics:

● Prerequisites

● Installing PDS 12.0 Service Pack 5


! Important:Important: The installation of this Service Pack for the non-English languages does not

retain changes to certain files as it does on an English system. Instead it overwrites them. There may be files that have been configured that are overwritten during the installation process.

After installation it may be necessary to reinstall and/or reconfigure features. The original copy of the files overwritten or modified during installation can all be found in the following directory:

/opt/avaya/pds/pre_sp5

Do not copy these files back. Use them as a reference.

PrerequisitesBefore installing Service Pack 5, verify that the operating system is up to date with the current revision level and patch level.

Stopping PDS and the mid-tier softwareTo stop the PDS and the mid-tier software:

1. Log in as admin.

2. Execute the following commands:

stop_pds

stop_mts

3. Take any steps necessary to back up configuration files that must be brought forward after this release is installed.



Removing existing softwareTo remove the previous version of the software:

1. Log out and log back in as root.

CAUTION:!

CAUTION: Do not su to root from admin.

2. Execute the following command:

swlist DIALER

If the DIALER.SURF fileset is installed on this machine, execute the following steps to remove it.

swremove (and press Enter to continue if prompted)

The system displays the SD Remove - Software Selection dialog, as well as the installed software products.

3. Using the arrow keys, position the cursor on the DIALER product and press Enter. The system displays the product file sets.

4. Using the arrow keys, position the cursor on the SURF file set, and press SPACEBAR to highlight the entry.

5. Press Tab, and then enter a to display the Actions menu item.

6. Enter r to select the Remove (analysis) option. The system displays the Remove Analysis dialog and the analysis phase begins. At the conclusion of the analysis phase, the system displays the results.

- Status should be Ready- Products Scheduled should be x of x, where x is the total number of products

selected. If there are no errors, go to step 10.

If an error occurred, the system displays an Error dialog. Press Enter (OK) to acknowledge the error.

a. Tab to Cancel and press Enter.

b. Press Tab and then enter f to display the File menu items.

c. Enter e to exit swremove.

d. Refer to the file /var/adm/sw/swagent.log for a listing of the errors and/or warnings. Resolve all problems and go back to step 1.

7. Tab to OK and press Enter. The system displays Do you still wish to begin Removal?. Press Enter (yes). The system displays the Remove Window dialog and the removal of filesets begins. When the removal has concluded, the system display the results.

Installing PDS 12.0 Service Pack 5


- Status should be Completed- Percent Complete should 100%- Kbytes Removed should be x of x


9. Press Tab and then f to display the File menu items.

10. Press e to exit swremove.

Installing PDS 12.0 Service Pack 5To install PDS 12.0 Service Pack 5 application software:

1. Insert the Avaya Predictive Dialing System Service Pack 5, Version 12.0 CD into the CD-ROM drive and wait until it loads.

2. Execute the following command:

swinstall (and press Enter to continue if prompted)

The system displays the Specify Source dialog and the Source Depot Type field will be highlighted.

3. Tab to Find Local CD and press Enter.


The system displays the SD Install - Software Selection dialog, as well as the software products found on the CD media.

5. Using the arrow keys, position the cursor on the PDS_SVCPK product and press Enter. The system displays the file sets that comprise the PDS_SVCPK product.

a. Using the arrow keys, position the cursor on each of the appropriate filesets (see below), and press SPACEBAR to highlight the entry. For all installations, the following filesets are required and must be selected.

ADMIN

DIALER

PDSBASE

SOE

TZONEBASE

ZIPS



b. Depending on the language of the installation, select one, and only one, of the following file sets.

CHINESE_SIMPLIFIED

ENGLISH

JAPANESE

KOREAN

SPANISH_INTL

Note:Note: The following languages are no longer supported for the Avaya Predictive Dialing

System, Version 12.0 and as such have been removed from Service Pack 5.

FRENCH_FRANCE

GERMAN

ITALIAN

PORTUGUESE_BRAZIL

c. If this system is a MidTier Server, select the following file sets:

MIDTIER

MTBASE

d. If the on-line manpages are wanted on the system, the following fileset must be selected.

MANBASE

e. If the IVR Integration feature is installed on this system, the following fileset must be selected.

IVR

f. If Predictive Agent Blend is installed on this system, the following filesets must be selected.

BLEND

DISPATCHER

PABBASE

6. After the appropriate selections have been made, press 'm' to mark the highlighted entries for installation. If you see a message about additional software being marked, press Enter (OK) to acknowledge the message.

7. Using the arrow keys, position the cursor on the ..(go up) and press Enter. At this time there will be a "Partial" in front of PDS_SVCPK.

Post installation


8. Press Tab, and then 'a' (without the quotes) to display the Actions menu item. Press 'i' to select the Install (analysis) option.

The Install Analysis dialog will be displayed and the analysis phase will begin. At the conclusion of the analysis phase, the Install Analysis dialog will display the results.

- Status should be "Ready" - Products Scheduled should be "x of x".

If there are no errors, go to step 9.

If an error occurs, an Error dialog will be displayed. Press Enter (OK) to acknowledge the error. Tab to Cancel and press Enter.

Press Tab and then 'f' to display the File menu items. Press 'e' to exit swinstall.

Refer to the file "/var/adm/sw/swagent.log" for a listing of the errors and/or warnings. Resolve all problems and go back to step 1.

9. Tab to OK and press Enter. The Install Window dialog will be displayed and the installation of the filesets will commence. When the installation has concluded, the Install Window dialog will display the results. Status should be "Completed", Percent Complete should be "100%" and Kbytes Installed should be "x of x".


11. The SD Install - Software Selection dialog will again be displayed. Press Tab and then 'f' to display the File menu items. Press 'e' to exit swinstall.

12. Review the file "/var/adm/sw/swagent.log" for any additional errors or warnings. Resolve all problems before proceeding.

13. Remove the CD from the CD-ROM drive and store in a safe place.

Post installationThis section describes the steps that must be taken after this software is installed but before the Avaya PDS is started up with the start_pds command.

Modifying write tape parametersWith this release the *.wt_tape files were modified to replace RMDUPS with RMDUPSFIELD and RMDUPSVALUE. The entry for RMDUPSFIELD is defaulted to ACCTNUM.

● If the wt_tape command was modified to change the parameter to de_reject from ACCTNUM to some other field, change the RMDUPSFIELD entry in each of the .wt_tape files to that field name.



Modifying pds_system and pds_extract usersWith this release the pcanal directory was moved to below the public directory and the permissions and ownership changed to 2775 and ftp:other.

Because all files created in that directory now have a group ID of other, all users that access those files need to belong to group other. The service pack will take care of the necessary system users, however, users added by the customer (from running createop) that are members of group pds_system or pds_extract will not get fixed.

● Modify users by logging in as root and running the following command:

usermod -G pds_agent,other <userID>

Modifying master.cfg parameter defaultsWith this release the parameter PRIMARY was added to master.cfg. The default is set to NO.

● If this release is installed on a system that is either a stand-alone or primary system in a pod, edit the /opt/avaya/pds/etc/master.cfg file to set the PRIMARY parameter to YES.

● If this release is being installed on a system where the TZ parameter is set to GMT0BST, edit the /opt/avaya/pds/etc/master.cfg file to set the LANG parameter to en_GB.iso88591.


Update PDS database


● Prerequisites

● Installing PDS Database Service Pack 5

PrerequisitesInstall the Avaya PDS 12.0 Service Pack 5 software update.

Update PDS database


Installing PDS Database Service Pack 5To install PDS 12.0 Service Pack 5:

1. Insert the Avaya PDS Database Service Pack 5, Version 1.0 CD into the CD-ROM drive, wait until it loads and then execute the following commands from the UNIX command prompt.

su admin

check_db

sqlplus avayadba/avayadba

quit

If not all processes are running or the connection to sqlplus did not succeed, execute the following commands.

stop_db

start_db

check_db

sqlplus avayadba/avayadba

quit

If not all processes are running or the connection to sqlplus did not succeed, resolve the problems and execute the stop and start commands again.

exit (to return to root)

swinstall (and press Enter to continue if prompted).

The Specify Source dialog will appear and the Source Depot Type field will be highlighted.

2. Tab to Find Local CD and press Enter.


The SD Install - Software Selection dialog will be displayed, as well as the software products found on the CD media. Using the arrow keys, position the cursor on the PDSDB_SVCPK product and press 'm' to mark the entry for installation.

4. Press Tab, and then 'a' (without the quotes) to display the Actions menu item. Press 'i' to select the Install (analysis) option.

The Install Analysis dialog will be displayed and the analysis phase will begin. At the conclusion of the analysis phase, the Install Analysis dialog will display the results.

- Status should be "Ready"

Installing PDS Database Service Pack 5


- Products Scheduled should be "x of x".

If there are no errors, go to step 5.

If an error occurs, an Error dialog will be displayed. Press Enter (OK) to acknowledge the error.

Tab to Cancel and press Enter.

Press Tab and then 'f' to display the File menu items. Press 'e' to exit swinstall.

Refer to the file "/var/adm/sw/swagent.log" for a listing of the errors and/or warnings. Resolve all problems and go back to step 2.

5. Tab to OK and press Enter. The Install Window dialog will be displayed and the installation of the filesets will commence. When the installation has concluded, the Install Window dialog will display the results.

- Status should be "Completed", - Percent Complete should be "100%" - Kbytes Installed should be "x of x".

Tab to Done and press Enter.

The SD Install - Software Selection dialog will again be displayed. Press Tab and then 'f' to display the File menu items. Press 'e' to exit swinstall.

Review the file "/var/adm/sw/swagent.log" for any additional errors or warnings. Resolve all problems before proceeding.

6. Review the following log files for any additional errors or warnings:

/opt/oracle/sp5_install.log

/opt/oracle/sp5_stdout.log

/opt/oracle/sp5_stderr.log

Resolve all problems before proceeding.

7. Remove the CD from the CD-ROM drive and store in a safe place.

8. Execute the following command from the UNIX command prompt:

swlist PDSDB_SVCPK

Compare the output of the command with the last entry for PDSDB_SVCPK in /opt/avaya/pds/etc/log_file. If they are not the same, edit log_file to match the output of swlist.

Note:Note: This should only occur if an earlier version of PDSDB_SVCPK existed on the

system when the new version was installed.

Update PDS database



Update Campaign Director 4.0 software


● Prerequisites

● Installing Campaign Director 4.0 Service Pack 5


PrerequisitesThe following instructions describe steps that must be completed before Campaign Director is installed.

This release requires the installation of the PDS Middle Tier Windows Components 1.0 which provides data services to the Campaign Director 4.0 applications. The services are related to:

● Historical Monitoring

● Exception/Alerts Monitoring

● Command and Control Services Integration for Campaign Director

● Session Management

● Middle Tier Configuration Tools

● Real Time Monitoring Hierarchy Editor

● Oracle Client

● ODBC Database Connectivity Services

● Middle-tier diagnostic logging and other utilities

There are two options for installing these components:

● Cummulative: Use when the PC has no earlier version of the PDS Middle Tier Windows Components installed. The setup will install Version 1.0 and all service packs (1 through 5).

● Service Pack 5 only: Use when the PC has any earlier release of the PDS Middle Tier Windows Components and service packs 1 through 4 installed. Do not remove the existing copy of Avaya PDS Middle Tier Windows Components 1.0 software.



To install the PDS Middle Tier Windows Components:

! Important:Important: Oracle 8i (8.1.6) client is installed and configured as part of the installation. In the

event that there are any other versions of Oracle software on the PC where this is being installed, please remove the earlier versions of Oracle software before proceeding with the installation.

1. Insert the Avaya PDS Campaign Director 4.0 Service Pack 5 CD in the CD-ROM drive.

2. Click Start > Run.

3. Browse to the \MT1_SP5\Cumulative or MT1_SP5\ServicePackOnly directory on the CD, depending on which setup option you require. Choose SP5setup.exe. Click OK.

4. Follow the setup instructions.

● If you chose the cumulative setup, the PC will be updated to version 1.0 with SP1, SP2, SP3, SP4, and SP5 updates.

● If you chose the Service Pack 5 only setup, the PC will be update with the PDS Middle Tier Windows Components Service Pack 5.

Setup installs the following files in \program files\Avaya\PDSMiddleTier:

Avmesg.dll (No Version Info)

Avmtdsci.dll (1.5.07)

Ccbridge.dll (1.5.07)

Sessionmgr.dll (1.4.02)

PDSMiddleTierConfigurator.Exe (1.5.07)

Ccsclient.exe (No Version Info)

OopSession.exe (1.5.07)

OopSessionps.dll (No version info)

Note:Note: You may see the following message towards the end of the midtier installation:

Unable to delete directory. Please delete folder ClientCD from C: manually after installation.Click OK, then ignore this message. Do not delete the folder.

Note:Note: In the event of a failure in installing the service pack, do the following:

a. Insert the original CD used for installing the product into the CD-ROM drive.

b. Uninstall the earlier version using Control Panel > Add Remove Programs.

c. Remove the original CD from the CD-ROM drive.

Installing Campaign Director 4.0 Service Pack 5


d. Insert the SP5 CD into the CD-ROM drive and reinstall PDS Middle Tier Windows Components 1.0 SP5 using the cumulative setup method described above.

5. The Avaya Mid-Tier Configuration application online help resides on the CD-ROM, and the CD-ROM is needed to access it while running the application.

a. To access the Help, browse to the directory: \MT1_SP5\Cumulative\Helpb. Double-click on the index.htm file to activate the help.

Tip:Tip: Copy all the files in the \MT1_SP5\Cumulative\Help directory from the CD-ROM

to the [PROGRAMFILES]\Avaya\PDSMiddleTier directory on the client PC to make the online help files available from the Avaya Mid-Tier Configuration application without the CD.

6. Run PDSMiddleTierConfigurator.exe from the [PROGRAMFILES]\Avaya\PDSMiddleTier folder on the PC. Enter the IP address and name settings for your Primary PDS (Middle Tier PDS) system. (Setup clears any previous middle-tier configuration settings if a previous version was installed.)

If all validation tests succeed, follow the instructions below to uninstall the previous version (if necessary) and then install the Campaign Director applications.

To uninstall a previous version of Campaign Director:

Note:Note: If you are upgrading from an earlier version of Campaign Director, your custom

and personalized Monitor views will be upgraded automatically.

If you have customized Analyst reports, those reports will not be upgraded.

1. Go to Start > Settings > Control Panel.2. Double-click Add/Remove Programs.

3. Select Campaign Director. Click Uninstall.4. Follow the instructions to remove the applications. If you have installed an earlier version

of Compliance Monitor, uninstall it now.

Installing Campaign Director 4.0 Service Pack 5To install Campaign Director 4.0 Service Pack 5:

1. Insert the Avaya PDS Campaign Director 4.0 Service Pack 5 CD in the CD-ROM drive.


3. Browse to the CD and choose Setup.exe. Click OK.




Post installation

Installing Campaign Director patches if availableInstall any patches that may be available. Go to http://support.avaya.com and click Downloads.

Setting double-byte language settingsIf Campaign Director has been installed in a double-byte language such as Korean, Chinese or Japanese, follow these additional steps:

1. Copy the file DBSetting.exe from the installation CD to a temporary directory on the PC.

2. Double-click DBSetting.exe.

3. Select the language that was used to install Campaign Director, then click OK.

The application updates the registry with the correct information so that the Oracle database will display data with the correct language settings.

4. Click Close.



Update PDS Agent 1.0

This release is a service pack for PDS Agent 1.0. It contains bug fixes and incorporates patches issued since Service Pack 4.

● PDS1_681 PDS agent won't allow a recall to be established during preview time.

● PDS1_617 Telephone bar loses focus.

The installation program has been modified so that only English, Spanish, Chinese, Japanese, and Korean are offered as available language versions.

PrerequisitesUninstall the existing PDS Agent application.

1. Go to Start > Settings > Control Panel.2. Double-click Add/Remove Programs.

3. Select Avaya PDS Agent. Click Uninstall.

Installing PDS Agent 1.0 Service Pack 5To install PDS Agent 1.0 Service Pack 5:

1. Insert the Avaya PDS Agent 1.0 Service Pack 5 CD in the CD-ROM drive.


3. Browse to the CD and choose Setup.exe. Click OK.


Update PDS Agent 1.0


avaya12.pds

Documents

Transcript of avaya12.pds