PC4 Troubleshooting Main

846
Avaya Proactive Contact Release 4.0 Maintenance and Troubleshooting March 2008

Transcript of PC4 Troubleshooting Main

Page 1: PC4 Troubleshooting Main

Avaya Proactive Contact Release 4.0Maintenance and Troubleshooting

March 2008

Page 2: PC4 Troubleshooting Main

© 2008 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 might 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. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User.

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 the time and we have no control over the availability of the linked pages.

WarrantyAvaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya�s standard warranty language, as well as information regarding support for this product, while under warranty, is available through the Avaya Support Web site:http://www.avaya.com/support

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 WEB SITEhttp://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)

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 the Avaya Support Web site:http://support.avaya.com/ThirdPartyLicense/

Preventing toll fraud"Toll fraud" is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of toll fraud associated with your system and that, if toll fraud occurs, it can result in substantial additional charges for your telecommunications services.

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. For additional support telephone numbers, see the Avaya Support Web site:http://www.avaya.com/support

TrademarksAvaya and the Avaya logo are either registered trademarks or trademarks of Avaya Inc. in the United States of America and/or other jurisdictions.

All other trademarks are the property of their respective owners.

Downloading documentsFor the most current versions of documentation, see the Avaya Support Web site:http://www.avaya.com/support

114549Avaya supportAvaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is 1-888-732-3343 in the United States. For additional support telephone numbers, see the Avaya Support Web site:http://www.avaya.com/support

To provide feedback on this document, send email to [email protected].

Page 3: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 1

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Reasons for reissue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Related documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Hardware maintenance large cabinet and PG230 . . . . . . . . . . . . . . . . . . . . . . . 15Reseat or replace current supported cards . . . . . . . . . . . . . . . . . . . . . . . . 15Reseat or replace obsolete cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Obsolete cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Ribbon cable from the SWI to the NBC. . . . . . . . . . . . . . . . . . . . . . . . . 18

Avaya Proactive Contact dialer troubleshooting . . . . . . . . . . . . . . . . . . . . . . . 21Enhanced Network Bus Controller (ENBC) . . . . . . . . . . . . . . . . . . . . . . . . 21

LED indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Solutions for red or yellow LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Large Port Voice Card (LPVC2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23LED indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Solutions for red or yellow LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Enhanced Universal Trunk card (EUTC) . . . . . . . . . . . . . . . . . . . . . . . . . . 25LED indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Operator Line Interface card (OLIC2). . . . . . . . . . . . . . . . . . . . . . . . . . . . 26LED indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Quad digital trunk cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Quad T1 (QT1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Quad T1 primary rate interface card (QT1-PRI) . . . . . . . . . . . . . . . . . . . . 29Quad E1-Channel Associated Signaling 120 Ohm (QE1-CAS 120) . . . . . . . . . . 30Quad E1Primary Rate ISDN 120 Ohm (QE1-PRI 120) . . . . . . . . . . . . . . . . . 31Quad E1-Channel Associated Signaling 75 Ohm (QE1-CAS 75) . . . . . . . . . . . 33Quad E1- Primary Rate ISDN 75 Ohm (QE1-PRI 75) . . . . . . . . . . . . . . . . . . 34

Digital Signal Processor -2 (DSP2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35LED indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Internet Protocol Telephony Card (IPTC). . . . . . . . . . . . . . . . . . . . . . . . . . 37

Software Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Understanding backup and restore operations . . . . . . . . . . . . . . . . . . . . . . 39Using backup and restore commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Monitor the DAT drive status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Contents

Page 4: PC4 Troubleshooting Main

2 Maintenance and Troubleshooting Guide March 2008

Various options for Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . 41Back up the complete system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Back up the system and calling lists . . . . . . . . . . . . . . . . . . . . . . . . . . 42Back up Avaya Proactive Contact system files . . . . . . . . . . . . . . . . . . . . 42Back up system configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . 43Back up system data/stat files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Restore all the data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Restore a file from archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45List/Verify a file in archive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46List/Verify archive contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46List archive volume information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Back up all calling lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Back up a specific calling list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Restore all calling lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Restore a specific calling list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Back up a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Restore a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Error messages and message type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Troubleshooting questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Unable to start jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121List did not download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Agent cannot connect- dialback failure - unable to login - headset in use . . . . . . . 123Reports not working . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Analyst - GUI based reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123PC Analysis - UNIX Based Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . 124

Call completion codes such as line Idle, busy, or hung up in queue, appears excessively 124Internet Monitor issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Changes affecting performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Message Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Message Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Agent key files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Calling list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Upload/Download list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Dialer event Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Completion Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Message Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Back ups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Data pops (slow or none) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Page 5: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 3

Predictive Blend not acquiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Detailed troubleshooting questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Networking Issues: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Hardware troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

General hardware issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Avaya CPU Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Digital Switch Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Telephony Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Telephony & Switch Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Software Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

General software issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Mid-Tier Services Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Supervisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Database Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Avaya Proactive Contact Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . 141Verify software is running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141CORBA services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

nsls script fails to list names in Naming_Service . . . . . . . . . . . . . . . . . . . 142Some services fail to start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Sales Verification testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143CCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

CCS not running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143CCS not passing requests to DCCS server . . . . . . . . . . . . . . . . . . . . . . 144

DCCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144DCCS processing errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144DCCS and Corba problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144DCCS crashes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144DCCS general troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Using Test Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Job will not start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Jobs ends just after start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Invalid headset ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Agent profile will not execute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Selection list Unavailable for use. . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Job in test mode ignores keystrokes. . . . . . . . . . . . . . . . . . . . . . . . . . 150General Job troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

CTI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Page 6: PC4 Troubleshooting Main

4 Maintenance and Troubleshooting Guide March 2008

Installation: Verify CTI link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152CTO OAM Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157CTI Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Troubleshooting tips for Avaya CTI . . . . . . . . . . . . . . . . . . . . . . . . . . 159

StatsPump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Mid-Tier Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Mid-Tier database network problems . . . . . . . . . . . . . . . . . . . . . . . . . 161Mid-Tier database not running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Verify Mid-Tier components can access database . . . . . . . . . . . . . . . . . . 162

Mid-Tier Data Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Dialer Mid-Tier connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Historical Data Server Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

HDCC troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Recovering in the event of media failure. . . . . . . . . . . . . . . . . . . . . . . . 168Common Oracle errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

End user applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170Analyst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Error message, source and error description table . . . . . . . . . . . . . . . . . . . . . . 175

Error message text and source file table. . . . . . . . . . . . . . . . . . . . . . . . . . . . 269Cannot transfer inbound call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385Command failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387Timed out waiting for <message> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389Operator monitor process does not respond . . . . . . . . . . . . . . . . . . . . . . . 391Agent <name> logged in Already - Access Denied . . . . . . . . . . . . . . . . . . . . 393Unable to send message to porter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395Password has expired. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397<agent><agent_name> - Operator number returned invalid <slot_num> . . . . . . . . 399Incorrect message type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401Incorrect number of arguments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403Must select unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405Failed to allocate memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407Audio file name too long . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409Bad argument . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411

Page 7: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 5

ERROR - Unknown file descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413Invalid entry for <name> in <filename> . . . . . . . . . . . . . . . . . . . . . . . . . . 415Field has incorrect length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417Bad file descriptor <num>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419Invalid headset number <num> <line> . . . . . . . . . . . . . . . . . . . . . . . . . . . 421Failed to initialize screen environment. . . . . . . . . . . . . . . . . . . . . . . . . . . 423Invalid line selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425Invalid logical connector <name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427Invalid recall code <num>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429Invalid ring count <num> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431Invalid time format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433Conference in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435Field not defined in calling list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437Unable to create file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439agent - Failed to read from file <name> . . . . . . . . . . . . . . . . . . . . . . . . . . 441Failed to unlock file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443Warning: CFRM message truncated . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445Callbacks are not permitted on inbound calls . . . . . . . . . . . . . . . . . . . . . . . 447Field <name> not defined in calling list <filename>. . . . . . . . . . . . . . . . . . . . 449clstat <xfd> failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451Failed to remove file <filename> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453Clear fdict <number> failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455Date is before the current date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457Incoming command exceeded maximum buffer size . . . . . . . . . . . . . . . . . . . 459<string>: Confirm error (num) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461File corruption or record size mismatch detected in calling list (name> . . . . . . . . 463CTI Error: <string><num> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465CTI not configured for agent events . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467Duplicate ALL phone numbers specification . . . . . . . . . . . . . . . . . . . . . . . 469Duplicate country specified . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471Environment variable not set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473OnEventEstablished: Unknown command (7) . . . . . . . . . . . . . . . . . . . . . . . 475Recall attempt can�t exceed <num> . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477Extra comma in selection criteria. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479Failed to setup command keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481Failed to lock file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483

Page 8: PC4 Troubleshooting Main

6 Maintenance and Troubleshooting Guide March 2008

Failed to initialize keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485Failed to open directory <dir_name>. . . . . . . . . . . . . . . . . . . . . . . . . . . . 487Failed to read file header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489Failed to initialize switcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491Fail to load record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493Fatal error on select - <num> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495Field name <name> is invalid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497Invalid field value <value>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499Missing or invalid entry in file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501File <filename> exists, but is not readable by user <user_name. . . . . . . . . . . . . 503File <filename> exists, but cannot be written by user <user_name . . . . . . . . . . . 505File <filename> does not exist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507File did not close. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509No space on file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511Unequal phone number field lengths in file <name> . . . . . . . . . . . . . . . . . . . 513Field value not in acceptable list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515 Entry <value> missing/invalid in <filename> file . . . . . . . . . . . . . . . . . . . . . 517Gap found between selection criteria lines . . . . . . . . . . . . . . . . . . . . . . . . 519Headset <id_num> not specified in dgswitch.cfg file . . . . . . . . . . . . . . . . . . . 521Headset port number <num> out of range . . . . . . . . . . . . . . . . . . . . . . . . . 523<agent_name> - Exceeded operator slots available, MAXOPS is low . . . . . . . . . . 525Inbound agents only permitted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527Invalid answer delay time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529Invalid call detection mode <name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531CSTAUniversalConfEvent for call monitor, error = 24. . . . . . . . . . . . . . . . . . . 533Invalid format character found . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535invalid channel number <string> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537Invalid DAA type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539Invalid date format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541Invalid delay specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543Invalid file name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545New password entered is invalid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547Invalid offhook retry delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549Invalid phone. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551Invalid phone <number> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553Invalid phone number length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555

Page 9: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 7

Invalid phonestat - <status>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557Original password is invalid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559Invalid pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561Invalid recall code <code> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563 Invalid response from operator monitor process. . . . . . . . . . . . . . . . . . . . . 565Invalid range character . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567Invalid ring count <num> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569Invalid time zone character <char> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571Invalid use of ALL phone numbers specification . . . . . . . . . . . . . . . . . . . . . 573Invalid VM2 locale code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575Invalid wait limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577Failed to invoke function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579IPC - invalid input argument . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581IPC - invalid ipc entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583Invalid ipc number <num> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585<process_name> - Accessing bad semaphore . . . . . . . . . . . . . . . . . . . . . . 587<process_name> - Failed to open semaphore, err(<num>). . . . . . . . . . . . . . . . 589<process_name> - Failed on semaphore operation, err <err_num> key = <sem_key_id> code = <op_code> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591

<process_name> Failed on semaphore removal, err=<num> key=<num> . . . . . . . 593IPC - Failed to open opmon message queue . . . . . . . . . . . . . . . . . . . . . . . 595Response message too long . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597IVR_SCRIPT is blank in job <name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599Failed to create jobmon graphical user interface (GUI) . . . . . . . . . . . . . . . . . . 601Job <name> not running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603Job <name> is not valid for IVR agents . . . . . . . . . . . . . . . . . . . . . . . . . . 605Error loading job chain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607Attempt to store list_client on host failed . . . . . . . . . . . . . . . . . . . . . . . . . 609Line not released . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611Mastercfg error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613Failed to determine max number of phones . . . . . . . . . . . . . . . . . . . . . . . . 615Unable to remove message queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617Missing delay specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619Missing high range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621Missing completion code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623Missing line type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625

Page 10: PC4 Troubleshooting Main

8 Maintenance and Troubleshooting Guide March 2008

Missing or invalid num of chars to strip . . . . . . . . . . . . . . . . . . . . . . . . . . 627Missing phone numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629Missing prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631Missing limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633Missing suffix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635Missing or invalid low range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637Missing or invalid reject phone number pattern. . . . . . . . . . . . . . . . . . . . . . 639Missing or invalid time zone designation . . . . . . . . . . . . . . . . . . . . . . . . . 641Missing time zone specification for country <num> . . . . . . . . . . . . . . . . . . . 643MakeCall/MakePredictiveCall/TransferCall Confirm error (33) . . . . . . . . . . . . . . 645<type> agents are not permitted on this job . . . . . . . . . . . . . . . . . . . . . . . . 647Must specify transfer job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649Failed to attach shared memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651Cannot open channel to operator monitor process . . . . . . . . . . . . . . . . . . . . 653Failed to detach shared memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655No DONE_TME setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657Failed to find linked job file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659Unable to open keys file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661Failed to get message queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663Unable to receive a message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665Failed to send message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667No more records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669Field has non-numeric value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671No previous record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673Failed to process file <filename> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675Cannot be DONE from alternate screen . . . . . . . . . . . . . . . . . . . . . . . . . . 677Non-directory in directory path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679<process_name> failed to read from file <filename> . . . . . . . . . . . . . . . . . . . 681Recall not allowed for inbound call. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683No record found . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685No REL_DIST setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687No REL_TME setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689Failed to remove shared memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691Sales verification with unit work lists is not permitted . . . . . . . . . . . . . . . . . . 693Missing std to dial phone number format . . . . . . . . . . . . . . . . . . . . . . . . . 695Not a calling list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697

Page 11: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 9

Unable to become root privilege for setting password . . . . . . . . . . . . . . . . . . 699Cannot find time zone for phone number . . . . . . . . . . . . . . . . . . . . . . . . . 701Failed to create window pointer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703Failed to write to file <filename> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705Only outbound agents permitted by sales verification . . . . . . . . . . . . . . . . . . 707Outbound or Managed agents only permitted . . . . . . . . . . . . . . . . . . . . . . . 709<opname> operation failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711<op_name> operation failed for file <file_name> . . . . . . . . . . . . . . . . . . . . . 713<string><string>- Operator number returned wrong <num1>, job number <num2> . . 715Operator slot semaphore not available . . . . . . . . . . . . . . . . . . . . . . . . . . 717Headset value (<headset_value>, <return_value>) out of bound. . . . . . . . . . . . . 719Outbound agents only permitted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721Pattern error at line <number> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723Pattern error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725Telephone line not available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727Telephone line not offhook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729Phone number too long . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731Timed out waiting for response from porter . . . . . . . . . . . . . . . . . . . . . . . . 733Password can not be changed, change limit not expired. . . . . . . . . . . . . . . . . 735Preview record search failed to initialize. . . . . . . . . . . . . . . . . . . . . . . . . . 737Changes to record not saved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739Recall can't be less than <num> minutes . . . . . . . . . . . . . . . . . . . . . . . . . 741Range does not come after previous range . . . . . . . . . . . . . . . . . . . . . . . . 743Recall time and date outside timezone. . . . . . . . . . . . . . . . . . . . . . . . . . . 745Record is no longer available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747Record currently in use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749Rejected phone number (L<num>) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751Field entry is required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753Route End Error: RegReqID = <num>, CrossRefID = <num>, Error = <num> . . . . . . 755Report failed, system out of space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757Molocale - unknown language name <lang>. . . . . . . . . . . . . . . . . . . . . . . . 759Selection list not available for use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761Could not verify selection list for job. . . . . . . . . . . . . . . . . . . . . . . . . . . . 763Selection list not created with this calling list . . . . . . . . . . . . . . . . . . . . . . . 765Could not verify selection list for job. . . . . . . . . . . . . . . . . . . . . . . . . . . . 767Cannot find service in /etc/services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769

Page 12: PC4 Troubleshooting Main

10 Maintenance and Troubleshooting Guide March 2008

Caught signal number <num> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771Caught signal <num> and terminated . . . . . . . . . . . . . . . . . . . . . . . . . . . 773Socket call failed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775Unable to setup listen on socket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777Socket failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779Socket connection to list server running on <name> failed . . . . . . . . . . . . . . . 781STATUSFLAG field missing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783Failed to process line (<line_buffer_name>). . . . . . . . . . . . . . . . . . . . . . . . 785tget returned error number <num> raising signal <num> . . . . . . . . . . . . . . . . 787<string>-<string> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 789Timed out waiting for <string> confirmation. . . . . . . . . . . . . . . . . . . . . . . . 791Calling list <name> is not in shared memory . . . . . . . . . . . . . . . . . . . . . . . 793Calling list line count does not match shared memory . . . . . . . . . . . . . . . . . . 795Invalid normal trunk equipment number <num> . . . . . . . . . . . . . . . . . . . . . 797Normal trunk port number <num> out of range . . . . . . . . . . . . . . . . . . . . . . 799Unable to bind to local address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801Unable to accept connection on socket . . . . . . . . . . . . . . . . . . . . . . . . . . 803Unable to access host <name> using name . . . . . . . . . . . . . . . . . . . . . . . . 805Unable to connect to socket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807Failed to create directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809Failed to read calling list definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811Unable to open list <calling_list_name> . . . . . . . . . . . . . . . . . . . . . . . . . . 813Process unable to send <string> to <process_name> . . . . . . . . . . . . . . . . . . 815Unable to send data to socket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817Molocale - failed to set locale <name> . . . . . . . . . . . . . . . . . . . . . . . . . . . 819Call blending is not available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821Unequal phone number field lengths in file <filename> . . . . . . . . . . . . . . . . . 823Unknown Command message - <command> . . . . . . . . . . . . . . . . . . . . . . . 825Unknown IPC message - <string> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827Incorrect job type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829Unknown screen type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831Unit value not found, or unavailable . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833Linking between virtual agent jobs and non-virtual jobs is not permitted. . . . . . . . 835Unable to open file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837Failed to find screen <name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839Write error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 841

Page 13: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 11

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843

Page 14: PC4 Troubleshooting Main

12 Maintenance and Troubleshooting Guide March 2008

Page 15: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 13

Preface

This section contains the following topics:

● Purpose on page 13

● Audience on page 13

● Reasons for reissue on page 13

● Related documents on page 14

PurposeThe purpose of this guide is to provide detailed information for hardware and software maintenance for the Avaya Proactive Contact 4.0 system. It also includes up to date troubleshooting for hardware and software maintenance for the Avaya Proactive Contact 4.0 system.

Audience

This guide is for personnel who install, configure, and troubleshoot Avaya Proactive Contact installations.

Reasons for reissue

Avaya Proactive Contact 4.0 is a major new release of the Avaya Proactive Contact (previously known as PDS), featuring substantial advances in core functionality, new deployment options, and updates to the underlying platform technology.

Avaya Proactive Contact 4.0 provides you with three system deployment options tailored to meet your specific call center requirements:

● Avaya Proactive Contact with AES.

Page 16: PC4 Troubleshooting Main

14 Maintenance and Troubleshooting Guide March 2008

● Avaya Proactive Contact with Avaya PG230 Proactive Contact Gateway (available with an Avaya-provided server)

● Avaya Proactive Contact system (with the traditional system cabinet)

This release supports simple migrations between the different deployments allowing you to start small and easily upgrade to a larger system.

All configurations use the same robust Avaya Proactive Contact core predictive dialing application and the same client suite called Avaya Proactive Contact Supervisor. The application suite includes Monitor, Editor, Analyst, and a new Health Manager application designed to help you monitor and administer system functions. Changes were also made to provide a more robust, simplified version of the current feature set, as well as simplified configuration and installation of the system. Powerful tools such as Hierarchy Manager and Completion Code Manager continue to be supported.

Avaya Proactive Contact 4.0 introduces an updated predictive dialing algorithm with a revolutionary operating mode called Cruise Control, which allows you to achieve even higher operational efficiencies than were previously possible with Avaya PDS version 12.0.

Related documents● Planning and Prerequisites for Avaya Proactive Contact

● Installing and Configuring Avaya Proactive Contact

● Administering Avaya Proactive Contact (UNIX-based Interface)

● Using Avaya Proactive Contact Supervisor

● Using Avaya Proactive Contact Analyst

● Avaya Proactive Contact Safety and Regulatory Information

● Avaya Proactive Contact Documentation Library (CD-ROM)

Page 17: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 15

Hardware maintenance large cabinet and PG230

This section details the hardware maintenance tasks required for the large cabinet and PG230. The maintenance involves replacing or reseating cards. The topics covered in this section are:

● Reseat or replace current supported cards

● Reseat or replace obsolete cards

Reseat or replace current supported cards

To reseat or replace a card follow these steps:

1. Power down the switch and the card cage.

2. Slide the board into the card slot.

Page 18: PC4 Troubleshooting Main

16 Maintenance and Troubleshooting Guide March 2008

3. Hook the tabs onto the upper and lower lips of the card shelf.

4. Press firmly on the tabs to seat the board.

Reseat or replace obsolete cardsThese cards are still in use but are no longer shipping. The topics covered in this section are:

Page 19: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 17

Obsolete cardsTo remove the SWI card, follow these steps:

1. Shut down Digital Switch Controller (DSC) through the menu system.

2. Wait for the File System Successfully Closed message on the Switch Console screen.

3. Power off the Digital Switch Controller.

4. Unscrew the 1/8 inch Phillip's head screws on both sides of the card.

Note:Note: The screws do not need to be removed entirely from card.

5. Pull outward on tabs on both sides of the SWI card as shown below:

6. Pull the card out of the card slot.

7. Place the card on a static-proof mat or in a static-proof bag.

To replace the card with a new card:

1. Verify that the jumper settings on replacement card are the same as on the original.

2. Insert the card into the same slot that you removed the previous card from.

3. Push in card at points just inside the tabs on both sides of the card as shown below until card is firmly seated.

4. Tighten the screws on both sides of the card.

Page 20: PC4 Troubleshooting Main

18 Maintenance and Troubleshooting Guide March 2008

5. Restart the DSC.

Ribbon cable from the SWI to the NBCThe ribbon cable from the SWI to the NBC originates on the back of the Digital Switch Controller (DSC). A metal cable housing clamps this ribbon cable in place to prevent it unseating itself. In order to reseat or replace this cable, you must loosen the housing clamp and remove the housing from the DSC.

Follow these steps to reseat or replace the ribbon cable:

1. Loosen the screws identified as Step1 in the illustration to clamp and un-clamp the ribbon cable.

Page 21: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 19

2. Loosen the screws identified as Step 2 in the illustration to slide the clamp plate up and down. Reseat the ribbon cable if necessary.

3. If you need to replace the ribbon cable, you need to remove the screws labeled Step 3 in the illustration.

4. Replace the ribbon cable if necessary.

In step 5, pull the card straight back out of the slot without pulling outwards on the tabs on either side of the card as illustrated in the following:

Make sure to push the A RESET button so that the DSC reboots after the file system has been shut down through the menus. Switch the A-AUTO-B switch to the "A" position so that in normal operation the switch auto boots after a crash.

Page 22: PC4 Troubleshooting Main

20 Maintenance and Troubleshooting Guide March 2008

Page 23: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 21

Avaya Proactive Contact dialer troubleshooting

This section details solutions for hardware related issues in the Avaya Proactive Contact dialer. The two versions of the Avaya Proactive Contact hardware dialer are:

● Avaya Proactive Contact System

● Avaya Proactive Contact with PG230

The telecommunications switching component in each version is the same Avaya proprietary switch.

The cards covered in this section are the:

● Enhanced Network Bus Controller (ENBC)

● Large Port Voice Card (LPVC2)

● Enhanced Universal Trunk card (EUTC)

● Operator Line Interface card (OLIC2)

● Quad digital trunk cards

● Digital Signal Processor -2 (DSP2)

● Internet Protocol Telephony Card (IPTC)

Enhanced Network Bus Controller (ENBC)

The ENBC card is the CPU for the digital switch. It runs the switch generic software, which controls all aspects and operation of the switch.

Page 24: PC4 Troubleshooting Main

22 Maintenance and Troubleshooting Guide March 2008

! WARNING:!

WARNING: Never pull or reinsert the ENBC card in a slot while the switch is powered up. Never pull or reinsert the NBC cable or SCSI cable while the switch is powered up. This may cause severe damage to the ENBC.

! WARNING:!

WARNING: The only method for powering off the card cage (and therefore the ENBC Card) is to power off the UPS or disconnect the digital switch Power Supply from the power source. The digital switch does not have a built-in on/off switch.

LED indicators

Solutions for red or yellow LED

Note:Note: A major alarm anywhere in the switch causes the red LED on the ENBC card to

light, even if there is no problem with the ENBC card.

Note:Note: A minor alarm anywhere in the switch causes the yellow LED on the ENBC card

to light, even if there is no problem with the ENBC card.

Follow these steps to resolve the problem:

1. Check the system log file for error messages related to all cards other than the ENBC.

2. If any error messages exist, troubleshoot those cards.

Red Yellow Green Status

OFF OFF OFF Normal operation

OFF ON OFF Indicates Minor Alarm condition in system. Look at Card and System Alarm screens to determine details of alarm condition.

ON OFF OFF Indicates Major Alarm condition in system. Look at Card and System Alarm screens to determine details of alarm condition.

ON ON OFF Indicates ENBC is being reinitialized, ENBC software download, and self-test.

Page 25: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 23

3. Check for alarms on all cards other than the ENBC card. If alarms exist, troubleshoot those alarms.

4. If a red or yellow LED is still lit on the ENBC card, go to step 5.

5. Check the system log file for error messages related to the ENBC.

6. Reboot the switch. If the alarm LED remains lit, proceed to the next step.

7. Power down the switch and reseat the ENBC in slot 1.

8. Restart the switch. If the alarm LED remains lit, proceed to the next step.

9. Check the NBC cable behind slot 1 and connected to I/O Transition Module for a secure fit.

10. If required, power down the switch and reseat the cable.

11. Restart the switch. If the alarm LED remains lit, proceed to the next step.

12. Power down the switch and replace the ENBC.

13. Restart the switch. If the alarm LED remains lit, proceed to the next step.

14. Power down the switch and replace the NBC cable.

Large Port Voice Card (LPVC2)

The standard LPVC2 card carries 16 Mbytes of memory, and provides approximately 35 minutes of local voice storage. A larger version of the LPVC2 is an available option that carries 32 Mbytes of memory for 70 minutes of storage capacity. The LPVC2 has a direct connection to the ENBC I/O Transition Module over a SCSI bus. The connection enables the card to store and retrieve voice messages to and from the hard drive.

Page 26: PC4 Troubleshooting Main

24 Maintenance and Troubleshooting Guide March 2008

! WARNING:!

WARNING: Never remove, reseat or replace the SCSI cable behind the LPVC while the ENBC or card cage are powered on.

LED indicators

Solutions for red or yellow LEDFollow these steps to resolve the problem:

1. Check system log file for error messages related to the card in slot 3.

2. Check the Card Alarm screen in the Card Maintenance menu.

3. Try activating the LPVC via the Card Maintenance menu. If the LED remains lit, proceed to the next step.

4. Reseat the LPVC card.

5. Restart the system. If the LED remains lit, proceed to the next step.

6. Power down the system and reseat the SCSI cable at both ends.

7. Restart the system. If the LED remains lit, proceed to the next step.

Red Yellow Green Status

OFF OFF OFF Normal operation

OFF ON OFF Indicates Minor Alarm condition in system. Look at Card Alarm screen to determine details of alarm condition.

ON OFF OFF Indicates Major Alarm condition in system. Look at Card Alarm screen to determine details of alarm condition.

FLASH FLASH FLASH All flashing in sequence indicates the LPVC is receiving a download from Avaya Proactive Contact.

ON ON ON LPVC self test. Should only last 60 or so seconds.

OFF OFF ON Card is in Stand-by, Diagnostic, or Out of service mode.

Page 27: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 25

8. Replace the LPVC card.

Enhanced Universal Trunk card (EUTC)

The EUTC is a 16 port, 2-wire, analog card that can operate in Loop Start mode or Ground Start mode. Use the switch menus to configure loop or ground start. This card is rarely used.

LED indicators

SolutionsThe LEDS do not register phone line issues. Test phone lines with either the driver or the swit utility.

If the red LED is lit, replace the EUTC.

Red Yellow Green Status

OFF OFF OFF Normal operation

ON OFF OFF The EUTC has failed the self test.

OFF ON OFF The ENBC is unable to communicate with the EUTC and has stopped polling the EUTC.

OFF OFF ON The EUTC has not been added to the database or has been taken out of service via the Card Maintenance screen.

Page 28: PC4 Troubleshooting Main

26 Maintenance and Troubleshooting Guide March 2008

Operator Line Interface card (OLIC2)

The OLIC2 provides 24 4-wire headset connections for use by agents on the dialer. This function is seldom used, as most customers find the digital agent connections, dial-up and dial-back, to be far more efficient and workable. However, in certain environments, where no PBX is present or no agents are used on the PBX, a direct connection for the agents can be utilized. The OLIC2 is specifically designed for this environment.

LED indicators

SolutionsFollow these steps to resolve issues:

1. Check the system log for error messages related to the slots containing the OLIC2 card and the OLIC MDF adapter.

2. If there is a minor or major alarm on the OLIC card, on the main switch menu select C > G.

Red Yellow Green Status

OFF OFF OFF Normal operation

ON ON ON OLIC self-test in progress.

ON OFF OFF The OLIC2 has failed the self test on one or more ports.

OFF ON OFF The ENBC is unable to communicate with the OLIC2 and has stopped polling the OLIC2.

OFF OFF ON The OLIC2 has not been added to the database or has been taken out of service via the Card Maintenance screen.

Page 29: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 27

3. Use the Maintenance Menu to reset the card.

4. Check Maintenance Menu > Card Maintenance for unavailable ports that are marked with a P.

5. If a port is marked with a P, check the cabling for that port. If the problem persists, go to the next step.

6. If there is no specific alarm on the OLIC card, the problem may be in the OLIC port or in the wiring from the card to the agent�s workstation. To determine if the OLIC port is functioning correctly:

a. Remove the cable from the OLIC adapter for this port.

Note:Note: There are two cables which connect to each OLIC adapter. The top cable is for

ports 1-12.Tthe lower cable is for ports 13-24.

b. To cause the OLIC card to run its self-test, reseat the card. The self-test tests each of the 24 ports. It sends a signal out on the ear pair and expects to receive the same signal on the mouth pair.

c. If the OLIC card resets with no port failures, the problem is with one of the following:

● Cabling from the OLIC adapter to the workstation

● Headset equipment at the workstation

● OLIC adapter

d. If the OLIC card restores with port failures such as Code 4, Code 5, or Code6 on a specific port with no cable attached, then the problem is the OLIC card, go to step 9.

7. Shut down the digital switch and reboot the system. If the problem persists, go to the next step.

8. Reseat the OLIC card. If the problem persists, go to the next step.

9. Swap the OLIC 2 card with a new OLIC 2.

Quad digital trunk cardsThe Quad Digital Trunk Cards (QDTC) are a group of six similar cards that provide all the versions of digital trunking for the switch. Each version of this card is built on a common circuit board. Each card has four separate digital trunking spans of the type supported by the card. The six digital trunking cards are:

● Quad T1 (QT1)

● Quad T1 primary rate interface card (QT1-PRI)

● Quad E1-Channel Associated Signaling 120 Ohm (QE1-CAS 120)

Page 30: PC4 Troubleshooting Main

28 Maintenance and Troubleshooting Guide March 2008

● Quad E1Primary Rate ISDN 120 Ohm (QE1-PRI 120)

● Quad E1-Channel Associated Signaling 75 Ohm (QE1-CAS 75)

● Quad E1- Primary Rate ISDN 75 Ohm (QE1-PRI 75)

Quad T1 (QT1)

The card provides spans that comply to the original T1 specification for North America (ANSI T1.105). Each digital span includes four wires, two for the receive direction and two for the transmit direction. There are 24 pulse code modulated (PCM) time slots on the T1 span that provide 24 voice channels, with signaling provided by using low order bits in the voice channels, Robbed-Bit Signaling, in such a way that the overall voice quality is not significantly affected.

LED indicators

Solutions

Follow these steps to resolve issues:

1. Check the system log for error messages related to the slots containing the QT1 card.

2. Check Maintenance Menu > Card Alarm for alarms.

Red Yellow Green Status

ON ON ON Self-test in progress.

FLASH FL:ASH FLASH QT1.dwn file being downloaded.

OFF OFF OFF Normal operation

ON OFF OFF Carrier loss, OOF detected.

OFF ON OFF Remote alarm detected.

OFF OFF ON Waiting for the ENBC card to initialize communications.

Page 31: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 29

3. Us the Maintenance Menu > Card Maintenance to reset the specific T1 causing the alarm.

4. Shut down the digital switch and reseat the T1 cable on the backplane of the card cage.

5. Restart the system. If the problem persists, go to the next step.

6. Request the T1 provider to reset the T1 and check cable connections. If the problem persists, go to the next step.

7. Try reconnecting the T1 cable to a different slot. If the trouble follows the cable, work with the far end of the T1 to resolve. If the trouble remains with the slot, replace the QT1 or the QT1 trunk adapter or both cards if necessary.

Quad T1 primary rate interface card (QT1-PRI)

The QT1-PRI card uses the same 24 channel format as the QT1 with one voice channel for use as a D-channel for signaling. This provides the 23B+D service that consists of 23 Bearer, or voice channels, and one Data, or signaling channel. This card is NFAS compatible.

LED indicators

Red Yellow Green Status

ON ON ON Self-test in progress.

FLASH FL:ASH FLASH QT1.dwn file being downloaded.

OFF OFF OFF Normal operation

ON OFF OFF Carrier loss, OOF detected.

OFF ON OFF Remote alarm detected.

OFF OFF ON Waiting for the ENBC card to initialize communications.

Page 32: PC4 Troubleshooting Main

30 Maintenance and Troubleshooting Guide March 2008

Solutions

Follow these steps to resolve issues:

1. Check the system log for error messages related to the slots containing the QT1-PRI card.

2. Check Maintenance Menu > Card Alarm for alarms.

3. Us the Maintenance Menu > Card Maintenance to reset the specific T1 causing the alarm.

4. Shut down the digital switch and reseat the T1 cable on the backplane of the card cage.

5. Restart the system. If the problem persists, go to the next step.

6. Request the T1 provider to reset the T1 and check cable connections. If the problem persists, go to the next step.

7. Try reconnecting the T1 cable to a different slot. If the trouble follows the cable, work with the far end of the T1 to resolve. If the trouble remains with the slot, replace the QT1-PRI or the trunk adapter or both cards if necessary.

Quad E1-Channel Associated Signaling 120 Ohm (QE1-CAS 120)

The QE1-CAS 120 card uses the E1-CAS digital transmission that is defined in ITU G.703 and Q.421. Each digital span includes four wires, two for the receive direction and two for the transmit direction. It uses 32 time slots to carry one framing channel, one signaling channel, and 30 PCM voice channels. The eight bits in the signaling channel are shared over time to provide signaling bits for each voice channel to indicate things like off-hook, answer, clearing, and more.

The 120 Ohm designation signifies that the wire interface for these spans is twisted pair cabling, which has an approximate impedance of 120 ohms at 2 MHz.

LED indicators

Red Yellow Green Status

ON ON ON Self-test in progress.

FLASH FL:ASH FLASH QE1.dwn file being downloaded.

Page 33: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 31

Solutions

Follow these steps to resolve issues:

1. Check the system log for error messages related to the slots containing the QE1-CAS 120 card.

2. Check Maintenance Menu > Card Alarm for alarms.

3. Us the Maintenance Menu > Card Maintenance to reset the specific E1 causing the alarm.

4. Shut down the digital switch and reseat the E1 cable on the backplane of the card cage.

5. Restart the system. If the problem persists, go to the next step.

6. Request the E1 provider to reset the E1 and check cable connections. If the problem persists, go to the next step.

7. Try reconnecting the E1 cable to a different slot. If the trouble follows the cable, work with the far end of the E1 to resolve. If the trouble remains with the slot, replace the QE1-CAS 120 or the trunk adapter or both cards if necessary.

Quad E1Primary Rate ISDN 120 Ohm (QE1-PRI 120)

The QE1-PRI 120 card uses the E1-PRI digital transmission which has the same physical and electrical facilities as E1-CAS, with the E1-CAS signaling channel replaced with a D-channel in the ISDN version. Otherwise the spans look the same. This scheme gives 30B+D capabilities, for an increase of 7 voice channels over the T1-PRI. The QE1-PRI 120 card uses the 120 ohm connection method on twisted pair cabling.

OFF OFF OFF Normal operation

ON OFF OFF Carrier loss, OOF detected.

OFF ON OFF Remote alarm detected.

OFF OFF ON Waiting for the ENBC card to initialize communications.

Page 34: PC4 Troubleshooting Main

32 Maintenance and Troubleshooting Guide March 2008

LED indicators

Solutions

Follow these steps to resolve issues:

1. Check the system log for error messages related to the slots containing the QE1-PRI 120 card.

2. Check Maintenance Menu > Card Alarm for alarms.

3. Us the Maintenance Menu > Card Maintenance to reset the specific E1 causing the alarm.

4. Shut down the digital switch and reseat the E1 cable on the backplane of the card cage.

5. Restart the system. If the problem persists, go to the next step.

6. Request the E1 provider to reset the E1 and check cable connections. If the problem persists, go to the next step.

7. Try reconnecting the E1 cable to a different slot. If the trouble follows the cable, work with the far end of the E1 to resolve. If the trouble remains with the slot, replace the QE1-PRI 120120 or the trunk adapter or both cards if necessary.

Red Yellow Green Status

ON ON ON Self-test in progress.

FLASH FL:ASH FLASH qe1pri.dwn file being downloaded.

OFF OFF OFF Normal operation

ON OFF OFF Carrier loss, OOF detected.

OFF ON OFF Remote alarm detected.

OFF OFF ON Waiting for the ENBC card to initialize communications.

Page 35: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 33

Quad E1-Channel Associated Signaling 75 Ohm (QE1-CAS 75)

The 75 ohm version of the QE1-CAS card is similar to the 120 ohm version. However, the 75 ohm version uses two coaxial cables instead of two pairs of twisted wires. The impedance of the interface is 75 ohms at 2 MHz.

LED indicators

Solutions

Follow these steps to resolve issues:

1. Check the system log for error messages related to the slots containing the QE1-CAS 75 card.

2. Check Maintenance Menu > Card Alarm for alarms.

3. Us the Maintenance Menu > Card Maintenance to reset the specific E1 causing the alarm.

4. Shut down the digital switch and reseat the E1 cable on the backplane of the card cage.

5. Restart the system. If the problem persists, go to the next step.

Red Yellow Green Status

ON ON ON Self-test in progress.

FLASH FL:ASH FLASH QE1.dwn file being downloaded.

OFF OFF OFF Normal operation

ON OFF OFF Carrier loss, OOF detected.

OFF ON OFF Remote alarm detected.

OFF OFF ON Waiting for the ENBC card to initialize communications.

Page 36: PC4 Troubleshooting Main

34 Maintenance and Troubleshooting Guide March 2008

6. Request the E1 provider to reset the E1 and check cable connections. If the problem persists, go to the next step.

7. Try reconnecting the E1 cable to a different slot. If the trouble follows the cable, work with the far end of the E1 to resolve. If the trouble remains with the slot, replace the QE1-CAS 75 or the trunk adapter or both cards if necessary.

Quad E1- Primary Rate ISDN 75 Ohm (QE1-PRI 75)

The 75 ohm version of the QE1-PRI card is similar to the 120 ohm version. However, the 75 ohm version uses two coaxial cables, one for transmit and one for receive, instead of two pairs of twisted wires. The impedance of the interface is 75 ohms at 2 MHz.

LED indicators

Solutions

Follow these steps to resolve issues:

1. Check the system log for error messages related to the slots containing the QE1-PRI 75 card.

Red Yellow Green Status

ON ON ON Self-test in progress.

FLASH FLASH FLASH QE1.dwn file being downloaded.

OFF OFF OFF Normal operation

ON OFF OFF Carrier loss, OOF detected.

OFF ON OFF Remote alarm detected.

OFF OFF ON Waiting for the ENBC card to initialize communications.

Page 37: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 35

2. Check Maintenance Menu > Card Alarm for alarms.

3. Us the Maintenance Menu > Card Maintenance to reset the specific E1 causing the alarm.

4. Shut down the digital switch and reseat the E1 cable on the backplane of the card cage.

5. Restart the system. If the problem persists, go to the next step.

6. Request the E1 provider to reset the E1 and check cable connections. If the problem persists, go to the next step.

7. Try reconnecting the E1 cable to a different slot. If the trouble follows the cable, work with the far end of the E1 to resolve. If the trouble remains with the slot, replace the QE1-PRI 75 or the trunk adapter or both cards if necessary.

Digital Signal Processor -2 (DSP2)

The Digital Signal Processor 2 (DSP2) card accepts up to four of these DSP applications:

● Call Analysis replaces the Enhanced Call Progress Analyzer (ECPA) and provides real time analysis of a dialed call.

● Conference replaces the Enhanced Conference Card (ECC) and has the capability to conference up to 128 ports together in various combinations.

● Dual tone multifrequency (DTMF) Receiver replaces the Enhanced DTMF Receiver Card (EDRC) and provides the capability to receive DTMF tones.

Page 38: PC4 Troubleshooting Main

36 Maintenance and Troubleshooting Guide March 2008

● Tone Generator replaces the Enhanced Digital Tone Generator (EDTG) and provides tone outputs for DTMF and MF dialing and other maintenance and switch usage.

● MFCR2 Transceiver replaces the Enhanced Multi-Frequency Compelled R2 Transceiver (EMFCR2) and produces and receives R2 dialing tones on the network or PBX.

● Digital Dialer replaces the Digital Dialer Card (DDC) and provides 192 DTMF/MF dialing ports.

This card comes in two configurations:

● DSP2-41 - Has 4 DSP devices and one bank of external RAM installed in each section.

● DSP2-11 - Has 1 DSP device and one bank of external RAM installed.

The applications that run on the DSP2 card are configured completely within the Digital Switch menu screens on the Switch Console.

LED indicators

Note that the 331 HB and DSP HB are not on the front panel. SB stands for slow blink, MB for medium blink, and FB for fast blink.

331 HBGreen

DSP HBGreen

Red Yellow Green Status

ON ON ON ON ON Reset in progress.

SB SB OFF OFF OFF Normal operation

ON MB ON ON ON JTAG download

SB OFF OFF OFF ON Internal memory test

SB FB OFF OFF OFF External memory test

SB SB OFF OFF ON Waiting for download

SB SB FB FB FB Card download

Page 39: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 37

LED Error conditions

In all cases where an error occurs, remove the card and return it to customer support with details on the error that occurred.

Internet Protocol Telephony Card (IPTC)

The IPTC is still in development. This card will provide approximately 100 IP Telephony voice connections, Voice over Internet Protocol (VoIP). This card is being developed to meet Avaya's commitment to a future IP connected world. It is based on the DSP2 card design and utilizes many of the same circuits. At this time, only H.323 signaling is supported, but SIP is on the list for the future.

331 HB Error

Blink 1 External RAM Bank 0 failure

Blink 2 External RAM Bank 1 failure

Blink 3 External RAM Bank 2 failure

Blink 4 External RAM Bank 3 failure

Blink 5 Internal Block 0 failure

Blink 6 Internal Block 1 failure

Blink 7 Convergence error

Blink 8 External Bank 0 flag missing

Blink 9 Dual port RAM failure

Blink 10 Unexpected interrupt

Page 40: PC4 Troubleshooting Main

38 Maintenance and Troubleshooting Guide March 2008

LED indicators

Red Yellow Green Status

ON ON ON Self-test in progress.

FLASH FL:ASH FLASH IPTC.dwn file being downloaded.

OFF OFF OFF Normal operation

OFF OFF ON Waiting for the ENBC card to initialize communications.

Page 41: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 39

Software Maintenance

This section contains the following topics:

● Understanding backup and restore operations on page 39

● Using backup and restore commands on page 40

Understanding backup and restore operationsFor local backup and restoration capabilities, you must configure an external DDS tape drive, a third party host, or use the DVD Writer. For more information, see Planning and Prerequisites for Avaya Proactive Contact and Installing and Configuring Avaya Proactive Contact.

Back up the following files on a regular basis:

● outbound calling lists

● inbound calling results

● call activity statistics

● system configuration files

● system data / statistics file

To prevent data loss, Avaya recommends that you follow these guidelines:

● Keep a minimum of two sets of backup. In each set, keep one backup for each day.

● Store one backup set away from your site.

● Store backed up data in a controlled environment. Optimal tape storage environment is 50% relative humidity at 22° C.

● Replace each DDS tape after 100 uses, approximately two years.

● Clean the tape drive monthly using a cleaning tape.

● Replace cleaning tapes after 25 uses.

The standard backup medium is a 4.3 GB DVD. You can also use a 4mm, 90-meter, 2.2 GB digital data storage (DDS) tape or a 9-track tape if you are planning to use a tape drive.

Page 42: PC4 Troubleshooting Main

40 Maintenance and Troubleshooting Guide March 2008

Using backup and restore commandsThis section contains the following topics:

● Monitor the DAT drive status on page 40

● Back up the complete system on page 41

● Back up the system and calling lists on page 42

● Back up Avaya Proactive Contact system files on page 42

● Back up system configuration files on page 43

● Back up system data/stat files on page 44

● Restore all the data on page 44

● Restore a file from archive on page 45

● List/Verify a file in archive on page 46

● List/Verify archive contents on page 46

● List archive volume information on page 47

● Back up all calling lists on page 47

● Back up a specific calling list on page 48

● Restore all calling lists on page 48

● Restore a specific calling list on page 49

● Back up a database on page 49

● Restore a database on page 50

Monitor the DAT drive statusYou can monitor the tape drive status during backup and restore procedures. There are two LEDs on the tape drive. The LED on the left is the cassette LED. The LED on the right is the drive LED. When the system uses the tape drive, both lights flash in different color combinations.

Cassette LED Color

Drive LED Color Status

Flashing green Flashing green Write-enabled tape loading or unloading.

Green Green Write-enabled tape loaded and online.

Page 43: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 41

Various options for Backup and RestoreYou can use the following for backing up and restoring information on Proactive Contact:

● DAT 72 USB External Tape Drive

● DVD Writable

● A Third Party Host

Back up the complete systemYou can back up the entire root file system contents, including the operating system and the Avaya Proactive Contact system files.

To back up the system:

1. Locate the DVD drive / tape drive in the system cabinet. Insert a new DVD / DDS tape in the drive.

2. From the Administrator Main Menu, type 3 and press enter to select Back up, restore and verify option.

3. From the Back Up and Restore Menu, type 2 and press enter to select Local backup /restore/verify option.

4. Type 2 and press enter to select Back up complete system.

Flashing amber Flashing green Write-protected tape loading or unloading.

Amber Green Write-protected tape loaded and online.

Green Flashing green and amber

Media wear. Replace tape or clean tape drive.

Amber Amber High room humidity. Tape cannot load or unload.

Flashing amber Flashing amber Successful power-on self-test.

Flashing amber Amber Unsuccessful power-on self-test.

Cassette LED Color

Drive LED Color Status

Page 44: PC4 Troubleshooting Main

42 Maintenance and Troubleshooting Guide March 2008

5. Choose backup media type.

6. After the backup process is completed, store the backup in antistatic environment at the proper temperature and humidity.

Back up the system and calling listsYou can back up the system and all calling lists.

To back up the system and calling lists:

1. Locate the DVD drive / tape drive in the system cabinet. Insert a new DVD / DDS tape in the drive.

2. From the Administrator Main Menu, type 3 and press enter to select Back up, restore and verify option.

3. From the Back Up and Restore Menu, type 2 and press enter to select Local backup /restore/verify option.

4. Type 3 and press enter to select Back up system and calling list.

5. The system will ask you the following "Back up system and calling lists - Are you sure?". Type Y for yes and N for no.

6. From ADDITIONAL ENTRY for Back up system and calling lists menu, type I for Incremental backup or F for Full backup

7. The system will ask you the following "Are above entries correct?". Type Y for yes and N for no.

8. Choose the backup media type.

9. Follow the onscreen instructions.

10. After the backup process is completed, store the backup in antistatic environment at the proper temperature and humidity.

Back up Avaya Proactive Contact system filesYou can back up the entire system excluding the calling lists (specifically, excluding all data in the /opt/avaya/pds/xfer/clist directory).

To back up the system files:

1. Locate the DVD drive / tape drive in the system cabinet. Insert a new DVD / DDS tape in the drive.

2. From the Administrator Main Menu, type 3 and press enter to select Back up, restore and verify option.

Page 45: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 43

3. From the Back Up and Restore Menu, type 2 and press enter to select Local backup /restore/verify option.

4. Type 4 and press enter to select Back up system only.

5. The system will ask you the following "Back up system only - Are you sure?". Type Y for yes and N for no.

6. From ADDITIONAL ENTRY for Back up system only menu, type I for Incremental backup or F for Full backup

7. The system will ask you the following "Are above entries correct?". Type Y for yes and N for no.

8. Choose the backup media type.

9. Follow the onscreen instructions.

10. After the backup process is completed, store the backup in antistatic environment at the proper temperature and humidity.

Back up system configuration filesYou can back up all the system configuration files (all files needed to customize a newly installed system to the customer's specifications).

To back up system configuration files:

1. Locate the DVD drive / tape drive in the system cabinet. Insert a new DVD / DDS tape in the drive.

2. From the Administrator Main Menu, type 3 and press enter to select Back up, restore and verify option.

3. From the Back Up and Restore Menu, type 2 and press enter to select Local backup /restore/verify option.

4. Type 5 and press enter to select Back up system configuration files.

5. The system will ask you the following "Back up system configuration files - Are you sure?". Type Y for yes and N for no.

6. From ADDITIONAL ENTRY for Back up system configuration files menu, type I for Incremental backup or F for Full backup

7. The system will ask you the following "Are above entries correct?". Type Y for yes and N for no.

8. Choose the backup media type.

9. Follow the onscreen instructions.

10. After the backup process is completed, store the backup in antistatic environment at the proper temperature and humidity.

Page 46: PC4 Troubleshooting Main

44 Maintenance and Troubleshooting Guide March 2008

Back up system data/stat filesYou can back up all data files needed to run reports via the PC Analysis tools. Specifically, all files matching the following patterns:

● /opt/avaya/pds/lists/*.stat

● /opt/avaya/pds/lists/history/*.hist

● /opt/avaya/pds/account/*

If you select any of the above choices, you will next be asked if you want the backup to be incremental or full. In the case of a full back up, the system backs up all files in the specified category. In the case of an incremental back up, the system backs up a file only if it has changed since it was last backed up as part of any full back up.

To back up system data/stat files:

1. Locate the DVD drive / tape drive in the system cabinet. Insert a new DVD / DDS tape in the drive.

2. From the Administrator Main Menu, type 3 and press enter to select Back up, restore and verify option.

3. From the Back Up and Restore Menu, type 2 and press enter to select Local backup /restore/verify option.

4. Type 6 and press enter to select Back up system data/stat files.

5. The system will ask you the following " Back up system data/stat files - Are you sure?". Type Y for yes and N for no.

6. From ADDITIONAL ENTRY for Back up system data/stat files menu, type I for Incremental backup or F for Full backup

7. The system will ask you the following "Are above entries correct?". Type Y for yes and N for no.

8. Choose the backup media type.

9. Follow the onscreen instructions.

10. After the backup process is completed, store the backup in antistatic environment at the proper temperature and humidity.

Restore all the dataYou can restore all files from any backup tape created using the backup menu commands (or any file created with the UNIX fbackup utility).

Page 47: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 45

To restore all files from a tape:

1. From the Administrator Main Menu, type 3 and press enter to select Back up, restore and verify option.

2. From the Back Up and Restore Menu, type 2 and press enter to select Local backup /restore/verify option.

3. Type 7 and press enter to select Restore all.

4. The system will ask you the following " Restore all - Are you sure?". Type Y for yes and N for no.

5. Choose the restore media type.

6. Follow the onscreen instructions.

7. After the restore process is completed, store the backup in antistatic environment at the proper temperature and humidity.

! Important:Important: You cannot restore files from backup tapes created on earlier versions of the

system.

Restore a file from archiveTo restore a file from tape:

1. From the Administrator Main Menu, type 3 and press enter to select Back up, restore and verify option.

2. From the Back Up and Restore Menu, type 2 and press enter to select Local backup /restore/verify option.

3. Type 8 and press enter to select Restore a file.

4. Enter the full filename in the "ADDITIONAL ENTRY for Restore a file" menu.

5. The system will ask you "Are above entries correct?". Type Y for yes and N for no.

6. Choose the backup media type.

7. Locate the DVD drive / tape drive in the system cabinet. Insert the DVD / DDS tape with the existing backup files in the drive.

8. Follow the instructions on the screen.

Page 48: PC4 Troubleshooting Main

46 Maintenance and Troubleshooting Guide March 2008

List/Verify a file in archiveTo verify a backup file in archive:

1. From the Administrator Main Menu, type 3 and press enter to select Back up, restore and verify option.

2. From the Back Up and Restore Menu, type 2 and press enter to select Local backup /restore/verify option.

3. Type 9 and press enter to select List/Verify a file in archive.

4. The system will prompt the following " List/Verify a file in archive - Are you sure?". Type Y for yes and N for no

5. Enter the full filename in the "ADDITIONAL ENTRY for List/Verify a file in archive" menu.

6. The system will ask you "Are above entries correct?". Type Y for yes and N for no.

7. Choose the backup media type.

8. Locate the DVD drive / tape drive in the system cabinet. Insert the DVD / DDS tape with the existing backup files in the drive.

The system displays the byte count, date, size, and file names on the screen during the tape verification process.

9. After verifying the tape, follow the unloading instructions on the screen. Type C to return to the previous menu.

List/Verify archive contentsTo verify a backup file on a tape:

1. From the Administrator Main Menu, type 3 and press enter to select Back up, restore and verify option.

2. From the Back Up and Restore Menu, type 2 and press enter to select Local backup /restore/verify option.

3. Type 10 and press enter to select List/Verify List/Verify archive contents.

4. The system will prompt the following "List/Verify archive contents - Are you sure?". Type Y for yes and N for no

5. Choose the backup media type.

The system displays the byte count, date, size, and file names on the screen during the tape verification process.

6. After verifying the archive contents, follow the unloading instructions on the screen.

Page 49: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 47

List archive volume informationYou can view the creation information on a backup tape.

To view backup volume information:

1. From the Administrator Main Menu, type 3 and press enter to select Back up, restore and verify option.

2. From the Back Up and Restore Menu, type 2 and press enter to select Local backup /restore/verify option.

3. Type 11 and press enter to select List archive volume information.

4. The system will prompt the following "List archive volume information - Are you sure?". Type Y for yes and N for no

5. Choose the backup media type.

6. The system displays the volume information.

7. After verifying the archive volume, follow the unloading instructions on the screen.

! Important:Important: You cannot restore files from backup tapes created on earlier versions of the

system.

Back up all calling listsYou can back up all calling lists currently on the system. Specifically, all files in the directory /opt/avaya/pds/xfer/clist.

To back up a calling list:

1. Locate the DVD drive / tape drive in the system cabinet. Insert a new DVD / DDS tape in the drive.

2. From the Administrator Main Menu, type 3 and press enter to select Back up, restore and verify option.

3. From the Back Up and Restore Menu, type 3 and press enter to select Local backup up/restore calling lists option.

4. Type 2 and press enter to select Back up all calling lists command.

5. The system will ask you the following "Back up all calling lists - Are you sure?". Type Y for yes and N for no.

6. Choose the backup media type.

7. Follow the onscreen instructions.

Page 50: PC4 Troubleshooting Main

48 Maintenance and Troubleshooting Guide March 2008

8. After the backup process is completed, store the backup in antistatic environment at the proper temperature and humidity.

Back up a specific calling listYou can choose a specific calling list from the Item List on the right side of the screen. View additional files by scrolling down the list in the standard way.

Note:Note: The files are listed in alphabetical order, and file names with more than 10

characters are truncated in the displayed list. If a truncated file name is selected, however, the correct file is selected and backed up.

To back up a specific calling list:

1. Locate the DVD drive / tape drive in the system cabinet. Insert a new DVD / DDS tape in the drive.

2. From the Administrator Main Menu, type 3 and press enter to select Back up, restore and verify option.

3. From the Back Up and Restore Menu, type 3 and press enter to select Local backup up/restore calling lists option.

4. Type 3 and press enter to execute Back up a specific calling list command.

5. Type the item number of the calling list on the right of the command menu that needs to be backed up and press enter.

6. The system will ask you the following "Back up a specific calling list on item <listname> - Are you sure?". Type Y for yes and N for no.

7. Choose the backup media type.

8. Follow the onscreen instructions.

9. After the backup process is completed, store the backup in antistatic environment at the proper temperature and humidity.

Restore all calling listsTo restore all callings lists from a backup tape:

1. Locate the DVD drive / tape drive in the system cabinet. Insert a new DVD / DDS tape in the drive.

2. From the Administrator Main Menu, type 3 and press enter to select Back up, restore and verify option.

Page 51: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 49

3. From the Back Up and Restore Menu, type 3 and press enter to select Local backup up/restore calling lists option.

4. Type 4 and press enter to execute Restore all calling lists command.

5. The system will ask you the following "Restore all calling lists - Are you sure?". Type Y for yes and N for no.

6. Choose the backup media type.

7. Follow the onscreen instructions.

Restore a specific calling listYou can restore a single calling list file from tape. This choice is similar to the previous choice except that the file to be restored must appear in the Item List on the right hand side of the menu. This command will overwrite the list of the same name currently on the system.

To restore a specific calling list from tape:

1. Locate the DVD drive / tape drive in the system cabinet. Insert a new DVD / DDS tape in the drive.

2. From the Administrator Main Menu, type 3 and press enter to select Back up, restore and verify option.

3. From the Back Up and Restore Menu, type 3 and press enter to select Local backup up/restore calling lists option.

4. Type 5 and press enter to execute Restore a specific calling list command.

5. Type the item number of the calling list on the right of the command menu that needs to be restored and press enter.

6. The system will ask you the following "Restore a specific calling list on item <listname> - Are you sure?". Type Y for yes and N for no.

7. Choose the restore media type.

8. Follow onscreen instructions.

Back up a databaseYou can back up all database data files and database system files, specifically, all files in the directory /opt/oracle/oradata.

Page 52: PC4 Troubleshooting Main

50 Maintenance and Troubleshooting Guide March 2008

! Important:Important: Avaya strongly recommends that you execute a database backup when no other

activities (such as dialing) are in progress. During this operation, the control and monitor functions are unavailable. This operation is also time and resource intensive, which can slow system activity.

To back up a database:

1. Locate the DVD drive / tape drive in the system cabinet. Insert a new DVD / DDS tape in the drive.

2. From the Administrator Main Menu, type 3 and press enter to select Back up, restore and verify option.

3. From the Back Up and Restore Menu, type 4 and press enter to select Local backup up/restore database option.

4. Type 3 and press enter to execute Back up a specific calling list command.

5. Type 2 and press enter to select Back up the database option.

6. The system will ask you the following " Back up the database - Are you sure?". Type Y for yes and N for no.

7. Choose the backup media type.

8. Follow the onscreen instructions.

9. After the backup process is completed, store the backup in antistatic environment at the proper temperature and humidity.

Restore a databaseYou can restore database data files and database system files, specifically, all files in the directory /opt/oracle/oradata.

! Important:Important: Avaya strongly recommends that you execute a database restore when no other

activities (such as dialing) are in progress. During this operation, the control and monitor functions are unavailable. This operation is also time and resource intensive, which can slow system activity.

To restore a database:

1. Locate the DVD drive / tape drive in the system cabinet. Insert the backup DVD / DDS tape in the drive.

2. From the Administrator Main Menu, type 3 and press enter to select Back up, restore and verify option.

Page 53: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 51

3. From the Back Up and Restore Menu, type 4 and press enter to select Local backup up/restore database option.

4. Type 3 and press enter to execute Restore the database command.

5. The system will ask you the following " Restore the database - Are you sure?". Type Y for yes and N for no.

6. Choose the backup media type.

7. Follow the onscreen instructions.

Page 54: PC4 Troubleshooting Main

52 Maintenance and Troubleshooting Guide March 2008

Page 55: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 53

Error messages and message type

Message Type Error Number

Error Message

GLOB E00500 %s - Caught signal %d (%s)

GLOB E00501 %s - Caught signal %d (%s) and terminated

GLOB E00502 %s - Failed to allocate Memory

GLOB E00503 %s - Pattern error: %s

GLOB E00504 %s - Bad argument

GLOB E00505 %s - Invalid time format

GLOB E00506 %s - Invalid date format

GLOB E00507 %s - Failed to retrieve environmental variable %s

GLOB E00508 %s - Entry %s missing/invalid in master.cfg file

GLOB E00509 %s - Entry %s missing/invalid in %s file

GLOB E00510 %s - Entry %s is incompatible in length

GLOB E00511 %s - Failed to process file %s

GLOB E00512 %s - File name %s too long

GLOB E00513 %s - Invalid file name %s

GLOB E00514 %s - File name %s already exist

GLOB E00515 %s - Failed to open file %s

GLOB E00516 %s - Failed to close file %s

GLOB E00517 %s - Failed to create file %s

GLOB E00518 %s - Failed to read from file %s

GLOB E00519 %s - v_dialer\dialer\src\dbconst\readtape.c %s

GLOB E00520 %s - Failed to lock file %s

GLOB E00521 %s - Failed to unlock file %s

GLOB E00522 %s - Failed to attach to shm, err=%d, id=%d

Page 56: PC4 Troubleshooting Main

54 Maintenance and Troubleshooting Guide March 2008

GLOB E00523 %s - Failed to detach from shm, err=%d, id=%d

GLOB E00524 %s - Failed to remove shm, err=%d, id=%d

GLOB E00525 %s - Failed to get msgq, err=%d, id=%d

GLOB E00526 %s - Failed to send msg, err=%d, id=%d

GLOB E00527 %s - Failed to recv msg, err=%d, id=%d

GLOB E00528 %s - Failed to remove msgq, err=%d, id=%d

GLOB E00529 %s - Failed to invoke function %s, err=%d

GLOB E00530 %s - Failed to open calling list %s

GLOB E00531 %s - Failed to read calling list definition %s

GLOB E00532 Field %s not defined in calling list %s

GLOB E00533 Field %s has incorrect length

GLOB E00534 Not a calling list

GLOB E00535 %s - No space on file system

GLOB E00536 %s - Failed to initialize keyboard

GLOB E00537 %s - Failed to initialize screen environment

GLOB E00538 %s - Failed to setup command keys

GLOB E00539 %s - Failed to create %s window

GLOB E00540 %s - Failed to create window pointer

GLOB E00541 %s - Failed to open keys file %s

GLOB E00542 %s - Field %s not defined in calling list %s

GLOB E00543 Field %s not defined in calling list %s (WARNING)

GLOB E00544 %s - Invalid Pattern '%s'

GLOB E00545 %s:fail to send %s to %s

GLOB E00546 Failed to create directory '%s' -- errno %d: %s

GLOB E00547 Non-directory '%s' in directory path '%s'

GLOB E00548 Missing/invalid entry for %s in file %s

GLOB E00549 %s operation failed, file '%s' -- errno %d: %s

GLOB E00550 Invalid entry for %s in file %s near '%s'

GLOB E00551 Assertion failed (expression false), aborting

Page 57: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 55

GLOB E00552 Failed to open directory %d

GLOB E00553 File '%s' does not exist

GLOB E00554 %s operation failed

GLOB E00555 %s - %s

GLOB E00556 File '%s' exists, but is not readable by user %s

GLOB E00557 File '%s' exists, but is not writable by user %s

LIBDSI E10000 Exceeded max number (%d) of associate calling lists

LIBDSI E10001 Not an associate List

LIBDSI E10002 Not an associate select file: %s

LIBDSI E10003 Associate list name missing

LIBDSI E10004 Associate list name not in assoc.cfg file

LIBDSI E10005 %s - Creation time for %s is incorrect

LIBDSI E10006 Failed to change master clist: %s

LIBDSI E10007 Invalid logical connector at line %d

LIBDSI E10008 Missing field name or value at line %d

LIBDSI E10009 Group may not begin with no selection

LIBDSI E10010 Gap found between select fields within group

LIBDSI E10011 Field name not found at line %d

LIBDSI E10012 Pattern error at line %d: %s

LIBDSI E10013 can't find service entry in /etc/services, errno=%d

LIBDSI E10014 socket call failed, errno=%d

LIBDSI E10015 Unable to bind to local address, errno=%d

LIBDSI E10016 Unable to setup listen on socket, errno=%d

LIBDSI E10017 Unable to accept connection on socket, errno=%d

LIBDSI E10018 Unable to connect to socket, errno=%d

LIBDSI E10019 Unable to send data to socket %d, errno=%d

LIBDSI E10200 Unequal phone number field lengths in file %s

LIBDSI E10201 Invalid line selection

LIBDSI E10600 Failed to allocate memory

Page 58: PC4 Troubleshooting Main

56 Maintenance and Troubleshooting Guide March 2008

LIBDSI E10601 Invalid usage

LIBDSI E10602 Invalid job name

LIBDSI E10603 Failed to open edit file

LIBDSI E10604 No editable line in job file

LIBDSI E10605 Job file in use

LIBDSI E10606 Wrong job for verification editor

LIBDSI E10607 Required field not filled in

LIBDSI E10608 HUNTGRP format error

LIBDSI E10609 No HUNTGRP setting

LIBDSI E10610 No Inbound jobs allowed

LIBDSI E10611 Invalid number of reserve inbound line

LIBDSI E10612 Script label for answer missing/invalid

LIBDSI E10613 Failed to read inbound calling list

LIBDSI E10614 Failed to read associated calling list

LIBDSI E10615 Failed to read inbound screen file

LIBDSI E10616 Failed to read inbound screen map

LIBDSI E10617 Failed to read multiple screen

LIBDSI E10618 Failed to read multiple screen map

LIBDSI E10619 Failed to read associated screen

LIBDSI E10620 Failed to read associated screen map

LIBDSI E10621 Failed to read outbound list

LIBDSI E10622 Failed to read outbound screen

LIBDSI E10623 Failed to read outbound map

LIBDSI E10624 Failed to read calling script

LIBDSI E10625 Failed to read key file

LIBDSI E10626 Failed to match associated field

LIBDSI E10627 Failed to process data transfer field

LIBDSI E10628 Failed to process associated selection

LIBDSI E10629 Selection list not available for use

Page 59: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 57

LIBDSI E10630 STATUSFLAG field missing

LIBDSI E10631 CODE field missing

LIBDSI E10632 DTE field missing

LIBDSI E10633 TME field missing

LIBDSI E10634 Invalid start or stop time format

LIBDSI E10635 Invalid Hit Rate

LIBDSI E10636 Invalid Expert Calling Ratio

LIBDSI E10637 Invalid call completion code for Quota Value

LIBDSI E10638 Invalid quota value

LIBDSI E10639 Invalid paired phone count/type

LIBDSI E10640 Invalid number of phone lines

LIBDSI E10641 Odd number of phone lines specified

LIBDSI E10642 Invalid phone type specified

LIBDSI E10643 Failed to initialize call strategy

LIBDSI E10644 Failed to read call strategy

LIBDSI E10645 Failed to verify call strategy

LIBDSI E10646 The specified job already running

LIBDSI E10648 Non-OP completion code specified for Quota setting

LIBDSI E10649 Failed to find linked job file

LIBDSI E10650 Linking between virtual agent jobs and non-virtual jobs is not permitted

LIBDSI E10651 Sales verification job linking is not permitted

LIBDSI E10652 Job linking is not permitted

LIBDSI E10653 Invalid call completion code for TRANSTAT

LIBDSI E10654 Selection list for job not found

LIBDSI E10655 No verification selection list ready for job

LIBDSI E10656 Selection list not created with this calling list

LIBDSI E10657 missing or invalid script label for call

LIBDSI E10658 Failed to open script file for IVR ID

Page 60: PC4 Troubleshooting Main

58 Maintenance and Troubleshooting Guide March 2008

LIBDSI E10659 IVR script name not specified; required if IVR ID specified

LIBDSI E10660 Unable to find script name in script file for IVR ID

LIBDSI E10661 remote list use not permitted

LIBDSI E10662 Sales verification or managed dialing must have agents

LIBDSI E10663 Managed dialing is not permitted with sales verification or inbound

LIBDSI E10664 Virtual agents cannot select a specific unit to log in to

LIBDSI E10665 Sales verification is not permitted with unit work lists

LIBDSI E10666 Sales verification is not permitted with inbound

LIBDSI E10667 Selecting unit to log in to is not permitted with inbound-only job

LIBDSI E10800 Not an error

LIBDSI E10801 Not an open file descriptor

LIBDSI E10802 Failed to open file

LIBDSI E10803 Failed to close file

LIBDSI E10804 Failed to lock record

LIBDSI E10805 Failed to unlock record

LIBDSI E10806 Failed to read file header

LIBDSI E10807 Failed to write file header

LIBDSI E10808 Failed to read record

LIBDSI E10809 Failed to write record

LIBDSI E10810 Failed to allocate CLSTAT table

LIBDSI E10811 Failed to get record totals

LIBDSI E10812 Invalid operation code

LIBDSI E10813 Failed to read file dictionary

LIBDSI E10814 Failed to write file dictionary

LIBDSI E10815 Failed to create file

LIBDSI E10816 Failed to access file

LIBDSI E10817 Unconverted to year 2000

Page 61: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 59

LIBDSI E10818 Unable to connect to listserver

LIBDSI E10819 XFD overflow (no XFD slots available)

LIBDSI E10820 Socket read error

LIBDSI E10821 Socket write error

LIBDSI E10822 Tag value incorrect - message alignment/framing error

LIBDSI E10823 File is open for reading only

LIBDSI E10824 File is open for writing only

LIBDSI E10850 Unable to open list '%s'

LIBDSI E10851 gethostbyname ('%s') failed

LIBDSI E10852 socket () failed

LIBDSI E10853 connect (conn_fd=%d) failed (is listserver running on host '%s'?)

LIBDSI E10854 _LcCreateXfd () failed

LIBDSI E10855 Write error -- wrote %d != expected %d

LIBDSI E10856 clstat (%d) failed

LIBDSI E10857 clrddict (%d) failed

LIBDSI E10858 getservbyname () failed -- using default LSERVPORT value (%d)

LIBDSI E10859 Bad file descriptor (%d)

LIBDSI E10860 File corruption or record size mismatch detected in calling list %s; fd=%d

LIBDSI E10861 Failed to remove file %s

LIBDSI E10900 Error: Value: <%s> not in master.cfg

LIBDSI E11000 Error: Recall attempt #%d (%s) can't be less than %d seconds

LIBDSI E11001 Recall (%s) attempts can't exceed %d

LIBDSI E11002 Invalid recall code: %s

LIBDSI E11003 Failed to determine max number of phones

LIBDSI E11004 Field value missing

LIBDSI E11005 Gap found between selection criteria lines

Page 62: PC4 Troubleshooting Main

60 Maintenance and Troubleshooting Guide March 2008

LIBDSI E11006 Extra ',' found

LIBDSI E11007 Invalid phone: %s

LIBDSI E11008 Invalid field name: %s

LIBDSI E11009 Invalid field value: %s

LIBDSI E11010 Invalid logical connector: %s

LIBDSI E11011 Invalid time zone letter: %c

LIBDSI E11012 Invalid completion code: %s

LIBDSI E11013 Invalid ring count: %s. Must be 1 - %d

LIBDSI E11014 Invalid call detection mode: %s

LIBDSI E11015 Error: Recall attempt #%d (%s) can't be less than %d minutes

LIBDSI E12000 File %s busy, try again later

LIBDSI E12100 Molocale - Unknown language name %s

LIBDSI E12101 Molocale - Failed to set locale %s errno=%d

LIBDSI E12150 PVRS - Failed to initialize %s

LIBDSI E12151 Hash key field is not defined in %s

LIBDSI E12152 No Previous Record

LIBDSI E12153 No More Record

LIBDSI E12154 Failed to Load Record

LIBDSI E12155 Record Currently In Use

LIBDSI E12156 No Record Found

LIBDSI E12200 Attempt to read hidfile without lock

LIBDSI E12201 Username %s exceeds %d characters in length

LIBDSI E12202 %s - Failed to lock file %s, errno(%d)

LIBDSI E12203 %s - Failed to unlock file %s, errno(%d)

LIBDSI E12400 tget returned errno %d raising signal %d

LIBDSI E12600 Calling list %s not in shared memory

LIBDSI E12601 Calling list field count not match

LIBDSI E12800 Failed to find screen %s

Page 63: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 61

LIBDSI E13000 IPC - Invalid input argument

LIBDSI E13001 IPC - Invalid ipc entry

LIBDSI E13002 IPC - Invalid ipc name

LIBDSI E13003 IPC - Invalid ipc number %d

LIBDSI E13004 Warning: CFRM message truncated

LIBDSI E13005 Timed out waiting for %s confirmation

LIBDSI E13006 Response message too long!

LIBDSI E13007 IPC - Failed to open opmon message queue

LIBDSI E13008 %s - Failed on semaphore removal, err=%d key=%d

LIBDSI E13009 %s - Failed on semaphore operation, err(%d) key = %d code = %d

LIBDSI E13010 %s - Accessing bad semaphore

LIBDSI E13011 %s - Failed to open semaphore, err(%d)

LIBDSI E13200 Headset value (%s, %d) out of bound

LIBDSI E13201 Headset %d not specified in %s file

LIBDSI E13400 Missing or invalid YES/NO field

LIBDSI E13401 Missing or invalid length

LIBDSI E13402 Missing prefix

LIBDSI E13403 Missing line type

LIBDSI E13404 Missing or invalid num of chars to strip

LIBDSI E13405 Missing prefix

LIBDSI E13406 Missing suffix

LIBDSI E13407 Duplicate ALL phone numbers specification

LIBDSI E13408 Phone number too long

LIBDSI E13409 Dial phone number too long

LIBDSI E13410 Missing std to dial phone number format

LIBDSI E13411 Invalid use of ALL phone numbers specification

LIBDSI E13412 Missing phone numbers

LIBDSI E13600 Report failed, system out of space

Page 64: PC4 Troubleshooting Main

62 Maintenance and Troubleshooting Guide March 2008

LIBDSI E13800 Invalid Headset Number (%d, %s)

LIBDSI E13801 Headset port no. %d out of range (1-%d)

LIBDSI E13802 Normal trunk port no. %d out of range (1-%d)

LIBDSI E13803 Invalid normal trunk equip no %d

LIBDSI E13804 Invalid normal trunk group no %d

LIBDSI E13805 Invalid transfer trunk group no %d

LIBDSI E13806 Failed to determine switch type

LIBDSI E13807 Failed to process line (%s)

LIBDSI E14000 Invalid timezone from GMT

LIBDSI E14001 Invalid time format at line %d in file %s

LIBDSI E14200 Missing delay specification

LIBDSI E14201 Missing or invalid low range

LIBDSI E14202 Invalid range character

LIBDSI E14203 Invalid high range

LIBDSI E14204 Invalid min delay

LIBDSI E14205 Missing completion code

LIBDSI E14206 Invalid completion code

LIBDSI E14207 Range does not come after previous range

LIBDSI E14208 Missing limit

LIBDSI E14209 Missing or invalid YES/NO field

LIBDSI E14210 Missing time zone specification for country %d

LIBDSI E14211 Missing or invalid time zone designation

LIBDSI E14212 Missing reject phone number pattern

LIBDSI E14213 Invalid reject phone number pattern

LIBDSI E14214 Duplicate country specified

LIBDSI E14215 Invalid answer delay time

LIBDSI E14216 Invalid DAA type

LIBDSI E14217 Invalid VM2 locale code

LIBDSI E14218 Invalid phone number length

Page 65: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 63

LIBDSI E14219 Rejected phone number (L%d)

LIBDSI E14220 Cannot find time zone for phone number

LIBDSI E14221 Invalid offhook retry delay

LIBDSI E14222 Invalid wait limit

LIBDSI E14400 Unknown select file %s

LIBDSI E14401 Unknown call completion code %s

LIBDSI E14402 No call completion codes selected

LIBDSI E14404 Missing field name or value at selection entry %d

LIBDSI E14405 Group may not begin with no selection

LIBDSI E14406 Gap found between select fields within group

LIBDSI E14407 Field name not found at selection entry %d

LIBDSI E14408 Pattern error at selection entry %d: %s

LIBDSI E14409 Unit Control - Invalid memory slot position

LIBDSI E14410 Unit Control - Failed to attach to data segment

LIBTCAP E14800 Termcap entry larger than buffer size

LIBTCAP E14801 Invalid termcap entry format

LIBTCAP E14802 'tc' entries exceed maximum allowed

LIBTCAP E14900 Terminal type %s not found in %s

LIBTCAP E14901 Default terminal type vt100 not found in %s

LIBUI E15200 No summary information available

LIBUI E15201 Invalid field type

LIBUI E15202 Invalid value, Must be %s

LIBUI E15203 Sorry, command not allowed inside editor

LIBUI E15204 %s - Menubar '%s' already exists.

LIBUI E15205 %s - Menubar '%s' not found.

LIBDSI E15400 %s:new_bsrch - Memory allocation (%d bytes) failed, loc %d

LIBDSI E15401 %s:new_bsrch - Bad value in new_bsrch (cl_name=%s cl_fd=%d, cl_keyname=%s init_type=%c pgmname=%s log_type=%d log_file=%s)

Page 66: PC4 Troubleshooting Main

64 Maintenance and Troubleshooting Guide March 2008

LIBDSI E15402 %s:new_bsrch - List recno %d locked-skipping;

LIBDSI E15403 %s:new_bsrch - List recno %d locked-aborting;

LIBDSI E15404 %s:new_bsrch - Bad calling list record parameter(s): keylen=%d reclen=%d nrecs=%d

LIBDSI E15420 %s:new_hsrch - Memory allocation (%d bytes) failed, loc %d

LIBDSI E15421 %s:new_hsrch - Unable to open hash file for %s

LIBDSI E15422 %s:new_hsrch - Missing key_field entry in hash file %s

LIBDSI E15424 %s:new_hsrch - Bad calling list record parameter(s): keylen=%d reclen=%d

LIBUTIL E16000 Missing or invalid country code

LIBUTIL E16100 Line too long

LIBUTIL E16101 Missing label

LIBUTIL E16102 Invalid label on line

LIBUTIL E16400 Range not properly nested

LIBUTIL E16401 Prefix falls on a range's border

LIBUTIL E16402 Range border falls on a prefix

LIBUTIL E16403 Range straddles previous range

LIBUTIL E16404 Prefix has the same value as a shorter prefix

LIBUTIL E16405 Same prefix is already specified

LIBUTIL E16406 Prefix has the same value as a longer prefix

LIBUTIL E16407 Missing prefix

LIBUTIL E16408 Invalid character in prefix

LIBUTIL E16409 Low range has fewer digits than high

LIBUTIL E16410 Range borders are out of order

LIBUTIL E16411 Bad argument in ptree

LIBUTIL E16500 Hash_get (%x, %s, %d) failed due to too many probes

LIBUTIL E16501 Requested size %d is too large -- Max hash table slots currently supported is %d

LIBUTIL E16600 Pattern '%s': Expected numerical lval, found '%s'

Page 67: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 65

LIBUTIL E16601 Pattern '%s': Expected numerical rval, found '%s'

LIBUTIL E16602 Pattern '%s': lval > rval (%g > %g)

LIBUTIL E16603 Pattern '%s': Expected hyphen, list separator, or end of pattern; found '%c'

LIBUTIL E16604 Pattern '%s': Unexpected end of numerical comparison

LIBUTIL E16605 Pattern '%s': Pattern too large

LIBUTIL E16606 Pattern '%s': Bad or missing DATEFORM parameter in master.cfg

LIBUTIL E16607 Pattern '%s': Bad format for date comparison

LIBUTIL E16608 Pattern '%s': Bad format for time comparison

LIBUTIL E16609 Pattern '%s': Bad format for relative date comparison

LIBUTIL E16610 Pattern '%s': Undefined backslashed character '%c'

LIBUTIL E16611 Pattern '%s': Unknown pattern type '%c' specified

LIBUTIL E16612 Pattern '%s': Failed to compile - use explicit pattern syntax for more details

LIBUTIL E16620 Unable to compare - previous pattern failed compilation - '%s'

LIBUTIL E16621 No compiled pattern to compare against for string '%s'

LIBUTIL E16800 Undefined func call: %s

LIBUTIL E16900 EXECPROG:Unexpected exit from waitpid() returning -1:errno=%d:pid=%d,child=%d

LIBUTIL E16901 EXECPROG:not returning from child process:pid=%d,child=%d

LIBUTIL E16902 EXECPROG:Exit(%d) wait(pid=%d)

LIBUTIL E16903 EXECPROG:Signal STOPPED wait(%d)

LIBUTIL E16904 EXECPROG:Sig_Exit:errno=%d:stat=0x%X:sig=%d:pid=%d,child=%d

LIBUTIL E16905 EXECPROG:Unexpected exit:errno=%d:stat_loc=0x%X:ret=%d:pid=%d,child=%d

LIBUTIL E16906 EXECPROG:Killed Child(%d):%s:

Page 68: PC4 Troubleshooting Main

66 Maintenance and Troubleshooting Guide March 2008

LIBUTIL E16907 EXECPROG:errno=%d:stat_loc=0x%X:ret=%d:pid=%d,child=%d

LIBUTIL E16908 PID(%d)Relaying signal=%d to child_pid=%d

LIBUTIL E16909 PID(%d)Ignoring signal=%d

LIBUTIL E16910 PID(%d)Activating Default Signal Handler

LIBUTIL E16911 PID(%d)Returning to exec_prog() Routine

LIBUTIL E16912 PID(%d)Calling Primary Signal Handler

LIBUTIL E17000 Error: system message '%s' not found

LIBUTIL E17001 Error: unable to open account file '%s'

LIBUTIL E17002 Error: unknown user '%s' specified.

LIBUTIL E17003 Error: unknown group '%s' specified.

LIBUTIL E17004 Error: chown ('%s', %d, %d) failed.

LIBUTIL E17005 Error: malloc ('%s') failed.

LIBUTIL E17100 getconfig: File '%s' is empty

LIBUTIL E17101 getconfig: Couldn't open file '%s'

LIBSWIF E18200 DISABLE INBOUND FAILED: (%d)%s

LIBSWIF E18201 ENABLE INBOUND FAILED: (%d)%s, ns=%x, rsb=%x, cause_IE=%x

LIBSWIF E18202 PORTER%d: switch out of sync

LIBSWIF E18203 Download of voice prompt file [%s] failed

LIBSWIF E18204 CALL FAILED ON %d: %s

LIBSWIF E18205 ORULE OVERRIDE DISABLE FAILED: %s

LIBSWIF E18206 HANGUP FAILED FOR %d: %s, ns=%x, rsb=%x, cause_IE=%x

LIBSWIF E18207 HANGUP FAILED: EQUIP= %d

LIBSWIF E18208 TRNSFR Transfer trunks not configured

LIBSWIF E18209 TRNSFR No transfer trunks available

LIBSWIF E18210 TRNSFR Transfer dial failed

LIBSWIF E18211 TRNSFR Transfer Failed

LIBSWIF E18212 TRNSFR Failed to put line on hold

Page 69: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 67

LIBSWIF E18213 RESPONSE FAILED: (%d)%s, ns=%x, rsb=%x, cause_IE=%x

LIBSWIF E18214 DOWNLOAD FAILED: file=%s, %s, ns=%x, rsb=%x, cause_IE=%x

LIBSWIF E18215 TRANSFER DIAL FAILED: (%d)%s, ns=%x, rsb=%x, cause_IE=%x

LIBSWIF E18216 TRANSFER CONFERENCE FAILED: (%d)%s, ns=%x

LIBSWIF E18217 Porter %d failed to busy-out line

LIBSWIF E18218 Porter %d abandoned inbound call

LIBSWIF E18219 DELIVER FAILED: (%d)%s, ns=%x, rsb=%x, cause_IE=%x

LIBSWIF E18220 POLL_MSG FAILED: (%d)%s, ns=%x, rsb=%x, cause_IE=%x

LIBSWIF E18221 OFFHOOK FAILED FOR %d: %s, ns=%x, rsb=%x, cause_IE=%x

LIBSWIF E18222 HOOKFLASH FAILED: (%d)%s, ns=%x, rsb=%x, cause_IE=%x

LIBSWIF E18223 STUTTERED DIALTONE TEST FAILED: (%d)%s, ns=%x, rsb=%x, cause_IE=%x

LIBSWIF E18224 DIAL FAILED: (%d)%s, ns=%x, rsb=%x, cause_IE=%x

LIBSWIF E18225 TRANSFER OFFHOOK FAILED: (%d)%s, ns=%x, rsb=%x, cause_IE=%x

LIBSWIF E18226 CAMPON FAILED equip_no=%d: %s, ns=%x, rsb=%x, cause_IE=%x, status=%d

LIBSWIF E18227 POLL_EVENT FAILED: (%d)%s, ns=%x, rsb=%x, cause_IE=%x

LIBSWIF E18228 TRNSFR Failed to find job specified holdmsg number in voicemsg.cfg

LIBSWIF E18400 swid_process_report: bad ns = 0x%04x

LIBSWIF E18401 swid_process_report: bad 0x%x reply

LIBSWIF E18402 swid_process_report: bad <port> in 0x%x reply

LIBSWIF E18403 swid_process_report: 0x%x reply <control_port> out of range.

Page 70: PC4 Troubleshooting Main

68 Maintenance and Troubleshooting Guide March 2008

LIBSWIF E18404 swid_process_report: 0x69 reply on inactive virtual port (0x%04x).

LIBSWIF E18405 swid_process_report: 0x69 reply <outgoing_port=0x%03x> out of range.

LIBSWIF E18406 swid_report_72(reset): bad NSB.

LIBSWIF E18407 swid_process_report: bad port = %d(0x%03x) in 0xDA reply

LIBSWIF E18408 swid_process_report: Ignored 0x%x report on port=%d(0x%03x),supcode=0x%04x

LIBSWIF E18409 swid_process_report: unknown/unexpected change

LIBSWIF E18410 (%d)/event %s(%d) on port (0x%03x).

LIBSWIF E18411 swid_process_report: bad port %d(0x%03x) in 0xDB reply

LIBSWIF E18412 change=%x

LIBSWIF E18413 swid_process_report: <port> (0x%03x) in 0xDD reply not enabled for inbound

LIBSWIF E18414 swid_process_report: 0x49 reply on inactive virtual port (0x%04x).

LIBSWIF E18415 swid_process_report: 0x49 reply <outgoing_port=0x%03x> out of range.

LIBSWIF E18416 swid_process_report: bad port = %d(0x%03x) in 0xEA reply

LIBSWIF E19000 '%s' not in /etc/hosts!

LIBSWIF E19001 swif: '%s' cannot create socket!

LIBSWIF E19002 swif: cannot connect to ethernet switch port '%s:%d',(%d)

LIBSWIF E19003 swif: cannot set socket option SO_KEEPALIVE, err(%d)

LIBSWIF E19004 Failed to read packet header (%d,%d)

LIBSWIF E19005 Failed to read packet body (%d,%d)

LIBSWIF E19006 ethernet receive buffer too small

LIBSWIF E19007 swif: listener cannot swic_init_client()

LIBSWIF E19200 Unable to save switch log history

LIBSWIF E19201 Log event from %s line %d is being throttled.

Page 71: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 69

LIBSWIF E19400 Unable to initialize switch channel, swif return=[%d]

LIBSWIF E19401 Failed to reset switch channel

LIBSWIF E19402 %s TONE DOWNLOAD FAILED, %s, ns=%x, rsb=%x, cause_IE=%x

LIBSWIF E19403 GREETING PROMPT DOWNLOAD FAILED, %s, ns=%x, rsb=%x, cause_IE=%x

LIBSWIF E19404 Failed to reset switch, swif return=[%d],ns=%x, rsb=%x, cause_IE=%x

LIBSWIF E19405 ZIP TONE FAILED, %s, ns=%x, rsb=%x, cause_IE=%x, equip=%d

LIBSWIF E19406 CONNECT RESPONSE: %s, ns=%x, rsb=%x, cause_IE=%x, equip1:%d, equip2:%d

LIBSWIF E19407 DISCONNECT RESPONSE: %s, ns=%x, rsb=%x, cause_IE=%x, equip:%d,

LIBSWIF E19408 Invalid prompt index:%d

LIBSWIF E19600 unexpected EOF/incomplete comment

LIBSWIF E19601 non-ASCII character.

LIBSWIF E19602 Error reading exercise script '%%s':

LIBSWIF E19603 line %%d:

LIBSWIF E19604 event table full

LIBSWIF E19605 not a SWIF function name

LIBSWIF E19606 expecting a time value, digits only, enclosed in ()

LIBSWIF E19607 expecting closing paren

LIBSWIF E19608 expecting SWIF event name

LIBSWIF E19609 too many exercise script errors -- aborting!

CALLSEL E25000 Recall field name or value missing

CALLSEL E25001 Recall field name not found

CALLSEL E25002 Recall pattern error: %s

CALLSEL E25003 %s - Failed to locate strategy files

CALLSEL E25004 Unknown time zone designator %c

CALLSEL E25005 No time zones selected

CALLSEL E25007 Missing field name or value at recall entry %d

Page 72: PC4 Troubleshooting Main

70 Maintenance and Troubleshooting Guide March 2008

CALLSEL E25008 Group may not begin with no selection

CALLSEL E25009 Gap found between select fields within group

CALLSEL E25010 Field name not found at recall entry %d

CALLSEL E25011 Pattern error at recall entry %d: %s

CALLSEL E25012 Sort direction is invalid

CALLSEL E25013 Sort field name not found

CALLSEL E25014 Unit work list Key field name missing

CALLSEL E25015 Unit work list Key field name not found

CALLSEL E25016 Strategy file name missing

CALLSEL E25017 Strategy file name not found

CALLSEL E25018 Unable to read strategy file

CALLSEL E25019 %s - Unable to initialize strategy table

CALLSEL E25020 %s - Time zoning of phone numbers not done on calling list

CALLSEL E25021 %s - Master calling list error

CALLSEL E25022 %s - Unable to get callsel number

CALLSEL E25023 %s - List selection aborted

CALLSEL E25024 %s - Calling List %s is not Time Zoned

CALLSEL E25025 %s - %s field not defined or incorrect length

CALLSEL E25026 Callsel verification failed. Please use change option

CALLSEL E25027 Improper Usage

CALLSEL E25028 Special time zone + is not available

CALLSEL E25029 Report field name not found

CALLSEL E25030 You must specify at least one field

CALLSEL E25031 Timeout: failed to identify status of the Index Processing within %d seconds

CALLSEL E25032 Failed to start asynchronous Index Processing sub-process

CALLSEL E25501 Callsel terminated by signal = %d

CALLSEL E25502 Callsel exited with status of %o (octal)

Page 73: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 71

CALLSEL E25503 Couldn't open file %s

CALLSEL E25504 Failed to read file %s

CALLSEL E25505 callconn:fail to send zALTQUE msg

SEVMONT E27000 Invalid input parameter(s)

SEVMONT E27100 Failed to process the method

SEVMONT E27200 Failed to open the file

SEVMONT E27300 Failed to activate the service

CORE E28000 Failed to initialize switcher

CORE E28100 Unable to attach to data segment

CORE E28101 invalid channel number %s

CORE E28102 couldn't open switch channel

CORE E28103 *** no active channel !!

CORE E28104 'memory' is not implemented

CORE E28105 cannot attach to ipc queue, retval=%d, errno=%d

CORE E28106 equipment number type not found

CORE E28107 no seize on ISDN ports

CORE E28108 no drop on ISDN ports

CORE E28109 UNRECOGNIZED COMMAND! %s

CORE E28200 %s - Job %s %s already exists

CORE E28201 %s - Job %s %s does not exist

CORE E28202 %s - Exceeded shared segment limit

CORE E28203 %s - No phone calls in wait but wait count disagrees

CORE E28204 %s (test_inbound_service) - Conn_op_line failed

CORE E28205 %s - Invalid slot number(%d) passed

CORE E28206 %s - Invalid agent number %d

CORE E28207 %s - Invalid call trans type %c

CORE E28208 No oper_name ('%s') or oper_jobnum (%d), cannot archive

CORE E28209 No oper_name ('%s') or oper_jobnum (%d), cannot restore

Page 74: PC4 Troubleshooting Main

72 Maintenance and Troubleshooting Guide March 2008

CORE E28210 No oper_name ('%s'), cannot restore

CORE E28211 No jobname ('%s') or jobnum (%d), cannot archive

CORE E28300 Unable to create a list of extensions

CORE E28301 add_agent: Unable to insert agent

CORE E28302 add_agent: entered a duplicate value

CORE E28303 add_agent: Error getting current pointer

CORE E28304 agent_recall: Unable to insert recall

CORE E28305 recall_rmp - Exit since AGENTOWNRECALL is off

CORE E28306 recall_rmp - Unable to create a list of agent

CORE E28307 recall_rmp - Unable to create a list of recall

CORE E28308 recall_rmp - unknown message received '%s'

CORE E28309 Failed to setup ipc for agent %s

CORE E28310 recall_rmp - agent %s not available

CORE E28400 Sales verification or managed dialing must have agents

CORE E28401 Managed dialing is not permitted with sales verification or inbound

CORE E28402 Virtual agents cannot select a specific unit to log in to

CORE E28404 Sales verification is not permitted with unit work lists

CORE E28405 Sales verification is not permitted with inbound

CORE E28406 Inbound with unshared account ownership is not permitted

CORE E28407 Alternate selection %s is not permitted with unit work lists

CORE E28408 %s - Failed to get job number

CORE E28409 Job startup failed in job configuration

CORE E28410 Job setup incomplete, Aborting %s

CORE E28411 %s - Unknown message: %s, %s, %s

CORE E28412 %s - Not an inbound capable system

CORE E28413 %s - Failed to setup hunt group

CORE E28414 %s - Invalid hunt group

Page 75: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 73

CORE E28415 %s - Failed to receive a job info position

CORE E28416 %s - FATAL_ERROR: %s

CORE E28417 %s - Record length greater than %d

CORE E28418 %s - Failed on verifying assoc. list

CORE E28419 %s - Failed on reading assoc. list

CORE E28420 %s - Master calling list error

CORE E28421 %s - Invalid strategy: %s

CORE E28422 %s - Failed to table strategy file: %s

CORE E28423 %s - Index file not created with calling list %s

CORE E28424 %s - Exceeded record slots available,PORTCOEF may be low

CORE E28425 %s(%s) - Record number returned invalid %d

CORE E28426 %s(%s) - Record number returned wrong %d, job number %d

CORE E28427 Failed to attach to semaphore

CORE E28428 Failed to read selection criteria file:%s

CORE E28429 %s - Call cancel is not permitted

CORE E28430 Job linking is not permitted

CORE E28431 ERROR: EDTFILE not specified in job file %s

CORE E28432 ERROR: Failed to fork job %s (error=%d)

CORE E28433 ERROR: Failed to exec job %s

CORE E28434 ERROR: Failed to invoke wait for job %s (error=%d)

CORE E28435 Next job %s started

CORE E28436 Next job %s error: %s

CORE E28437 Next job %s terminated by signal %d

CORE E28438 Next job %s stopped by signal %d

CORE E28439 ERROR: Next job %s already starting up.

CORE E28440 Caller(launch_posttrans) - Failed to invoke function fork, err=%d

CORE E28441 Caller(launch_posttrans) - Failed to invoke function rtprio, err=%d

Page 76: PC4 Troubleshooting Main

74 Maintenance and Troubleshooting Guide March 2008

CORE E28442 Caller(launch_posttrans) - Failed to invoke function pipe, err=%d

CORE E28443 %s - Failed to create calling script %s

CORE E28444 Caller - Failed to get port matching label %s N%s

CORE E28445 %s - Failed to terminate proc %d for Agent %s

CORE E28446 caller:fail to send %s to %s

CORE E28447 caller:fail to get shadowjobname

CORE E28448 Job(%s) '%s' sent to a non shadow job

CORE E28449 Caller - PostTrans:Failed to exec prog '%s'

CORE E28450 Caller - %s (R%d) (N%s)

CORE E28451 Job(%s):%s: no available line

CORE E28452 Job(%s):%s: no available record slot

CORE E28453 Job(%s):%s:No recall found in queue

CORE E28454 Job(%s):%s:Invalid phone for this recall, rec_slot=%d

CORE E28455 Job(%s):%s:Same record (%d)is opened

CORE E28456 Job(%s):%s:Record %d is locked

CORE E28457 Job(%s):%s:Failed to read record %d

CORE E28458 Job(%s)::Failed to get phone number:%s

CORE E28459 Job(%s)!get_ft_sort_key!clread error rec_num=%d

CORE E28460 Job(%s):PostTrans:Failed to write pipe, recnum = %d, errno = %d

CORE E28461 Listops(pvrs_record_load) - Record number transferred is bad (%d)

CORE E28462 Preview Empty Record with Multi Units is not allowed.

CORE E28463 Caller - RTSTATS is YES but failed to get operstats_base and/or job_stats_base

CORE E28464 Invalid name (%s) for IVR pool job

CORE E28465 Data process label '%s' for job '%s' missing/invalid

CORE E28600 %s - Invalid port number assigned

CORE E28601 Porter %d - Line inoperable

Page 77: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 75

CORE E28602 %s - Failed to setup input IPC.

CORE E28603 %s - Failed to setup conn_mgr IPC.

CORE E28604 Failed on inbound list def. %s

CORE E28605 Failed on outbound list def. %s

CORE E28606 No extension number for the IVR to dial

CORE E28607 No ring command for IVR to run an application

CORE E28608 HOOKIVR: No dial tone from PBX

CORE E28609 %s - Preview failed to find agent %s

CORE E28610 %s - Mdial failed to find agent %s

CORE E28611 Not allowed in wait

CORE E28612 Request out of sequence

CORE E28613 Missing preview

CORE E28614 Second transaction

CORE E28615 No text in script

LIBDSI E28616 Script missing label %s

CORE E28617 Op keys missing label %s

CORE E28618 Job - Data script %s label missing

CORE E28619 Job - Inbound script label %s missing/invalid

GLOB E28620 Job - Outbound script label for call %s missing/invalid

CORE E28621 Failed to set DAA type:

CORE E28622 Failed to set country code:

CORE E28623 Porter %d failed to busy-out line

CORE E28624 Porter %d abandoned inbound call

CORE E28625 Failed to set DAA type: %d, Porter%d, %d

CORE E28626 Porter %d: Line Fail:

CORE E28627 %s - Invalid line class %c

CORE E28628 Transfer failed, try again later

CORE E28629 No agent available, try again later

CORE E28630 NO DIAL TONE

Page 78: PC4 Troubleshooting Main

76 Maintenance and Troubleshooting Guide March 2008

CORE E28631 M %d > MAX

CORE E28632 M %d < MIN

CORE E28633 Porter - bld_dspmesg:message too long for internal buffer

GLOB E28634 Job - Transfer Wait Queue script label %s missing/invalid

CORE E28800 Recall can't be less than %d minutes

CORE E28801 Record is busy

CORE E28802 Recall not allowed for inbound call

CORE E28803 Transfer setup failed

CORE E28804 Job %s not running

CORE E28805 Job %s not ready - Log on later

CORE E28806 %s - Failed to find job name %s in data seg

CORE E28807 Agent number (%d) invalid

CORE E28808 Headset (%s) not specified in %s file

CORE E28809 %s not specified in switch.cfg file

CORE E28810 Duplicate headset ID (%d) already in use by agent %s

CORE E28811 Duplicate headset ID (%d) already in use

CORE E28812 Agent %s logged in Already - Access Denied

CORE E28813 Maximum %s agent limit reached

CORE E28814 Managed agents are not permitted on this job

CORE E28815 Sales verification with unit work lists is not permitted

CORE E28816 Inbound agents only permitted

CORE E28817 Outbound agents only permitted

CORE E28818 Outbound or Managed agents only permitted

CORE E28819 Only outbound agents permitted by sales verification

CORE E28820 Unit value not found, or unavailable

CORE E28821 Cannot be DONE from alternate screen

CORE E28822 Line not released

Page 79: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 77

CORE E28823 Failed to save record

CORE E28824 Changes to record not saved

CORE E28825 Record not found

CORE E28826 Record is no longer available

CORE E28827 Failed to unlock record

CORE E28828 Unknown screen type

CORE E28829 Field entry is required

CORE E28830 Field value not in acceptable list

CORE E28831 Field has non-numeric value

CORE E28832 %s doesn't match %s format

CORE E28833 Invalid month in date

CORE E28834 Invalid year in date

CORE E28835 Invalid day in date

CORE E28836 Invalid format character found

CORE E28837 Invalid hour in time

CORE E28838 Invalid minute in time

CORE E28839 Invalid second in time

CORE E28840 Time is not in correct format

CORE E28841 Invalid phone

CORE E28842 Invalid phonestat - %c

CORE E28843 Invalid phone number - %s

CORE E28844 No REL_DIST setting

CORE E28845 No REL_TME setting

CORE E28846 No DONE_TME setting

CORE E28847 Date is before the current date

CORE E28848 Recall time and date outside timezone

CORE E28849 %s - Record's timezone is unknown

CORE E28850 ERROR: Cannot open channel to operator monitor process

Page 80: PC4 Troubleshooting Main

78 Maintenance and Troubleshooting Guide March 2008

CORE E28851 ERROR: Operator monitor process does not respond

CORE E28852 ERROR: HEADSET IS NOT ACTIVE

CORE E28853 Error sending digits to switch

CORE E28854 DIALDIGIT Customer Hangup(%d)

CORE E28855 DIALDIGIT Dial Error=%d

CORE E28856 ERROR: Invalid response from operator monitor process

CORE E28857 Feature only available for DIGITAL switch

CORE E28858 %s - Exceeded operator slots available,MAXOPS is low

CORE E28859 %s(%s) - Operator number returned invalid %d

CORE E28860 %s(%s) - Operator number returned wrong %d, job number %d

CORE E28861 Operator slot semaphore not available

CORE E28862 FATAL ERROR ON SELECT - %d

CORE E28863 ERROR - Unknown file descriptor

CORE E28864 Unknown IPC message - %s

CORE E28865 Unknown Command message - %s

CORE E28866 Telephone line not available

CORE E28867 Telephone line not offhook

CORE E28868 Callbacks are not permitted on inbound calls

CORE E28869 Headset volume must be in the range of 1 to 8

CORE E28870 Reserve headset id request pending

CORE E28871 Invalid headset id - %s, %s

CORE E28872 Headset already connected

CORE E28873 Headset ID not reserved nor validated

CORE E28874 Connect headset request pending

CORE E28875 No headset connect request pending

CORE E28876 Headset not connected

CORE E28877 Disconnect headset request pending

Page 81: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 79

CORE E28878 No headset disconnect request pending

CORE E28879 Headset not disconnected

CORE E28880 Headset connection broken

CORE E28881 Headset connection re-connected

CORE E28882 Already available for work - Cannot change class

CORE E28883 Invalid work class

CORE E28884 Not attached to data shared memory

CORE E28885 Not attached to a job

CORE E28886 Unit work lists are not permitted on this job

CORE E28887 Already available for work - Cannot change unit id

CORE E28888 Unit id not found

CORE E28889 Attached to a job already - Must detach first

CORE E28890 Failure to open job %s resource file

CORE E28891 Must specify INBOUND or OUTBOUND operation

CORE E28892 No inbound calling list fields available

CORE E28893 No outbound calling list fields available

CORE E28894 Field name not found

CORE E28895 Already available for work

CORE E28896 Headset must be active

CORE E28897 Available for work request pending

CORE E28898 Job not available

CORE E28899 No available for work request pending

CORE E28900 Wrong message id received - %s

CORE E28901 Not available for work

CORE E28902 Already on work item

CORE E28903 Already set ready for next work item

CORE E28904 Request for no further work pending

CORE E28905 Request to transfer to another job is active

CORE E28906 Not ready for next work item

Page 82: PC4 Troubleshooting Main

80 Maintenance and Troubleshooting Guide March 2008

CORE E28907 Not a managed dialing job

CORE E28908 Not on work item

CORE E28909 Managed call already complete

CORE E28910 Managed call cancelled or complete

CORE E28911 Managed call cancelled

CORE E28912 Data record not available for update

CORE E28913 No job attached

CORE E28914 Still available for work on the job

CORE E28915 Not logged off job yet

CORE E28916 Job attached - Must detach first

CORE E28917 No job attached

CORE E28918 Not avail for work on the job

CORE E28919 Not currently assigned to a work item

CORE E28920 Headset ID not found in reserved list - %s

CORE E28921 FATAL ERROR ABORTING

CORE E28922 No reserve headset id request pending

CORE E28923 Headset ID - %s already reserved

CORE E28924 Must sign on system first

CORE E28925 Already signed on the system

CORE E28926 Invalid sign on

CORE E28927 Agent - Unable to open command input socket - errno:%d

CORE E28928 Agent - Unable to find agent service entry in /etc/services

CORE E28929 Agent - Unable to bind to local address - errno:%d

CORE E28930 Agent - Unable to setup listen on socket - errno:%d

CORE E28931 Agent - Fork of process failed - errno:%d

CORE E28932 Agent - Accept socket connection call failed - errno:%d

CORE E28933 Agent - Read error on client command socket - count:%d, errno:%d

Page 83: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 81

CORE E28934 Agent - Send error on client command socket - errno:%d

CORE E28935 Agent - Parent process exiting

CORE E28936 Agent - Setting of linger failed - errno:%d

CORE E28937 %s agent is not allowed

CORE E28938 Invalid phone type

CORE E28940 Operator - data_synced timeout, data may not be updated

CORE E28942 Job %s is not available

CORE E28943 Invalid key

CORE E28944 COLONS(:) NOT ALLOWED IN PHONE FIELD

CORE E28945 Managed agents only permitted

CORE E28946 Agent not acquired yet

CORE E28947 Invalid call completion code %s

CORE E28948 Jobmon found incorrect PID %d when releasing opslot %d

CORE E28949 Unable to mark as DO NOT CALL

CORE E28950 Extension not in database

CORE E28951 Extension in use

CORE E28952 Cannot add agent

CORE E28953 Acd_ext file read failed

CORE E28954 Duplicate login - please try again

CORE E28955 DNC cannot find key field %s

CORE E28956 ACD Login Error

CORE E28957 Unable to mark other calling lists

CORE E28958 Do Not Call group '%s' not defined

CORE E28959 Invalid Agent Type

CORE E28960 HASH key %s not defined in calling list %s

CORE E28961 Invalid Jobname

CORE E28962 ERROR - Unknown file descriptor

Page 84: PC4 Troubleshooting Main

82 Maintenance and Troubleshooting Guide March 2008

CORE E28963 ZONEPHONE%d field not set

CORE E28964 Agent phone is busy. Release phone line before proceeding.

CORE E28965 Softdialer link is down. Please wait until the link is up.

CORE E28966 Invalid headset ID

CORE E28967 Agent is not allowed to logoff

CORE E28968 Failed to register with dispatcher

CORE E28969 Operator - init_op_cntrl() invoked with NULL curr_op_ptr

CORE E28970 Error queuing jobname data in list_running_jobs

CORE E28971 Operator - cannot access job resource file

CORE E28972 Operator - Timed out while waiting for job resouce file

CORE E28973 Operator - Cannot setup screen '%s'.

CORE E28974 Operator - cannot read screen map - %s:%s

CORE E28975 Cannot search when previewing a recall

CORE E28976 Cannot dial from deleted record

CORE E28977 Operator - Failed to initialize signal %s(%d)

CORE E28978 Operator - Failed to ignore signal %s(%d)

CORE E28979 Operator - Failed to enable auto release SIGUSR1 handler

CORE E28980 Operator - Failed to disable auto release SIGUSR1 handler

CORE E28981 Invalid format for %s for job %s

CORE E28982 Managed call cannot be cancelled

CORE E28983 AGTNoFurtherWork is already in progress

CORE E28984 Agent is being released to ACD inbound

CORE E29000 Managed dialing capable jobs only

CORE E29001 Jobmon - Failed on startup

CORE E29002 Jobmon - Failed to Setup Windows

CORE E29006 Job '%s' not running

CORE E29007 Job not ready, waiting %d seconds...

Page 85: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 83

CORE E29008 Job not Ready - Logon later

CORE E29009 Outbound capable jobs only

CORE E29010 Inbound capable jobs only

CORE E29011 Not a multi-unit job

CORE E29012 May only monitor Inbound

CORE E29013 Invalid number entered

CORE E29014 Monitoring of phone line disabled

CORE E29015 Monitoring of agent disabled

CORE E29016 Invalid port for monitoring agents

CORE E29017 Agent being monitored

CORE E29018 No jobs currently running.

CORE E29019 Error multiple job entrys in SHM

CORE E29020 No agents having a record available

CORE E29021 Record no longer available

CORE E29022 No units currently available

CORE E29023 No agents available to be killed

CORE E29024 Invalid entry, no changes saved.

CORE E29025 No other jobs currently running.

CORE E29026 No agents currently available.

CORE E29027 Agent transfer currently being processed.

CORE E29028 Phone line allocation currently being processed.

CORE E29029 No jobs currently linked.

CORE E29030 No jobs available for selection.

CORE E29031 Link Job '%s' already starting up.

CORE E29032 No phone lines currently acquired

CORE E29033 No request of phone lines currently pending

CORE E29034 No phone lines of type %s acquired

CORE E29035 Job linking capable jobs only

CORE E29036 Invalid system terminal.

Page 86: PC4 Troubleshooting Main

84 Maintenance and Troubleshooting Guide March 2008

CORE E29037 WARNING!!!

CORE E29038 May not monitor op/lines

CORE E29039 Duplicate HEADSET value.

CORE E29040 Illegal W, Q or U rate setting

CORE E29041 Illegal Hit Rate setting

CORE E29042 Allow sending 75 characters

CORE E29043 jobmon: failed to send %s to %s

CORE E29044 Wrong type %s of message for job_strter

CORE E29045 Invalid data from system for get_iicb_status

CORE E29046 Invalid response for list_domain

CORE E29047 Invalid control method

CORE E29048 Invalid response for list_group

CORE E29049 Invalid response for get_group_stats

CORE E29050 Resynch agents is not allowed in the current state

CORE E29051 Unable to create a list of extensions

CORE E29052 Unable to add extension to list!

CORE E29053 Unable to insert extension

CORE E29054 Entered a duplicate value

CORE E29055 Error getting current pointer

CORE E29056 No operator to monitor

CORE E29057 Jobmon: Release code %d has count of %d

CORE E29150 %s:failed to %s

CORE E29151 Failed to initialize signals

CORE E29152 Failed to set SIGALRM handler

CORE E29153 BEEPER:unknown message %s

CORE E29154 Beeper - INTERVAL_ZIPTONE is not set in master.cfg

CORE E29200 %s - Failed to send msg[%s] on channel %d

CORE E29201 %s - Failed to %s data segment

Page 87: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 85

CORE E29202 %s - Failed to %s unit segment

CORE E29203 %s - Failed to attach data segment

CORE E29204 %s - Failed to create data segment

CORE E29205 %s - Failed to create unit segment

CORE E29206 %s - Failed to attach unit segment

CORE E29207 Invalid number entered

CORE E29208 %s - Failed to open channel %d

CORE E29210 %s - Failed to erase voice message %s

CORE E29212 %s - Failed to erase all messages

CORE E29213 %s - MSGNO parameter too big

CORE E29214 %s - Too many messages to load

CORE E29400 Unable to find base file for %s

CORE E29500 ao_recall: failed to send %s

CORE E29501 ao_recall: callsel for %s failed

CORE E29502 ao_recall - cannot retrieve selection file from '%s'

CORE E29503 ao_recall - no strategy file in selection file '%s'

CORE E29505 Error queuing timeout data in add_timeout

CORE E29600 Unable to attach to data segment

CORE E29601 HUNTGRP set incorrectly

CORE E29602 Login code not defined for line %s

CORE E29603 Could not open channel #%d

CORE E29604 No login dial tone on line #%d

CORE E29605 No dial tone on line #%d

CORE E29606 Unable to dial %s

CORE E29607 Error with line %d

CORE E29608 ACD_login : Signal Abort:%s(%d)

CORE E29700 Invalid Selection Number

CORE E29701 Unable to open %s for reading

CORE E29702 Unable to open %s for writing

Page 88: PC4 Troubleshooting Main

86 Maintenance and Troubleshooting Guide March 2008

CORE E29703 Unable to load job file for agent %s

CORE E29704 Unable to read header in job file for agent %s

CORE E29705 Unable to read job list in job file for agent %s

CORE E29706 Unable to write header in job file for agent %s

CORE E29707 Unable to write job list in job file for agent %s

CORE E29708 Job not valid for agent

CORE E29709 Agent job list feature not activated

CORE E29710 Invalid line (%s) in agentjobs.raw; skipping

CORE E29711 Invalid header in job file for agent %s; will recreate

CORE E29712 Job name for agent %s too long; will truncate to %d characters

CORE E29714 Unable to load job file for job chain %s

CORE E29715 Unable to write header in job file for job chain %s

CORE E29716 Unable to write job list in job file for job chain %s

CORE E29717 Unable to read header in job file for job chain %s

CORE E29718 Invalid header in job file for job chain %s; will recreate

CORE E29719 Unable to read job list in job file for job chain %s

CORE E29800 Job Chain %s does not exist

CORE E29900 Unable to start next job %s

CORE E29901 %s - Chain %s already started.

CORE E29902 %s - Max number of chains already started.

CORE E29903 Unable to start job %s

CORE E29904 Unable to stop job %s

CORE E29950 Feature not available in Softdialer Mode

CORE E29951 Specified more than %d line groups for use on job

CIVR E30000 IVR: -- The IVR_REC_LEN is not defined

CIVR E30001 IVR: -- The IVR_HEADER is not defined

CIVR E30002 IVR: -- The signal call failed - SIGUSR1

CIVR E30003 IVR: -- Cannot open the IVR read port

Page 89: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 87

CIVR E30004 IVR: -- Cannot open the output file 1.

CIVR E30005 IVR: -- Problem with read from tty port

CIVR E30006 IVR: -- Received 15 bad IVR records1

CIVR E30007 IVR: -- Problem writing to output file

CIVR E30008 IVR: -- The signal call failed.

CIVR E30009 IVR: -- SIGUSR Cannot open output file 2.

CIVR E30010 IVR: -- SIGUSR Cannot open output file 1.

CIVR E30011 IVR: -- The IVR_TIME_INTVAL is not defined

CIVR E30012 IVR: -- The IVR_NUM_PORTS is not defined

CIVR E30013 IVR: -- Could not exec the process for child

CIVR E30014 IVR: -- Could not fork the child

CIVR E30015 IVR: SYSTEM call for ivr_mk_clist did not return 0

CIVR E30016 IVR: Could not re-exec the process for child

CIVR E30017 IVR: Tried to restart the child 15 times unsuccessfully

CIVR E30018 IVR -- SEVERE ERROR, IVR_DAEMON HAS DIED.

CIVR E30019 IVR: -- System call did not return 0

RECORDX E31200 Null character specified as fill not allowed

RECORDX E31400 Not a valid hexadecimal

DBCONST E32000 %s - No backup list file given

DBCONST E32001 %s - File dictionary name missing

DBCONST E32002 %s - Calling list or file dictionary name missing

DBCONST E32003 %s - One or both merge file names missing

DBCONST E32004 %s - Warning: Reached record limit, additional data not converted

DBCONST E32005 %s - Invalid calling list name

DBCONST E32006 %s - Mismatch in calling lists

DBCONST E32007 %s - Invalid tape record size

DBCONST E32008 %s - Invalid switch year parameter (%d), using default of 70

DBCONST E32400 %s - Rewind failed

Page 90: PC4 Troubleshooting Main

88 Maintenance and Troubleshooting Guide March 2008

DBCONST E32401 %s - System OS ID error

DBCONST E32402 %s - Backup device name(s) missing

DBCONST E32403 %s - Calling list name missing

DBCONST E32404 %s - Dictionary or configuration file missing

DBCONST E32405 %s - Bad tape device name: %s

DBCONST E32600 %s - Failed to execute program '%s' successfully.

DBCONST E32601 Wrong hexadecimal value specified with -a option

DBCONST E32602 CHARSET parameter in .conf file must be set to 'ASCII', with moj_conv program.

DBCONST E32603 CHARCASE parameter in .conf file must be set to 'UPLOW', with moj_conv program.

DBCONST E32604 TAPEDEV parameter in .conf file must not be the device in /dev directory.

DBCONST E32605 BLKSIZE parameter and RESIZE parameter are inconsistent.

DBCONST E32606 Cannot read Japanese code control file %s

DBCONST E32607 No DBCS conversion table name in the code control file.

LETTRGN E34000 formlet - Error reading record: %s

LETTRGN E34001 Criteria error: %s

LSTEXTR E35000 ext_data - Failed to insert new Calling List header info %s

LSTEXTR E35001 ext_data - Invalid new calling list name

LSTEXTR E35002 ext_data - Unable to append - calling list fdicts differ

LSTEXTR E35200 ext_list - Invalid new calling list name

LSTEXTR E35201 ext_list - Failed to read file dictionary %s

DBMAINT E36000 Record_ed: Mark field '%s' not defined for list '%s'

DBMAINT E36001 Invalid record number %s

DBMAINT E36002 Failed to find record number %d

DBMAINT E36003 Failed to determine HASH field %s

DBMAINT E36004 Failed to find select field %s

DBMAINT E36005 Failed to find record number %d

Page 91: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 89

DBMAINT E36006 Record_ed - Could not save Record %d, Value=%s in List %s

DBMAINT E36101 Rec_update - Child process %s terminated

DBMAINT E36200 Pattern error in field %d

DBMAINT E36201 Hash file '%s' (%s) is older than calling list '%s' (%s), please run clhash again.

DBMAINT E36202 Hash key field length %d does not match calling list field length %d

DBMAINT E36203 Source calling list of hash file %s does not match current calling list %s

TOOLS E37000 Error - Failed to load security files

TOOLS E37001 Invalid Name

TOOLS E37002 Name already exists or invalid name

TOOLS E37003 Invalid character in Name

TOOLS E37004 A password must be entered:ERROR

TOOLS E37005 Login Group is Not Valid

TOOLS E37006 ERROR: exceeded valid number of user entries[%d].:Invalid,%s:%s:%s:%s

TOOLS E37007 Createop:%s:Discard:%s:

TOOLS E37008 Invalid Name:Duplicate account

TOOLS E37009 Name already exists:Failed to add account

TOOLS E37010 File is locked by another supervisor, try later!

TOOLS E37011 Unknown error, try later!

TOOLS E37012 No group information is loaded--%s

TOOLS E37013 Fail to read createop.cfg file

TOOLS E37014 Current user is not authorized

TOOLS E37015 Validate group information failed

TOOLS E37016 Invalid old password, Cannot add %s

TOOLS E37017 Error, cannot add %s

TOOLS E37018 Invalid or duplicate user %s

TOOLS E37019 Fail to add to ftpusers-> %s

Page 92: PC4 Troubleshooting Main

90 Maintenance and Troubleshooting Guide March 2008

TOOLS E37020 Invalid user name length: %s

TOOLS E37021 Cannot change owner of %s to admin

TOOLS E37022 Invalid sub-group found in sub-group string %s of group.pds file

TOOLS E37023 Could not setuid(), error = %d

TOOLS E37024 Could not setgid(), error = %d

TOOLS E37025 Have to supply both password file and vllogin or group file

TOOLS E37026 Fail to getpwnam(%s)

TOOLS E37027 alter_entry: Fail to do lckpwdf()

TOOLS E37028 %s not found in vllogin

TOOLS E37029 Fail to enforce new password for %s

TOOLS E37030 DEL_REC: Fail to delete %s

TOOLS E37031 EDIT_REC: Fail to modify account %s

TOOLS E37032 Account not found: %s

TOOLS E37033 Fail to link correct profile for %s

TOOLS E37034 Fail to add user %s

TOOLS E37035 Missing Password or Menu fields: %s:%s:%s:%s

TOOLS E37036 %s not found in group file

TOOLS E37037 WARNING: Reached limit of MAX_USERS (%d) as set in createop.cfg file

TOOLS E37038 ERROR: Reached limit of MAX_USERS (%d) as set in createop.cfg file

TOOLS E37039 Error - Failed to load existing user IDs

EDITOR E37200 Invalid Expert Calling Ratio

EDITOR E37201 Field '%s' not filled in

EDITOR E37202 No Inbound jobs allowed on this system.

EDITOR E37203 Number of reserved inbound lines must be from 1 to %s

EDITOR E37204 Invalid call completion code specified

EDITOR E37205 Invalid start or stop time format

Page 93: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 91

EDITOR E37206 Invalid Hit Rate

EDITOR E37207 Invalid paired phone count/type

EDITOR E37208 Invalid line type specified

EDITOR E37209 HUNTGRP: format error

EDITOR E37210 No HUNTGRP setting.

EDITOR E37211 Selection list not available for use

EDITOR E37212 Selection list for job not found

EDITOR E37213 No Verification Selection List Ready for Job

EDITOR E37214 Selection list not created with this Calling List

EDITOR E37215 Number of telephone lines must be from 1 to 96

EDITOR E37216 An odd number of telephone lines is not allowed

EDITOR E37217 Quota Value less than one

EDITOR E37218 There must be a script label for answer specified

EDITOR E37219 Invalid call completion code for Quota Value %d

EDITOR E37220 Quota %d is not OP completion code

EDITOR E37221 %s field missing from %s

EDITOR E37222 Creation date/time error: %s

EDITOR E37223 Data Transfer file %s.axfr: %s not in %s

EDITOR E37224 Wrong job for verification editor

EDITOR E37225 No editable line found in file: %s

EDITOR E37226 Failed to create link list header

EDITOR E37227 ERROR: Job %s is already running

EDITOR E37228 ERROR: Job file %s already in use

EDITOR E37229 Failed to find linked job file: %s

EDITOR E37230 Managed dialing job linking is not permitted

EDITOR E37231 Sales verification job linking is not permitted

EDITOR E37232 Job linking is not permitted

EDITOR E37233 %s - Unable to start job %s

EDITOR E37234 Failed to find Inbound Job Screen: %s

Page 94: PC4 Troubleshooting Main

92 Maintenance and Troubleshooting Guide March 2008

EDITOR E37235 Failed to find Inbound Job Map: %s

EDITOR E37236 Failed to read Inbound List: %s

EDITOR E37237 Failed to find MSCRN - Job screen: %s

EDITOR E37238 Failed to find MSCRN - Job map: %s

EDITOR E37239 Number of multi screens does not match number of multi lists

EDITOR E37240 Failed to find ASCRN - Job screen: %s

EDITOR E37241 Failed to find MSCRN - Job map: %s

EDITOR E37242 Failed to read Assoc List: %s

EDITOR E37243 Number of associate screens does not match number of associate lists

EDITOR E37244 Number of edit fields does not match number of associate lists

EDITOR E37245 %s - %s(err_code=%d)

EDITOR E37246 %s(err_code=%d)

EDITOR E37247 Unable to clear %s

EDITOR E37248 Line type specified already in use

EDITOR E37249 Improper usage

EDITOR E37250 There must be a script label for call specified

EDITOR E37251 Initial Hit Rate out of range (1-100)

EDITOR E37252 Failed to open script file for IVR ID %s

EDITOR E37253 IVR script name not specified; required if IVR ID specified

EDITOR E37254 Unable to find %s in script file for IVR ID %s

EDITOR E37255 Calling list %s is not on local dialer.

EDITOR E37256 Selecting unit to log in to is not permitted with inbound-only job

TOOLS E37300 %s: Invalid process ID %d

TOOLS E37301 termprocess:fail to send signal message %s

EDITOR E37400 Failed to find %s: %s

EDITOR E37401 Failed to save %s file: %s

Page 95: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 93

EDITOR E37402 Failed to allocate %s

EDITOR E37403 Failed to read %s: %s

EDITOR E37404 Number of %s do not match number of %s

EDITOR E37405 %s field missing or incorrect length

TOOLS E37500 Fail to terminate process %d, errno %d

TOOLS E37501 Fail to kill process %d, errno %d

TOOLS E37502 Fail to send SIGUSR1 process %d, errno %d

TOOLS E37503 Fail to setreuid to (-1, 0)

EDITOR E37600 Field #%d not filled in

EDITOR E37601 No editable line found in file: %s

EDITOR E37602 Failed to create link list header

EDITOR E37603 ERROR: %s already in use

EDITOR E37604 Unable to clear %s

TOOLS E37800 Groupname %s has invalid length

TOOLS E37801 Skeleton path %s for group %s does not exist

TOOLS E37802 Could not add group %s

MARKREC E38000 Chkentdt - Failed to create old database index

MARKREC E38001 Chkentdt - Failed to create new database index

MARKREC E38002 Chkentdt WARNING - cannot open old database %s. Assuming none exists

MARKREC E38003 Chkentdt ERROR:-S option must be used with -i option

MARKREC E38004 Chkentdt - Unable to malloc hash_table

MARKREC E38400 Latemrk - Failed to create calling list index

MARKREC E38401 Latemrk - Failed to create late list index

MARKREC E38402 Latemrk - file error building late list

MARKREC E38403 Latemrk - field_list - key fields not the same length

MARKREC E38404 Latemrk - %s recno %d locked; skipping;

MARKREC E38405 Latemrk - %s '%s' not found in %s, skipping;

MARKREC E38406 Latemrk - Field '%s' not found in %s

Page 96: PC4 Troubleshooting Main

94 Maintenance and Troubleshooting Guide March 2008

MARKREC E38600 %s - Failed to read record: %s

MARKREC E38601 %s - Failed to update record: %s

MARKREC E38602 %s - Failed to create calling list search index

MARKREC E38603 %s - %s '%s' not found in %s.

MARKREC E38604 %s - Valid record range is 1 - %d.

MARKREC E38605 %s - No records in calling list

MARKREC E38800 %s - key fields not the same length

MARKREC E38801 %s - Key '%s' not found in hash file

MARKREC E38802 %s - Error allocating memory for '%s'

MENU E39000 Failed to find user logon entry %s in V/L login file

MENU E39001 Error _ No Menu Name

MENU E39002 Help File Not Found: %s

MENU E39003 Menu File Not Found: %s

MENU E39004 MENU(%d)Signal Interrupt=%d

MENU E39005 %s - User not authorized to run this menu - %s

MENU E39200 Incorrect Item Number

MENU E39201 Failed to Search Directory for File Extension: %s

MENU E39202 Invalid list number

PCEXTRA E40000 No Calling Statistics Files Available

PCEXTRA E40001 PC Analysis - Reopen of %s failed

PCEXTRA E40002 PC Analysis - Invalid File Type of %c

PCEXTRA E40003 No Agent Files Available

PCEXTRA E40200 Pc Analysis - Unknown Type %c for Input File type

PCEXTRA E40201 File Name not Found

PCEXTRA E40202 File does not Exist

PCEXTRA E40203 In Help mode, Cannot Select Criteria

PCEXTRA E40204 Invalid Field Order Select Number

PCEXTRA E40400 %s - Invalid config file name

PCEXTRA E40401 Invalid Extraction Type

Page 97: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 95

PREPROC E42000 -S option must be used with -i option

PREPROC E42100 -S option must be used with -i option

PREPROC E42101 Third argument must be -c

PREPROC E42400 %s - Failed hash open of %s

PREPROC E42401 %s - Failed to stat associated calling list %s

PREPROC E42402 %s - %s : %s

PREPROC E42403 %s - Associate list and hash index date/time do not agree for %s. Run clhash

PREPROC E42404 %s - Field %s length %d not match hash key %s length %d

PREPROC E42405 Record number %s too big for field %s

PREPROC E42406 %s - Record number %s too big for field %s

PREPROC E42600 Field undefined in the calling list

PREPROC E42601 Gap found between field names within group

PREPROC E42602 Missing assigned field values

PREPROC E42603 Gap found in value selections

PREPROC E42604 Field value has an invalid character

PREPROC E42605 Missing Range or Item specification in field values

PREPROC E42606 Values not in ascending order

PREPROC E42607 No fields selected for reporting

PREPROC E42608 Miss value in filler criteria

PREPROC E42609 Miss field name in filler criteria

PREPROC E42610 Pattern Error: %s

PREPROC E42611 'ALL' cannot co-exist with other selections

PREPROC E42612 Unknown call completion code

PREPROC E42613 %s - Unknown select file %s

PREPROC E42614 %s - Unknown supplement file %s

PREPROC E42615 Invalid code. Type R for row, C for column or T for table.

PREPROC E42616 Invalid line number

Page 98: PC4 Troubleshooting Main

96 Maintenance and Troubleshooting Guide March 2008

PREPROC E42617 Cannot move to same location

PREPROC E42800 Invalid number indicator: %s

PREPROC E42801 -S option must be used with -i option

PREPROC E43000 %s - Match field %s length %d not match associated field %s length %d

PREPROC E43001 Record %d - Bad Record number in field %s

PREPROC E43002 %s - Record %d - Assoc list %s read error(%d) for record no. %d

PREPROC E43200 Record %d - Too many records in set

PREPROC E43201 %s - Record %d - Too many records in set

PREPROC E43400 TERMINAL ERROR

PREPROC E43401 Record %d - READ ERROR (%d)

PREPROC E43402 Record %d - WRITE ERROR (%d)

PREPROC E43403 Record %d - HASH ERROR (%d)

PREPROC E43404 %s - Failed hash initialization!

PREPROC E43405 %s - Failed to stat calling list %s

PREPROC E43406 %s - Record %d - READ ERROR (%d)

PREPROC E43407 %s - Record %d - HASH ERROR (%d)

PREPROC E43408 %s - Record %d - WRITE ERROR (%d)

PREPROC E43500 Calling List %s open error

PREPROC E43501 Calling List %s header error

PREPROC E43502 Calling List %s definition error

PREPROC E43503 Field name %s missing in Calling List %s

PREPROC E43504 Error initializing LISTS hash file %s

PREPROC E43505 Error hashing record %d in Calling List %s. Errcode = %d

PREPROC E43506 Error writing hash record %d in hash file %s. Errcode = %d

PREPROC E43507 System_value %d too big. Limit is MAXMSGS

PREPROC E43508 Record %d - READ ERROR

PREPROC E43509 Record %d - WRITE ERROR

Page 99: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 97

PREPROC E43510 Record %d - CALLING LIST BUFFER MALLOC ERROR

PREPROC E43511 Error: colon missing on line %s:%s

PREPROC E43512 %s:%s, Field name %s missing in Calling List %s

HISTORY E44000 %s - Bad arguments

HISTORY E44001 %s - Memory allocation error

HISTORY E44002 %s - File access error

HISTORY E44003 %s - Equation syntax error

HISTORY E44004 %s - Invalid format code

HISTORY E44005 %s - Report configuration error

HISTORY E44006 %s - No HISTORY variable in master.cfg

HISTORY E44007 %s - History dictionary error

HISTORY E44008 %s - Incorrect sort field name

HISTORY E44009 %s - Failed to open report format file

HISTORY E44010 %s - Failed to write output report file

HISTORY E44011 %s - No record selection criteria given

HISTORY E44012 %s - Failed to open input file

HISTORY E44013 %s - Failed to set/reset record lock

HISTORY E44014 %s - job and report format type are not compatible

RPT_MGR E45000 rpt_view - Caught signal %d and terminated

RPT_MGR E45001 Incorrect Report Number

RPT_MGR E45200 File name for view missing

RPT_MGR E45201 pds_view - Caught signal %d and terminated

RPT_MGR E45202 REPORT %s NOT FOUND

RPTGEN E46200 Invalid line number

RPTGEN E46201 Exceeded maximum number of expressions

RPTGEN E46202 Invalid PAGE flag

RPTGEN E46203 Invalid RESET flag

RPTGEN E46204 Missing expression name

Page 100: PC4 Troubleshooting Main

98 Maintenance and Troubleshooting Guide March 2008

RPTGEN E46205 Unknown operator: %s

RPTGEN E46206 Missing operator

RPTGEN E46207 Too many operands for operator '%s'

RPTGEN E46208 Missing operand for operator '%s'

RPTGEN E46209 %s is undefined in the printcap file

RPTGEN E46210 %s is undefined in the dictionary

RPTGEN E46211 Unknown variable name %s

RPTGEN E46212 Unmatching ' in literal string %s

RPTGEN E46213 Unknown data type: %s

RPTGEN E46214 Invalid data type for operator %s

RPTGEN E46400 No expression located at cursor position

RPTGEN E46401 Insufficient memory for screen buffer allocation

RPTGEN E46402 End of file reached

RPTGEN E46403 No lines in buffer

RPTGEN E46404 Invalid starting location - expression overlap

RPTGEN E46405 Invalid ending location - expression overlap

RPTGEN E46406 Must specify start location

RPTGEN E46407 Invalid ending location

RPTGEN E46408 Exceeded maximum report dimensions

RPTGEN E46409 Failed to open format temp file

RPTGEN E46410 Invalid line marker at line %d

RPTGEN E46411 Invalid starting location

RPTGEN E46412 Invalid ending location

RPTGEN E46600 No entries in printcap file

RPTGEN E46601 No entries in file dictionary

RPTGEN E46602 No expressions defined in file

RPTGEN E46603 Failed to open report list file

RPTGEN E46800 Failed to list defined printer model names

RPTGEN E46801 Failed to read printcap file

Page 101: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 99

RPTGEN E46802 Unknown printer model

RPTGEN E46803 Report -

RPTGEN E46804 Failed to get defn. for calling list

RPTGEN E46805 File name missing

RPTGEN E46806 Failed to open text substitution file

RPTGEN E46807 Report control file name too long

RPTGEN E46808 Failed to write report control file

RPTGEN E46809 Failed to read report help file

RPTGEN E46810 Failed to open report control file: %s

RPTGEN E46811 Unknown report control file: %s

SCRNBLD E47000 Failed to initialize

SCRNBLD E47001 Failed to read command keys file

SCRNBLD E47002 Terminal Screen too small for screen editor.

SCRNBLD E47003 May not shift fields further

SCRNBLD E47004 Only Date, Time, or Numeric fields may have Verification Formats

SCRNBLD E47005 Field does not fit in screen.

SCRNBLD E47006 May not overlay screen labels.

SCRNBLD E47007 May not place fields in column one.

SCRNBLD E47008 May not overlap screen fields.

SCRNBLD E47009 May only edit lists [1..%d]

SCRNBLD E47010 %s(ScreenBuilder) - Failed to open output report file

SCRNBLD E47011 May not change to the same file dictionary.

SCRNBLD E47012 No Jobs available

SCRNBLD E47013 No jobs use the current screen

SCRNBLD E47014 Screen does not exist:

SCRNBLD E47015 No changes made.

SCRNBLD E47016 UNFINISHED COMMAND: TESTMODE

SCRNBLD E47017 Invalid %s number specified=%d.

Page 102: PC4 Troubleshooting Main

100 Maintenance and Troubleshooting Guide March 2008

SCRNBLD E47018 Cut & Paste Field Not %s

SCRNBLD E47019 You may not PASTE over fields.

SCRNBLD E47020 Fields may not start in column one.

SCRNBLD E47021 Field in block does not fit on screen.

SCRNBLD E47022 Fields may not overlap.

SCRNBLD E47023 Block must fit on screen.

SCRNBLD E47024 Field[%s,%d] does not match dictionary.

SCRNBLD E47025 Not enough menu options

SCRNBLD E47026 ERROR: no screen open

SCRNBLD E47027 Failed to write screen file

SCRNBLD E47028 Save to a different name.

SCRNBLD E47029 You may not %s the current edit screen.

SCRNBLD E47030 NO HELP TABLE

SCRNBLD E47031 Protected file.

SCRNBLD E47032 Use a different name.

SCRNBLD E47033 Invalid sequence number specified=%d.

SCRNBLD E47034 Invalid field number specified=%d.

SCRNBLD E47035 Cut & Paste Field Not Copied

SCRNBLD E47036 Cut & Paste Field Not Cut, or Copied

SCRNBLD E47037 Cut & Paste Field Not Cleared

SCRNBLD E47038 You may not delete the current edit screen.

SCRNBLD E47039 You may not recover the current edit screen.

SCRNBLD E47040 Failed to initialize Screen

SCRNBLD E47041 Failed to initialize Keyboard

SWIFEXC E48000 Conflicting interface types specified.

SWIFEXC E48001 swif - virtual ports specified are out of range, using defaults

SWIFEXC E48002 Failed to make Ethernet connection to switch. Giving up!

Page 103: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 101

SWIFEXC E48003 Failed to make Ethernet connection to switch. retry=%d, code=%d

SWIFEXC E48004 *** %d=swie_open() retry=%d failed

SWIFEXC E48005 swif_ct - failed to start. Giving up

SWIFEXC E48006 CTI Link Failure

SWIFEXC E48007 CTI Link Recovery

SWIFEXC E48008 Could not open password configuration file.

SWIFEXC E48009 Could not read password configuration file.

SWIFEXC E48010 CTI Error: %s

SWIFEXC E48011 CTI Error: %s %d

SWIFEXC E48012 ReasonCode (%d) is out of range.

SWIFEXC E48013 CTI not configured for agent events.

SWIFEXC E48014 Unable to register for CTI System Status Events

SWIFEXC E48015 No Call for Route Request: RegReqID = %d, CrossRefID = %d, CallID = %d

SWIFEXC E48016 No invoke id for CTI confirmation event: %s %d

SWIFEXC E48017 Insert into STL Map failed, Map name = %s

SWIFEXC E48018 Feature Request for agent event failed, error = %d

SWIFEXC E48019 RecvSysStat - unknown systemStatus = %d

SWIFEXC E48020 TSAPI Command (%s) failed, error = %d

SWIFEXC E48021 Sent Connect Request after Hangup Request. Porter = %d

SWIFEXC E48022 Invalid Prompt_id (%d)

SWIFEXC E48023 Unknown Confirmation event type (%d)

SWIFEXC E48024 TSAPI Command (%s) failed, error = %d, Unable to UUI.

SWIFEXC E48025 CSTAUniversalConfEvent for Call Monitor, error = %d.

SWIFEXC E48026 No available phantom numbers for acquiring an agent

SWIFEXC E48027 Route End Error: RegReqID = %d, CrossRefID = %d, Error = %d

Page 104: PC4 Troubleshooting Main

102 Maintenance and Troubleshooting Guide March 2008

SWIFEXC E48028 OnEventEstablished: Unknown command (%d)

SWIFEXC E48029 Unable to play voice message, unknown agent extension %s

SWIFEXC E48030 Unknown Agent Event (%d), extension (%s)

SWIFEXC E48031 Unable to get hostname to send to the Service Monitor.

SWIFEXC E48032 Unable to send soe_message to the Service Monitor.

SWIFEXC E48033 Unable to create the soe mailbox (%s) error (%d)

SWIFEXC E48034 CSTAUniversalConfEvent (%d) for Phantom number (%s).

SWIFEXC E48035 Unable to set up communications with the server's message queue.

SWIFEXC E48036 MakeCall/MakePredictiveCall/TransferCall Confirm error (%d).

SWIFEXC E48037 %s: Confirm error (%d).

SWIFEXC E48038 OnEventEstablished: SWIF_RESOURCE_LIMIT - cause (%d)

SWIFEXC E48400 Opmon - Unable to setup channel with swif

SWIFEXC E48401 Opmon - Unable to setup input IPC.

SWIFEXC E48402 Opmon - Unable to attach to data segment

SWIFEXC E48403 Opmon - Unable to load operator line configuration

SWIFEXC E48404 Opmon - Invalid number of operators configured.

SWIFEXC E48405 Opmon failed to get time of day to process timeouts

SWIFEXC E48406 Opmon failed to get time of day to set timeout

SWIFEXC E48407 Opmon: Unable to start dialback

SWIFEXC E48408 Opmon received bad headset: %d

SWIFEXC E48409 Opmon bad headset type: %d, hs=%d

SWIFEXC E48410 Opmon received unknown command: %s

SWIFEXC E48411 Opmon unable to find string for msg code %d

SWIFEXC E48412 Opmon : Signal Abort:%s(%d)

SWIFEXC E48413 OPERATOR MONITOR ENABLE FAILED: (%d)%s

Page 105: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 103

SWIFEXC E48414 OPMON DIALBACK FAILURE: (%d)%s,ns=%x,rsb=%x,cause_IE=%x

SWIFEXC E48415 NO HEADSET ASSIGNED TO KEY

SWIFEXC E48416 OPERATOR TYPE MISMATCH FOR HEADSET AND KEY

SWIFEXC E48417 OPERATOR TYPE FOR KEY IS INVALID

SWIFEXC E48418 UNKNOWN COMMAND

SWIFEXC E48419 INVALID GROUP CONFIGURATION FOR DIAL-BACK

SWIFEXC E48420 Opmon - Unable to setup agent_mgr IPC.

SWIFEXC E48421 Invalid DBKGRP in master.cfg

SWIFEXC E48422 Number in DBKGRP and NUM_OF_PBXS in master.cfg is inconsistent

SWIFEXC E48423 Opmon: swif_ct communication failure

SWIFEXC E48600 Missing or invalid headset id

SWIFEXC E48601 Missing or invalid CFGTIME value

SWIFEXC E48602 opmon.cfg - Headset configuration has changed

SWIFEXC E48603 opmon.cfg - Changes will not take effect until reboot

SWIFEXC E48604 Duplicate headset id %d (L%d)

SWIFEXC E48605 Missing comma-separated fields

SWIFEXC E48606 Duplicate key %s

SWIFEXC E48607 Missing or invalid key

SWIFEXC E48608 Missing or invalid phonenum

SWIFEXC E48609 Single value required (not range)

SWIFEXC E48610 Missing or invalid dial-in login timeout

SWIFEXC E48611 Missing or invalid group number

SWIFEXC E48612 A DIALBACK line must precede this line

SWIFEXC E48613 Dialback phone number too long with prefix

SWIFEXC E48614 Dialback phone number too long with suffix

SWIFEXC E48615 Opmon: cleanup abnormal termination of session for headset %d

Page 106: PC4 Troubleshooting Main

104 Maintenance and Troubleshooting Guide March 2008

SWIFEXC E48616 Missing or invalid ISDN protocol

SWIFEXC E48800 Opmon failed to get time of day to set timeout

SWIFEXC E48801 Opmon: Unknown state call %d, hs=%d.

SWIFEXC E48802 Opmon: Key code already in use by headset %d: key=%s

SWIFEXC E48803 Opmon: Unable to play greeting to operator

SWIFEXC E48804 Opmon: HANGUP FAILED: equip=(%d)%x

SWIFEXC E48805 Invalid key code entered: key=%s

SWIFEXC E48806 Opmon: Unable to play prompt %d on equipnum %d:%s

LIBCPP E49001 Password verification failed for user: %s, Exception: %s

UTILITY E50000 Data File Not in Calling List Format

UTILITY E50100 Exceeded number of %s agents

UTILITY E50101 Exceeded wait limit for acceptance

UTILITY E50200 Invalid time format

UTILITY E50201 Invalid hour in time

UTILITY E50202 Invalid minutes in time

UTILITY E50203 Invalid date format

UTILITY E50204 Invalid year in date

UTILITY E50205 Invalid month in date

UTILITY E50206 Invalid day in date

UTILITY E50600 No Headset ID Specified.

UTILITY E50601 Failed to Initialize Keyboard

UTILITY E50602 Failed to Initialize screen environment

UTILITY E50603 Failed to create display window.

UTILITY E50604 Not a pseudo-terminal port

UTILITY E50605 No response from system, login failed

UTILITY E50606 Headset ID (%d) Out of Range (1-%d)

UTILITY E50607 Failed to select Headset ID(%d)

Page 107: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 105

UTILITY E50608 Exceeded retry limits, No valid headset ID specified

UTILITY E50609 Exceeded retry limits, No valid key code specified

UTILITY E50610 Headset ID (%d) Already in use by %s

UTILITY E50611 Headset ID (%s) Already in use

UTILITY E50612 No more Headsets permitted on system

UTILITY E50613 Failure to access Headset Table

UTILITY E50800 op_logout: failed to establish input queue for hs %s

UTILITY E51001 Goodbye...

UTILITY E51200 No information on keys for job %s

UTILITY E51201 No such keys file defined named: %s

UTILITY E51400 Port_start - Failed to get VOICEDIR directory

UTILITY E51600 No <###tran.stat> files are marked with todays date

UTILITY E51601 Cannot open file chi_data

UTILITY E52800 Only single zipcode field is allowed

UTILITY E52801 Exceeded area code fields limit of (%d)

UTILITY E52802 Illegal option -%c

UTILITY E52803 No main option specified

UTILITY E52804 '-f' option also require '-a' & '-z' option

UTILITY E52805 Bad pattern specified with '-x' option

UTILITY E52806 Area code offset can't exceed %d

UTILITY E53000 %s - Unable to open Calling List '%s'

UTILITY E53001 %s - Unable to get List Definition for '%s'

UTILITY E53002 %s - Unable to stat Calling List '%s'

UTILITY E53003 %s - Unable to open Prepare Check file '%s'. Must run clhash first.

UTILITY E53004 %s - Unable to find correct entry for '%s' in Prepare Check file '%s'. Must run clhashin first.

UTILITY E53005 %s - Field '%s' not in Calling List '%s'

UTILITY E53006 %s - Unable to open Associated Calling List '%s'

UTILITY E53007 %s - Unable to stat Associate List '%s'

Page 108: PC4 Troubleshooting Main

106 Maintenance and Troubleshooting Guide March 2008

UTILITY E53008 %s - Field '%s' not in Associate Calling List '%s'

UTILITY E53009 %s - Match field '%s' length %d not same as associated field '%s' length %d!

UTILITY E53010 %d - READ ERROR (%d)

UTILITY E53011 %s - Record %d - READ ERROR (%d)

UTILITY E53012 %d - A READ ERR (%d)

UTILITY E53013 %s - Record %d - ASSOC READ ERROR (%d)

UTILITY E53014 %d - WRITE ERROR (%d)

UTILITY E53015 %s - Associate Record %d - WRITE ERROR (%d)

UTILITY E53016 %d BAD RECORDS

UTILITY E53017 %s - %d BAD RECORDS

UTILITY E53018 %s - %d BAD RECORDS

UTILITY E53019 %s - Unable to open: %s

UTILITY E53020 %s - Unknown configuration file %s

UTILITY E53021 %s - Unable to allocate list buffer

UTILITY E53022 TERMINAL ERROR

UTILITY E53023 %s - Usage error

IMON E53650 compcode.cfg not found

IMON E53651 INTERNETMONDIR parameter is missing from master.cfg

IMON E53652 Internet Monitor shutting down

IMON E53654 Internet Monitor failed to attach to shared memory - conn_mgr may not be running - exiting

IMON E53655 HTML Page update failed - remote Web server may no longer be mounted

UTILITY E53800 Caught error #%d!

UTILITY E53801 Error %d writing msg '%s' to log file [%s].

UTILITY E53802 Error: Unable to log system message. Message '%s' not found.

UTILITY E53803 Error: Couldn't open file '%s'

UTILITY E53804 Error formatting message '%s'.

Page 109: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 107

UTILITY E53805 Error: Nothing to monitor!

UTILITY E53806 Error: Unable to open log file %s for appending.

UTILITY E53807 Error: Couldn't open log file [%s]

UTILITY E53808 Error: Bad date-time format: [%s]

UTILITY E53809 Error: Unable to retrieve EVMON filespec from master.cfg

UTILITY E53810 Error: Config file [%s] was not found.

UTILITY E53811 Error: System call auditing is requested but system is not trusted

UTILITY E53812 Error: File %s was not found. Make sure system auditing is turned on.

UTILITY E53813 Error: Couldn't stat [%s]

UTILITY E53814 Warning: No 'next' audit log defined.

UTILITY E53815 Error: Bad update interval value

UTILITY E53816 Error: Unknown option %c

UTILITY E53817 Error: Unknown/unimplemented entry in cfg file on line %d

UTILITY E53818 Error: The HP-UX auditing system is OFF. Please use SAM to turn it on.

UTILITY E53819 Error: Audctl failed: errno=%d

LISTSVR E54100 Unexpected program exit

LISTSVR E54101 getservbyname ('%s', tcp) failed

LISTSVR E54102 socket () failed

LISTSVR E54103 bind (fd=%d) failed (are clients still connected to sockets of previous listserver instance?)

LISTSVR E54104 listen (fd=%d) failed

LISTSVR E54105 setsockoopt (fd=%d, SO_LINGER) failed

LISTSVR E54106 setsockoopt (fd=%d, SO_KEEPALIVE) failed

LISTSVR E54107 accept (fd=%d) failed

LISTSVR E54108 Usage error

LISTSVR E54109 Received signal %d -- exiting

LISTSVR E54110 FD_ISSET (conn_fd=%d) failed

Page 110: PC4 Troubleshooting Main

108 Maintenance and Troubleshooting Guide March 2008

LISTSVR E54111 Write error -- exiting

LISTSVR E54112 Read error -- exiting

LISTSVR E54113 File descriptor too large (fd=%d) -- exiting

LISTSVR E54114 cllstat (fd=%d) failed -- exiting

LISTSVR E54115 cllrddict (fd=%d) failed -- exiting

LISTSVR E54120 fork failed -- errno=%d '%s'

LISTSVR E54121 Unable to open list '%s'

RPTGEN E55000 Insufficient memory for %s

RPTGEN E55001 Error reading records

RPTGEN E55002 Failed to open report output file

RPTGEN E55200 Group may not begin with no criteria

RPTGEN E55201 Gap found between select fields

RPTGEN E55202 Invalid logical connector

RPTGEN E55203 Missing field name

RPTGEN E55204 Missing field value

RPTGEN E55205 Duplicate field name found

RPTGEN E55206 Invalid sort directive

RPTGEN E55207 Error Pattern: %s

RPTGEN E55400 Failed to write text substitution file

RPTGEN E55600 Invalid number

RPTGEN E55601 Insufficient memory for %s

IVR E56001 ivr_supr: Error connecting to socket, errno %d

IVR E56002 ivr_supr: Unknown command ID:%d

IVR E56003 ivr_supr: IVR_INTEGRATION not set in master.cfg

IVR E56004 Invalid IP address: %s

IVR E56005 No host information is loaded--%s

IVR E56006 Error - Failed to load user interface files

IVR E56007 Validation of IVR information failed

IVR E56008 Invalid IVR ID length: %s

Page 111: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 109

IVR E56009 IVR ID not found in /etc/hosts file: %s

IVR E56010 IVR ID already exists: %s

IVR E56011 Invalid character in IVR ID: %s

IVR E56012 An IP address must be entered

IVR E56013 Fail to add to /etc/hosts: %s

IVR E56014 IVR ID %s not found

IVR E56015 Failed to add IVR %s

IVR E56016 IVR ID already exists in /etc/hosts file: %s

IVR E56017 Currently connected to IVR %s; cannot change or delete configuration

IVR E56018 IVR IP address already exists: %s

IVR E56019 IVR IP address already found in /etc/hosts file: %s

IVR E56020 ivr_conn: ivr_conn service not found in /etc/services

IVR E56021 ivr_conn: Unable to create socket, errno %d - %s

IVR E56022 ivr_conn: Unable to bind to the socket, errno %d

IVR E56023 ivr_conn: Unable to connect to the socket, errno %d

IVR E56024 ivr_conn: Unable to listen to the socket, errno %d

IVR E56025 ivr_conn: Error in select, errno %d

IVR E56026 ivr_conn: Error in accept, errno %d

IVR E56027 ivr_conn: Error on recv from supervisor socket, errno %d

IVR E56028 ivr_conn: Nothing read from supervisor socket, errno %d

IVR E56029 ivr_conn: Unknown message '%s:%s' from supervisor socket

IVR E56030 ivr_conn: Error on recv from IVR socket, errno %d

IVR E56031 ivr_conn: Nothing read from IVR socket, errno %d

IVR E56032 ivr_conn: Unknown message (%c) from IVR socket

IVR E56033 ivr_conn: Invalid message (%s) in input IPC queue

IVR E56034 ivr_conn: Unable to set socket to FIOASYNC, errno %d

Page 112: PC4 Troubleshooting Main

110 Maintenance and Troubleshooting Guide March 2008

IVR E56035 ivr_conn: Unable to set socket to FIOSNBIO, errno %d

IVR E56036 ivr_conn: Unable to set process to receive SIGIO, errno %d

IVR E56037 ivr_conn: Send error, client %d (still trying)

IVR E56038 ivr_conn: Send error, client %d (giving up)

IVR E56039 : err=%d sent=%d rem=%d dt=%d try=%d

IVR E56040 ivr_conn: Error in select in MicroSleep, errno %d

IVR E56041 ivr_conn: Fail to write to pipe - sd %d

IVR E56042 ivr_conn: Caught signal %d, err %d

IVR E56043 ivr_conn: sigaction failed in InitSigHandlers

IVR E56044 ivr_conn: IVR pool job '%s' does not exist

IVR E56045 ivr_conn: Error in trying to access IVR pool job '%s'; errno = %d

IVR E56046 ivr_conn: Already connected to IVR '%s'

IVR E56047 ivr_conn: Not connected to IVR '%s'

IVR E56048 ivr_conn: Still connected to IVR '%s'

IVR E56049 ivr_conn: Reset of IVR '%s' in progress, please wait...

IICB E57000 Dispatcher startup soe_init error: %d

IICB E57001 Dispatcher startup invalid argument count: %d

IICB E57002 Linked list insert error: %d for list: %s

IICB E57003 Linked list create error: %d for list: %s

IICB E57004 Unable to find opmon IPC

IICB E57005 Unable to create dispatcher mailbox <%s>, error: %d

IICB E57006 Cleaning up received fatal signal: %d

IICB E57007 Error: %d deleting dispatcher mailbox

IICB E57008 Send message error: %d <%s>

IICB E57009 Error trying to malloc space: <%s>

IICB E57010 Error opening file: <%s>

IICB E57011 Unexpected object: %d msgtype: %d from md: %d

Page 113: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 111

IICB E57012 Invalid msgtype: %d from md: %d

IICB E57013 Receive message error: %d

IICB E57014 Unknown mode %s: %d

IICB E57015 Attribute not found: %d

IICB E57016 Linked list queuing error: %s

IICB E57017 Invalid mailbox: %s

IICB E57018 Invalid event: %d %s

IICB E57019 Unable to register to mailbox <%s>, error: %d

IICB E57020 Duplicate acquire request on vdn <%s>

IICB E57021 Not enough licenses - Max acquire agents: %d

IICB E57022 Invalid attribute: %d %s

IICB E57023 Unexpected call connect for call_id: %d

IICB E57024 Unexpected call made to vdn: <%s> scai_link: %d

IICB E57025 Call reject error: %d for call_id: %d

IICB E57026 Invalid job id: %d

IICB E57027 Unexpected create call for call_req_id: %d

IICB E57028 Invalid action: %d %s

IICB E57029 Invalid process state: %d %s

IICB E57030 Extension <%s> is already in use by user: %d

IICB E57031 Error: %d as a response to: <%s> message

IICB E57032 Unknown resp_type event: %d

IICB E57033 Unexpected response objid: %d, invokeid: %d

IICB E57034 Process <%s> not responding to msg: <%s>

IICB E57035 Get time error: <%d>, will try again

IICB E57036 Invalid timeout event: <%d>

IICB E57037 Voice message not defined: <%d>

IICB E57038 Extension <%s> scai_link: %d is not installed

IICB E57039 Expected timeout <%s> not found, call_id: <%d>

IICB E57040 Expected timeout <%s> not found, vdn: <%s>

Page 114: PC4 Troubleshooting Main

112 Maintenance and Troubleshooting Guide March 2008

IICB E57041 Release of pbx ext <%s> which is not fully acquired

IICB E57042 User id %d was already in use

IICB E57043 User ext <%s> scai_link <%d> is not found

IICB E57044 Unable to read acd_license.cfg, error: <%d>

CORE E58002 %s - Unable to initialize soe (%d)

JOBCTRL E59500 Job %s not currently running.

JOBCTRL E59501 Illegal parameters: %s

JOBCTRL E59502 Job %s not ready.

JOBCTRL E59503 Job name not specified: %s

JOBCTRL E59505 Job(%s) not linkable

JOBCTRL E59506 Malloc failure in list_agents

JOBCTRL E59507 Inbound capable jobs only: %s

JOBCTRL E59508 Outbound capable jobs only: %s

JOBCTRL E59509 Monitoring of operator disabled

JOBCTRL E59510 Error, no operator %s on job %s

JOBCTRL E59511 Managed dialing capable jobs only: %s

JOBCTRL E59512 Illegal time zone: %s

JOBCTRL E59513 Illegal action %s

JOBCTRL E59514 Inbound capable jobs only

JOBCTRL E59516 Outbound capable jobs only

JOBCTRL E59517 Managed dialing capable jobs only

JOBCTRL E59518 Illegal time zone name %c

JOBCTRL E59519 Unable to open transfer lock file %s

JOBCTRL E59520 Not a multi-unit job: %s

JOBCTRL E59521 No units currently available

JOBCTRL E59522 Illegal units %s

JOBCTRL E59527 Job name not specified

JOBCTRL E59528 Job linking capable jobs only

JOBCTRL E59530 Job not currently linked

Page 115: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 113

JOBCTRL E59531 Invalid port for monitoring agents

JOBCTRL E59533 Warning: Operator already being transferred.

JOBCTRL E59534 Job1 %s not ready.

JOBCTRL E59535 Job2 %s not ready.

JOBCTRL E59539 Illegal change %s

JOBCTRL E59540 Headset ID (%s) already in use

JOBCTRL E59541 No more headsets permitted on system

JOBCTRL E59542 Failure to access headset table

JOBCTRL E59596 No operator slot available

JOBCTRL E59597 System is not running

JOBCTRL E59598 Illegal parameters

JOBCTRL E59599 Bad command

JOBCTRL E59600 Not a Cruise Control job

EVENTSERVER E61000 %s failed: Exception %s; Id %ul

EVENTSERVER E61001 Exception raised: %s

EVENTSERVER E61002 Failed to create thread

EVENTSERVER E61003 Caught unknown exception

EVENTSERVER E61004 Failed to write to IOR file %s

EVENTSERVER E61005 Failed to initialize signal handlers

EVENTSERVER E61006 Failed to initialize %d

EVENTSERVER E61007 attach_datashm () failed -- is system up?

EVENTSERVER E61008 Number of line pools defined in LINEASSIGN in master.cfg (%d) exceeds value of MAX_LINEASSIGN_LABELS (%d)

EVENTSERVER E61009 Exceeded max limit of inactive jobs (%d); skipping the rest

EVENTSERVER E61040 CosNaming NamingContext not found

EVENTSERVER E61041 CosNaming NamingContext cannot proceed

EVENTSERVER E61042 CosNaming NamingContext invalid name

EVENTSERVER E61043 CosNaming NamingContext already bound

Page 116: PC4 Troubleshooting Main

114 Maintenance and Troubleshooting Guide March 2008

DCCS E62000 (%s): Operation %s is not implemented

DCCS E62001 (%s): Operation %s is not applicable to object %s

DCCS E62002 (%s): Requested column %s not available in table %s

DCCS E62003 (%s): Invalid predicate expression %s: %s

DCCS E62004 (%s): Invalid column name %s in predicate expression

DCCS E62005 (%s): Record %s is locked by owner %s

DCCS E62006 (add_lock): failed for Record %s Owner %s

DCCS E62007 (%s): lock for Record %s Owner %s is no longer valid

DCCS E62008 (%s): internal error - no data

DCCS E62009 (%s): no values for input

DCCS E62010 (%s): Operation %s requires %s

DCCS E62011 (%s): Operation %s: Invalid parameters

DCCS E62012 (%s): Record %s is not locked by owner %s, current owner is %s

DCCS E62013 (%s): Requested row %s not available in table %s

DCCS E62014 Unable to create file %s, errno = %d

DCCS E62015 Unable to open file %s for read/write, errno = %d

DCCS E62016 Unable to open file %s for update, errno = %d

DCCS E62017 Unable to open file %s for readonly, errno = %d

DCCS E62018 Unable to delete file %s, errno = %d

DCCS E62019 Unable to create file %s, file already exists

DCCS E62020 General Exception - Table: %s Method: %s

DCCS E62021 File %s does not exist, errno = %d

DCCS E62022 (%s): Operation %s requires Record ID as one of the query conditions

DCCS E62023 Incorrect Table Type

DCCS E62024 (%s): lock_record - Unknown locktype %s

DCCS E62025 (%s) [%#x] : %s(): Error %#x [%s] %s occurred

DCCS E62026 (%s) [%#x] : %s(): Error %#x %s occurred\n

Page 117: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 115

DCCS E62027 Platform Exception - Table: %s Method: %s

DCCS E62028 %s - Error allocating memory

DCCS E62029 (%s): Invalid Message Queue handle

DCCS E62030 (%s): Invalid agent name

DCCS E62031 (%s): Invalid headset ID

DCCS E62032 (%s): Failed to connect to shared memory

DCCS E62033 (%s): Failed to connect to agent %s shared memory

DCCS E62034 (%s): Agent %s is not active

DCCS E62035 (%s): Agent %s is already monitored by line %d

DCCS E62036 (%s): Failed to get IPC key for job: %s

DCCS E62037 (%s): Failed to open IPC for %s

DCCS E62038 (%s): Invalid message to notify agent(s)

DCCS E62039 (%s): Failed to connect to job %s shared memory

DCCS E62040 Lock expired for Record: %s, Owner: %s

DCCS E62041 Unable to fill required field %s for Job %s

DCCS E62042 (%s): Selection Index Failure: Could not verify selection %s with list %s. Run Verify Selection to find specific errors.

DCCS E62043 (%s): Invalid agent name selection pattern '%s'

DCCS E62044 (%s): Selection Index Failure: Could not verify strategy %s with list %s. Run Verify Strategy to find specific errors.

DCCS E62045 (%s): Shared memory object not associated with job: %s

DCCS E62046 Invalid parameters for setting %s

DCCS E62047 Number of Call Strategy Control items requested is greater than allowed on system

DCCS E62048 Requested value less than minimum value.

DCCS E62049 Unable to start job - job file in use by character user interface.

DCCS E62050 Unable to start job - lock on file failed.

DCCS E62051 Unable to start job - job file in use by %s

Page 118: PC4 Troubleshooting Main

116 Maintenance and Troubleshooting Guide March 2008

DCCS E62052 File %s in use by character user interface.

DCCS E62053 Lock on file failed.

DCCS E62054 No response from Job Starter for %s

DCCS E62055 Invalid response from Job Starter for %s

DCCS E62056 Failed check for required fields due to lock on job file

DCCS E62057 (%s): Invalid index process handle

DCCS E62058 (%s): Unable to locate status for calling index process handle '%s'

DCCS E62059 (%s): Failed to send a notification to agent %s

DCCS E62060 Invalid file name: %s

DCCS E62061 (%s): Communication with remote list server failed when processing %s calling list and %s calling selection

DCCS E62062 (%s): Invalid Next Phone definition from phone %s to phone %s that creates infinite loop

DCCS E62070 %s(%d): Syntax error: %s

DCCS E62071 %s(%d): Error in command '%s': %s

DCCS E62072 Unknown variable name '%s'

DCCS E62073 Unexpected error in script definition

DCCS E62074 Total number of lines %d exceeds maximum allowed (must be %d or less)

DCCS E62075 Invalid field name '%s'

DCCS E62076 Invalid number of days %d

DCCS E62077 Invalid number of hours %d

DCCS E62078 Invalid number of minutes %d

DCCS E62079 Invalid audio message ID value %d

DCCS E62080 Invalid time interval value %d

DCCS E62081 Invalid relational operator '%s'

DCCS E62082 Invalid completion code keyword '%s'

DCCS E62083 (%s): Failed to initialize XML processor: %s

DCCS E62084 (%s): Failed to terminate XML processor: %s

Page 119: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 117

DCCS E62085 (%s): Failed to initialize XSLT processor: %s

DCCS E62086 (%s): Failed to terminate XSLT processor: %s

DCCS E62087 (%s): XML processing failed: %s

DCCS E62088 (%s): XML/DOM processing failed

DCCS E62089 (%s): XSLT processing failed: %s

DCCS E62090 Invalid element '%s'

DCCS E62091 (%s): Failed to compile XSLT stylesheet '%s'

DCCS E62092 Invalid label length '%s' (must be %d bytes or less)

DCCS E62093 Referenced label '%s' not defined

DCCS E62094 Command '%s' malformed

DCCS E62095 (%s) Operation %s:%s failed during validation

DCCS E62096 Duplicate label '%s' definition (first definition found in file %s, line %d)

DCCS E62097 File not open

DCCS E62098 Unable to seek to beginning of file

DCCS E62099 File %s is not a valid audio message file

DCCS E62100 Combined size of audio messages of %d kB (approx. %02d:%02d minutes) exceeds the total storage capacity %d kB (approx. %02d:%02d minutes) on PG230 board

DCCS E62101 Total number of audio messages %d exceeds the limit of %d messages

DCCS E62102 Referenced %s audio message not available on the system

DCCS E62103 Audio message ID %d exceeds the the limit of highest ID value %d

DCCS E62104 Using a reserved audio message ID %d

DCCS E62105 Invalid attribute keyword '%s'

DCCS E62106 Invalid attribute value '%s' for keyword '%s'

DCCS E62107 Cannot start monitor agent '%s' audio when on a shadow job

DCCS E62108 Cannot stop monitor agent '%s' audio when on a shadow job

Page 120: PC4 Troubleshooting Main

118 Maintenance and Troubleshooting Guide March 2008

DCCS E62109 Cannot send a message to '%s' agent when on a shadow job

DCCS E62110 Cannot remove an agent '%s' when on a shadow job

DCCS E62111 Cannot transfer agent '%s' when on a shadow job

DCCS E62112 Record is already locked by current user '%s'

DCCS E62113 Record is not locked. Current user '%s'

DCCS E62114 Unknown lock state. Current user '%s'

CCS E63000 Unable to send a message to Dialer: %s Object: %s

AGENTAPI E70000 Incorrect number of arguments

AGENTAPI E70001 Incorrect message type

AGENTAPI E70002 Timed out waiting for %s

AGENTAPI E70003 Incorrect job type

AGENTAPI E70004 Command failed

AGENTAPI E70005 Incoming command exceeded maximum buffer size

AGENTAPI E70006 Must select unit

AGENTAPI E70007 Cannot transfer inbound call

AGENTAPI E70008 Must specify transfer job

AGENTAPI E70009 Unable to send message to %s

AGENTAPI E70010 Conference in progress

AGENTAPI E70011 Call blending is not available

AGENTAPI E70012 Password has expired

AGENTAPI E70013 Password can not be changed, change limit not expired

AGENTAPI E70014 Password can not be changed, password file locked

AGENTAPI E70015 Unable to become root privilege for setting password

AGENTAPI E70016 Original password is invalid

AGENTAPI E70017 New password entered is invalid

AGENTAPI E70018 IVR_SCRIPT is blank in job %s

AGENTAPI E70019 Job %s is not valid for IVR agents

HEALTHMON E72000 %s can't initialize signal handlers

Page 121: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 119

HEALTHMON E72010 %s server name AlreadyBound. ignored

HEALTHMON E72030 %s server name resolve CannotProceed

HEALTHMON E72040 %s server name resolve InvalidName

HEALTHMON E72050 %s Caught CORBA system exception: err=%s

HEALTHMON E72051 %s Caught CORBA exception: err=%s

HEALTHMON E72052 %s Caught CORBA TRANSIENT error.

HEALTHMON E72060 %s Caught unknown exception

HEALTHMON E72070 %s is NotFound

HEALTHMON E72080 failed to write %s IOR

HEALTHMON E72090 %s:: Caught LogOnOffError exception(%d, %s)

HEALTHMON E72100 function %s failed!

HEALTHMON E72110 failed to create %s!

HEALTHMON E72120 can not start activation, %s!

HEALTHMON E72130 failed on starting a %s thread.

HEALTHMON E72140 reqID=%d, failed to add request.

HEALTHMON E72150 failed to load %s.

HEALTHMON E72160 %s: failed on %s.

HEALTHMON E72170 reqID=%d, Failed to execute child process =%s. cmd=%s, errno=%d, ret=%d

HEALTHMON E72180 reqID=%d, Failed to start the service=%s

HEALTHMON E72190 reqID=%d, Caught DSAError.failed to stop the service=%d

HEALTHMON E72200 reqID=%d, Caught unknown exception. failed to stop the service=%d

HEALTHMON E72210 %s: reqID=%d, the reference no longer denotes an existing obj

HEALTHMON E72220 %s: reqID=%d, could not decide whether or not obj exists.

HEALTHMON E72230 %s: reqID=%d, failed on calling observer's Update method.

HEALTHMON E72240 %s: reqID=%d, cmd=%s, caught unknown exception. %s

Page 122: PC4 Troubleshooting Main

120 Maintenance and Troubleshooting Guide March 2008

HEALTHMON E72250 %s: reqID=%d, Failed to %s. cmd=%s, errno=%d, ret=%d

HEALTHMON E72260 %s: Failed to convert from char to LocText

HEALTHMON E72270 %s: the event either is NOT found or is not supported or there is no info for the event.

HEALTHMON E72280 %s: Caught SubError. SubError is: errorID =%s, msg=%s.

HEALTHMON E72290 %s: input param ObserverIF_ptr is null.

HEALTHMON E72300 %s: Create error=%d on mailbox: %s

HEALTHMON E72310 %s: Create error on mailbox: %s

Page 123: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 121

Troubleshooting questions

The following sections each contain questions to ask the customer to help gather information for troubleshooting:

● Unable to start jobs

● List did not download

● Reports not working

● Call completion codes such as line Idle, busy, or hung up in queue, appears excessively

● Internet Monitor issues

● Changes affecting performance

● Agent key files

● Back ups

● Data pops (slow or none)

● Predictive Blend not acquiring

If further questioning is necessary, see Detailed troubleshooting questions.

For in depth problem solving on many issues, see Avaya Proactive Contact Troubleshooting.

Unable to start jobsTo help troubleshoot the issue, have the customer answer these questions:

1. What is the name of the job?

a. What is the start time of the job?

b. What is the stop time of the job?

c. Is the job an Inbound, Blend, or Outbound job?

2. What list is the job using to run?

3. What record selection are you using?

a. Was the record selection run?

b. How many records were selected?

4. What strategy are you using?

5. Where are you starting it? Have the customer try starting the job using both options:

Page 124: PC4 Troubleshooting Main

122 Maintenance and Troubleshooting Guide March 2008

a. In Editor (GUI or windows point and click)

b. In Administrator (UNIX or telnet window)

6. What errors did you get?

7. Has the job ever worked? If so when was the last time it worked?

8. Have there been any changes to the job?

For further job troubleshooting help see Jobs.

List did not downloadTo help troubleshoot the issue, have the customer answer these questions:

1. What list did not download?

2. Has the customer tried to do a manual download?

3. Were there any errors?

a. If the download is stuck at time zoning, have the customer back out of all jobs that are running.

b. If they received the error "ERROR -- No Download Received", have the customer contact their host to see if the file was sent.

4. Has this list ever downloaded successfully?

a. If yes, when was the last time?

b. If no, did they create this list with "Supervisor"?

c. If yes, see Supervisor.

5. Is there any other list they can work off at this time?

a. If answer is yes, then the Severity is "1a Impaired".

b. If the answer is no, then the Severity is "0 Down" follow the routing steps located on page #8 of the Survival Guide.

For more troubleshooting help on lists, see Check list.

Page 125: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 123

Agent cannot connect- dialback failure - unable to login - headset in use

To help troubleshoot the issue, have the customer answer these questions:

1. How many agents are affected, and how many agents do you have?

a. What is the affected agent's log in?

b. Has the agent logged in successfully before?

c. Has anything changed on the workstations or network?

2. What is the error?

a. If the connection timed out, has the workstation ever connected?

b. If DBK failure, has anyone recently logged out of the system?

Reports not workingTo troubleshoot reports not working, have the customer select the reporting tool in use:

Analyst - GUI based reporting

PC Analysis - UNIX Based Reporting

Analyst - GUI based reportingIf the Analyst reporting tool is in use, have the customer answer these questions:

1. What version of Analyst are you using?

2. What version of Crystal Reports are you using?

3. What version of Excel are you using?

4. What report is not working?

a. Is it a standard report? (canned report)

b. Is it a custom report? (the customer modified a canned report)

5. Did you use auto conversion or manual conversion? If auto conversion, go to the next step. If not, go to step 7.

6. Did your auto conversion work?

Page 126: PC4 Troubleshooting Main

124 Maintenance and Troubleshooting Guide March 2008

a. Is there another workstation that did convert records?

b. What time was it set for?

c. Do you have a screen saver, or low power standby on the monitor?

7. Did you run a manual conversion? If yes, then answer a,b,c. If no, go to step 8.

a. Did the screen turn yellow?

b. What error did they get? (At the bottom of the screen)

c. Has the PC been moved?

8. Has the IP address been changed?

9. When was the last time it worked?

PC Analysis - UNIX Based ReportingIf the PC Analysis reporting tool is in use, have the customer answer these questions:

1. a. Is this a new or existing extract?

2. b. What type of extract is it?

a. J - Job History

b. A - Agent History

c. I - Calling Info Statistics

d. T - Calling Trans Statistics

e. L - Calling List

3. What fields are you trying to extract information from?

4. What results are you getting?

5. Are you getting an error?

Call completion codes such as line Idle, busy, or hung up in queue, appears excessively

To help troubleshoot the issue, have the customer answer these questions:

1. What completion code?

2. Is it on all jobs?

3. When did the issue first start?

Page 127: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 125

Internet Monitor issuesTo help troubleshoot the issue, have the customer answer these questions:

1. Is the web server working?

2. Have you reset the web server workstation?

3. How do you know Internet Monitor is not working? Do you see errors? Is it not updating?

4. Are there any network issues?

5. Have there been any recent changes in the network topology?

6. Have there been any recent changes to the web server?

Changes affecting performanceTo help troubleshoot the issue, have the customer answer these questions concerning changes made to the system:

1. Where were changes made?

● Message Text

● Message Assignment

● Agent key files

● Calling list

● Upload/Download list

● Dialer event Scheduler

● Completion Codes

● Message Mapping

Message TextTo help troubleshoot the issue, have the customer answer these questions:

1. What was the message "Number"?

2. What was the message "File Name (AU)" (Be case sensitive)?

3. What was the message "Type"?. What is the "Music or Voice" setting?

Page 128: PC4 Troubleshooting Main

126 Maintenance and Troubleshooting Guide March 2008

Message AssignmentTo help troubleshoot the issue, have the customer answer these questions:

1. What is the name of the script you created? It is case sensitive.

a. Is the name longer than seven characters?

2. What is the type of script you created?

a. Automated

b. Outbound

c. Inbound

d. Transfer

e. Virtual

Agent key filesTo help troubleshoot the issue, have the customer answer these questions:

1. What is the name of the keys file?

Calling listTo help troubleshoot the issue, have the customer answer these questions:

1. What is the name of the list?

2. What tab did you make changes to? Tabs listed below:

● Features

● Fields

● Prepare

● Update

● Custom

● Message Map

● Ordering

3. What change did you make?

Page 129: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 127

Upload/Download listTo help troubleshoot the issue, have the customer answer these questions:

1. What is the name of the list?

2. Did you add or delete fields? If so which fields were affected?

3. What type, Text, Number, Date, etc., of field was it?

4. What was the length of the field?

5. Did the field have any special formatting? If so which kind?

6. Did you refresh the calling list after making changes to the Upload/download?

7. Did you update the Structures and Method tabs?

Dialer event SchedulerTo help troubleshoot the issue, have the customer answer this question:

1. What changes did you make?

Completion CodesTo help troubleshoot the issue, have the customer answer this question:

1. What changes did you make?

Message MappingTo help troubleshoot the issue, have the customer answer this question:

1. What changes did you make?

Back upsTo help troubleshoot the issue, have the customer answer this question:

What kind of Back up?

a. An Avaya Proactive Contact system back up?

Page 130: PC4 Troubleshooting Main

128 Maintenance and Troubleshooting Guide March 2008

b. A calling list back up?

c. A CDW backup?

Data pops (slow or none)To help troubleshoot the issue, have the customer answer these questions:

1. Can you send e-mail both internally and externally?

2. Are you having any known network issues?

3. Has your company been expanding the network?

Predictive Blend not acquiringTo help troubleshoot the issue, have the customer answer these questions:

1. What is the job name?

2. Can the agents log into the job?

3. How long have the agents been sitting idle?

4. What type of switch do you have?

Page 131: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 129

Detailed troubleshooting questions

This section covers scenarios with these areas of Avaya Proactive Contact troubleshooting:

● Networking Issues:

● Hardware troubleshooting

● Telephony & Switch Troubleshooting

● Software Issues

For other detailed troubleshooting help, see Avaya Proactive Contact Troubleshooting.

Networking Issues:

Question Result

Can you ping the CPU from the agent station?

No. There is no response from the CPU.

Can you ping an agent station from the CPU?

No. There is no response from the agent workstation.

Can you ping the switch from the CPU?

No. There is no response from the switch.

Run lanscan. Can you see the network interface?

No, cannot see the network interface of the CPU.

Can you ping the customer's default gateway from the CPU? (Defined as "route1" in the dialer hosts table)

IP Address does not connect.

Confirm network connectivity between the CPU and switch, check processes and look for 4 swif_mako processes running.

Determine that the swif_mako process is not running.

For CTI systems, check processes and look for one swif_dg process running.

Determine that the swif_dg process is not running.

Page 132: PC4 Troubleshooting Main

130 Maintenance and Troubleshooting Guide March 2008

Hardware troubleshooting

General hardware issues

Run landiag. Do you see any errors?

There are errors in the network connection package level.

Ask the customer's network administrator for help in determining if there are other network connectivity problems at the site.

Question Result

Do any of the telephony cards have alarm lights on?

Red alarm lights are on.

On the front of the CPU is a small LCD panel. In the lower right of this panel is a small heart that alternates between an outline and a solid black heart. This heartbeat indicates that the HP operating system is functioning without any major errors.

When the heartbeat indicator is present, look elsewhere for a system fault.

Hard drive failure, the system does not boot. In boot administration, search for boot devices using the SEA command.

If no devices are found, the hard drive has most probably failed.

Are there any errors on the switch for telephony cards?

The switch error log has errors for telephony cards.

Does the Uninterruptible Power Supply have any red lights displayed?

Battery failure.

Page 133: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 131

Avaya CPU Issues

Digital Switch Issues

Question Result

On the front of the CPU is a small LCD panel. In the lower right of this panel is a small heart, which alternates between an outline and a solid black heart. This heartbeat indicates that the HP operating system is functioning without any major errors.

When the heartbeat indicator is present, look elsewhere for a system fault.

Can the customer connect through the console port rather than through the network.

The CPU does not boot up/cannot log into the console.

Is it possible to get into the CPU in Single-user mode and not in multi-user (normal) mode?

No. This indicates an operating system configuration problem.

Question Result

Are there any alarms on the Digital Switch subrack?

Yes. Review the troubleshooting information for the card causing the alarms and determine whether the card needs replacing.

Is there a diskette in the floppy drive?

Yes. The system will attempt to reboot from the floppy.

Can you log into the digital switch?

No, a message displays indicating that the connection was refused.

Can you view the switch menus on the console?

No. An error message displays indicating it could not connect.

Run ps -ef | grep swif_dg to verify if the digital switch is running properly.

If four instances of the swif_dg are not present, the switch is not properly connected to the CPU.

Page 134: PC4 Troubleshooting Main

132 Maintenance and Troubleshooting Guide March 2008

Telephony Issues

Telephony & Switch Troubleshooting

Question Result

Look in the digital switch diagnostic menu to verify if the card alarm status is activated.

One of the cards in the digital switch subrack has an alarm light on it.

Are the T1/E1 spans down or out of sync?

Yes. This indicates problems with connectivity to the central office or PBX. Reseat problem T1/E1's. This can be done without restarting the switch. Follow the troubleshooting steps outlined for the cards in the switch subrack.

Are there excessive T1/E1 slips?

Yes. This indicates timing problems. Reseat problem T1/E1's. This can be done with the card cage and DSC running.

Where in the span is the switch timing coming from? Which span provides the switch timing? This information is found in the digital switch control menu.

Use the master timing selection from the Card Maintenance menu to verify the switch timing. Change the timing to another card, if available.

Is the switch software up but all the cards are in an alarm state?

Yes. Shut down digital switch console and card cage first and then power down and reseat the ENBC card.

Note:Note: You must shut down the digital switch (and

Avaya PDS) before doing this!

Problem Probable Cause Corrective Action

Agent has data but no audio.

The agent entered a valid keycode that belongs to another agent's headset when logging into the Avaya Proactive Contact. This only applies to network- attached headsets.

Have agent log out, then log in again. Verify the agent's headset ID by looking at the opmon.cfg, dgswitch.cfg, and hidfile files.

Page 135: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 133

Messages not playing in hold queue.

Messages are not installed on the digital switch controller.

Verify messages are installed by using the Disk Utilities menu to list the C:/ directory on the digital switch controller. If necessary, reinstall the messages.

Failure of NFS mount after nightly reboot.

Log into the switch and remount NFS. Then rerun msg_loader, and test.

LPVC card is poorly seated or defective.

Check status of LPVC from Card Maintenance screen on switch. If the card is not in Status A (active) reseat it. If this fails, replace card.

Digital switch SCSI cable is poorly seated or defective

Inspect and re-seat the cable.

Customer selected wrong start script label for job.

Check the RUNCALL parameter to find the start script label being used for the job. Then check telephny.spt to find the functionality of the start script label. Verify with the customer that the functionality is what they expected.

Changes in Supervisor. Discuss changes with customer, investigate possible problems.

Wrong message name in voicemsg.cfg on Avaya Proactive Contact CPU. Example: fwait1 when message file is named f_wait1

Verify that the message filenames in job parameters match those in the voicemsg.cfg.

An agent entered the wrong telephone extension at the Enter Key Code prompt. Affects one workstation only.

Have the agent log out, then log in again. Verify the agent enters the telephone extension correctly. Verify the number is valid by looking at the opmon.cfg file.

Page 136: PC4 Troubleshooting Main

134 Maintenance and Troubleshooting Guide March 2008

Change to or failure of customer's telephone network. For example, the customer reprograms the ACD in the network. A T1/E1 span in the customer's telephone network is down. These causes affect multiple workstations.

Try to re-establish the connection by resetting the trunk port interface card. Try to re-establish the connection by resetting the digital switch. Ask the customer to test and fix the suspect trunk.

Other. Isolate the problem by looking for error messages in the log files on the Avaya Proactive Contact CPU and digital switch. For example, digital switch system log file messages might indicate an interface port card for headsets is out of service, indicating the card needs resetting, re-seating, or replacing.

Workstation(s) with dial-back headsets display DIALBACK ATTEMPT FAILED.

A T1/E1 card has lost synchronization with the incoming data stream This condition is typically due to the customer losing service from the Central Office or PBX, or due to the customer changing class of service at the Central Office or PBX.

Note:Note:

The loss of carrier typically forces the T1/E1 card out of service. Requiring that you reset it to re- establish T1/E1 communication.

Confirm diagnosis by looking at the sync source in the Master Timing Link Selection screen. T1/E1 cards default to internal sync if incoming sync is lost. Re-establish incoming sync from the Master Timing Link Selection screen. If the T1/E1 card is out of service, which is typical, reset the card by re-seating it or by changing its status, or reset the digital switch. If the T1/E1 span is down, ask the customer to fix it.

A T1/E1 card is poorly seated or defective. This is rare.

Look for alarms in System Alarm or Card Alarm screens The alarm my be T1/E1 remote out of frame or T1/PRI, E1/PRI card failure. Re-seat or replace the card.

Page 137: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 135

Ground-start T1/E1 trunk(s) connected to a Central Office that is having channel bank problems. Will see issue with individual lines, not the whole T1/E1 span.

Have customer call their CO representative to verify the problem and request assistance.

NO DIAL TONE appears on Phone Line Usage or Line Usage screen for some or all T1/E1 trunks; excessive (>100) out- of-frame errors seen in the Card Display screen.

PBX or Central Office has taken out a telephone trunk by failing to hang up, usually due to a signaling error. Service from the Central Office or PBX has been lost for some other reason. The customer has changed telephone wiring. The trunk ports are incorrectly configured in the digital switch menu system.

Verify which ports are affected by looking at portcorr phone line report or Job Monitor Port Display. Look at the Port Display screen in the digital switch menu system. If a port is stuck in the CP_DISC state, clear the trunk by resetting the port from the Card Maintenance screen or by re- seating the corresponding port interface card. Test the trunk with the breakout box or the Driver program. If the trunk is bad, ask the customer to fix it.

A T1/E1 card has lost the incoming data stream. Typically a T1/E1 span is down.

Verify the diagnosis by looking for "Remote Carrier" or "T1/E1 Carrier" alarm messages in the digital switch log file or by looking at the Card Maintenance screen. T1/E1 cards that have lost carrier switch to Maintenance status. Ask the customer to test and fix the T1/E1 span.

NO DIAL TONE appears on Phone Line Usage or Line Usage screen for one or two trunks (typical). A value of 5% or less for this is normal.

The PBX or Central Office failed to hang up due to a signaling error.

You can sometimes fix the problem by resetting the port. Or, ask the customer to reset the trunk at the PBX or Central Office.

NO DIAL TONE appears on Phone Line Usage or Line Usage screen for a large number of trunks to T1/E1 cards.

The ear or mouth gain for the headset has been set to 0 This only occurs on 4-wire OLIC connections.

Check the ear and mouth gain for the headset port on the digital switch.

Page 138: PC4 Troubleshooting Main

136 Maintenance and Troubleshooting Guide March 2008

The headset is bad. Swap with a known-good headset.

A trunk is stuck at Line Available on the Phone Line Usage screen or Line Usage screen.

Voice cable or OLIC card is bad.

While headsets are not in use, disconnect cables from OLIC. Reset the OLIC card. If alarms clear, then the problem is in the cabling. If you still have failed OLIC ports with no cables attached, then the replace the OLIC card. Also, try swapping OLIC cables. If the problem follows the cable, then the issue is wiring. If the problem stays with the OLIC port, then replace the OLIC card.

A direct-connect headset is dead.

Wrong headset type is configured on OLIC card

Headsets which plug into an adapter box (2-wire headset to 4-wire connection), sometimes called an M10 box, should be configured as "CARBON" on OLIC card. Headsets without this adapter are configured as "ELECTRET"

Avaya Proactive Contact CPU was not rebooted after the digital switch was reset.

Reboot the Avaya Proactive Contact CPU.

Ziptone messages are not download to LVPC.

Verify status of LPVC is "A" for Active on switch. Verify NFS is "mounted." Ask if all agents have this problem, or if it is intermittent. If intermittent, test the LPVC.

A direct-connect headset has poor sound quality.

Network issues. Run landiag to check for network issues, verify transceiver is functioning.

Agents don't hear ziptones.

LPVC card is poorly seated or failing.

Check the status of LPVC from Card Maintenance screen on switch. If card is not in status A (active), reseat. If this fails, replace the card.

Page 139: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 137

Software Issues

General software issues

Mid-Tier Services Issues

Question Result

What feature(s) aren't working?

This question helps narrow down the issue.

If the Agent API is in use, can an agent successfully telnet to the dialer and receive?

If the agent can telnet to the dialer this indicates problems with the API specifically and rules out job operation issues.

Are all Avaya Proactive Contact processes running? Run check_pds.

Look for errors in the log files (check_errors).

Is Supervisor software working?

No. This would indicate a Mid-Tier services failure.

Are the Mid-Tier processes running? Run check_mts.

The Mid-Tier process is down. Run a stop_mts and a start_mts to reset the Mid-Tier services.

Run check_errors and look for issues with the Mid-Tier.

Results in a list of errors collected by the log files on a given day between specified hours.

Page 140: PC4 Troubleshooting Main

138 Maintenance and Troubleshooting Guide March 2008

Supervisor

Database Services

Question Result

Is Supervisor software working?

No. This could indicate a Mid-Tier services failure.

Run a check_mts to find out if the Mid-Tier services are running.

Not running, run a stop_mts and a start_mts to reset the Mid-Tier services.

Was Supervisor software installed properly? (The Mid-Tier systems must be installed prior to installing Supervisor.)

No. Must reinstall the software in the proper order.

Is Supervisor configured correctly through the Configurator Tool?

Configurator lists the correct network information for the Avaya Proactive Contact components.

Is the dialer's IP address resolvable on the network (hosts file or in DNS)?

No. Correct the IP address in the associated file.

Can you ping from the Supervisor workstation to the dialer or ping the workstation from the dialer?

No. This is a network issue.

Symptom Remedy

Verify that the dialer and Mid-Tier processes are running, including HDSC and HDCC.

● check_pds (dialer)● check_mts (Mid-Tier server)

Verify that the database is running.

check_db (dialer)

To verify that the HDCC is running and writing data to the database

check_mts (Mid-Tier server)

Page 141: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 139

Verify that there is historical data available on the target dialer.

List the contents of the /opt/avaya/pds/lists/history/datastore.● Ensure there is a directory corresponding to the current

date.● List the contents of the directory corresponding to the

current date.● Verify there is an event_store.data file in this directory and

ensure that it is the current date.● Verify the data manager process is running (do a

check_pds).● Execute the dataclient test program to verify that the

event_store.data file contains valid data by typing at the command prompt:dataclient -d mmddyyyy

A job is running and agents are logged in on one or more dialers but a report executed from Analyst shows no data for that job.

● Verify that the database is running.● Verify that the HDCC is running and writing data to the

database.● Check to see if data for this job is being populated into the

tables.● If the tables are populated, then consult the

troubleshooting guide for Analyst.

A job is running and agents are logged in to one or more dialers but the historical data tables are not being populated with data for a specific job.

● Verify that the database is running.● Verify that the HDCC is running and writing data to the

database.● Check the Mid-Tier log for HDCC error messages.● Verify that the HDSC is running.● Verify that there is historical data available on the dialer.● Verify that there is only one HDCC process running on the

Mid-Tier server.

The HDCC is not running, or fails to stay up after being restarted.

● Verify that the Logger and Service Monitor are running.● Verify that the database is running.● Check the Mid-Tier log for HDCC error messages● Verify that the HDSC is running. Run a check_mts and

ensure that the HDSC is visible in the naming service.● Stop the HDCC and execute it from the command line.

Observe the output.

Historical data is incomplete.

● Ensure that the job has completed before running report.● Check the mid tier log for HDCC error messages.

Page 142: PC4 Troubleshooting Main

140 Maintenance and Troubleshooting Guide March 2008

Page 143: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 141

Avaya Proactive Contact Troubleshooting

Troubleshooting strategies for these areas of functionality are covered here:

● Verify software is running

● CORBA services

● CCS

● DCCS

● Jobs

● CTI

● StatsPump

● Mid-Tier Database

● Mid-Tier Data Services

● Dialer Mid-Tier connectivity

● Historical Data Server Component

● Database

● End user applications

Verify software is runningTo verify that the Avaya Proactive Contact is running correctly:

1. Identify errors by checking the log files:

tail -f /opt/avaya/pds/account/mid_tier_log.<ccyymmdd>tail -f /opt/avaya/pds/account/account.<ccyymmdd>

2. Verify proper functionality of MTS by running check_mts. The system displays the following message:

>>> All processes running!

3. Verify system proper functionality by running check_pds. The system displays the following message:

>>> All processes running!

Page 144: PC4 Troubleshooting Main

142 Maintenance and Troubleshooting Guide March 2008

4. Verify proper functionality of database by running check_db. The system displays the following message:

>>> All processes running!

CORBA servicesThere are two common errors with CORBA services:

● The nsls script fails to list names in Naming_Service.

● Some services fail to start.

nsls script fails to list names in Naming_ServiceTry the following to correct the problem:

1. Check that the NAMESERVICEHOST keyword in $VOICEDIR/etc/master.cfg is set to the correct value.

2. If the NAMESERVICEHOST keyword value is incorrect, replace the value with the correct value and rerun nsls. If the nsls script still fails to list names in Naming_Service, go to the next step.

3. Go to Mid-Tier dialer and run check_mts to make sure all the mts services are running. If the check_mts script does not display All processes are running!, the script lists any processes that are not running.

4. Start any process the check_mts script reports is missing following the instructions for starting that process in Avaya Procative Contact Software Reference.

Some services fail to startTry the following to correct the problem:

1. Some services such as serviceAct and serviceMonitor require logger to be running. Make sure both logger and serviceMonitor, also a requirement for some services, are both running using Health Manager, Middle-Tier Services > All.

2. If either logger of serviceMonitor is not running, right click in the Middle-Tier Services:All window and click Stop All Midtier Services.

3. Right click in the Middle-Tier Services:All window and click Start All Midtier Services.

Page 145: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 143

Sales Verification testingFollow these steps to set up the Sales Verification feature test:

1. Install the Sales Verification feature.

2. Edit the list#.prep file to include this line:

EXECPROG:callconn:5 list1 verify1 verify1

which uses this syntax for callconn:

callconn <interval> list<num> <select name> <job name>

Follow these steps to test the Sales Verification feature:

1. Enter hostpds list1 at the command prompt.

2. To run callsel for an outbound job, enter callsel at the command prompt.

CCSCommand and control service (CCS) is Mid-Tier server deployed on the primary dialer system which in collaboration with DCCS provides a unified multi-dialer command and control ability. CSS maintains one DCCS connection for each dialer.

CCS not runningIf CCS is not running, follow these steps to correct the problem:

1. Enter ps -e at the command prompt to verify that Naming_Service, Logger and ServiceMonitor are all running.

2. If any of these processes is not running, following the instructions for starting that process in Avaya Procative Contact Software Reference.

3. If CCS is still not running, the wrong Naming_Service may be in use by this set of Mid-Tier services. Run nsls multiple times and make sure the results are identical.

4. If the results are not identical, more than one Naming_Service has been started on the same multicast port. Make sure each system uses it own unique NameServicePort.

5. Run mtsconfigure and start_mts following the instructions for starting these scripts in Avaya Procative Contact Software Reference.

Page 146: PC4 Troubleshooting Main

144 Maintenance and Troubleshooting Guide March 2008

CCS not passing requests to DCCS serverIf CSS is not passing requests to the DCCS server, examine the $VOICEDIR/account/mid_tier_log.ccyymmdd file to see if it contains any errors concerning DCCS.

DCCSThe Dialer Command and Control (DCCS) may have issues that result in processing errors, CORBA problems, or crashes. This section covers those issues and more general DCCS troubleshooting techniques.

DCCS processing errorsProcessing errors for DCCS are logged in the general account log file, $VOICEDIR/account/account.<ccyymmdd>. The prefix DCCS identifies DCCS entries in the log. All error messages must be looked at in context and so a DCCS error message does not necessarily imply a problem with DCCS.

DCCS and Corba problemsAlthough DCCS does not trace CORBA level calls, the $VOICEDIR/account/mid_tier_log.<ccyymmdd> file can provide clues about DCCS CORBA level operations. The CCS component produces this file and logs in detail each CORBA level interface call. Since the CCS CORBA interface maps practically one-to-one with the DCCS CORBA interface, the log file enables you to determine operations that were executed at or around the time of a DCCS error such as a crash.

DCCS crashesThe $TAO_DATA/dccs_log file captures the STDOUT and STDERR. This log file accumulates reports from multiple DCCS runs as each run�s data is appended to the end of the file. The contents of this file are cleared daily by one of the maintenance scripts.

The dccs_log file is usually the very first indicator of a DCCS crash. All kinds of crashes report at least a brief message to STDERR so this file can give a clue as to what was the reason for a crash. The STDERR messages include the SIGTERM (signal #15) which is normally used to stop DCCS, so that entry can be ignored.

Page 147: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 145

Note:Note: Consequently, by counting the number of these messages, Entering Sig

Handler: 15, using a command like this on a HP-UX cmd-prompt:

$ grep 'Entering Sig Handler: 15' $TAO_DATA/dccs_logfile | wc -l

You should always get the numbers of DCCS terminations that day.

DCCS general troubleshootingA trace file and unit testing can be great aids in troubleshooting DCCS problems.

Isolating DCCS problems

To determine if a problem is with DCCS or a connection issue, run DCCS with the -s, simulation option, on the command line. In this mode, any call to the DCCS returns "junk" data. This test verifies that a connection to the server is established without exercising the server's actual data retrieval functionality. If the server does not return any data, the problem is probably a connection issue and is not related to CORBA and its services.

DCCS trace file

The standard DCCS binary supports the creation of a trace file by running the binary with a -d option. Running the binary with the -d option creates a detailed debug trace file, /tmp/dccserverf.dbg.

DCCS unit testing

The dcctest tool, fully documented in the Avaya Proactive Contact Software Reference Binaries, may help isolate problems. The tool uses an XML input file and generates output to the screen and to an XML file.

The directory /opt/avaya/pds/tools/xml contains a Readme file, the dcclient.dtd file needed by dcctest, and sample xml files used by dcctest. The xml files are in sub directories. The names of the directories correspond to the "tables" in dccserver.

You can also use the md_callsel binary to help solve problems involving DCCS and the way it does remote Selection Index processing. md_callsel is a simple cmd-line tool that can exercise the request for a remote processing the same way the DCCS does it.

Use this syntax for md_callsel on the command line:

md_callsel <hostname-list_name #1> <selection_name #1> [<hostname-list_name #2> <selection_name #2>] ... [options_string]

Page 148: PC4 Troubleshooting Main

146 Maintenance and Troubleshooting Guide March 2008

Using this tool helps narrow down the scope of the problem. If the command line above returns the expected results it means that the problem must be with DCCS itself and/or any of the DCCS clients (CCS or CCBridge or the front-end clients). If the command line above fails, the problem is somewhere in the libdsi.a library, specifically the claccesss.c and clcallsel.c and the listserver on the remote machine.

JobsThis section describes several job troubleshooting processes. They include:

● Using Test Mode

● Job will not start

● Jobs ends just after start

● Invalid headset ID

● Agent profile will not execute

● Selection list Unavailable for use

● Job in test mode ignores keystrokes

Using Test ModeSeveral job troubleshooting scenarios require you to put the system in test mode. This section describes how to set up test mode.

Set up call processing in test mode

To set up call processing in test mode, make the following changes to the system configuration:

1. In the /opt/avaya/pds/etc/master.cfg file, set the SWITCHTESTMODE parameter to YES.

2. In the /opt/avaya/pds/config/opmon.cfg file, set the DEDHEAD parameter to DEDHEAD:1-48,1 to define the dedicated agent headset ID number range used for testing purposes.

3. In the /opt/avaya/pds/job/outbnd.job file, set the TESTMODE parameter to:

TESTMODE:VOICE=40 BUSY=20 NOANSWER=20 AUTOVOICE=20:This setting defines the completion code distribution in the test call processing mode.

Page 149: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 147

Set up calling list processing

To prepare the default list1 calling list for use:

1. Type createlist -A <Calling list application name>. The system displays a message like this:

Put Data Onto System

Number of records processed - 501

This generates the /opt/avaya/pds/xfer/clist/list1.

2. Type list_prep list1. The system displays a message like this: CALLING LIST BEING PREPARED FOR CALLING# RETAINING CALL COMPLETION STATUS

latelst - Failed to open file list1.oldmv: /opt/avaya/pds/xfer/clist/list1.old.late: cannot access: No such file or directoryE00515|latemrk - Failed to open file list1.lateENTERING TIME ZONES

Setzones - 501 records processed from list list1 - 426 records successfully processed - 75 records failed with bad phone numbers - 0 records failed time zone lookup - 0 records failed with status of 'deleted'REMOVING DUPLICATE RECORDS

Reject - Found 0 duplicates and 0 special exceptions in calling list list1HASHING THE CALLING LISTclhash - Successful processing for list 'list1' field 'ACCTNUM' 501 recordsHASHING THE CALLING LIST FOR DO NOT CALLclhash - Successful processing for list 'list1' field 'ACCTNUM' 501 recordsMARK RECORDS WITH DAYS ON PROACTIVE CONTACT GREATER THAN 5OOPSchkentdt - Processed 501 records on list: list1 with 0 records deletedREJECTED ACCOUNTSREJECTED ACCOUNTSCALLING LIST PREPARED FOR CALLING - list1Type chkentdt list1 ACCTNUM d=5 w=5. The system displays a message like this:OOPSchkentdt - Processed 501 records on list: list1 with 0 records deletedType callsel -l list1 -s all -x -p. The system displays a message like this:

CALL SELECTION

Page 150: PC4 Troubleshooting Main

148 Maintenance and Troubleshooting Guide March 2008

Selection List Generation

Records processed 501 Total records 501

398 records selected and 0 recalls

Writing Selection List Index #1

Generating Report File 11876

Job will not startCheck the job guard times, STARTTIME and STOPTIME, in the .job file and adjust the values as necessary to fix this problem.

Jobs ends just after startIf when you start a job, its ends abruptly after a few seconds, check the following to troubleshoot this issue:

1. Are timezone codes for each phone number classified in the calling list? If not, correct the timezone codes for phone numbers and restart the job.

2. Check to see that there are uncalled records in the calling list. If there are no uncalled records, either obtain a fresh list or reset list to an uncalled state. Enter this command at the command prompt to reset the list:

set_field list1 STATUSFLAG CODE DTE TME.

3. Check the timezone report in config_ed to see if you are attempting to call within the timezone guard times of at least some of the records in your list.

Note:Note: If you need to modify timezone.cfg, you must re-run your callsel for the new

times to take effect.

Page 151: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 149

Invalid headset IDIn test mode, you try to log on an Agent and get the error message, Invalid headset ID. Try the following to correct the problem:

1. It may be that the system is not in testmode. Check that the SWITCHTESTMODE keyword in $VOICEDIR/etc/master.cfg is to YES.

2. If the error persists, check that these keywords in $VOICEDIR/config/opmon.cfg have the listed values:

● CFGTIME:15

● DEDHEAD:1-48,1

● #DIALBACK:49-96:15:0::

● #DIALBACKNUM:ALL

● DIALINTIMEOUT:30

3. If the values in opmon.cfg are correct and the error still occurs, check that PORTS keyword value in $VOICEDIR/etc/master.cfg matches the DEDEAD keyword value in $VOICEDIR/config/opmon.cfg. If they do not match, make them have the same value.

4. If the error is still there, check that the number of headsets in $VOICEDIR/config/dgswitch.cfg matches the value for the keyword, PORTS in $VOICEDIR/etc/master.cfg.

5. If you made any changes to parameters, reboot Avaya Proactive Contact.

Agent profile will not executeIf when agents log in, their .profile will not execute:

1. Make sure that the agent's .profile is soft-linked to /etc/skel/pds_agent/.profile. The /etc directory must have correct ownership and permissions or the agent may not have permission to run it.

2. If agents still have problems with their .profiles, try logging in as root and running $VOICEDIR/tools/shell/sysverify. This tool checks to see whether all dialer files, ownerships and permissions are present and correct. sysverify -f corrects any permission or ownership problems. Use the -f option only as a last resort.

Page 152: PC4 Troubleshooting Main

150 Maintenance and Troubleshooting Guide March 2008

Selection list Unavailable for useWhen you try to start a job, you get the message Selection list unavailable for use. There are two possible causes of this error:

1. Jobs may be trying to use the same .S file. Check that each currently running job is accessing its own .S file.

2. If a job (or caller) aborted prematurely, it did not do its cleanup steps.

Note:Note: Only perform these steps as a last resort. These steps remove all current job files.

To do the clean up manually, first stop all jobs. Then, at the command prompt, enter:

● cd $VOICEDIR/lists

● rm *.inx *.rcl *.sel *.stgy *.stat *.as *.recsel stat.*

Rerun callsel before trying to start the job again.

Job in test mode ignores keystrokesWhen running a job in test mode, the system ignores keystrokes to the agent CUI window. For inbound and outbound agents in test mode, if you want to interact manually with the agent CUI, set the <jobname>.job TESTOPER parameter to an empty string.

General Job troubleshooting● Check job parameters

● Check list

Page 153: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 151

Check job parameters

In the /opt/avaya/pds/job/<job_name>.job file you wish to run, check the following keywords:

Check list

To make sure the list you intend to use for testing exists, check the /opt/avaya/pds/xfer/clist directory for it. If it is not present or if you just need a small sample list to test with, you can generate one with the readtape command as follows:

1. On the same system as the clist directory, type:

readtape -c hg_in1 -d lt_in1 -olist_prep list1

Keyword Value Description

LIST: hula:list1 Indicates the name of the calling list to use for the job.

SELECT: all Indicates the record selection (*.S) filename.

STARTTIME: 08.00: Earliest start time for a job in 24-hour format hh.mm. Set to 00.01 for night-owl/early-bird testers.

STOPTIME: 23.00: Latest stop time for a job in 24-hour format hh.mm. Set to 23.59 for night-owl/early-bird testers.

TESTMODE: Indicates the distribution of call completion code results required in test mode. Percentages must equal 100.

VOICE Set to 100 for manual calling. 40 is the default value for test mode.

BUSY 20 is the default value for test mode.

NOANSWER 20 is the default value for test mode.

AUTOVOICE 20 is the default value for test mode.

TESTOPER: <talktime= sec>, <updtime=sec>

Leave blank for manual calling. Indicates the number of seconds agents are allowed for talk time <talktime> and update time <updtime>. Set both values to 5 for test mode.

Page 154: PC4 Troubleshooting Main

152 Maintenance and Troubleshooting Guide March 2008

2. The first time the list is used run setzones, to classify the time zone of each phone number, type:

setzones list13. Run callsel to set up an index with pointers to selected records:

callsel -l list1 -s all -x -p [-u]where -x means skip manual configuration, use as is (if possible)

-p means print results to /tmp/reports

-u unit work lists active (for unit work list jobs)

-s defines the strategy file, /opt/avaya/pds/callsel/all.S

-l defines the calling list, /opt/avaya/pds/xfer/clist/list1

CTIThe topics of CTI troubleshooting covered are:

● Installation: Verify CTI link

● CTO OAM Utilities

● CTI Troubleshooting

● Troubleshooting tips for Avaya CTI

Installation: Verify CTI link To verify the CTI link you need to check the state of Avaya CT or Application Enablement Services (AES).

Page 155: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 153

Avaya CT

Follow these steps to verify the CTI link:

1. Go to the server that is running Avaya CT 1.x and start the TS Controller by entering Start > All Programs > Avaya Telephony Computer > TS Controller that displays this dialog box:

The Telephony Services State text box should contain the word RUNNING which verifies that Avaya CT is running.

Page 156: PC4 Troubleshooting Main

154 Maintenance and Troubleshooting Guide March 2008

2. To check that a call can be made through Avaya CT, go to the server that is running Avaya CT 1.x and start TS Test by selecting Start > Al Programs > Avaya Telephony Computer > TS Win32 Client > TS Test to display this dialog box:

3. In the TSTest Telephony Services Test Application dialog box fill in the Server, User, and Password text boxes with dialer values found in the swif_ct.cfg and cti_passwd.cfg files.

4. In the TSTest Telephony Services Test Application dialog box fill the From and To text boxes with real extensions on the PBX.

5. Click Dial to run the test.

6. If the test is successful, the test displays a message box with this content:

Call successfully originated. Dismiss this message box to terminate call.7. If the test is unsuccessful, verify that the extensions used for To and From are working by

placing a call from them using a hard phone. If either of these calls fail, there is a line problem with the extension that failed.

8. If these calls are successful, then there is a problem with either the configuration of Avaya CT Server, the CTI Link, or on the Avaya PBX.

9. To troubleshoot these errors, inspect the error logs on the server that is running Avaya CT 1.x by selecting Start > All Programs > Avaya Telephony Computer > Error Log.

Page 157: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 155

AES

To verify that the AES process is running:

1. Log in to CTI OAM Admin to display the Operations, Administration and Maintenance (OAM) home page.

2. From the main menu, select CTI OAM Admin to display the CTI OAM home page:

On this screen check that all the services have a Controller Status of Running.

Page 158: PC4 Troubleshooting Main

156 Maintenance and Troubleshooting Guide March 2008

3. To view the connection state, select Status and Control > Switch Conn Summary to display this screen:

The entry for the Conn Stat column should be Talking.

Page 159: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 157

CTO OAM UtilitiesThe CTI OAM home page also provides access to Utilities. To access the utilities, select Utilities from the main menu to display this screen:

ASAI Test

Use the ASAI Test page to determine if the AE Server is communicating with Communication Manager.

Ping Host

Use the Ping Host page to determine if the hostname or IP address you specify exists and is accepting requests.

TSAPI Test

Use the TSAPI page to place a test phone call.

Page 160: PC4 Troubleshooting Main

158 Maintenance and Troubleshooting Guide March 2008

CTI TroubleshootingThis section includes a discussion of Testmode, Debugging logs and some general troubleshooting techniques for Avaya CTI.

Testmode

Use testmode to test the CTI configuration, but not the switch. It is particularly useful for use before the CTI Link and PBX are ready for test. Since testmode does not work with Avaya Proactive Contact with CTI, you must change the configuration slightly to use testmode. Make these changes:

Restart the dialer.

Debugging logs

There are three logs that can be used for solving problems with swif_ct and its functionality:

● switch_log.ccyymmdd

● cti.dbg

● swif_ct.dbg

The switch_log.ccyymmdd is always available on a running dialer in the /opt/avaya/pds/account directory. The contents of this file include such events as start, link down, link up and errors.

The cti.dbg file is a log of all the messages flowing between swif_ct and the CTI Link. To create this log file, set this environment variable in the /opt/avaya/pds/scripts/pdscontrol file:

export CSTATRACE=/opt/avaya/pds/account/cti.dbg

Make sure the line above is close to the beginning of the file. The directory and file name can be any valid directory and file name, although the account directory contains several other logs, so it is an easily remembered choice. Since this file can grow quite large, use it only during a debug session, not for normal use.

File Keyword Value

master.cfg SWITCHTESTMODE YES

master.cfg SWITCHTYPE DIGITAL

opmon.cfg DEDHEAD 1-48,1

Page 161: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 159

The swif_ct.dbg file cannot be created by the standard swif_ct binary, but requires a special debug version of the binary to create it. If a debug version is available, make a copy of the original swif_ct file and put in it in a safe place. Overwrite the original swif_ct with the debug version. To have the debug version create the swif_ct.dbg file, add this line near the start of the /opt/avaya/pds/scripts/pdscontrol file:

export SWIFDEBUG=1,10-31:timestamp

Restart the dialer. Every time swif_ct is restarted, the swif_ct.dbg file, located in the /tmp directory is overwritten.

Troubleshooting tips for Avaya CTIThis section contains a small set of troubleshooting tips for Avaya CTI.

driver_ct

Use driver_ct, a CTI test tool, to send messages to swif_ct as if the messages were coming from opmon or porter. The tool reports the messages back from swif_ct and is useful for verifying functionality from swif_ct through the switch to the end station. See the Driver_ct User Guide, CID 113850, for more information on driver_ct.

Managed job without CPA issues

There are four different scenarios that can cause problems with managed jobs:

1. If the system is using Make Predictive Call instead of Make Call, make this change:

● Set the VISUAL_CPA keyword in master.cfg to NO.

● Do not use with Agent, only with the Agent API such as PDS Agent.

2. If the system appears to be working because pop screens appear, but agents are not making calls, the system may be in testmode. See Testmode for details on testmode.

3. Problem with "operator" can occur when an agent logs in, puts in extension and agent type, and the error message Invalid headset displays. To correct this error:

● Run check_pds to assure that the swif_ct process is running. If the swif_ct process is not running, it can cause the error message.

● If the swif_ct process is not running, check the switch_log to determine the reason it is not running.

4. With PDS Agent, when the agent clicks OK on the login screen, the error message Unable to open channel to agent monitor process displays.

● This error message occurs when swif_ct is not running. Run check_pds to assure that the swif_ct process is running.

Page 162: PC4 Troubleshooting Main

160 Maintenance and Troubleshooting Guide March 2008

● If the swif_ct process is not running, check the switch_log to determine the reason it is not running.

Predictive calls troubleshooting

Sometimes with predictive calls, an agent can generate pop screens, but has no audio call. This often results in error messages in the switch log such as:

● Unknow!2005/10/21!17.08.55!(type=0,severity=3,subsys=6) Swif_ct: E48015: No Call for Route Request: RegReqID?=1, CrossRefID? = 283, CallID?=709

● Unknow!2005/10/21!17.09.55!(type=0,severity=3,subsys=6) Swif_ct: E48027: Route End Error: RegReqID?=1, CrossRefID?=283, Error = 52

Resolves these errors by setting the Universal Call ID in the PBX to Yes.

StatsPumpStatspump consists of the statsPumpCtrl process and statspump java process.

Follow these steps to troubleshoot statspump:

1. Check that statspump is running by entering check_mts at the command prompt.

2. If statsPumpCtrl does not display in the results for check_mts, most likely statsPumpCtrl has not started. Run check_mts again to make sure serviceMonitor and Naming_Service are running.

3. If either these two processes are not running, follow the instructions for starting that process in Avaya Procative Contact Software Reference.

4. Check that statspump is running by entering check_mts at the command prompt. If it is still not running, go to the next step.

5. Reconfigure the system by following these steps:

a. Check the keyword values in $VOICEDIR/etc/master.cfg to ensure they are set correctly. Edit the file to correct any mistakes.

b. Enter stop_pds and then stop_mts at the command prompt.

c. Delete all files in the /opt/avaya/services/data directory.

d. Enter start_mts and then start_pds at the command prompt.

e. Enter check_mts at the command prompt and inspect the results to ensure that statsPumpCtrl is running.

Page 163: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 161

Mid-Tier DatabaseTwo common problems with the Mid-Tier database are networking issues that prevent access to the database and in some cases the database process is not running. The next two sections provide guidance on resolving these issues.

Mid-Tier database network problemsIf you suspect the Mid-Tier database is not available on the network, follow these steps to troubleshoot the problem:

1. From the command prompt, ping the host system for the database using the IP address of the host system.

2. If the ping is successful, go to Mid-Tier database not running.

3. If the ping is unsuccessful, check that the /etc/resolv.conf file contains the line:

domain <domain name>

4. If /etc/resolv.conf does not contain the line above, add the line to the file.

5. From the command prompt, ping the host system for the database using the IP address of the host system. If the ping is unsuccessful, there are two possible next steps depending on whether or not DNS is in use.

6. If DNS is in use, edit the /etc/nsswitch.conf to contain this line:

<IP_address><machine_name><machine_name.domain>

7. If DNS is not in use, edit the /etc/hosts to contain this line:

<IP_address><machine_name><machine_name.domain>

8. From the command prompt, ping the host system for the database using the IP address of the host system.

Mid-Tier database not runningTo see if the Mid-Tier database is running, enter this command at the command prompt on the database host system:

check_db

If the Mid-Tier database is not running, start it by entering these command at the command prompt on the database host system:

stop_mts

Page 164: PC4 Troubleshooting Main

162 Maintenance and Troubleshooting Guide March 2008

start_db

start_mts

Verify Mid-Tier components can access databaseTo verify StatsPump updates data in the database and Mid-Tier components can access the database, follow these steps:

1. Open Window Explorer on the client system.

2. Navigate to the Avaya Proactive Contact install directory.

3. In the ..\Services\3rdParty\Oracle10g directory, double-click sqlplus.exe.

4. At the Enter user-name prompt, type avayapdsdb/avayadba.

5. At the SQL> prompt, type select * from dialerdef; and press ENTER. Make sure you have entered the semi-colon (;).

6. The screen should display something like this:DIALER_ID DIALERNAME_NTXT PACKETTIME_NUM DIALERIP_NTXT---------- -------------------- -------------- ------------------------------SYSTIME_NTXT SYSLINES_NUM SYSAGENTS_NUM SYSJOBS_NUM SYSUPDATETIME_NUM-------------------- ------------ ------------- ----------- -----------------LASTUPDTIME_NUM--------------- 23 redlab23 1144852359 143.243.248.1232006/4/12 7:32:39 21 108 50 6 1144932555

There is one row of data for each dialer in the pod. Be sure to note the SYSTIME_NTXT data, 2006/4/12 7:32:39 in the example. This time stamp should be current.

7. Enter the command again.

8. Each time you enter the command with about a 30 second pause, the systime_ntxt value updates for dialers running Avaya Proactive Contact.

9. If it is not updating, there in a problem with connectivity, see Dialer Mid-Tier connectivity.

Mid-Tier Data ServicesThis MS Windows component, avmtdsci.dll, provides database connection between the client applications and the primary dialer. At one end, it connects to a database to get data and at the other; it offers several interfaces to the client. The data returned by MTDSC is computed based on the information available in the database and the parameters provided by the client.

Page 165: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 163

If errors occur inside MTDSC, messages register in Window's Event Viewer. Usually the errors relate to the database connections, database operations and interface specifics.

To troubleshoot these issues, follow these steps:

1. To set the avmtdsci.dll in debug mode, change the Windows Registry entry for HKEY_LOCAL_MACHINE/SOFTWARE/Avaya/Proactive Contact 4.0/Supervisor/DscDebug to 1.

Avaya Proactive Contact creates an AvMTier directory at the Windows root that contains the avmtdsciiL0.log and the dscHierL0.log files.

Note:Note: You can also turn on debugging by through the CD Log Viewer main menu, Tools

> Turn Data Services Debug Logging On.2. To check the database connection, from the Windows Start menu, select Settings >

Control Panel > Administrative Tools > Data Sources (ODBC).3. Click on the System DSN tab.

4. Select AvayaPDSDB from the list of System Data Sources.

5. Click Configure.

6. In the Oracle ODBC Driver Configuration window, click Test Connection.

7. You should see a Connection successful message. Otherwise you see an error message which you should record.

Dialer Mid-Tier connectivityIf any client application has problems communicating with the Mid-Tier, follow these steps:

1. Type check_pds on the dialer and you should see the following message:

>>> All processes are running!

2. Open a Windows command prompt and enter the following command:

nslist -ORBSvcConf "C:\Program Files\Avaya\Proactive Contact 4.0\Supervisor\Common\corba_svc.conf" -ORBInitRef NameService=corbaloc:ssliop:<dialername>:23201/NameService

in which <sysname> is either the IP address or alias of the system on which the Mid-Tier Naming Service resides.

3. From the Windows Start menu, select Settings > Control Panel > Administrative Tools > Data Sources (ODBC).

4. Click on the System DSN tab.

5. Select AvayaPDSDB from the list of System Data Sources.

Page 166: PC4 Troubleshooting Main

164 Maintenance and Troubleshooting Guide March 2008

6. Click Configure....7. In the Oracle ODBC Driver Configuration window, click Test Connection.

8. You should see a Connection successful message. Otherwise you see an error message which you should record.

Historical Data Server ComponentHistorical data describes all activities that take place on one or more dialers over a specified time interval. The datapump binary serves as the historical data component client (HDCC). The historical data server component (HDSC) runs from the start_pds script and the pdsconfigure script registers the HDSC into the Naming Service on the dialer.

HDCC troubleshootingIf the HDCC is not running:

1. Use check_mts to make sure the logger and serviceMonitor processes are running before starting the datapump binary.

2. On the primary dialer, use check_db to make sure the database is running and available to users. It should display this message:

>> > All processes are running and the database is opened to the users!

The following sections detail some typical problems that occur with the HDSC and HDCC.

Analyst shows no data for running job

A job is running and agents are logged in on one or more dialers, but a report executed from Analyst shows no data for that job.

To resolve this issue, follow these steps:

1. On the HDSC host system, use check_db to determine if the database is running. If the database is running, go to the next step.

2. If the database is not running, you need to start it using the start_db script. Consult Avaya Proactive Contact Software Reference Scripts for important information on using this script.

3. On the HDCC host system, enter check_mts to check that datapump is running. If the datapump is running, go to step 5.

Page 167: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 165

4. If datapump is not running, you need to run the start_mts script. Consult Avaya Proactive Contact Software Reference Scripts for important information on using this script.

5. Verify that HDCC is writing data to the database by:

a. At the command prompt on the client system, enter:

sqlplus

b. The database prompts you for a username and password. Log in as avayadba.

c. Enter this command at the sqlplus command prompt:

select * mo_job;See if data for this job is being populated into the tables.

6. If data for this job is being populated into the tables, consult Analyst troubleshooting for further help.

Historical data tables not being populated with data

A job is running and agents are logged in to one or more dialers but the historical data tables are not being populated with data for a specific job.

To resolve this issue, follow these steps:

1. On the HDSC host system, use check_db to determine if the database is running. If the database is running, go to step 3.

2. If the database is not running, you need to start it using the start_db script. Consult Avaya Proactive Contact Software Reference Scripts for important information on using this script.

3. On the HDCC host system, enter check_mts to check that datapump is running.

4. f the datapump is running, go to the next step. If datapump is not running, you need to run the start_mts script. Consult Avaya Proactive Contact Software Reference Scripts for important information on using this script.

5. Check the mid_tier_log.<ccyymmdd> with today�s date for error messages.

6. Verify that HDCC is writing data to the database by:

a. At the command prompt on the client system, enter:

sqlplus

b. The database prompts you for a username and password. Log in as avayadba.

c. Enter this command at the sqlplus command prompt:

select * mo_job;

See if data for this job is being populated into the tables.

7. If data for this job is being populated into the tables, use the UNIX ps command to make sure there is only one HDCC process running on the Mid-Tier host system.

Page 168: PC4 Troubleshooting Main

166 Maintenance and Troubleshooting Guide March 2008

HDCC is not running

If the HDCC is not running, or fails to stay up after being restarted, follow these steps to resolve the issue:

1. Make sure both logger and serviceMonitor are both running by typing check_mts at the command prompt on the Mid-Tier host system.

2. If either logger of serviceMonitor is not running, use start_mts following the directions in start_mts topic in Avaya Proactive Contact Software Reference Scripts to start either or both binaries. If the problem persists, go to the next step.

3. On the HDSC host system, use check_db to determine if the database is running.

4. If the database is running, go to the next step. If the database is not running, you need to start it using the start_db script. Consult Avaya Proactive Contact Software Reference Scripts for important information on using this script.

5. Check the $VOICEDIR/account/mid_tier_log.ccyymmdd for today�s date for HDCC error messages.

HDSC run problems

The HDSC is not running or fails to stay up after being restarted. To resolve this issue run HDSC in debug mode and observe the output.

No historical data on the dialer

There is no historical data available on the dialer. Either the directory or file is missing, or the Data Manager is not running. To solve this issues, use stop_pds to stop Avaya Proactive Contact and start_pds following the directions in the stop_pds and start_pds topics in Avaya Proactive Contact Software Reference Scripts.

Historical data is incomplete

When historical data is incomplete, follow these steps to resolve the issue:

1. Check to make sure the job has completed before running the report.

2. Check the $VOICEDIR/account/mid_tier_log.ccyymmdd for today�s date for HDCC error messages.

Page 169: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 167

DatabaseOracle provides a mechanism, the online redo log, to recover from database errors. Each online redo log has at least two redo log files that contain redo records, also called redo entries. Each record is made up of a group of change vectors. Each vector is a description of a change made to a single block in the database. For instance, changing a salary value in an employee table, generates a redo record that describes changes to the:

● data segment block for the table

● rollback segment data block

● transaction table of the rollback segments

Note:Note: The Oracle background process Log Writer (LGWR) creates the redo log files in

the redo log buffer of the System Global Area (SGA). Whenever a transaction is committed, LGWR writes the transaction's redo records from the redo log buffer of the SGA to an online redo log file, and a system change number (SCN) is assigned to identify the redo records for each committed transaction.

The online redo log of a database consists of two or more online redo log files. Oracle requires a minimum of two files to guarantee that one is always available for writing while the other is being archived if the system is in ARCHIVELOG mode. LGWR writes to online redo log files in a circular fashion such that when the current online redo log file fills, LGWR begins writing to the next available online redo log file.

Redo records can also be written to an online redo log file before the corresponding transaction is committed. If the redo log buffer fills, or another transaction commits, LGWR flushes all of the redo log entries in the redo log buffer to an online redo log file, even though some redo records may not be committed. If necessary, Oracle can roll back these changes.

Redo entries record data that you can use to reconstruct all changes made to the database, including the rollback segments. Therefore, the online redo log also protects rollback data. When you recover the database using redo data, Oracle reads the change vectors in the redo records and applies the changes to the relevant blocks.

Filled online redo log files are available to LGWR for re-use depending on whether archiving is enabled:

● If archiving is disabled (NOARCHIVELOG mode), a filled online redo log file is available once the changes recorded in it have been written to the data files.

● If archiving is enabled (ARCHIVELOG mode), a filled online redo log file is available to LGWR once the changes recorded in it have been written to the deadfalls and once the file has been archived.

Page 170: PC4 Troubleshooting Main

168 Maintenance and Troubleshooting Guide March 2008

Note:Note: ARCHIVELOG mode is not the default. You have to set it up as part of the admin

job. You can find more details on this entire process in the ORACLE Admin manual. There is a whole section about how you have to plan and configure your system to do this type of logging for recoverability.

Recovering in the event of media failure You can restore a database to the state it was in at the point of failure if the current transaction log file for the database is available and undamaged.

To restore the database to the point of failure:

1. Back up the currently active transaction log. For more information, see Transaction Log Backups in the Oracle documentation.

2. Restore the most recent database backup without recovering the database.

3. If differential backups exist, restore the most recent one.

4. Restore each transaction log backup created since the database or differential backup in the same sequence in which they were created without recovering the database.

5. Apply the most recent log backup (created in Step 1), and recover the database.

! Important:Important: To protect against loss of transactions under the Full Recovery model, the

transaction log must be protected against damage. It is strongly recommended that fault-tolerant disk storage be used for the transaction log.

See also Administering SQL Server/Transaction Log Backups in the Oracle documentation.

● You can set up your database so that you can fully recover data from a previous backup. All the logging you did is relative to the previous backup, it is not a snapshot of the database data taken at intervals of time.

● To do 1., you have to set up your database to log activities from the moment you did the backup to � the moment you do a next backup (for example) (this is the strategy that a dba, has to choose, plan, and configure for his system backup and recovery)

● This option is not the default or something that happens automatically because it is resource consuming and you really have to go through some planning and know what you are doing and be aware you are doing it.

● This is an admin function, not a conceptual function of the database.

Page 171: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 169

Common Oracle errorsIf an error occurs when preforming the procedure in the first part of Dialer Mid-Tier connectivity, make a note of the error number and the exact text of the error message. This contains the solutions to a couple common Oracle error messages.

ORA-12154: TNS: could not resolve the connect identifier

To resolve this issue, follow these steps:

1. In the Avaya Proactive Contact install directory, verify that the ..\Services\3rdParty\Oracle10g\tnsnames.ora file exists. When the user runs the Avaya Proactive Contact Configurator in Health Manager it creates this file. If it does not exist, create it by running the Avaya Proactive Contact Configurator again, then closing Health Manager. If the error message reappears, go to the next step.

2. Verify that there is no other installation of Oracle on the machine. Although Avaya Proactive Contact is designed to be self-contained and should coexist with other Oracle installations, there are some possible points of conflict, particularly if the other Oracle is older than version 10i. For example, if another Oracle installation uses a client profile (SQLnet.ora), this file may prevent the tnsnames.ora file from being discovered.

ORA-12545: Connect failed because target host or object does not exist

To resolve this issue, follow these steps:

1. In the Avaya Proactive Contact install directory, verify that the ..\Services\3rdParty\Oracle10g\tnsnames.ora file contains this line:

HOST = <dialername>

in which <dialername> is either the alias of the dialer or the dialer�s IP address.

2. If the tnsnames.ora file does not contain the line in step 1, add it to the file. If the error message persists, go to the next step.

3. Open Window Explorer.

4. Navigate to the Avaya Proactive Contact install directory.

5. In the ..\Services\3rdParty\Oracle10g directory, double-click sqlplus.exe.

6. At the Enter user-name prompt, type avayapdsdb/avayadba.

7. At the SQL> prompt, type select * from dialerdef; and press ENTER. Make sure you have entered the semi-colon (;).

8. The screen should display something like this:DIALER_ID DIALERNAME_NTXT PACKETTIME_NUM DIALERIP_NTXT---------- -------------------- -------------- ------------------------------SYSTIME_NTXT SYSLINES_NUM SYSAGENTS_NUM SYSJOBS_NUM SYSUPDATETIME_NUM

Page 172: PC4 Troubleshooting Main

170 Maintenance and Troubleshooting Guide March 2008

-------------------- ------------ ------------- ----------- -----------------LASTUPDTIME_NUM--------------- 23 redlab23 1144852359 143.243.248.1232006/4/12 7:32:39 21 108 50 6 1144932555

There is one row of data for each dialer in the pod. Be sure to note the SYSTIME_NTXT data, 2006/4/12 7:32:39 in the example. This time stamp should be current. If it is not, data is not being updated to the database.

End user applicationsThis section covers some general troubleshooting tools and a couple specific troubleshooting scenarios.

AnalystIf there are connectivity issues, see Mid-Tier database network problems. If there are problems with reports such as printing, previewing, or incorrect content, check that these files in the C:\Windows\system32 directory have the listed value for attributes:

Use Windows Explore to navigate to the C:\Windows\system32 directory. Right click on each file name and click Properties to see these attributes.

If the size and version match, the file is most likely the current version.

File name Creation date Time Size Version

crpe32.dll

Friday, February 09, 2001

10:43:51 4587577

8.5.0.217

crwrap32.dll

Thursday, December 10, 1999

23:17:28 66560 7.0.0.8

Implode.dll

Thursday, November 10, 2001

15:42:09 1792018944

Crpaige80.dll

Thursday, November 09, 2000

07:52:00 618496 8.0.1.3

Page 173: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 171

EditorMost Supervisor Editor problems generate a message box with an error message. If such an error occurs note all the details in the message box.

cd.log file

For errors that do not generate a message box, use LogView.exe to view the cd.log file.

Note:Note: If errors occur, select Tools > Increase Logging Level on the LogView main

menu bar to make sure the maximum number of messages are written to the log.

Follow these steps using LogView to troubleshoot the issue:

1. On the main menu select View > Show Code Errors and uncheck the other options.

2. Search the Date/Time column until you find one or more errors that match the same time frame of the reported error.

3. If that isn't possible, make a backup of the cd.log file by copying it to another directory then renaming the copy as cd.bak.

4. Delete the original cd.log file using the LogViewer tool then click Refresh.

5. Perform the same action that caused the reported problems and re-examine the log. If there are no errors, uncheck the Show Code Errors option and check Show Transaction Tracking.

6. Click Refresh.

7. Record any errors that occur.

mid_tier_log files

In systems with a dialer pod, the mid_tier_log.ccyymmdd daily log file is on the master dialer. in such situations to determine the master dialer, check the Windows system�s registry entry for:MyComputer\HKEY_LOCAL_MACHINE\SOFTWARE\AvayaInc\PDS\CommandControl

The entry value should look like this:ORBInitRef"NameService=iioploc://<master_dialer>:23200/NameService

in which <master_dialer> is the name of the master dialer system.

Check the $VOICEDIR/account/mid_tier_log.ccyymmdd for today�s date for Supervisor Editor error messages.

You can also use Health Manager to check the status of the system.

Page 174: PC4 Troubleshooting Main

172 Maintenance and Troubleshooting Guide March 2008

MonitorMonitor, Hierarchy Manager and Analyst use the same dll. This dll, the Mid-Tier data services component , AVMTDSCI.dll, handles real-time data communications between client applications and the dialer database. The AVMTDSCI.dll writes error messages to two logs, avmtdscil0.log and dscHier0.log in an AVMTier directory that the dll creates. Monitor error messages may appear in both logs.

Note:Note: Hierarchy Manager and Analyst error messages only appear in the dscHier0.log

file.

The next couple sections detail a couple common Monitor issues.

Log on to dialer, but no data in Monitor

If the user can log on to the dialer, but no data appears in Monitor, follow these step to resolve the issue:

1. From the Windows Start menu, select Settings > Control Panel > Administrative Tools > Data Sources (ODBC).

2. Click on the System DSN tab.

3. Select AvayaPDSDB from the list of System Data Sources.

4. Click Configure.

5. In the Oracle ODBC Driver Configuration window, click Test Connection.

6. You should see a Connection successful message. Otherwise you see an error message which you should record. If successful, go to the next step.

7. Use Health Manager, Dialer Services > Data to check that HDSC and EVENT_SERVICE are running.

8. If either is not running, use Health Manager to start the process that is not running.

9. On the middle-tier server, use check_db to make sure the database is running.

10. If the database process is not running, use start_db on the server as instructed in Avaya Proactive Contact Software Reference Scripts. If the problem persists, go to the next step.

11. Check the AVMTSDCI.log file or Windows Event Viewer for errors.

Stale Monitor data

If agent states are not being updated or jobs that have stopped are listed as active, the data available to Monitor is stale. Follow these steps to resolve the issue:

1. Use Health Manager, Dialer Services > Data to check that STAT_PUMP is running.

Page 175: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 173

2. If i is not running, use Health Manager to start STAT_PUMP.

3. On the middle-tier server, use check_db to make sure the database is running.

4. If the database process is not running, use start_db on the server as instructed in Avaya Proactive Contact Software Reference Scripts. If the problem persists, go to the next step.

5. Check the AVMTSDCI.log file or Windows Event Viewer for errors.

Page 176: PC4 Troubleshooting Main

174 Maintenance and Troubleshooting Guide March 2008

Page 177: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 175

Error message, source and error description table

The table in this section includes the error message number, source files and a more complete description of the condition that generated the error message.

Error Numbers

Found in these files Extended Description

E????? v_dialer\dialer\src\core\agent.c Timed out waiting for response from porter

E00000 v_dialer\dialer\src\core\job_strter.c Error loading job chain

E00500 v_dialer\dialer\src\core\caller.cv_dialer\dialer\src\callsel\callsel.cv_dialer\dialer\src\core\job_strter.cv_dialer\dialer\src\core\joblib.cv_dialer\dialer\src\core\donotcall.cv_dialer\dialer\src\preprocess\listdist.cv_dialer\dialer\enforcer\src\enforcer.cppv_dialer\dialer\src\swif\exec\swid_main.cv_dialer\dialer\src\core\nuisance.cv_dialer\dialer\src\core\porter.cv_dialer\dialer\src\dbconst\readtape.cv_dialer\dialer\src\core\recall_rmp.cv_dialer\dialer\src\dbmaint\record_ed.cv_dialer\dialer\src\core\switcher.cv_dialer\dialer\src\dbconst\writetape.c

Caught signal number <num>

Page 178: PC4 Troubleshooting Main

176 Maintenance and Troubleshooting Guide March 2008

E00501 v_dialer\admin\src\signalit.cv_dialer\admin\src\termprocess.cv_dialer\dialer\src\utility\agentcheck.cv_dialer\dialer\src\utility\agentcount.cv_dialer\dialer\src\core\ao_recall.cv_dialer\dialer\src\core\beeper.cv_dialer\dialer\src\callsel\callconn.cv_dialer\dialer\src\core\conn_mgr.cv_dialer\dialer\src\dbconst\moj_conv.cv_dialer\dialer\src\utility\list_status.cv_dialer\dialer\DialerServiceActivation\src\DSA.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitor.cxxv_dialer\dialer\src\reports\rpt_mgr\pds_view.cv_dialer\dialer\src\reports\rpt_mgr\rpt_view.c

Caught signal <num> and terminated

Page 179: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 177

E00502 v_dialer\dialer\src\core\caller.cv_dialer\dialer\src\callsel\callsel.cv_dialer\dialer\src\markrec\chkentdt.cv_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\src\core\conn_mgr.cv_dialer\admin\src\createop.cv_dialer\dialer\src\callsel\cseldmp.cv_dialer\dialer\src\callsel\call_scrn.cv_dialer\dialer\src\callsel\call_stgy.cv_dialer\dialer\src\core\agent_misc_util.cv_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\core\jobscrn.cv_dialer\dialer\src\core\listops.cv_dialer\dialer\src\core\port_hndle.cv_dialer\dialer\src\core\screen.cv_dialer\dialer\src\dbconst\moj_conv.cv_dialer\dialer\src\reports\reportgen\reportfmt.cv_dialer\dialer\src\swif\exec\swid_main.cv_dialer\dialer\src\lstextract\ext_list.cv_dialer\dialer\src\preprocess\ij_merge.cv_dialer\ivr\src\ivr_config.cv_dialer\dialer\src\markrec\latelst.cv_dialer\dialer\src\markrec\latemrk.cv_dialer\dialer\src\preprocess\listdist.cv_dialer\dialer\src\editor\master_ed.cv_dialer\dialer\DialerCmdCtrl\AgentLib.cppv_dialer\dialer\src\core\porter.cv_dialer\dialer\src\postupdate\postupdate.cv_dialer\dialer\src\dbmaint\record_ed.cv_dialer\dialer\src\preprocess\setzones.cv_dialer\dialer\src\utility\ziptoarea.cv_dialer\dialer\src\core\screen.c

Failed to allocate memory

Page 180: PC4 Troubleshooting Main

178 Maintenance and Troubleshooting Guide March 2008

E00503 v_dialer\dialer\src\callsel\callconn.cv_dialer\dialer\src\callsel\callsel.cv_dialer\dialer\src\dbconst\selection.cv_dialer\dialer\src\reports\history\hist_rpt.cv_dialer\dialer\src\lstextract\ext_data.cv_dialer\dialer\src\markrec\get_field.cv_dialer\dialer\src\dbconst\readtape.cv_dialer\dialer\src\markrec\set_field.cv_dialer\dialer\src\menu\submenu.cv_dialer\dialer\src\dbconst\writetape.c

Pattern error

E00504 v_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\swif\exec\swid_main.cv_dialer\dialer\src\utility\pds_pg.cv_dialer\dialer\src\dbconst\readtape.cv_dialer\dialer\src\dbconst\writetape.c

Bad argument

E00505 v_dialer\dialer\src\markrec\latelst.c Invalid time format

E00506 v_dialer\dialer\src\markrec\latelst.c Invalid date format

E00507 v_dialer\dialer\src\listserver\listserver.cv_dialer\dialer\DialerCmdCtrl\MasterCfgTable.cppv_dialer\dialer\src\utility\port_start.c

Environment variable not set

E00508 v_dialer\dialer\src\core\caller.cv_dialer\dialer\src\callsel\call_scrn.cv_dialer\dialer\src\core\joblib.cv_dialer\dialer\src\listserver\listserver.cv_dialer\dialer\src\core\porter.cv_dialer\dialer\src\preprocess\setzones.cv_dialer\dialer\src\reports\history\vrecords.c

Mastercfg error

Page 181: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 179

E00509 v_dialer\dialer\src\markrec\chkentdt.cv_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\dbconst\moj_conv.cv_dialer\dialer\src\preprocess\msgmap.cv_dialer\dialer\src\markrec\get_field.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\dialer\src\postupdate\postupdate.cv_dialer\dialer\src\dbmaint\rec_update.cv_dialer\dialer\src\scrnbld\scrnbld.cv_dialer\dialer\src\markrec\set_field.cv_dialer\dialer\src\preprocess\update_cl.cv_dialer\dialer\src\reports\history\vrecords.c

Entry <value> missing/invalid in <filename> file

E00510

E00511 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\callsel\callsel.cv_dialer\dialer\src\markrec\chkentdt.cv_dialer\dialer\src\core\conn_mgr.cv_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\core\listops.cv_dialer\dialer\src\core\operator.cv_dialer\dialer\src\dbmaint\redit_scrn.cv_dialer\dialer\src\preprocess\ij_merge.cv_dialer\dialer\src\markrec\latelst.cv_dialer\dialer\src\dbconst\readtape.cv_dialer\dialer\src\dbmaint\record_ed.cv_dialer\dialer\src\preprocess\setzones.cv_dialer\dialer\src\dbconst\writetape.c

Failed to process file <filename>

E00512 v_dialer\dialer\DialerCmdCtrl\DccsVmValidator.cpp

Audio file name too long

E00513 v_dialer\dialer\src\callsel\callsel.cv_dialer\dialer\src\reports\reportgen\reportfmt.cv_dialer\dialer\src\preprocess\listdist.cv_dialer\dialer\src\utility\pds_pg.cv_dialer\dialer\src\scrnbld\scrnbld.c

Invalid file name

E00514

Page 182: PC4 Troubleshooting Main

180 Maintenance and Troubleshooting Guide March 2008

E00515 v_dialer\admin\src\addgroup.cv_dialer\dialer\src\utility\adump.cv_dialer\dialer\src\core\ao_recall.cv_dialer\dialer\src\callsel\callconn.cv_dialer\dialer\src\core\caller.cv_dialer\dialer\src\callsel\callsel.cv_dialer\dialer\src\markrec\chkentdt.cv_dialer\dialer\src\preprocess\clhashin.cv_dialer\dialer\src\editor\config_ed.cv_dialer\admin\src\createop.cv_dialer\dialer\src\callsel\cseldmp.cv_dialer\dialer\src\core\agent_io_util.cv_dialer\dialer\src\core\agent_tdss_util.cv_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\core\chainhandler.cv_dialer\dialer\src\core\dnc_mark.cv_dialer\dialer\src\core\install_ext.cv_dialer\dialer\src\core\job_strter.cv_dialer\dialer\src\core\listops.cv_dialer\dialer\src\core\screen.c8v_dialer\dialer\src\core\transfer.cv_dialer\dialer\src\dbconst\moj_conv.cv_dialer\dialer\src\pcextract\fileops.cv_dialer\dialer\src\custom\readwrt.cv_dialer\dialer\src\utility\portcorr.cv_dialer\dialer\src\utility\test_help.cv_dialer\library\libdsi\src\rpt_server.cv_dialer\dialer\src\swif\exec\opmoncfg.cv_dialer\dialer\src\utility\edump.cv_dialer\dialer\src\utility\fdictdump.cv_dialer\dialer\src\lettergen\formlet.cv_dialer\dialer\src\markrec\get_field.cv_dialer\dialer\src\preprocess\hsh_dump.cv_dialer\dialer\src\preprocess\ij_merge.cv_dialer\dialer\src\imon\internetmon.cv_dialer\ivr\src\ivr_config.cv_dialer\dialer\src\utility\jobkeys.c

Unable to open file

Page 183: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 181

E00515 v_dialer\dialer\src\markrec\latelst.cv_dialer\dialer\src\markrec\latemrk.cv_dialer\dialer\src\preprocess\listdist.cv_dialer\dialer\src\lettergen\mail_label.cv_dialer\dialer\src\editor\master_ed.cv_dialer\dialer\src\menu\menu.cv_dialer\dialer\src\dbconst\moj_conv.cv_dialer\dialer\src\core\msg_loader.cv_dialer\dialer\DialerServiceActivation\src\DSAIFImpl.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceController.cxxv_dialer\dialer\enforcer\src\enlicense.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cppv_dialer\dialer\DialerCmdCtrl\SptValidatingProcessor_utest.cppv_dialer\dialer\src\core\nuisance.cv_dialer\dialer\src\reports\history\op_hist.cv_dialer\dialer\src\core\porter.cv_dialer\dialer\src\postupdate\postupdate.cv_dialer\dialer\src\utility\print_pif.cv_dialer\dialer\src\dbconst\readtape.cv_dialer\dialer\src\dbmaint\rec_update.cv_dialer\dialer\src\dbmaint\record_ed.cv_dialer\dialer\src\reports\rpt_mgr\rpt_view.cv_dialer\dialer\src\utility\scan.cv_dialer\dialer\src\scrnbld\scrnbld.cv_dialer\dialer\src\markrec\set_field.cv_dialer\dialer\src\menu\submenu.cv_dialer\dialer\src\preprocess\update_cl.cv_dialer\dialer\src\reports\history\vrecords.cv_dialer\dialer\src\dbconst\writetape.cv_dialer\dialer\src\utility\ziptoarea.c

E00516 v_dialer\dialer\DialerServiceActivation\src\DSAIFImpl.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceController.cxx

File did not close

Page 184: PC4 Troubleshooting Main

182 Maintenance and Troubleshooting Guide March 2008

E00517 v_dialer\dialer\src\preprocess\clhashin.cv_dialer\dialer\src\markrec\latelst.cv_dialer\dialer\src\utility\ziptoarea.c

Unable to create file

E00518 v_dialer\dialer\src\callsel\callconn.cv_dialer\dialer\src\callsel\callsel.cv_dialer\dialer\src\callsel\call_scrn.cv_dialer\dialer\src\core\agent_misc_util.cv_dialer\dialer\src\core\agent_sys_util.cv_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\core\screen.cv_dialer\dialer\src\dbconst\moj_conv.cv_dialer\dialer\src\dbmaint\redit_scrn.cv_dialer\dialer\src\pcextract\fileops.cv_dialer\dialer\src\reports\history\op_hist.cv_dialer\dialer\src\markrec\latelst.cv_dialer\dialer\DialerCmdCtrl\DccsAudioFileValidator.cppv_dialer\dialer\src\reports\history\op_hist.cv_dialer\dialer\src\dbconst\readtape.c

<process_name> failed to read from file <filename>

E00519 v_dialer\dialer\src\callsel\callsel.cv_dialer\dialer\src\preprocess\clhashin.cv_dialer\dialer\src\dbconst\moj_conv.cv_dialer\dialer\src\markrec\latelst.cv_dialer\dialer\src\dbconst\writetape.c

Failed to write to file <filename>

E00520 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\src\reports\history\vrecords.c

Failed to lock file

E00521 v_dialer\library\libdsi\src\getnum.c Failed to unlock file

E00522 v_dialer\dialer\src\utility\enq_pty.cv_dialer\dialer\Cmdctrl\HeadsetLib.cppv_dialer\dialer\Cmdctrl\ShmAccess.cpp

Failed to attach shared memory

E00523 v_dialer\library\libdsi\src\conn_queue.c Failed to detach shared memory

E00524 v_dialer\library\libdsi\src\conn_queue.c Failed to remove shared memory

E00525 v_dialer\library\libdsi\src\mqueue.c Failed to get message queue

Page 185: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 183

E00526 v_dialer\library\libdsi\src\mqueue.c Failed to send message

E00527 v_dialer\library\libdsi\src\mqueue.c Unable to receive a message

E00528 v_dialer\library\libdsi\src\mqueue.c Unable to remove message queue

E00529 v_dialer\dialer\src\callsel\callsel.cv_dialer\dialer\src\dbmaint\rec_update.cv_dialer\dialer\src\swif\exec\swid_main.c

Failed to invoke function

E00530 v_dialer\dialer\src\preprocess\clhash.cv_dialer\dialer\src\preprocess\clhashin.cv_dialer\dialer\src\callsel\call_scrn.cv_dialer\dialer\src\core\dnc_mark.cv_dialer\dialer\src\core\listops.cv_dialer\dialer\src\core\screen.cv_dialer\dialer\src\dbmaint\redit_scrn.cv_dialer\dialer\src\reports\reportgen\reportinit.cv_dialer\dialer\src\lstextract\ext_data.cv_dialer\dialer\src\lstextract\ext_list.cv_dialer\dialer\src\utility\fdictdump.cv_dialer\dialer\src\lettergen\formlet.cv_dialer\dialer\src\preprocess\ij_merge.cv_dialer\dialer\src\preprocess\listdist.cv_dialer\dialer\src\lettergen\mail_label.cv_dialer\dialer\src\preprocess\setzones.cv_dialer\dialer\src\preprocess\update_cl.cv_dialer\dialer\src\preprocess\update_upl.cv_dialer\dialer\src\dbconst\writetape.cv_dialer\dialer\src\utility\ziptoarea.c

Unable to open list <calling_list_name>

Page 186: PC4 Troubleshooting Main

184 Maintenance and Troubleshooting Guide March 2008

E00531 v_dialer\dialer\src\preprocess\clhash.cv_dialer\dialer\src\preprocess\clhashin.cv_dialer\dialer\src\callsel\call_scrn.cv_dialer\dialer\src\core\dnc_mark.cv_dialer\dialer\src\core\screen.cv_dialer\dialer\src\dbmaint\redit_scrn.cv_dialer\dialer\src\preprocess\ij_merge.cv_dialer\dialer\src\preprocess\listdist.cv_dialer\dialer\src\postupdate\postupdate.cv_dialer\dialer\src\preprocess\setzones.cv_dialer\dialer\src\preprocess\update_cl.cv_dialer\dialer\src\preprocess\update_upl.cv_dialer\dialer\src\dbconst\writetape.cv_dialer\dialer\src\utility\ziptoarea.c

Failed to read calling list definition

E00532 v_dialer\dialer\src\markrec\chkentdt.cv_dialer\dialer\src\preprocess\clhash.cv_dialer\dialer\src\preprocess\clhashin.cv_dialer\dialer\src\preprocess\de_reject.cv_dialer\dialer\src\callsel\call_scrn.cv_dialer\dialer\src\core\listops.cv_dialer\dialer\src\core\screen.cv_dialer\dialer\src\lstextract\ext_data.cv_dialer\dialer\src\preprocess\ij_merge.cv_dialer\dialer\src\markrec\latelst.cv_dialer\dialer\src\markrec\latemrk.cv_dialer\dialer\src\preprocess\listdist.cv_dialer\dialer\src\lettergen\mail_label.cv_dialer\dialer\src\preprocess\setzones.cv_dialer\dialer\src\preprocess\update_cl.cv_dialer\dialer\src\preprocess\update_upl.cv_dialer\dialer\src\utility\ziptoarea.c

Field <name> not defined in calling list <filename>

E00533 v_dialer\dialer\src\preprocess\listdist.c Field has incorrect length

E00534 v_dialer\dialer\src\core\agent_tdss_util.cv_dialer\dialer\src\core\transfer.cv_dialer\dialer\src\dbconst\readtape.c

Not a calling list

Page 187: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 185

E00535 v_dialer\dialer\src\callsel\callsel.cv_dialer\dialer\src\dbconst\readtape.cv_dialer\dialer\src\dbconst\writetape.c

No space on file system

E00536 v_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\dbconst\moj_conv.c

Failed to initialize keyboard

E00537 v_dialer\dialer\src\core\api_jobctl.c Failed to initialize screen environment

E00538 v_dialer\dialer\src\core\api_jobctl.c Failed to setup command keys

E00539 v_dialer\dialer\src\core\api_jobctl.c Failed to create jobmon graphical user interface (GUI)

E00540 v_dialer\library\libui\src\vlui.c Failed to create window pointer

E00541 v_dialer\dialer\src\core\screen.cv_dialer\dialer\src\dbmaint\redit_scrn.cv_dialer\dialer\src\utility\vfiles.c

Unable to open keys file

E00542 v_dialer\dialer\src\preprocess\clhashin.cv_dialer\dialer\src\dbconst\selection.c

Field not defined in calling list

E00543 v_dialer\dialer\src\preprocess\clhash.c Field not defined in calling list

E00544 v_dialer\dialer\src\core\listops.c Invalid pattern

E00545 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\ao_recall.cv_dialer\dialer\src\core\caller.cv_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\src\core\conn_mgr.cv_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\agent_misc_util.cv_dialer\dialer\src\core\chainhandler.cv_dialer\dialer\src\core\job_strter.cv_dialer\dialer\src\core\joblib.cv_dialer\dialer\src\core\listops.cv_dialer\dialer\src\core\op_handler.cv_dialer\dialer\src\core\operator.cv_dialer\dialer\src\core\port_hndle.cv_dialer\dialer\src\core\scripter.cv_dialer\dialer\src\core\jobctrl.cv_dialer\dialer\src\core\recall_rmp.c

Process unable to send <string> to <process_name>

E00546 v_dialer\library\libutil\src\checkdir.c Failed to create directory

Page 188: PC4 Troubleshooting Main

186 Maintenance and Troubleshooting Guide March 2008

E00547 v_dialer\library\libutil\src\checkdir.c Non-directory in directory path

E00548 v_dialer\dialer\src\core\conn_mgr.cmidtier\unixdev\services\src\ShmDataReader.cpp

Missing or invalid entry in file

E00549 v_dialer\dialer\src\core\conn_mgr.cv_dialer\dialer\src\listserver\listserver.cmidtier\unixdev\services\src\ShmDataReader.cpp

<op_name> operation failed for file <file_name>

E00550 midtier\unixdev\services\src\ShmDataReader.cpp

Invalid entry for <name> in <filename>

E00551

E00552 v_dialer\dialer\src\listserver\listserver.cmidtier\unixdev\services\src\ShmDataReader.cpp

Failed to open directory <dir_name>

E00553 midtier\unixdev\services\src\ShmDataReader.cpp

File <filename> does not exist

E00554 v_dialer\dialer\src\listserver\listserver.c <opname> operation failed

E00555 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.cv_dialer\dialer\src\\callsel\md_callsel.cmidtier\unixdev\services\src\EventServiceIF_i.cppv_dialer\dialer\DialerCmdCtrl\expr_utest.cpp

<string>-<string>

E00556 v_dialer\library\libutil++\src\ReadOnlyFile.cpp

File <filename> exists, but is not readable by user <user_name

E00557 v_dialer\library\libutil++\src\WriteOnlyFile.cpp

File <filename> exists, but cannot be written by user <user_name

E10012 v_dialer\library\libdsi\src\script_lng.c Pattern error at line <number>

E10013 v_dialer\library\libdsi\src\sock_stream.cpp Cannot find service in /etc/services

E10014 v_dialer\library\libdsi\src\sock_stream.cpp Socket call failed

E10015 v_dialer\library\libdsi\src\sock_stream.cpp Unable to bind to local address

E10016 v_dialer\library\libdsi\src\sock_stream.cpp Unable to setup listen on socket

Page 189: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 187

E10017 v_dialer\library\libdsi\src\sock_stream.cpp Unable to accept connection on socket

E10018 v_dialer\library\libdsi\src\sock_stream.cpp Unable to connect to socket

E10019 v_dialer\library\libdsi\src\sock_stream.cpp Unable to send data to socket

E10200 v_dialer\library\libdsi\src\getnum.c Unequal phone number field lengths in file <filename>

E10201 v_dialer\dialer\src\core\operator.c Invalid line selection

E10600

E10601

E10602 v_dialer\dialer\src\core\job_strter.cdialer_client\Redwood\VBApps\Editor\MDIForm1.frm

File <filename> does not exist

E10603 - E10628

E10629 dialerclient\Redwood\VBApps\Editor\MDIForm1.frmdialerclient\Redwood\VBApps\Editor\Classes\CJobs.cls

Selection list not available for use

E10630 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

STATUSFLAG field missing

E10631 - E10648

E10649 v_dialer\library\libdsi\src\job_cntrl.c Failed to find linked job file

E10650 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\library\libdsi\src\job_cntrl.c

Linking between virtual agent jobs and non-virtual jobs is not permitted

E10651-E10653

E10654 dialerclient\Redwood\VBApps\Editor\MDIForm1.frmdialerclient\Redwood\VBApps\Editor\Classes\CJobs.cls

Could not verify selection list for job

E10655 dialerclient\Redwood\VBApps\Editor\MDIForm1.frmdialerclient\Redwood\VBApps\Editor\Classes\CJobs.cls

Could not verify selection list for job

Page 190: PC4 Troubleshooting Main

188 Maintenance and Troubleshooting Guide March 2008

E10656 dialerclient\Redwood\VBApps\Editor\MDIForm1.frmdialerclient\Redwood\VBApps\Editor\Classes\CJobs.cls

Selection list not created with this calling list

E10657-E10659

E10660- E10667

E10800-E10805

E10806 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Failed to read file header

E10807

E10808 v_dialer\library\libutil++\src\KeywordValue.cppv_dialer\library\libutil++\src\mbcs_string.cppv_dialer\library\libutil++\src\SerializableErrorRev_dialer\dialer\src\core\porter.cppv_dialer\library\libutil++\src\SerializableKvErrorStorage.cpp

agent - Failed to read from file <name>

E10809-E10824

E10850 v_dialer\library\libdsi\src\claccess.c Unable to open list <calling_list_name>

E10851 v_dialer\library\libdsi\src\claccess.c Unable to access host <name> using name

E10852 v_dialer\library\libdsi\src\claccess.c Socket failed

E10853 v_dialer\library\libdsi\src\claccess.c Socket connection to list server running on <name> failed

E10854 v_dialer\library\libdsi\src\claccess.c Attempt to store list_client on host failed

E10855 v_dialer\library\libdsi\src\claccess.c Write error

E10856 v_dialer\library\libdsi\src\claccess.c clstat <xfd> failed

E10857 v_dialer\library\libdsi\src\claccess.c Clear fdict <number> failed

E10858 v_dialer\library\libdsi\src\claccess.c Unable to access host <name> using name

Page 191: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 189

E10859 v_dialer\library\libdsi\src\cllaccess.c Bad file descriptor <num>

E10860 v_dialer\library\libdsi\src\claccess.c File corruption or record size mismatch detected in calling list (name>

E10861 v_dialer\library\libdsi\src\cllaccess.c Failed to remove file <filename>

E10900 v_dialer\library\libdsi\src\conn_crit.c Mastercfg error

E11000 v_dialer\library\libcallsel\src\CallStgyLib.cppv_dialer\library\libdsi\src\cstgy.c

Invalid delay specification

E11001 v_dialer\library\libcallsel\src\CallStgyLib.cppv_dialer\library\libdsi\src\cstgy.c

Recall attempt can�t exceed <num>

E11002 v_dialer\library\libcallsel\src\CallStgyLib.cppv_dialer\library\libdsi\src\cstgy.c

Invalid recall code <code>

E11003 v_dialer\library\libutil++\src\FileMasterConfig.cppv_dialer\library\libdsi\src\cstgy.c

Failed to determine max number of phones

E11004 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Failed to determine max number of phones

E11005 v_dialer\library\libcallsel\src\CallStgyLib.cppv_dialer\library\libdsi\src\cstgy.c

Gap found between selection criteria lines

E11006 v_dialer\library\libcallsel\src\CallStgyLib.cppv_dialer\library\libdsi\src\cstgy.c

Extra comma in selection criteria

E11007 v_dialer\library\libcallsel\src\CallStgyLib.cppv_dialer\library\libdsi\src\cstgy.c

Invalid phone <number>

E11008 v_dialer\library\libcallsel\src\CallStgyLib.cppv_dialer\library\libdsi\src\cstgy.c

Field name <name> is invalid

E11009 v_dialer\library\libcallsel\src\CallStgyLib.cppv_dialer\library\libdsi\src\cstgy.c

Invalid field value <value>

Page 192: PC4 Troubleshooting Main

190 Maintenance and Troubleshooting Guide March 2008

E11010 v_dialer\library\libcallsel\src\CallStgyLib.cppv_dialer\library\libdsi\src\cstgy.c

Invalid logical connector <name>

E11011 v_dialer\library\libcallsel\src\CallStgyLib.cpp

Invalid time zone character <char>

E11012

E11013 v_dialer\library\libcallsel\src\CallStgyLib.cppv_dialer\library\libdsi\src\cstgy.c

Invalid ring count <num>

E11014 v_dialer\library\libcallsel\src\CallStgyLib.cppv_dialer\library\libdsi\src\cstgy.c

Invalid call detection mode <name>

E11015 v_dialer\library\libcallsel\src\CallStgyLib.cppv_dialer\library\libdsi\src\cstgy.c

Invalid delay specification

E12000 v_dialer\library\libdsi\src\getnum.c Unequal phone number field lengths in file <name>

E12001

E12100 v_dialer\library\libutil\src\molocale.c Molocale - unknown language name <lang>

E12101 v_dialer\library\libutil\src\molocale.c Molocale - failed to set locale <name>

E12150 v_dialer\library\libdsi\src\pvrs_helper.c Preview record search failed to initialize

E12151

E12152 v_dialer\library\libdsi\src\pvrs_helper.cv_dialer\dialer\src\dbmaint\record_ed.c

No previous record

E12153 v_dialer\library\libdsi\src\pvrs_helper.cv_dialer\dialer\src\dbmaint\record_ed.c

No more records

E12154 v_dialer\dialer\src\core\oper_pvrs.cv_dialer\dialer\src\dbmaint\record_ed.c

Fail to load record

E12155 v_dialer\dialer\src\core\oper_pvrs.c Record currently in use

E12156 v_dialer\library\libdsi\src\pvrs_helper.c No record found

E12200-E12203

Page 193: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 191

E12400 v_dialer\library\libdsi\src\keystroke.cv_dialer\library\libutil\src\tsystem.c

tget returned error number <num> raising signal <num>

E12600 v_dialer\library\libdsi\src\map_dict.cv_dialer\library\libcallsel\src\map_dict2.cpp

Calling list <name> is not in shared memory

E12601 v_dialer\library\libdsi\src\map_dict.cv_dialer\library\libcallsel\src\map_dict2.cpp

Calling list line count does not match shared memory

E12800 v_dialer\library\libdsi\src\map_scrn.c Failed to find screen <name>

E13000 v_dialer\library\libdsi\src\mqueue.c IPC - invalid input argument

E13001 v_dialer\library\libdsi\src\mqueue.c IPC - invalid ipc entry

E13002

E13003 v_dialer\library\libdsi\src\mqueue.c Invalid ipc number <num>

E13004 v_dialer\library\libdsi\src\mqueue.c Warning: CFRM message truncated

E13005 v_dialer\library\libdsi\src\mqueue.c Timed out waiting for <string> confirmation

E13006 v_dialer\library\libdsi\src\mqueue.c Response message too long

E13007 v_dialer\library\libdsi\src\mqueue.c IPC - Failed to open opmon message queue

E13008 v_dialer\library\libdsi\src\mqueue.c <process_name> Failed on semaphore removal, err=<num> key=<num>

E13009 v_dialer\library\libdsi\src\mqueue.c <process_name> - Failed on semaphore operation, err <err_num> key = <sem_key_id> code = <op_code>

E13010 v_dialer\library\libdsi\src\mqueue.c <process_name> - Accessing bad semaphore

E13011 v_dialer\library\libdsi\src\mqueue.c <process_name> - Failed to open semaphore, err(<num>)

E13200 v_dialer\library\libdsi\src\opident.c Headset value (<headset_value>, <return_value>) out of bound

E13201 v_dialer\library\libdsi\src\opident.c Headset <id_num> not specified in dgswitch.cfg file

Page 194: PC4 Troubleshooting Main

192 Maintenance and Troubleshooting Guide March 2008

E13400

E13401

E13402 v_dialer\library\libdsi\src\phonefmt.c Missing prefix

E13403 v_dialer\library\libdsi\src\phonefmt.c Missing line type

E13404 v_dialer\library\libdsi\src\phonefmt.c Missing or invalid num of chars to strip

E13405

E13406 v_dialer\library\libdsi\src\phonefmt.c Missing suffix

E13407 v_dialer\library\libdsi\src\phonefmt.cv_dialer\library\libdsi\src\vlloccall.c

Duplicate ALL phone numbers specification

E13408 v_dialer\library\libdsi\src\phonefmt.c Phone number too long

E13409 v_dialer\library\libdsi\src\phonefmt.c Phone number too long

E13410 v_dialer\library\libdsi\src\phonefmt.c Missing std to dial phone number format

E13411 v_dialer\library\libdsi\src\phonefmt.c Invalid use of ALL phone numbers specification

E13412 v_dialer\library\libdsi\src\phonefmt.c Missing phone numbers

E13600 v_dialer\library\libdsi\src\rpt_server.c Report failed, system out of space

E13800 v_dialer\library\libdsi\src\swcfg_tbl.c Invalid headset number <num> <line>

E13801 v_dialer\library\libdsi\src\swcfg_tbl.c Headset port number <num> out of range

E13802 v_dialer\library\libdsi\src\swcfg_tbl.c Normal trunk port number <num> out of range

E13803 v_dialer\library\libdsi\src\swcfg_tbl.c Invalid normal trunk equipment number <num>

E13804

E13805 v_dialer\library\libdsi\src\swcfg_tbl.c Invalid normal trunk equipment number <num>

E13806

E13807 v_dialer\library\libdsi\src\swcfg_tbl.c Failed to process line (<line_buffer_name>)

E14100

Page 195: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 193

E14101

E14200 v_dialer\library\libdsi\src\vlloccall.c Missing delay specification

E14201 v_dialer\library\libdsi\src\phonefmt.cv_dialer\library\libdsi\src\vlloccall.c

Missing or invalid low range

E14202 v_dialer\library\libdsi\src\phonefmt.cv_dialer\library\libdsi\src\vlloccall.c

Invalid range character

E14203 v_dialer\library\libdsi\src\phonefmt.cv_dialer\library\libdsi\src\vlloccall.c

Missing high range

E14204 v_dialer\library\libdsi\src\vlloccall.c Invalid delay specification

E14205 v_dialer\library\libdsi\src\vlloccall.c Missing completion code

E14206 v_dialer\library\libdsi\src\vlloccall.c Missing completion code

E14207 v_dialer\library\libdsi\src\vlloccall.c Range does not come after previous range

E14208 v_dialer\library\libdsi\src\vlloccall.c Missing limit

E14209 v_dialer\library\libdsi\src\phonefmt.cv_dialer\library\libdsi\src\vlloccall.c

future use - phonefmt.cfg

E14210 v_dialer\library\libdsi\src\vlloccall.c Missing time zone specification for country <num>

E14211 v_dialer\library\libdsi\src\vlloccall.c Missing or invalid time zone designation

E14212 v_dialer\library\libdsi\src\vlloccall.c Missing or invalid reject phone number pattern

E14213 v_dialer\library\libdsi\src\vlloccall.c Missing or invalid reject phone number pattern

E14214 v_dialer\library\libdsi\src\vllocmisc.cv_dialer\library\libdsi\src\vllocport.c

Duplicate country specified

E14215 v_dialer\library\libdsi\src\vllocmisc.cv_dialer\library\libdsi\src\vllocport.c

Invalid answer delay time

E14216 v_dialer\library\libdsi\src\vllocport.c Invalid DAA type

E14217 v_dialer\library\libdsi\src\vllocport.c Invalid VM2 locale code

E14218 v_dialer\library\libdsi\src\vlloccall.c Invalid phone number length

E14219 v_dialer\library\libdsi\src\vlloccall.c Rejected phone number (L<num>)

Page 196: PC4 Troubleshooting Main

194 Maintenance and Troubleshooting Guide March 2008

E14220 v_dialer\library\libdsi\src\vlloccall.c Cannot find time zone for phone number

E14221 v_dialer\library\libdsi\src\vllocport.c Invalid offhook retry delay

E14222 v_dialer\library\libdsi\src\vllocport.c Invalid wait limit

E14400

E14401 v_dialer\dialer\src\preprocess\ij_merge.cv_dialer\library\libcallsel\src\CallSelLib.cppv_dialer\library\libdsi\src\cselect.c

E14402 v_dialer\library\libcallsel\src\CallSelLib.cppv_dialer\library\libdsi\src\cselect.c

E14404 v_dialer\library\libcallsel\src\CallSelLib.cppv_dialer\library\libdsi\src\cselect.c

E14405 v_dialer\library\libcallsel\src\CallSelLib.cppv_dialer\library\libdsi\src\cselect.c

E14406 v_dialer\library\libcallsel\src\CallSelLib.cppv_dialer\library\libdsi\src\cselect.c

E14407 v_dialer\library\libcallsel\src\CallSelLib.cppv_dialer\library\libdsi\src\cselect.c

E14408 v_dialer\library\libcallsel\src\CallSelLib.cppv_dialer\library\libdsi\src\cselect.c

E14409 v_dialer\library\libdsi\src\conn_queue.c

E14410 v_dialer\library\libdsi\src\conn_queue.c

E14800 v_dialer\library\libutil\src\tcap.c

E14801 v_dialer\library\libutil\src\tcap.c

E14802 v_dialer\library\libutil\src\tcap.c

E14900 v_dialer\library\libutil\src\terminal.c

E14901 v_dialer\library\libutil\src\terminal.c

E15200 v_dialer\library\libui\src\vlui.c

Page 197: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 195

E15201 v_dialer\library\libui\src\vlui.c

E15202 v_dialer\library\libui\src\vlui.c

E15203 v_dialer\library\libui\src\vlui.c

E15204 v_dialer\library\libui\src\vlui.c

E15205 v_dialer\library\libui\src\vlui.c

E15206 v_dialer\library\libui\src\vlui.c

E15400 v_dialer\library\libdsi\src\bsrch.c

E15401 v_dialer\library\libdsi\src\bsrch.c

E15402 v_dialer\library\libdsi\src\bsrch.c

E15403 v_dialer\library\libdsi\src\bsrch.c

E15404 v_dialer\library\libdsi\src\bsrch.c

E15420 v_dialer\library\libdsi\src\bsrch.c

E15421 v_dialer\library\libdsi\src\bsrch.c

E15422 v_dialer\library\libdsi\src\bsrch.c

E15424 v_dialer\library\libdsi\src\bsrch.c

E16000 v_dialer\library\libutil\src\labfdctry.c

E16100 v_dialer\library\libutil\src\labfile.c

E16101 v_dialer\library\libutil\src\labfile.c

E16102 v_dialer\library\libutil\src\labfile.c

E16400 v_dialer\library\libutil\src\preftree.c

E16401 v_dialer\library\libutil\src\preftree.c

E16402 v_dialer\library\libutil\src\preftree.c

E16403 v_dialer\library\libutil\src\preftree.c

E16404 v_dialer\library\libutil\src\preftree.c

E16405 v_dialer\library\libutil\src\preftree.c

E16406 v_dialer\library\libutil\src\preftree.c

E16407 v_dialer\library\libutil\src\preftree.c

E16408 v_dialer\library\libutil\src\preftree.c

E16409 v_dialer\library\libutil\src\preftree.c

Page 198: PC4 Troubleshooting Main

196 Maintenance and Troubleshooting Guide March 2008

E16410 v_dialer\library\libutil\src\preftree.c

E16411 v_dialer\library\libutil\src\preftree.c

E16500 v_dialer\library\libutil\src\hash.c

E16501 v_dialer\library\libutil\src\hash.c

E16600 v_dialer\library\libutil\src\expr.c

E16601 v_dialer\library\libutil\src\expr.c

E16602 v_dialer\library\libutil\src\expr.c

E16603 v_dialer\library\libutil\src\expr.c

E16604 v_dialer\library\libutil\src\expr.c

E16605 v_dialer\library\libutil\src\expr.c

E16606 v_dialer\library\libutil\src\expr.c

E16607 v_dialer\library\libutil\src\expr.c

E16608 v_dialer\library\libutil\src\expr.c

E16609 v_dialer\library\libutil\src\expr.c

E16610 v_dialer\library\libutil\src\expr.c

E16611 v_dialer\dialer\DialerCmdCtrl\expr_utest.cpp

E16612 v_dialer\library\libutil\src\expr.c

E16620 v_dialer\library\libutil\src\expr.c

E16621 v_dialer\library\libutil\src\expr.c

E16800 v_dialer\library\libutil\src\undefined.c

E16900 v_dialer\library\libutil\src\exec_prog.c

E16901 v_dialer\library\libutil\src\exec_prog.c

E16902 v_dialer\library\libutil\src\exec_prog.c

E16903 v_dialer\library\libutil\src\exec_prog.c

E16904 v_dialer\library\libutil\src\exec_prog.c

E16905 v_dialer\library\libutil\src\exec_prog.c

E16906 v_dialer\library\libutil\src\exec_prog.c

E16907 v_dialer\library\libutil\src\exec_prog.c

Page 199: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 197

E16908 v_dialer\library\libutil\src\exec_prog.c

E16909 v_dialer\library\libutil\src\exec_prog.c

E16910 v_dialer\library\libutil\src\exec_prog.c

E16911 v_dialer\library\libutil\src\exec_prog.c

E16912 v_dialer\library\libutil\src\exec_prog.c

E17000 v_dialer\library\libutil\src\account.cv_dialer\library\libutil++\src\account_r.c

E17001

E17002

E17003 v_dialer\dialer\DialerCmdCtrl\AgentLib.cpp

E17004

E17005 v_dialer\library\libutil\src\config.c

E17100

E17101

E18200 v_dialer\library\libswif\src\port_dg.c

E18201 v_dialer\library\libswif\src\port_dg.c

E18202 v_dialer\library\libswif\src\port_dg.c

E18203 v_dialer\dialer\src\core\msg_loader.cv_dialer\library\libswif\src\port_dg.c

E18204 v_dialer\library\libswif\src\port_dg.c

E18205 v_dialer\library\libswif\src\port_dg.c

E18206 v_dialer\library\libswif\src\port_dg.c

E18207 v_dialer\library\libswif\src\port_dg.c

E18208 v_dialer\library\libswif\src\port_dg.c

E18209 v_dialer\library\libswif\src\port_dg.c

E18210 v_dialer\library\libswif\src\port_dg.c

E18211

E18212 v_dialer\library\libswif\src\port_dg.c

E18213 v_dialer\library\libswif\src\port_dg.c

Page 200: PC4 Troubleshooting Main

198 Maintenance and Troubleshooting Guide March 2008

E18214 v_dialer\library\libswif\src\port_dg.c

E18215 v_dialer\library\libswif\src\port_dg.c

E18216

E18217

E18218

E18219 v_dialer\library\libswif\src\port_dg.c

E18220 v_dialer\library\libswif\src\port_dg.c

E18221 v_dialer\library\libswif\src\port_dg.c

E18222 v_dialer\library\libswif\src\port_dg.c

E18223 v_dialer\library\libswif\src\port_dg.c

E18224 v_dialer\library\libswif\src\port_dg.c

E18225 v_dialer\library\libswif\src\port_dg.c

E18226 v_dialer\library\libswif\src\port_dg.c

E18227 v_dialer\library\libswif\src\port_dg.c

E18228 v_dialer\library\libswif\src\port_dg.c

E18400 v_dialer\library\libswif\src\swid.c

E18401 v_dialer\library\libswif\src\swid.c

E18402 v_dialer\library\libswif\src\swid.c

E18403 v_dialer\library\libswif\src\swid.c

E18404 v_dialer\library\libswif\src\swid.c

E18405 v_dialer\library\libswif\src\swid.c

E18406 v_dialer\library\libswif\src\swid.c

E18407 v_dialer\library\libswif\src\swid.c

E18408 v_dialer\library\libswif\src\swid.c

E18409 v_dialer\library\libswif\src\swid.c

E18410 v_dialer\library\libswif\src\swid.c

E18411 v_dialer\library\libswif\src\swid.c

E18412 v_dialer\library\libswif\src\swid.c

E18413 v_dialer\library\libswif\src\swid.c

Page 201: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 199

E18414 v_dialer\library\libswif\src\swid.c

E18415 v_dialer\library\libswif\src\swid.c

E18416 v_dialer\library\libswif\src\swid.c

E19000 v_dialer\library\libswif\src\swie.c

E19001 v_dialer\library\libswif\src\swie.c

E19002 v_dialer\library\libswif\src\swie.c

E19003 v_dialer\library\libswif\src\swie.c

E19004 v_dialer\library\libswif\src\swie.c

E19005 v_dialer\library\libswif\src\swie.c

E19006 v_dialer\library\libswif\src\swie.c

E19007 v_dialer\library\libswif\src\swie.c

E19200 v_dialer\library\libswif\src\swiq.c

E19201 v_dialer\library\libswif\src\swiq.c

E19400 v_dialer\library\libswif\src\switch_dg.c

E19401 v_dialer\library\libswif\src\switch_dg.c

E19402 v_dialer\library\libswif\src\switch_dg.c

E19403 v_dialer\library\libswif\src\switch_dg.c

E19404 v_dialer\library\libswif\src\switch_dg.c

E19405 v_dialer\library\libswif\src\switch_dg.c

E19406 v_dialer\library\libswif\src\switch_dg.cv_dialer\library\libswif\src\port_sd.c

E19407 v_dialer\library\libswif\src\switch_dg.c

E19408 v_dialer\library\libswif\src\switch_dg.c

E19600 v_dialer\library\libswif\src\swix.c

E19601 v_dialer\library\libswif\src\swix.c

E19602 v_dialer\library\libswif\src\swix.c

E19603 v_dialer\library\libswif\src\swix.c

E19604 v_dialer\library\libswif\src\swix.c

E19605 v_dialer\library\libswif\src\swix.c

Page 202: PC4 Troubleshooting Main

200 Maintenance and Troubleshooting Guide March 2008

E19606 v_dialer\library\libswif\src\swix.c

E19607 v_dialer\library\libswif\src\swix.c

E19608 v_dialer\library\libswif\src\swix.c

E19609 v_dialer\library\libswif\src\swix.c

E25000 v_dialer\dialer\src\callsel\call_scrn.c

E25001 v_dialer\dialer\src\callsel\call_scrn.c

E25002 v_dialer\dialer\src\callsel\call_scrn.c

E25003 v_dialer\dialer\src\callsel\callsel.cv_dialer\dialer\src\core\agent_misc_util.c

E25004 v_dialer\dialer\src\callsel\call_scrn.c

E25005 v_dialer\dialer\src\callsel\call_scrn.c

E25006

E25007 v_dialer\dialer\src\callsel\call_scrn.c

E25008

E25009 v_dialer\dialer\src\callsel\call_scrn.c

E25010 v_dialer\dialer\src\callsel\call_scrn.c

E25011 v_dialer\dialer\src\callsel\call_scrn.c

E25012

E25013 v_dialer\dialer\src\callsel\call_scrn.c

E25014 v_dialer\dialer\src\callsel\call_scrn.c

E25015 v_dialer\dialer\src\callsel\call_scrn.c

E25016 v_dialer\dialer\src\callsel\call_scrn.c

E25017 v_dialer\dialer\src\callsel\call_scrn.c

E25018 v_dialer\dialer\src\callsel\call_scrn.c

E25019 v_dialer\dialer\src\callsel\callsel.c

E25020 v_dialer\dialer\src\callsel\callsel.c

E25021 v_dialer\dialer\src\callsel\callsel.c

E25022 v_dialer\dialer\src\callsel\callsel.c

E25023 v_dialer\dialer\src\callsel\callsel.c

Page 203: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 201

E25024 v_dialer\dialer\src\callsel\call_scrn.c

E25025 v_dialer\dialer\src\callsel\call_scrn.c

E25026 v_dialer\dialer\src\callsel\callsel.c

E25027

E25028 v_dialer\dialer\src\callsel\callsel.c

E25029 v_dialer\dialer\src\callsel\call_scrn.c

E25030

E25031 v_dialer\library\libcallsel\src\cllcallsel.cpp

E25032 v_dialer\library\libcallsel\src\cllcallsel.cpp

E25501 v_dialer\dialer\src\callsel\callconn.c

E25502 v_dialer\dialer\src\callsel\callconn.c

E25503 v_dialer\dialer\src\callsel\callconn.c

E25504 v_dialer\dialer\src\core\ao_recall.cv_dialer\dialer\src\callsel\callconn.c

E25505 v_dialer\dialer\src\callsel\callconn.c

E27000 midtier\unixdev\ServiceMonitor\src\ServiceMonitor_ServiceController.cxxmidtier\unixdev\SysHealth\src\SystemHealthImpl.cppv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitorIFImpl.cxx

E27100 midtier\unixdev\ServiceMonitor\src\ServiceMonitor_ServiceController.cxxmidtier\unixdev\ServiceMonitor\src\ServiceMonitor_ServiceMonitorIFImpl.cxxmidtier\unixdev\SysHealth\src\SystemHealthImpl.cppv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitorIFImpl.cxx

E27200

Page 204: PC4 Troubleshooting Main

202 Maintenance and Troubleshooting Guide March 2008

E27300 midtier\unixdev\ServiceActivation\src\SARequest.cxxmidtier\unixdev\ServiceActivation\src\ServiceActivationIFImpl.cxxmidtier\unixdev\ServiceMonitor\src\ServiceMonitor_ServiceMonitorIFImpl.cxxv_dialer\dialer\DialerServiceActivation\src\DSARequest.cxx

E28000 v_dialer\dialer\src\core\switcher.c Failed to initialize switcher

E28100 v_dialer\dialer\src\core\driver.c Failed to attach shared memory

E28101 v_dialer\dialer\src\core\driver.c invalid channel number <string>

E28102

E28103 v_dialer\dialer\src\core\driver.c

E28104 v_dialer\dialer\src\core\driver.c

E28105

E28106 v_dialer\dialer\src\core\driver.c

E28107 v_dialer\dialer\src\core\driver.c

E28108 v_dialer\dialer\src\core\driver.c

E28109 v_dialer\dialer\src\core\driver.c

E28200 v_dialer\dialer\src\core\conn_mgr.c

E28201 v_dialer\dialer\src\core\conn_mgr.c

E28202 v_dialer\dialer\src\core\conn_mgr.c

E28203 v_dialer\dialer\src\core\conn_mgr.c

E28204 v_dialer\dialer\src\core\conn_mgr.c

E28205 v_dialer\dialer\src\core\conn_mgr.c

E28206 v_dialer\dialer\src\core\conn_mgr.c

E28207 v_dialer\dialer\src\core\conn_mgr.c

E28208 v_dialer\dialer\src\core\conn_mgr.c

E28209 v_dialer\dialer\src\core\conn_mgr.c

E28210 v_dialer\dialer\src\core\conn_mgr.c

E28211 v_dialer\dialer\src\core\conn_mgr.c

Page 205: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 203

E28300

E28301 v_dialer\dialer\src\core\recall_rmp.c

E28302 v_dialer\dialer\src\core\recall_rmp.c

E28303 v_dialer\dialer\src\core\recall_rmp.c

E28304 v_dialer\dialer\src\core\recall_rmp.c

E28305 v_dialer\dialer\src\core\recall_rmp.c

E28306 v_dialer\dialer\src\core\recall_rmp.c

E28307 v_dialer\dialer\src\core\recall_rmp.c

E28308 v_dialer\dialer\src\core\recall_rmp.c

E28309 v_dialer\dialer\src\core\recall_rmp.c

E28310 v_dialer\dialer\src\core\listops.cv_dialer\dialer\src\core\recall_rmp.c

E28400 v_dialer\dialer\src\core\caller.cv_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E28401 v_dialer\dialer\src\core\caller.cv_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E28402 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E28404 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\src\core\listops.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E28405 v_dialer\dialer\src\core\caller.cv_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E28406 v_dialer\dialer\src\core\listops.c

E28407 v_dialer\dialer\src\core\listops.c

Page 206: PC4 Troubleshooting Main

204 Maintenance and Troubleshooting Guide March 2008

E28408 v_dialer\dialer\src\core\caller.cv_dialer\dialer\src\core\nuisance.c

E28409 v_dialer\dialer\src\core\caller.c

E28410 v_dialer\dialer\src\core\caller.c

E28411 v_dialer\dialer\src\core\caller.c

E28412 v_dialer\dialer\src\core\caller.c

E28413, E28414

E28415 v_dialer\dialer\src\core\caller.c

E28416 v_dialer\dialer\src\core\caller.c

E28417 v_dialer\dialer\src\core\listops.c

E28418 v_dialer\dialer\src\core\listops.c

E28419 v_dialer\dialer\src\core\listops.c

E28420 v_dialer\dialer\src\core\listops.c

E28421 v_dialer\dialer\src\core\listops.c

E28422 v_dialer\dialer\src\core\listops.c

E28423 v_dialer\dialer\src\core\listops.c

E28424 v_dialer\dialer\src\core\listops.c

E28425 v_dialer\dialer\src\core\listops.c

E28426 v_dialer\dialer\src\core\listops.c

E28427 v_dialer\dialer\src\core\listops.c

E28428 v_dialer\dialer\src\core\listops.cv_dialer\dialer\DialerCmdCtrl\ErrorHandling_utest.cpp

E28429 v_dialer\dialer\src\core\caller.c

E28430 v_dialer\dialer\src\core\caller.c

E28431 v_dialer\dialer\src\core\job_strter.c

E28432 v_dialer\dialer\src\core\job_strter.c

E28433 v_dialer\dialer\src\core\job_strter.c

Page 207: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 205

E28434 v_dialer\dialer\src\core\caller.cv_dialer\dialer\src\core\job_strter.c

E28435 v_dialer\dialer\src\core\job_strter.c

E28436 v_dialer\dialer\src\core\job_strter.c

E28437 v_dialer\dialer\src\core\job_strter.c

E28438 v_dialer\dialer\src\core\job_strter.c

E28439 v_dialer\dialer\src\core\caller.c

E28440 v_dialer\dialer\src\core\ao_recall.cv_dialer\dialer\src\core\caller.c

E28441 v_dialer\dialer\src\core\caller.c

E28442 v_dialer\dialer\src\core\caller.c

E28443 v_dialer\dialer\src\core\listops.c

E28444

E28445 v_dialer\dialer\src\core\caller.cv_dialer\dialer\src\core\joblib.c

E28446

E28447 v_dialer\dialer\src\core\caller.c

E28448 v_dialer\dialer\src\core\caller.c

E28449 v_dialer\dialer\src\core\caller.c

E28450 v_dialer\dialer\src\core\listops.c

E28451 v_dialer\dialer\src\core\listops.c

E28452 v_dialer\dialer\src\core\listops.c

E28453 v_dialer\dialer\src\core\listops.c

E28454 v_dialer\dialer\src\core\listops.c

E28455 v_dialer\dialer\src\core\listops.c

E28456 v_dialer\dialer\src\core\listops.c

E28457 v_dialer\dialer\src\core\listops.c

E28458 v_dialer\dialer\src\core\listops.c

E28459 v_dialer\dialer\src\core\listops.c

E28460 v_dialer\dialer\src\core\listops.c

Page 208: PC4 Troubleshooting Main

206 Maintenance and Troubleshooting Guide March 2008

E28461 v_dialer\dialer\src\core\listops.c

E28462 v_dialer\dialer\src\core\listops.c

E28463 v_dialer\dialer\src\core\port_hndle.c

E28464 v_dialer\dialer\src\core\caller.cv_dialer\dialer\src\editor\config_ed.c

E28465

E28600 v_dialer\dialer\src\core\porter.c

E28601 v_dialer\dialer\src\core\porter.c

E28602 v_dialer\dialer\src\core\ao_recall.cv_dialer\dialer\src\utility\list_status.cv_dialer\dialer\enforcer\src\enforcer.cppv_dialer\dialer\src\core\porter.cv_dialer\dialer\src\core\recall_rmp.c

E28603 v_dialer\dialer\src\core\agent_misc_util.cv_dialer\dialer\src\core\operator.cv_dialer\dialer\src\core\port_hndle.cv_dialer\dialer\src\core\portevent.cv_dialer\dialer\src\core\porter.c

E28604, E28605

E28606 v_dialer\dialer\src\core\scripter.c

E28607 v_dialer\dialer\src\core\scripter.c

E28608 v_dialer\dialer\src\core\scripter.c

E28609 v_dialer\dialer\src\core\scripter.c

E28610

E28611 v_dialer\dialer\src\core\scripter.c

E28612 v_dialer\dialer\src\core\scripter.c

E28613 v_dialer\dialer\src\core\scripter.c

E28614 v_dialer\dialer\src\core\scripter.c

E28615

E28616 v_dialer\library\libdsi\src\script_lng.c

E28617 v_dialer\dialer\src\core\listops.c

Page 209: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 207

E28618 v_dialer\dialer\src\core\listops.c

E28619 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\src\core\listops.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E28620 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\src\core\listops.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E28621-E28625

E28626 v_dialer\dialer\src\core\porter.c

E28627 v_dialer\dialer\src\core\porter.c

E28628 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\operator.cv_dialer\dialer\src\core\scripter.c

E28629 v_dialer\dialer\src\core\scripter.c

E28630 v_dialer\dialer\src\core\scripter.c

E28631 v_dialer\dialer\src\core\scripter.c

E28632 v_dialer\dialer\src\core\scripter.c

E28633 v_dialer\dialer\src\core\scripter.c

E28634 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E28800 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Invalid delay specification

E28801 v_dialer\dialer\src\core\screen.c Record currently in use

E28802 v_dialer\dialer\src\core\screen.c Recall not allowed for inbound call

E28803

E28804 v_dialer\dialer\src\core\agent.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Job <name> not running

Page 210: PC4 Troubleshooting Main

208 Maintenance and Troubleshooting Guide March 2008

E28805 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\operator.c

Job <name> not running

E28806-E28811

E28812 v_dialer\dialer\src\core\agent_misc_util.cv_dialer\dialer\src\core\operator.c

Agent <name> logged in Already - Access Denied

E28813 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\operator.c

<type> agents are not permitted on this job

E28814 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\operator.c

<type> agents are not permitted on this job

E28815 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\operator.c

Sales verification with unit work lists is not permitted

E28816 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\operator.c

Inbound agents only permitted

E28817 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\operator.c

Outbound agents only permitted

E28818 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\operator.c

Outbound or Managed agents only permitted

E28819 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\operator.c

Only outbound agents permitted by sales verification

E28820 v_dialer\dialer\src\core\operator.c Unit value not found, or unavailable

E28821 v_dialer\dialer\src\core\screen.c Cannot be DONE from alternate screen

E28822 v_dialer\dialer\src\core\screen.c Line not released

E28823

E28824 v_dialer\dialer\src\core\screen.c Changes to record not saved

E28825 v_dialer\dialer\src\core\screen.c Changes to record not saved

E28826 v_dialer\dialer\src\core\screen.c Record is no longer available

E28827 v_dialer\dialer\src\core\screen.c Failed to unlock file

E28828 v_dialer\dialer\src\core\screen.cv_dialer\dialer\src\utility\shmon.c

Unknown screen type

E28829 v_dialer\dialer\src\core\screen.c Field entry is required

Page 211: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 209

E28830 v_dialer\dialer\src\core\screen.c Field value not in acceptable list

E28831 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Field has non-numeric value

E28832 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Invalid date format

E28833 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Invalid date format

E28834 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Invalid date format

E28835 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Invalid date format

E28836 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Invalid format character found

E28837 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Invalid time format

E28838 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Invalid time format

E28839 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Invalid time format

E28840 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Invalid time format

E28841 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Invalid phone

E28842 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Invalid phonestat - <status>

E28843 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Invalid phone <number>

E28844 v_dialer\dialer\src\core\screen.c No REL_DIST setting

E28845 v_dialer\dialer\src\core\screen.c No REL_TME setting

E28846 v_dialer\dialer\src\core\screen.c No DONE_TME setting

E28847 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Date is before the current date

Page 212: PC4 Troubleshooting Main

210 Maintenance and Troubleshooting Guide March 2008

E28848 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Recall time and date outside timezone

E28849 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Missing or invalid time zone designation

E28850 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\screen.c

Cannot open channel to operator monitor process

E28851 v_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\screen.c

Operator monitor process does not respond

E28852-E28855

E28856 v_dialer\dialer\src\core\screen.c Invalid response from operator monitor process

E28857

E28858 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\core\operator.c

<agent_name> - Exceeded operator slots available, MAXOPS is low

E28859 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\joblib.cv_dialer\dialer\src\core\operator.c

<agent><agent_name> - Operator number returned invalid <slot_num>

E28860 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\operator.c

<string><string>- Operator number returned wrong <num1>, job number <num2>

E28861 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\joblib.cv_dialer\dialer\src\core\operator.c

Operator slot semaphore not available

E28862 v_dialer\dialer\src\core\agent.c Fatal error on select - <num>

E28863 v_dialer\dialer\src\core\agent.c ERROR - Unknown file descriptor

E28864 v_dialer\dialer\src\core\agent_io_util.cv_dialer\dialer\src\core\job_strter.c

Unknown IPC message - <string>

E28865 v_dialer\dialer\src\core\agent_io_util.c Unknown Command message - <command>

Page 213: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 211

E28866 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\agent_tdss_util.cv_dialer\dialer\src\core\screen.c

Telephone line not available

E28867 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\agent_tdss_util.c

Telephone line not offhook

E28868 v_dialer\dialer\src\core\agent.c Callbacks are not permitted on inbound calls

E28869 v_dialer\dialer\src\core\agent.c

E28870 v_dialer\dialer\src\core\agent_hs_util.c

E28871 v_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\DialerCmdCtrl\HeadsetLib.cpp

E28872 v_dialer\dialer\src\core\agent_hs_util.c

E28873 v_dialer\dialer\src\core\agent_hs_util.c

E28874 v_dialer\dialer\src\core\agent_hs_util.c

E28875 v_dialer\dialer\src\core\agent_hs_util.c

E28876 v_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\DialerCmdCtrl\HeadsetLib.cpp

E28877 v_dialer\dialer\src\core\agent_hs_util.c

E28878, E28879

E28880 v_dialer\dialer\src\core\agent_hs_util.c

E28881 v_dialer\dialer\src\core\agent_hs_util.c

E28882 v_dialer\dialer\src\core\agent.c

E28883 v_dialer\dialer\src\core\agent.c

E28884 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_misc_util.c

E28885 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_misc_util.cv_dialer\dialer\src\core\agent_pvrs_util.c

Page 214: PC4 Troubleshooting Main

212 Maintenance and Troubleshooting Guide March 2008

E28886 v_dialer\dialer\src\core\agent.c

E28887 v_dialer\dialer\src\core\agent.c

E28888 v_dialer\dialer\src\core\agent.c

E28889 v_dialer\dialer\src\core\agent.c

E28890 v_dialer\dialer\src\core\agent.c

E28891 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_misc_util.c

E28892 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_misc_util.c

E28893 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_misc_util.c

E28894 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_misc_util.c

E28895 v_dialer\dialer\src\core\agent.c

E28896 v_dialer\dialer\src\core\agent.c

E28897 v_dialer\dialer\src\core\agent.c

E28898 v_dialer\dialer\src\core\agent.c

E28899 v_dialer\dialer\src\core\agent.c

E28900 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_misc_util.cv_dialer\dialer\src\core\agent_hs_util.c

E28901 v_dialer\dialer\src\core\agent.c

E28902 v_dialer\dialer\src\core\agent.c

E28903 v_dialer\dialer\src\core\agent.c

E28904 v_dialer\dialer\src\core\agent.c

E28905 v_dialer\dialer\src\core\agent.c

E28906 v_dialer\dialer\src\core\agent.c

E28907 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_pvrs_util.c

E28908 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_pvrs_util.c

Page 215: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 213

E28909 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_pvrs_util.c

E28910 v_dialer\dialer\src\core\agent.c

E28911 v_dialer\dialer\src\core\agent.c

E28912 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_misc_util.c

E28913 v_dialer\dialer\src\core\agent.c

E28914 v_dialer\dialer\src\core\agent.c

E28915 v_dialer\dialer\src\core\agent.c

E28916 v_dialer\dialer\src\core\agent_misc_util.c

E28917 v_dialer\dialer\src\core\agent.c

E28918 v_dialer\dialer\src\core\agent.c

E28919 v_dialer\dialer\src\core\agent.c

E28920 v_dialer\dialer\src\core\agent_hs_util.c

E28921 v_dialer\dialer\src\core\agent_misc_util.c

E28922 v_dialer\dialer\src\core\agent_hs_util.c

E28923 v_dialer\dialer\src\core\agent_hs_util.c

E28924 v_dialer\dialer\src\core\agent_io_util.c

E28925 v_dialer\dialer\src\core\agent_misc_util.c

E28926 v_dialer\dialer\src\core\agent_misc_util.c

E28927 v_dialer\dialer\src\core\agent.c

E28928 v_dialer\dialer\src\core\agent.c

E28929 v_dialer\dialer\src\core\agent.c

E28930 v_dialer\dialer\src\core\agent.c

E28931 v_dialer\dialer\src\core\agent.c

E28932 v_dialer\dialer\src\core\agent.c

E28933 v_dialer\dialer\src\core\agent_io_util.c

E28934 v_dialer\dialer\src\core\agent_io_util.c

E28935 v_dialer\dialer\src\core\agent_misc_util.c

Page 216: PC4 Troubleshooting Main

214 Maintenance and Troubleshooting Guide March 2008

E28936 v_dialer\dialer\src\core\agent.c

E28937 v_dialer\dialer\src\core\operator.c

E28938 v_dialer\dialer\src\core\api_jobctl.c

E28940 v_dialer\dialer\src\core\agent_tdss_util.cv_dialer\dialer\src\core\transfer.c

E28942 v_dialer\dialer\src\core\agent_tdss_util.cv_dialer\dialer\src\core\screen.c

E28943 v_dialer\dialer\src\core\screen.c

E28944 v_dialer\dialer\src\core\screen.c

E28945 v_dialer\dialer\src\core\operator.c

E28946 v_dialer\dialer\src\core\agent.c

E28947 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

E28948 v_dialer\dialer\src\core\joblib.c

E28949 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

E28950 v_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\operator.c

E28951 v_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\operator.c

E28952 v_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\operator.c

E28953 v_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\operator.c

E28954 v_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\operator.c

E28955 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

E28956 v_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\operator.c

E28957 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Page 217: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 215

E28958 v_dialer\dialer\src\core\donotcall.c

E28959 v_dialer\dialer\src\core\operator.c

E28960 v_dialer\dialer\src\core\dnc_mark.c

E28961 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\src\core\operator.c

E28962 v_dialer\dialer\src\core\operator.c

E28963 v_dialer\dialer\src\core\screen.c

E28964 v_dialer\dialer\src\core\agent.c

E28965 v_dialer\dialer\src\core\agent.c

E28966 v_dialer\dialer\src\core\operator.c

E28967 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\operator.cv_dialer\dialer\src\core\screen.c

E28968 v_dialer\dialer\src\core\operator.c

E28969 v_dialer\dialer\src\core\agent_pvrs_util.c

E28970 v_dialer\dialer\src\core\agent_pvrs_util.cv_dialer\dialer\src\core\operator.c

E28971 v_dialer\dialer\src\core\agent_pvrs_util.cv_dialer\dialer\src\core\oper_pvrs.cv_dialer\dialer\src\core\screen.c

E28972 v_dialer\dialer\src\core\agent_pvrs_util.cv_dialer\dialer\src\core\oper_pvrs.cv_dialer\dialer\src\core\screen.c

E28973 v_dialer\dialer\src\core\agent_pvrs_util.cv_dialer\dialer\src\core\oper_pvrs.cv_dialer\dialer\src\core\screen.c

E28974 v_dialer\dialer\src\core\agent_pvrs_util.cv_dialer\dialer\src\core\screen.c

E28975 v_dialer\dialer\src\core\screen.c

E28976 v_dialer\dialer\src\core\screen.c

E28977 v_dialer\dialer\src\core\operator.c

E28978 v_dialer\dialer\src\core\operator.c

Page 218: PC4 Troubleshooting Main

216 Maintenance and Troubleshooting Guide March 2008

E28979 v_dialer\dialer\src\core\screen.c

E28980 v_dialer\dialer\src\core\screen.c

E28981 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\operator.c

E28982 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

E28983 v_dialer\dialer\src\core\agent.c

E28984 v_dialer\dialer\src\core\agent.c

E29000 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\api_jobctl.c

E29001 v_dialer\dialer\src\core\api_jobctl.c

E29002 v_dialer\dialer\src\core\api_jobctl.c

E29006 v_dialer\dialer\src\core\api_jobctl.c

E29007

E29008

E29009 v_dialer\dialer\src\core\api_jobctl.c

E29010 v_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\core\joblib.c

E29011 v_dialer\dialer\src\core\api_jobctl.c

E29012 v_dialer\dialer\src\core\api_jobctl.c

E29014 v_dialer\dialer\src\core\api_jobctl.c

E29015 v_dialer\dialer\src\core\api_jobctl.c

E29016 v_dialer\dialer\src\core\api_jobctl.c

E29017 v_dialer\dialer\src\core\api_jobctl.c

E29018 v_dialer\dialer\src\core\api_jobctl.c

E29019 v_dialer\dialer\src\core\joblib.c

E29020 v_dialer\dialer\src\core\api_jobctl.c

E29021 v_dialer\dialer\src\core\api_jobctl.c

E29022 v_dialer\dialer\src\core\api_jobctl.c

E29023 v_dialer\dialer\src\core\api_jobctl.c

Page 219: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 217

E29024 v_dialer\dialer\src\core\api_jobctl.c

E29025 v_dialer\dialer\src\core\api_jobctl.c

E29026 v_dialer\dialer\src\core\api_jobctl.c

E29027 v_dialer\dialer\src\core\api_jobctl.c

E29028 v_dialer\dialer\src\core\api_jobctl.c

E29029 v_dialer\dialer\src\core\api_jobctl.c

E29030 v_dialer\dialer\src\core\api_jobctl.c

E29031 v_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E29032 v_dialer\dialer\src\core\api_jobctl.c

E29033-E29035

E29036 v_dialer\dialer\src\core\joblib.c

E29037 v_dialer\dialer\src\core\joblib.c

E29038 v_dialer\dialer\src\core\joblib.c

E29039

E29040 v_dialer\dialer\src\core\api_jobctl.c

E29041

E29042 v_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\core\iicb_conf.c

E29043 v_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\core\iicb_conf.c

E29044 v_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\core\iicb_conf.c

E29045 v_dialer\dialer\src\core\iicb_conf.c

E29046 v_dialer\dialer\src\core\iicb_conf.c

E29047 v_dialer\dialer\src\core\iicb_conf.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E29048 v_dialer\dialer\src\core\iicb_conf.c

E29049 v_dialer\dialer\src\core\iicb_conf.c

Page 220: PC4 Troubleshooting Main

218 Maintenance and Troubleshooting Guide March 2008

E29050 v_dialer\dialer\src\core\iicb_conf.c

E29051 v_dialer\dialer\src\core\install_ext.c

E29052 v_dialer\dialer\src\core\install_ext.c

E29053 v_dialer\dialer\src\core\install_ext.c

E29054 v_dialer\dialer\src\core\install_ext.c

E29055 v_dialer\dialer\src\core\install_ext.c

E29056 v_dialer\dialer\src\core\api_jobctl.c

E29057 v_dialer\dialer\src\core\api_jobctl.c

E29150 v_dialer\dialer\src\core\beeper.c

E29151 v_dialer\dialer\src\core\beeper.c

E29152 v_dialer\dialer\src\core\beeper.c

E29153 v_dialer\dialer\src\core\beeper.c

E29154 v_dialer\dialer\src\core\beeper.c

E29200 v_dialer\dialer\src\core\ao_recall.cv_dialer\dialer\src\core\caller.cv_dialer\dialer\src\core\conn_mgr.cv_dialer\dialer\src\core\agent_tdss_util.c

E29201

E29202

Page 221: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 219

E29203 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\ao_recall.cv_dialer\dialer\src\core\beeper.cv_dialer\dialer\src\core\caller.cv_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\src\core\job_strter.cv_dialer\dialer\src\core\joblib.cv_dialer\dialer\src\core\operator.cv_dialer\ivr\src\ivr_config.cv_dialer\ivr\src\ivr_conn.cv_dialer\dialer\src\utility\mem_dump.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\dialer\src\core\porter.cv_dialer\dialer\src\core\recall_rmp.cv_dialer\dialer\src\utility\shmon.c

E29204 v_dialer\dialer\src\core\conn_mgr.c

E29205 v_dialer\dialer\src\core\listops.c

E29206 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\operator.c

E29207 v_dialer\dialer\src\core\screen.c

E29208 v_dialer\dialer\src\core\caller.cv_dialer\dialer\src\core\joblib.cv_dialer\dialer\src\core\driver.cv_dialer\dialer\src\core\msg_loader.c

E29210 v_dialer\dialer\src\core\msg_loader.c

E29212 v_dialer\dialer\src\core\msg_loader.c

E29213 v_dialer\dialer\src\core\msg_loader.cv_dialer\dialer\DialerCmdCtrl\DccsAudioFileValidator.cpp

E29214 v_dialer\dialer\src\core\msg_loader.cv_dialer\dialer\DialerCmdCtrl\DccsAudioFileValidator.cpp

E29400 v_dialer\dialer\src\core\testmsg.c

E29500 v_dialer\dialer\src\core\ao_recall.c

E29501 v_dialer\dialer\src\core\ao_recall.c

Page 222: PC4 Troubleshooting Main

220 Maintenance and Troubleshooting Guide March 2008

E29502 v_dialer\dialer\src\core\ao_recall.c

E29503 v_dialer\dialer\src\core\ao_recall.c

E29505 v_dialer\dialer\src\core\ao_recall.c

E29600 - E29608

E29700 v_dialer\dialer\src\core\joblist_ed.c

E29701 v_dialer\dialer\src\core\ld_joblist.cv_dialer\dialer\src\core\joblist_ed.c

E29702 v_dialer\dialer\src\core\ld_joblist.cv_dialer\dialer\src\core\joblist_ed.c

E29703 v_dialer\dialer\src\core\ld_joblist.cv_dialer\dialer\src\core\joblist_ed.c

E29704 v_dialer\dialer\src\core\ld_joblist.c

E29705 v_dialer\dialer\src\core\ld_joblist.c

E29706 v_dialer\dialer\src\core\ld_joblist.cv_dialer\dialer\src\core\joblist_ed.c

E29707 v_dialer\dialer\src\core\ld_joblist.cv_dialer\dialer\src\core\joblist_ed.c

E29708 v_dialer\dialer\src\core\operator.c

E29709 v_dialer\dialer\src\core\joblist_ed.c

E29710 v_dialer\dialer\src\core\ld_joblist.c

E29711 v_dialer\dialer\src\core\ld_joblist.c

E29712 v_dialer\dialer\src\core\ld_joblist.c

E29714 v_dialer\dialer\src\core\ld_joblist.cv_dialer\dialer\src\core\joblist_ed.c

E29715 v_dialer\dialer\src\core\ld_joblist.cv_dialer\dialer\src\core\joblist_ed.c

E29716 v_dialer\dialer\src\core\joblist_ed.c

E29717 v_dialer\dialer\src\core\job_strter.cv_dialer\dialer\src\core\ld_joblist.cv_dialer\dialer\src\core\joblist_ed.c

E29718 v_dialer\dialer\src\core\ld_joblist.c

Page 223: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 221

E29719 v_dialer\dialer\src\core\job_strter.cv_dialer\dialer\src\core\ld_joblist.cv_dialer\dialer\src\core\joblist_ed.c

E29800 v_dialer\dialer\src\core\chainhandler.c

E29900 v_dialer\dialer\src\core\job_strter.c

E29901 v_dialer\dialer\src\core\job_strter.c

E29902 v_dialer\dialer\src\core\job_strter.c

E29903 v_dialer\dialer\src\core\job_strter.c

E29904 v_dialer\dialer\src\core\job_strter.c

E29950 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\agent_tdss_util.cv_dialer\dialer\src\core\screen.c

E29951 v_dialer\dialer\src\core\port_hndle.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E30000-E30019

E31200 v_dialer\dialer\src\custom\readwrt.c

E31400 v_dialer\dialer\src\custom\atohex.c

E32000 v_dialer\dialer\src\dbconst\readtape.c

E32001 v_dialer\dialer\src\dbconst\readtape.c

E32002 v_dialer\dialer\src\dbconst\readtape.c

E32003 v_dialer\dialer\src\dbconst\readtape.c

E32004 v_dialer\dialer\src\dbconst\readtape.c

E32005 v_dialer\dialer\src\dbconst\readtape.c

E32005 v_dialer\dialer\src\dbconst\readtape.c

E32006 v_dialer\dialer\src\dbconst\readtape.c

E32007 v_dialer\dialer\src\dbconst\readtape.c

E32008 v_dialer\dialer\src\dbconst\readtape.c

E32400 v_dialer\dialer\src\dbconst\readtape.cv_dialer\dialer\src\dbconst\writetape.c

Page 224: PC4 Troubleshooting Main

222 Maintenance and Troubleshooting Guide March 2008

E32401 v_dialer\dialer\src\dbconst\readtape.cv_dialer\dialer\src\dbconst\writetape.c

E32402 v_dialer\dialer\src\dbconst\readtape.cv_dialer\dialer\src\dbconst\writetape.c

E32403 v_dialer\dialer\src\dbconst\readtape.cv_dialer\dialer\src\dbconst\writetape.c

E32404 v_dialer\dialer\src\dbconst\readtape.cv_dialer\dialer\src\dbconst\writetape.c

E32405 v_dialer\dialer\src\dbconst\readtape.c

E32600 v_dialer\dialer\src\dbconst\moj_conv.cv_dialer\dialer\DialerCmdCtrl\VoicemsgCfgTable.cpp

E32601

E32602 v_dialer\dialer\src\dbconst\moj_conv.c

E32603 v_dialer\dialer\src\dbconst\moj_conv.c

E32604 v_dialer\dialer\src\dbconst\moj_conv.c

E32605 v_dialer\dialer\src\dbconst\moj_conv.c

E32606

E32607 v_dialer\dialer\src\dbconst\moj_conv.c

E34000 v_dialer\dialer\src\lettergen\formlet.c

E34001 v_dialer\dialer\src\lettergen\formlet.c

E35000 v_dialer\dialer\src\lstextract\ext_data.c

E35001 v_dialer\dialer\src\lstextract\ext_data.c

E35002 v_dialer\dialer\src\lstextract\ext_data.c

E35200 v_dialer\dialer\src\lstextract\ext_list.c

E35201 v_dialer\dialer\src\lstextract\ext_list.c

E36000 v_dialer\dialer\src\dbmaint\record_ed.c

E36001 v_dialer\dialer\src\dbmaint\record_ed.c

E36002 v_dialer\dialer\src\dbmaint\record_ed.c

E36003 v_dialer\dialer\src\dbmaint\record_ed.c

E36004 v_dialer\dialer\src\dbmaint\record_ed.c

Page 225: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 223

E36005 v_dialer\dialer\src\dbmaint\record_ed.c

E36006 v_dialer\dialer\src\dbmaint\redit_scrn.c

E36101 v_dialer\dialer\src\dbmaint\rec_update.c

E36200 v_dialer\dialer\src\dbmaint\redit_scrn.c

E36201 v_dialer\dialer\src\core\dnc_mark.c

E36202 v_dialer\dialer\src\core\dnc_mark.c

E36203

E37000 v_dialer\admin\src\createop.c

E37001 v_dialer\admin\src\createop.c

E37002 v_dialer\admin\src\createop.c

E37003 v_dialer\admin\src\createop.c

E37004 v_dialer\admin\src\createop.c

E37005 v_dialer\admin\src\createop.c

E37006 v_dialer\admin\src\createop.c

E37007

E37008 v_dialer\admin\src\createop.c

E37009

E37010 v_dialer\admin\src\createop.cv_dialer\ivr\src\ivr_config.c

E37011 v_dialer\admin\src\createop.cv_dialer\ivr\src\ivr_config.c

E37012 v_dialer\admin\src\createop.c

E37013 v_dialer\admin\src\createop.c

E37014 v_dialer\admin\src\createop.c

E37015 v_dialer\admin\src\createop.c

E37016 v_dialer\admin\src\createop.c

E37017 v_dialer\admin\src\createop.c

E37018 v_dialer\admin\src\createop.c

E37019 v_dialer\admin\src\createop.c

Page 226: PC4 Troubleshooting Main

224 Maintenance and Troubleshooting Guide March 2008

E37020 v_dialer\admin\src\createop.c

E37021 v_dialer\admin\src\createop.c

E37022 v_dialer\admin\src\createop.c

E37023 v_dialer\admin\src\createop.cv_dialer\ivr\src\ivr_config.c

E37024 v_dialer\admin\src\createop.cv_dialer\ivr\src\ivr_config.c

E37025 v_dialer\admin\src\createop.c

E37026 v_dialer\admin\src\createop.c

E37027 v_dialer\admin\src\createop.c

E37028 v_dialer\admin\src\createop.c

E37029 v_dialer\admin\src\createop.c

E37030 v_dialer\admin\src\createop.c

E37031 v_dialer\admin\src\createop.c

E37032 v_dialer\admin\src\createop.c

E37033

E37034 v_dialer\admin\src\createop.c

E37035 v_dialer\admin\src\createop.c

E37036 v_dialer\admin\src\createop.c

E37037 v_dialer\admin\src\createop.c

E37038 v_dialer\admin\src\createop.c

E37039

E37200 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E37201 v_dialer\dialer\src\editor\config_ed.c

E37202 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E37203

Page 227: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 225

E37204 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E37205 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E37206, E37207

E37208 v_dialer\dialer\src\editor\config_ed.c

E37209, E37210

E37211 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E37212 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E37213 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E37214 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E37215, E37216

E37217 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E37218 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E37219 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E37220 v_dialer\dialer\src\editor\config_ed.c

E37221 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Page 228: PC4 Troubleshooting Main

226 Maintenance and Troubleshooting Guide March 2008

E37222 v_dialer\dialer\src\editor\config_ed.c

E37223 v_dialer\dialer\src\editor\config_ed.c

E37224 v_dialer\dialer\src\editor\config_ed.c

E37225 v_dialer\dialer\src\editor\config_ed.c

E37226 v_dialer\dialer\src\editor\config_ed.c

E37227 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E37228

E37229 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E37230

E37231 v_dialer\dialer\src\editor\config_ed.c

E37232 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E37233 v_dialer\dialer\src\editor\config_ed.c

E37234 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E37235 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E37236 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E37237 v_dialer\dialer\src\editor\config_ed.c

E37238 v_dialer\dialer\src\editor\config_ed.c

E37239 v_dialer\dialer\src\editor\config_ed.c

E37240 v_dialer\dialer\src\editor\config_ed.c

E37241 v_dialer\dialer\src\editor\config_ed.c

E37242 v_dialer\dialer\src\editor\config_ed.c

Page 229: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 227

E37243 v_dialer\dialer\src\editor\config_ed.c

E37244 v_dialer\dialer\src\editor\config_ed.c

E37245 v_dialer\dialer\src\editor\config_ed.c

E37246 v_dialer\dialer\src\editor\config_ed.c

E37247 v_dialer\dialer\src\editor\config_ed.c

E37248 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E37249 v_dialer\dialer\src\editor\config_ed.c

E37250 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E37251 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E37252 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E37253 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E37254 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E37255

E37256 v_dialer\dialer\src\editor\config_ed.c

E37300 v_dialer\admin\src\termprocess.c

E37301 v_dialer\admin\src\termprocess.c

E37400 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E37401

E37402 v_dialer\dialer\src\editor\config_ed.c

E37403 v_dialer\dialer\src\editor\config_ed.c

Page 230: PC4 Troubleshooting Main

228 Maintenance and Troubleshooting Guide March 2008

E37404 v_dialer\dialer\src\editor\config_ed.c

E37405 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E37500 v_dialer\admin\src\signalit.c

E37501 v_dialer\admin\src\signalit.c

E37502 v_dialer\admin\src\signalit.c

E37503 v_dialer\admin\src\signalit.c

E37503 v_dialer\dialer\src\utility\agentcount.c

E37600 v_dialer\dialer\src\editor\master_ed.c

E37601 v_dialer\dialer\src\editor\master_ed.c

E37602 v_dialer\dialer\src\editor\master_ed.c

E37603 v_dialer\dialer\src\editor\master_ed.c

E37604 v_dialer\dialer\src\editor\master_ed.c

E37800 v_dialer\admin\src\addgroup.c

E37801

E37802 v_dialer\admin\src\addgroup.c

E38000 v_dialer\dialer\src\markrec\chkentdt.c

E38001

E38002 v_dialer\dialer\src\markrec\chkentdt.c

E38003 v_dialer\dialer\src\markrec\chkentdt.c

E38004 v_dialer\dialer\src\markrec\chkentdt.c

E38400 v_dialer\dialer\src\markrec\latemrk.c

E38401

E38402 v_dialer\dialer\src\markrec\latemrk.c

E38403 v_dialer\dialer\src\markrec\latemrk.c

E38404 v_dialer\dialer\src\markrec\latemrk.c

E38405 v_dialer\dialer\src\markrec\latemrk.c

E38406 v_dialer\dialer\src\markrec\latemrk.c

Page 231: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 229

E38600 v_dialer\dialer\src\markrec\get_field.cv_dialer\dialer\src\markrec\set_field.c

E38601 v_dialer\dialer\src\markrec\set_field.c

E38602 v_dialer\dialer\src\markrec\get_field.cv_dialer\dialer\src\markrec\set_field.c

E38603 v_dialer\dialer\src\markrec\get_field.cv_dialer\dialer\src\markrec\set_field.c

E38604 v_dialer\dialer\src\markrec\get_field.cv_dialer\dialer\src\markrec\set_field.c

E38605 v_dialer\dialer\src\markrec\get_field.c

E38800 v_dialer\dialer\src\markrec\latelst.c

E38801

E38802

E39000

E39001 v_dialer\dialer\src\menu\menu.c

E39002 v_dialer\dialer\src\menu\menu.c

E39003 v_dialer\dialer\src\menu\menu.c

E39004 v_dialer\dialer\src\menu\menu.c

E39005 v_dialer\dialer\src\menu\menu.c

E39200 v_dialer\dialer\src\menu\submenu.c

E39201 v_dialer\dialer\src\menu\submenu.c

E39202 v_dialer\dialer\src\menu\submenu.c

E40000 v_dialer\dialer\src\pcextract\brkfile.c

E40001 v_dialer\dialer\src\pcextract\brkfile.c

E40002 v_dialer\dialer\src\pcextract\fileops.c

E40003 v_dialer\dialer\src\pcextract\brkfile.c

E40200 v_dialer\dialer\src\pcextract\fileops.c

E40201 v_dialer\dialer\src\pcextract\fileops.c

E40202 v_dialer\dialer\src\pcextract\fileops.c File <filename> does not exist

E40203 v_dialer\dialer\src\pcextract\fileops.c

Page 232: PC4 Troubleshooting Main

230 Maintenance and Troubleshooting Guide March 2008

E40204 v_dialer\dialer\src\pcextract\fileops.c

E40400 v_dialer\dialer\src\pcextract\msetup.c

E40401 v_dialer\dialer\src\pcextract\msetup.c

E42000 v_dialer\dialer\src\preprocess\de_reject.c

E42100 v_dialer\dialer\src\preprocess\ij_merge.c

E42101 v_dialer\dialer\src\preprocess\ij_merge.c

E42400 v_dialer\dialer\src\preprocess\clhashin.c

E42401

E42402 v_dialer\dialer\src\preprocess\clhashin.c

E42403 v_dialer\dialer\src\preprocess\clhashin.c

E42404 v_dialer\dialer\src\preprocess\clhashin.c

E42405 v_dialer\dialer\src\preprocess\clhashin.c

E42406 v_dialer\dialer\src\preprocess\clhashin.c

E42600-42617

E42800

E42801 v_dialer\dialer\src\preprocess\setzones.c

E43000 v_dialer\dialer\src\preprocess\update_cl.c

E43001 v_dialer\dialer\src\preprocess\update_cl.c

E43002 v_dialer\dialer\src\preprocess\update_cl.c

E43200

E43201

E43400 v_dialer\dialer\src\preprocess\clhash.cv_dialer\dialer\src\preprocess\clhashin.cv_dialer\dialer\src\preprocess\update_cl.cv_dialer\dialer\src\preprocess\update_upl.c

E43401 v_dialer\dialer\src\preprocess\clhashin.cv_dialer\dialer\src\preprocess\update_cl.cv_dialer\dialer\src\preprocess\update_upl.c

Page 233: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 231

E43402 v_dialer\dialer\src\preprocess\clhashin.cv_dialer\dialer\src\preprocess\update_cl.cv_dialer\dialer\src\preprocess\update_upl.c

E43403 v_dialer\dialer\src\preprocess\update_upl.c

E43404 v_dialer\dialer\src\preprocess\clhash.cv_dialer\dialer\src\preprocess\update_upl.c

E43405 v_dialer\dialer\src\preprocess\clhashin.cv_dialer\dialer\src\preprocess\update_cl.cv_dialer\dialer\src\preprocess\update_upl.c

E43406 v_dialer\dialer\src\preprocess\clhashin.cv_dialer\dialer\src\preprocess\update_cl.cv_dialer\dialer\src\preprocess\update_upl.c

E43407 v_dialer\dialer\src\preprocess\clhash.cv_dialer\dialer\src\preprocess\update_upl.c

E43408 v_dialer\dialer\src\preprocess\update_cl.cv_dialer\dialer\src\preprocess\update_upl.c

E43500 v_dialer\dialer\src\preprocess\msgmap.c

E43501 v_dialer\dialer\src\preprocess\msgmap.c

E43502 v_dialer\dialer\src\preprocess\msgmap.c

E43503 v_dialer\dialer\src\preprocess\msgmap.c

E43504 v_dialer\dialer\src\preprocess\msgmap.c

E43505 v_dialer\dialer\src\preprocess\msgmap.c

E43506 v_dialer\dialer\src\preprocess\msgmap.c

E43507 v_dialer\dialer\src\preprocess\msgmap.c

E43508

E43509 v_dialer\dialer\src\preprocess\msgmap.c

E43510 v_dialer\dialer\src\preprocess\msgmap.c

E43511 v_dialer\dialer\src\preprocess\msgmap.c

Page 234: PC4 Troubleshooting Main

232 Maintenance and Troubleshooting Guide March 2008

E43512 v_dialer\dialer\src\preprocess\msgmap.c

E44000 v_dialer\dialer\src\reports\history\hist_rpt.c

E44001 v_dialer\dialer\src\reports\history\hist_rpt.c

E44002 v_dialer\dialer\src\reports\history\hist_rpt.c

E44003 v_dialer\dialer\src\reports\history\hist_rpt.c

E44004 v_dialer\dialer\src\reports\history\hist_rpt.c

E44005 v_dialer\dialer\src\reports\history\hist_rpt.c

E44006 v_dialer\dialer\src\reports\history\hist_rpt.c

E44007 v_dialer\dialer\src\reports\history\hist_rpt.c

E44008 v_dialer\dialer\src\reports\history\hist_rpt.c

E44009 v_dialer\dialer\src\reports\history\hist_rpt.c

E44010 v_dialer\dialer\src\reports\history\hist_rpt.c

E44011 v_dialer\dialer\src\reports\history\hist_rpt.c

E44012 v_dialer\dialer\src\reports\history\hist_rpt.c

E44013 v_dialer\dialer\src\reports\history\hist_rpt.c

E44014 v_dialer\dialer\src\reports\history\hist_rpt.c

E45000

E45001 v_dialer\dialer\src\reports\rpt_mgr\rpt_view.c

E45200, E45201

Page 235: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 233

E45202 v_dialer\dialer\src\reports\rpt_mgr\pds_view.c

E46200 v_dialer\dialer\src\reports\reportgen\reportexp.cv_dialer\dialer\src\reports\reportgen\reportsub.c

E46201 v_dialer\dialer\src\reports\reportgen\reportexp.c

E46202 v_dialer\dialer\src\reports\reportgen\reportexp.c

E46203 v_dialer\dialer\src\reports\reportgen\reportexp.c

E46204 v_dialer\dialer\src\reports\reportgen\reportexp.c

E46205 v_dialer\dialer\src\reports\reportgen\reportexp.c

E46206 v_dialer\dialer\src\reports\reportgen\reportexp.c

E46207 v_dialer\dialer\src\reports\reportgen\reportexp.c

E46208 v_dialer\dialer\src\reports\reportgen\reportexp.c

E46209 v_dialer\dialer\src\reports\reportgen\reportexp.c

E46210 v_dialer\dialer\src\reports\reportgen\reportexp.cv_dialer\dialer\src\reports\reportgen\reportsub.cv_dialer\dialer\src\reports\reportgen\reportsel.cv_dialer\dialer\src\reports\reportgen\reportprn.c

E46211 v_dialer\dialer\src\reports\reportgen\reportexp.c

E46212 v_dialer\dialer\src\reports\reportgen\reportexp.c

E46213 v_dialer\dialer\src\reports\reportgen\reportexp.c

Page 236: PC4 Troubleshooting Main

234 Maintenance and Troubleshooting Guide March 2008

E46214 v_dialer\dialer\src\reports\reportgen\reportexp.c

E46400 v_dialer\dialer\src\reports\reportgen\reportfmt.c

E46401 v_dialer\dialer\src\reports\reportgen\reportfmt.c

E46402 v_dialer\dialer\src\reports\reportgen\reportfmt.c

E46403 v_dialer\dialer\src\reports\reportgen\reportfmt.c

E46404 v_dialer\dialer\src\reports\reportgen\reportfmt.c

E46405 v_dialer\dialer\src\reports\reportgen\reportfmt.c

E46406 v_dialer\dialer\src\reports\reportgen\reportfmt.c

E46407 v_dialer\dialer\src\reports\reportgen\reportfmt.c

E46408 v_dialer\dialer\src\reports\reportgen\reportfmt.c

E46409 v_dialer\dialer\src\reports\reportgen\reportfmt.c

E46410 v_dialer\dialer\src\reports\reportgen\reportfmt.c

E46411 v_dialer\dialer\src\reports\reportgen\reportfmt.c

E46412 v_dialer\dialer\src\reports\reportgen\reportfmt.c

E46600 v_dialer\dialer\src\reports\reportgen\reporthlp.c

E46601 v_dialer\dialer\src\reports\reportgen\reporthlp.c

E46602 v_dialer\dialer\src\reports\reportgen\reporthlp.c

E46603 v_dialer\dialer\src\reports\reportgen\reportinit.c

E46800 v_dialer\dialer\src\reports\reportgen\reportinit.c

Page 237: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 235

E46801 v_dialer\dialer\src\reports\reportgen\reportinit.c

E46802 v_dialer\dialer\src\reports\reportgen\reportinit.c

E46803 v_dialer\dialer\src\reports\reportgen\reportinit.c

E46804 v_dialer\dialer\src\reports\reportgen\reportinit.c

E46805 v_dialer\dialer\src\reports\reportgen\reportinit.c

E46806 v_dialer\dialer\src\reports\reportgen\reportinit.c

E46807 v_dialer\dialer\src\reports\rptgen\reportconvert.cv_dialer\dialer\src\reports\reportgen\reportinit.cv_dialer\dialer\src\reports\reportgen\reportconvert_prev.c

E46808 v_dialer\dialer\src\reports\rptgen\reportconvert.cv_dialer\dialer\src\reports\reportgen\reportinit.cv_dialer\dialer\src\reports\reportgen\reportconvert_prev.c

E46809 v_dialer\dialer\src\reports\reportgen\reportinit.c

E46810 v_dialer\dialer\src\reports\reportgen\reportinit.cv_dialer\dialer\src\reports\reportgen\reportconvert_prev.cv_dialer\dialer\src\reports\rptgen\reportconvert.c

E46811 v_dialer\dialer\src\reports\reportgen\reportinit.cv_dialer\dialer\src\reports\reportgen\reportconvert_prev.cv_dialer\dialer\src\reports\rptgen\reportconvert.c

E47000

E47001 v_dialer\dialer\src\scrnbld\scrnbld.c

Page 238: PC4 Troubleshooting Main

236 Maintenance and Troubleshooting Guide March 2008

E47002 v_dialer\dialer\src\scrnbld\scrnbld.c

E47003 v_dialer\dialer\src\scrnbld\scrnbld.c

E47004 v_dialer\dialer\src\scrnbld\scrnbld.c

E47005 v_dialer\dialer\src\scrnbld\scrnbld.c

E47006 v_dialer\dialer\src\scrnbld\scrnbld.c

E47007 v_dialer\dialer\src\scrnbld\scrnbld.c

E47008 v_dialer\dialer\src\scrnbld\scrnbld.c

E47009 v_dialer\dialer\src\scrnbld\scrnbld.c

E47010 v_dialer\dialer\src\scrnbld\scrnbld.c

E47011

E47012 v_dialer\dialer\src\scrnbld\scrnbld.c

E47013 v_dialer\dialer\src\scrnbld\scrnbld.c

E47014 v_dialer\dialer\src\scrnbld\scrnbld.c

E47015 v_dialer\dialer\src\scrnbld\scrnbld.c

E47016-E47018

E47019 v_dialer\dialer\src\scrnbld\sbld_block.c

E47020 v_dialer\dialer\src\scrnbld\sbld_block.c

E47021 v_dialer\dialer\src\scrnbld\sbld_block.c

E47022 v_dialer\dialer\src\scrnbld\sbld_block.c

E47023 v_dialer\dialer\src\scrnbld\sbld_block.c

E47024 v_dialer\dialer\src\scrnbld\sbld_block.c

E47025 v_dialer\dialer\src\scrnbld\scrnbld.c

E47026 v_dialer\dialer\src\scrnbld\scrnbld.c

E47027 v_dialer\dialer\src\scrnbld\scrnbld.c

E47028 v_dialer\dialer\src\scrnbld\scrnbld.c

E47029

E47030 v_dialer\dialer\src\scrnbld\scrnbld.c

E47031 v_dialer\dialer\src\scrnbld\scrnbld.c

Page 239: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 237

E47032 v_dialer\dialer\src\scrnbld\scrnbld.c

E47033 v_dialer\dialer\src\scrnbld\scrnbld.c

E47034 v_dialer\dialer\src\scrnbld\scrnbld.c

E47035 v_dialer\dialer\src\scrnbld\sbld_block.c

E47036 v_dialer\dialer\src\scrnbld\sbld_block.c

E47037 v_dialer\dialer\src\scrnbld\sbld_block.c

E47038 v_dialer\dialer\src\scrnbld\scrnbld.c

E47039 v_dialer\dialer\src\scrnbld\scrnbld.c

E47040 v_dialer\dialer\src\scrnbld\scrnbld.c

E47041

E49001 v_dialer\library\libcpp\src\Passwd.cpp

E50000 v_dialer\dialer\src\utility\adump.c

E50100 v_dialer\dialer\src\utility\agentcheck.cv_dialer\dialer\src\core\agent_misc_util.c

E50101 v_dialer\dialer\src\utility\agentcheck.c

E50200 v_dialer\dialer\src\utility\datetime.c

E50201 v_dialer\dialer\src\utility\datetime.c

E50202 v_dialer\dialer\src\utility\datetime.c

E50203 v_dialer\dialer\src\utility\datetime.c

E50204 v_dialer\dialer\src\utility\datetime.c

E50205 v_dialer\dialer\src\utility\datetime.c

E50206 v_dialer\dialer\src\utility\datetime.c

E50600 v_dialer\dialer\src\utility\enq_pty.c

E50601 v_dialer\dialer\src\utility\enq_pty.c

E50602 v_dialer\dialer\src\utility\enq_pty.c

E50603 v_dialer\dialer\src\utility\enq_pty.c

E50604 v_dialer\dialer\src\utility\enq_pty.c

E50605 v_dialer\dialer\DialerCmdCtrl\HeadsetLib.cpp

Page 240: PC4 Troubleshooting Main

238 Maintenance and Troubleshooting Guide March 2008

E50606-E50608

E50609 v_dialer\dialer\src\utility\enq_pty.c

E50610

E50611 v_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\operator.cv_dialer\dialer\src\utility\enq_pty.c

E50612 v_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\operator.cv_dialer\dialer\src\utility\enq_pty.c

E50613 v_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\operator.cv_dialer\dialer\src\utility\enq_pty.c

E50800

E51001 v_dialer\dialer\src\utility\fdictdump.c

E51200 v_dialer\dialer\src\utility\jobkeys.c

E51201

E51400

E51600 v_dialer\dialer\src\utility\portcorr.c

E51601 v_dialer\dialer\src\utility\portcorr.c

E52800 v_dialer\dialer\src\utility\ziptoarea.c

E52801 v_dialer\dialer\src\utility\ziptoarea.c

E52802 v_dialer\dialer\src\utility\ziptoarea.c

E52803 v_dialer\dialer\src\utility\ziptoarea.c

E52804 v_dialer\dialer\src\utility\ziptoarea.c

E52805 v_dialer\dialer\src\utility\ziptoarea.c

E52806 v_dialer\dialer\src\utility\ziptoarea.c

E53000 v_dialer\dialer\src\utility\copyfields.c

E53001 v_dialer\dialer\src\utility\copyfields.c

E53002 v_dialer\dialer\src\utility\copyfields.c

E53003 v_dialer\dialer\src\utility\copyfields.c

Page 241: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 239

E53004 v_dialer\dialer\src\utility\copyfields.c

E53005 v_dialer\dialer\src\utility\copyfields.c

E53006 v_dialer\dialer\src\utility\copyfields.c

E53007 v_dialer\dialer\src\utility\copyfields.c

E53008 v_dialer\dialer\src\utility\copyfields.c

E53009 v_dialer\dialer\src\utility\copyfields.c

E53010 v_dialer\dialer\src\utility\copyfields.c

E53011 v_dialer\dialer\src\utility\copyfields.c

E53012 v_dialer\dialer\src\utility\copyfields.c

E53013 v_dialer\dialer\src\utility\copyfields.c

E53014 v_dialer\dialer\src\utility\copyfields.c

E53015 v_dialer\dialer\src\utility\copyfields.c

E53016 v_dialer\dialer\src\utility\copyfields.c

E53017 v_dialer\dialer\src\utility\copyfields.c

E53018

E53019 v_dialer\dialer\src\utility\copyfields.c

E53020 v_dialer\dialer\src\utility\copyfields.c

E53021 v_dialer\dialer\src\utility\copyfields.c

E53022 v_dialer\dialer\src\utility\copyfields.c

E53023 v_dialer\dialer\src\utility\copyfields.c

E53650 v_dialer\dialer\src\imon\internetmon.c

E53651 v_dialer\dialer\src\imon\internetmon.c

E53652 v_dialer\dialer\src\imon\internetmon.c

E53654 v_dialer\dialer\src\imon\internetmon.c

E53655

E53800 v_dialer\dialer\src\utility\evmon.c

E53801 v_dialer\dialer\src\utility\evmon.c

E53802 v_dialer\dialer\src\utility\evmon.c

E53803 v_dialer\library\libdsi\src\script_lng.c

Page 242: PC4 Troubleshooting Main

240 Maintenance and Troubleshooting Guide March 2008

E53804 v_dialer\dialer\src\utility\evmon.c

E53805 v_dialer\dialer\src\utility\evmon.c

E53806 v_dialer\dialer\src\utility\evmon.c

E53807 v_dialer\dialer\src\utility\evmon.c

E53808 v_dialer\library\libdsi\src\script_lng.c

E53809 v_dialer\dialer\src\utility\evmon.c

E53810 v_dialer\dialer\src\utility\evmon.c

E53811 v_dialer\dialer\src\utility\evmon.c

E53812

E53813 v_dialer\dialer\src\utility\evmon.c

E53814 v_dialer\dialer\src\utility\evmon.c

E53815 v_dialer\dialer\src\utility\evmon.c

E53816 v_dialer\dialer\src\utility\evmon.c

E53817 v_dialer\dialer\src\utility\evmon.c

E53818 v_dialer\dialer\src\utility\evmon.c

E53819 v_dialer\dialer\src\utility\evmon.c

E54100 v_dialer\dialer\src\listserver\listserver.c

E54101 v_dialer\dialer\src\listserver\listserver.c

E54102 v_dialer\dialer\src\listserver\listserver.c

E54103 v_dialer\dialer\src\listserver\listserver.c

E54104 v_dialer\dialer\src\listserver\listserver.c

E54105 v_dialer\dialer\src\listserver\listserver.c

E54106 v_dialer\dialer\src\listserver\listserver.c

E54107 v_dialer\dialer\src\listserver\listserver.c

E54108

E54109 v_dialer\dialer\src\listserver\listserver.c

E54110 v_dialer\dialer\src\listserver\listserver.c

E54111 v_dialer\dialer\src\listserver\listserver.c

E54112 v_dialer\library\libdsi\src\clutils.c

Page 243: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 241

E54113 v_dialer\dialer\src\listserver\listserver.c

E54114 v_dialer\dialer\src\listserver\listserver.c

E54115 v_dialer\dialer\src\listserver\listserver.c

E54120 v_dialer\dialer\src\listserver\listserver.cv_dialer\dialer\DialerCmdCtrl\VoicemsgCfgTable.cpp

E54121 v_dialer\dialer\src\listserver\listserver.c

E55000 v_dialer\dialer\src\reports\reportgen\reportprn.c

E55001 v_dialer\dialer\src\reports\reportgen\reportprn.c

E55002 v_dialer\dialer\src\reports\reportgen\reportprn.c

E55200 v_dialer\dialer\src\reports\reportgen\reportsel.c

E55201 v_dialer\dialer\src\reports\reportgen\reportsel.c

E55202 v_dialer\dialer\src\reports\reportgen\reportsel.c

E55203 v_dialer\dialer\src\reports\reportgen\reportsel.c

E55204 v_dialer\dialer\src\reports\reportgen\reportsel.c

E55205 v_dialer\dialer\src\reports\reportgen\reportsel.c

E55206 v_dialer\dialer\src\reports\reportgen\reportsel.c

E55207 v_dialer\dialer\src\reports\reportgen\reportsel.c

E55400 v_dialer\dialer\src\reports\reportgen\reportsub.c

Page 244: PC4 Troubleshooting Main

242 Maintenance and Troubleshooting Guide March 2008

E55600 v_dialer\dialer\src\reports\reportgen\reportexp.cv_dialer\dialer\src\reports\reportgen\reportsel.cv_dialer\dialer\src\reports\reportgen\reportfmt.cv_dialer\dialer\src\reports\reportgen\reporthlp.c

E55601 v_dialer\dialer\src\reports\reportgen\reportsub.cv_dialer\ivr\src\ivr_supr.c

E56001 v_dialer\ivr\src\ivr_supr.c

E56002 v_dialer\ivr\src\ivr_supr.c

E56003 v_dialer\ivr\src\ivr_supr.c

E56004 v_dialer\ivr\src\ivr_config.c

E56005 v_dialer\ivr\src\ivr_config.c

E56006 v_dialer\ivr\src\ivr_config.c

E56007 v_dialer\ivr\src\ivr_config.c

E56008 v_dialer\ivr\src\ivr_config.c

E56009 v_dialer\ivr\src\ivr_config.c

E56010 v_dialer\ivr\src\ivr_config.c

E56011 v_dialer\ivr\src\ivr_config.c

E56012 v_dialer\ivr\src\ivr_config.c

E56013 v_dialer\ivr\src\ivr_config.c

E56014 v_dialer\ivr\src\ivr_config.c

E56015 v_dialer\ivr\src\ivr_config.c

E56016 v_dialer\ivr\src\ivr_config.c

E56017 v_dialer\ivr\src\ivr_config.c

E56018 v_dialer\ivr\src\ivr_config.c

E56019 v_dialer\ivr\src\ivr_config.c

E56020 v_dialer\ivr\src\ivr_conn.c

E56021 v_dialer\ivr\src\ivr_conn.c

Page 245: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 243

E56022 v_dialer\ivr\src\ivr_conn.c

E56023 v_dialer\ivr\src\ivr_conn.c

E56024 v_dialer\ivr\src\ivr_conn.c

E56025 v_dialer\ivr\src\ivr_conn.c

E56026 v_dialer\ivr\src\ivr_conn.c

E56027 v_dialer\ivr\src\ivr_conn.c

E56028 v_dialer\ivr\src\ivr_conn.c

E56029 v_dialer\ivr\src\ivr_conn.c

E56030 v_dialer\ivr\src\ivr_conn.c

E56031

E56032 v_dialer\ivr\src\ivr_conn.c

E56033 v_dialer\ivr\src\ivr_conn.c

E56034 v_dialer\ivr\src\ivr_conn.c

E56035 v_dialer\ivr\src\ivr_conn.c

E56036 v_dialer\ivr\src\ivr_conn.c

E56037 v_dialer\ivr\src\ivr_conn_io.c

E56038 v_dialer\ivr\src\ivr_conn_io.c

E56039 v_dialer\ivr\src\ivr_conn_io.c

E56040 v_dialer\ivr\src\ivr_conn_io.c

E56041 v_dialer\ivr\src\ivr_conn_io.c

E56042 v_dialer\ivr\src\ivr_conn_io.c

E56043 v_dialer\ivr\src\ivr_conn_io.c

E56044 v_dialer\ivr\src\ivr_conn.c

E56045 v_dialer\ivr\src\ivr_conn.c

E56046 v_dialer\ivr\src\ivr_conn.c

E56047 v_dialer\ivr\src\ivr_conn.c

E56048 v_dialer\ivr\src\ivr_conn.c

E56049 v_dialer\ivr\src\ivr_conn.c

E57000 v_dailer\dialer\dispatcher\dunupinit.c

Page 246: PC4 Troubleshooting Main

244 Maintenance and Troubleshooting Guide March 2008

E57001 v_dailer\dialer\dispatcher\dunupinit.c

E57002 v_dialer\dialer\src\core\ao_recall.cv_dialer\dialer\src\core\agent_time_util.cv_dialer\dialer\src\core\operator.cv_dailer\dialer\dispatcher\dunupinit.cv_dialer\dialer\src\swif\exec\opmon.c

E57003

E57004 v_dailer\dialer\dispatcher\dunupinit.c

E57005 v_dailer\dialer\dispatcher\dunupinit.c

E57006 v_dailer\dialer\dispatcher\dunupinit.c

E57007 v_dailer\dialer\dispatcher\dunupinit.c

E57008 v_dailer\dialer\dispatcher\dunupinit.cv_dailer\dialer\dispatcher\mp_change_groupid.cv_dailer\dialer\dispatcher\pa_acd_perm.cv_dailer\dialer\dispatcher\snd_agt_msg.cv_dailer\dialer\dispatcher\gateway.c

E57009 v_dailer\dialer\dispatcher\ap_aborting.cv_dailer\dialer\dispatcher\ap_acquiring.cv_dailer\dialer\dispatcher\ap_prereleasing.cv_dailer\dialer\dispatcher\ap_releasing.cv_dailer\dialer\dispatcher\dunupinit.cv_dailer\dialer\dispatcher\mp_change_groupid.cv_dailer\dialer\dispatcher\mp_job_set.cv_dailer\dialer\dispatcher\pa_acd_perm.cv_dailer\dialer\dispatcher\snd_agt_msg.cv_dailer\dialer\dispatcher\dunup.cv_dailer\dialer\dispatcher\gateway.c

E57010 v_dailer\dialer\dispatcher\dunupinit.cv_dailer\dialer\dispatcher\mp_login.c

E57011 v_dailer\dialer\dispatcher\dunup.c

E57012 v_dailer\dialer\dispatcher\dunup.c

E57013 v_dailer\dialer\dispatcher\dunup.c

Page 247: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 245

E57014 v_dailer\dialer\dispatcher\action_processor.c

E57015 v_dailer\dialer\dispatcher\du_format.cv_dailer\dialer\dispatcher\mp_genrel_query.cv_dailer\dialer\dispatcher\mp_op_headset_state.cv_dailer\dialer\dispatcher\mp_op_link_failure.cv_dailer\dialer\dispatcher\mp_response.c

E57016 v_dialer\dialer\src\core\ao_recall.cv_dialer\dialer\src\core\agent_time_util.cv_dialer\dialer\src\core\operator.cv_dailer\dialer\dispatcher\dunupinit.cv_dailer\dialer\dispatcher\genrel_util.cv_dailer\dialer\dispatcher\mp_acquire_op.cv_dailer\dialer\dispatcher\mp_call_connect.cv_dailer\dialer\dispatcher\mp_login.cv_dialer\dialer\src\swif\exec\opmon.c

E57017 v_dailer\dialer\dispatcher\dunuputil.c

E57018 v_dailer\dialer\dispatcher\event_processor.cv_dailer\dialer\dispatcher\mp_call_event.c

E57019 v_dailer\dialer\dispatcher\gateway.cv_dialer\dialer\src\swif\exec\ServMonMsg.cpp

E57020 v_dailer\dialer\dispatcher\mp_acquire_op.c

E57021 v_dailer\dialer\dispatcher\mp_acquire_op.c

Page 248: PC4 Troubleshooting Main

246 Maintenance and Troubleshooting Guide March 2008

E57022 v_dailer\dialer\dispatcher\mp_call_connect.cv_dailer\dialer\dispatcher\mp_call_event.cv_dailer\dialer\dispatcher\mp_change_groupid.cv_dailer\dialer\dispatcher\mp_create_call.cv_dailer\dialer\dispatcher\mp_domain_action.cv_dailer\dialer\dispatcher\mp_job_set.cv_dailer\dialer\dispatcher\mp_login.cv_dailer\dialer\dispatcher\mp_logout.cv_dailer\dialer\dispatcher\mp_trunk_release.cv_dailer\dialer\dispatcher\mp_user_action.c

E57023

E57024 v_dailer\dialer\dispatcher\mp_call_made.c

E57025 v_dailer\dialer\dispatcher\mp_response.c

E57026 v_dailer\dialer\dispatcher\mp_call_reject.cv_dailer\dialer\dispatcher\mp_job_set.c

E57027 v_dailer\dialer\dispatcher\mp_create_call.c

E57028 v_dailer\dialer\dispatcher\mp_domain_action.cv_dailer\dialer\dispatcher\mp_user_action.c

E57029 v_dailer\dialer\dispatcher\mp_job_set.c

E57030 v_dailer\dialer\dispatcher\mp_login.c

E57031 v_dailer\dialer\dispatcher\mp_response.c

E57032 v_dailer\dialer\dispatcher\mp_response.c

E57033 v_dailer\dialer\dispatcher\mp_response.c

E57034 v_dialer\dialer\src\core\agent_misc_util.cv_dailer\dialer\dispatcher\mp_timeout.c

E57035 v_dialer\dialer\src\core\ao_recall.cv_dialer\dialer\src\core\agent_time_util.cv_dailer\dialer\dispatcher\mp_timeout.c

Page 249: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 247

E57036 v_dialer\dialer\src\core\ao_recall.cv_dialer\dialer\src\core\agent_time_util.cv_dailer\dialer\dispatcher\mp_timeout.c

E57037

E57038 v_dailer\dialer\dispatcher\mp_login.c

E57039 v_dailer\dialer\dispatcher\mp_call_connect.c

E57040 v_dailer\dialer\dispatcher\mp_call_made.c

E57041 v_dailer\dialer\dispatcher\mp_release.c

E57042 v_dailer\dialer\dispatcher\mp_login.c

E57043 v_dailer\dialer\dispatcher\mp_user_action.c

E57044 v_dailer\dialer\dispatcher\dunupinit.c

E58002 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\caller.cv_dialer\dialer\src\core\operator.cv_dialer\dialer\src\reports\history\datamgr_init.cppv_dialer\dialer\src\swif\exec\ServMonMsg.cppv_dialer\dialer\services\srcEventServer.cppv_dialer\dialer\src\swif\exec\opmon.cv_dialer\dialer\src\core\porter.c

E59500 v_dialer\dialer\src\core\jobctrl.c

E59501 v_dialer\dialer\src\core\jobctrl.cv_dialer\dialer\DialerCmdCtrl\HeadsetLib.cpp

E59502

E59503 v_dialer\dialer\src\core\jobctrl.c

E59505 v_dialer\dialer\src\core\jobctrl.c

E59506 v_dialer\dialer\src\core\jobctrl.c

E59507 v_dialer\dialer\src\core\jobctrl.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Page 250: PC4 Troubleshooting Main

248 Maintenance and Troubleshooting Guide March 2008

E59508 v_dialer\dialer\src\core\jobctrl.c

E59508 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E59509 v_dialer\dialer\src\core\jobctrl.c

E59510 v_dialer\dialer\src\core\jobctrl.c

E59511 v_dialer\dialer\src\core\jobctrl.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E59512 v_dialer\dialer\src\core\jobctrl.c

E59513 v_dialer\dialer\src\core\jobctrl.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E59514 v_dialer\dialer\src\core\jobctrl.c

E59516 v_dialer\dialer\src\core\jobctrl.c

E59517 v_dialer\dialer\src\core\jobctrl.c

E59518 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E59519 v_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\core\jobctrl.c

E59520 v_dialer\dialer\src\core\jobctrl.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E59521 v_dialer\dialer\src\core\jobctrl.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E59522 v_dialer\dialer\src\core\jobctrl.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E59527 v_dialer\dialer\src\core\jobctrl.c

E59528 v_dialer\dialer\src\core\jobctrl.c

E59530 v_dialer\dialer\src\core\jobctrl.c

E59531

E59533 v_dialer\dialer\src\core\jobctrl.c

E59534 v_dialer\dialer\src\core\jobctrl.c

Page 251: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 249

E59535 v_dialer\dialer\src\core\jobctrl.c

E59539 v_dialer\dialer\src\core\jobctrl.c

E59540 v_dialer\dialer\src\core\jobctrl.cv_dialer\dialer\DialerCmdCtrl\HeadsetLib.cpp

E59541 v_dialer\dialer\src\core\jobctrl.cv_dialer\dialer\DialerCmdCtrl\HeadsetLib.cpp

E59542 v_dialer\dialer\src\core\jobctrl.cv_dialer\dialer\DialerCmdCtrl\HeadsetLib.cpp

E59596 v_dialer\dialer\src\core\jobctrl.c

E59597 v_dialer\dialer\src\core\jobctrl.c

E59598 v_dialer\dialer\src\core\jobctrl.c

E59599 v_dialer\dialer\src\core\jobctrl.c

E59600 v_dialer\dialer\src\core\jobctrl.c

E61000 midtier\unixdev\CmdCtrl\src\DialerCfgClient.cpp

Page 252: PC4 Troubleshooting Main

250 Maintenance and Troubleshooting Guide March 2008

E61001 midtier\unixdev\RealTimeDataServer\src\RTRMmain.cppmidtier\unixdevv_dialer\dialer\services\src\Init.cppv_dialer\dialer\services\srcEventServiceIF_i.cppmidtier\unixdev\CmdCtrl\src\DialerCfgClient.cppmidtier\unixdev\Logger\src\LoggingServer_i.cppmidtier\unixdev\ServiceActivation\src\ServiceActivatingIFImpl.cxxmidtier\unixdev\ServiceMonitor\src\ServiceMonitor_ServiceMonitoringIFImpl.cxxmidtier\unixdevv_dialer\dialer\services\src\DialerEventServerIF_i.cppmidtier\unixdevv_dialer\dialer\services\src\EventClient.cppmidtier\unixdevv_dialer\dialer\services\src\EventServer.cppmidtier\unixdevv_dialer\dialer\services\src\EventServiceIF_i.cppmidtier\unixdev\SysHealth\src\SystemHealthEntryImpl.cppv_dialer\dialer\DialerServiceActivation\src\DSAServiceIFImpl.cxx\DSHdialerSystemHealthEntryImpl.cppv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitoringIFImpl.cxx

E61002 midtier\unixdevv_dialer\dialer\services\src\EventServiceIF_i.cppv_dialer\dialer\services\srcEventServiceIF_i.cpp

Page 253: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 251

E61003 midtier\unixdev\CmdCtrl\src\DialerCfgClient.cppmidtier\unixdev\RealTimeDataServer\src\RTRMmain.cppmidtier\unixdevv_dialer\dialer\services\src\EventClient.cppmidtier\unixdevv_dialer\dialer\services\src\EventServer.cppmidtier\unixdevv_dialer\dialer\services\src\EventServiceIF_i.cppmidtier\unixdevv_dialer\dialer\services\src\Init.cppv_dialer\dialer\services\srcEventServiceIF_i.cpp

E61004 midtier\unixdev\services\src\Init.cpp

E61005 midtier\unixdev\services\src\Init.cpp

E61006 midtier\unixdev\services\src\Init.cpp

E61007 midtier\unixdev\services\src\EventServer.cpp

E61008 midtier\unixdev\services\src\ShmDataReader.cpp

E61009

E61040 midtier\unixdev\services\src\Init.cpp

E61041 midtier\unixdev\services\src\Init.cpp

E61042 midtier\unixdev\services\src\Init.cpp

E61043 midtier\unixdev\services\src\Init.cpp

E62000 v_dialer\dialer\DialerCmdCtrl\src\CmdCtrl_Table_i.cpp

E62001 dialer\Cmdctrl\CCompcodeTableSO.cppv_dialer\dialer\DialerCmdCtrl\CConfigTableSO.cpp

E62002 v_dialer\dialer\DialerCmdCtrl\AgentLib.cppv_dialer\dialer\DialerCmdCtrl\CTableSO.cppv_dialer\dialer\DialerCmdCtrl\FileTable.cpp

Page 254: PC4 Troubleshooting Main

252 Maintenance and Troubleshooting Guide March 2008

E62003 v_dialer\dialer\DialerCmdCtrl\AgentLib.cpp

E62004 v_dialer\dialer\DialerCmdCtrl\AgentLib.cppv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\dialer\DialerCmdCtrl\CSelIndexTableSO.cppv_dialer\dialer\DialerCmdCtrl\FileTable.cppv_dialer\dialer\DialerCmdCtrl\SelData.cppv_dialer\dialer\DialerCmdCtrl\StratData.cpp

E62005 v_dialer\dialer\DialerCmdCtrl\CCallSelTableSO.cppv_dialer\dialer\DialerCmdCtrl\CCallStratTableSO.cppv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\dialer\DialerCmdCtrl\CompcodeTable.cppv_dialer\dialer\DialerCmdCtrl\RecordLock.cppv_dialer\dialer\DialerCmdCtrl\RecordLock_utest.cpp

E62006 v_dialer\dialer\DialerCmdCtrl\RecordLock.cpp

E62007 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\dialer\DialerCmdCtrl\RecordLock.cpp

E62008 v_dialer\dialer\DialerCmdCtrl\CompcodeData.cppv_dialer\dialer\DialerCmdCtrl\JobData.cppv_dialer\dialer\DialerCmdCtrl\PromptData.cppv_dialer\dialer\DialerCmdCtrl\SelData.cppv_dialer\dialer\DialerCmdCtrl\StratData.cpp

E62009 v_dialer\dialer\DialerCmdCtrl\CompcodeData.cpp

Page 255: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 253

E62010 v_dialer\dialer\DialerCmdCtrl\CAgentTableSO.cppv_dialer\dialer\DialerCmdCtrl\CCallListTableSO.cppv_dialer\dialer\DialerCmdCtrl\CCallStratTableSO.cppv_dialer\dialer\DialerCmdCtrl\CConfigTableSO.cppv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\dialer\DialerCmdCtrl\CLineGrpTableSO.cppv_dialer\dialer\DialerCmdCtrl\CSelIndexTableSO.cppv_dialer\dialer\DialerCmdCtrl\CTelephnySpt.cpp

E62011 v_dialer\dialer\DialerCmdCtrl\CConfigTableSO.cppv_dialer\dialer\DialerCmdCtrl\CLineGrpTableSO.cppv_dialer\dialer\DialerCmdCtrl\CodeDescTable.cppv_dialer\dialer\DialerCmdCtrl\CSelIndexTableSO.cppv_dialer\dialer\DialerCmdCtrl\CTelephnySpt.cppv_dialer\dialer\DialerCmdCtrl\TelephnyTable.cppv_dialer\dialer\DialerCmdCtrl\VoicemsgCfgTable.cpp

E62012 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\dialer\DialerCmdCtrl\RecordLock.cpp

E62013 v_dialer\dialer\DialerCmdCtrl\AgentLib.cppv_dialer\dialer\DialerCmdCtrl\CCompcodeTableSO.cppv_dialer\dialer\DialerCmdCtrl\FileTable.cpp

E62014 v_dialer\dialer\DialerCmdCtrl\FileAccess.cpp

E62015 v_dialer\dialer\DialerCmdCtrl\FileAccess.cpp

Page 256: PC4 Troubleshooting Main

254 Maintenance and Troubleshooting Guide March 2008

E62016 v_dialer\dialer\DialerCmdCtrl\FileAccess.cpp

E62017 v_dialer\dialer\DialerCmdCtrl\FileAccess.cpp

E62018 v_dialer\dialer\DialerCmdCtrl\FileAccess.cpp

E62019 v_dialer\dialer\DialerCmdCtrl\FileAccess.cpp

E62020 v_dialer\dialer\DialerCmdCtrl\CrudulMethods.cppv_dialer\dialer\DialerCmdCtrl_Agent_i.cppv_dialer\dialer\DialerCmdCtrl_CallSelect_i.cppv_dialer\dialer\DialerCmdCtrlv_dialer\dialer\DialerCmdCtrl_CallStrategy_i.cppv_dialer\dialer\DialerCmdCtrlv_dialer\dialer\DialerCmdCtrl_Compcode_i.cppv_dialer\dialer\DialerCmdCtrl_Config_i.cppv_dialer\dialer\DialerCmdCtrl_DialerControl_i.cppv_dialer\dialer\DialerCmdCtrl_Domain_i.cppv_dialer\dialer\DialerCmdCtrl_Headset_i.cppv_dialer\dialer\DialerCmdCtrl_Ivr_i.cppv_dialer\dialer\DialerCmdCtrl_Job_i.cppv_dialer\dialer\DialerCmdCtrl_SelectIndex_i.cppv_dialer\dialer\DialerCmdCtrl_TableFactory_i.cpp

E62021 v_dialer\dialer\DialerCmdCtrl\FileAccess.cpp

E62022 v_dialer\dialer\DialerCmdCtrl\CCallSelTableSO.cppv_dialer\dialer\DialerCmdCtrl\CCallStratTableSO.cppv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Page 257: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 255

E62023 v_dialer\dialer\DialerCmdCtrl_TableFactory_i.cpp

E62024 v_dialer\dialer\DialerCmdCtrl\CCallSelTableSO.cppv_dialer\dialer\DialerCmdCtrl\CCallStratTableSO.cppv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\dialer\DialerCmdCtrl\CompcodeTable.cppv_dialer\dialer\DialerCmdCtrl\CTelephnySpt.cppv_dialer\dialer\DialerCmdCtrl\MasterCfgTable.cppv_dialer\dialer\DialerCmdCtrl\TelephnyTable.cppv_dialer\dialer\DialerCmdCtrl\VoicemsgCfgTable.cpp

E62025 v_dialer\library\libutil++\src\account_r.

E62026 v_dialer\library\libutil++\src\account_r.

Page 258: PC4 Troubleshooting Main

256 Maintenance and Troubleshooting Guide March 2008

E62027 v_dialer\dialer\DialerCmdCtrl\CrudulMethods.cppv_dialer\dialer\DialerCmdCtrl_Agent_i.cppv_dialer\dialer\DialerCmdCtrl_Blend_i.cppv_dialer\dialer\DialerCmdCtrl_CallSelect_i.cppv_dialer\dialer\DialerCmdCtrl_CallStrategy_i.cppv_dialer\dialer\DialerCmdCtrl_Compcode_i.cppv_dialer\dialer\DialerCmdCtrl_Config_i.cppv_dialer\dialer\DialerCmdCtrl_DialerControl_i.cppv_dialer\dialer\DialerCmdCtrl_Domain_i.cppv_dialer\dialer\DialerCmdCtrl_Headset_i.cppv_dialer\dialer\DialerCmdCtrl_Ivr_i.cppv_dialer\dialer\DialerCmdCtrl_Job_i.cppv_dialer\dialer\DialerCmdCtrl_SelectIndex_i.cppv_dialer\dialer\DialerCmdCtrl_TableFactory_i.cpp

E62028

E62029 v_dialer\dialer\DialerCmdCtrl\MsgQueue.cpp

E62030 v_dialer\dialer\DialerCmdCtrl\CAgentTableSO.cpp

E62031 v_dialer\dialer\DialerCmdCtrl\CAgentTableSO.cpp

E62032 v_dialer\dialer\DialerCmdCtrl\AgentShmLib_utest.cppv_dialer\dialer\DialerCmdCtrl\CAgentTableSO.cppv_dialer\dialer\DialerCmdCtrl\CCompcodeTableSO.cpp

E62033 v_dialer\dialer\DialerCmdCtrl\ShmAccess.cpp

E62034

E62035 v_dialer\dialer\DialerCmdCtrl\AgentShmLib.cpp

Page 259: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 257

E62036 v_dialer\dialer\DialerCmdCtrl\AgentShmLib.cppv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E62037 v_dialer\dialer\DialerCmdCtrl\AgentShmLib.cpp

E62038 v_dialer\dialer\DialerCmdCtrl\CAgentTableSO.cpp

E62039 v_dialer\dialer\DialerCmdCtrl\AgentShmLib_utest.cppv_dialer\dialer\DialerCmdCtrl\CAgentTableSO.cpp

E62040 v_dialer\dialer\DialerCmdCtrl\RecordLock.cpp

E62041 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E62042 v_dialer\library\libcallsel\src\cllcallsel.cpp

E62043 v_dialer\dialer\DialerCmdCtrl\AgentShmLib.cpp

E62044 v_dialer\library\libcallsel\src\cllcallsel.cpp

E62045 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E62046 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E62047 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E62048 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E62049 dialerclient\Redwood\VBApps\Editor\MDIForm1.frmv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E62050 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppdialerclient\Redwood\VBApps\Editor\MDIForm1.frm

Page 260: PC4 Troubleshooting Main

258 Maintenance and Troubleshooting Guide March 2008

E62051 dialerclient\Redwood\VBApps\Editor\MDIForm1.frmdialerclient\Redwood\VBApps\Editor\Modules\General.bas

E62052 v_dialer\dialer\DialerCmdCtrl\CCallSelTableSO.cppv_dialer\dialer\DialerCmdCtrl\CCallStratTableSO.cppv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\dialer\DialerCmdCtrl\RecordLock.cppv_dialer\dialer\DialerCmdCtrl\CompcodeTable.cpp

E62053 v_dialer\dialer\DialerCmdCtrl\CCallSelTableSO.cppv_dialer\dialer\DialerCmdCtrl\CCallStratTableSO.cppv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\dialer\DialerCmdCtrl\CompcodeTable.cppv_dialer\dialer\DialerCmdCtrl\RecordLock.cpp

E62054 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E62055 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E62056

E62057 v_dialer\dialer\DialerCmdCtrl\CSelIndexTableSO.cpp

E62058 v_dialer\dialer\DialerCmdCtrl\CSelIndexTableSO.cpp

E62059 v_dialer\dialer\DialerCmdCtrl\AgentShmLib.cpp

E62060 v_dialer\dialer\DialerCmdCtrl\CCallSelTableSO.cppv_dialer\dialer\DialerCmdCtrl\CCallStratTableSO.cppv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

E62061 v_dialer\dialer\DialerCmdCtrl\CSelIndexTableSO.cpp

Page 261: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 259

E62062 v_dialer\library\libcallsel\src\CallStgyLib.cpp

E62070 v_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cppv_dialer\dialer\DialerCmdCtrl\SptSyntaxErrorRe.cpp

E62071 v_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cppv_dialer\dialer\DialerCmdCtrl\SptSyntaxErrorRe.cpp

E62072 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

E62073 v_dialer\dialer\DialerCmdCtrl\CTelephnySpt.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

E62074 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

E62075 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

E62076 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

E62077 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

E62078 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

E62079 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

Page 262: PC4 Troubleshooting Main

260 Maintenance and Troubleshooting Guide March 2008

E62080 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

E62081 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

E62082 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

E62083 v_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cppv_dialer\dialer\DialerCmdCtrl\XmlBase.cpp

E62084 v_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cppv_dialer\dialer\DialerCmdCtrl\XmlBase.cpp

E62085 v_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cppv_dialer\dialer\DialerCmdCtrl\XmlBase.cpp

E62086 v_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cppv_dialer\dialer\DialerCmdCtrl\XmlBase.cpp

E62087 v_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cppv_dialer\dialer\DialerCmdCtrl\SptTransform.cpp

E62088 v_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cppv_dialer\dialer\DialerCmdCtrl\SptTransform.cpp

E62089 v_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cppv_dialer\dialer\DialerCmdCtrl\SptTransform.cpp

Page 263: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 261

E62090 v_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cppv_dialer\dialer\DialerCmdCtrl\XmlDomErrorHandler.cpp

E62091 v_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cppv_dialer\dialer\DialerCmdCtrl\XsltBase.cpp

E62092 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

E62093 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

E62094 v_dialer\dialer\DialerCmdCtrl\SptParserApi.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

E62095 v_dialer\dialer\DialerCmdCtrl\CTelephnySpt.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

E62096 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

E62097 v_dialer\dialer\DialerCmdCtrl\FileAccess.cpp

E62098 v_dialer\dialer\DialerCmdCtrl\FileAccess.cpp

E62099 v_dialer\dialer\DialerCmdCtrl\DccsAudioFileValidator.cpp

E62100 v_dialer\dialer\DialerCmdCtrl\DccsAudioFileValidator.cpp

E62101 v_dialer\dialer\DialerCmdCtrl\DccsAudioFileValidator.cpp

E62102 v_dialer\dialer\DialerCmdCtrl\DccsAudioFileValidator.cpp

Page 264: PC4 Troubleshooting Main

262 Maintenance and Troubleshooting Guide March 2008

E62103 v_dialer\dialer\DialerCmdCtrl\DccsAudioFileValidator.cpp

E62104 v_dialer\dialer\DialerCmdCtrl\DccsAudioFileValidator.cpp

E62105 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cpp

E62106 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cpp

E62107, E62108

E62109 v_dialer\dialer\DialerCmdCtrl\AgentShmLib.cpp

E62110-E62111

E62112 v_dialer\dialer\DialerCmdCtrl\CCallSelTableSO.cppv_dialer\dialer\DialerCmdCtrl\CCallStratTableSO.cppv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\dialer\DialerCmdCtrl\RecordLock.cppv_dialer\dialer\DialerCmdCtrl\RecordLock_utest.cpp

E62113 v_dialer\dialer\DialerCmdCtrl\CCallSelTableSO.cppv_dialer\dialer\DialerCmdCtrl\CCallStratTableSO.cppv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\dialer\DialerCmdCtrl\RecordLock.cpp

E62114

E63000 midtier\unixdev\CmdCtrl\src\CCTable.cppmidtier\unixdev\CmdCtrl\src\CmdCtrlImpl.cpp

E66666 (not in list)

v_dialer\dialer\src\core\agent.c

Page 265: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 263

E70000 v_dialer\dialer\src\core\agent_io_util.c Incorrect number of arguments

E70001 v_dialer\dialer\src\core\agent_io_util.c Incorrect message type

E70002 v_dialer\dialer\src\core\agent_time_util.c Timed out waiting for <message>

E70003 v_dialer\dialer\src\core\agent_misc_util.c Incorrect job type

E70004 v_dialer\dialer\src\core\agent_misc_util.cv_dialer\dialer\src\core\agent_sys_util.c

Command failed

E70005 v_dialer\dialer\src\core\agent_io_util.c Incoming command exceeded maximum buffer size

E70006 v_dialer\dialer\src\core\agent.c Must select unit

E70007 v_dialer\dialer\src\core\agent_tdss_util.c Cannot transfer inbound call

E70008 v_dialer\dialer\src\core\agent_tdss_util.c Must specify transfer job

E70009 v_dialer\dialer\src\core\agent_tdss_util.c Unable to send message to porter

E70010 v_dialer\dialer\src\core\agent_tdss_util.c Conference in progress

E70011 v_dialer\dialer\src\core\agent_hs_util.c Call blending is not available

E70012 v_dialer\dialer\src\core\agent_misc_util.c Password has expired

E70013 v_dialer\dialer\src\core\agent_misc_util.c Password can not be changed, change limit not expired

E70014

E70015 v_dialer\dialer\src\core\agent_misc_util.c Unable to become root privilege for setting password

E70016 v_dialer\dialer\src\core\agent_misc_util.c Original password is invalid

E70017 v_dialer\dialer\src\core\agent_misc_util.c New password entered is invalid

E70018 v_dialer\dialer\src\core\agent.c IVR_SCRIPT is blank in job <name>

E70019 v_dialer\dialer\src\core\agent.c Job <name> is not valid for IVR agents

E72000 v_dialer\dialer\DialerServiceActivation\src\DSA.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitor.cxx

Page 266: PC4 Troubleshooting Main

264 Maintenance and Troubleshooting Guide March 2008

E72010 v_dialer\dialer\DialerServiceActivation\src\DSA.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitor.cxx

E72030 v_dialer\dialer\DialerServiceActivation\src\DSA.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitor.cxx

E72040 v_dialer\dialer\DialerServiceActivation\src\DSA.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitor.cxx

E72050 v_dialer\dialer\DialerServiceActivation\src\DSA.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitor.cxx

E72051 v_dialer\dialer\DialerServiceActivation\src\DSA.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitor.cxx

E72052 v_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitorIFImpl.cxx

E72060 v_dialer\dialer\DialerServiceActivation\src\DSA.cxxv_dialer\dialer\DialerServiceMonitor\src\DSMEvent.cxxv_dialer\dialer\DialerServiceMonitor\src\EventReceiver.cxxv_dialer\dialer\DialerServiceMonitor\src\SoeEvent.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceController.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitor.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitorIFImpl.cxx

E72070 v_dialer\dialer\DialerServiceActivation\src\DSA.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitor.cxx

Page 267: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 265

E72080 v_dialer\dialer\DialerServiceActivation\src\DSA.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitor.cxx

E72090 v_dialer\dialer\DialerServiceActivation\src\DSA.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitor.cxx

E72100 v_dialer\dialer\DialerServiceActivation\src\DSA.cxx

E72110

E72120 v_dialer\dialer\DialerServiceActivation\src\DSAIFImpl.cxx

E72130 v_dialer\dialer\DialerServiceActivation\src\DSAIFImpl.cxx

E72140 v_dialer\dialer\DialerServiceActivation\src\DSAIFImpl.cxx

E72150 v_dialer\dialer\DialerServiceActivation\src\DSAIFImpl.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceController.cxx

E72160 v_dialer\dialer\DialerServiceActivation\src\DSA.cxxv_dialer\dialer\DialerServiceActivation\src\DSAIFImpl.cxxv_dialer\dialer\DialerServiceActivation\src\DSAServiceIFImpl.cxxv_dialer\dialer\DialerServiceMonitor\src\EventReceiver.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceController.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitor.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitorIFImpl.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitoringIFImpl.cxx

E72170 v_dialer\dialer\DialerServiceActivation\src\DSARequest.cxx

E72180 v_dialer\dialer\DialerServiceActivation\src\DSARequest.cxx

Page 268: PC4 Troubleshooting Main

266 Maintenance and Troubleshooting Guide March 2008

E72190 v_dialer\dialer\DialerServiceActivation\src\DSARequest.cxx

E72200 v_dialer\dialer\DialerServiceActivation\src\DSARequest.cxx

E72201 (not in list)

v_dialer\dialer\DialerServiceActivation\src\DSARequest.cxx

E72210 v_dialer\dialer\DialerServiceActivation\src\DSARequest.cxx

E72220 v_dialer\dialer\DialerServiceActivation\src\DSARequest.cxx

E72230 v_dialer\dialer\DialerServiceActivation\src\DSARequest.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitorIFImpl.cxx

E72240 v_dialer\dialer\DialerServiceActivation\src\DSARequest.cxx

E72250 v_dialer\dialer\DialerServiceActivation\src\DSARequest.cxx

E72260 v_dialer\dialer\DialerServiceActivation\src\DSAServiceIFImpl.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitor.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitorIFImpl.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitoringIFImpl.cxx

E72270 v_dialer\dialer\DialerServiceMonitor\src\DialerServiceController.cxx

E72280 v_dialer\dialer\DialerServiceMonitor\src\\DialerServiceMonitor.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitorIFImpl.cxx

E72290 v_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitorIFImpl.cxx

E72300 v_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitorIFImpl.cxx

Page 269: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 267

E72310 v_dialer\dialer\DialerServiceMonitor\src\EventReceiver.cxx

E72320(not in list)

v_dialer\dialer\DialerServiceMonitor\src\EventReceiver.cxxv_dialer\dialer\DialerServiceMonitor\src\SoeEvent.cxx

Page 270: PC4 Troubleshooting Main

268 Maintenance and Troubleshooting Guide March 2008

Page 271: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 269

Error message text and source file table

The table in this section includes the error messafge number, text, and source files.

Error Numbers Found in these files Error message

E00000 v_dialer\dialer\src\core\job_strter.c

E00500 v_dialer\dialer\src\core\caller.cv_dialer\dialer\src\callsel\callsel.cv_dialer\dialer\src\core\job_strter.cv_dialer\dialer\src\core\joblib.cv_dialer\dialer\src\core\donotcall.cv_dialer\dialer\src\preprocess\listdist.cv_dialer\dialer\enforcer\src\enforcer.cppv_dialer\dialer\src\swif\exec\swid_main.cv_dialer\dialer\src\core\nuisance.cv_dialer\dialer\src\core\porter.cv_dialer\dialer\src\dbconst\readtape.cv_dialer\dialer\src\core\recall_rmp.cv_dialer\dialer\src\dbmaint\record_ed.cv_dialer\dialer\src\core\switcher.cv_dialer\dialer\src\dbconst\writetape.c

%s - Caught signal %d (%s)

Page 272: PC4 Troubleshooting Main

270 Maintenance and Troubleshooting Guide March 2008

E00501 v_dialer\admin\src\signalit.cv_dialer\admin\src\termprocess.cv_dialer\dialer\src\utility\agentcheck.cv_dialer\dialer\src\utility\agentcount.cv_dialer\dialer\src\core\ao_recall.cv_dialer\dialer\src\core\beeper.cv_dialer\dialer\src\callsel\callconn.cv_dialer\dialer\src\core\conn_mgr.cv_dialer\dialer\src\dbconst\moj_conv.cv_dialer\dialer\src\utility\list_status.cv_dialer\dialer\DialerServiceActivation\src\DSA.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitor.cxxv_dialer\dialer\src\reports\rpt_mgr\pds_view.cv_dialer\dialer\src\reports\rpt_mgr\rpt_view.c

%s - Caught signal %d (%s) and terminated

Page 273: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 271

E00502 v_dialer\dialer\src\core\caller.cv_dialer\dialer\src\callsel\callsel.cv_dialer\dialer\src\markrec\chkentdt.cv_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\src\core\conn_mgr.cv_dialer\admin\src\createop.cv_dialer\dialer\src\callsel\cseldmp.cv_dialer\dialer\src\callsel\call_scrn.cv_dialer\dialer\src\callsel\call_stgy.cv_dialer\dialer\src\core\agent_misc_util.cv_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\core\jobscrn.cv_dialer\dialer\src\core\listops.cv_dialer\dialer\src\core\port_hndle.cv_dialer\dialer\src\core\screen.cv_dialer\dialer\src\dbconst\moj_conv.cv_dialer\dialer\src\reports\reportgen\reportfmt.cv_dialer\dialer\src\swif\exec\swid_main.cv_dialer\dialer\src\lstextract\ext_list.cv_dialer\dialer\src\preprocess\ij_merge.cv_dialer\ivr\src\ivr_config.cv_dialer\dialer\src\markrec\latelst.cv_dialer\dialer\src\markrec\latemrk.cv_dialer\dialer\src\preprocess\listdist.cv_dialer\dialer\src\editor\master_ed.cv_dialer\dialer\DialerCmdCtrl\AgentLib.cppv_dialer\dialer\src\core\porter.cv_dialer\dialer\src\postupdate\postupdate.cv_dialer\dialer\src\dbmaint\record_ed.cv_dialer\dialer\src\preprocess\setzones.cv_dialer\dialer\src\utility\ziptoarea.cv_dialer\dialer\src\core\screen.c

%s - Failed to allocate Memory

Page 274: PC4 Troubleshooting Main

272 Maintenance and Troubleshooting Guide March 2008

E00503 v_dialer\dialer\src\callsel\callconn.cv_dialer\dialer\src\callsel\callsel.cv_dialer\dialer\src\dbconst\selection.cv_dialer\dialer\src\reports\history\hist_rpt.cv_dialer\dialer\src\lstextract\ext_data.cv_dialer\dialer\src\markrec\get_field.cv_dialer\dialer\src\dbconst\readtape.cv_dialer\dialer\src\markrec\set_field.cv_dialer\dialer\src\menu\submenu.cv_dialer\dialer\src\dbconst\writetape.c

%s - Pattern error: %s

E00504 v_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\swif\exec\swid_main.cv_dialer\dialer\src\utility\pds_pg.cv_dialer\dialer\src\dbconst\readtape.cv_dialer\dialer\src\dbconst\writetape.c

%s - Bad argument

E00505 v_dialer\dialer\src\markrec\latelst.c %s - Invalid time format

E00506 v_dialer\dialer\src\markrec\latelst.c %s - Invalid date format

E00507 v_dialer\dialer\src\listserver\listserver.cv_dialer\dialer\DialerCmdCtrl\MasterCfgTable.cppv_dialer\dialer\src\utility\port_start.c

%s - Failed to retrieve environmental variable %s

E00508 v_dialer\dialer\src\core\caller.cv_dialer\dialer\src\callsel\call_scrn.cv_dialer\dialer\src\core\joblib.cv_dialer\dialer\src\listserver\listserver.cv_dialer\dialer\src\core\porter.cv_dialer\dialer\src\preprocess\setzones.cv_dialer\dialer\src\reports\history\vrecords.c

%s - Entry %s missing/invalid in master.cfg file

Page 275: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 273

E00509 v_dialer\dialer\src\markrec\chkentdt.cv_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\dbconst\moj_conv.cv_dialer\dialer\src\preprocess\msgmap.cv_dialer\dialer\src\markrec\get_field.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\dialer\src\postupdate\postupdate.cv_dialer\dialer\src\dbmaint\rec_update.cv_dialer\dialer\src\scrnbld\scrnbld.cv_dialer\dialer\src\markrec\set_field.cv_dialer\dialer\src\preprocess\update_cl.cv_dialer\dialer\src\reports\history\vrecords.c

%s - Entry %s missing/invalid in %s file

E00510 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\callsel\callsel.cv_dialer\dialer\src\markrec\chkentdt.cv_dialer\dialer\src\core\conn_mgr.cv_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\core\dnc_mark.cv_dialer\dialer\src\core\listops.cv_dialer\dialer\src\core\operator.cv_dialer\dialer\src\dbconst\moj_conv.cv_dialer\dialer\src\preprocess\ij_merge.cv_dialer\dialer\src\markrec\latelst.cv_dialer\dialer\src\dbconst\readtape.cv_dialer\dialer\src\dbmaint\record_ed.cv_dialer\dialer\src\preprocess\setzones.cv_dialer\dialer\src\dbconst\writetape.c

%s - Entry %s is incompatible in length

Page 276: PC4 Troubleshooting Main

274 Maintenance and Troubleshooting Guide March 2008

E00511 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\callsel\callsel.cv_dialer\dialer\src\markrec\chkentdt.cv_dialer\dialer\src\core\conn_mgr.cv_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\core\dnc_mark.cv_dialer\dialer\src\core\listops.cv_dialer\dialer\src\core\operator.cv_dialer\dialer\src\dbconst\moj_conv.cv_dialer\dialer\src\dbmaint\redit_scrn.cv_dialer\dialer\src\preprocess\ij_merge.cv_dialer\dialer\src\markrec\latelst.cv_dialer\dialer\src\dbconst\readtape.cv_dialer\dialer\src\dbmaint\record_ed.cv_dialer\dialer\src\preprocess\setzones.cv_dialer\dialer\src\dbconst\writetape.c

%s - Failed to process file %s

E00512 v_dialer\dialer\DialerCmdCtrl\DccsVmValidator.cpp

%s - File name %s too long

E00513 v_dialer\dialer\src\callsel\callsel.cv_dialer\dialer\src\reports\reportgen\reportfmt.cv_dialer\dialer\src\preprocess\listdist.cv_dialer\dialer\src\utility\pds_pg.cv_dialer\dialer\src\scrnbld\scrnbld.c

%s - Invalid file name %s

E00514 dialer_library\libdsi\src\dispkey.cdialer_library\libdsi\src\help.cdialer_library\libui\src\vlui.c

%s - File name %s already exist

Page 277: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 275

E00515 v_dialer\admin\src\addgroup.cv_dialer\dialer\src\utility\adump.cv_dialer\dialer\src\core\ao_recall.cv_dialer\dialer\src\callsel\callconn.cv_dialer\dialer\src\core\caller.cv_dialer\dialer\src\callsel\callsel.cv_dialer\dialer\src\markrec\chkentdt.cv_dialer\dialer\src\preprocess\clhashin.cv_dialer\dialer\src\editor\config_ed.cv_dialer\admin\src\createop.cv_dialer\dialer\src\callsel\cseldmp.cv_dialer\dialer\src\core\agent_io_util.cv_dialer\dialer\src\core\agent_tdss_util.cv_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\core\chainhandler.cv_dialer\dialer\src\core\dnc_mark.cv_dialer\dialer\src\core\install_ext.cv_dialer\dialer\src\core\job_strter.cv_dialer\dialer\src\core\listops.cv_dialer\dialer\src\core\screen.c8v_dialer\dialer\src\core\transfer.cv_dialer\dialer\src\dbconst\moj_conv.cv_dialer\dialer\src\pcextract\fileops.cv_dialer\dialer\src\custom\readwrt.cv_dialer\dialer\src\utility\portcorr.cv_dialer\dialer\src\utility\test_help.cv_dialer\library\libdsi\src\rpt_server.cv_dialer\dialer\src\swif\exec\opmoncfg.cv_dialer\dialer\src\utility\edump.cv_dialer\dialer\src\utility\fdictdump.cv_dialer\dialer\src\lettergen\formlet.cv_dialer\dialer\src\markrec\get_field.cv_dialer\dialer\src\preprocess\hsh_dump.cv_dialer\dialer\src\preprocess\ij_merge.cv_dialer\dialer\src\imon\internetmon.cv_dialer\ivr\src\ivr_config.cv_dialer\dialer\src\utility\jobkeys.c

%s - Failed to open file %s

Page 278: PC4 Troubleshooting Main

276 Maintenance and Troubleshooting Guide March 2008

E00515 v_dialer\dialer\src\markrec\latelst.cv_dialer\dialer\src\markrec\latemrk.cv_dialer\dialer\src\preprocess\listdist.cv_dialer\dialer\src\lettergen\mail_label.cv_dialer\dialer\src\editor\master_ed.cv_dialer\dialer\src\menu\menu.cv_dialer\dialer\src\dbconst\moj_conv.cv_dialer\dialer\src\core\msg_loader.cv_dialer\dialer\DialerServiceActivation\src\DSAIFImpl.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceController.cxxv_dialer\dialer\enforcer\src\enlicense.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cppv_dialer\dialer\DialerCmdCtrl\SptValidatingProcessor_utest.cppv_dialer\dialer\src\core\nuisance.cv_dialer\dialer\src\reports\history\op_hist.cv_dialer\dialer\src\core\porter.cv_dialer\dialer\src\postupdate\postupdate.cv_dialer\dialer\src\utility\print_pif.cv_dialer\dialer\src\dbconst\readtape.cv_dialer\dialer\src\dbmaint\rec_update.cv_dialer\dialer\src\dbmaint\record_ed.cv_dialer\dialer\src\reports\rpt_mgr\rpt_view.cv_dialer\dialer\src\utility\scan.cv_dialer\dialer\src\scrnbld\scrnbld.cv_dialer\dialer\src\markrec\set_field.cv_dialer\dialer\src\menu\submenu.cv_dialer\dialer\src\preprocess\update_cl.cv_dialer\dialer\src\reports\history\vrecords.cv_dialer\dialer\src\dbconst\writetape.cv_dialer\dialer\src\utility\ziptoarea.c

Page 279: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 277

E00516 v_dialer\dialer\DialerServiceActivation\src\DSAIFImpl.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceController.cxx

%s - Failed to close file %s

E00517 v_dialer\dialer\src\preprocess\clhashin.cv_dialer\dialer\src\markrec\latelst.cv_dialer\dialer\src\utility\ziptoarea.c

%s - Failed to create file %s

E00518 v_dialer\dialer\src\callsel\callconn.cv_dialer\dialer\src\callsel\callsel.cv_dialer\dialer\src\callsel\call_scrn.cv_dialer\dialer\src\core\agent_misc_util.cv_dialer\dialer\src\core\agent_sys_util.cv_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\core\screen.cv_dialer\dialer\src\dbconst\moj_conv.cv_dialer\dialer\src\dbmaint\redit_scrn.cv_dialer\dialer\src\pcextract\fileops.cv_dialer\dialer\src\reports\history\op_hist.cv_dialer\dialer\src\markrec\latelst.cv_dialer\dialer\DialerCmdCtrl\DccsAudioFileValidator.cppv_dialer\dialer\src\reports\history\op_hist.cv_dialer\dialer\src\dbconst\readtape.c

%s - Failed to read from file %s

E00519 v_dialer\dialer\src\callsel\callsel.cv_dialer\dialer\src\preprocess\clhashin.cv_dialer\dialer\src\dbconst\moj_conv.cv_dialer\dialer\src\markrec\latelst.cv_dialer\dialer\src\dbconst\writetape.c

%s - Failed to write to file %s

E00520 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\src\reports\history\vrecords.c

%s - Failed to lock file %s

E00521 v_dialer\library\libdsi\src\getnum.c %s - Failed to unlock file %s

E00522 v_dialer\dialer\src\utility\enq_pty.cv_dialer\dialer\Cmdctrl\HeadsetLib.cppv_dialer\dialer\Cmdctrl\ShmAccess.cpp

%s - Failed to attach to shm, err=%d, id=%d

Page 280: PC4 Troubleshooting Main

278 Maintenance and Troubleshooting Guide March 2008

E00523 v_dialer\library\libdsi\src\conn_queue.c %s - Failed to detach from shm, err=%d, id=%d

E00524 v_dialer\library\libdsi\src\conn_queue.c %s - Failed to remove shm, err=%d, id=%d

E00525 v_dialer\library\libdsi\src\mqueue.c %s - Failed to get msgq, err=%d, id=%d

E00526 v_dialer\library\libdsi\src\mqueue.c %s - Failed to send msg, err=%d, id=%d

E00527 v_dialer\library\libdsi\src\mqueue.c %s - Failed to recv msg, err=%d, id=%d

E00528 v_dialer\library\libdsi\src\mqueue.c %s - Failed to remove msgq, err=%d, id=%d

E00529 v_dialer\dialer\src\callsel\callsel.cv_dialer\dialer\src\dbmaint\rec_update.cv_dialer\dialer\src\swif\exec\swid_main.c

%s - Failed to invoke function %s, err=%d

Page 281: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 279

E00530 v_dialer\dialer\src\preprocess\clhash.cv_dialer\dialer\src\preprocess\clhashin.cv_dialer\dialer\src\callsel\call_scrn.cv_dialer\dialer\src\core\dnc_mark.cv_dialer\dialer\src\core\listops.cv_dialer\dialer\src\core\screen.cv_dialer\dialer\src\dbmaint\redit_scrn.cv_dialer\dialer\src\reports\reportgen\reportinit.cv_dialer\dialer\src\lstextract\ext_data.cv_dialer\dialer\src\lstextract\ext_list.cv_dialer\dialer\src\utility\fdictdump.cv_dialer\dialer\src\lettergen\formlet.cv_dialer\dialer\src\preprocess\ij_merge.cv_dialer\dialer\src\preprocess\listdist.cv_dialer\dialer\src\lettergen\mail_label.cv_dialer\dialer\src\preprocess\setzones.cv_dialer\dialer\src\preprocess\update_cl.cv_dialer\dialer\src\preprocess\update_upl.cv_dialer\dialer\src\dbconst\writetape.cv_dialer\dialer\src\utility\ziptoarea.c

%s - Failed to open calling list %s

Page 282: PC4 Troubleshooting Main

280 Maintenance and Troubleshooting Guide March 2008

E00531 v_dialer\dialer\src\preprocess\clhash.cv_dialer\dialer\src\preprocess\clhashin.cv_dialer\dialer\src\callsel\call_scrn.cv_dialer\dialer\src\core\dnc_mark.cv_dialer\dialer\src\core\screen.cv_dialer\dialer\src\dbmaint\redit_scrn.cv_dialer\dialer\src\preprocess\ij_merge.cv_dialer\dialer\src\preprocess\listdist.cv_dialer\dialer\src\postupdate\postupdate.cv_dialer\dialer\src\preprocess\setzones.cv_dialer\dialer\src\preprocess\update_cl.cv_dialer\dialer\src\preprocess\update_upl.cv_dialer\dialer\src\dbconst\writetape.cv_dialer\dialer\src\utility\ziptoarea.c

%s - Failed to read calling list definition %s

E00532 v_dialer\dialer\src\markrec\chkentdt.cv_dialer\dialer\src\preprocess\clhash.cv_dialer\dialer\src\preprocess\clhashin.cv_dialer\dialer\src\preprocess\de_reject.cv_dialer\dialer\src\callsel\call_scrn.cv_dialer\dialer\src\core\listops.cv_dialer\dialer\src\core\screen.cv_dialer\dialer\src\lstextract\ext_data.cv_dialer\dialer\src\preprocess\ij_merge.cv_dialer\dialer\src\markrec\latelst.cv_dialer\dialer\src\markrec\latemrk.cv_dialer\dialer\src\preprocess\listdist.cv_dialer\dialer\src\lettergen\mail_label.cv_dialer\dialer\src\preprocess\setzones.cv_dialer\dialer\src\preprocess\update_cl.cv_dialer\dialer\src\preprocess\update_upl.cv_dialer\dialer\src\utility\ziptoarea.c

Field %s not defined in calling list %s

E00533 v_dialer\dialer\src\preprocess\listdist.c Field %s has incorrect length

Page 283: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 281

E00534 v_dialer\dialer\src\core\agent_tdss_util.cv_dialer\dialer\src\core\transfer.cv_dialer\dialer\src\dbconst\readtape.c

Not a calling list

E00535 v_dialer\dialer\src\callsel\callsel.cv_dialer\dialer\src\dbconst\readtape.cv_dialer\dialer\src\dbconst\writetape.c

%s - No space on file system

E00536 v_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\dbconst\moj_conv.c

%s - Failed to initialize keyboard

E00537 v_dialer\dialer\src\core\api_jobctl.c %s - Failed to initialize screen environment

E00538 v_dialer\dialer\src\core\api_jobctl.c %s - Failed to setup command keys

E00539 v_dialer\dialer\src\core\api_jobctl.c %s - Failed to create %s window

E00540 v_dialer\library\libui\src\vlui.c %s - Failed to create window pointer

E00541 v_dialer\dialer\src\core\screen.cv_dialer\dialer\src\dbmaint\redit_scrn.cv_dialer\dialer\src\utility\vfiles.c

%s - Failed to open keys file %s

E00542 v_dialer\dialer\src\preprocess\clhashin.cv_dialer\dialer\src\dbconst\selection.c

%s - Field %s not defined in calling list %s

E00543 v_dialer\dialer\src\preprocess\clhash.c Field %s not defined in calling list %s (WARNING)

E00544 v_dialer\dialer\src\core\listops.c %s - Invalid Pattern '%s'

Page 284: PC4 Troubleshooting Main

282 Maintenance and Troubleshooting Guide March 2008

E00545 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\ao_recall.cv_dialer\dialer\src\core\caller.cv_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\src\core\conn_mgr.cv_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\agent_misc_util.cv_dialer\dialer\src\core\chainhandler.cv_dialer\dialer\src\core\job_strter.cv_dialer\dialer\src\core\joblib.cv_dialer\dialer\src\core\listops.cv_dialer\dialer\src\core\op_handler.cv_dialer\dialer\src\core\operator.cv_dialer\dialer\src\core\port_hndle.cv_dialer\dialer\src\core\scripter.cv_dialer\dialer\src\core\jobctrl.cv_dialer\dialer\src\core\recall_rmp.c

%s:fail to send %s to %s

E00546 v_dialer\library\libutil\src\checkdir.c Failed to create directory '%s' -- errno %d: %s

E00547 v_dialer\library\libutil\src\checkdir.c Non-directory '%s' in directory path '%s'

E00548 v_dialer\dialer\src\core\conn_mgr.cmidtier\unixdev\services\src\ShmDataReader.cpp

Missing/invalid entry for %s in file %s

E00549 v_dialer\dialer\src\core\conn_mgr.cv_dialer\dialer\src\listserver\listserver.cmidtier\unixdev\services\src\ShmDataReader.cpp

%s operation failed, file '%s' -- errno %d: %s

E00550 midtier\unixdev\services\src\ShmDataReader.cpp

Invalid entry for %s in file %s near '%s'

E00551 Assertion failed (expression false), aborting

E00552 v_dialer\dialer\src\listserver\listserver.cmidtier\unixdev\services\src\ShmDataReader.cpp

Failed to open directory %d

E00553 midtier\unixdev\services\src\ShmDataReader.cpp

File '%s' does not exist

E00554 v_dialer\dialer\src\listserver\listserver.c %s operation failed

Page 285: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 283

E00555 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.cv_dialer\dialer\src\\callsel\md_callsel.cmidtier\unixdev\services\src\EventServiceIF_i.cppv_dialer\dialer\DialerCmdCtrl\expr_utest.cpp

%s - %s

E00556 v_dialer\library\libutil++\src\ReadOnlyFile.cpp

File '%s' exists, but is not readable by user %s

E00557 v_dialer\library\libutil++\src\WriteOnlyFile.cpp

File '%s' exists, but is not writable by user %s

E10000 v_dialer\library\libdsi\src\asclist.c Exceeded max number (%d) of associate calling lists

E10001 v_dialer\library\libdsi\src\asclist.c Not an associate List

E10002 v_dialer\library\libdsi\src\asclist.c Not an associate select file: %s

E10003 v_dialer\library\libdsi\src\asclist.c Associate list name missing

E10004 v_dialer\library\libdsi\src\asclist.c Associate list name not in assoc.cfg file

E10005 v_dialer\library\libdsi\src\asclist.c %s - Creation time for %s is incorrect

E10006 v_dialer\library\libdsi\src\asclist.c Failed to change master clist: %s

E10007 v_dialer\library\libdsi\src\asclist.c Invalid logical connector at line %d

E10008 v_dialer\library\libdsi\src\asclist.c Missing field name or value at line %d

E10009 v_dialer\library\libdsi\src\asclist.c Group may not begin with no selection

E10010 v_dialer\library\libdsi\src\asclist.c Gap found between select fields within group

E10011 v_dialer\library\libdsi\src\asclist.c Field name not found at line %d

E10012 v_dialer\library\libdsi\src\asclist.cv_dialer\library\libdsi\src\script_lng.c

Pattern error at line %d: %s

E10013 v_dialer\library\libdsi\src\sock_stream.cpp

can't find service entry in /etc/services, errno=%d

E10014 v_dialer\library\libdsi\src\sock_stream.cpp

socket call failed, errno=%d

Page 286: PC4 Troubleshooting Main

284 Maintenance and Troubleshooting Guide March 2008

E10015 v_dialer\library\libdsi\src\sock_stream.cpp

Unable to bind to local address, errno=%d

E10016 v_dialer\library\libdsi\src\sock_stream.cpp

Unable to setup listen on socket, errno=%d

E10017 v_dialer\library\libdsi\src\sock_stream.cpp

Unable to accept connection on socket, errno=%d

E10018 v_dialer\library\libdsi\src\sock_stream.cpp

Unable to connect to socket, errno=%d

E10019 v_dialer\library\libdsi\src\sock_stream.cpp

Unable to send data to socket %d, errno=%d

E10200 Unequal phone number field lengths in file %s

E10201 v_dialer\dialer\src\core\operator.c Invalid line selection

E10600 Failed to allocate memory

E10601 Invalid usage

E10602 v_dialer\dialer\src\core\job_strter.c Invalid job name

E10603 Failed to open edit file

E10604 No editable line in job file

E10605 Job file in use

E10606 Wrong job for verification editor

E10607 Required field not filled in

E10608 HUNTGRP format error

E10609 No HUNTGRP setting

E10610 No Inbound jobs allowed

E10611 Invalid number of reserve inbound line

E10612 Script label for answer missing/invalid

E10613 Failed to read inbound calling list

E10614 Failed to read associated calling list

E10615 Failed to read inbound screen file

Page 287: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 285

E10616 Failed to read inbound screen map

E10617 Failed to read multiple screen

E10618 Failed to read multiple screen map

E10619 Failed to read associated screen

E10620 Failed to read associated screen map

E10621 Failed to read outbound list

E10622 Failed to read outbound screen

E10623 Failed to read outbound map

E10624 Failed to read calling script

E10625 Failed to read key file

E10626 Failed to match associated field

E10627 Failed to process data transfer field

E10628 Failed to process associated selection

E10629 dialerclient\Redwood\VBAppsApps\Editor\MDIForm1.frmdialerclient\Redwood\VBApps\Editor\Classes\CJobs.cls

Selection list not available for use

E10630 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

STATUSFLAG field missing

E10631 CODE field missing

E10632 DTE field missing

E10633 TME field missing

E10634 Invalid start or stop time format

E10635 Invalid Hit Rate

E10636 Invalid Expert Calling Ratio

E10637 Invalid call completion code for Quota Value

E10638 Invalid quota value

Page 288: PC4 Troubleshooting Main

286 Maintenance and Troubleshooting Guide March 2008

E10639 Invalid paired phone count/type

E10640 Invalid number of phone lines

E10641 Odd number of phone lines specified

E10642 Invalid phone type specified

E10643 Failed to initialize call strategy

E10644 Failed to read call strategy

E10645 Failed to verify call strategy

E10646 The specified job already running

E10648 Non-OP completion code specified for Quota setting

E10649 v_dialer\library\libdsi\src\job_cntrl.c Failed to find linked job file

E10650 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\library\libdsi\src\job_cntrl.c

Linking between virtual agent jobs and non-virtual jobs is not permitted

E10651 Sales verification job linking is not permitted

E10652 Job linking is not permitted

E10653 Invalid call completion code for TRANSTAT

E10654 dialer_client\VB\Editor\MDIForm1.frmdialer_client\VB\Editor\Classes\CJobs.cls

Selection list for job not found

E10655 dialer_client\VB\Editor\MDIForm1.frmdialer_client\VB\Editor\Classes\CJobs.cls

No verification selection list ready for job

E10656 dialer_client\VB\Editor\MDIForm1.frmdialer_client\VB\Editor\Classes\CJobs.cls

Selection list not created with this calling list

E10657 missing or invalid script label for call

E10658 Failed to open script file for IVR ID

E10659 IVR script name not specified; required if IVR ID specified

Page 289: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 287

E10660 dialerclient\Redwood\VBApps\Editor\MDIForm1.frm

Unable to find script name in script file for IVR ID

E10661 remote list use not permitted

E10662 Sales verification or managed dialing must have agents

E10663 Managed dialing is not permitted with sales verification or inbound

E10664 Virtual agents cannot select a specific unit to log in to

E10665 Sales verification is not permitted with unit work lists

E10666 Sales verification is not permitted with inbound

E10667 Selecting unit to log in to is not permitted with inbound-only job

E10800 Not an error

E10801 Not an open file descriptor

E10802 Failed to open file

E10803 Failed to close file

E10804 Failed to lock record

E10805 Failed to unlock record

E10806 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Failed to read file header

E10807 Failed to write file header

E10808 v_dialer\library\libutil++\src\KeywordValue.cppv_dialer\library\libutil++\src\mbcs_string.cppv_dialer\library\libutil++\src\SerializableErrorRev_dialer\dialer\src\core\porter.cppv_dialer\library\libutil++\src\SerializableKvErrorStorage.cpp

Failed to read record

E10809 Failed to write record

E10810 Failed to allocate CLSTAT table

Page 290: PC4 Troubleshooting Main

288 Maintenance and Troubleshooting Guide March 2008

E10811 Failed to get record totals

E10812 Invalid operation code

E10813 Failed to read file dictionary

E10814 Failed to write file dictionary

E10815 Failed to create file

E10816 Failed to access file

E10817 Unconverted to year 2000

E10818 Unable to connect to listserver

E10819 XFD overflow (no XFD slots available)

E10820 Socket read error

E10821 Socket write error

E10822 Tag value incorrect - message alignment/framing error

E10823 File is open for reading only

E10824 File is open for writing only

E10850 v_dialer\library\libdsi\src\claccess.c Unable to open list '%s'

E10851 v_dialer\library\libdsi\src\claccess.c gethostbyname ('%s') failed

E10852 v_dialer\library\libdsi\src\claccess.c socket () failed

E10853 v_dialer\library\libdsi\src\claccess.c connect (conn_fd=%d) failed (is listserver running on host '%s'?)

E10854 v_dialer\library\libdsi\src\claccess.c _LcCreateXfd () failed

E10855 v_dialer\library\libdsi\src\claccess.c Write error -- wrote %d != expected %d

E10856 v_dialer\library\libdsi\src\claccess.c clstat (%d) failed

E10857 v_dialer\library\libdsi\src\claccess.c clrddict (%d) failed

E10858 v_dialer\library\libdsi\src\claccess.c getservbyname () failed -- using default LSERVPORT value (%d)

E10859 v_dialer\library\libdsi\src\cllaccess.c Bad file descriptor (%d)

Page 291: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 289

E10860 v_dialer\library\libdsi\src\claccess.c File corruption or record size mismatch detected in calling list %s; fd=%d

E10861 v_dialer\library\libdsi\src\cllaccess.c Failed to remove file %s

E10900 v_dialer\library\libdsi\src\conn_crit.c Error: Value: <%s> not in master.cfg

E11000 v_dialer\library\libcallsel\src\CallStgyLib.cppv_dialer\library\libdsi\src\cstgy.c

Error: Recall attempt #%d (%s) can't be less than %d seconds

E11001 v_dialer\library\libcallsel\src\CallStgyLib.cppv_dialer\library\libdsi\src\cstgy.c

Recall (%s) attempts can't exceed %d

E11002 v_dialer\library\libcallsel\src\CallStgyLib.cppv_dialer\library\libdsi\src\cstgy.c

Invalid recall code: %s

E11003 v_dialer\library\libutil++\src\FileMasterConfig.cppv_dialer\library\libdsi\src\cstgy.c

Failed to determine max number of phones

E11004 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Field value missing

E11005 v_dialer\library\libcallsel\src\CallStgyLib.cppv_dialer\library\libdsi\src\cstgy.c

Gap found between selection criteria lines

E11006 v_dialer\library\libcallsel\src\CallStgyLib.cppv_dialer\library\libdsi\src\cstgy.c

Extra ',' found

E11007 v_dialer\library\libcallsel\src\CallStgyLib.cppv_dialer\library\libdsi\src\cstgy.c

Invalid phone: %s

E11008 v_dialer\library\libcallsel\src\CallStgyLib.cppv_dialer\library\libdsi\src\cstgy.c

Invalid field name: %s

E11009 v_dialer\library\libcallsel\src\CallStgyLib.cppv_dialer\library\libdsi\src\cstgy.c

Invalid field value: %s

E11010 v_dialer\library\libcallsel\src\CallStgyLib.cppv_dialer\library\libdsi\src\cstgy.c

Invalid logical connector: %s

Page 292: PC4 Troubleshooting Main

290 Maintenance and Troubleshooting Guide March 2008

E11011 v_dialer\library\libcallsel\src\CallStgyLib.cpp

Invalid time zone letter: %c

E11012 Invalid completion code: %s

E11013 v_dialer\library\libcallsel\src\CallStgyLib.cppv_dialer\library\libdsi\src\cstgy.c

Invalid ring count: %s. Must be 1 - %d

E11014 v_dialer\library\libcallsel\src\CallStgyLib.cppv_dialer\library\libdsi\src\cstgy.c

Invalid call detection mode: %s

E11015 v_dialer\library\libcallsel\src\CallStgyLib.cppv_dialer\library\libdsi\src\cstgy.c

Error: Recall attempt #%d (%s) can't be less than %d minutes

E12000 v_dialer\library\libdsi\src\getnum.c File %s busy, try again later

E12100 Molocale - Unknown language name %s

E12101 v_dialer\library\libutil\src\molocale.c Molocale - Failed to set locale %s errno=%d

E12150 v_dialer\library\libdsi\src\pvrs_helper.c PVRS - Failed to initialize %s

E12151 Hash key field is not defined in %s

E12152 v_dialer\library\libdsi\src\pvrs_helper.cv_dialer\dialer\src\dbmaint\record_ed.c

No Previous Record

E12153 v_dialer\library\libdsi\src\pvrs_helper.cv_dialer\dialer\src\dbmaint\record_ed.c

No More Record

E12154 v_dialer\dialer\src\core\oper_pvrs.cv_dialer\dialer\src\dbmaint\record_ed.c

Failed to Load Record

E12155 v_dialer\dialer\src\core\oper_pvrs.c Record Currently In Use

E12156 v_dialer\library\libdsi\src\pvrs_helper.c No Record Found

E12200 Attempt to read hidfile without lock

E12201 Username %s exceeds %d characters in length

E12202 %s - Failed to lock file %s, errno(%d)

E12203 %s - Failed to unlock file %s, errno(%d)

Page 293: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 291

E12345 v_dialer\dialer\DialerCmdCtrl\DccGlobalFunc.cpp

E12400 v_dialer\library\libdsi\src\keystroke.cv_dialer\library\libutil\src\tsystem.c

tget returned errno %d raising signal %d

E12600 v_dialer\library\libdsi\src\map_dict.cv_dialer\library\libcallsel\src\map_dict2.cpp

Calling list %s not in shared memory

E12601 v_dialer\library\libdsi\src\map_dict.cv_dialer\library\libcallsel\src\map_dict2.cpp

Calling list field count not match

E12800 v_dialer\library\libdsi\src\map_scrn.c Failed to find screen %s

E13000 v_dialer\library\libdsi\src\mqueue.c IPC - Invalid input argument

E13001 v_dialer\library\libdsi\src\mqueue.c IPC - Invalid ipc entry

E13002 IPC - Invalid ipc name

E13003 v_dialer\library\libdsi\src\mqueue.c IPC - Invalid ipc number %d

E13004 v_dialer\library\libdsi\src\mqueue.c Warning: CFRM message truncated

E13005 v_dialer\library\libdsi\src\mqueue.c Timed out waiting for %s confirmation

E13006 v_dialer\library\libdsi\src\mqueue.c Response message too long!

E13007 v_dialer\library\libdsi\src\mqueue.c IPC - Failed to open opmon message queue

E13008 v_dialer\library\libdsi\src\mqueue.c %s - Failed on semaphore removal, err=%d key=%d

E13009 v_dialer\library\libdsi\src\mqueue.c %s - Failed on semaphore operation, err(%d) key = %d code = %d

E13010 v_dialer\library\libdsi\src\mqueue.c %s - Accessing bad semaphore

E13011 v_dialer\library\libdsi\src\mqueue.c %s - Failed to open semaphore, err(%d)

E13200 v_dialer\library\libdsi\src\opident.c Headset value (%s, %d) out of bound

E13201 v_dialer\library\libdsi\src\opident.c Headset %d not specified in %s file

E13400 Missing or invalid YES/NO field

Page 294: PC4 Troubleshooting Main

292 Maintenance and Troubleshooting Guide March 2008

E13401 Missing or invalid length

E13402 v_dialer\library\libdsi\src\phonefmt.c Missing prefix

E13403 v_dialer\library\libdsi\src\phonefmt.c Missing line type

E13404 v_dialer\library\libdsi\src\phonefmt.c Missing or invalid num of chars to strip

E13405 Missing prefix

E13406 v_dialer\library\libdsi\src\phonefmt.c Missing suffix

E13407 v_dialer\library\libdsi\src\phonefmt.cv_dialer\library\libdsi\src\vlloccall.c

Duplicate ALL phone numbers specification

E13408 v_dialer\library\libdsi\src\phonefmt.c Phone number too long

E13409 v_dialer\library\libdsi\src\phonefmt.c Dial phone number too long

E13410 v_dialer\library\libdsi\src\phonefmt.c Missing std to dial phone number format

E13411 v_dialer\library\libdsi\src\phonefmt.c Invalid use of ALL phone numbers specification

E13412 v_dialer\library\libdsi\src\phonefmt.c Missing phone numbers

E13600 v_dialer\library\libdsi\src\rpt_server.c Report failed, system out of space

E13800 v_dialer\library\libdsi\src\swcfg_tbl.c Invalid Headset Number (%d, %s)

E13801 v_dialer\library\libdsi\src\swcfg_tbl.c Headset port no. %d out of range (1-%d)

E13802 v_dialer\library\libdsi\src\swcfg_tbl.c Normal trunk port no. %d out of range (1-%d)

E13803 v_dialer\library\libdsi\src\swcfg_tbl.c Invalid normal trunk equip no %d

E13804 Invalid normal trunk group no %d

E13805 v_dialer\library\libdsi\src\swcfg_tbl.c Invalid transfer trunk group no %d

E13806 Failed to determine switch type

E13807 v_dialer\library\libdsi\src\swcfg_tbl.c Failed to process line (%s)

E14100 Invalid timezone from GMT

Page 295: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 293

E14101 Invalid time format at line %d in file %s

E14200 v_dialer\library\libdsi\src\vlloccall.c Missing delay specification

E14201 v_dialer\library\libdsi\src\phonefmt.cv_dialer\library\libdsi\src\vlloccall.c

Missing or invalid low range

E14202 v_dialer\library\libdsi\src\phonefmt.cv_dialer\library\libdsi\src\vlloccall.c

Invalid range character

E14203 v_dialer\library\libdsi\src\phonefmt.cv_dialer\library\libdsi\src\vlloccall.c

Invalid high range

E14204 v_dialer\library\libdsi\src\vlloccall.c Invalid min delay

E14205 v_dialer\library\libdsi\src\vlloccall.c Missing completion code

E14206 v_dialer\library\libdsi\src\vlloccall.c Invalid completion code

E14207 v_dialer\library\libdsi\src\vlloccall.c Range does not come after previous range

E14208 v_dialer\library\libdsi\src\vlloccall.c Missing limit

E14209 v_dialer\library\libdsi\src\phonefmt.cv_dialer\library\libdsi\src\vlloccall.c

Missing or invalid YES/NO field

E14210 v_dialer\library\libdsi\src\vlloccall.c Missing time zone specification for country %d

E14211 v_dialer\library\libdsi\src\vlloccall.c Missing or invalid time zone designation

E14212 v_dialer\library\libdsi\src\vlloccall.c Missing reject phone number pattern

E14213 v_dialer\library\libdsi\src\vlloccall.c Invalid reject phone number pattern

E14214 v_dialer\library\libdsi\src\vllocmisc.cv_dialer\library\libdsi\src\vllocport.c

Duplicate country specified

E14215 v_dialer\library\libdsi\src\vllocmisc.cv_dialer\library\libdsi\src\vllocport.c

Invalid answer delay time

E14216 v_dialer\library\libdsi\src\vllocport.c Invalid DAA type

E14217 v_dialer\library\libdsi\src\vllocport.c Invalid VM2 locale code

E14218 v_dialer\library\libdsi\src\vllocport.c Invalid phone number length

E14219 v_dialer\library\libdsi\src\vllocport.c Rejected phone number (L%d)

Page 296: PC4 Troubleshooting Main

294 Maintenance and Troubleshooting Guide March 2008

E14220 v_dialer\library\libdsi\src\vllocport.c Cannot find time zone for phone number

E14221 v_dialer\library\libdsi\src\vllocport.c Invalid offhook retry delay

E14222 v_dialer\library\libdsi\src\vllocport.c Invalid wait limit

E14400 Unknown select file %s

E14401 v_dialer\dialer\src\preprocess\ij_merge.cv_dialer\library\libcallsel\src\CallSelLib.cppv_dialer\library\libdsi\src\cselect.c

Unknown call completion code %s

E14402 v_dialer\library\libcallsel\src\CallSelLib.cppv_dialer\library\libdsi\src\cselect.c

No call completion codes selected

E14404 v_dialer\library\libcallsel\src\CallSelLib.cppv_dialer\library\libdsi\src\cselect.c

Missing field name or value at selection entry %d

E14405 v_dialer\library\libcallsel\src\CallSelLib.cppv_dialer\library\libdsi\src\cselect.c

Group may not begin with no selection

E14406 v_dialer\library\libcallsel\src\CallSelLib.cppv_dialer\library\libdsi\src\cselect.c

Gap found between select fields within group

E14407 v_dialer\library\libcallsel\src\CallSelLib.cppv_dialer\library\libdsi\src\cselect.c

Field name not found at selection entry %d

E14408 v_dialer\library\libcallsel\src\CallSelLib.cppv_dialer\library\libdsi\src\cselect.c

Pattern error at selection entry %d: %s

E14409 v_dialer\library\libdsi\src\conn_queue.c Unit Control - Invalid memory slot position

E14410 v_dialer\library\libdsi\src\conn_queue.c Unit Control - Failed to attach to data segment

E14800 v_dialer\library\libutil\src\tcap.c Termcap entry larger than buffer size

E14801 v_dialer\library\libutil\src\tcap.c Invalid termcap entry format

E14802 v_dialer\library\libutil\src\tcap.c 'tc' entries exceed maximum allowed

Page 297: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 295

E14900 v_dialer\library\libutil\src\terminal.c Terminal type %s not found in %s

E14901 v_dialer\library\libutil\src\terminal.c Default terminal type vt100 not found in %s

E15200 v_dialer\library\libui\src\vlui.c No summary information available

E15201 v_dialer\library\libui\src\vlui.c Invalid field type

E15202 v_dialer\library\libui\src\vlui.c Invalid value, Must be %s

E15203 v_dialer\library\libui\src\vlui.c Sorry, command not allowed inside editor

E15204 v_dialer\library\libui\src\vlui.c %s - Menubar '%s' already exists.

E15205 v_dialer\library\libui\src\vlui.c %s - Menubar '%s' not found.

E15400 v_dialer\library\libui\src\vlui.c %s:new_bsrch - Memory allocation (%d bytes) failed, loc %d

E15401 v_dialer\library\libdsi\src\bsrch.c %s:new_bsrch - Bad value in new_bsrch (cl_name=%s cl_fd=%d, cl_keyname=%s init_type=%c pgmname=%s log_type=%d log_file=%s)

E15402 v_dialer\library\libdsi\src\bsrch.c %s:new_bsrch - List recno %d locked-skipping;

E15403 v_dialer\library\libdsi\src\bsrch.c %s:new_bsrch - List recno %d locked-aborting;

E15404 v_dialer\library\libdsi\src\bsrch.c %s:new_bsrch - Bad calling list record parameter(s): keylen=%d reclen=%d nrecs=%d

E15420 v_dialer\library\libdsi\src\bsrch.c %s:new_hsrch - Memory allocation (%d bytes) failed, loc %d

E15421 v_dialer\library\libdsi\src\bsrch.c %s:new_hsrch - Unable to open hash file for %s

E15422 v_dialer\library\libdsi\src\bsrch.c %s:new_hsrch - Missing key_field entry in hash file %s

E15424 %s:new_hsrch - Bad calling list record parameter(s): keylen=%d reclen=%d

Page 298: PC4 Troubleshooting Main

296 Maintenance and Troubleshooting Guide March 2008

E16000 v_dialer\library\libutil\src\labfdctry.c Missing or invalid country code

E16100 v_dialer\library\libutil\src\labfile.c Line too long

E16101 v_dialer\library\libutil\src\labfile.c Missing label

E16102 v_dialer\library\libutil\src\labfile.c Invalid label on line

E16400 v_dialer\library\libutil\src\preftree.c Range not properly nested

E16401 v_dialer\library\libutil\src\preftree.c Prefix falls on a range's border

E16402 v_dialer\library\libutil\src\preftree.c Range border falls on a prefix

E16403 v_dialer\library\libutil\src\preftree.c Range straddles previous range

E16404 v_dialer\library\libutil\src\preftree.c Prefix has the same value as a shorter prefix

E16405 v_dialer\library\libutil\src\preftree.c Same prefix is already specified

E16406 v_dialer\library\libutil\src\preftree.c Prefix has the same value as a longer prefix

E16407 v_dialer\library\libutil\src\preftree.c Missing prefix

E16408 v_dialer\library\libutil\src\preftree.c Invalid character in prefix

E16409 v_dialer\library\libutil\src\preftree.c Low range has fewer digits than high

E16410 v_dialer\library\libutil\src\preftree.c Range borders are out of order

E16411 v_dialer\library\libutil\src\preftree.c Bad argument in ptree

E16500 v_dialer\library\libutil\src\hash.c Hash_get (%x, %s, %d) failed due to too many probes

E16501 v_dialer\library\libutil\src\hash.c Requested size %d is too large -- Max hash table slots currently supported is %d

E16600 v_dialer\library\libutil\src\expr.c Pattern '%s': Expected numerical lval, found '%s'

E16601 v_dialer\library\libutil\src\expr.c Pattern '%s': Expected numerical rval, found '%s'

E16602 v_dialer\library\libutil\src\expr.c Pattern '%s': lval > rval (%g > %g)

E16603 v_dialer\library\libutil\src\expr.c Pattern '%s': Expected hyphen, list separator, or end of pattern; found '%c'

Page 299: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 297

E16604 v_dialer\library\libutil\src\expr.c Pattern '%s': Unexpected end of numerical comparison

E16605 v_dialer\library\libutil\src\expr.c Pattern '%s': Pattern too large

E16606 v_dialer\library\libutil\src\expr.c Pattern '%s': Bad or missing DATEFORM parameter in master.cfg

E16607 v_dialer\library\libutil\src\expr.c Pattern '%s': Bad format for date comparison

E16608 v_dialer\library\libutil\src\expr.c Pattern '%s': Bad format for time comparison

E16609 v_dialer\library\libutil\src\expr.c Pattern '%s': Bad format for relative date comparison

E16610 v_dialer\library\libutil\src\expr.c Pattern '%s': Undefined backslashed character '%c'

E16611 v_dialer\dialer\DialerCmdCtrl\expr_utest.cpp

Pattern '%s': Unknown pattern type '%c' specified

E16612 v_dialer\library\libutil\src\expr.c Pattern '%s': Failed to compile - use explicit pattern syntax for more details

E16620 v_dialer\library\libutil\src\expr.c Unable to compare - previous pattern failed compilation - '%s'

E16621 v_dialer\library\libutil\src\expr.c No compiled pattern to compare against for string '%s'

E16800 v_dialer\library\libutil\src\undefined.c Undefined func call: %s

E16900 v_dialer\library\libutil\src\exec_prog.c EXECPROG:Unexpected exit from waitpid() returning -1:errno=%d:pid=%d,child=%d

E16901 v_dialer\library\libutil\src\exec_prog.c EXECPROG:not returning from child process:pid=%d,child=%d

E16902 v_dialer\library\libutil\src\exec_prog.c EXECPROG:Exit(%d) wait(pid=%d)

E16903 v_dialer\library\libutil\src\exec_prog.c EXECPROG:Signal STOPPED wait(%d)

E16904 v_dialer\library\libutil\src\exec_prog.c EXECPROG:Sig_Exit:errno=%d:stat=0x%X:sig=%d:pid=%d,child=%d

E16905 v_dialer\library\libutil\src\exec_prog.c EXECPROG:Unexpected exit:errno=%d:stat_loc=0x%X:ret=%d:pid=%d,child=%d

Page 300: PC4 Troubleshooting Main

298 Maintenance and Troubleshooting Guide March 2008

E16906 v_dialer\library\libutil\src\exec_prog.c EXECPROG:Killed Child(%d):%s:

E16907 v_dialer\library\libutil\src\exec_prog.c EXECPROG:errno=%d:stat_loc=0x%X:ret=%d:pid=%d,child=%d

E16908 v_dialer\library\libutil\src\exec_prog.c PID(%d)Relaying signal=%d to child_pid=%d

E16909 v_dialer\library\libutil\src\exec_prog.c PID(%d)Ignoring signal=%d

E16910 v_dialer\library\libutil\src\exec_prog.c PID(%d)Activating Default Signal Handler

E16911 v_dialer\library\libutil\src\exec_prog.c PID(%d)Returning to exec_prog() Routine

E16912 v_dialer\library\libutil\src\exec_prog.c PID(%d)Calling Primary Signal Handler

E17000 v_dialer\library\libutil\src\account.cv_dialer\library\libutil++\src\account_r.c

Error: system message '%s' not found

E17001 Error: unable to open account file '%s'

E17002 Error: unknown user '%s' specified.

E17003 v_dialer\dialer\DialerCmdCtrl\AgentLib.cpp

Error: unknown group '%s' specified.

E17004 Error: chown ('%s', %d, %d) failed.

E17005 v_dialer\library\libutil\src\config.c Error: malloc ('%s') failed.

E17100 getconfig: File '%s' is empty

E17101 getconfig: Couldn't open file '%s'

E18200 v_dialer\library\libswif\src\port_dg.c DISABLE INBOUND FAILED: (%d)%s

E18201 v_dialer\library\libswif\src\port_dg.c ENABLE INBOUND FAILED: (%d)%s, ns=%x, rsb=%x, cause_IE=%x

E18202 v_dialer\library\libswif\src\port_dg.c PORTER%d: switch out of sync

E18203 v_dialer\dialer\src\core\msg_loader.cv_dialer\library\libswif\src\port_dg.c

Download of voice prompt file [%s] failed

Page 301: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 299

E18204 v_dialer\library\libswif\src\port_dg.c CALL FAILED ON %d: %s

E18205 v_dialer\library\libswif\src\port_dg.c ORULE OVERRIDE DISABLE FAILED: %s

E18206 v_dialer\library\libswif\src\port_dg.c HANGUP FAILED FOR %d: %s, ns=%x, rsb=%x, cause_IE=%x

E18207 v_dialer\library\libswif\src\port_dg.c HANGUP FAILED: EQUIP= %d

E18208 v_dialer\library\libswif\src\port_dg.c TRNSFR Transfer trunks not configured

E18209 v_dialer\library\libswif\src\port_dg.c TRNSFR No transfer trunks available

E18210 dialer_library\libswif\src\port_dg.c TRNSFR Transfer dial failed

E18211 TRNSFR Transfer Failed

E18212 v_dialer\library\libswif\src\port_dg.c TRNSFR Failed to put line on hold

E18213 v_dialer\library\libswif\src\port_dg.c RESPONSE FAILED: (%d)%s, ns=%x, rsb=%x, cause_IE=%x

E18214 v_dialer\library\libswif\src\port_dg.c DOWNLOAD FAILED: file=%s, %s, ns=%x, rsb=%x, cause_IE=%x

E18215 v_dialer\library\libswif\src\port_dg.c TRANSFER DIAL FAILED: (%d)%s, ns=%x, rsb=%x, cause_IE=%x

E18216 TRANSFER CONFERENCE FAILED: (%d)%s, ns=%x

E18217 Porter %d failed to busy-out line

E18218 Porter %d abandoned inbound call

E18219 v_dialer\library\libswif\src\port_dg.c DELIVER FAILED: (%d)%s, ns=%x, rsb=%x, cause_IE=%x

E18220 v_dialer\library\libswif\src\port_dg.c POLL_MSG FAILED: (%d)%s, ns=%x, rsb=%x, cause_IE=%x

E18221 v_dialer\library\libswif\src\port_dg.c OFFHOOK FAILED FOR %d: %s, ns=%x, rsb=%x, cause_IE=%x

Page 302: PC4 Troubleshooting Main

300 Maintenance and Troubleshooting Guide March 2008

E18222 v_dialer\library\libswif\src\port_dg.c HOOKFLASH FAILED: (%d)%s, ns=%x, rsb=%x, cause_IE=%x

E18223 v_dialer\library\libswif\src\port_dg.c STUTTERED DIALTONE TEST FAILED: (%d)%s, ns=%x, rsb=%x, cause_IE=%x

E18224 v_dialer\library\libswif\src\port_dg.c DIAL FAILED: (%d)%s, ns=%x, rsb=%x, cause_IE=%x

E18225 v_dialer\library\libswif\src\port_dg.c TRANSFER OFFHOOK FAILED: (%d)%s, ns=%x, rsb=%x, cause_IE=%x

E18226 v_dialer\library\libswif\src\port_dg.c CAMPON FAILED equip_no=%d: %s, ns=%x, rsb=%x, cause_IE=%x, status=%d

E18227 v_dialer\library\libswif\src\port_dg.c POLL_EVENT FAILED: (%d)%s, ns=%x, rsb=%x, cause_IE=%x

E18228 v_dialer\library\libswif\src\port_dg.c TRNSFR Failed to find job specified holdmsg number in voicemsg.cfg

E18400 v_dialer\library\libswif\src\swid.c swid_process_report: bad ns = 0x%04x

E18401 v_dialer\library\libswif\src\swid.c swid_process_report: bad 0x%x reply

E18402 v_dialer\library\libswif\src\swid.c swid_process_report: bad <port> in 0x%x reply

E18403 v_dialer\library\libswif\src\swid.c swid_process_report: 0x%x reply <control_port> out of range.

E18404 v_dialer\library\libswif\src\swid.c swid_process_report: 0x69 reply on inactive virtual port (0x%04x).

E18405 v_dialer\library\libswif\src\swid.c swid_process_report: 0x69 reply <outgoing_port=0x%03x> out of range.

E18406 v_dialer\library\libswif\src\swid.c swid_report_72(reset): bad NSB.

E18407 v_dialer\library\libswif\src\swid.c swid_process_report: bad port = %d(0x%03x) in 0xDA reply

Page 303: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 301

E18408 v_dialer\library\libswif\src\swid.c swid_process_report: Ignored 0x%x report on port=%d(0x%03x),supcode=0x%04x

E18409 v_dialer\library\libswif\src\swid.c swid_process_report: unknown/unexpected change

E18410 v_dialer\library\libswif\src\swid.c (%d)/event %s(%d) on port (0x%03x).

E18411 v_dialer\library\libswif\src\swid.c swid_process_report: bad port %d(0x%03x) in 0xDB reply

E18412 v_dialer\library\libswif\src\swid.c change=%x

E18413 v_dialer\library\libswif\src\swid.c swid_process_report: <port> (0x%03x) in 0xDD reply not enabled for inbound

E18414 v_dialer\library\libswif\src\swid.c swid_process_report: 0x49 reply on inactive virtual port (0x%04x).

E18415 v_dialer\library\libswif\src\swid.c swid_process_report: 0x49 reply <outgoing_port=0x%03x> out of range.

E18416 v_dialer\library\libswif\src\swid.c swid_process_report: bad port = %d(0x%03x) in 0xEA reply

E19000 v_dialer\library\libswif\src\swie.c '%s' not in /etc/hosts!

E19001 v_dialer\library\libswif\src\swie.c swif: '%s' cannot create socket!

E19002 v_dialer\library\libswif\src\swie.c swif: cannot connect to ethernet switch port '%s:%d',(%d)

E19003 v_dialer\library\libswif\src\swie.c swif: cannot set socket option SO_KEEPALIVE, err(%d)

E19004 v_dialer\library\libswif\src\swie.c Failed to read packet header (%d,%d)

E19005 v_dialer\library\libswif\src\swie.c Failed to read packet body (%d,%d)

E19006 v_dialer\library\libswif\src\swie.c ethernet receive buffer too small

E19007 v_dialer\library\libswif\src\swie.c swif: listener cannot swic_init_client()

E19200 v_dialer\library\libswif\src\swiq.c Unable to save switch log history

Page 304: PC4 Troubleshooting Main

302 Maintenance and Troubleshooting Guide March 2008

E19201 v_dialer\library\libswif\src\swiq.c Log event from %s line %d is being throttled.

E19400 v_dialer\library\libswif\src\switch_dg.c Unable to initialize switch channel, swif return=[%d]

E19401 v_dialer\library\libswif\src\switch_dg.c Failed to reset switch channel

E19402 v_dialer\library\libswif\src\switch_dg.c %s TONE DOWNLOAD FAILED, %s, ns=%x, rsb=%x, cause_IE=%x

E19403 v_dialer\library\libswif\src\switch_dg.c GREETING PROMPT DOWNLOAD FAILED, %s, ns=%x, rsb=%x, cause_IE=%x

E19404 v_dialer\library\libswif\src\switch_dg.c Failed to reset switch, swif return=[%d],ns=%x, rsb=%x, cause_IE=%x

E19405 v_dialer\library\libswif\src\switch_dg.c ZIP TONE FAILED, %s, ns=%x, rsb=%x, cause_IE=%x, equip=%d

E19406 v_dialer\library\libswif\src\switch_dg.cv_dialer\library\libswif\src\port_sd.c

CONNECT RESPONSE: %s, ns=%x, rsb=%x, cause_IE=%x, equip1:%d, equip2:%d

E19407 v_dialer\library\libswif\src\switch_dg.c DISCONNECT RESPONSE: %s, ns=%x, rsb=%x, cause_IE=%x, equip:%d,

E19408 v_dialer\library\libswif\src\switch_dg.c Invalid prompt index:%d

E19600 v_dialer\library\libswif\src\swix.c unexpected EOF/incomplete comment

E19601 v_dialer\library\libswif\src\swix.c non-ASCII character.

E19602 dialer_library\libswif\src\swix.c Error reading exercise script '%%s':

E19603 v_dialer\library\libswif\src\swix.c line %%d:

E19604 v_dialer\library\libswif\src\swix.c event table full

E19605 v_dialer\library\libswif\src\swix.c not a SWIF function name

E19606 v_dialer\library\libswif\src\swix.c expecting a time value, digits only, enclosed in ()

E19607 v_dialer\library\libswif\src\swix.c expecting closing paren

E19608 v_dialer\library\libswif\src\swix.c expecting SWIF event name

Page 305: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 303

E19609 v_dialer\library\libswif\src\swix.c too many exercise script errors -- aborting!

E25000 v_dialer\dialer\src\callsel\call_scrn.c Recall field name or value missing

E25001 v_dialer\dialer\src\callsel\call_scrn.c Recall field name not found

E25002 v_dialer\dialer\src\callsel\call_scrn.c Recall pattern error: %s

E25003 v_dialer\dialer\src\callsel\callsel.cv_dialer\dialer\src\core\agent_misc_util.c

%s - Failed to locate strategy files

E25004 v_dialer\dialer\src\callsel\call_scrn.c Unknown time zone designator %c

E25005 v_dialer\dialer\src\callsel\call_scrn.c No time zones selected

E25007 Missing field name or value at recall entry %d

E25008 v_dialer\dialer\src\callsel\call_scrn.c Group may not begin with no selection

E25009 Gap found between select fields within group

E25010 v_dialer\dialer\src\callsel\call_scrn.c Field name not found at recall entry %d

E25011 v_dialer\dialer\src\callsel\call_scrn.c Pattern error at recall entry %d: %s

E25012 v_dialer\dialer\src\callsel\call_scrn.c Sort direction is invalid

E25013 Sort field name not found

E25014 v_dialer\dialer\src\callsel\call_scrn.c Unit work list Key field name missing

E25015 v_dialer\dialer\src\callsel\call_scrn.c Unit work list Key field name not found

E25016 v_dialer\dialer\src\callsel\call_scrn.c Strategy file name missing

E25017 v_dialer\dialer\src\callsel\call_scrn.c Strategy file name not found

E25018 v_dialer\dialer\src\callsel\call_scrn.c Unable to read strategy file

E25019 v_dialer\dialer\src\callsel\call_scrn.c %s - Unable to initialize strategy table

E25020 v_dialer\dialer\src\callsel\callsel.c %s - Time zoning of phone numbers not done on calling list

Page 306: PC4 Troubleshooting Main

304 Maintenance and Troubleshooting Guide March 2008

E25021 v_dialer\dialer\src\callsel\callsel.c %s - Master calling list error

E25022 v_dialer\dialer\src\callsel\callsel.c %s - Unable to get callsel number

E25023 v_dialer\dialer\src\callsel\callsel.c %s - List selection aborted

E25024 v_dialer\dialer\src\callsel\call_scrn.c %s - Calling List %s is not Time Zoned

E25025 v_dialer\dialer\src\callsel\call_scrn.c %s - %s field not defined or incorrect length

E25026 v_dialer\dialer\src\callsel\callsel.c Callsel verification failed. Please use change option

E25027 Improper Usage

E25028 v_dialer\dialer\src\callsel\callsel.c Special time zone + is not available

E25029 v_dialer\dialer\src\callsel\call_scrn.c Report field name not found

E25030 You must specify at least one field

E25031 v_dialer\library\libcallsel\src\cllcallsel.cpp

Timeout: failed to identify status of the Index Processing within %d seconds

E25032 v_dialer\library\libcallsel\src\cllcallsel.cpp

Failed to start asynchronous Index Processing sub-process

E25501 v_dialer\dialer\src\callsel\callconn.c Callsel terminated by signal = %d

E25502 v_dialer\dialer\src\callsel\callconn.c Callsel exited with status of %o (octal)

E25503 v_dialer\dialer\src\callsel\callconn.c Couldn't open file %s

E25504 v_dialer\dialer\src\core\ao_recall.cv_dialer\dialer\src\callsel\callconn.c

Failed to read file %s

E25505 v_dialer\dialer\src\callsel\callconn.c callconn:fail to send zALTQUE msg

E27000 midtier\unixdev\ServiceMonitor\src\ServiceMonitor_ServiceController.cxxmidtier\unixdev\SysHealth\src\SystemHealthImpl.cppv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitorIFImpl.cxx

Invalid input parameter(s)

Page 307: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 305

E27100 midtier\unixdev\ServiceMonitor\src\ServiceMonitor_ServiceController.cxxmidtier\unixdev\ServiceMonitor\src\ServiceMonitor_ServiceMonitorIFImpl.cxxmidtier\unixdev\SysHealth\src\SystemHealthImpl.cppv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitorIFImpl.cxx

Failed to process the method

E27200 Failed to open the file

E27300 midtier\unixdev\ServiceActivation\src\SARequest.cxxmidtier\unixdev\ServiceActivation\src\ServiceActivationIFImpl.cxxmidtier\unixdev\ServiceMonitor\src\ServiceMonitor_ServiceMonitorIFImpl.cxxv_dialer\dialer\DialerServiceActivation\src\DSARequest.cxx

Failed to activate the service

E28000 v_dialer\dialer\src\core\switcher.c Failed to initialize switcher

E28100 v_dialer\dialer\src\core\driver.c Unable to attach to data segment

E28101 v_dialer\dialer\src\core\driver.c invalid channel number %s

E28102 couldn't open switch channel

E28103 v_dialer\dialer\src\core\driver.c *** no active channel !!

E28104 v_dialer\dialer\src\core\driver.c 'memory' is not implemented

E28105 cannot attach to ipc queue, retval=%d, errno=%d

E28106 v_dialer\dialer\src\core\driver.c equipment number type not found

E28107 v_dialer\dialer\src\core\driver.c no seize on ISDN ports

E28108 v_dialer\dialer\src\core\driver.c no drop on ISDN ports

E28109 v_dialer\dialer\src\core\driver.c UNRECOGNIZED COMMAND! %s

E28200 v_dialer\dialer\src\core\conn_mgr.c %s - Job %s %s already exists

E28201 v_dialer\dialer\src\core\conn_mgr.c %s - Job %s %s does not exist

E28202 v_dialer\dialer\src\core\conn_mgr.c %s - Exceeded shared segment limit

Page 308: PC4 Troubleshooting Main

306 Maintenance and Troubleshooting Guide March 2008

E28203 v_dialer\dialer\src\core\conn_mgr.c %s - No phone calls in wait but wait count disagrees

E28204 v_dialer\dialer\src\core\conn_mgr.c %s (test_inbound_service) - Conn_op_line failed

E28205 v_dialer\dialer\src\core\conn_mgr.c %s - Invalid slot number(%d) passed

E28206 v_dialer\dialer\src\core\conn_mgr.c %s - Invalid agent number %d

E28207 v_dialer\dialer\src\core\conn_mgr.c %s - Invalid call trans type %c

E28208 v_dialer\dialer\src\core\conn_mgr.c No oper_name ('%s') or oper_jobnum (%d), cannot archive

E28209 v_dialer\dialer\src\core\conn_mgr.c No oper_name ('%s') or oper_jobnum (%d), cannot restore

E28210 v_dialer\dialer\src\core\conn_mgr.c No oper_name ('%s'), cannot restore

E28211 v_dialer\dialer\src\core\conn_mgr.c No jobname ('%s') or jobnum (%d), cannot archive

E28300 Unable to create a list of extensions

E28301 v_dialer\dialer\src\core\conn_mgr.c add_agent: Unable to insert agent

E28302 v_dialer\dialer\src\core\conn_mgr.c add_agent: entered a duplicate value

E28303 v_dialer\dialer\src\core\conn_mgr.c add_agent: Error getting current pointer

E28304 v_dialer\dialer\src\core\conn_mgr.c agent_recall: Unable to insert recall

E28305 v_dialer\dialer\src\core\conn_mgr.c recall_rmp - Exit since AGENTOWNRECALL is off

E28306 v_dialer\dialer\src\core\conn_mgr.c recall_rmp - Unable to create a list of agent

E28307 v_dialer\dialer\src\core\conn_mgr.c recall_rmp - Unable to create a list of recall

E28308 v_dialer\dialer\src\core\conn_mgr.c recall_rmp - unknown message received '%s'

E28309 v_dialer\dialer\src\core\conn_mgr.c Failed to setup ipc for agent %s

Page 309: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 307

E28310 v_dialer\dialer\src\core\listops.cv_dialer\dialer\src\core\recall_rmp.c

recall_rmp - agent %s not available

E28400 v_dialer\dialer\src\core\caller.cv_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Sales verification or managed dialing must have agents

E28401 v_dialer\dialer\src\core\caller.cv_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Managed dialing is not permitted with sales verification or inbound

E28402 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Virtual agents cannot select a specific unit to log in to

E28404 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\src\core\listops.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Sales verification is not permitted with unit work lists

E28405 v_dialer\dialer\src\core\caller.cv_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Sales verification is not permitted with inbound

E28406 v_dialer\dialer\src\core\listops.c Inbound with unshared account ownership is not permitted

E28407 v_dialer\dialer\src\core\listops.c Alternate selection %s is not permitted with unit work lists

E28408 v_dialer\dialer\src\core\caller.cv_dialer\dialer\src\core\nuisance.c

%s - Failed to get job number

E28409 v_dialer\dialer\src\core\caller.c Job startup failed in job configuration

E28410 v_dialer\dialer\src\core\caller.c Job setup incomplete, Aborting %s

E28411 v_dialer\dialer\src\core\caller.c %s - Unknown message: %s, %s, %s

E28412 v_dialer\dialer\src\core\caller.c %s - Not an inbound capable system

E28413 %s - Failed to setup hunt group

E28414 %s - Invalid hunt group

Page 310: PC4 Troubleshooting Main

308 Maintenance and Troubleshooting Guide March 2008

E28415 v_dialer\dialer\src\core\caller.c %s - Failed to receive a job info position

E28416 v_dialer\dialer\src\core\caller.c %s - FATAL_ERROR: %s

E28417 v_dialer\dialer\src\core\listops.c %s - Record length greater than %d

E28418 v_dialer\dialer\src\core\listops.c %s - Failed on verifying assoc. list

E28419 v_dialer\dialer\src\core\listops.c %s - Failed on reading assoc. list

E28420 v_dialer\dialer\src\core\listops.c %s - Master calling list error

E28421 v_dialer\dialer\src\core\listops.c %s - Invalid strategy: %s

E28422 v_dialer\dialer\src\core\listops.c %s - Failed to table strategy file: %s

E28423 v_dialer\dialer\src\core\listops.c %s - Index file not created with calling list %s

E28424 v_dialer\dialer\src\core\listops.c %s - Exceeded record slots available,PORTCOEF may be low

E28425 v_dialer\dialer\src\core\listops.c %s(%s) - Record number returned invalid %d

E28426 v_dialer\dialer\src\core\listops.c %s(%s) - Record number returned wrong %d, job number %d

E28427 v_dialer\dialer\src\core\listops.c Failed to attach to semaphore

E28428 v_dialer\dialer\src\core\listops.cv_dialer\dialer\DialerCmdCtrl\ErrorHandling_utest.cpp

Failed to read selection criteria file:%s

E28429 v_dialer\dialer\src\core\caller.c %s - Call cancel is not permitted

E28430 v_dialer\dialer\src\core\caller.c Job linking is not permitted

E28431 v_dialer\dialer\src\core\job_strter.c ERROR: EDTFILE not specified in job file %s

E28432 v_dialer\dialer\src\core\job_strter.c ERROR: Failed to fork job %s (error=%d)

E28433 v_dialer\dialer\src\core\job_strter.c ERROR: Failed to exec job %s

Page 311: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 309

E28434 v_dialer\dialer\src\core\caller.cv_dialer\dialer\src\core\job_strter.c

ERROR: Failed to invoke wait for job %s (error=%d)

E28435 v_dialer\dialer\src\core\job_strter.c Next job %s started

E28436 v_dialer\dialer\src\core\job_strter.c Next job %s error: %s

E28437 v_dialer\dialer\src\core\job_strter.c Next job %s terminated by signal %d

E28438 v_dialer\dialer\src\core\job_strter.c Next job %s stopped by signal %d

E28439 v_dialer\dialer\src\core\caller.c ERROR: Next job %s already starting up.

E28440 v_dialer\dialer\src\core\ao_recall.cv_dialer\dialer\src\core\caller.c

Caller(launch_posttrans) - Failed to invoke function fork, err=%d

E28441 v_dialer\dialer\src\core\caller.c Caller(launch_posttrans) - Failed to invoke function rtprio, err=%d

E28442 v_dialer\dialer\src\core\caller.c Caller(launch_posttrans) - Failed to invoke function pipe, err=%d

E28443 v_dialer\dialer\src\core\listops.c %s - Failed to create calling script %s

E28444 Caller - Failed to get port matching label %s N%s

E28445 v_dialer\dialer\src\core\caller.cv_dialer\dialer\src\core\joblib.c

%s - Failed to terminate proc %d for Agent %s

E28446 caller:fail to send %s to %s

E28447 v_dialer\dialer\src\core\caller.c caller:fail to get shadowjobname

E28448 v_dialer\dialer\src\core\caller.c Job(%s) '%s' sent to a non shadow job

E28449 v_dialer\dialer\src\core\caller.c Caller - PostTrans:Failed to exec prog '%s'

E28450 v_dialer\dialer\src\core\listops.c Caller - %s (R%d) (N%s)

E28451 v_dialer\dialer\src\core\listops.c Job(%s):%s: no available line

E28452 v_dialer\dialer\src\core\listops.c Job(%s):%s: no available record slot

Page 312: PC4 Troubleshooting Main

310 Maintenance and Troubleshooting Guide March 2008

E28453 v_dialer\dialer\src\core\listops.c Job(%s):%s:No recall found in queue

E28454 v_dialer\dialer\src\core\listops.c Job(%s):%s:Invalid phone for this recall, rec_slot=%d

E28455 v_dialer\dialer\src\core\listops.c Job(%s):%s:Same record (%d)is opened

E28456 v_dialer\dialer\src\core\listops.c Job(%s):%s:Record %d is locked

E28457 v_dialer\dialer\src\core\listops.c Job(%s):%s:Failed to read record %d

E28458 v_dialer\dialer\src\core\listops.c Job(%s)::Failed to get phone number:%s

E28459 v_dialer\dialer\src\core\listops.c Job(%s)!get_ft_sort_key!clread error rec_num=%d

E28460 v_dialer\dialer\src\core\listops.c Job(%s):PostTrans:Failed to write pipe, recnum = %d, errno = %d

E28461 v_dialer\dialer\src\core\listops.c Listops(pvrs_record_load) - Record number transferred is bad (%d)

E28462 v_dialer\dialer\src\core\listops.c Preview Empty Record with Multi Units is not allowed.

E28463 v_dialer\dialer\src\core\port_hndle.c Caller - RTSTATS is YES but failed to get operstats_base and/or job_stats_base

E28464 v_dialer\dialer\src\core\caller.cv_dialer\dialer\src\editor\config_ed.c

Invalid name (%s) for IVR pool job

E28465 Data process label '%s' for job '%s' missing/invalid

E28600 v_dialer\dialer\src\core\porter.c %s - Invalid port number assigned

E28601 v_dialer\dialer\src\core\porter.c Porter %d - Line inoperable

E28602 v_dialer\dialer\src\core\ao_recall.cv_dialer\dialer\src\utility\list_status.cv_dialer\dialer\enforcer\src\enforcer.cppv_dialer\dialer\src\core\porter.cv_dialer\dialer\src\core\recall_rmp.c

%s - Failed to setup input IPC.

Page 313: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 311

E28603 v_dialer\dialer\src\core\agent_misc_util.cv_dialer\dialer\src\core\operator.cv_dialer\dialer\src\core\port_hndle.cv_dialer\dialer\src\core\portevent.cv_dialer\dialer\src\core\porter.c

%s - Failed to setup conn_mgr IPC.

E28604 Failed on inbound list def. %s

E28605 Failed on outbound list def. %s

E28606 v_dialer\dialer\src\core\scripter.c No extension number for the IVR to dial

E28607 v_dialer\dialer\src\core\scripter.c No ring command for IVR to run an application

E28608 v_dialer\dialer\src\core\scripter.c HOOKIVR: No dial tone from PBX

E28609 v_dialer\dialer\src\core\scripter.c %s - Preview failed to find agent %s

E28610 %s - Mdial failed to find agent %s

E28611 v_dialer\dialer\src\core\scripter.c Not allowed in wait

E28612 v_dialer\dialer\src\core\scripter.c Request out of sequence

E28613 v_dialer\dialer\src\core\scripter.c Missing preview

E28614 v_dialer\dialer\src\core\scripter.c Second transaction

E28615 No text in script

E28616 v_dialer\library\libdsi\src\script_lng.c Script missing label %s

E28617 v_dialer\dialer\src\core\listops.c Op keys missing label %s

E28618 v_dialer\dialer\src\core\listops.c Job - Data script %s label missing

E28619 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\src\core\listops.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Job - Inbound script label %s missing/invalid

E28620 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\src\core\listops.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Job - Outbound script label for call %s missing/invalid

Page 314: PC4 Troubleshooting Main

312 Maintenance and Troubleshooting Guide March 2008

E28621 Failed to set DAA type:

E28622 Failed to set country code:

E28623 Porter %d failed to busy-out line

E28624 Porter %d abandoned inbound call

E28625 Failed to set DAA type: %d, Porter%d, %d

E28626 v_dialer\dialer\src\core\porter.c Porter %d: Line Fail:

E28627 v_dialer\dialer\src\core\porter.c %s - Invalid line class %c

E28628 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\operator.cv_dialer\dialer\src\core\scripter.c

Transfer failed, try again later

E28629 v_dialer\dialer\src\core\scripter.c No agent available, try again later

E28630 v_dialer\dialer\src\core\scripter.c NO DIAL TONE

E28631 v_dialer\dialer\src\core\scripter.c M %d > MAX

E28632 v_dialer\dialer\src\core\scripter.c M %d < MIN

E28633 v_dialer\dialer\src\core\scripter.c Porter - bld_dspmesg:message too long for internal buffer

E28634 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Job - Transfer Wait Queue script label %s missing/invalid

E28800 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Recall can't be less than %d minutes

E28801 v_dialer\dialer\src\core\screen.c Record is busy

E28802 v_dialer\dialer\src\core\screen.c Recall not allowed for inbound call

E28803 Transfer setup failed

E28804 v_dialer\dialer\src\core\agent.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Job %s not running

Page 315: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 313

E28805 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\operator.c

Job %s not ready - Log on later

E28806 %s - Failed to find job name %s in data seg

E28807 Agent number (%d) invalid

E28808 Headset (%s) not specified in %s file

E28809 %s not specified in switch.cfg file

E28810 Duplicate headset ID (%d) already in use by agent %s

E28811 Duplicate headset ID (%d) already in use

E28812 v_dialer\dialer\src\core\agent_misc_util.cv_dialer\dialer\src\core\operator.c

Agent %s logged in Already - Access Denied

E28813 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\operator.c

Maximum %s agent limit reached

E28814 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\operator.c

Managed agents are not permitted on this job

E28815 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\operator.c

Sales verification with unit work lists is not permitted

E28816 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\operator.c

Inbound agents only permitted

E28817 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\operator.c

Outbound agents only permitted

E28818 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\operator.c

Outbound or Managed agents only permitted

E28819 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\operator.c

Only outbound agents permitted by sales verification

E28820 v_dialer\dialer\src\core\operator.c Unit value not found, or unavailable

E28821 v_dialer\dialer\src\core\screen.c Cannot be DONE from alternate screen

Page 316: PC4 Troubleshooting Main

314 Maintenance and Troubleshooting Guide March 2008

E28822 v_dialer\dialer\src\core\screen.c Line not released

E28823 Failed to save record

E28824 v_dialer\dialer\src\core\screen.c Changes to record not saved

E28825 v_dialer\dialer\src\core\screen.c Record not found

E28826 v_dialer\dialer\src\core\screen.c Record is no longer available

E28827 v_dialer\dialer\src\core\screen.c Failed to unlock record

E28828 v_dialer\dialer\src\core\screen.cv_dialer\dialer\src\utility\shmon.c

Unknown screen type

E28829 v_dialer\dialer\src\core\screen.c Field entry is required

E28830 v_dialer\dialer\src\core\screen.c Field value not in acceptable list

E28831 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Field has non-numeric value

E28832 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

%s doesn't match %s format

E28833 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Invalid month in date

E28834 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Invalid year in date

E28835 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Invalid day in date

E28836 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Invalid format character found

E28837 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Invalid hour in time

E28838 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Invalid minute in time

E28839 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Invalid second in time

E28840 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Time is not in correct format

E28841 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Invalid phone

Page 317: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 315

E28842 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Invalid phonestat - %c

E28843 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Invalid phone number - %s

E28844 v_dialer\dialer\src\core\screen.c No REL_DIST setting

E28845 v_dialer\dialer\src\core\screen.c No REL_TME setting

E28846 v_dialer\dialer\src\core\screen.c No DONE_TME setting

E28847 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Date is before the current date

E28848 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Recall time and date outside timezone

E28849 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

%s - Record's timezone is unknown

E28850 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\screen.c

ERROR: Cannot open channel to operator monitor process

E28851 v_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\screen.c

ERROR: Operator monitor process does not respond

E28852 ERROR: HEADSET IS NOT ACTIVE

E28853 Error sending digits to switch

E28854 DIALDIGIT Customer Hangup(%d)

E28855 DIALDIGIT Dial Error=%d

E28856 v_dialer\dialer\src\core\screen.c ERROR: Invalid response from operator monitor process

E28857 Feature only available for DIGITAL switch

E28858 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\core\operator.c

%s - Exceeded operator slots available,MAXOPS is low

E28859 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\joblib.cv_dialer\dialer\src\core\operator.c

%s(%s) - Operator number returned invalid %d

Page 318: PC4 Troubleshooting Main

316 Maintenance and Troubleshooting Guide March 2008

E28860 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\operator.c

%s(%s) - Operator number returned wrong %d, job number %d

E28861 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\joblib.cv_dialer\dialer\src\core\operator.c

Operator slot semaphore not available

E28862 v_dialer\dialer\src\core\agent.c FATAL ERROR ON SELECT - %d

E28863 v_dialer\dialer\src\core\agent.c ERROR - Unknown file descriptor

E28864 v_dialer\dialer\src\core\agent_io_util.cv_dialer\dialer\src\core\job_strter.c

Unknown IPC message - %s

E28865 v_dialer\dialer\src\core\agent_io_util.c Unknown Command message - %s

E28866 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\agent_tdss_util.cv_dialer\dialer\src\core\screen.c

Telephone line not available

E28867 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\agent_tdss_util.c

Telephone line not offhook

E28868 v_dialer\dialer\src\core\agent.c Callbacks are not permitted on inbound calls

E28869 v_dialer\dialer\src\core\agent.c Headset volume must be in the range of 1 to 8

E28870 v_dialer\dialer\src\core\agent_hs_util.c Reserve headset id request pending

E28871 v_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\DialerCmdCtrl\HeadsetLib.cpp

Invalid headset id - %s, %s

E28872 v_dialer\dialer\src\core\agent_hs_util.c Headset already connected

E28873 v_dialer\dialer\src\core\agent_hs_util.c Headset ID not reserved nor validated

E28874 v_dialer\dialer\src\core\agent_hs_util.c Connect headset request pending

E28875 v_dialer\dialer\src\core\agent_hs_util.c No headset connect request pending

Page 319: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 317

E28876 v_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\DialerCmdCtrl\HeadsetLib.cpp

Headset not connected

E28877 v_dialer\dialer\src\core\agent_hs_util.c Disconnect headset request pending

E28878 No headset disconnect request pending

E28879 Headset not disconnected

E28880 v_dialer\dialer\src\core\agent_hs_util.c Headset connection broken

E28881 v_dialer\dialer\src\core\agent_hs_util.c Headset connection re-connected

E28882 v_dialer\dialer\src\core\agent.c Already available for work - Cannot change class

E28883 v_dialer\dialer\src\core\agent.c Invalid work class

E28884 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_misc_util.c

Not attached to data shared memory

E28885 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_misc_util.cv_dialer\dialer\src\core\agent_pvrs_util.c

Not attached to a job

E28886 v_dialer\dialer\src\core\agent.c Unit work lists are not permitted on this job

E28887 v_dialer\dialer\src\core\agent.c Already available for work - Cannot change unit id

E28888 v_dialer\dialer\src\core\agent.c Unit id not found

E28889 v_dialer\dialer\src\core\agent.c Attached to a job already - Must detach first

E28890 v_dialer\dialer\src\core\agent.c Failure to open job %s resource file

E28891 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_misc_util.c

Must specify INBOUND or OUTBOUND operation

E28892 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_misc_util.c

No inbound calling list fields available

Page 320: PC4 Troubleshooting Main

318 Maintenance and Troubleshooting Guide March 2008

E28893 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_misc_util.c

No outbound calling list fields available

E28894 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_misc_util.c

Field name not found

E28895 v_dialer\dialer\src\core\agent.c Already available for work

E28896 v_dialer\dialer\src\core\agent.c Headset must be active

E28897 v_dialer\dialer\src\core\agent.c Available for work request pending

E28898 v_dialer\dialer\src\core\agent.c Job not available

E28899 v_dialer\dialer\src\core\agent.c No available for work request pending

E28900 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_misc_util.cv_dialer\dialer\src\core\agent_hs_util.c

Wrong message id received - %s

E28901 v_dialer\dialer\src\core\agent.c Not available for work

E28902 v_dialer\dialer\src\core\agent.c Already on work item

E28903 v_dialer\dialer\src\core\agent.c Already set ready for next work item

E28904 v_dialer\dialer\src\core\agent.c Request for no further work pending

E28905 v_dialer\dialer\src\core\agent.c Request to transfer to another job is active

E28906 v_dialer\dialer\src\core\agent.c Not ready for next work item

E28907 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_pvrs_util.c

Not a managed dialing job

E28908 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_pvrs_util.c

Not on work item

E28909 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_pvrs_util.c

Managed call already complete

E28910 v_dialer\dialer\src\core\agent.c Managed call cancelled or complete

E28911 v_dialer\dialer\src\core\agent.c Managed call cancelled

Page 321: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 319

E28912 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_misc_util.c

Data record not available for update

E28913 v_dialer\dialer\src\core\agent.c No job attached

E28914 v_dialer\dialer\src\core\agent.c Still available for work on the job

E28915 v_dialer\dialer\src\core\agent.c Not logged off job yet

E28916 v_dialer\dialer\src\core\agent_misc_util.c

Job attached - Must detach first

E28917 v_dialer\dialer\src\core\agent.c No job attached

E28918 v_dialer\dialer\src\core\agent.c Not avail for work on the job

E28919 v_dialer\dialer\src\core\agent.c Not currently assigned to a work item

E28920 v_dialer\dialer\src\core\agent_hs_util.c Headset ID not found in reserved list - %s

E28921 v_dialer\dialer\src\core\agent_misc_util.c

FATAL ERROR ABORTING

E28922 v_dialer\dialer\src\core\agent_hs_util.c No reserve headset id request pending

E28923 v_dialer\dialer\src\core\agent_hs_util.c Headset ID - %s already reserved

E28924 v_dialer\dialer\src\core\agent_io_util.c Must sign on system first

E28925 v_dialer\dialer\src\core\agent_misc_util.c

Already signed on the system

E28926 v_dialer\dialer\src\core\agent_misc_util.c

Invalid sign on

E28927 v_dialer\dialer\src\core\agent.c Agent - Unable to open command input socket - errno:%d

E28928 v_dialer\dialer\src\core\agent.c Agent - Unable to find agent service entry in /etc/services

E28929 v_dialer\dialer\src\core\agent.c Agent - Unable to bind to local address - errno:%d

E28930 v_dialer\dialer\src\core\agent.c Agent - Unable to setup listen on socket - errno:%d

E28931 v_dialer\dialer\src\core\agent.c Agent - Fork of process failed - errno:%d

Page 322: PC4 Troubleshooting Main

320 Maintenance and Troubleshooting Guide March 2008

E28932 v_dialer\dialer\src\core\agent.c Agent - Accept socket connection call failed - errno:%d

E28933 v_dialer\dialer\src\core\agent_io_util.c Agent - Read error on client command socket - count:%d, errno:%d

E28934 v_dialer\dialer\src\core\agent_io_util.c Agent - Send error on client command socket - errno:%d

E28935 v_dialer\dialer\src\core\agent_misc_util.c

Agent - Parent process exiting

E28936 v_dialer\dialer\src\core\agent.c Agent - Setting of linger failed - errno:%d

E28937 v_dialer\dialer\src\core\operator.c %s agent is not allowed

E28938 v_dialer\dialer\src\core\api_jobctl.c Invalid phone type

E28940 v_dialer\dialer\src\core\agent_tdss_util.cv_dialer\dialer\src\core\transfer.c

Operator - data_synced timeout, data may not be updated

E28942 v_dialer\dialer\src\core\agent_tdss_util.cv_dialer\dialer\src\core\screen.c

Job %s is not available

E28943 v_dialer\dialer\src\core\screen.c Invalid key

E28944 v_dialer\dialer\src\core\screen.c COLONS(:) NOT ALLOWED IN PHONE FIELD

E28945 v_dialer\dialer\src\core\operator.c Managed agents only permitted

E28946 v_dialer\dialer\src\core\agent.c Agent not acquired yet

E28947 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Invalid call completion code %s

E28948 v_dialer\dialer\src\core\joblib.c Jobmon found incorrect PID %d when releasing opslot %d

E28949 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Unable to mark as DO NOT CALL

E28950 v_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\operator.c

Extension not in database

E28951 v_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\operator.c

Extension in use

E28952 v_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\operator.c

Cannot add agent

Page 323: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 321

E28953 v_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\operator.c

Acd_ext file read failed

E28954 v_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\operator.c

Duplicate login - please try again

E28955 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

DNC cannot find key field %s

E28956 v_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\operator.c

ACD Login Error

E28957 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Unable to mark other calling lists

E28958 v_dialer\dialer\src\core\donotcall.c Do Not Call group '%s' not defined

E28959 v_dialer\dialer\src\core\operator.c Invalid Agent Type

E28960 v_dialer\dialer\src\core\dnc_mark.c HASH key %s not defined in calling list %s

E28961 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\src\core\operator.c

Invalid Jobname

E28962 v_dialer\dialer\src\core\operator.c ERROR - Unknown file descriptor

E28963 v_dialer\dialer\src\core\screen.c ZONEPHONE%d field not set

E28964 v_dialer\dialer\src\core\agent.c Agent phone is busy. Release phone line before proceeding.

E28965 v_dialer\dialer\src\core\agent.c Softdialer link is down. Please wait until the link is up.

E28966 v_dialer\dialer\src\core\operator.c Invalid headset ID

E28967 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\operator.cv_dialer\dialer\src\core\screen.c

Agent is not allowed to logoff

E28968 v_dialer\dialer\src\core\operator.c Failed to register with dispatcher

E28969 v_dialer\dialer\src\core\agent_pvrs_util.c Operator - init_op_cntrl() invoked with NULL curr_op_ptr

E28970 v_dialer\dialer\src\core\agent_pvrs_util.cv_dialer\dialer\src\core\operator.c

Error queuing jobname data in list_running_jobs

Page 324: PC4 Troubleshooting Main

322 Maintenance and Troubleshooting Guide March 2008

E28971 v_dialer\dialer\src\core\agent_pvrs_util.cv_dialer\dialer\src\core\oper_pvrs.cv_dialer\dialer\src\core\screen.c

Operator - cannot access job resource file

E28972 v_dialer\dialer\src\core\agent_pvrs_util.cv_dialer\dialer\src\core\oper_pvrs.cv_dialer\dialer\src\core\screen.c

Operator - Timed out while waiting for job resouce file

E28973 v_dialer\dialer\src\core\agent_pvrs_util.cv_dialer\dialer\src\core\oper_pvrs.cv_dialer\dialer\src\core\screen.c

Operator - Cannot setup screen '%s'.

E28974 v_dialer\dialer\src\core\agent_pvrs_util.cv_dialer\dialer\src\core\screen.c

Operator - cannot read screen map - %s:%s

E28975 v_dialer\dialer\src\core\screen.c Cannot search when previewing a recall

E28976 v_dialer\dialer\src\core\screen.c Cannot dial from deleted record

E28977 v_dialer\dialer\src\core\operator.c Operator - Failed to initialize signal %s(%d)

E28978 v_dialer\dialer\src\core\operator.c Operator - Failed to ignore signal %s(%d)

E28979 v_dialer\dialer\src\core\screen.c Operator - Failed to enable auto release SIGUSR1 handler

E28980 v_dialer\dialer\src\core\screen.c Operator - Failed to disable auto release SIGUSR1 handler

E28981 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\operator.c

Invalid format for %s for job %s

E28982 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\screen.c

Managed call cannot be cancelled

E28983 v_dialer\dialer\src\core\agent.c AGTNoFurtherWork is already in progress

E28984 v_dialer\dialer\src\core\agent.c Agent is being released to ACD inbound

E29000 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\api_jobctl.c

Managed dialing capable jobs only

E29001 v_dialer\dialer\src\core\api_jobctl.c Jobmon - Failed on startup

E29002 v_dialer\dialer\src\core\api_jobctl.c Jobmon - Failed to Setup Windows

Page 325: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 323

E29006 v_dialer\dialer\src\core\api_jobctl.c Job '%s' not running

E29007 Job not ready, waiting %d seconds...

E29008 Job not Ready - Logon later

E29009 v_dialer\dialer\src\core\api_jobctl.c Outbound capable jobs only

E29010 v_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\core\joblib.c

Inbound capable jobs only

E29011 v_dialer\dialer\src\core\api_jobctl.c Not a multi-unit job

E29012 v_dialer\dialer\src\core\api_jobctl.c May only monitor Inbound

E29013 v_dialer\dialer\src\core\api_jobctl.c Invalid number entered

E29014 v_dialer\dialer\src\core\api_jobctl.c Monitoring of phone line disabled

E29015 v_dialer\dialer\src\core\api_jobctl.c Monitoring of agent disabled

E29016 v_dialer\dialer\src\core\api_jobctl.c Invalid port for monitoring agents

E29017 v_dialer\dialer\src\core\api_jobctl.c Agent being monitored

E29018 v_dialer\dialer\src\core\joblib.c No jobs currently running.

E29019 v_dialer\dialer\src\core\api_jobctl.c Error multiple job entrys in SHM

E29020 v_dialer\dialer\src\core\api_jobctl.c No agents having a record available

E29021 v_dialer\dialer\src\core\api_jobctl.c Record no longer available

E29022 v_dialer\dialer\src\core\api_jobctl.c No units currently available

E29023 v_dialer\dialer\src\core\api_jobctl.c No agents available to be killed

E29024 v_dialer\dialer\src\core\api_jobctl.c Invalid entry, no changes saved.

E29025 v_dialer\dialer\src\core\api_jobctl.c No other jobs currently running.

E29026 v_dialer\dialer\src\core\api_jobctl.c No agents currently available.

E29027 v_dialer\dialer\src\core\api_jobctl.c Agent transfer currently being processed.

E29028 v_dialer\dialer\src\core\api_jobctl.c Phone line allocation currently being processed.

E29029 v_dialer\dialer\src\core\api_jobctl.c No jobs currently linked.

Page 326: PC4 Troubleshooting Main

324 Maintenance and Troubleshooting Guide March 2008

E29030 v_dialer\dialer\src\core\api_jobctl.c No jobs available for selection.

E29031 v_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Link Job '%s' already starting up.

E29032 v_dialer\dialer\src\core\api_jobctl.c No phone lines currently acquired

E29033 No request of phone lines currently pending

E29034 No phone lines of type %s acquired

E29035 Job linking capable jobs only

E29036 v_dialer\dialer\src\core\joblib.c Invalid system terminal.

E29037 v_dialer\dialer\src\core\joblib.c WARNING!!!

E29038 v_dialer\dialer\src\core\joblib.c May not monitor op/lines

E29039 Duplicate HEADSET value.

E29040 v_dialer\dialer\src\core\api_jobctl.c Illegal W, Q or U rate setting

E29041 Illegal Hit Rate setting

E29042 v_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\core\iicb_conf.c

Allow sending 75 characters

E29043 v_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\core\iicb_conf.c

jobmon: failed to send %s to %s

E29044 v_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\core\iicb_conf.c

Wrong type %s of message for job_strter

E29045 v_dialer\dialer\src\core\iicb_conf.c Invalid data from system for get_iicb_status

E29046 v_dialer\dialer\src\core\iicb_conf.c Invalid response for list_domain

E29047 v_dialer\dialer\src\core\iicb_conf.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Invalid control method

E29048 v_dialer\dialer\src\core\iicb_conf.c Invalid response for list_group

E29049 v_dialer\dialer\src\core\iicb_conf.c Invalid response for get_group_stats

Page 327: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 325

E29050 v_dialer\dialer\src\core\iicb_conf.c Resynch agents is not allowed in the current state

E29051 v_dialer\dialer\src\core\install_ext.c Unable to create a list of extensions

E29052 v_dialer\dialer\src\core\install_ext.c Unable to add extension to list!

E29053 v_dialer\dialer\src\core\install_ext.c Unable to insert extension

E29054 v_dialer\dialer\src\core\install_ext.c Entered a duplicate value

E29055 v_dialer\dialer\src\core\install_ext.c Error getting current pointer

E29056 v_dialer\dialer\src\core\api_jobctl.c No operator to monitor

E29057 v_dialer\dialer\src\core\api_jobctl.c Jobmon: Release code %d has count of %d

E29150 v_dialer\dialer\src\core\beeper.c %s:failed to %s

E29151 v_dialer\dialer\src\core\beeper.c Failed to initialize signals

E29152 v_dialer\dialer\src\core\beeper.c Failed to set SIGALRM handler

E29153 v_dialer\dialer\src\core\beeper.c BEEPER:unknown message %s

E29154 v_dialer\dialer\src\core\beeper.c Beeper - INTERVAL_ZIPTONE is not set in master.cfg

E29200 v_dialer\dialer\src\core\ao_recall.cv_dialer\dialer\src\core\caller.cv_dialer\dialer\src\core\conn_mgr.cv_dialer\dialer\src\core\agent_tdss_util.c

%s - Failed to send msg[%s] on channel %d

E29201 %s - Failed to %s data segment

E29202 %s - Failed to %s unit segment

Page 328: PC4 Troubleshooting Main

326 Maintenance and Troubleshooting Guide March 2008

E29203 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\ao_recall.cv_dialer\dialer\src\core\beeper.cv_dialer\dialer\src\core\caller.cv_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\src\core\job_strter.cv_dialer\dialer\src\core\joblib.cv_dialer\dialer\src\core\operator.cv_dialer\ivr\src\ivr_config.cv_dialer\ivr\src\ivr_conn.cv_dialer\dialer\src\utility\mem_dump.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\dialer\src\core\porter.cv_dialer\dialer\src\core\recall_rmp.cv_dialer\dialer\src\utility\shmon.c

%s - Failed to attach data segment

E29204 v_dialer\dialer\src\core\conn_mgr.c %s - Failed to create data segment

E29205 v_dialer\dialer\src\core\listops.c %s - Failed to create unit segment

E29206 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\operator.c

%s - Failed to attach unit segment

E29207 v_dialer\dialer\src\core\screen.c Invalid number entered

E29208 v_dialer\dialer\src\core\caller.cv_dialer\dialer\src\core\joblib.cv_dialer\dialer\src\core\driver.cv_dialer\dialer\src\core\msg_loader.c

%s - Failed to open channel %d

E29210 v_dialer\dialer\src\core\msg_loader.c %s - Failed to erase voice message %s

E29212 v_dialer\dialer\src\core\msg_loader.c %s - Failed to erase all messages

E29213 v_dialer\dialer\src\core\msg_loader.cv_dialer\dialer\DialerCmdCtrl\DccsAudioFileValidator.cpp

%s - MSGNO parameter too big

E29214 v_dialer\dialer\src\core\msg_loader.cv_dialer\dialer\DialerCmdCtrl\DccsAudioFileValidator.cpp

%s - Too many messages to load

E29400 v_dialer\dialer\src\core\testmsg.c Unable to find base file for %s

Page 329: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 327

E29500 v_dialer\dialer\src\core\ao_recall.c ao_recall: failed to send %s

E29501 v_dialer\dialer\src\core\ao_recall.c ao_recall: callsel for %s failed

E29502 dialer/src/core/ao_recall.c ao_recall - cannot retrieve selection file from '%s'

E29503 dialer/src/core/ao_recall.c ao_recall - no strategy file in selection file '%s'

E29505 dialer/src/core/ao_recall.c Error queuing timeout data in add_timeout

E29600 Unable to attach to data segment

E29601 HUNTGRP set incorrectly

E29602 Login code not defined for line %s

E29603 Could not open channel #%d

E29604 No login dial tone on line #%d

E29605 No dial tone on line #%d

E29606 Unable to dial %s

E29607 Error with line %d

E29608 ACD_login : Signal Abort:%s(%d)

E29700 v_dialer\dialer\src\core\joblist_ed.c Invalid Selection Number

E29701 v_dialer\dialer\src\core\ld_joblist.cv_dialer\dialer\src\core\joblist_ed.c

Unable to open %s for reading

E29702 v_dialer\dialer\src\core\ld_joblist.cv_dialer\dialer\src\core\joblist_ed.c

Unable to open %s for writing

E29703 v_dialer\dialer\src\core\ld_joblist.cv_dialer\dialer\src\core\joblist_ed.c

Unable to load job file for agent %s

E29704 v_dialer\dialer\src\core\ld_joblist.c Unable to read header in job file for agent %s

E29705 v_dialer\dialer\src\core\ld_joblist.c Unable to read job list in job file for agent %s

E29706 v_dialer\dialer\src\core\ld_joblist.cv_dialer\dialer\src\core\joblist_ed.c

Unable to write header in job file for agent %s

Page 330: PC4 Troubleshooting Main

328 Maintenance and Troubleshooting Guide March 2008

E29707 v_dialer\dialer\src\core\ld_joblist.cv_dialer\dialer\src\core\joblist_ed.c

Unable to write job list in job file for agent %s

E29708 v_dialer\dialer\src\core\operator.c Job not valid for agent

E29709 v_dialer\dialer\src\core\joblist_ed.c Agent job list feature not activated

E29710 v_dialer\dialer\src\core\ld_joblist.c Invalid line (%s) in agentjobs.raw; skipping

E29711 v_dialer\dialer\src\core\ld_joblist.c Invalid header in job file for agent %s; will recreate

E29712 v_dialer\dialer\src\core\ld_joblist.c Job name for agent %s too long; will truncate to %d characters

E29714 v_dialer\dialer\src\core\ld_joblist.cv_dialer\dialer\src\core\joblist_ed.c

Unable to load job file for job chain %s

E29715 v_dialer\dialer\src\core\ld_joblist.cv_dialer\dialer\src\core\joblist_ed.c

Unable to write header in job file for job chain %s

E29716 v_dialer\dialer\src\core\joblist_ed.c Unable to write job list in job file for job chain %s

E29717 v_dialer\dialer\src\core\job_strter.cv_dialer\dialer\src\core\ld_joblist.cv_dialer\dialer\src\core\joblist_ed.c

Unable to read header in job file for job chain %s

E29718 v_dialer\dialer\src\core\ld_joblist.c Invalid header in job file for job chain %s; will recreate

E29719 v_dialer\dialer\src\core\job_strter.cv_dialer\dialer\src\core\ld_joblist.cv_dialer\dialer\src\core\joblist_ed.c

Unable to read job list in job file for job chain %s

E29800 v_dialer\dialer\src\core\chainhandler.c Job Chain %s does not exist

E29900 v_dialer\dialer\src\core\job_strter.c Unable to start next job %s

E29901 v_dialer\dialer\src\core\job_strter.c %s - Chain %s already started.

E29902 v_dialer\dialer\src\core\job_strter.c %s - Max number of chains already started.

E29903 v_dialer\dialer\src\core\job_strter.c Unable to start job %s

E29904 v_dialer\dialer\src\core\job_strter.c Unable to stop job %s

Page 331: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 329

E29950 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\agent_tdss_util.cv_dialer\dialer\src\core\screen.c

Feature not available in Softdialer Mode

E29951 v_dialer\dialer\src\core\port_hndle.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Specified more than %d line groups for use on job

E30000 IVR: -- The IVR_REC_LEN is not defined

E30001 IVR: -- The IVR_HEADER is not defined

E30002 IVR: -- The signal call failed - SIGUSR1

E30003 IVR: -- Cannot open the IVR read port

E30004 IVR: -- Cannot open the output file 1.

E30005 IVR: -- Problem with read from tty port

E30006 IVR: -- Received 15 bad IVR records1

E30007 IVR: -- Problem writing to output file

E30008 IVR: -- The signal call failed.

E30009 IVR: -- SIGUSR Cannot open output file 2.

E30010 IVR: -- SIGUSR Cannot open output file 1.

E30011 IVR: -- The IVR_TIME_INTVAL is not defined

E30012 IVR: -- The IVR_NUM_PORTS is not defined

E30013 IVR: -- Could not exec the process for child

E30014 IVR: -- Could not fork the child

E30015 IVR: SYSTEM call for ivr_mk_clist did not return 0

Page 332: PC4 Troubleshooting Main

330 Maintenance and Troubleshooting Guide March 2008

E30016 IVR: Could not re-exec the process for child

E30017 IVR: Tried to restart the child 15 times unsuccessfully

E30018 IVR -- SEVERE ERROR, IVR_DAEMON HAS DIED.

E30019 IVR: -- System call did not return 0

E31200 v_dialer\dialer\src\custom\readwrt.c Null character specified as fill not allowed

E31400 v_dialer\dialer\src\custom\atohex.c Not a valid hexadecimal

E32000 v_dialer\dialer\src\dbconst\readtape.c %s - No backup list file given

E32001 v_dialer\dialer\src\dbconst\readtape.c %s - File dictionary name missing

E32002 v_dialer\dialer\src\dbconst\readtape.c %s - Calling list or file dictionary name missing

E32003 v_dialer\dialer\src\dbconst\readtape.c %s - One or both merge file names missing

E32004 v_dialer\dialer\src\dbconst\readtape.c %s - Warning: Reached record limit, additional data not converted

E32005 v_dialer\dialer\src\dbconst\readtape.c %s - Invalid calling list name

E32005 v_dialer\dialer\src\dbconst\readtape.c %s - Mismatch in calling lists

E32006 v_dialer\dialer\src\dbconst\readtape.c %s - Invalid tape record size

E32007 v_dialer\dialer\src\dbconst\readtape.c %s - Invalid switch year parameter (%d), using default of 70

E32008 v_dialer\dialer\src\dbconst\readtape.c %s - Rewind failed

E32400 v_dialer\dialer\src\dbconst\readtape.cv_dialer\dialer\src\dbconst\writetape.c

%s - System OS ID error

E32401 v_dialer\dialer\src\dbconst\readtape.cv_dialer\dialer\src\dbconst\writetape.c

%s - Backup device name(s) missing

E32402 v_dialer\dialer\src\dbconst\readtape.cv_dialer\dialer\src\dbconst\writetape.c

%s - Calling list name missing

E32403 v_dialer\dialer\src\dbconst\readtape.cv_dialer\dialer\src\dbconst\writetape.c

%s - Dictionary or configuration file missing

Page 333: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 331

E32404 v_dialer\dialer\src\dbconst\readtape.cv_dialer\dialer\src\dbconst\writetape.c

%s - Bad tape device name: %s

E32405 v_dialer\dialer\src\dbconst\readtape.c %s - No backup list file given

E32600 v_dialer\dialer\src\dbconst\moj_conv.cv_dialer\dialer\DialerCmdCtrl\VoicemsgCfgTable.cpp

%s - Failed to execute program '%s' successfully.

E32601 Wrong hexadecimal value specified with -a option

E32602 v_dialer\dialer\src\dbconst\moj_conv.c CHARSET parameter in .conf file must be set to 'ASCII', with moj_conv program.

E32603 v_dialer\dialer\src\dbconst\moj_conv.c CHARCASE parameter in .conf file must be set to 'UPLOW', with moj_conv program.

E32604 v_dialer\dialer\src\dbconst\moj_conv.c TAPEDEV parameter in .conf file must not be the device in /dev directory.

E32605 v_dialer\dialer\src\dbconst\moj_conv.c BLKSIZE parameter and RESIZE parameter are inconsistent.

E32606 Cannot read Japanese code control file %s

E32607 v_dialer\dialer\src\dbconst\moj_conv.c No DBCS conversion table name in the code control file.

E34000 v_dialer\dialer\src\lettergen\formlet.c formlet - Error reading record: %s

E34001 v_dialer\dialer\src\lettergen\formlet.c Criteria error: %s

E35000 v_dialer\dialer\src\lstextract\ext_data.c ext_data - Failed to insert new Calling List header info %s

E35001 v_dialer\dialer\src\lstextract\ext_data.c ext_data - Invalid new calling list name

E35002 v_dialer\dialer\src\lstextract\ext_data.c ext_data - Unable to append - calling list fdicts differ

E35200 v_dialer\dialer\src\lstextract\ext_list.c ext_list - Invalid new calling list name

E35201 v_dialer\dialer\src\lstextract\ext_list.c ext_list - Failed to read file dictionary %s

Page 334: PC4 Troubleshooting Main

332 Maintenance and Troubleshooting Guide March 2008

E36000 v_dialer\dialer\src\dbmaint\record_ed.c Record_ed: Mark field '%s' not defined for list '%s'

E36001 v_dialer\dialer\src\dbmaint\record_ed.c Invalid record number %s

E36002 v_dialer\dialer\src\dbmaint\record_ed.c Failed to find record number %d

E36003 v_dialer\dialer\src\dbmaint\record_ed.c Failed to determine HASH field %s

E36004 v_dialer\dialer\src\dbmaint\record_ed.c Failed to find select field %s

E36005 v_dialer\dialer\src\dbmaint\record_ed.c Failed to find record number %d

E36006 v_dialer\dialer\src\dbmaint\redit_scrn.c Record_ed - Could not save Record %d, Value=%s in List %s

E36101 v_dialer\dialer\src\dbmaint\rec_update.c Rec_update - Child process %s terminated

E36200 v_dialer\dialer\src\dbmaint\redit_scrn.c Pattern error in field %d

E36201 v_dialer\dialer\src\core\dnc_mark.c Hash file '%s' (%s) is older than calling list '%s' (%s), please run clhash again.

E36202 v_dialer\dialer\src\core\dnc_mark.c Hash key field length %d does not match calling list field length %d

E36203 Source calling list of hash file %s does not match current calling list %s

E37000 v_dialer\admin\src\createop.c Error - Failed to load security files

E37001 v_dialer\admin\src\createop.c Invalid Name

E37002 v_dialer\admin\src\createop.c Name already exists or invalid name

E37003 v_dialer\admin\src\createop.c Invalid character in Name

E37004 v_dialer\admin\src\createop.c A password must be entered:ERROR

E37005 v_dialer\admin\src\createop.c Login Group is Not Valid

E37006 v_dialer\admin\src\createop.c ERROR: exceeded valid number of user entries[%d].:Invalid,%s:%s:%s:%s

Page 335: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 333

E37007 Createop:%s:Discard:%s:

E37008 v_dialer\admin\src\createop.c Invalid Name:Duplicate account

E37009 Name already exists:Failed to add account

E37010 v_dialer\admin\src\createop.cv_dialer\ivr\src\ivr_config.c

File is locked by another supervisor, try later!

E37011 v_dialer\admin\src\createop.cv_dialer\ivr\src\ivr_config.c

Unknown error, try later!

E37012 v_dialer\admin\src\createop.c No group information is loaded--%s

E37013 v_dialer\admin\src\createop.c Fail to read createop.cfg file

E37014 v_dialer\admin\src\createop.c Current user is not authorized

E37015 v_dialer\admin\src\createop.c Validate group information failed

E37016 v_dialer\admin\src\createop.c Invalid old password, Cannot add %s

E37017 v_dialer\admin\src\createop.c Error, cannot add %s

E37018 v_dialer\admin\src\createop.c Invalid or duplicate user %s

E37019 v_dialer\admin\src\createop.c Fail to add to ftpusers-> %s

E37020 v_dialer\admin\src\createop.c Invalid user name length: %s

E37021 v_dialer\admin\src\createop.c Cannot change owner of %s to admin

E37022 v_dialer\admin\src\createop.c Invalid sub-group found in sub-group string %s of group.pds file

E37023 v_dialer\admin\src\createop.cv_dialer\ivr\src\ivr_config.c

Could not setuid(), error = %d

E37024 v_dialer\admin\src\createop.cv_dialer\ivr\src\ivr_config.c

Could not setgid(), error = %d

E37025 v_dialer\admin\src\createop.c Have to supply both password file and vllogin or group file

E37026 v_dialer\admin\src\createop.c Fail to getpwnam(%s)

E37027 v_dialer\admin\src\createop.c alter_entry: Fail to do lckpwdf()

Page 336: PC4 Troubleshooting Main

334 Maintenance and Troubleshooting Guide March 2008

E37028 v_dialer\admin\src\createop.c %s not found in vllogin

E37029 v_dialer\admin\src\createop.c Fail to enforce new password for %s

E37030 v_dialer\admin\src\createop.c DEL_REC: Fail to delete %s

E37031 v_dialer\admin\src\createop.c EDIT_REC: Fail to modify account %s

E37032 v_dialer\admin\src\createop.c Account not found: %s

E37033 Fail to link correct profile for %s

E37034 v_dialer\admin\src\createop.c Fail to add user %s

E37035 v_dialer\admin\src\createop.c Missing Password or Menu fields: %s:%s:%s:%s

E37036 v_dialer\admin\src\createop.c %s not found in group file

E37037 v_dialer\admin\src\createop.c WARNING: Reached limit of MAX_USERS (%d) as set in createop.cfg file

E37038 v_dialer\admin\src\createop.c ERROR: Reached limit of MAX_USERS (%d) as set in createop.cfg file

E37039 Error - Failed to load existing user IDs

E37200 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Invalid Expert Calling Ratio

E37201 v_dialer\dialer\src\editor\config_ed.c Field '%s' not filled in

E37202 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

No Inbound jobs allowed on this system.

E37203 Number of reserved inbound lines must be from 1 to %s

E37204 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Invalid call completion code specified

E37205 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Invalid start or stop time format

E37206 Invalid Hit Rate

Page 337: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 335

E37207 Invalid paired phone count/type

E37208 v_dialer\dialer\src\editor\config_ed.c HUNTGRP: format error

E37209 No HUNTGRP setting.

E37210 Selection list not available for use

E37211 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Selection list for job not found

E37212 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

No Verification Selection List Ready for Job

E37213 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Selection list not created with this Calling List

E37214 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Number of telephone lines must be from 1 to 96

E37215 An odd number of telephone lines is not allowed

E37216 Quota Value less than one

E37217 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

HUNTGRP: format error

E37218 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

There must be a script label for answer specified

E37219 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Invalid call completion code for Quota Value %d

E37220 v_dialer\dialer\src\editor\config_ed.c Quota %d is not OP completion code

E37221 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

%s field missing from %s

E37222 v_dialer\dialer\src\editor\config_ed.c Creation date/time error: %s

E37223 v_dialer\dialer\src\editor\config_ed.c Data Transfer file %s.axfr: %s not in %s

Page 338: PC4 Troubleshooting Main

336 Maintenance and Troubleshooting Guide March 2008

E37224 v_dialer\dialer\src\editor\config_ed.c Wrong job for verification editor

E37225 v_dialer\dialer\src\editor\config_ed.c No editable line found in file: %s

E37226 v_dialer\dialer\src\editor\config_ed.c Failed to create link list header

E37227 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

ERROR: Job %s is already running

E37228 ERROR: Job file %s already in use

E37229 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Failed to find linked job file: %s

E37230 Managed dialing job linking is not permitted

E37231 v_dialer\dialer\src\editor\config_ed.c Sales verification job linking is not permitted

E37232 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Job linking is not permitted

E37233 v_dialer\dialer\src\editor\config_ed.c %s - Unable to start job %s

E37234 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Failed to find Inbound Job Screen: %s

E37235 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Failed to find Inbound Job Map: %s

E37236 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Failed to read Inbound List: %s

E37237 v_dialer\dialer\src\editor\config_ed.c Failed to find MSCRN - Job screen: %s

E37238 v_dialer\dialer\src\editor\config_ed.c Failed to find MSCRN - Job map: %s

E37239 v_dialer\dialer\src\editor\config_ed.c Number of multi screens does not match number of multi lists

E37240 v_dialer\dialer\src\editor\config_ed.c Failed to find ASCRN - Job screen: %s

Page 339: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 337

E37241 v_dialer\dialer\src\editor\config_ed.c Failed to find MSCRN - Job map: %s

E37242 v_dialer\dialer\src\editor\config_ed.c Failed to read Assoc List: %s

E37243 v_dialer\dialer\src\editor\config_ed.c Number of associate screens does not match number of associate lists

E37244 v_dialer\dialer\src\editor\config_ed.c Number of edit fields does not match number of associate lists

E37245 v_dialer\dialer\src\editor\config_ed.c %s - %s(err_code=%d)

E37246 v_dialer\dialer\src\editor\config_ed.c %s(err_code=%d)

E37247 v_dialer\dialer\src\editor\config_ed.c Unable to clear %s

E37248 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Line type specified already in use

E37249 v_dialer\dialer\src\editor\config_ed.c Improper usage

E37250 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

There must be a script label for call specified

E37251 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Initial Hit Rate out of range (1-100)

E37252 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Failed to open script file for IVR ID %s

E37253 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

IVR script name not specified; required if IVR ID specified

E37254 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Unable to find %s in script file for IVR ID %s

E37255 Calling list %s is not on local dialer.

E37256 v_dialer\dialer\src\editor\config_ed.c Selecting unit to log in to is not permitted with inbound-only job

E37300 v_dialer\admin\src\termprocess.c %s: Invalid process ID %d

E37301 v_dialer\admin\src\termprocess.c termprocess:fail to send signal message %s

Page 340: PC4 Troubleshooting Main

338 Maintenance and Troubleshooting Guide March 2008

E37400 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Failed to find %s: %s

E37401 Failed to save %s file: %s

E37402 v_dialer\dialer\src\editor\config_ed.c Failed to allocate %s

E37403 v_dialer\dialer\src\editor\config_ed.c Failed to read %s: %s

E37404 v_dialer\dialer\src\editor\config_ed.c Number of %s do not match number of %s

E37405 v_dialer\dialer\src\editor\config_ed.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

%s field missing or incorrect length

E37500 v_dialer\admin\src\signalit.c Fail to terminate process %d, errno %d

E37501 v_dialer\admin\src\signalit.c Fail to kill process %d, errno %d

E37502 v_dialer\admin\src\signalit.c Fail to send SIGUSR1 process %d, errno %d

E37503 v_dialer\admin\src\signalit.c Fail to setreuid to (-1, 0)

E37600 v_dialer\dialer\src\utility\agentcount.c Field #%d not filled in

E37601 v_dialer\dialer\src\editor\master_ed.c No editable line found in file: %s

E37602 v_dialer\dialer\src\editor\master_ed.c Failed to create link list header

E37603 v_dialer\dialer\src\editor\master_ed.c ERROR: %s already in use

E37604 v_dialer\dialer\src\editor\master_ed.c Unable to clear %s

E37800 v_dialer\dialer\src\editor\master_ed.c Groupname %s has invalid length

E37801 Skeleton path %s for group %s does not exist

E37802 v_dialer\admin\src\addgroup.c Could not add group %s

E38000 v_dialer\dialer\src\markrec\chkentdt.c Chkentdt - Failed to create old database index

E38001 Chkentdt - Failed to create new database index

Page 341: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 339

E38002 v_dialer\dialer\src\markrec\chkentdt.c Chkentdt WARNING - cannot open old database %s. Assuming none exists

E38003 v_dialer\dialer\src\markrec\chkentdt.c Chkentdt ERROR:-S option must be used with -i option

E38004 v_dialer\dialer\src\markrec\chkentdt.c Chkentdt - Unable to malloc hash_table

E38400 v_dialer\dialer\src\markrec\latemrk.c Latemrk - Failed to create calling list index

E38401 Latemrk - Failed to create late list index

E38402 v_dialer\dialer\src\markrec\latemrk.c Latemrk - file error building late list

E38403 v_dialer\dialer\src\markrec\latemrk.c Latemrk - field_list - key fields not the same length

E38404 v_dialer\dialer\src\markrec\latemrk.c Latemrk - %s recno %d locked; skipping;

E38405 v_dialer\dialer\src\markrec\latemrk.c Latemrk - %s '%s' not found in %s, skipping;

E38406 v_dialer\dialer\src\markrec\latemrk.c Latemrk - Field '%s' not found in %s

E38600 v_dialer\dialer\src\markrec\get_field.cv_dialer\dialer\src\markrec\set_field.c

%s - Failed to read record: %s

E38601 v_dialer\dialer\src\markrec\set_field.c %s - Failed to update record: %s

E38602 v_dialer\dialer\src\markrec\get_field.cv_dialer\dialer\src\markrec\set_field.c

%s - Failed to create calling list search index

E38603 v_dialer\dialer\src\markrec\get_field.cv_dialer\dialer\src\markrec\set_field.c

%s - %s '%s' not found in %s.

E38604 v_dialer\dialer\src\markrec\get_field.cv_dialer\dialer\src\markrec\set_field.c

%s - Valid record range is 1 - %d.

E38605 v_dialer\dialer\src\markrec\get_field.c %s - No records in calling list

E38800 v_dialer\dialer\src\markrec\latelst.c %s - key fields not the same length

E38801 %s - Key '%s' not found in hash file

Page 342: PC4 Troubleshooting Main

340 Maintenance and Troubleshooting Guide March 2008

E38802 %s - Error allocating memory for '%s'

E39000 Failed to find user logon entry %s in V/L login file

E39001 v_dialer\dialer\src\menu\menu.c Error _ No Menu Name

E39002 v_dialer\dialer\src\menu\menu.c Help File Not Found: %s

E39003 v_dialer\dialer\src\menu\menu.c Menu File Not Found: %s

E39004 v_dialer\dialer\src\menu\menu.c MENU(%d)Signal Interrupt=%d

E39005 v_dialer\dialer\src\menu\menu.c %s - User not authorized to run this menu - %s

E39200 v_dialer\dialer\src\menu\submenu.c Incorrect Item Number

E39201 v_dialer\dialer\src\menu\submenu.c Failed to Search Directory for File Extension: %s

E39202 v_dialer\dialer\src\menu\submenu.c Invalid list number

E40000 v_dialer\dialer\src\pcextract\brkfile.c No Calling Statistics Files Available

E40001 v_dialer\dialer\src\pcextract\brkfile.c PC Analysis - Reopen of %s failed

E40002 v_dialer\dialer\src\pcextract\fileops.c PC Analysis - Invalid File Type of %c

E40003 v_dialer\dialer\src\pcextract\brkfile.c No Agent Files Available

E40200 v_dialer\dialer\src\pcextract\fileops.c Pc Analysis - Unknown Type %c for Input File type

E40201 v_dialer\dialer\src\pcextract\fileops.c File Name not Found

E40202 v_dialer\dialer\src\pcextract\fileops.c File does not Exist

E40203 v_dialer\dialer\src\pcextract\fileops.c In Help mode, Cannot Select Criteria

E40204 v_dialer\dialer\src\pcextract\fileops.c Invalid Field Order Select Number

E40400 v_dialer\dialer\src\pcextract\msetup.c %s - Invalid config file name

E40401 v_dialer\dialer\src\pcextract\msetup.c Invalid Extraction Type

E42000 v_dialer\dialer\src\preprocess\de_reject.c

-S option must be used with -i option

Page 343: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 341

E42100 v_dialer\dialer\src\preprocess\ij_merge.c

-S option must be used with -i option

E42101 v_dialer\dialer\src\preprocess\ij_merge.c

Third argument must be -c

E42400 v_dialer\dialer\src\preprocess\clhashin.c %s - Failed hash open of %s

E42401 %s - Failed to stat associated calling list %s

E42402 v_dialer\dialer\src\preprocess\clhashin.c %s - %s : %s

E42403 v_dialer\dialer\src\preprocess\clhashin.c %s - Associate list and hash index date/time do not agree for %s. Run clhash

E42404 v_dialer\dialer\src\preprocess\clhashin.c %s - Field %s length %d not match hash key %s length %d

E42405 v_dialer\dialer\src\preprocess\clhashin.c Record number %s too big for field %s

E42406 v_dialer\dialer\src\preprocess\clhashin.c %s - Record number %s too big for field %s

E42600 Field undefined in the calling list

E42601 Gap found between field names within group

E42602 Missing assigned field values

E42603 Gap found in value selections

E42604 Field value has an invalid character

E42605 Missing Range or Item specification in field values

E42606 Values not in ascending order

E42607 No fields selected for reporting

E42608 Miss value in filler criteria

E42609 Miss field name in filler criteria

E42610 Pattern Error: %s

E42611 'ALL' cannot co-exist with other selections

E42612 Unknown call completion code

Page 344: PC4 Troubleshooting Main

342 Maintenance and Troubleshooting Guide March 2008

E42613 %s - Unknown select file %s

E42614 %s - Unknown supplement file %s

E42615 Invalid code. Type R for row, C for column or T for table.

E42616 Invalid line number

E42617 Cannot move to same location

E42800 Invalid number indicator: %s

E42801 v_dialer\dialer\src\preprocess\setzones.c

-S option must be used with -i option

E43000 v_dialer\dialer\src\preprocess\update_cl.c

%s - Match field %s length %d not match associated field %s length %d

E43001 v_dialer\dialer\src\preprocess\update_cl.c

Record %d - Bad Record number in field %s

E43002 v_dialer\dialer\src\preprocess\update_cl.c

%s - Record %d - Assoc list %s read error(%d) for record no. %d

E43200 Record %d - Too many records in set

E43201 %s - Record %d - Too many records in set

E43400 v_dialer\dialer\src\preprocess\clhash.cv_dialer\dialer\src\preprocess\clhashin.cv_dialer\dialer\src\preprocess\update_cl.cv_dialer\dialer\src\preprocess\update_upl.c

TERMINAL ERROR

E43401 v_dialer\dialer\src\preprocess\clhashin.cv_dialer\dialer\src\preprocess\update_cl.cv_dialer\dialer\src\preprocess\update_upl.c

Record %d - READ ERROR (%d)

E43402 v_dialer\dialer\src\preprocess\clhashin.cv_dialer\dialer\src\preprocess\update_cl.cv_dialer\dialer\src\preprocess\update_upl.c

Record %d - WRITE ERROR (%d)

Page 345: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 343

E43403 v_dialer\dialer\src\preprocess\update_upl.c

Record %d - HASH ERROR (%d)

E43404 v_dialer\dialer\src\preprocess\clhash.cv_dialer\dialer\src\preprocess\update_upl.c

%s - Failed hash initialization!

E43405 v_dialer\dialer\src\preprocess\clhashin.cv_dialer\dialer\src\preprocess\update_cl.cv_dialer\dialer\src\preprocess\update_upl.c

%s - Failed to stat calling list %s

E43406 v_dialer\dialer\src\preprocess\clhashin.cv_dialer\dialer\src\preprocess\update_cl.cv_dialer\dialer\src\preprocess\update_upl.c

%s - Record %d - READ ERROR (%d)

E43407 v_dialer\dialer\src\preprocess\clhash.cv_dialer\dialer\src\preprocess\update_upl.c

%s - Record %d - HASH ERROR (%d)

E43408 v_dialer\dialer\src\preprocess\update_cl.cv_dialer\dialer\src\preprocess\update_upl.c

%s - Record %d - WRITE ERROR (%d)

E43500 v_dialer\dialer\src\preprocess\msgmap.c

Calling List %s open error

E43501 v_dialer\dialer\src\preprocess\msgmap.c

Calling List %s header error

E43502 v_dialer\dialer\src\preprocess\msgmap.c

Calling List %s definition error

E43503 v_dialer\dialer\src\preprocess\msgmap.c

Field name %s missing in Calling List %s

E43504 v_dialer\dialer\src\preprocess\msgmap.c

Error initializing LISTS hash file %s

E43505 v_dialer\dialer\src\preprocess\msgmap.c

Error hashing record %d in Calling List %s. Errcode = %d

E43506 v_dialer\dialer\src\preprocess\msgmap.c

Error writing hash record %d in hash file %s. Errcode = %d

E43507 v_dialer\dialer\src\preprocess\msgmap.c

System_value %d too big. Limit is MAXMSGS

E43508 Record %d - READ ERROR

Page 346: PC4 Troubleshooting Main

344 Maintenance and Troubleshooting Guide March 2008

E43509 v_dialer\dialer\src\preprocess\msgmap.c

Record %d - WRITE ERROR

E43510 v_dialer\dialer\src\preprocess\msgmap.c

Record %d - CALLING LIST BUFFER MALLOC ERROR

E43511 v_dialer\dialer\src\preprocess\msgmap.c

Error: colon missing on line %s:%s

E43512 dialer\src\preprocess\msgmap.c %s:%s, Field name %s missing in Calling List %s

E44000 v_dialer\dialer\src\reports\history\hist_rpt.c

%s - Bad arguments

E44001 v_dialer\dialer\src\reports\history\hist_rpt.c

%s - Memory allocation error

E44002 v_dialer\dialer\src\reports\history\hist_rpt.c

%s - File access error

E44003 v_dialer\dialer\src\reports\history\hist_rpt.c

%s - Equation syntax error

E44004 v_dialer\dialer\src\reports\history\hist_rpt.c

%s - Invalid format code

E44005 v_dialer\dialer\src\reports\history\hist_rpt.c

%s - Report configuration error

E44006 v_dialer\dialer\src\reports\history\hist_rpt.c

%s - No HISTORY variable in master.cfg

E44007 v_dialer\dialer\src\reports\history\hist_rpt.c

%s - History dictionary error

E44008 v_dialer\dialer\src\reports\history\hist_rpt.c

%s - Incorrect sort field name

E44009 v_dialer\dialer\src\reports\history\hist_rpt.c

%s - Failed to open report format file

E44010 v_dialer\dialer\src\reports\history\hist_rpt.c

%s - Failed to write output report file

E44011 v_dialer\dialer\src\reports\history\hist_rpt.c

%s - No record selection criteria given

E44012 v_dialer\dialer\src\reports\history\hist_rpt.c

%s - Failed to open input file

E44013 v_dialer\dialer\src\reports\history\hist_rpt.c

%s - Failed to set/reset record lock

E44014 v_dialer\dialer\src\reports\history\hist_rpt.c

%s - job and report format type are not compatible

Page 347: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 345

E45000 rpt_view - Caught signal %d and terminated

E45001 v_dialer\dialer\src\reports\rpt_mgr\rpt_view.c

Incorrect Report Number

E45200 File name for view missing

E45201 pds_view - Caught signal %d and terminated

E45202 v_dialer\dialer\src\reports\rpt_mgr\pds_view.c

REPORT %s NOT FOUND

E46200 v_dialer\dialer\src\reports\reportgen\reportexp.cv_dialer\dialer\src\reports\reportgen\reportsub.c

Invalid line number

E46201 v_dialer\dialer\src\reports\reportgen\reportexp.c

Exceeded maximum number of expressions

E46202 v_dialer\dialer\src\reports\reportgen\reportexp.c

Invalid PAGE flag

E46203 v_dialer\dialer\src\reports\reportgen\reportexp.c

Invalid RESET flag

E46204 v_dialer\dialer\src\reports\reportgen\reportexp.c

Missing expression name

E46205 v_dialer\dialer\src\reports\reportgen\reportexp.c

Unknown operator: %s

E46206 v_dialer\dialer\src\reports\reportgen\reportexp.c

Missing operator

E46207 v_dialer\dialer\src\reports\reportgen\reportexp.c

Too many operands for operator '%s'

E46208 v_dialer\dialer\src\reports\reportgen\reportexp.c

Missing operand for operator '%s'

E46209 v_dialer\dialer\src\reports\reportgen\reportexp.c

%s is undefined in the printcap file

E46210 v_dialer\dialer\src\reports\reportgen\reportexp.cv_dialer\dialer\src\reports\reportgen\reportsub.cv_dialer\dialer\src\reports\reportgen\reportsel.cv_dialer\dialer\src\reports\reportgen\reportprn.c

%s is undefined in the dictionary

Page 348: PC4 Troubleshooting Main

346 Maintenance and Troubleshooting Guide March 2008

E46211 v_dialer\dialer\src\reports\reportgen\reportexp.c

Unknown variable name %s

E46212 v_dialer\dialer\src\reports\reportgen\reportexp.c

Unmatching ' in literal string %s

E46213 v_dialer\dialer\src\reports\reportgen\reportexp.c

Unknown data type: %s

E46214 v_dialer\dialer\src\reports\reportgen\reportexp.c

Invalid data type for operator %s

E46400 v_dialer\dialer\src\reports\reportgen\reportfmt.c

No expression located at cursor position

E46401 v_dialer\dialer\src\reports\reportgen\reportfmt.c

Insufficient memory for screen buffer allocation

E46402 v_dialer\dialer\src\reports\reportgen\reportfmt.c

End of file reached

E46403 v_dialer\dialer\src\reports\reportgen\reportfmt.c

No lines in buffer

E46404 v_dialer\dialer\src\reports\reportgen\reportfmt.c

Invalid starting location - expression overlap

E46405 v_dialer\dialer\src\reports\reportgen\reportfmt.c

Invalid ending location - expression overlap

E46406 v_dialer\dialer\src\reports\reportgen\reportfmt.c

Must specify start location

E46407 v_dialer\dialer\src\reports\reportgen\reportfmt.c

Invalid ending location

E46408 v_dialer\dialer\src\reports\reportgen\reportfmt.c

Exceeded maximum report dimensions

E46409 v_dialer\dialer\src\reports\reportgen\reportfmt.c

Failed to open format temp file

E46410 v_dialer\dialer\src\reports\reportgen\reportfmt.c

Invalid line marker at line %d

E46411 v_dialer\dialer\src\reports\reportgen\reportfmt.c

Invalid starting location

E46412 v_dialer\dialer\src\reports\reportgen\reportfmt.c

Invalid ending location

E46600 v_dialer\dialer\src\reports\reportgen\reporthlp.c

No entries in printcap file

E46601 v_dialer\dialer\src\reports\reportgen\reporthlp.c

No entries in file dictionary

Page 349: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 347

E46602 v_dialer\dialer\src\reports\reportgen\reporthlp.c

No expressions defined in file

E46603 v_dialer\dialer\src\reports\reportgen\reportinit.c

Failed to open report list file

E46800 v_dialer\dialer\src\reports\reportgen\reportinit.c

Failed to list defined printer model names

E46801 v_dialer\dialer\src\reports\reportgen\reportinit.c

Failed to read printcap file

E46802 v_dialer\dialer\src\reports\reportgen\reportinit.c

Unknown printer model

E46803 v_dialer\dialer\src\reports\reportgen\reportinit.c

Report -

E46804 v_dialer\dialer\src\reports\reportgen\reportinit.c

Failed to get defn. for calling list

E46805 v_dialer\dialer\src\reports\reportgen\reportinit.c

File name missing

E46806 v_dialer\dialer\src\reports\reportgen\reportinit.c

Failed to open text substitution file

E46807 v_dialer\dialer\src\reports\rptgen\reportconvert.cv_dialer\dialer\src\reports\reportgen\reportinit.cv_dialer\dialer\src\reports\reportgen\reportconvert_prev.c

Report control file name too long

E46808 v_dialer\dialer\src\reports\rptgen\reportconvert.cv_dialer\dialer\src\reports\reportgen\reportinit.cv_dialer\dialer\src\reports\reportgen\reportconvert_prev.c

Failed to write report control file

E46809 v_dialer\dialer\src\reports\reportgen\reportinit.c

Failed to read report help file

E46810 v_dialer\dialer\src\reports\reportgen\reportinit.cv_dialer\dialer\src\reports\reportgen\reportconvert_prev.cv_dialer\dialer\src\reports\rptgen\reportconvert.c

Failed to open report control file: %s

Page 350: PC4 Troubleshooting Main

348 Maintenance and Troubleshooting Guide March 2008

E46811 v_dialer\dialer\src\reports\reportgen\reportinit.cv_dialer\dialer\src\reports\reportgen\reportconvert_prev.cv_dialer\dialer\src\reports\rptgen\reportconvert.c

Unknown report control file: %s

E47000 Failed to initialize

E47001 v_dialer\dialer\src\scrnbld\scrnbld.c Failed to read command keys file

E47002 v_dialer\dialer\src\scrnbld\scrnbld.c Terminal Screen too small for screen editor.

E47003 v_dialer\dialer\src\scrnbld\scrnbld.c May not shift fields further

E47004 v_dialer\dialer\src\scrnbld\scrnbld.c Only Date, Time, or Numeric fields may have Verification Formats

E47005 v_dialer\dialer\src\scrnbld\scrnbld.c Field does not fit in screen.

E47006 v_dialer\dialer\src\scrnbld\scrnbld.c May not overlay screen labels.

E47007 v_dialer\dialer\src\scrnbld\scrnbld.c May not place fields in column one.

E47008 v_dialer\dialer\src\scrnbld\scrnbld.c May not overlap screen fields.

E47009 v_dialer\dialer\src\scrnbld\scrnbld.c May only edit lists [1..%d]

E47010 v_dialer\dialer\src\scrnbld\scrnbld.c %s(ScreenBuilder) - Failed to open output report file

E47011 May not change to the same file dictionary.

E47012 v_dialer\dialer\src\scrnbld\scrnbld.c No Jobs available

E47013 v_dialer\dialer\src\scrnbld\scrnbld.c No jobs use the current screen

E47014 v_dialer\dialer\src\scrnbld\scrnbld.c Screen does not exist:

E47015 v_dialer\dialer\src\scrnbld\scrnbld.c No changes made.

E47016 UNFINISHED COMMAND: TESTMODE

E47017 Invalid %s number specified=%d.

E47018 Cut & Paste Field Not %s

Page 351: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 349

E47019 v_dialer\dialer\src\scrnbld\sbld_block.c You may not PASTE over fields.

E47020 v_dialer\dialer\src\scrnbld\sbld_block.c Fields may not start in column one.

E47021 v_dialer\dialer\src\scrnbld\sbld_block.c Field in block does not fit on screen.

E47022 v_dialer\dialer\src\scrnbld\sbld_block.c Fields may not overlap.

E47023 v_dialer\dialer\src\scrnbld\sbld_block.c Block must fit on screen.

E47024 v_dialer\dialer\src\scrnbld\sbld_block.c Field[%s,%d] does not match dictionary.

E47025 v_dialer\dialer\src\scrnbld\scrnbld.c Not enough menu options

E47026 v_dialer\dialer\src\scrnbld\scrnbld.c ERROR: no screen open

E47027 v_dialer\dialer\src\scrnbld\scrnbld.c Failed to write screen file

E47028 v_dialer\dialer\src\scrnbld\scrnbld.c Save to a different name.

E47029 You may not %s the current edit screen.

E47030 v_dialer\dialer\src\scrnbld\scrnbld.c NO HELP TABLE

E47031 v_dialer\dialer\src\scrnbld\scrnbld.c Protected file.

E47032 v_dialer\dialer\src\scrnbld\scrnbld.c Use a different name.

E47033 v_dialer\dialer\src\scrnbld\scrnbld.c Invalid sequence number specified=%d.

E47034 v_dialer\dialer\src\scrnbld\scrnbld.c Invalid field number specified=%d.

E47035 v_dialer\dialer\src\scrnbld\sbld_block.c Cut & Paste Field Not Copied

E47036 v_dialer\dialer\src\scrnbld\sbld_block.c Cut & Paste Field Not Cut, or Copied

E47037 v_dialer\dialer\src\scrnbld\sbld_block.c Cut & Paste Field Not Cleared

E47038 v_dialer\dialer\src\scrnbld\scrnbld.c You may not delete the current edit screen.

E47039 v_dialer\dialer\src\scrnbld\scrnbld.c You may not recover the current edit screen.

E47040 v_dialer\dialer\src\scrnbld\scrnbld.c Failed to initialize Screen

E47041 Failed to initialize Keyboard

Page 352: PC4 Troubleshooting Main

350 Maintenance and Troubleshooting Guide March 2008

E49001 dialer_library\libcpp\src\Passwd.cpp Password verification failed for user: %s, Exception: %s

E50000 v_dialer\dialer\src\utility\adump.c Data File Not in Calling List Format

E50100 v_dialer\dialer\src\utility\agentcheck.cv_dialer\dialer\src\core\agent_misc_util.c

Exceeded number of %s agents

E50101 v_dialer\dialer\src\utility\agentcheck.c Exceeded wait limit for acceptance

E50200 v_dialer\dialer\src\utility\datetime.c Invalid time format

E50201 v_dialer\dialer\src\utility\datetime.c Invalid hour in time

E50202 v_dialer\dialer\src\utility\datetime.c Invalid minutes in time

E50203 v_dialer\dialer\src\utility\datetime.c Invalid date format

E50204 v_dialer\dialer\src\utility\datetime.c Invalid year in date

E50205 v_dialer\dialer\src\utility\datetime.c Invalid month in date

E50206 v_dialer\dialer\src\utility\datetime.c Invalid day in date

E50600 v_dialer\dialer\src\utility\enq_pty.c No Headset ID Specified.

E50601 v_dialer\dialer\src\utility\enq_pty.c Failed to Initialize Keyboard

E50602 v_dialer\dialer\src\utility\enq_pty.c Failed to Initialize screen environment

E50603 v_dialer\dialer\src\utility\enq_pty.c Failed to create display window.

E50604 v_dialer\dialer\src\utility\enq_pty.c Not a pseudo-terminal port

E50605 v_dialer\dialer\DialerCmdCtrl\HeadsetLib.cpp

No response from system, login failed

E50606 Headset ID (%d) Out of Range (1-%d)

E50607 Failed to select Headset ID(%d)

E50608 Exceeded retry limits, No valid headset ID specified

E50609 v_dialer\dialer\src\utility\enq_pty.c Exceeded retry limits, No valid key code specified

E50610 Headset ID (%d) Already in use by %s

Page 353: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 351

E50611 v_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\operator.cv_dialer\dialer\src\utility\enq_pty.c

Headset ID (%s) Already in use

E50612 v_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\operator.cv_dialer\dialer\src\utility\enq_pty.c

No more Headsets permitted on system

E50613 v_dialer\dialer\src\core\agent_hs_util.cv_dialer\dialer\src\core\operator.cv_dialer\dialer\src\utility\enq_pty.c

Failure to access Headset Table

E50800 op_logout: failed to establish input queue for hs %s

E51001 v_dialer\dialer\src\utility\fdictdump.c Goodbye...

E51200 v_dialer\dialer\src\utility\jobkeys.c No information on keys for job %s

E51201 No such keys file defined named: %s

E51400 Port_start - Failed to get VOICEDIR directory

E51600 v_dialer\dialer\src\utility\portcorr.c No <###tran.stat> files are marked with todays date

E51601 v_dialer\dialer\src\utility\portcorr.c Cannot open file chi_data

E52800 v_dialer\dialer\src\utility\ziptoarea.c Only single zipcode field is allowed

E52801 v_dialer\dialer\src\utility\ziptoarea.c Exceeded area code fields limit of (%d)

E52802 v_dialer\dialer\src\utility\ziptoarea.c Illegal option -%c

E52803 v_dialer\dialer\src\utility\ziptoarea.c No main option specified

E52804 v_dialer\dialer\src\utility\ziptoarea.c '-f' option also require '-a' & '-z' option

E52805 v_dialer\dialer\src\utility\ziptoarea.c Bad pattern specified with '-x' option

E52806 v_dialer\dialer\src\utility\ziptoarea.c Area code offset can't exceed %d

E53000 v_dialer\dialer\src\utility\copyfields.c %s - Unable to open Calling List '%s'

Page 354: PC4 Troubleshooting Main

352 Maintenance and Troubleshooting Guide March 2008

E53001 v_dialer\dialer\src\utility\copyfields.c %s - Unable to get List Definition for '%s'

E53002 v_dialer\dialer\src\utility\copyfields.c %s - Unable to stat Calling List '%s'

E53003 v_dialer\dialer\src\utility\copyfields.c %s - Unable to open Prepare Check file '%s'. Must run clhash first.

E53004 v_dialer\dialer\src\utility\copyfields.c %s - Unable to find correct entry for '%s' in Prepare Check file '%s'. Must run clhashin first.

E53005 v_dialer\dialer\src\utility\copyfields.c %s - Field '%s' not in Calling List '%s'

E53006 v_dialer\dialer\src\utility\copyfields.c %s - Unable to open Associated Calling List '%s'

E53007 v_dialer\dialer\src\utility\copyfields.c %s - Unable to stat Associate List '%s'

E53008 v_dialer\dialer\src\utility\copyfields.c %s - Field '%s' not in Associate Calling List '%s'

E53009 v_dialer\dialer\src\utility\copyfields.c %s - Match field '%s' length %d not same as associated field '%s' length %d!

E53010 v_dialer\dialer\src\utility\copyfields.c %d - READ ERROR (%d)

E53011 v_dialer\dialer\src\utility\copyfields.c %s - Record %d - READ ERROR (%d)

E53012 v_dialer\dialer\src\utility\copyfields.c %d - A READ ERR (%d)

E53013 v_dialer\dialer\src\utility\copyfields.c %s - Record %d - ASSOC READ ERROR (%d)

E53014 v_dialer\dialer\src\utility\copyfields.c %d - WRITE ERROR (%d)

E53015 v_dialer\dialer\src\utility\copyfields.c %s - Associate Record %d - WRITE ERROR (%d)

E53016 v_dialer\dialer\src\utility\copyfields.c %d BAD RECORDS

E53017 v_dialer\dialer\src\utility\copyfields.c %s - %d BAD RECORDS

E53018 %s - %d BAD RECORDS

E53019 v_dialer\dialer\src\utility\copyfields.c %s - Unable to open: %s

E53020 v_dialer\dialer\src\utility\copyfields.c %s - Unknown configuration file %s

Page 355: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 353

E53021 v_dialer\dialer\src\utility\copyfields.c %s - Unable to allocate list buffer

E53022 v_dialer\dialer\src\utility\copyfields.c TERMINAL ERROR

E53023 v_dialer\dialer\src\utility\copyfields.c %s - Usage error

E53650 v_dialer\dialer\src\imon\internetmon.c compcode.cfg not found

E53651 v_dialer\dialer\src\imon\internetmon.c INTERNETMONDIR parameter is missing from master.cfg

E53652 v_dialer\dialer\src\imon\internetmon.c Internet Monitor shutting down

E53654 v_dialer\dialer\src\imon\internetmon.c Internet Monitor failed to attach to shared memory - conn_mgr may not be running - exiting

E53655 HTML Page update failed - remote Web server may no longer be mounted

E53800 v_dialer\dialer\src\utility\evmon.c Caught error #%d!

E53801 v_dialer\dialer\src\utility\evmon.c Error %d writing msg '%s' to log file [%s].

E53802 v_dialer\dialer\src\utility\evmon.c Error: Unable to log system message. Message '%s' not found.

E53803 v_dialer\library\libdsi\src\script_lng.c Error: Couldn't open file '%s'

E53804 v_dialer\dialer\src\utility\evmon.c Error formatting message '%s'.

E53805 v_dialer\dialer\src\utility\evmon.c Error: Nothing to monitor!

E53806 v_dialer\dialer\src\utility\evmon.c Error: Unable to open log file %s for appending.

E53807 v_dialer\dialer\src\utility\evmon.c Error: Couldn't open log file [%s]

E53808 v_dialer\library\libdsi\src\script_lng.c Error: Bad date-time format: [%s]

E53809 v_dialer\dialer\src\utility\evmon.c Error: Unable to retrieve EVMON filespec from master.cfg

E53810 v_dialer\dialer\src\utility\evmon.c Error: Config file [%s] was not found.

E53811 v_dialer\dialer\src\utility\evmon.c Error: System call auditing is requested but system is not trusted

Page 356: PC4 Troubleshooting Main

354 Maintenance and Troubleshooting Guide March 2008

E53812 Error: File %s was not found. Make sure system auditing is turned on.

E53813 v_dialer\dialer\src\utility\evmon.c Error: Couldn't stat [%s]

E53814 v_dialer\dialer\src\utility\evmon.c Warning: No 'next' audit log defined.

E53815 v_dialer\dialer\src\utility\evmon.c Error: Bad update interval value

E53816 v_dialer\dialer\src\utility\evmon.c Error: Unknown option %c

E53817 v_dialer\dialer\src\utility\evmon.c Error: Unknown/unimplemented entry in cfg file on line %d

E53818 v_dialer\dialer\src\utility\evmon.c Error: The HP-UX auditing system is OFF. Please use SAM to turn it on.

E53819 v_dialer\dialer\src\utility\evmon.c Error: Audctl failed: errno=%d

E54100 v_dialer\dialer\src\listserver\listserver.c Unexpected program exit

E54101 v_dialer\dialer\src\listserver\listserver.c getservbyname ('%s', tcp) failed

E54102 v_dialer\dialer\src\listserver\listserver.c socket () failed

E54103 v_dialer\dialer\src\listserver\listserver.c bind (fd=%d) failed (are clients still connected to sockets of previous listserver instance?)

E54104 v_dialer\dialer\src\listserver\listserver.c listen (fd=%d) failed

E54105 v_dialer\dialer\src\listserver\listserver.c setsockoopt (fd=%d, SO_LINGER) failed

E54106 v_dialer\dialer\src\listserver\listserver.c setsockoopt (fd=%d, SO_KEEPALIVE) failed

E54107 v_dialer\dialer\src\listserver\listserver.c accept (fd=%d) failed

E54108 Usage error

E54109 v_dialer\dialer\src\listserver\listserver.c Received signal %d -- exiting

E54110 v_dialer\dialer\src\listserver\listserver.c FD_ISSET (conn_fd=%d) failed

E54111 v_dialer\dialer\src\listserver\listserver.c Write error -- exiting

E54112 v_dialer\library\libdsi\src\clutils.c Read error -- exiting

E54113 v_dialer\dialer\src\listserver\listserver.c File descriptor too large (fd=%d) -- exiting

Page 357: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 355

E54114 v_dialer\dialer\src\listserver\listserver.c cllstat (fd=%d) failed -- exiting

E54115 v_dialer\dialer\src\listserver\listserver.c cllrddict (fd=%d) failed -- exiting

E54120 v_dialer\dialer\src\listserver\listserver.cv_dialer\dialer\DialerCmdCtrl\VoicemsgCfgTable.cpp

fork failed -- errno=%d '%s'

E54121 v_dialer\dialer\src\listserver\listserver.c Unable to open list '%s'

E55000 v_dialer\dialer\src\reports\reportgen\reportprn.c

Insufficient memory for %s

E55001 v_dialer\dialer\src\reports\reportgen\reportprn.c

Error reading records

E55002 v_dialer\dialer\src\reports\reportgen\reportprn.c

Failed to open report output file

E55200 v_dialer\dialer\src\reports\reportgen\reportsel.c

Group may not begin with no criteria

E55201 v_dialer\dialer\src\reports\reportgen\reportsel.c

Gap found between select fields

E55202 v_dialer\dialer\src\reports\reportgen\reportsel.c

Invalid logical connector

E55203 v_dialer\dialer\src\reports\reportgen\reportsel.c

Missing field name

E55204 v_dialer\dialer\src\reports\reportgen\reportsel.c

Missing field value

E55205 v_dialer\dialer\src\reports\reportgen\reportsel.c

Duplicate field name found

E55206 v_dialer\dialer\src\reports\reportgen\reportsel.c

Invalid sort directive

E55207 v_dialer\dialer\src\reports\reportgen\reportsel.c

Error Pattern: %s

E55400 v_dialer\dialer\src\reports\reportgen\reportsub.c

Failed to write text substitution file

E55600 v_dialer\dialer\src\reports\reportgen\reportexp.cv_dialer\dialer\src\reports\reportgen\reportsel.cv_dialer\dialer\src\reports\reportgen\reportfmt.cv_dialer\dialer\src\reports\reportgen\reporthlp.c

Invalid number

Page 358: PC4 Troubleshooting Main

356 Maintenance and Troubleshooting Guide March 2008

E55601 v_dialer\dialer\src\reports\reportgen\reportsub.cv_dialer\ivr\src\ivr_supr.c

Insufficient memory for %s

E56001 v_dialer\ivr\src\ivr_supr.c ivr_supr: Error connecting to socket, errno %d

E56002 v_dialer\ivr\src\ivr_supr.c ivr_supr: Unknown command ID:%d

E56003 v_dialer\ivr\src\ivr_supr.c ivr_supr: IVR_INTEGRATION not set in master.cfg

E56004 v_dialer\ivr\src\ivr_config.c Invalid IP address: %s

E56005 v_dialer\ivr\src\ivr_config.c No host information is loaded--%s

E56006 v_dialer\ivr\src\ivr_config.c Error - Failed to load user interface files

E56007 v_dialer\ivr\src\ivr_config.c Validation of IVR information failed

E56008 v_dialer\ivr\src\ivr_config.c Invalid IVR ID length: %s

E56009 v_dialer\ivr\src\ivr_config.c IVR ID not found in /etc/hosts file: %s

E56010 v_dialer\ivr\src\ivr_config.c IVR ID already exists: %s

E56011 v_dialer\ivr\src\ivr_config.c Invalid character in IVR ID: %s

E56012 v_dialer\ivr\src\ivr_config.c An IP address must be entered

E56013 v_dialer\ivr\src\ivr_config.c Fail to add to /etc/hosts: %s

E56014 v_dialer\ivr\src\ivr_config.c IVR ID %s not found

E56015 v_dialer\ivr\src\ivr_config.c Failed to add IVR %s

E56016 v_dialer\ivr\src\ivr_config.c IVR ID already exists in /etc/hosts file: %s

E56017 v_dialer\ivr\src\ivr_config.c Currently connected to IVR %s; cannot change or delete configuration

E56018 v_dialer\ivr\src\ivr_config.c IVR IP address already exists: %s

E56019 v_dialer\ivr\src\ivr_config.c IVR IP address already found in /etc/hosts file: %s

E56020 v_dialer\ivr\src\ivr_conn.c ivr_conn: ivr_conn service not found in /etc/services

Page 359: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 357

E56021 v_dialer\ivr\src\ivr_conn.c ivr_conn: Unable to create socket, errno %d - %s

E56022 v_dialer\ivr\src\ivr_conn.c ivr_conn: Unable to bind to the socket, errno %d

E56023 v_dialer\ivr\src\ivr_conn.c ivr_conn: Unable to connect to the socket, errno %d

E56024 v_dialer\ivr\src\ivr_conn.c ivr_conn: Unable to listen to the socket, errno %d

E56025 v_dialer\ivr\src\ivr_conn.c ivr_conn: Error in select, errno %d

E56026 v_dialer\ivr\src\ivr_conn.c ivr_conn: Error in accept, errno %d

E56027 v_dialer\ivr\src\ivr_conn.c ivr_conn: Error on recv from supervisor socket, errno %d

E56028 v_dialer\ivr\src\ivr_conn.c ivr_conn: Nothing read from supervisor socket, errno %d

E56029 v_dialer\ivr\src\ivr_conn.c ivr_conn: Unknown message '%s:%s' from supervisor socket

E56030 v_dialer\ivr\src\ivr_conn.c ivr_conn: Error on recv from IVR socket, errno %d

E56031 ivr_conn: Nothing read from IVR socket, errno %d

E56032 v_dialer\ivr\src\ivr_conn.c ivr_conn: Unknown message (%c) from IVR socket

E56033 v_dialer\ivr\src\ivr_conn.c ivr_conn: Invalid message (%s) in input IPC queue

E56034 v_dialer\ivr\src\ivr_conn.c ivr_conn: Unable to set socket to FIOASYNC, errno %d

E56035 v_dialer\ivr\src\ivr_conn.c ivr_conn: Unable to set socket to FIOSNBIO, errno %d

E56036 v_dialer\ivr\src\ivr_conn.c ivr_conn: Unable to set process to receive SIGIO, errno %d

E56037 v_dialer\ivr\src\ivr_conn_io.c ivr_conn: Send error, client %d (still trying)

E56038 v_dialer\ivr\src\ivr_conn_io.c ivr_conn: Send error, client %d (giving up)

E56039 v_dialer\ivr\src\ivr_conn_io.c : err=%d sent=%d rem=%d dt=%d try=%d

Page 360: PC4 Troubleshooting Main

358 Maintenance and Troubleshooting Guide March 2008

E56040 v_dialer\ivr\src\ivr_conn_io.c ivr_conn: Error in select in MicroSleep, errno %d

E56041 v_dialer\ivr\src\ivr_conn_io.c ivr_conn: Fail to write to pipe - sd %d

E56042 v_dialer\ivr\src\ivr_conn_io.c ivr_conn: Caught signal %d, err %d

E56043 v_dialer\ivr\src\ivr_conn_io.c ivr_conn: sigaction failed in InitSigHandlers

E56044 v_dialer\ivr\src\ivr_conn.c ivr_conn: IVR pool job '%s' does not exist

E56045 v_dialer\ivr\src\ivr_conn.c ivr_conn: Error in trying to access IVR pool job '%s'; errno = %d

E56046 v_dialer\ivr\src\ivr_conn.c ivr_conn: Already connected to IVR '%s'

E56047 v_dialer\ivr\src\ivr_conn.c ivr_conn: Not connected to IVR '%s'

E56048 v_dialer\ivr\src\ivr_conn.c ivr_conn: Still connected to IVR '%s'

E56049 v_dialer\ivr\src\ivr_conn.c ivr_conn: Reset of IVR '%s' in progress, please wait...

E57000 v_dailer\dialer\dispatcher\dunupinit.c Dispatcher startup soe_init error: %d

E57001 v_dailer\dialer\dispatcher\dunupinit.c Dispatcher startup invalid argument count: %d

E57002 v_dialer\dialer\src\core\ao_recall.cv_dialer\dialer\src\core\agent_time_util.cv_dialer\dialer\src\core\operator.cv_dailer\dialer\dispatcher\dunupinit.cv_dialer\dialer\src\swif\exec\opmon.c

Linked list insert error: %d for list: %s

E57003 Linked list create error: %d for list: %s

E57004 v_dailer\dialer\dispatcher\dunupinit.c Unable to find opmon IPC

E57005 v_dailer\dialer\dispatcher\dunupinit.c Unable to create dispatcher mailbox <%s>, error: %d

E57006 v_dailer\dialer\dispatcher\dunupinit.c Cleaning up received fatal signal: %d

Page 361: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 359

E57007 v_dailer\dialer\dispatcher\dunupinit.c Error: %d deleting dispatcher mailbox

E57008 v_dailer\dialer\dispatcher\dunupinit.cv_dailer\dialer\dispatcher\mp_change_groupid.cv_dailer\dialer\dispatcher\pa_acd_perm.cv_dailer\dialer\dispatcher\snd_agt_msg.cv_dailer\dialer\dispatcher\gateway.c

Send message error: %d <%s>

E57009 v_dailer\dialer\dispatcher\ap_aborting.cv_dailer\dialer\dispatcher\ap_acquiring.cv_dailer\dialer\dispatcher\ap_prereleasing.cv_dailer\dialer\dispatcher\ap_releasing.cv_dailer\dialer\dispatcher\dunupinit.cv_dailer\dialer\dispatcher\mp_change_groupid.cv_dailer\dialer\dispatcher\mp_job_set.cv_dailer\dialer\dispatcher\pa_acd_perm.cv_dailer\dialer\dispatcher\snd_agt_msg.cv_dailer\dialer\dispatcher\dunup.cv_dailer\dialer\dispatcher\gateway.c

Error trying to malloc space: <%s>

E57010 v_dailer\dialer\dispatcher\dunupinit.cv_dailer\dialer\dispatcher\mp_login.c

Error opening file: <%s>

E57011 v_dailer\dialer\dispatcher\dunup.c Unexpected object: %d msgtype: %d from md: %d

E57012 v_dailer\dialer\dispatcher\dunup.c Invalid msgtype: %d from md: %d

E57013 v_dailer\dialer\dispatcher\dunup.c Receive message error: %d

E57014 v_dailer\dialer\dispatcher\action_processor.c

Unknown mode %s: %d

Page 362: PC4 Troubleshooting Main

360 Maintenance and Troubleshooting Guide March 2008

E57015 v_dailer\dialer\dispatcher\du_format.cv_dailer\dialer\dispatcher\mp_genrel_query.cv_dailer\dialer\dispatcher\mp_op_headset_state.cv_dailer\dialer\dispatcher\mp_op_link_failure.cv_dailer\dialer\dispatcher\mp_response.c

Attribute not found: %d

E57016 v_dialer\dialer\src\core\ao_recall.cv_dialer\dialer\src\core\agent_time_util.cv_dialer\dialer\src\core\operator.cv_dailer\dialer\dispatcher\dunupinit.cv_dailer\dialer\dispatcher\genrel_util.cv_dailer\dialer\dispatcher\mp_acquire_op.cv_dailer\dialer\dispatcher\mp_call_connect.cv_dailer\dialer\dispatcher\mp_login.cv_dialer\dialer\src\swif\exec\opmon.c

Linked list queuing error: %s

E57017 v_dailer\dialer\dispatcher\dunuputil.c Invalid mailbox: %s

E57018 v_dailer\dialer\dispatcher\event_processor.cv_dailer\dialer\dispatcher\mp_call_event.c

Invalid event: %d %s

E57019 v_dailer\dialer\dispatcher\gateway.cv_dialer\dialer\src\swif\exec\ServMonMsg.cpp

Unable to register to mailbox <%s>, error: %d

E57020 v_dailer\dialer\dispatcher\mp_acquire_op.c

Duplicate acquire request on vdn <%s>

E57021 v_dailer\dialer\dispatcher\mp_acquire_op.c

Not enough licenses - Max acquire agents: %d

Page 363: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 361

E57022 v_dailer\dialer\dispatcher\mp_call_connect.cv_dailer\dialer\dispatcher\mp_call_event.cv_dailer\dialer\dispatcher\mp_change_groupid.cv_dailer\dialer\dispatcher\mp_create_call.cv_dailer\dialer\dispatcher\mp_domain_action.cv_dailer\dialer\dispatcher\mp_job_set.cv_dailer\dialer\dispatcher\mp_login.cv_dailer\dialer\dispatcher\mp_logout.cv_dailer\dialer\dispatcher\mp_trunk_release.cv_dailer\dialer\dispatcher\mp_user_action.c

Invalid attribute: %d %s

E57023 Unexpected call connect for call_id: %d

E57024 v_dailer\dialer\dispatcher\mp_call_made.c

Unexpected call made to vdn: <%s> scai_link: %d

E57025 v_dailer\dialer\dispatcher\mp_response.c

Call reject error: %d for call_id: %d

E57026 v_dailer\dialer\dispatcher\mp_call_reject.cv_dailer\dialer\dispatcher\mp_job_set.c

Invalid job id: %d

E57027 v_dailer\dialer\dispatcher\mp_create_call.c

Unexpected create call for call_req_id: %d

E57028 v_dailer\dialer\dispatcher\mp_domain_action.cv_dailer\dialer\dispatcher\mp_user_action.c

Invalid action: %d %s

E57029 v_dailer\dialer\dispatcher\mp_job_set.c Invalid process state: %d %s

E57030 v_dailer\dialer\dispatcher\mp_login.c Extension <%s> is already in use by user: %d

E57031 v_dailer\dialer\dispatcher\mp_response.c

Error: %d as a response to: <%s> message

E57032 v_dailer\dialer\dispatcher\mp_response.c

Unknown resp_type event: %d

Page 364: PC4 Troubleshooting Main

362 Maintenance and Troubleshooting Guide March 2008

E57033 v_dailer\dialer\dispatcher\mp_response.c

Unexpected response objid: %d, invokeid: %d

E57034 v_dialer\dialer\src\core\agent_misc_util.cv_dailer\dialer\dispatcher\mp_timeout.c

Process <%s> not responding to msg: <%s>

E57035 v_dialer\dialer\src\core\ao_recall.cv_dialer\dialer\src\core\agent_time_util.cv_dailer\dialer\dispatcher\mp_timeout.c

Get time error: <%d>, will try again

E57036 v_dialer\dialer\src\core\ao_recall.cv_dialer\dialer\src\core\agent_time_util.cv_dailer\dialer\dispatcher\mp_timeout.c

Invalid timeout event: <%d>

E57037 Voice message not defined: <%d>

E57038 v_dailer\dialer\dispatcher\mp_login.c Extension <%s> scai_link: %d is not installed

E57039 v_dailer\dialer\dispatcher\mp_call_connect.c

Expected timeout <%s> not found, call_id: <%d>

E57040 v_dailer\dialer\dispatcher\mp_call_made.c

Expected timeout <%s> not found, vdn: <%s>

E57041 v_dailer\dialer\dispatcher\mp_release.c Release of pbx ext <%s> which is not fully acquired

E57042 v_dailer\dialer\dispatcher\mp_login.c User id %d was already in use

E57043 v_dailer\dialer\dispatcher\mp_user_action.c

User ext <%s> scai_link <%d> is not found

E57044 v_dailer\dialer\dispatcher\dunupinit.c Unable to read acd_license.cfg, error: <%d>

E58002 v_dialer\dialer\src\core\agent.cv_dialer\dialer\src\core\caller.cv_dialer\dialer\src\core\operator.cv_dialer\dialer\src\reports\history\datamgr_init.cppv_dialer\dialer\src\swif\exec\ServMonMsg.cppv_dialer\dialer\services\srcEventServer.cppv_dialer\dialer\src\swif\exec\opmon.cv_dialer\dialer\src\core\porter.c

%s - Unable to initialize soe (%d)

E59500 v_dialer\dialer\src\core\jobctrl.c Job %s not currently running.

Page 365: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 363

E59501 dialer/src/core/jobctrl.cdialerCmdctrl\HeadsetLib.cpp

Illegal parameters: %s

E59502 Job %s not ready.

E59503 v_dialer\dialer\src\core\jobctrl.c Job name not specified: %s

E59505 v_dialer\dialer\src\core\jobctrl.c Job(%s) not linkable

E59506 v_dialer\dialer\src\core\jobctrl.c Malloc failure in list_agents

E59507 v_dialer\dialer\src\core\jobctrl.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Inbound capable jobs only: %s

E59508 v_dialer\dialer\src\core\jobctrl.c Outbound capable jobs only: %s

E59508 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Monitoring of operator disabled

E59509 v_dialer\dialer\src\core\jobctrl.c Monitoring of operator disabled

E59510 v_dialer\dialer\src\core\jobctrl.c Error, no operator %s on job %s

E59511 v_dialer\dialer\src\core\jobctrl.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Managed dialing capable jobs only: %s

E59512 v_dialer\dialer\src\core\jobctrl.c Illegal time zone: %s

E59513 v_dialer\dialer\src\core\jobctrl.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Illegal action %s

E59514 v_dialer\dialer\src\core\jobctrl.c Inbound capable jobs only

E59516 v_dialer\dialer\src\core\jobctrl.c Outbound capable jobs only

E59517 v_dialer\dialer\src\core\jobctrl.c Managed dialing capable jobs only

E59518 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Illegal time zone name %c

E59519 v_dialer\dialer\src\core\api_jobctl.cv_dialer\dialer\src\core\jobctrl.c

Unable to open transfer lock file %s

E59520 v_dialer\dialer\src\core\jobctrl.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Not a multi-unit job: %s

Page 366: PC4 Troubleshooting Main

364 Maintenance and Troubleshooting Guide March 2008

E59521 v_dialer\dialer\src\core\jobctrl.cv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

No units currently available

E59522 dialer/src/core/jobctrl.cdialerCmdctrl\CJobTableSO.cpp

Illegal units %s

E59527 v_dialer\dialer\src\core\jobctrl.c Job name not specified

E59528 v_dialer\dialer\src\core\jobctrl.c Job linking capable jobs only

E59530 v_dialer\dialer\src\core\jobctrl.c Job not currently linked

E59531 Invalid port for monitoring agents

E59533 v_dialer\dialer\src\core\jobctrl.c Warning: Operator already being transferred.

E59534 v_dialer\dialer\src\core\jobctrl.c Job1 %s not ready.

E59535 v_dialer\dialer\src\core\jobctrl.c Job2 %s not ready.

E59539 v_dialer\dialer\src\core\jobctrl.c Illegal change %s

E59540 v_dialer\dialer\src\core\jobctrl.cv_dialer\dialer\DialerCmdCtrl\HeadsetLib.cpp

Headset ID (%s) already in use

E59541 v_dialer\dialer\src\core\jobctrl.cv_dialer\dialer\DialerCmdCtrl\HeadsetLib.cpp

No more headsets permitted on system

E59542 v_dialer\dialer\src\core\jobctrl.cv_dialer\dialer\DialerCmdCtrl\HeadsetLib.cpp

Failure to access headset table

E59596 v_dialer\dialer\src\core\jobctrl.c No operator slot available

E59597 v_dialer\dialer\src\core\jobctrl.c System is not running

E59598 v_dialer\dialer\src\core\jobctrl.c Illegal parameters

E59599 v_dialer\dialer\src\core\jobctrl.c Bad command

E59600 v_dialer\dialer\src\core\jobctrl.c Not a Cruise Control job

E61000 midtier\unixdev\CmdCtrl\src\DialerCfgClient.cpp

%s failed: Exception %s; Id %ul

Page 367: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 365

E61001 midtier\unixdev\RealTimeDataServer\src\RTRMmain.cppmidtier\unixdevv_dialer\dialer\services\src\Init.cppv_dialer\dialer\services\srcEventServiceIF_i.cppmidtier\unixdev\CmdCtrl\src\DialerCfgClient.cppmidtier\unixdev\Logger\src\LoggingServer_i.cppmidtier\unixdev\ServiceActivation\src\ServiceActivatingIFImpl.cxxmidtier\unixdev\ServiceMonitor\src\ServiceMonitor_ServiceMonitoringIFImpl.cxxmidtier\unixdevv_dialer\dialer\services\src\DialerEventServerIF_i.cppmidtier\unixdevv_dialer\dialer\services\src\EventClient.cppmidtier\unixdevv_dialer\dialer\services\src\EventServer.cppmidtier\unixdevv_dialer\dialer\services\src\EventServiceIF_i.cppmidtier\unixdev\SysHealth\src\SystemHealthEntryImpl.cppv_dialer\dialer\DialerServiceActivation\src\DSAServiceIFImpl.cxx\DSHdialerSystemHealthEntryImpl.cppv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitoringIFImpl.cxx

Exception raised: %s

E61002 midtier\unixdevv_dialer\dialer\services\src\EventServiceIF_i.cppv_dialer\dialer\services\srcEventServiceIF_i.cpp

Failed to create thread

Page 368: PC4 Troubleshooting Main

366 Maintenance and Troubleshooting Guide March 2008

E61003 midtier\unixdev\CmdCtrl\src\DialerCfgClient.cppmidtier\unixdev\RealTimeDataServer\src\RTRMmain.cppmidtier\unixdevv_dialer\dialer\services\src\EventClient.cppmidtier\unixdevv_dialer\dialer\services\src\EventServer.cppmidtier\unixdevv_dialer\dialer\services\src\EventServiceIF_i.cppmidtier\unixdevv_dialer\dialer\services\src\Init.cppv_dialer\dialer\services\srcEventServiceIF_i.cpp

Caught unknown exception

E61004 midtier\unixdev\services\src\Init.cpp Failed to write to IOR file %s

E61005 midtier\unixdev\services\src\Init.cpp Failed to initialize signal handlers

E61006 midtier\unixdev\services\src\Init.cpp Failed to initialize %d

E61007 midtier\unixdev\services\src\EventServer.cpp

attach_datashm () failed -- is system up?

E61008 midtier\unixdev\services\src\ShmDataReader.cpp

Number of line pools defined in LINEASSIGN in master.cfg (%d) exceeds value of MAX_LINEASSIGN_LABELS (%d)

E61009 Exceeded max limit of inactive jobs (%d); skipping the rest

E61040 midtier\unixdev\services\src\Init.cpp CosNaming NamingContext not found

E61041 midtier\unixdev\services\src\Init.cpp CosNaming NamingContext cannot proceed

E61042 midtier\unixdev\services\src\Init.cpp CosNaming NamingContext invalid name

E61043 midtier\unixdev\services\src\Init.cpp CosNaming NamingContext already bound

E62000 v_dialer\dialer\DialerCmdCtrl\src\CmdCtrl_Table_i.cpp

(%s): Operation %s is not implemented

E62001 dialer\Cmdctrl\CCompcodeTableSO.cppv_dialer\dialer\DialerCmdCtrl\CConfigTableSO.cpp

(%s): Operation %s is not applicable to object %s

Page 369: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 367

E62002 v_dialer\dialer\DialerCmdCtrl\AgentLib.cppv_dialer\dialer\DialerCmdCtrl\CTableSO.cppv_dialer\dialer\DialerCmdCtrl\FileTable.cpp

(%s): Requested column %s not available in table %s

E62003 v_dialer\dialer\DialerCmdCtrl\AgentLib.cpp

(%s): Invalid predicate expression %s: %s

E62004 v_dialer\dialer\DialerCmdCtrl\AgentLib.cppv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\dialer\DialerCmdCtrl\CSelIndexTableSO.cppv_dialer\dialer\DialerCmdCtrl\FileTable.cppv_dialer\dialer\DialerCmdCtrl\SelData.cppv_dialer\dialer\DialerCmdCtrl\StratData.cpp

(%s): Invalid column name %s in predicate expression

E62005 v_dialer\dialer\DialerCmdCtrl\CCallSelTableSO.cppv_dialer\dialer\DialerCmdCtrl\CCallStratTableSO.cppv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\dialer\DialerCmdCtrl\CompcodeTable.cppv_dialer\dialer\DialerCmdCtrl\RecordLock.cppv_dialer\dialer\DialerCmdCtrl\RecordLock_utest.cpp

(%s): Record %s is locked by owner %s

E62006 v_dialer\dialer\DialerCmdCtrl\RecordLock.cpp

(add_lock): failed for Record %s Owner %s

E62007 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\dialer\DialerCmdCtrl\RecordLock.cpp

(%s): lock for Record %s Owner %s is no longer valid

Page 370: PC4 Troubleshooting Main

368 Maintenance and Troubleshooting Guide March 2008

E62008 v_dialer\dialer\DialerCmdCtrl\CompcodeData.cppv_dialer\dialer\DialerCmdCtrl\JobData.cppv_dialer\dialer\DialerCmdCtrl\PromptData.cppv_dialer\dialer\DialerCmdCtrl\SelData.cppv_dialer\dialer\DialerCmdCtrl\StratData.cpp

(%s): internal error - no data

E62009 v_dialer\dialer\DialerCmdCtrl\CompcodeData.cpp

(%s): no values for input

E62010 v_dialer\dialer\DialerCmdCtrl\CAgentTableSO.cppv_dialer\dialer\DialerCmdCtrl\CCallListTableSO.cppv_dialer\dialer\DialerCmdCtrl\CCallStratTableSO.cppv_dialer\dialer\DialerCmdCtrl\CConfigTableSO.cppv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\dialer\DialerCmdCtrl\CLineGrpTableSO.cppv_dialer\dialer\DialerCmdCtrl\CSelIndexTableSO.cppv_dialer\dialer\DialerCmdCtrl\CTelephnySpt.cpp

(%s): Operation %s requires %s

E62011 v_dialer\dialer\DialerCmdCtrl\CConfigTableSO.cppv_dialer\dialer\DialerCmdCtrl\CLineGrpTableSO.cppv_dialer\dialer\DialerCmdCtrl\CodeDescTable.cppv_dialer\dialer\DialerCmdCtrl\CSelIndexTableSO.cppv_dialer\dialer\DialerCmdCtrl\CTelephnySpt.cppv_dialer\dialer\DialerCmdCtrl\TelephnyTable.cppv_dialer\dialer\DialerCmdCtrl\VoicemsgCfgTable.cpp

(%s): Operation %s: Invalid parameters

Page 371: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 369

E62012 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\dialer\DialerCmdCtrl\RecordLock.cpp

(%s): Record %s is not locked by owner %s, current owner is %s

E62013 v_dialer\dialer\DialerCmdCtrl\AgentLib.cppv_dialer\dialer\DialerCmdCtrl\CCompcodeTableSO.cppv_dialer\dialer\DialerCmdCtrl\FileTable.cpp

(%s): Requested row %s not available in table %s

E62014 v_dialer\dialer\DialerCmdCtrl\FileAccess.cpp

Unable to create file %s, errno = %d

E62015 v_dialer\dialer\DialerCmdCtrl\FileAccess.cpp

Unable to open file %s for read/write, errno = %d

E62016 v_dialer\dialer\DialerCmdCtrl\FileAccess.cpp

Unable to open file %s for update, errno = %d

E62017 v_dialer\dialer\DialerCmdCtrl\FileAccess.cpp

Unable to open file %s for readonly, errno = %d

E62018 v_dialer\dialer\DialerCmdCtrl\FileAccess.cpp

Unable to delete file %s, errno = %d

E62019 v_dialer\dialer\DialerCmdCtrl\FileAccess.cpp

Unable to create file %s, file already exists

Page 372: PC4 Troubleshooting Main

370 Maintenance and Troubleshooting Guide March 2008

E62020 v_dialer\dialer\DialerCmdCtrl\CrudulMethods.cppv_dialer\dialer\DialerCmdCtrl_Agent_i.cppv_dialer\dialer\DialerCmdCtrl_CallSelect_i.cppv_dialer\dialer\DialerCmdCtrlv_dialer\dialer\DialerCmdCtrl_CallStrategy_i.cppv_dialer\dialer\DialerCmdCtrlv_dialer\dialer\DialerCmdCtrl_Compcode_i.cppv_dialer\dialer\DialerCmdCtrl_Config_i.cppv_dialer\dialer\DialerCmdCtrl_DialerControl_i.cppv_dialer\dialer\DialerCmdCtrl_Domain_i.cppv_dialer\dialer\DialerCmdCtrl_Headset_i.cppv_dialer\dialer\DialerCmdCtrl_Ivr_i.cppv_dialer\dialer\DialerCmdCtrl_Job_i.cppv_dialer\dialer\DialerCmdCtrl_SelectIndex_i.cppv_dialer\dialer\DialerCmdCtrl_TableFactory_i.cpp

General Exception - Table: %s Method: %s

E62021 v_dialer\dialer\DialerCmdCtrl\FileAccess.cpp

File %s does not exist, errno = %d

E62022 v_dialer\dialer\DialerCmdCtrl\CCallSelTableSO.cppv_dialer\dialer\DialerCmdCtrl\CCallStratTableSO.cppv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

(%s): Operation %s requires Record ID as one of the query conditions

E62023 v_dialer\dialer\DialerCmdCtrl_TableFactory_i.cpp

Incorrect Table Type

Page 373: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 371

E62024 v_dialer\dialer\DialerCmdCtrl\CCallSelTableSO.cppv_dialer\dialer\DialerCmdCtrl\CCallStratTableSO.cppv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\dialer\DialerCmdCtrl\CompcodeTable.cppv_dialer\dialer\DialerCmdCtrl\CTelephnySpt.cppv_dialer\dialer\DialerCmdCtrl\MasterCfgTable.cppv_dialer\dialer\DialerCmdCtrl\TelephnyTable.cppv_dialer\dialer\DialerCmdCtrl\VoicemsgCfgTable.cpp

(%s): lock_record - Unknown locktype %s

E62025 v_dialer\library\libutil++\src\account_r. (%s) [%#x] : %s(): Error %#x [%s] %s occurred

E62026 v_dialer\library\libutil++\src\account_r. (%s) [%#x] : %s(): Error %#x %s occurred\n

Page 374: PC4 Troubleshooting Main

372 Maintenance and Troubleshooting Guide March 2008

E62027 v_dialer\dialer\DialerCmdCtrl\CrudulMethods.cppv_dialer\dialer\DialerCmdCtrl_Agent_i.cppv_dialer\dialer\DialerCmdCtrl_Blend_i.cppv_dialer\dialer\DialerCmdCtrl_CallSelect_i.cppv_dialer\dialer\DialerCmdCtrl_CallStrategy_i.cppv_dialer\dialer\DialerCmdCtrl_Compcode_i.cppv_dialer\dialer\DialerCmdCtrl_Config_i.cppv_dialer\dialer\DialerCmdCtrl_DialerControl_i.cppv_dialer\dialer\DialerCmdCtrl_Domain_i.cppv_dialer\dialer\DialerCmdCtrl_Headset_i.cppv_dialer\dialer\DialerCmdCtrl_Ivr_i.cppv_dialer\dialer\DialerCmdCtrl_Job_i.cppv_dialer\dialer\DialerCmdCtrl_SelectIndex_i.cppv_dialer\dialer\DialerCmdCtrl_TableFactory_i.cpp

Platform Exception - Table: %s Method: %s

E62028 %s - Error allocating memory

E62029 v_dialer\dialer\DialerCmdCtrl\MsgQueue.cpp

(%s): Invalid Message Queue handle

E62030 v_dialer\dialer\DialerCmdCtrl\CAgentTableSO.cpp

(%s): Invalid agent name

E62031 v_dialer\dialer\DialerCmdCtrl\CAgentTableSO.cpp

(%s): Invalid headset ID

E62032 v_dialer\dialer\DialerCmdCtrl\AgentShmLib_utest.cppv_dialer\dialer\DialerCmdCtrl\CAgentTableSO.cppv_dialer\dialer\DialerCmdCtrl\CCompcodeTableSO.cpp

(%s): Failed to connect to shared memory

E62033 v_dialer\dialer\DialerCmdCtrl\ShmAccess.cpp

(%s): Failed to connect to agent %s shared memory

E62034 (%s): Agent %s is not active

Page 375: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 373

E62035 v_dialer\dialer\DialerCmdCtrl\AgentShmLib.cpp

(%s): Agent %s is already monitored by line %d

E62036 v_dialer\dialer\DialerCmdCtrl\AgentShmLib.cppv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

(%s): Failed to get IPC key for job: %s

E62037 v_dialer\dialer\DialerCmdCtrl\AgentShmLib.cpp

(%s): Failed to open IPC for %s

E62038 v_dialer\dialer\DialerCmdCtrl\CAgentTableSO.cpp

(%s): Invalid message to notify agent(s)

E62039 v_dialer\dialer\DialerCmdCtrl\AgentShmLib_utest.cppv_dialer\dialer\DialerCmdCtrl\CAgentTableSO.cpp

(%s): Failed to connect to job %s shared memory

E62040 v_dialer\dialer\DialerCmdCtrl\RecordLock.cpp

Lock expired for Record: %s, Owner: %s

E62041 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Unable to fill required field %s for Job %s

E62042 v_dialer\library\libcallsel\src\cllcallsel.cpp

(%s): Selection Index Failure: Could not verify selection %s with list %s. Run Verify Selection to find specific errors.

E62043 v_dialer\dialer\DialerCmdCtrl\AgentShmLib.cpp

(%s): Invalid agent name selection pattern '%s'

E62044 v_dialer\library\libcallsel\src\cllcallsel.cpp

(%s): Selection Index Failure: Could not verify strategy %s with list %s. Run Verify Strategy to find specific errors.

E62045 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

(%s): Shared memory object not associated with job: %s

E62046 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Invalid parameters for setting %s

E62047 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Number of Call Strategy Control items requested is greater than allowed on system

E62048 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Requested value less than minimum value.

Page 376: PC4 Troubleshooting Main

374 Maintenance and Troubleshooting Guide March 2008

E62049 dialerclient\Redwood\VBApps\Editor\MDIForm1.frmv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Unable to start job - job file in use by character user interface.

E62050 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppdialerclient\Redwood\VBApps\Editor\MDIForm1.frm

Unable to start job - lock on file failed.

E62051 dialerclient\Redwood\VBApps\Editor\MDIForm1.frmdialerclient\Redwood\VBApps\Editor\Modules\General.bas

Unable to start job - job file in use by %s

E62052 v_dialer\dialer\DialerCmdCtrl\CCallSelTableSO.cppv_dialer\dialer\DialerCmdCtrl\CCallStratTableSO.cppv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\dialer\DialerCmdCtrl\RecordLock.cppv_dialer\dialer\DialerCmdCtrl\CompcodeTable.cpp

File %s in use by character user interface.

E62053 v_dialer\dialer\DialerCmdCtrl\CCallSelTableSO.cppv_dialer\dialer\DialerCmdCtrl\CCallStratTableSO.cppv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\dialer\DialerCmdCtrl\CompcodeTable.cppv_dialer\dialer\DialerCmdCtrl\RecordLock.cpp

Lock on file failed.

E62054 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

No response from Job Starter for %s

E62055 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Invalid response from Job Starter for %s

E62056 Failed check for required fields due to lock on job file

E62057 v_dialer\dialer\DialerCmdCtrl\CSelIndexTableSO.cpp

(%s): Invalid index process handle

E62058 v_dialer\dialer\DialerCmdCtrl\CSelIndexTableSO.cpp

(%s): Unable to locate status for calling index process handle '%s'

Page 377: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 375

E62059 v_dialer\dialer\DialerCmdCtrl\AgentShmLib.cpp

(%s): Failed to send a notification to agent %s

E62060 v_dialer\dialer\DialerCmdCtrl\CCallSelTableSO.cppv_dialer\dialer\DialerCmdCtrl\CCallStratTableSO.cppv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cpp

Invalid file name: %s

E62061 v_dialer\dialer\DialerCmdCtrl\CSelIndexTableSO.cpp

(%s): Communication with remote list server failed when processing %s calling list and %s calling selection

E62062 v_dialer\library\libcallsel\src\CallStgyLib.cpp

(%s): Invalid Next Phone definition from phone %s to phone %s that creates infinite loop

E62070 v_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cppv_dialer\dialer\DialerCmdCtrl\SptSyntaxErrorRe.cpp

%s(%d): Syntax error: %s

E62071 v_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cppv_dialer\dialer\DialerCmdCtrl\SptSyntaxErrorRe.cpp

%s(%d): Error in command '%s': %s

E62072 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

Unknown variable name '%s'

E62073 v_dialer\dialer\DialerCmdCtrl\CTelephnySpt.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

Unexpected error in script definition

E62074 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

Total number of lines %d exceeds maximum allowed (must be %d or less)

E62075 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

Invalid field name '%s'

Page 378: PC4 Troubleshooting Main

376 Maintenance and Troubleshooting Guide March 2008

E62076 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

Invalid number of days %d

E62077 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

Invalid number of hours %d

E62078 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

Invalid number of minutes %d

E62079 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

Invalid audio message ID value %d

E62080 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

Invalid time interval value %d

E62081 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

Invalid relational operator '%s'

E62082 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

Invalid completion code keyword '%s'

E62083 v_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cppv_dialer\dialer\DialerCmdCtrl\XmlBase.cpp

(%s): Failed to initialize XML processor: %s

E62084 v_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cppv_dialer\dialer\DialerCmdCtrl\XmlBase.cpp

(%s): Failed to terminate XML processor: %s

E62085 v_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cppv_dialer\dialer\DialerCmdCtrl\XmlBase.cpp

(%s): Failed to initialize XSLT processor: %s

Page 379: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 377

E62086 v_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cppv_dialer\dialer\DialerCmdCtrl\XmlBase.cpp

(%s): Failed to terminate XSLT processor: %s

E62087 v_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cppv_dialer\dialer\DialerCmdCtrl\SptTransform.cpp

(%s): XML processing failed: %s

E62088 v_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cppv_dialer\dialer\DialerCmdCtrl\SptTransform.cpp

(%s): XML/DOM processing failed

E62089 v_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cppv_dialer\dialer\DialerCmdCtrl\SptTransform.cpp

(%s): XSLT processing failed: %s

E62090 v_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cppv_dialer\dialer\DialerCmdCtrl\XmlDomErrorHandler.cpp

Invalid element '%s'

E62091 v_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cppv_dialer\dialer\DialerCmdCtrl\XsltBase.cpp

(%s): Failed to compile XSLT stylesheet '%s'

E62092 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

Invalid label length '%s' (must be %d bytes or less)

E62093 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

Referenced label '%s' not defined

E62094 v_dialer\dialer\DialerCmdCtrl\SptParserApi.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

Command '%s' malformed

E62095 v_dialer\dialer\DialerCmdCtrl\CTelephnySpt.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

(%s) Operation %s:%s failed during validation

Page 380: PC4 Troubleshooting Main

378 Maintenance and Troubleshooting Guide March 2008

E62096 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cppv_dialer\dialer\DialerCmdCtrl\SptProcessor_utest.cpp

Duplicate label '%s' definition (first definition found in file %s, line %d)

E62097 v_dialer\dialer\DialerCmdCtrl\FileAccess.cpp

File not open

E62098 v_dialer\dialer\DialerCmdCtrl\FileAccess.cpp

Unable to seek to beginning of file

E62099 v_dialer\dialer\DialerCmdCtrl\DccsAudioFileValidator.cpp

File %s is not a valid audio message file

E62100 v_dialer\dialer\DialerCmdCtrl\DccsAudioFileValidator.cpp

Combined size of audio messages of %d kB (approx. %02d:%02d minutes) exceeds the total storage capacity %d kB (approx. %02d:%02d minutes) on PG230 board

E62101 v_dialer\dialer\DialerCmdCtrl\DccsAudioFileValidator.cpp

Total number of audio messages %d exceeds the limit of %d messages

E62102 v_dialer\dialer\DialerCmdCtrl\DccsAudioFileValidator.cpp

Referenced %s audio message not available on the system

E62103 v_dialer\dialer\DialerCmdCtrl\DccsAudioFileValidator.cpp

Audio message ID %d exceeds the the limit of highest ID value %d

E62104 v_dialer\dialer\DialerCmdCtrl\DccsAudioFileValidator.cpp

Using a reserved audio message ID %d

E62105 v_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cpp

Invalid attribute keyword '%s'

E62106 v_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\dialer\DialerCmdCtrl\DccsSptValidator.cpp

Invalid attribute value '%s' for keyword '%s'

E62107 Cannot start monitor agent '%s' audio when on a shadow job

E62108 Cannot stop monitor agent '%s' audio when on a shadow job

E62109 v_dialer\dialer\DialerCmdCtrl\AgentShmLib.cpp

Cannot send a message to '%s' agent when on a shadow job

E62110 Cannot remove an agent '%s' when on a shadow job

Page 381: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 379

E62111 Cannot start monitor agent '%s' audio when on a shadow job

E62112 v_dialer\dialer\DialerCmdCtrl\CCallSelTableSO.cppv_dialer\dialer\DialerCmdCtrl\CCallStratTableSO.cppv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\dialer\DialerCmdCtrl\RecordLock.cppv_dialer\dialer\DialerCmdCtrl\RecordLock_utest.cpp

Record is already locked by current user '%s'

E62113 v_dialer\dialer\DialerCmdCtrl\CCallSelTableSO.cppv_dialer\dialer\DialerCmdCtrl\CCallStratTableSO.cppv_dialer\dialer\DialerCmdCtrl\CJobTableSO.cppv_dialer\dialer\DialerCmdCtrl\RecordLock.cpp

Record is not locked. Current user '%s'

E62114 Unknown lock state. Current user '%s'

E63000 midtier\unixdev\CmdCtrl\src\CCTable.cppmidtier\unixdev\CmdCtrl\src\CmdCtrlImpl.cpp

Unable to send a message to Dialer: %s Object: %s

E66666 v_dialer\dialer\src\core\agent.c

E70000 v_dialer\dialer\src\core\agent_io_util.c Incorrect number of arguments

E70001 v_dialer\dialer\src\core\agent_io_util.c Incorrect message type

E70002 v_dialer\dialer\src\core\agent_time_util.c Timed out waiting for %s

E70003 v_dialer\dialer\src\core\agent_misc_util.c

Incorrect job type

E70004 v_dialer\dialer\src\core\agent_misc_util.cv_dialer\dialer\src\core\agent_sys_util.c

Command failed

E70005 v_dialer\dialer\src\core\agent_io_util.c Incoming command exceeded maximum buffer size

E70006 v_dialer\dialer\src\core\agent.c Must select unit

E70007 v_dialer\dialer\src\core\agent_tdss_util.c Cannot transfer inbound call

Page 382: PC4 Troubleshooting Main

380 Maintenance and Troubleshooting Guide March 2008

E70008 v_dialer\dialer\src\core\agent_tdss_util.c Must specify transfer job

E70009 v_dialer\dialer\src\core\agent_tdss_util.c Unable to send message to %s

E70010 v_dialer\dialer\src\core\agent_tdss_util.c Conference in progress

E70011 v_dialer\dialer\src\core\agent_hs_util.c Call blending is not available

E70012 v_dialer\dialer\src\core\agent_misc_util.c

Password has expired

E70013 v_dialer\dialer\src\core\agent_misc_util.c

Password can not be changed, change limit not expired

E70014 Password can not be changed, password file locked

E70015 v_dialer\dialer\src\core\agent_misc_util.c

Unable to become root privilege for setting password

E70016 v_dialer\dialer\src\core\agent_misc_util.c

Original password is invalid

E70017 v_dialer\dialer\src\core\agent_misc_util.c

New password entered is invalid

E70018 v_dialer\dialer\src\core\agent.c IVR_SCRIPT is blank in job %s

E70019 v_dialer\dialer\src\core\agent.c Job %s is not valid for IVR agents

E72000 v_dialer\dialer\DialerServiceActivation\src\DSA.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitor.cxx

%s can't initialize signal handlers

E72010 v_dialer\dialer\DialerServiceActivation\src\DSA.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitor.cxx

%s server name AlreadyBound. ignored

E72030 v_dialer\dialer\DialerServiceActivation\src\DSA.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitor.cxx

%s server name resolve CannotProceed

E72040 v_dialer\dialer\DialerServiceActivation\src\DSA.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitor.cxx

%s server name resolve InvalidName

Page 383: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 381

E72050 v_dialer\dialer\DialerServiceActivation\src\DSA.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitor.cxx

%s Caught CORBA system exception: err=%s

E72051 v_dialer\dialer\DialerServiceActivation\src\DSA.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitor.cxx

%s Caught CORBA exception: err=%s

E72052 v_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitorIFImpl.cxx

%s Caught CORBA TRANSIENT error.

E72060 v_dialer\dialer\DialerServiceActivation\src\DSA.cxxv_dialer\dialer\DialerServiceMonitor\src\DSMEvent.cxxv_dialer\dialer\DialerServiceMonitor\src\EventReceiver.cxxv_dialer\dialer\DialerServiceMonitor\src\SoeEvent.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceController.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitor.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitorIFImpl.cxx

%s Caught unknown exception

E72070 v_dialer\dialer\DialerServiceActivation\src\DSA.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitor.cxx

%s is NotFound

E72080 v_dialer\dialer\DialerServiceActivation\src\DSA.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitor.cxx

failed to write %s IOR

E72090 v_dialer\dialer\DialerServiceActivation\src\DSA.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitor.cxx

%s:: Caught LogOnOffError exception(%d, %s)

E72100 v_dialer\dialer\DialerServiceActivation\src\DSA.cxx

function %s failed!

E72110 failed to create %s!

E72120 v_dialer\dialer\DialerServiceActivation\src\DSAIFImpl.cxx

can not start activation, %s!

Page 384: PC4 Troubleshooting Main

382 Maintenance and Troubleshooting Guide March 2008

E72130 v_dialer\dialer\DialerServiceActivation\src\DSAIFImpl.cxx

failed on starting a %s thread.

E72140 v_dialer\dialer\DialerServiceActivation\src\DSAIFImpl.cxx

reqID=%d, failed to add request.

E72150 v_dialer\dialer\DialerServiceActivation\src\DSAIFImpl.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceController.cxx

failed to load %s.

E72160 v_dialer\dialer\DialerServiceActivation\src\DSA.cxxv_dialer\dialer\DialerServiceActivation\src\DSAIFImpl.cxxv_dialer\dialer\DialerServiceActivation\src\DSAServiceIFImpl.cxxv_dialer\dialer\DialerServiceMonitor\src\EventReceiver.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceController.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitor.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitorIFImpl.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitoringIFImpl.cxx

%s: failed on %s.

E72170 v_dialer\dialer\DialerServiceActivation\src\DSARequest.cxx

reqID=%d, Failed to execute child process =%s. cmd=%s, errno=%d, ret=%d

E72180 v_dialer\dialer\DialerServiceActivation\src\DSARequest.cxx

reqID=%d, Failed to start the service=%s

E72190 v_dialer\dialer\DialerServiceActivation\src\DSARequest.cxx

reqID=%d, Caught DSAError.failed to stop the service=%d

E72200 v_dialer\dialer\DialerServiceActivation\src\DSARequest.cxx

reqID=%d, Caught unknown exception. failed to stop the service=%d

E72201 v_dialer\dialer\DialerServiceActivation\src\DSARequest.cxx

E72210 v_dialer\dialer\DialerServiceActivation\src\DSARequest.cxx

%s: reqID=%d, the reference no longer denotes an existing obj

Page 385: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 383

E72220 v_dialer\dialer\DialerServiceActivation\src\DSARequest.cxx

%s: reqID=%d, could not decide whether or not obj exists.

E72230 v_dialer\dialer\DialerServiceActivation\src\DSARequest.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitorIFImpl.cxx

%s: reqID=%d, failed on calling observer's Update method.

E72240 v_dialer\dialer\DialerServiceActivation\src\DSARequest.cxx

%s: reqID=%d, cmd=%s, caught unknown exception. %s

E72250 v_dialer\dialer\DialerServiceActivation\src\DSARequest.cxx

%s: reqID=%d, Failed to %s. cmd=%s, errno=%d, ret=%d

E72260 v_dialer\dialer\DialerServiceActivation\src\DSAServiceIFImpl.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitor.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitorIFImpl.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitoringIFImpl.cxx

%s: Failed to convert from char to LocText

E72270 v_dialer\dialer\DialerServiceMonitor\src\DialerServiceController.cxx

%s: the event either is NOT found or is not supported or there is no info for the event.

E72280 v_dialer\dialer\DialerServiceMonitor\src\\DialerServiceMonitor.cxxv_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitorIFImpl.cxx

%s: Caught SubError. SubError is: errorID =%s, msg=%s.

E72290 v_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitorIFImpl.cxx

%s: input param ObserverIF_ptr is null.

E72300 v_dialer\dialer\DialerServiceMonitor\src\DialerServiceMonitorIFImpl.cxx

%s: Create error=%d on mailbox: %s

E72310 v_dialer\dialer\DialerServiceMonitor\src\EventReceiver.cxx

%s: Create error on mailbox: %s

E72320 v_dialer\dialer\DialerServiceMonitor\src\EventReceiver.cxxv_dialer\dialer\DialerServiceMonitor\src\SoeEvent.cxx

Page 386: PC4 Troubleshooting Main

384 Maintenance and Troubleshooting Guide March 2008

Page 387: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 385

Cannot transfer inbound callAn agent is unable to transfer an inbound call.

Description

An agent is unable to transfer an inbound call. This error occurs when the AGTMoFlash_fn agent call or the agent API calls AGTMoFlashBlind or AGTMoFlashSupv attempt to transfer an inbound call.

Page 388: PC4 Troubleshooting Main

386 Maintenance and Troubleshooting Guide March 2008

Page 389: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 387

Command failedAn agent API command failed.

Description

This error occurs when trying to set an agent password and an internal system error occurs.

Page 390: PC4 Troubleshooting Main

388 Maintenance and Troubleshooting Guide March 2008

Page 391: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 389

Timed out waiting for <message>Pending request timed out waiting for a command that timed out.

Description

<message>, a string, contains the name of the command that timed out and the response that the agent binary was expecting from Avaya Proactive Contact.

Page 392: PC4 Troubleshooting Main

390 Maintenance and Troubleshooting Guide March 2008

Page 393: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 391

Operator monitor process does not respondA request concerning an agent�s headset volume has generated no response.

Description

A request concerning an agent�s headset volume has generated no response.

Page 394: PC4 Troubleshooting Main

392 Maintenance and Troubleshooting Guide March 2008

Page 395: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 393

Agent <name> logged in Already - Access DeniedAgent <name> is already logged in to the system.

Description

An agent tried to log on to the system with an agent name already in use and access was denied.

Page 396: PC4 Troubleshooting Main

394 Maintenance and Troubleshooting Guide March 2008

Page 397: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 395

Unable to send message to porterAn agent cannot send a message to porter.

Description

An agent cannot send a message to porter.

Page 398: PC4 Troubleshooting Main

396 Maintenance and Troubleshooting Guide March 2008

Page 399: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 397

Password has expiredDuring agent log on, the system determines the agent�s password has expired.

Description

During agent log on, the system determines the agent�s password has expired.

Page 400: PC4 Troubleshooting Main

398 Maintenance and Troubleshooting Guide March 2008

Page 401: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 399

<agent><agent_name> - Operator number returned invalid <slot_num>

The agent logon is invalid.

Description

The <slot_num> is the agent slot number assigned to the agent with user name <agent_name>.

Page 402: PC4 Troubleshooting Main

400 Maintenance and Troubleshooting Guide March 2008

Page 403: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 401

Incorrect message typeAgent application message headers may not be formatted correctly.

Description

This error message may mean that agent application message headers are not formatted correctly. The message type should be one of the following:

● Data

● Pending

● Error

● Response

● Busy

● Notify

Page 404: PC4 Troubleshooting Main

402 Maintenance and Troubleshooting Guide March 2008

Page 405: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 403

Incorrect number of argumentsCommand had wrong number of arguments.

Description

An agent application issued a command containing the wrong number of arguments.

Page 406: PC4 Troubleshooting Main

404 Maintenance and Troubleshooting Guide March 2008

Page 407: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 405

Must select unitAn agent did not select a unit ID value.

Description

The agent is logged in to a Unit Work List job but has not selected a unit ID value to work with. A Unit Work List job divides customer records into work lists or subsets. Agents work with records only in their assigned work lists.

Page 408: PC4 Troubleshooting Main

406 Maintenance and Troubleshooting Guide March 2008

Page 409: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 407

Failed to allocate memoryA process failed to allocate memory.

Description

Many different processes can generate this error message. A process is about to store something in memory and finds that it cannot allocate that memory for its purpose. In general, this means a malloc call failed.

Page 410: PC4 Troubleshooting Main

408 Maintenance and Troubleshooting Guide March 2008

Page 411: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 409

Audio file name too longAudio file name is too long

Description

An audio file name exceeds the eight character limit.

Page 412: PC4 Troubleshooting Main

410 Maintenance and Troubleshooting Guide March 2008

Page 413: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 411

Bad argumentA process encountered a bad argument to a function when trying to execute.

Description

A process encountered a bad argument to a function when trying to execute. This error message can occur when the readtape, writetape, or pds_page binary is trying to write a message to the screen. It can also occur when the swif_mako process or in some cases with job control.

The error message should provide the context of the error.

Page 414: PC4 Troubleshooting Main

412 Maintenance and Troubleshooting Guide March 2008

Page 415: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 413

ERROR - Unknown file descriptorAgent attempted a command that was not correctly formed.

Description

An agent attempted a command that was not correctly formed.

Page 416: PC4 Troubleshooting Main

414 Maintenance and Troubleshooting Guide March 2008

Page 417: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 415

Invalid entry for <name> in <filename> A process accessed the named file for the named parameter which has an invalid value.

Description

A process, typically in shared memory, found an invalid parameter value in the named file. The most common reason for this error is an invalid value for the LINEASSIGN value in the $VOICEDIR/etc/master.cfg file.

Page 418: PC4 Troubleshooting Main

416 Maintenance and Troubleshooting Guide March 2008

Page 419: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 417

Field has incorrect lengthList distribution process finds calling list field with incorrect length.

Description

The listdist binary, upon opening the calling list, checks the list�s status field locations and finds a field with an incorrect length.

Page 420: PC4 Troubleshooting Main

418 Maintenance and Troubleshooting Guide March 2008

Page 421: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 419

Bad file descriptor <num>Process encounters a bad file descriptor.

Description

A process encounters a bad file descriptor while trying to access a calling list.

Page 422: PC4 Troubleshooting Main

420 Maintenance and Troubleshooting Guide March 2008

Page 423: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 421

Invalid headset number <num> <line>A process accessed switch information concerning headsets and encountered a headset with an invalid number.

Description

A process accessed switch information concerning headsets and encountered a headset with an invalid number. The $VOICEDIR/config/dgswitch.cfg file contains the valid numbers.

Page 424: PC4 Troubleshooting Main

422 Maintenance and Troubleshooting Guide March 2008

Page 425: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 423

Failed to initialize screen environmentWindows screen environment failed to start.

Description

When starting a Windows-based application, the application does not start because Avaya Proactive Contact could not initiate the Windows screen environment.

Page 426: PC4 Troubleshooting Main

424 Maintenance and Troubleshooting Guide March 2008

Page 427: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 425

Invalid line selectionChoice of line to select is invalid.

Description

When viewing call lists or running jobs, for instance, the system may prompt you to select a line of the output on the screen to view. Your answer to this prompt did not mach any line number available for viewing.

Page 428: PC4 Troubleshooting Main

426 Maintenance and Troubleshooting Guide March 2008

Page 429: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 427

Invalid logical connector <name>A logical connector such as AND has been misspelled.

Description

When creating call strategy you can use logical operators such as AND, OR to create groupings of criteria. One of these groupings has an invalid logical connector.

Page 430: PC4 Troubleshooting Main

428 Maintenance and Troubleshooting Guide March 2008

Page 431: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 429

Invalid recall code <num>While working on call strategies, the system encountered an invalid recall code.

Description

While working on call strategies, the system encountered an invalid recall code.

Page 432: PC4 Troubleshooting Main

430 Maintenance and Troubleshooting Guide March 2008

Page 433: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 431

Invalid ring count <num>A call strategy process encountered an invalid ring count, <num>.

Description

A call strategy process encountered an invalid ring count, <num>.

Page 434: PC4 Troubleshooting Main

432 Maintenance and Troubleshooting Guide March 2008

Page 435: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 433

Invalid time formatIncorrect time format used.

Description

The code that generated this error message requires the user to provide a time. The time was not given in the correct format, HH.MM.SS

Page 436: PC4 Troubleshooting Main

434 Maintenance and Troubleshooting Guide March 2008

Page 437: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 435

Conference in progressAn agent attempted to add a call to a conference the call was already in.

Description

An agent attempted to add a call to a conference the call was already in.

Page 438: PC4 Troubleshooting Main

436 Maintenance and Troubleshooting Guide March 2008

Page 439: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 437

Field not defined in calling listA calling list contains a field that is not defined.

Description

A calling list contains a field that is not defined in the fdict file associated with the calling list.

Note:Note: If this error occurs when creating a hash index for the calling list, the

STATUSFLAG field is the source of the error.

Page 440: PC4 Troubleshooting Main

438 Maintenance and Troubleshooting Guide March 2008

Page 441: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 439

Unable to create fileA process cannot create a file required to successfully complete.

Description

Avaya Proactive Contact processes often create files. This particular error message is generated only during the following activities:

● Writing record numbers from the hash index file into a calling list.

● Moving record data, field by field, from one calling list to another.

● Converting zip codes to area codes.

Page 442: PC4 Troubleshooting Main

440 Maintenance and Troubleshooting Guide March 2008

Page 443: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 441

agent - Failed to read from file <name>A process, agent, is unable to read the contents of the named file.

Description

This error can occur from a wide variety of sources and for a equally wide range of reasons: Some of the reasons are:

● There is not enough memory allocated to read the file.

● The process cannot read a record in the file

Page 444: PC4 Troubleshooting Main

442 Maintenance and Troubleshooting Guide March 2008

Page 445: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 443

Failed to unlock fileA locked file cannot be unlocked.

Description

Typically, if more than one process or person can access file at any time, a process locks a file when it is in use so that changes cannot be made by more than user at a time. In this case a file that was locked cannot be unlocked.

This message can occur whenever a process tries to access a call list or other data file.

Page 446: PC4 Troubleshooting Main

444 Maintenance and Troubleshooting Guide March 2008

Page 447: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 445

Warning: CFRM message truncatedWhile sending a reply message to the last process that sent an IPC message to the process that generated the error message, the reply message is truncated.

Description

While sending a reply message to the last process that sent an IPC message to the process that generated the error message, the reply message is truncated. The message is truncated either because it is too long or it is no longer a valid message.

Page 448: PC4 Troubleshooting Main

446 Maintenance and Troubleshooting Guide March 2008

Page 449: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 447

Callbacks are not permitted on inbound callsAgent tried to make a callback on an inbound call.

Description

Agent tried to make a callback on an inbound call and callbacks are not permitted on inbound calls.

Page 450: PC4 Troubleshooting Main

448 Maintenance and Troubleshooting Guide March 2008

Page 451: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 449

Field <name> not defined in calling list <filename>A process tried to access the named field in the named calling list and the field does not exist.

Description

A process tried to access the named field in the named calling list and the field does not exist.

Page 452: PC4 Troubleshooting Main

450 Maintenance and Troubleshooting Guide March 2008

Page 453: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 451

clstat <xfd> failedCreation of a calling list, xfd, header failed.

Description

A process trying to create a list header for the calling list identified by xfd, was unsuccessful.

Page 454: PC4 Troubleshooting Main

452 Maintenance and Troubleshooting Guide March 2008

Page 455: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 453

Failed to remove file <filename>User attempted to remove a calling list file and could not.

Description

User attempted to remove a calling list file and could not. The error message does identify the file that was not removed.

Page 456: PC4 Troubleshooting Main

454 Maintenance and Troubleshooting Guide March 2008

Page 457: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 455

Clear fdict <number> failedCould not clear fdict file <num>.

Description

While creating a new header record and loading header data for the current xfd, there was a failure to clear the fdict file <num>.

Page 458: PC4 Troubleshooting Main

456 Maintenance and Troubleshooting Guide March 2008

Page 459: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 457

Date is before the current dateThe date for the command is before the current date.

Description

The date for the command is before the current date.

Page 460: PC4 Troubleshooting Main

458 Maintenance and Troubleshooting Guide March 2008

Page 461: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 459

Incoming command exceeded maximum buffer sizeAn agent binary command exceeded the maximum buffer size.

Description

An agent binary command exceeded the maximum buffer size.

Page 462: PC4 Troubleshooting Main

460 Maintenance and Troubleshooting Guide March 2008

Page 463: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 461

<string>: Confirm error (num)An Avaya CTI process is looking for confirmation of an event.

Description

An Avaya CTI process is looking for confirmation of an event. The string value in the error message can be one of these values:

● RouteSelectReq

● MsgCall - num = 21

● CSTA_SET_AGENT_STATE

● Monitor Agent

Page 464: PC4 Troubleshooting Main

462 Maintenance and Troubleshooting Guide March 2008

Page 465: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 463

File corruption or record size mismatch detected in calling list (name>

While attempting to access a calling list, a process found either a corrupt file or a record that did not match its known size.

Description

While attempting to access a calling list, a process found either a corrupt file or a record that did not match its known size.

Page 466: PC4 Troubleshooting Main

464 Maintenance and Troubleshooting Guide March 2008

Page 467: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 465

CTI Error: <string><num>Each CTI error designated by this error message carries the clue to its origin in the string.

Description

Each CTI error designated by this error message carries the clue to its origin in the string. For instance, these errors:

1. Error 65

CTI Error:ACSUNSOLICITED:ACS_UNIVERSAL_FAILURE error = 65

tells you the Avaya CT server was shut down.

2. Error -5

CTI Error:acsOpenStream? failed error = -5

tells you that Avaya CT server is not present in the network.

3. Error 25

acsOpenStream: ACS_UNIVERSAL_FAILURE_CONF error = 25

tells you that the login or password was invalid.

4. Error 1007

acsOpenStream: ACS_UNIVERSAL_FAILURE_CONF error = 1007

tells you that the driver was unable to open the new session because no link was available to the PBX.

Page 468: PC4 Troubleshooting Main

466 Maintenance and Troubleshooting Guide March 2008

Page 469: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 467

CTI not configured for agent eventsThe Avaya CT Server is not enabled for agent events.

Description

The Avaya CT Server is not enabled for agent events.

Page 470: PC4 Troubleshooting Main

468 Maintenance and Troubleshooting Guide March 2008

Page 471: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 469

Duplicate ALL phone numbers specificationA process was making a change to a calling list in the memory database and an error occurred.

Description

A process was making a change to a calling list in the memory database and an error occurred., The change most likely involved a time zone setting or the STD_TO_DIALFMT setting of one or more telephone numbers.

Page 472: PC4 Troubleshooting Main

470 Maintenance and Troubleshooting Guide March 2008

Page 473: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 471

Duplicate country specifiedThe system encountered duplicate country settings where it expected a single country.

Description

The system while loading country specific settings from files such as locale.cfg, encountered setting with duplicate countries where there should only be one country setting.

Page 474: PC4 Troubleshooting Main

472 Maintenance and Troubleshooting Guide March 2008

Page 475: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 473

Environment variable not setAn environment variable required for correct operation of Avaya Proactive Contact is missing.

Description

Environment variables determine how many aspects of the system work. In this case, the most likely environment variable this not set or not set correctly is $VOICEDIR.

Page 476: PC4 Troubleshooting Main

474 Maintenance and Troubleshooting Guide March 2008

Page 477: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 475

OnEventEstablished: Unknown command (7)An established event occurred after a request to hang up a call, but before the Clear Call Confirmation.

Description

An established event occurred after a request to hang up a call, but before the Clear Call Confirmation.

Page 478: PC4 Troubleshooting Main

476 Maintenance and Troubleshooting Guide March 2008

Page 479: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 477

Recall attempt can�t exceed <num>The number of recall attempts cannot exceed <num>.

Description

An agent tried to exceed the allowed number, <num>, of recall attempts.

Page 480: PC4 Troubleshooting Main

478 Maintenance and Troubleshooting Guide March 2008

Page 481: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 479

Extra comma in selection criteriaWhen setting up call strategy, found an extra comma in selection criteria.

Description

When setting up call strategy, the system found an extra comma in selection criteria.

Page 482: PC4 Troubleshooting Main

480 Maintenance and Troubleshooting Guide March 2008

Page 483: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 481

Failed to setup command keysThe command keys for the graphical user interface are not available.

Description

When starting Avaya Proactive Contact, the command keys do not work.

Page 484: PC4 Troubleshooting Main

482 Maintenance and Troubleshooting Guide March 2008

Page 485: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 483

Failed to lock fileA process did not lock a file.

Description

A file is open and can be accessed by more than one process for change. Typically, if more than one process or person can access file at any time, a process locks a file when it using so that changes cannot be made while the file is in use.

This message alerts the user that a file that should be locked, is not locked. It can only occur during these two activities:

● When generating *.hist files from *.stat files.

● When the job configuration editor is in use.

Page 486: PC4 Troubleshooting Main

484 Maintenance and Troubleshooting Guide March 2008

Page 487: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 485

Failed to initialize keyboardAt start of Agent API, the system keyboard did not initialize.

Description

For both the graphical user interface (GUI) and the character-based interface to the agent API, the system checks at startup for an initialized keyboard.

Page 488: PC4 Troubleshooting Main

486 Maintenance and Troubleshooting Guide March 2008

Page 489: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 487

Failed to open directory <dir_name>An operation tried to open a directory and failed.

Description

An operation tried to open a directory and failed.

Page 490: PC4 Troubleshooting Main

488 Maintenance and Troubleshooting Guide March 2008

Page 491: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 489

Failed to read file headerA process was unable to read the file header of a file.

Description

A shadow job process was unable to read the file header of an inbound calling list.

Resolution

To resolve this issue, follow these steps:

1. Inspect the calling list in use when the error occurred.

2. Repair the file header as necessary.

3. Retry the shadow job activity that created the error message.

Page 492: PC4 Troubleshooting Main

490 Maintenance and Troubleshooting Guide March 2008

Page 493: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 491

Failed to initialize switcherThe system failed to establish communications with the switch.

Description

The system failed to establish communications with the switch.

Page 494: PC4 Troubleshooting Main

492 Maintenance and Troubleshooting Guide March 2008

Page 495: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 493

Fail to load recordWhen editing calling lists, the user attempts to access a record and the record does not load.

Description

When editing calling lists, the user attempts to access a record and the record does not load.

Page 496: PC4 Troubleshooting Main

494 Maintenance and Troubleshooting Guide March 2008

Page 497: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 495

Fatal error on select - <num>Agent tried to select job <num> and got a fatal error.

Description

An agent tried to select job <num> and got a fatal error. The agent child process supporting the client session is terminating.

Page 498: PC4 Troubleshooting Main

496 Maintenance and Troubleshooting Guide March 2008

Page 499: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 497

Field name <name> is invalidThe named field name is not allowed.

Description

A call strategy process has encountered a field name that is invalid.

Page 500: PC4 Troubleshooting Main

498 Maintenance and Troubleshooting Guide March 2008

Page 501: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 499

Invalid field value <value>The named value for a field is not allowed.

Description

A call strategy process has encountered a named value for a field that is invalid.

Page 502: PC4 Troubleshooting Main

500 Maintenance and Troubleshooting Guide March 2008

Page 503: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 501

Missing or invalid entry in fileA process opens a file and a critical entry is missing or invalid.

Description

This error occurs when a process opens a file to get a parameter value and the parameter is either missing or invalid. In most cases the process is looking for a value in master.cfg. The master.cfg values most often looked for are:

● ARCHIVE_DIR

● DIALERID

● LINEASSIGN

● MAXHIDSLOTS

● MAXPHONE

● MAXCMPCODE

● PORTS

The error may also occur when the process tries to access a environment variable such as TZ, timezone. All the Avaya Proactive Contact environment files are defined in the $VOICEDIR/shell/envfile configuration file.

This error can occur when the process tries access other parameters from other configuration files, but the ones listed above are the most common cause of the error.

Page 504: PC4 Troubleshooting Main

502 Maintenance and Troubleshooting Guide March 2008

Page 505: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 503

File <filename> exists, but is not readable by user <user_name

A process cannot read an existing file.

Description

This error occurs when a process attempts to read a file, but the process owner does the have file permissions to read the file. It almost always is an indication of another, deeper, problem.

Page 506: PC4 Troubleshooting Main

504 Maintenance and Troubleshooting Guide March 2008

Page 507: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 505

File <filename> exists, but cannot be written by user <user_name

A process cannot write to an existing file.

Description

This error occurs when a process attempts to write to a file, but the file permissions do not permit that user to write to the file. Almost always this indicates a deeper problem.

Page 508: PC4 Troubleshooting Main

506 Maintenance and Troubleshooting Guide March 2008

Page 509: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 507

File <filename> does not existA process tried to access a file that does not exist.

Description

A process tried to access a file that does not exist. In many instances of this error message the process is trying to access an archive file.

This error appears as "Invalid job name" when starting jobs.

Page 510: PC4 Troubleshooting Main

508 Maintenance and Troubleshooting Guide March 2008

Page 511: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 509

File did not closeA process has left a file open that needs to be saved.

Description

This error is only generated by dialer service processes.

Page 512: PC4 Troubleshooting Main

510 Maintenance and Troubleshooting Guide March 2008

Page 513: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 511

No space on file systemThe file system is full.

Description

This error can occur when creating an index for use by a caller or when using readtape and writetape. Whether accessing a hard disk, CD-ROM or tape media, this error indicates the media is full.

Page 514: PC4 Troubleshooting Main

512 Maintenance and Troubleshooting Guide March 2008

Page 515: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 513

Unequal phone number field lengths in file <name>A process attempts to read a number written in string format in a file and is unsuccessful.

Description

A process is trying to read a number in string form in a file such as callselnum and encounters phone numbers of unequal length.

Page 516: PC4 Troubleshooting Main

514 Maintenance and Troubleshooting Guide March 2008

Page 517: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 515

Field value not in acceptable listA value in a comma delimited list is not allowed in the list.

Description

An agent has created a comma delimited list with an invalid entry.

Page 518: PC4 Troubleshooting Main

516 Maintenance and Troubleshooting Guide March 2008

Page 519: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 517

Entry <value> missing/invalid in <filename> fileA process tried to read a value from a file and <value> is either missing or invalid.

Description

A process tried to read a <value> from <filename> and <value> is either missing or invalid. This error can occur in many different situations. The first entry in the actual error message should contain some context of the error.

Page 520: PC4 Troubleshooting Main

518 Maintenance and Troubleshooting Guide March 2008

Page 521: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 519

Gap found between selection criteria linesWhen setting up call strategies, a gap exists in the selection criteria.

Description

When setting up call strategies, a gap exists in the selection criteria.

Page 522: PC4 Troubleshooting Main

520 Maintenance and Troubleshooting Guide March 2008

Page 523: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 521

Headset <id_num> not specified in dgswitch.cfg fileThe operator process while in test mode, encounters a headset number ID that is not in the dgswitch.cfg file.

Description

The operator process while in test mode, encounters a headset number ID that is not in the dgswitch.cfg file.

Page 524: PC4 Troubleshooting Main

522 Maintenance and Troubleshooting Guide March 2008

Page 525: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 523

Headset port number <num> out of range A process accessed switch information concerning headsets and encountered a headset with a port number out of range.

Description

A process accessed switch information concerning headsets and encountered a headset with a port number out of range. The $VOICEDIR/config/dgswitch.cfg file contains the valid port ranges.

Page 526: PC4 Troubleshooting Main

524 Maintenance and Troubleshooting Guide March 2008

Page 527: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 525

<agent_name> - Exceeded operator slots available, MAXOPS is low

The <agent_name> logon exceeds the Avaya Proactive Contact system limit on the number of agents.

Description

The <agent_name> logon exceeds the Avaya Proactive Contact system limit on the number of agents. MAXOPS is the number of headset ID slots. The number of agents is limited by the number of slots for headsets available on the switch. This limit is a physical restraint on the number of agents.

Note:Note: This error can occur if client sessions for the agent application are left running on

Avaya Proactive Contact after an agent workstation crashes.

Page 528: PC4 Troubleshooting Main

526 Maintenance and Troubleshooting Guide March 2008

Page 529: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 527

Inbound agents only permittedAn agent other than an inbound agent tried to access an inbound job.

Description

An agent other than an inbound agent tried to access an inbound job.

Page 530: PC4 Troubleshooting Main

528 Maintenance and Troubleshooting Guide March 2008

Page 531: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 529

Invalid answer delay timeA process while adding localization information to the in-memory database encountered an invalid answer delay time.

Description

A process while adding localization information to the in-memory database encountered an invalid answer delay time.

Page 532: PC4 Troubleshooting Main

530 Maintenance and Troubleshooting Guide March 2008

Page 533: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 531

Invalid call detection mode <name>A call detection setting in the call strategy files contains an invalid name.

Description

A call detection setting in the call strategy files contains an invalid name. This setting tells the system which calls to pass to agents. It can have the following values:

● Voice

● Autovoice

● Intercept

● No circuit

● Disconnect

● Vacant

● Reorder

Resolution

To resolve this issue, follow these steps:

1. Most likely the offending setting is in the call strategy settings. Find the value for the keyword, E_STRATEGY in jobEventData. The value is the name of the Call Strategy file which is typically in the $VOICEDIR/callsel directory. If it is not there, the CALLSEL keyword in $VOICEDIR/etc/master.cfg to determine the correct directory.

2. Inspect the all detection settings in the jobEventData file for invalid entries.

3. Correct any invalid entries you find.

4. Rerun the process that generated this error message.

You can also use Supervisor to make these corrections:

5. From the Supervisor Main menu, select Campaign > Strategy >Edit a phone strategy

6. See Using Supervisor for more information.

Page 534: PC4 Troubleshooting Main

532 Maintenance and Troubleshooting Guide March 2008

Page 535: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 533

CSTAUniversalConfEvent for call monitor, error = 24There is no active call because an application has sent an invalid call identifier.

Description

There is no active call because an application has sent an invalid call identifier. The call identifier is a numeric string of 18 digits. The system generates a call identifier in the following instances:

● A job initiates an outbound call

● .A job checks for an inbound call on an inbound trunk

● .An agent initiates a manual call

● .An agent initiates a field call

● .An agent initiates a transfer

In most cases of this error, the call does not exist or has been cleared.

Page 536: PC4 Troubleshooting Main

534 Maintenance and Troubleshooting Guide March 2008

Page 537: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 535

Invalid format character foundAgent entered a date with an invalid format character.

Description

Agent entered a date with an invalid format character. The agent either entered a date with a slash (/) versus backslash (\) or in the time format used colons or other extra characters.

Page 538: PC4 Troubleshooting Main

536 Maintenance and Troubleshooting Guide March 2008

Page 539: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 537

invalid channel number <string>An agent tries to talk directly to the switch/porter and uses an invalid channel number, <string>.

Description

An agent tries to talk directly to the switch/porter and uses an invalid channel number, <string>.

Page 540: PC4 Troubleshooting Main

538 Maintenance and Troubleshooting Guide March 2008

Page 541: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 539

Invalid DAA typeA process while adding localization information to the in-memory database encountered an invalid DAA type.

Description

A process while adding localization information to the in-memory database encountered an invalid DAA type.

Page 542: PC4 Troubleshooting Main

540 Maintenance and Troubleshooting Guide March 2008

Page 543: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 541

Invalid date formatIncorrect date format used.

Description

The code that generated this error message requires a date in the correct format. The required date format is ccyy/mm/dd.

Page 544: PC4 Troubleshooting Main

542 Maintenance and Troubleshooting Guide March 2008

Page 545: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 543

Invalid delay specificationA process accessed the time between recalls and found an invalid delay specification.

Description

A process accessed the time between recalls and found an invalid delay specification.

Page 546: PC4 Troubleshooting Main

544 Maintenance and Troubleshooting Guide March 2008

Page 547: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 545

Invalid file nameThe requested or supplied file name is not valid.

Description

Although many operations in Avaya Proactive Contact require specific file names, only a select few return this error message. This error occurs during the following activities:

1. Creating an index by searching a calling list for records with a specified criteria.

2. Preparing a calling list report.

3. Creating a distribution list of data in a calling list.

4. Displaying a file�s content on the screen.

Page 548: PC4 Troubleshooting Main

546 Maintenance and Troubleshooting Guide March 2008

Page 549: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 547

New password entered is invalidAn agent is trying to create a new password and entered an invalid password.

Description

An agent is trying to create a new password and entered an invalid password.

Page 550: PC4 Troubleshooting Main

548 Maintenance and Troubleshooting Guide March 2008

Page 551: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 549

Invalid offhook retry delayWhile a process is adding localization information for a calling list into the memory database, it finds a phone number with a invalid offhook retry delay.

Description

While a process is adding localization information for a calling list into the memory database, it finds a phone number with a invalid offhook retry delay.

Page 552: PC4 Troubleshooting Main

550 Maintenance and Troubleshooting Guide March 2008

Page 553: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 551

Invalid phoneWhen an agent is trying to set up recalls, the system checks that the phone number is valid and finds one that is not.

Description

When an agent is trying to set up recalls, the system checks that the phone number is valid and finds one that is not.

If this error occurred when using a process initiated using the Agent API, the telephone field index does not fall in the range returned by AGTListCallbackFmt for the customer record. In this case retry the process with a value between 1 and the AGTListCallbackFmt value.

Page 554: PC4 Troubleshooting Main

552 Maintenance and Troubleshooting Guide March 2008

Page 555: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 553

Invalid phone <number> While using a call strategy or setting up recalls, a process finds a listed invalid phone number.

Description

While using a call strategy or setting up recalls, a process finds a listed invalid phone number.

Page 556: PC4 Troubleshooting Main

554 Maintenance and Troubleshooting Guide March 2008

Page 557: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 555

Invalid phone number lengthSystem finds a phone number with an invalid length.

Description

While the system is entering locale information into memory, it encounters a phone number with an invalid length.

Page 558: PC4 Troubleshooting Main

556 Maintenance and Troubleshooting Guide March 2008

Page 559: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 557

Invalid phonestat - <status>Invalid recall telephone selected.

Description

The telephone number specified by the <index> parameter is not valid. The <status> value is B, T, or Z. B indicates a bad telephone number, T indicates the phone number belongs to an unknown time zone, and Z indicates that the recall time is invalid in the time zone.

Page 560: PC4 Troubleshooting Main

558 Maintenance and Troubleshooting Guide March 2008

Page 561: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 559

Original password is invalidThe entered password is invalid.

Description

An agent when logging in, enters an invalid password.

Page 562: PC4 Troubleshooting Main

560 Maintenance and Troubleshooting Guide March 2008

Page 563: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 561

Invalid patternA process tries to use a pattern as criteria for record selection and the pattern is invalid.

Description

A process tries to use a pattern as criteria for record selection and the pattern is invalid.

Page 564: PC4 Troubleshooting Main

562 Maintenance and Troubleshooting Guide March 2008

Page 565: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 563

Invalid recall code <code>A recall setting is not recognized by the system.

Description

When selecting records from a calling list, the user can mark entries for recall or choose a field with a specified value to mark the call for recall. To generate this error message, the value encountered is not a legitimate value for marking a call for recall or is not recognized a good value for a specific field.

Page 566: PC4 Troubleshooting Main

564 Maintenance and Troubleshooting Guide March 2008

Page 567: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 565

Invalid response from operator monitor processThe opmon process reported that an agent monitoring process returned an invalid response concerning headsets.

Description

The opmon process reported that an agent monitoring process returned an invalid response concerning headsets.

Page 568: PC4 Troubleshooting Main

566 Maintenance and Troubleshooting Guide March 2008

Page 569: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 567

Invalid range characterWhen converting a calling list to std_to_dialfmt, the length of a standard phone number for the specified country contains an invalid character.

Description

When converting a calling list to std_to_dialfmt, the length of a standard phone number for the specified country contains an invalid character.

Page 570: PC4 Troubleshooting Main

568 Maintenance and Troubleshooting Guide March 2008

Page 571: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 569

Invalid ring count <num>A ring count setting in the call strategy files contains an invalid number.

Description

A ring count setting in the call strategy files contains an invalid number.

Page 572: PC4 Troubleshooting Main

570 Maintenance and Troubleshooting Guide March 2008

Page 573: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 571

Invalid time zone character <char>A time zone setting in the call strategy files contains an invalid character.

Description

A time zone setting in the call strategy files contains an invalid character.

Page 574: PC4 Troubleshooting Main

572 Maintenance and Troubleshooting Guide March 2008

Page 575: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 573

Invalid use of ALL phone numbers specificationThe ALL parameter appears in the locale.cfg file as an invalid entry.

Description

As the system processes a calling list performing the change of phone numbers to standard to dial format, it uses parameters in the phonefmt.cfg some of which come from the local.cfg file. The ALL entry can be used in some cases in locale.cfg, but not all.

Page 576: PC4 Troubleshooting Main

574 Maintenance and Troubleshooting Guide March 2008

Page 577: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 575

Invalid VM2 locale codeA process is adding a line of localization code t0 memory and encounters an invalid VM2 locale code.

Description

A process is adding a line of localization code t0 memory and encounters an invalid VM2 locale code.

Page 578: PC4 Troubleshooting Main

576 Maintenance and Troubleshooting Guide March 2008

Page 579: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 577

Invalid wait limitWhile a process is adding localization information for a calling list into the memory database, it finds a phone number with a invalid wait limit.

Description

While a process is adding localization information for a calling list into the memory database, it finds a phone number with a invalid wait limit.

Page 580: PC4 Troubleshooting Main

578 Maintenance and Troubleshooting Guide March 2008

Page 581: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 579

Failed to invoke functionA process tried to start a function and failed.

Description

In most cases, this error occurs during record selection or the creation of phone strategy when a process tries to spawn a child process.

Page 582: PC4 Troubleshooting Main

580 Maintenance and Troubleshooting Guide March 2008

Page 583: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 581

IPC - invalid input argumentWhen the system was creating the inter-process communication module (IPC), it encountered an invalid input argument.

Description

When the system was creating the inter-process communication module (IPC), it encountered an invalid input argument.

Page 584: PC4 Troubleshooting Main

582 Maintenance and Troubleshooting Guide March 2008

Page 585: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 583

IPC - invalid ipc entryWhile sending a message to the ipc queue, the system determines that the message has invalid content.

Description

While sending a message to the ipc queue, the system determines that the message has invalid content.

Page 586: PC4 Troubleshooting Main

584 Maintenance and Troubleshooting Guide March 2008

Page 587: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 585

Invalid ipc number <num>A process sent or received an ipc message that has a invalid ipc number.

Description

A process sent or received an ipc message that has a invalid ipc number.

Page 588: PC4 Troubleshooting Main

586 Maintenance and Troubleshooting Guide March 2008

Page 589: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 587

<process_name> - Accessing bad semaphoreThe <process_name> process in trying to use an IPC message, encountered a bad semaphore.

Description

The <process_name> process in trying to use an IPC message, encountered a bad semaphore.

Page 590: PC4 Troubleshooting Main

588 Maintenance and Troubleshooting Guide March 2008

Page 591: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 589

<process_name> - Failed to open semaphore, err(<num>)The <process_name> process while attempting an IPC message, failed to open a semaphore.

Description

The <process_name> process while attempting an IPC message, failed to open a semaphore.

Page 592: PC4 Troubleshooting Main

590 Maintenance and Troubleshooting Guide March 2008

Page 593: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 591

<process_name> - Failed on semaphore operation, err <err_num> key = <sem_key_id> code = <op_code>

The <process_name> process attempted an IPC message semaphore operation and failed.

Description

he <process_name> process attempted an IPC message semaphore operation and failed. The error message includes the name of the process involved, the semipro key ID and the op code.

Page 594: PC4 Troubleshooting Main

592 Maintenance and Troubleshooting Guide March 2008

Page 595: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 593

<process_name> Failed on semaphore removal, err=<num> key=<num>

The <process_name> tried to remove a semaphore associated with IPC messaging and generated this error that includes the semaphore id as key=<num>.

Description

The <process_name> tried to remove a semaphore associated with IPC messaging and generated this error that includes the semaphore id as key=<num>.

Page 596: PC4 Troubleshooting Main

594 Maintenance and Troubleshooting Guide March 2008

Page 597: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 595

IPC - Failed to open opmon message queueA process tried to open an ipc message queue with opmon and could not open the queue.

Description

A process tried to open an ipc message queue with opmon and could not open the queue.

Page 598: PC4 Troubleshooting Main

596 Maintenance and Troubleshooting Guide March 2008

Page 599: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 597

Response message too longAn ipc response message is too long and therefore not sent.

Description

An ipc response message is too long and therefore not sent

Page 600: PC4 Troubleshooting Main

598 Maintenance and Troubleshooting Guide March 2008

Page 601: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 599

IVR_SCRIPT is blank in job <name>During a pool job for interactive voice response agents, an IVR script is empty.

Description

The error message names the pool job that encountered a empty IVR script.

Page 602: PC4 Troubleshooting Main

600 Maintenance and Troubleshooting Guide March 2008

Page 603: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 601

Failed to create jobmon graphical user interface (GUI)The job monitor�s GUI is missing some elements.

Description

When the job monitor GUI is created, either the menu bar, the job monitor window or the status bar is missing.

Page 604: PC4 Troubleshooting Main

602 Maintenance and Troubleshooting Guide March 2008

Page 605: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 603

Job <name> not runningAn agent tried to access a job that is not running.

Description

An agent tried to access a job that is not running.

Page 606: PC4 Troubleshooting Main

604 Maintenance and Troubleshooting Guide March 2008

Page 607: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 605

Job <name> is not valid for IVR agentsThe named job is not valid for IVR agents.

Description

The named job is not valid for IVR agents. Any job file has a set of IVR parameters, including the Allow IVR agents on job parameter. If this parameter is set to NO, IVR agents cannot access the job.

Page 608: PC4 Troubleshooting Main

606 Maintenance and Troubleshooting Guide March 2008

Page 609: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 607

Error loading job chainSystem attempts to load a job chain and next slot is already taken.

Description

System attempts to load a job chain and next slot is already taken.

Page 610: PC4 Troubleshooting Main

608 Maintenance and Troubleshooting Guide March 2008

Page 611: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 609

Attempt to store list_client on host failedThe attempt to store the list_client in slot failed.

Description

The _lcCreateXfd failed in its attempt to store the list_client in a slot on a local or remote host.

Page 612: PC4 Troubleshooting Main

610 Maintenance and Troubleshooting Guide March 2008

Page 613: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 611

Line not releasedA line is use by agent was not released.

Description

A line used by agent was not released upon completion of calls.

Page 614: PC4 Troubleshooting Main

612 Maintenance and Troubleshooting Guide March 2008

Page 615: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 613

Mastercfg errorThe master.cfg file is either missing an entry or an entry has an invalid value.

Description

The master.cfg value contains critical variables for Avaya Proactive Contact processes. Missing or invalid entries in master.cfg can cause the system to malfunction.

The master.cfg entries that most often cause this error are:

● ARCHIVE_DIR

● CALLSEL

● CONNABBREV

● CONNCRIT

● DATEFORM

● MAXCMPCODE

● MAXPHONE

● PORTCOEF

● PORTS

Page 616: PC4 Troubleshooting Main

614 Maintenance and Troubleshooting Guide March 2008

Page 617: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 615

Failed to determine max number of phonesThe MAXPHONE keyword in the $VOICEDIR/etc.master.cfg file is not set.

Description

The MAXPHONE keyword in the $VOICEDIR/etc.master.cfg file is not set. The MAXPHONE keyword sets the maximum number of phone numbers in a calling list.

Page 618: PC4 Troubleshooting Main

616 Maintenance and Troubleshooting Guide March 2008

Page 619: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 617

Unable to remove message queueA process was unable to remove the IPC message queue.

Description

During IPC communication with opmon, a process attempted to remove the IPC message queue and could not.

Page 620: PC4 Troubleshooting Main

618 Maintenance and Troubleshooting Guide March 2008

Page 621: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 619

Missing delay specificationA process accessed the time between recalls and did not find the delay specification.

Description

A process accessed the time between recalls and did not find the delay specification.

Page 622: PC4 Troubleshooting Main

620 Maintenance and Troubleshooting Guide March 2008

Page 623: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 621

Missing high rangeWhen converting a calling list to std_to_dialfmt, the length of a standard phone number for the specified country is missing the high limit for values given in locale.cfg.

Description

When converting a calling list to std_to_dialfmt, the length of a standard phone number for the specified country is missing the high limit for values given in locale.cfg.

Page 624: PC4 Troubleshooting Main

622 Maintenance and Troubleshooting Guide March 2008

Page 625: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 623

Missing completion codeA process working with recalls did not find a completion code.

Description

A process working with recalls did not find a completion code. Recalls use the local.cfg file RECALLLIMIT keyword to determine the completion code.

Page 626: PC4 Troubleshooting Main

624 Maintenance and Troubleshooting Guide March 2008

Page 627: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 625

Missing line typeA process is looking at the standard to dial format in phonefmt.cfg and cannot find the line type.

Description

The line type is missing from the standard to daily format in phoenfmt.cfg. The line types are REG (regular), INBND (inbound), OTHER, or ALLTYPES.

Page 628: PC4 Troubleshooting Main

626 Maintenance and Troubleshooting Guide March 2008

Page 629: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 627

Missing or invalid num of chars to stripA process is looking at the standard to dial format in phonefmt.cfg and cannot find the strip argument is either missing or invalid.

Description

The strip argument is either missing or invalid in the standard to dial format in phonefmt.cfg. The strip argument designates the number of digits to strip from the standard phone number when the prefix is applied.

Page 630: PC4 Troubleshooting Main

628 Maintenance and Troubleshooting Guide March 2008

Page 631: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 629

Missing phone numbersAs the system processes a calling list performing the change of phone numbers to standard to dial format, the calling list is missing phone numbers.

Description

As the system processes a calling list performing the change of phone numbers to standard to dial format, the calling list is missing phone numbers.

Page 632: PC4 Troubleshooting Main

630 Maintenance and Troubleshooting Guide March 2008

Page 633: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 631

Missing prefixA process is looking at the standard to dial format in phonefmt.cfg and cannot find the prefix.

Description

The prefix is missing from the standard to dial format in phonefmt.cfg. The prefix is known as the exchange.

.

Page 634: PC4 Troubleshooting Main

632 Maintenance and Troubleshooting Guide March 2008

Page 635: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 633

Missing limitA process is working with recalls and is missing a recall delay limit.

Description

A process is working with recalls and is missing a recall delay limit.

Page 636: PC4 Troubleshooting Main

634 Maintenance and Troubleshooting Guide March 2008

Page 637: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 635

Missing suffixA process is looking at the standard to dial format in phonefmt.cfg and cannot find the suffix.

Description

The suffix is missing from the standard to dial format in phonefmt.cfg. The suffix, which is added to the end of the phone number must be 12 characters or less.

Page 638: PC4 Troubleshooting Main

636 Maintenance and Troubleshooting Guide March 2008

Page 639: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 637

Missing or invalid low rangeWhen converting a calling list to std_to_dialfmt, the length of a standard phone number for the specified country is either missing or does not match the low limit value given in locale.cfg.

Description

When converting a calling list to std_to_dialfmt, the length of a standard phone number for the specified country is either missing or does not match the low limit value given in locale.cfg.

Page 640: PC4 Troubleshooting Main

638 Maintenance and Troubleshooting Guide March 2008

Page 641: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 639

Missing or invalid reject phone number patternThe locale.cfg file does not contain a valid or is missing a reject number pattern for a particular country.

Description

The locale.cfg file does not contain a valid or is missing a reject number pattern for a particular country.

Page 642: PC4 Troubleshooting Main

640 Maintenance and Troubleshooting Guide March 2008

Page 643: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 641

Missing or invalid time zone designationThe system found a phone number with a bad or missing time zone designation.

Description

While checking a phone number in standard_to_dial format, the system found a phone number with a bad or missing time zone designation.

Page 644: PC4 Troubleshooting Main

642 Maintenance and Troubleshooting Guide March 2008

Page 645: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 643

Missing time zone specification for country <num>While checking a phone number in calling list form, the system finds the country without the time zone specified.

Description

While checking a calling list, the system finds a country without the time zone specified.

Page 646: PC4 Troubleshooting Main

644 Maintenance and Troubleshooting Guide March 2008

Page 647: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 645

MakeCall/MakePredictiveCall/TransferCall Confirm error (33)

The dialer is trying to make or transfer a call and cannot.

Description

The swif_ct is trying to make or transfer a call in within Avaya Proactive Contact with CTI and the agent extension is busy.

Page 648: PC4 Troubleshooting Main

646 Maintenance and Troubleshooting Guide March 2008

Page 649: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 647

<type> agents are not permitted on this jobA <type> agent attempted to log on to a job that does permit more agents of that <type>.

Description

A <type> agent attempted to log on to a job that does permit more agents of that <type>. The $VOICEDIR/etc/master.cfg file keyword, OPLIMIT controls the number of <type> agents allowed on a job.

Page 650: PC4 Troubleshooting Main

648 Maintenance and Troubleshooting Guide March 2008

Page 651: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 649

Must specify transfer jobAgent did not specify a job name for a call transfer.

Description

An agent must specify a job name to use to transfer calls during inbound and blend jobs.

Page 652: PC4 Troubleshooting Main

650 Maintenance and Troubleshooting Guide March 2008

Page 653: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 651

Failed to attach shared memoryA process failed to attach to a segment of shared memory.

Description

Shared memory structures are used for headsets among other things. This error message is usually generated by processes involved with headsets or other communication processes.

Page 654: PC4 Troubleshooting Main

652 Maintenance and Troubleshooting Guide March 2008

Page 655: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 653

Cannot open channel to operator monitor processA supervisor is trying to monitor an agent�s headset and cannot reserve the agent headset ID.

Description

A supervisor is trying to monitor an agent�s headset and cannot reserve the agent headset ID or an agent cannot adjust headset speaker or ear volumes.

Page 656: PC4 Troubleshooting Main

654 Maintenance and Troubleshooting Guide March 2008

Page 657: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 655

Failed to detach shared memoryA process failed to detach a segment of shared memory.

Description

Shared memory structures are used for headsets among other things. This error message is usually generated by processes involved with headsets.

Page 658: PC4 Troubleshooting Main

656 Maintenance and Troubleshooting Guide March 2008

Page 659: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 657

No DONE_TME settingThe job file does not contain the DONE_TME field.

Description

The job file does not contain the DONE_TME field. The DONE_TIME field, used for testing, has a value of YES to allow a test agent to complete work after each call and NO does not permit that time.

Page 660: PC4 Troubleshooting Main

658 Maintenance and Troubleshooting Guide March 2008

Page 661: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 659

Failed to find linked job fileA process cannot find a job file identified as a linked job.

Description

A process cannot find a job file identified as a linked job.

Page 662: PC4 Troubleshooting Main

660 Maintenance and Troubleshooting Guide March 2008

Page 663: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 661

Unable to open keys fileAn application cannot open because it cannot create the necessary command keys for its screen.

Description

When creating the screen for applications, the key file defines the command keys. An application cannot open because it cannot create the necessary command keys for its screen.

Page 664: PC4 Troubleshooting Main

662 Maintenance and Troubleshooting Guide March 2008

Page 665: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 663

Failed to get message queueA process was unable to access the message queue.

Description

During IPC communication with opmon, a process attempted to access the message queue and could not.

Page 666: PC4 Troubleshooting Main

664 Maintenance and Troubleshooting Guide March 2008

Page 667: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 665

Unable to receive a messageA process was unable to receive an IPC message.

Description

During IPC communication with opmon, a process attempted to receive an IPC message and could not.

Page 668: PC4 Troubleshooting Main

666 Maintenance and Troubleshooting Guide March 2008

Page 669: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 667

Failed to send messageA process was unable to send a IPC message.

Description

During IPC communication with opmon, a process attempted to send an IPC message and could not.

Page 670: PC4 Troubleshooting Main

668 Maintenance and Troubleshooting Guide March 2008

Page 671: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 669

No more recordsWhen editing calling lists, the user attempts to access the next record when no more records exist.

Description

When editing calling lists, the user attempts to access the next record when no more records exist.

Page 672: PC4 Troubleshooting Main

670 Maintenance and Troubleshooting Guide March 2008

Page 673: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 671

Field has non-numeric valueAn agent has entered a non-numeric value in a field that only accepts numeric entries.

Description

An agent has entered a non-numeric value in a field that only accepts numeric entries.

Page 674: PC4 Troubleshooting Main

672 Maintenance and Troubleshooting Guide March 2008

Page 675: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 673

No previous recordWhen editing calling lists, the user attempts to access a previous record when no previous record exists.

Description

When editing calling lists, the user attempts to access a previous record when no previous record exists.

Page 676: PC4 Troubleshooting Main

674 Maintenance and Troubleshooting Guide March 2008

Page 677: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 675

Failed to process file <filename>A process could not open the <filename> file.

Description

A process could not open the <filename> file. The error message should include the name of the process that failed to open the file.

Page 678: PC4 Troubleshooting Main

676 Maintenance and Troubleshooting Guide March 2008

Page 679: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 677

Cannot be DONE from alternate screenAn agent has completed a call and enters DONE from the wrong screen.

Description

An agent has completed a call and enters DONE from the wrong screen. If the agent does not enter DONE from the current screen, data about the call is not stored. So, agent must enter DONE from current screen.

Page 680: PC4 Troubleshooting Main

678 Maintenance and Troubleshooting Guide March 2008

Page 681: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 679

Non-directory in directory pathA path contains at least one child that is not a directory.

Description

A process tried to create a directory in a path that contains at least one child that is not a directory.

Page 682: PC4 Troubleshooting Main

680 Maintenance and Troubleshooting Guide March 2008

Page 683: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 681

<process_name> failed to read from file <filename>The named process could not read the named file.

Description

The named process could not read the named file.

Page 684: PC4 Troubleshooting Main

682 Maintenance and Troubleshooting Guide March 2008

Page 685: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 683

Recall not allowed for inbound callAn agent tried to set up a recall for an inbound call.

Description

An agent tried to set up a recall for an inbound call. Recalls are not permitted for inbound calls.

Page 686: PC4 Troubleshooting Main

684 Maintenance and Troubleshooting Guide March 2008

Page 687: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 685

No record foundDuring a Avaya Proactive Contact system search for a previous record, no record is found.

Description

During a Avaya Proactive Contact system search for a previous record, no record is found.

Page 688: PC4 Troubleshooting Main

686 Maintenance and Troubleshooting Guide March 2008

Page 689: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 687

No REL_DIST settingThe job file does not contain the REL_DIST field.

Description

The job file does not contain the REL_DIST field. The REL_DIST field, used for testing, has a value of YES for released versions of Avaya Proactive Contact and NO for unreleased versions.

Page 690: PC4 Troubleshooting Main

688 Maintenance and Troubleshooting Guide March 2008

Page 691: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 689

No REL_TME settingThe job file does not contain the REL_TME field.

Description

The job file does not contain the REL_TME field. The REL_TME field, used for testing, has a value of YES for wait to release test call and NO for to release test call immediately.

Page 692: PC4 Troubleshooting Main

690 Maintenance and Troubleshooting Guide March 2008

Page 693: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 691

Failed to remove shared memoryA process failed to remove a segment of shared memory.

Description

Shared memory structures are used for headsets among other things. This error message is usually generated by processes involved with headsets.

Page 694: PC4 Troubleshooting Main

692 Maintenance and Troubleshooting Guide March 2008

Page 695: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 693

Sales verification with unit work lists is not permittedAn agent tried to do sales verification with a unit work list.

Description

Since sales verification and unit work lists are both peer types of outbound jobs, you cannot do sales verification with unit work lists.

Page 696: PC4 Troubleshooting Main

694 Maintenance and Troubleshooting Guide March 2008

Page 697: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 695

Missing std to dial phone number formatA job is attempting to make calls from a calling list and finds a phone number that is not in standard to dial format.

Description

A job is attempting to make calls from a calling list and finds a phone number that is not in standard to dial format. This is a common error.

Page 698: PC4 Troubleshooting Main

696 Maintenance and Troubleshooting Guide March 2008

Page 699: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 697

Not a calling listDuring a data transfer, the process expects a calling list and the file accessed is not a calling list.

Description

This error occurs during data transfer. If the error occurs during a readtape action, the error message should mention readtape.

Page 700: PC4 Troubleshooting Main

698 Maintenance and Troubleshooting Guide March 2008

Page 701: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 699

Unable to become root privilege for setting passwordAn agent tried to set a password but did not have root privileges.

Description

An agent tried to set a password but did not have root privileges.

Page 702: PC4 Troubleshooting Main

700 Maintenance and Troubleshooting Guide March 2008

Page 703: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 701

Cannot find time zone for phone numberA process is checking telephone numbers in standard format and cannot find the time zone designation for a number.

Description

A process is checking telephone numbers in standard format and cannot find the time zone designation for a number.

Page 704: PC4 Troubleshooting Main

702 Maintenance and Troubleshooting Guide March 2008

Page 705: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 703

Failed to create window pointerWhen constructing the GUI, the system did not create a window pointer.

Description

When constructing the GUI, the system did not create a cursor.

Page 706: PC4 Troubleshooting Main

704 Maintenance and Troubleshooting Guide March 2008

Page 707: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 705

Failed to write to file <filename>A process attempted to write to a file and failed.

Description

A process attempted to write to a file and failed. frequently the process is attempting to copy the contents of a buffer into a file when this error message occurs.

Page 708: PC4 Troubleshooting Main

706 Maintenance and Troubleshooting Guide March 2008

Page 709: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 707

Only outbound agents permitted by sales verificationA non-outbound agent tried to join a sales verification job.

Description

Sales verification jobs can only be done by outbound agents.

Page 710: PC4 Troubleshooting Main

708 Maintenance and Troubleshooting Guide March 2008

Page 711: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 709

Outbound or Managed agents only permittedAn agent that was not an outbound or managed agent tried to join this job.

Description

The current job requires outbound or managed agents. An agent who is neither type tried to join this job.

Page 712: PC4 Troubleshooting Main

710 Maintenance and Troubleshooting Guide March 2008

Page 713: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 711

<opname> operation failedThe named operation did not complete successfully.

Description

The named operation did not complete successfully. This error usually occurs when the listserver binary attempts to start the callsel binary.

Page 714: PC4 Troubleshooting Main

712 Maintenance and Troubleshooting Guide March 2008

Page 715: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 713

<op_name> operation failed for file <file_name>The named operation on the named file did not complete successfully.

Description

A process tried to complete an operation, often a read or write, on a file and was unsuccessful.

Page 716: PC4 Troubleshooting Main

714 Maintenance and Troubleshooting Guide March 2008

Page 717: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 715

<string><string>- Operator number returned wrong <num1>, job number <num2>

An operator slot could not be released.

Description

An operator slot could not be released.

Page 718: PC4 Troubleshooting Main

716 Maintenance and Troubleshooting Guide March 2008

Page 719: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 717

Operator slot semaphore not availableA process tries to access the operator slot base in shared memory and cannot.

Description

A process tries to access the operator slot base in shared memory and cannot. This error can occur when accessing the operator slot base or releasing it.

Page 720: PC4 Troubleshooting Main

718 Maintenance and Troubleshooting Guide March 2008

Page 721: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 719

Headset value (<headset_value>, <return_value>) out of bound

When the operator process is running in test mode, a headset value is encountered that is not within the prescribed headset values.

Description

When the operator process is running in test mode, a headset value is encountered that is not within the prescribed headset values

Page 722: PC4 Troubleshooting Main

720 Maintenance and Troubleshooting Guide March 2008

Page 723: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 721

Outbound agents only permittedAn agent other than an outbound agent tried to access an outbound job.

Description

An agent other than an outbound agent tried to access an outbound job.

Page 724: PC4 Troubleshooting Main

722 Maintenance and Troubleshooting Guide March 2008

Page 725: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 723

Pattern error at line <number>A process is running a script and finds a pattern error in the script at line number <num>.

Description

A process is running a script and finds a pattern error in the script at line number <num>.

Page 726: PC4 Troubleshooting Main

724 Maintenance and Troubleshooting Guide March 2008

Page 727: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 725

Pattern errorA process needs to make a selection of data and the pattern used for the selection contains an error.

Description

A process needs to make a selection of data and the pattern used for the selection contains an error. This error can occur reading and writing tapes, selecting fields from a record, and other areas where a selection criteria in the form of a pattern is used. The error message references the code that generated the error message.

Page 728: PC4 Troubleshooting Main

726 Maintenance and Troubleshooting Guide March 2008

Page 729: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 727

Telephone line not availableA telephone line is not available.

Description

A telephone line is not available for the agent�s current activity. The agent activity may be:

a. Trying to hang up a call, but there is no call to hang up.

b. Trying to place a call on hold and there is no open telephone line to place on hold.

c. Transferring a call and Avaya Proactive Contact does not have a telephone line available to place the transfer call.

d. Dialing preview (no telephone line available). This message results when Avaya Proactive Contact is placing the preview call.

e. Performing a recall scheduled for current date and time, but no telephone line is available to place the outbound call.

f. While there was a call on hold, it is not available to restore. The customer hung up while on hold.

Page 730: PC4 Troubleshooting Main

728 Maintenance and Troubleshooting Guide March 2008

Page 731: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 729

Telephone line not offhookAn agent tried an activity that required an offhook phone and the phone was not off hook.

Description

An agent tried an activity that required an offhook phone and the phone was not off hook. The agent was trying to do one of the following activities:

● Adjust the headset volume and has an open telephone line that is on hold.

● Place a call on hold while there is an open telephone line, there is no call to place on hold. This message may mean the agent has already placed the call on hold.

● Transfer a call and there is no call to transfer.

● Take a call off hold and there is no call on hold.

Page 732: PC4 Troubleshooting Main

730 Maintenance and Troubleshooting Guide March 2008

Page 733: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 731

Phone number too longIn converting a calling list phone number to the standard to dial format, the length of the telephone number becomes too long.

Description

In converting a calling list phone number to the standard to dial format, the length of the telephone number becomes too long.

Resolution

To resolve this issue, follow these steps:

1. Open the calling list that generated the error.

2. Inspect the phone numbers for irregularities.

3. Shorten any abnormally long phone numbers.

4. Rerun the process.

Page 734: PC4 Troubleshooting Main

732 Maintenance and Troubleshooting Guide March 2008

Page 735: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 733

Timed out waiting for response from porterWhile an agent was manually making calls, the screen failed to display the number, because porter timed out.

Description

While an agent was manually making calls, the screen failed to display the number, because porter timed out.

Page 736: PC4 Troubleshooting Main

734 Maintenance and Troubleshooting Guide March 2008

Page 737: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 735

Password can not be changed, change limit not expiredAn agent attempted to change a password and could not.

Description

An agent attempted to change a password and could not because the default time limit for password changes had not been reached.

Page 738: PC4 Troubleshooting Main

736 Maintenance and Troubleshooting Guide March 2008

Page 739: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 737

Preview record search failed to initializeThe preview record search (pvrs) failed to initialize.

Description

The preview record search (pvrs) failed to initialize. Note that several conditions must be met before pvrs runs successfully. Consult the pvrs_helpers.c source code for more information.

Page 740: PC4 Troubleshooting Main

738 Maintenance and Troubleshooting Guide March 2008

Page 741: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 739

Changes to record not savedAn agent made changes to a record that were not saved.

Description

An agent made changes to a record that were not saved. It may be that the record was locked so that changes could not be made.

Page 742: PC4 Troubleshooting Main

740 Maintenance and Troubleshooting Guide March 2008

Page 743: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 741

Recall can't be less than <num> minutesA recall cannot be less than <num> minutes from the current time.

Description

A agent has tried to set up a recall that is less than the number of minutes allowed. This recall limit is set by the RECALLLIMIT entry in the locale.cfg file.

Page 744: PC4 Troubleshooting Main

742 Maintenance and Troubleshooting Guide March 2008

Page 745: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 743

Range does not come after previous rangeA process accessed the recall attempt range and found an error in the attempt range parameter.

Description

A process accessed the recall attempt range and found an error in the attempt range parameter.

Page 746: PC4 Troubleshooting Main

744 Maintenance and Troubleshooting Guide March 2008

Page 747: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 745

Recall time and date outside timezoneRecall time is outside the limits for the time zone.

Description

The recall time setting is for the Avaya Proactive Contact system time. However, the telephone to recall is in a different time zone. In that time zone, the recall time setting is outside the legal boundaries for placing calls to customers.

Page 748: PC4 Troubleshooting Main

746 Maintenance and Troubleshooting Guide March 2008

Page 749: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 747

Record is no longer availableA process tried to access a record that is no longer available.

Description

A process tried to access a record that is no longer available. In most cases the process is either a call transfer or involves editing a record.

Page 750: PC4 Troubleshooting Main

748 Maintenance and Troubleshooting Guide March 2008

Page 751: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 749

Record currently in useA call strategy process tired to access a record, but it was in use by another process.

Description

A call strategy process tired to access a record, but it was in use by another process. This means the file is locked by the other process.

Page 752: PC4 Troubleshooting Main

750 Maintenance and Troubleshooting Guide March 2008

Page 753: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 751

Rejected phone number (L<num>)A process is checking phone numbers in a calling list and rejects the phone number on line <num> when comparing it to the standard phone number for the list.

Description

A process is checking phone numbers in a calling list and rejects the phone number on line <num> when comparing it to the standard phone number for the list.

Page 754: PC4 Troubleshooting Main

752 Maintenance and Troubleshooting Guide March 2008

Page 755: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 753

Field entry is requiredAn agent has left a required field on a screen blank.

Description

An agent has left a required field on a screen blank.

Page 756: PC4 Troubleshooting Main

754 Maintenance and Troubleshooting Guide March 2008

Page 757: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 755

Route End Error: RegReqID = <num>, CrossRefID = <num>, Error = <num>

For some reason the route end is not available.

Description

This error message has two distinct variations:

1. Route End Error: REqREqID??=1, CrossRefID??=70585, Error = 33

Avaya Proactive Contact with CTI uses an extension to an announcement port on the switch to play voice messages and this is not set up.

2. Route End Error: REqREqID??=1, CrossRefID??=12661, Error = 14

A CTI process encountered a invalid destination address.

Page 758: PC4 Troubleshooting Main

756 Maintenance and Troubleshooting Guide March 2008

Page 759: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 757

Report failed, system out of spaceA process was attempting to create a report and ran out of disk space.

Description

A process was attempting to create a report and ran out of disk space.

Page 760: PC4 Troubleshooting Main

758 Maintenance and Troubleshooting Guide March 2008

Page 761: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 759

Molocale - unknown language name <lang>During language localization, the language provided as a secondary language for display is unrecognized.

Description

The LANG_SECONDARY keyword in the $VOICEDIR/etc/master.cfg file is set to an unrecognized language.

Page 762: PC4 Troubleshooting Main

760 Maintenance and Troubleshooting Guide March 2008

Page 763: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 761

Selection list not available for useA client application has tried to start one or more jobs and was unsuccessful.

Description

A client application has tried to start one or more jobs and was unsuccessful. The process could not use the record selection list for one or more jobs because it was unavailable.

Page 764: PC4 Troubleshooting Main

762 Maintenance and Troubleshooting Guide March 2008

Page 765: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 763

Could not verify selection list for jobA client application has tried to start one or more jobs and was unsuccessful.

Description

A client application has tried to start one or more jobs and was unsuccessful. The process could could not verify the record selection list for the job. This error occurs if the new list download has happened after the selection was run.

Page 766: PC4 Troubleshooting Main

764 Maintenance and Troubleshooting Guide March 2008

Page 767: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 765

Selection list not created with this calling listA client application has tried to start one or more jobs and was unsuccessful.

Description

A client application has tried to start one or more jobs and was unsuccessful. The selection list in use was not created with this calling list.

Page 768: PC4 Troubleshooting Main

766 Maintenance and Troubleshooting Guide March 2008

Page 769: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 767

Could not verify selection list for jobA client application has tried to start one or more jobs and was unsuccessful.

Description

A client application has tried to start one or more jobs and was unsuccessful. The process could could not verify the record selection list for the job. This error occurs if the new list download has happened after the selection was run.

Resolution

To resolve this issue, rerun the selection.

Page 770: PC4 Troubleshooting Main

768 Maintenance and Troubleshooting Guide March 2008

Page 771: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 769

Cannot find service in /etc/servicesA process attempts to find the IP address of a service and the service does not exist.

Description

A process attempts to find the IP address of a service and the service does not exist. This error occurs in a module that provides functions to FileStore, Directory and DateGenerator functions elsewhere in the code.

Page 772: PC4 Troubleshooting Main

770 Maintenance and Troubleshooting Guide March 2008

Page 773: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 771

Caught signal number <num>Many different processes generate this error.

Description

Many different processes generate this error.

Page 774: PC4 Troubleshooting Main

772 Maintenance and Troubleshooting Guide March 2008

Page 775: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 773

Caught signal <num> and terminatedA process got a signal <num> and terminated.

Description

The error message identifies the process that terminated and the signal number that caused the termination.

Page 776: PC4 Troubleshooting Main

774 Maintenance and Troubleshooting Guide March 2008

Page 777: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 775

Socket call failedA server process attempted to accept a client connect request and the socket request failed.

Description

A server process attempted to accept a client connect request and the socket request failed. This error occurs in a module that provides functions to FileStore, Directory and DateGenerator functions elsewhere in the code.

Page 778: PC4 Troubleshooting Main

776 Maintenance and Troubleshooting Guide March 2008

Page 779: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 777

Unable to setup listen on socketA server process attempted to accept a client connect request and cannot set up to listen on the socket.

Description

A server process attempted to accept a client connect request and cannot set up to listen on the socket. This error occurs in a module that provides functions to FileStore, Directory and DateGenerator functions elsewhere in the code.

Page 780: PC4 Troubleshooting Main

778 Maintenance and Troubleshooting Guide March 2008

Page 781: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 779

Socket failedA socket for a connection to a server failed.

Description

While trying to access a calling list, a socket for a connection to the server hosting the calling list failed.

Page 782: PC4 Troubleshooting Main

780 Maintenance and Troubleshooting Guide March 2008

Page 783: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 781

Socket connection to list server running on <name> failedA socket connection to a list server running on the named server failed.

Description

While trying to access a calling list, a socket connection to a list server running on the named server failed.

Page 784: PC4 Troubleshooting Main

782 Maintenance and Troubleshooting Guide March 2008

Page 785: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 783

STATUSFLAG field missingThe current record does contain a STATUSFLAG field.

Description

During an attempt to mark a record as do not call, the system did not find a STATUSFLAG field in the record.

Page 786: PC4 Troubleshooting Main

784 Maintenance and Troubleshooting Guide March 2008

Page 787: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 785

Failed to process line (<line_buffer_name>)As a process attempts to read the switch configuration file, it cannot process a line of the file.

Description

As a process attempts to read the switch configuration file, it cannot process a line of the file.

Page 788: PC4 Troubleshooting Main

786 Maintenance and Troubleshooting Guide March 2008

Page 789: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 787

tget returned error number <num> raising signal <num>The user typed input that causes the system to terminate.

Description

The user typed input that causes the system to terminate.

Page 790: PC4 Troubleshooting Main

788 Maintenance and Troubleshooting Guide March 2008

Page 791: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 789

<string>-<string>This error message identifies the process that generated the error message and the object of the process.

Description

This error message identifies the process that generated the error message and the object of the process.

Page 792: PC4 Troubleshooting Main

790 Maintenance and Troubleshooting Guide March 2008

Page 793: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 791

Timed out waiting for <string> confirmationA process, waiting for an IPC message reply, times out.

Description

A process, waiting for an IPC message reply, times out.

Page 794: PC4 Troubleshooting Main

792 Maintenance and Troubleshooting Guide March 2008

Page 795: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 793

Calling list <name> is not in shared memoryA calling list/dictionary <name> is being processing and the calling list/dictionary cannot be loaded into shared memory.

Description

A calling list/dictionary <name> is being processing and the calling list/dictionary cannot be loaded into shared memory.

Page 796: PC4 Troubleshooting Main

794 Maintenance and Troubleshooting Guide March 2008

Page 797: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 795

Calling list line count does not match shared memoryWhile processing a calling list, the system determines that the calling list line count does not match the shared memory version.

Description

While processing a calling list, the system determines that the calling list line count does not match the shared memory version.

Page 798: PC4 Troubleshooting Main

796 Maintenance and Troubleshooting Guide March 2008

Page 799: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 797

Invalid normal trunk equipment number <num> A process accessed a trunk number for a headset or other equipment and found an invalid value.

Description

A process accessed a trunk number for a headset or other equipment and found an invalid value.The $VOICEDIR/config/dgswitch.cfg file contains the accepted trunk port numbers.

Page 800: PC4 Troubleshooting Main

798 Maintenance and Troubleshooting Guide March 2008

Page 801: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 799

Normal trunk port number <num> out of rangeA process accessed the trunk port numbers and found an out of range value.

Description

A process accessed the trunk port numbers and found an out of range value. The $VOICEDIR/config/dgswitch.cfg file contains the accepted trunk port numbers.

Page 802: PC4 Troubleshooting Main

800 Maintenance and Troubleshooting Guide March 2008

Page 803: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 801

Unable to bind to local addressA server process attempted to accept a client connect request and cannot bind to the local address.

Description

A server process attempted to accept a client connect request and cannot bind to the local address. This error occurs in a module that provides functions to FileStore, Directory and DateGenerator functions elsewhere in the code.

Page 804: PC4 Troubleshooting Main

802 Maintenance and Troubleshooting Guide March 2008

Page 805: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 803

Unable to accept connection on socketA server process attempted to accept a client connect request and cannot accept connection on the socket.

Description

A server process attempted to accept a client connect request and cannot accept connection on the socket. This error occurs in a module that provides functions to FileStore, Directory and DateGenerator functions elsewhere in the code.

Page 806: PC4 Troubleshooting Main

804 Maintenance and Troubleshooting Guide March 2008

Page 807: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 805

Unable to access host <name> using nameA process tried to unsuccessfully access a host using its name.

Description

A process associated with calling lists tried to unsuccessfully access a host using its name. If the process is trying to establish a connection with the list server on the server identified in the list client host_name, it uses the default LSERVPORT value for the server.

Page 808: PC4 Troubleshooting Main

806 Maintenance and Troubleshooting Guide March 2008

Page 809: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 807

Unable to connect to socketA client process attempted to connect to a server and cannot connect to the socket on the server.

Description

A client process attempted to connect to a server and cannot connect to the socket on the server. This error occurs in a module that provides functions to FileStore, Directory and DateGenerator functions elsewhere in the code.

Page 810: PC4 Troubleshooting Main

808 Maintenance and Troubleshooting Guide March 2008

Page 811: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 809

Failed to create directoryA process attempted to create a directory and failed.

Description

This error can occur in a wide range of circumstances. The error message contains the name of the directory that could not be created.

Page 812: PC4 Troubleshooting Main

810 Maintenance and Troubleshooting Guide March 2008

Page 813: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 811

Failed to read calling list definitionA process tried to read a calling list definition and failed.

Description

A process tried to read a calling list definition and failed. This error message can occur in a wide range of circumstances.

Page 814: PC4 Troubleshooting Main

812 Maintenance and Troubleshooting Guide March 2008

Page 815: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 813

Unable to open list <calling_list_name>A process tried to unsuccessfully open the named calling list.

Description

A process tried to unsuccessfully open the named calling list.

Page 816: PC4 Troubleshooting Main

814 Maintenance and Troubleshooting Guide March 2008

Page 817: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 815

Process unable to send <string> to <process_name>A process needs to send a string to another process and cannot.

Description

A process needs to send a string to another process and cannot. The error message names both processes and the string.

Page 818: PC4 Troubleshooting Main

816 Maintenance and Troubleshooting Guide March 2008

Page 819: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 817

Unable to send data to socketA process attempted to send data to a socket and the connection is gone.

Description

A process attempted to send data to a socket and the connection is gone. This error occurs in a module that provides functions to FileStore, Directory and DateGenerator functions elsewhere in the code.

Page 820: PC4 Troubleshooting Main

818 Maintenance and Troubleshooting Guide March 2008

Page 821: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 819

Molocale - failed to set locale <name>The system is trying to set a language for a locale and cannot.

Description

The system is trying to set a language for a locale and cannot.

Page 822: PC4 Troubleshooting Main

820 Maintenance and Troubleshooting Guide March 2008

Page 823: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 821

Call blending is not availableAn agent is trying to log on to dispatcher for call blending when call blending is not available.

Description

An agent is trying to log on to dispatcher for call blending when call blending is not available. The dispatcher process acquires and releases agents for outbound calling. Dispatcher is the sole interface between the Agent Blending system and the outbound calling system.

Page 824: PC4 Troubleshooting Main

822 Maintenance and Troubleshooting Guide March 2008

Page 825: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 823

Unequal phone number field lengths in file <filename>A process is reading the file <filename> and finds unequal phone number lengths.

Description

A process is reading the file <filename> and finds unequal phone number lengths. The function that generates this error is used to read a file such as. callselnum that contains numbers in text string form.

Page 826: PC4 Troubleshooting Main

824 Maintenance and Troubleshooting Guide March 2008

Page 827: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 825

Unknown Command message - <command><command> is the text string that the agent binary received as the command and did not recognize.

Description

The error typically occurs when an API call contains an undefined command.

Page 828: PC4 Troubleshooting Main

826 Maintenance and Troubleshooting Guide March 2008

Page 829: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 827

Unknown IPC message - <string>While processing IPC messages, the system encounters <string> that is not a known IPC message.

Description

While processing IPC messages, the system encounters <string> that is not a known IPC message.

Page 830: PC4 Troubleshooting Main

828 Maintenance and Troubleshooting Guide March 2008

Page 831: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 829

Incorrect job typeAgent command issued with an unknown job type.

Description

This error most likely occurred while executing the AGTListJobs API call. The job types are

● (A) all

● (I) inbound

● (B) blend

● (M) Managed Dialing

● (O) outbound, including Unit Work List and Sales Verification

Page 832: PC4 Troubleshooting Main

830 Maintenance and Troubleshooting Guide March 2008

Page 833: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 831

Unknown screen typeAn agent is attempting to use a screen type that is unknown to the system.

Description

An agent is attempting to use a screen type that is unknown to the system. Screen types are defined in *.init files.

Page 834: PC4 Troubleshooting Main

832 Maintenance and Troubleshooting Guide March 2008

Page 835: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 833

Unit value not found, or unavailableA unit work list was not found.

Description

An agent attempted to attach to a unit work list that either did not exist or was in use.

Page 836: PC4 Troubleshooting Main

834 Maintenance and Troubleshooting Guide March 2008

Page 837: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 835

Linking between virtual agent jobs and non-virtual jobs is not permitted

In an effort to link one job to another, one job is virtual and the other is non-virtual.

Description

When linking two agent jobs, both jobs must be either virtual or non-virtual. This error occurs when one job is virtual and the other is non-virtual which nullifies the requested link.

Page 838: PC4 Troubleshooting Main

836 Maintenance and Troubleshooting Guide March 2008

Page 839: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 837

Unable to open fileCalling code cannot open specified file.

Description

This error is one of the most common errors displayed by Avaya Proactive Contact. However, in almost all cases, the error message contains the name of the process that generated the error code and the name of the file that the process could not open.

Page 840: PC4 Troubleshooting Main

838 Maintenance and Troubleshooting Guide March 2008

Page 841: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 839

Failed to find screen <name>System could not display Window�s application <name> screen.

Description

System could not display Window�s application <name> screen. This error occurs when trying to load the information held in shared memory.

Page 842: PC4 Troubleshooting Main

840 Maintenance and Troubleshooting Guide March 2008

Page 843: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 841

Write errorAn attempt to write to a file generated an error.

Description

This error can occur for a variety of these reasons:

● In writing a calling list, the error message tells you that the process wrote one value when another was expected.

Page 844: PC4 Troubleshooting Main

842 Maintenance and Troubleshooting Guide March 2008

Page 845: PC4 Troubleshooting Main

Maintenance and Troubleshooting Guide March 2008 843

Index

Aarchive

restoring files . . . . . . . . . . . . . . . . . . 45verifying archive contents . . . . . . . . . . . . 46verifying files . . . . . . . . . . . . . . . . . . 46

Bbacking up

a specific calling list . . . . . . . . . . . . . . . 48calling lists, all . . . . . . . . . . . . . . . . . 47complete system . . . . . . . . . . . . . . . . 41database . . . . . . . . . . . . . . . . . . . . 49guidelines . . . . . . . . . . . . . . . . . . . 39operating system . . . . . . . . . . . . . . . . 41system and calling lists . . . . . . . . . . . . . 42system configuration files . . . . . . . . . . . . 43system data and statistics files. . . . . . . . . . 44system files . . . . . . . . . . . . . . . . . . 42

Ccalling lists

backing up a specific list . . . . . . . . . . . . 48backing up all. . . . . . . . . . . . . . . . . . 47backing up one . . . . . . . . . . . . . . . . . 42restoring . . . . . . . . . . . . . . . . . . . . 48restoring a specific list . . . . . . . . . . . . . 49

DDAT drive status . . . . . . . . . . . . . . . . . . 40data

backing up . . . . . . . . . . . . . . . . . . . 49backing up statistics files . . . . . . . . . . . . 44restoring . . . . . . . . . . . . . . . . . . . . 50restoring from . . . . . . . . . . . . . . . . . 44

databasebacking up . . . . . . . . . . . . . . . . . . . 49restoring . . . . . . . . . . . . . . . . . . . . 50

DDS tape . . . . . . . . . . . . . . . . . . . . . 39

Ffbackup utility . . . . . . . . . . . . . . . . . . . 44files

backing up system. . . . . . . . . . . . . . . . 42backing up system configuration . . . . . . . . . 43backing up system data . . . . . . . . . . . . . 44verifying in archive. . . . . . . . . . . . . . . . 46

Gguidelines

backing up . . . . . . . . . . . . . . . . . . . 39restoring . . . . . . . . . . . . . . . . . . . . 39

LLEDs, tape drive . . . . . . . . . . . . . . . . . . 40lists

backing up . . . . . . . . . . . . . . . . . . . 48restoring . . . . . . . . . . . . . . . . . . . . 49

Mmonitoring

DAT drive status, LEDs . . . . . . . . . . . . . 40

Ooperating system, backing up . . . . . . . . . . . . 41/opt/avaya/pds/account/* . . . . . . . . . . 44/opt/avaya/pds/lists/*.stat. . . . . . . . . 44/opt/avaya/pds/lists/history/*.hist . . . 44/opt/avaya/pds/xfer/clist . . . . . . . . 42, 47/opt/oracle/oradata . . . . . . . . . . . . 49, 50

Rrestoring

a specific calling list . . . . . . . . . . . . . . . 49calling list . . . . . . . . . . . . . . . . . . . . 48data, from. . . . . . . . . . . . . . . . . . . . 44database . . . . . . . . . . . . . . . . . . . . 50files from archive . . . . . . . . . . . . . . . . 45guidelines. . . . . . . . . . . . . . . . . . . . 39

Sstatistics

backing up system data . . . . . . . . . . . . . 44system

Page 846: PC4 Troubleshooting Main

844 Maintenance and Troubleshooting Guide March 2008

back up . . . . . . . . . . . . . . . . . . . . 41backing up calling lists . . . . . . . . . . . . . 42backing up configuration files . . . . . . . . . . 43backing up files . . . . . . . . . . . . . . . . . 42

Ttape storage environment . . . . . . . . . . . . . 39

Vvalidating

archive contents . . . . . . . . . . . . . . . . 46files in archive . . . . . . . . . . . . . . . . . 46

verifyingarchive contents . . . . . . . . . . . . . . . . 46files in archive . . . . . . . . . . . . . . . . . 46