AEP Events and Associated Alarm

Avaya Aura Experience Portal events and
associated alarms
February 2012
2012 Avaya Inc. different number of licenses or units of capacity is specified in the
Documentation or other materials available to End User. Designated
All Rights Reserved. Processor means a single stand-alone computing device. Server
means a Designated Processor that hosts a software application to be
Notice accessed by multiple users. Software means the computer programs
in object code, originally licensed by Avaya and ultimately utilized by
While reasonable efforts have been made to ensure that the
End User, whether as stand-alone Products or pre-installed on
information in this document is complete and accurate at the time of
Hardware. Hardware means the standard hardware originally sold by
printing, Avaya assumes no liability for any errors. Avaya reserves the
Avaya and ultimately utilized by End User.
right to make changes and corrections to the information in this
document without the obligation to notify any person or organization of License types
such changes.
Concurrent User License (CU). End User may install and use the
Documentation disclaimer Software on multiple Designated Processors or one or more Servers,
so long as only the licensed number of Units are accessing and using
Documentation means information published by Avaya in varying
the Software at any given time. A Unit means the unit on which Avaya,
mediums which may include product information, operating instructions
at its sole discretion, bases the pricing of its licenses and can be,
and performance specifications that Avaya generally makes available
without limitation, an agent, port or user, an e-mail or voice mail account
to users of its products. Documentation does not include marketing
in the name of a person or corporate function (e.g., webmaster or
materials. Avaya shall not be responsible for any modifications,
helpdesk), or a directory entry in the administrative database utilized
additions, or deletions to the original published version of
by the Software that permits one user to interface with the Software.
documentation unless such modifications, additions, or deletions were
Units may be linked to a specific, identified Server.
performed by Avaya. End User agrees to indemnify and hold harmless
Avaya, Avaya's agents, servants and employees against all claims, Shrinkwrap License (SR). Customer may install and use the Software
lawsuits, demands and judgments arising out of, or in connection with, in accordance with the terms and conditions of the applicable license
subsequent modifications, additions or deletions to this documentation, agreements, such as shrinkwrap or clickthrough license
to the extent made by End User. accompanying or applicable to the Software (Shrinkwrap License).
(see Third-party Components for more information).
Link disclaimer
Avaya is not responsible for the contents or reliability of any linked Web Copyright
sites referenced within this site or documentation provided by Avaya. Except where expressly stated otherwise, no use should be made of
Avaya is not responsible for the accuracy of any information, statement materials on this site, the Documentation, Software, or Hardware
or content provided on these sites and does not necessarily endorse provided by Avaya. All content on this site, the documentation and the
the products, services, or information described or offered within them. Product provided by Avaya including the selection, arrangement and
Avaya does not guarantee that these links will work all the time and has design of the content is owned either by Avaya or its licensors and is
no control over the availability of the linked pages. protected by copyright and other intellectual property laws including the
sui generis rights relating to the protection of databases. You may not
Warranty
modify, copy, reproduce, republish, upload, post, transmit or distribute
Avaya provides a limited warranty on its Hardware and Software in any way any content, in whole or in part, including any code and
(Product(s)). Refer to your sales agreement to establish the terms of software unless expressly authorized by Avaya. Unauthorized
the limited warranty. In addition, Avayas standard warranty language, reproduction, transmission, dissemination, storage, and or use without
as well as information regarding support for this Product while under the express written consent of Avaya can be a criminal, as well as a
warranty is available to Avaya customers and other parties through the civil offense under the applicable law.
Avaya Support Web site: http://support.avaya.com. Please note that if
you acquired the Product(s) from an authorized Avaya reseller outside Third-party components
of the United States and Canada, the warranty is provided to you by Certain software programs or portions thereof included in the Product
said Avaya reseller and not by Avaya. may contain software distributed under third party agreements (Third
Party Components), which may contain terms that expand or limit
Licenses
rights to use certain portions of the Product (Third Party Terms).
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA Information regarding distributed Linux OS source code (for those
WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ ARE Products that have distributed the Linux OS source code), and
APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR identifying the copyright holders of the Third Party Components and the
INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., Third Party Terms that apply to them is available on the Avaya Support
ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER Web site: http://support.avaya.com/Copyright.
(AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH
AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS Preventing Toll Fraud
OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES Toll fraud is the unauthorized use of your telecommunications system
NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED by an unauthorized party (for example, a person who is not a corporate
FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN employee, agent, subcontractor, or is not working on your company's
AVAYA AUTHORIZED RESELLER; AVAYA RESERVES THE RIGHT behalf). Be aware that there can be a risk of Toll Fraud associated with
TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE your system and that, if Toll Fraud occurs, it can result in substantial
USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY additional charges for your telecommunications services.
INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR
AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF Avaya Toll Fraud Intervention
YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING,
DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER If you suspect that you are being victimized by Toll Fraud and you need
REFERRED TO INTERCHANGEABLY AS YOU AND END USER), technical assistance or support, call Technical Service Center Toll
AGREE TO THESE TERMS AND CONDITIONS AND CREATE A Fraud Intervention Hotline at +1-800-643-2353 for the United States
BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE and Canada. For additional support telephone numbers, see the Avaya
APPLICABLE AVAYA AFFILIATE ( AVAYA). Support Web site: http://support.avaya.com. Suspected security
vulnerabilities with Avaya products should be reported to Avaya by
Avaya grants End User a license within the scope of the license types sending mail to: securityalerts@avaya.com.
described below. The applicable number of licenses and units of
capacity for which the license is granted will be one (1), unless a
2 Avaya Aura Experience Portal events and associated alarms February 2012
Comments? infodev@avaya.com
Trademarks
Avaya, the Avaya logo, Avaya Aura Experience Portal, AvayaAura
Communication Manager, and Avaya Aura Orchestration Designer
are either registered trademarks or trademarks of Avaya Inc. in the
United States of America and/or other jurisdictions.
All non-Avaya trademarks are the property of their respective owners,

and Linux is a registered trademark of Linus Torvalds.
Downloading Documentation
For the most current versions of Documentation, see the Avaya
Support Web site: http://support.avaya.com.
Contact Avaya Support

Avaya provides a telephone number for you to use to report problems
or to ask questions about your Product. The support telephone number
is 1-800-242-2121 in the United States. For additional support
telephone numbers, see the Avaya Web site: http://support.avaya.com.
Avaya Aura Experience Portal events and associated alarms February 2012 3
Contents
Chapter 1: Events and associated alarms overview........................................................ 37

Chapter 2: PADMN events.................................................................................................. 39
PADMN00001........................................................................................................................................... 39
PADMN00002........................................................................................................................................... 39
PADMN00003........................................................................................................................................... 40
PADMN00004........................................................................................................................................... 40
PADMN00005........................................................................................................................................... 41
PADMN00006........................................................................................................................................... 41
PADMN00007........................................................................................................................................... 42
PADMN01001........................................................................................................................................... 42
PADMN01002........................................................................................................................................... 43
PADMN01003........................................................................................................................................... 43
PADMN01004........................................................................................................................................... 44
PADMN01005........................................................................................................................................... 45
PADMN01006........................................................................................................................................... 45
PADMN01007........................................................................................................................................... 46
PADMN01008........................................................................................................................................... 46
PADMN01009........................................................................................................................................... 47
PADMN01010........................................................................................................................................... 48
PADMN01011............................................................................................................................................ 48
PADMN01101............................................................................................................................................ 49
PADMN01102............................................................................................................................................ 49
PADMN01103............................................................................................................................................ 50
PADMN01104............................................................................................................................................ 50
PADMN01105............................................................................................................................................ 51
PADMN01106............................................................................................................................................ 51
PADMN01107............................................................................................................................................ 52
PADMN01108............................................................................................................................................ 52
PADMN01109............................................................................................................................................ 53
PADMN01110............................................................................................................................................ 54
PADMN01111............................................................................................................................................ 54
PADMN01112............................................................................................................................................ 55
PADMN01113............................................................................................................................................ 55
PADMN01114............................................................................................................................................ 56
PADMN01115............................................................................................................................................ 56
PADMN01116............................................................................................................................................ 57
PADMN01117............................................................................................................................................ 58
PADMN01118............................................................................................................................................ 58
PADMN01119............................................................................................................................................ 59
PADMN01120............................................................................................................................................ 59
PADMN01121............................................................................................................................................ 60
PADMN01122............................................................................................................................................ 60
PADMN01123............................................................................................................................................ 61
PADMN01124............................................................................................................................................ 61
PADMN01125............................................................................................................................................ 62
PADMN01126............................................................................................................................................ 63
PADMN01127............................................................................................................................................ 63
PADMN01128............................................................................................................................................ 64
PADMN01129............................................................................................................................................ 64
PADMN01130............................................................................................................................................ 65
PADMN01131............................................................................................................................................ 66
PADMN01401........................................................................................................................................... 66
PADMN01402........................................................................................................................................... 67
PADMN01403........................................................................................................................................... 67
PADMN01404........................................................................................................................................... 68
PADMN01501........................................................................................................................................... 68
PADMN01502........................................................................................................................................... 69
PADMN01503........................................................................................................................................... 69
PADMN01504........................................................................................................................................... 70
PADMN01801........................................................................................................................................... 70
PADMN01802........................................................................................................................................... 71
PADMN01803........................................................................................................................................... 71
PADMN02101........................................................................................................................................... 72
PADMN02102........................................................................................................................................... 72
PADMN02103........................................................................................................................................... 73
PADMN02104........................................................................................................................................... 73
PADMN02105........................................................................................................................................... 74
PADMN02106........................................................................................................................................... 75
PADMN02301........................................................................................................................................... 75
PADMN02302........................................................................................................................................... 76
PADMN02303........................................................................................................................................... 77
PADMN02304........................................................................................................................................... 77
PADMN02305........................................................................................................................................... 78
PADMN02307........................................................................................................................................... 78
PADMN02401........................................................................................................................................... 79
PADMN02402........................................................................................................................................... 79
PADMN02403........................................................................................................................................... 80
PADMN03601........................................................................................................................................... 80
PADMN03701........................................................................................................................................... 81
PADMN03702........................................................................................................................................... 82
PADMN10001........................................................................................................................................... 82
PADMN10002........................................................................................................................................... 83
PADMN10003........................................................................................................................................... 84
PADMN10004........................................................................................................................................... 85
PADMN10005........................................................................................................................................... 87
PADMN10006........................................................................................................................................... 87
PADMN10007........................................................................................................................................... 88
Chapter 3: PADTL events................................................................................................... 91
PADTL00018............................................................................................................................................. 91
PADTL00101............................................................................................................................................. 91
PADTL00102............................................................................................................................................. 92
PADTL00103............................................................................................................................................. 92
Chapter 4: PAIWS events................................................................................................... 95
PAIWS_E001............................................................................................................................................ 95
PAIWS_E002............................................................................................................................................ 95
PAIWS_E003............................................................................................................................................ 96
PAIWS_E004............................................................................................................................................ 96
PAIWS_E005............................................................................................................................................ 97
PAIWS_E006............................................................................................................................................ 97
PAIWS_E007............................................................................................................................................ 98
PAIWS_E008............................................................................................................................................ 99
PAIWS_E009............................................................................................................................................ 99
PAIWS_E010............................................................................................................................................ 100
PAIWS_E011............................................................................................................................................. 101
PAIWS_E012............................................................................................................................................ 101
PAIWS_E013............................................................................................................................................ 102
PAIWS_F001............................................................................................................................................. 103
PAIWS_F002............................................................................................................................................. 104
PAIWS_W001........................................................................................................................................... 105
PAIWS_W002........................................................................................................................................... 106
PAIWS_W003........................................................................................................................................... 106
PAIWS_W004........................................................................................................................................... 107
PAIWS_W005........................................................................................................................................... 107
PAIWS_W006........................................................................................................................................... 108
PAIWS_W007........................................................................................................................................... 109
PAIWS_W008........................................................................................................................................... 109
PAIWS_W009........................................................................................................................................... 110
PAIWS_W010........................................................................................................................................... 110
PAIWS_W011............................................................................................................................................ 111
PAIWS_W012........................................................................................................................................... 111
PAIWS_W013........................................................................................................................................... 112
PAIWS_W014........................................................................................................................................... 113
PAIWS_W015........................................................................................................................................... 113
PAIWS_W016........................................................................................................................................... 114
PAIWS_W017........................................................................................................................................... 114
PAIWS_W018........................................................................................................................................... 115
PAIWS_W019........................................................................................................................................... 116
PAIWS_W020........................................................................................................................................... 116
PAIWS_W021........................................................................................................................................... 117
PAIWS_W022........................................................................................................................................... 118
PAIWS_W023........................................................................................................................................... 118
PAIWS_W024........................................................................................................................................... 119
PAIWS_W025........................................................................................................................................... 119
PAIWS_W026........................................................................................................................................... 120
PAIWS_W027........................................................................................................................................... 120
PAIWS_W028........................................................................................................................................... 121
PAIWS_W029........................................................................................................................................... 122
PAIWS_W030........................................................................................................................................... 122
PAIWS_W031........................................................................................................................................... 123
PAIWS_W032........................................................................................................................................... 123
PAIWS_W033........................................................................................................................................... 124
Chapter 5: PALOG events.................................................................................................. 127
PALOG00001............................................................................................................................................ 127
PALOG00002............................................................................................................................................ 127
PALOG00003............................................................................................................................................ 128
PALOG00004............................................................................................................................................ 129
PALOG00005............................................................................................................................................ 129
PALOG00006............................................................................................................................................ 130
PALOG00007............................................................................................................................................ 130
PALOG00008............................................................................................................................................ 131
PALOG00009............................................................................................................................................ 131
PALOG00010............................................................................................................................................ 132
PALOG00011............................................................................................................................................ 133
PALOG00012............................................................................................................................................ 133
PALOG00013............................................................................................................................................ 134
PALOG00014............................................................................................................................................ 135
PALOG00015............................................................................................................................................ 135
PALOG00016............................................................................................................................................ 136
PALOG00017............................................................................................................................................ 137
Chapter 6: PAPP events..................................................................................................... 139
PAPP_00001............................................................................................................................................. 139
PAPP_00002............................................................................................................................................. 140
PAPP_00003............................................................................................................................................. 141
Chapter 7: PASR events..................................................................................................... 143
PASR_00001............................................................................................................................................. 143
PASR_00002............................................................................................................................................. 143
PASR_00003............................................................................................................................................. 144
PASR_00004............................................................................................................................................. 145
PASR_00005............................................................................................................................................. 145
PASR_00006............................................................................................................................................. 146
PASR_00007............................................................................................................................................. 147
PASR_00008............................................................................................................................................. 148
PASR_00009............................................................................................................................................. 149
PASR_00010............................................................................................................................................. 149
PASR_00011............................................................................................................................................. 150
PASR_00012............................................................................................................................................. 150
PASR_00013............................................................................................................................................. 151
PASR_00014............................................................................................................................................. 151
PASR_00015............................................................................................................................................. 152
PASR_00016............................................................................................................................................. 153
PASR_00017............................................................................................................................................. 154
PASR_00018............................................................................................................................................. 154
PASR_00019............................................................................................................................................. 155
Chapter 8: PAVB events...................................................................................................... 157
PAVB_00001............................................................................................................................................. 157
PAVB_00002............................................................................................................................................. 158
PAVB_00003............................................................................................................................................. 158
PAVB_00004............................................................................................................................................. 159
PAVB_00005............................................................................................................................................. 160
PAVB_00006............................................................................................................................................. 160
PAVB_00101............................................................................................................................................. 161
PAVB_00102............................................................................................................................................. 162
PAVB_00103............................................................................................................................................. 162
PAVB_00104............................................................................................................................................. 163
PAVB_00106............................................................................................................................................. 163
PAVB_00107............................................................................................................................................. 164
PAVB_00109............................................................................................................................................. 165
PAVB_00110............................................................................................................................................. 165
PAVB_00111.............................................................................................................................................. 166
PAVB_00112............................................................................................................................................. 167
PAVB_00113............................................................................................................................................. 167
PAVB_00128............................................................................................................................................. 168
PAVB_00131............................................................................................................................................. 168
PAVB_00133............................................................................................................................................. 169
PAVB_00134............................................................................................................................................. 170
PAVB_00136............................................................................................................................................. 170
PAVB_00137............................................................................................................................................. 171
PAVB_00138............................................................................................................................................. 172
PAVB_00139............................................................................................................................................. 172
PAVB_00140............................................................................................................................................. 173
PAVB_00141............................................................................................................................................. 174
PAVB_00142............................................................................................................................................. 174
PAVB_00143............................................................................................................................................. 175
PAVB_00144............................................................................................................................................. 176
PAVB_00146............................................................................................................................................. 176
PAVB_00147............................................................................................................................................. 177
PAVB_00148............................................................................................................................................. 178
PAVB_00149............................................................................................................................................. 178
PAVB_00151............................................................................................................................................. 179
PAVB_00153............................................................................................................................................. 180
PAVB_00156............................................................................................................................................. 180
PAVB_00157............................................................................................................................................. 181
PAVB_00159............................................................................................................................................. 182
PAVB_00160............................................................................................................................................. 182
PAVB_00161............................................................................................................................................. 183
PAVB_00162............................................................................................................................................. 184
PAVB_00163............................................................................................................................................. 184
PAVB_00165............................................................................................................................................. 185
PAVB_00166............................................................................................................................................. 186
PAVB_00167............................................................................................................................................. 186
PAVB_00169............................................................................................................................................. 187
PAVB_00170............................................................................................................................................. 188
PAVB_00173............................................................................................................................................. 188
PAVB_00174............................................................................................................................................. 189
PAVB_00175............................................................................................................................................. 190
PAVB_00176............................................................................................................................................. 190
PAVB_00178............................................................................................................................................. 191
PAVB_00179............................................................................................................................................. 192
PAVB_00180............................................................................................................................................. 192
PAVB_00181............................................................................................................................................. 193
PAVB_00183............................................................................................................................................. 194
PAVB_00184............................................................................................................................................. 194
PAVB_00185............................................................................................................................................. 195
PAVB_00186............................................................................................................................................. 195
PAVB_00187............................................................................................................................................. 196
PAVB_00188............................................................................................................................................. 197
PAVB_00189............................................................................................................................................. 197
PAVB_00190............................................................................................................................................. 198
PAVB_00191............................................................................................................................................. 198
PAVB_00193............................................................................................................................................. 199
PAVB_00194............................................................................................................................................. 200
PAVB_00195............................................................................................................................................. 200
PAVB_00196............................................................................................................................................. 201
PAVB_00197............................................................................................................................................. 202
PAVB_00198............................................................................................................................................. 203
PAVB_00200............................................................................................................................................. 203
PAVB_00202............................................................................................................................................. 204
PAVB_00203............................................................................................................................................. 204
PAVB_00204............................................................................................................................................. 205
PAVB_00208............................................................................................................................................. 206
PAVB_00212............................................................................................................................................. 206
PAVB_00213............................................................................................................................................. 207
PAVB_00216............................................................................................................................................. 208
PAVB_00218............................................................................................................................................. 208
PAVB_00219............................................................................................................................................. 209
PAVB_00220............................................................................................................................................. 210
PAVB_00222............................................................................................................................................. 210
PAVB_00224............................................................................................................................................. 211
PAVB_00225............................................................................................................................................. 212
PAVB_00226............................................................................................................................................. 212
PAVB_00227............................................................................................................................................. 213
PAVB_00230............................................................................................................................................. 214
PAVB_00305............................................................................................................................................. 214
PAVB_01001............................................................................................................................................. 215
PAVB_01004............................................................................................................................................. 215
PAVB_01016............................................................................................................................................. 216
PAVB_01018............................................................................................................................................. 217
PAVB_01019............................................................................................................................................. 217
PAVB_01020............................................................................................................................................. 218
PAVB_01021............................................................................................................................................. 219
PAVB_01024............................................................................................................................................. 219
PAVB_01026............................................................................................................................................. 220
PAVB_01027............................................................................................................................................. 220
PAVB_01028............................................................................................................................................. 221
PAVB_01029............................................................................................................................................. 222
PAVB_01030............................................................................................................................................. 222
PAVB_01031............................................................................................................................................. 223
PAVB_01032............................................................................................................................................. 223
PAVB_01033............................................................................................................................................. 224
PAVB_01034............................................................................................................................................. 225
PAVB_01035............................................................................................................................................. 225
PAVB_01037............................................................................................................................................. 226
PAVB_01038............................................................................................................................................. 226
PAVB_01039............................................................................................................................................. 227
PAVB_01040............................................................................................................................................. 228
PAVB_01041............................................................................................................................................. 228
PAVB_01045............................................................................................................................................. 229
PAVB_01046............................................................................................................................................. 230
PAVB_01048............................................................................................................................................. 230
PAVB_01049............................................................................................................................................. 231
PAVB_01050............................................................................................................................................. 232
PAVB_01051............................................................................................................................................. 232
PAVB_01052............................................................................................................................................. 233
PAVB_01053............................................................................................................................................. 233
PAVB_01054............................................................................................................................................. 234
PAVB_01055............................................................................................................................................. 235
PAVB_01056............................................................................................................................................. 235
PAVB_01057............................................................................................................................................. 236
PAVB_01058............................................................................................................................................. 236
PAVB_01059............................................................................................................................................. 237
PAVB_01065............................................................................................................................................. 238
PAVB_01073............................................................................................................................................. 238
PAVB_01074............................................................................................................................................. 239
PAVB_01075............................................................................................................................................. 239
PAVB_01076............................................................................................................................................. 240
PAVB_01077............................................................................................................................................. 241
PAVB_01078............................................................................................................................................. 241
PAVB_01079............................................................................................................................................. 242
PAVB_01080............................................................................................................................................. 242
PAVB_01081............................................................................................................................................. 243
PAVB_01082............................................................................................................................................. 244
PAVB_01083............................................................................................................................................. 244
PAVB_01084............................................................................................................................................. 245
PAVB_02001............................................................................................................................................. 245
PAVB_02002............................................................................................................................................. 246
PAVB_02003............................................................................................................................................. 247
PAVB_03001............................................................................................................................................. 247
PAVB_03003............................................................................................................................................. 248
PAVB_03006............................................................................................................................................. 249
PAVB_03008............................................................................................................................................. 250
PAVB_03009............................................................................................................................................. 250
PAVB_03010............................................................................................................................................. 251
PAVB_03011............................................................................................................................................. 252
PAVB_03013............................................................................................................................................. 252
PAVB_03020............................................................................................................................................. 253
PAVB_03022............................................................................................................................................. 254
PAVB_03023............................................................................................................................................. 254
PAVB_03024............................................................................................................................................. 255
PAVB_03025............................................................................................................................................. 256
PAVB_03026............................................................................................................................................. 256
PAVB_03027............................................................................................................................................. 257
PAVB_03028............................................................................................................................................. 258
PAVB_03029............................................................................................................................................. 258
PAVB_03035............................................................................................................................................. 259
PAVB_03036............................................................................................................................................. 260
PAVB_03037............................................................................................................................................. 260
PAVB_03038............................................................................................................................................. 261
PAVB_03039............................................................................................................................................. 262
PAVB_03040............................................................................................................................................. 262
PAVB_03041............................................................................................................................................. 263
PAVB_03042............................................................................................................................................. 264
PAVB_03043............................................................................................................................................. 264
PAVB_03045............................................................................................................................................. 265
PAVB_03046............................................................................................................................................. 266
PAVB_03047............................................................................................................................................. 266
PAVB_03048............................................................................................................................................. 267
PAVB_03049............................................................................................................................................. 268
PAVB_03050............................................................................................................................................. 268
PAVB_03051............................................................................................................................................. 269
PAVB_03052............................................................................................................................................. 269
PAVB_03053............................................................................................................................................. 270
PAVB_03055............................................................................................................................................. 270
PAVB_03056............................................................................................................................................. 271
PAVB_03057............................................................................................................................................. 272
PAVB_03059............................................................................................................................................. 273
PAVB_03060............................................................................................................................................. 273
PAVB_03061............................................................................................................................................. 274
PAVB_03062............................................................................................................................................. 274
PAVB_03063............................................................................................................................................. 275
PAVB_03064............................................................................................................................................. 276
PAVB_03098............................................................................................................................................. 277
PAVB_03099............................................................................................................................................. 277
PAVB_03100............................................................................................................................................. 278
PAVB_03101............................................................................................................................................. 279
PAVB_03103............................................................................................................................................. 279
PAVB_03104............................................................................................................................................. 280
PAVB_03105............................................................................................................................................. 281
PAVB_03106............................................................................................................................................. 281
PAVB_03107............................................................................................................................................. 282
PAVB_03109............................................................................................................................................. 282
PAVB_03110............................................................................................................................................. 283
PAVB_03111.............................................................................................................................................. 284
PAVB_03112............................................................................................................................................. 285
PAVB_03151............................................................................................................................................. 285
PAVB_03152............................................................................................................................................. 286
PAVB_03154............................................................................................................................................. 286
PAVB_03155............................................................................................................................................. 287
PAVB_03156............................................................................................................................................. 288
PAVB_03158............................................................................................................................................. 288
PAVB_03160............................................................................................................................................. 289
PAVB_03162............................................................................................................................................. 290
PAVB_03163............................................................................................................................................. 290
PAVB_03164............................................................................................................................................. 291
PAVB_03165............................................................................................................................................. 291
PAVB_03169............................................................................................................................................. 292
PAVB_03170............................................................................................................................................. 293
PAVB_03172............................................................................................................................................. 293
PAVB_03173............................................................................................................................................. 294
PAVB_03174............................................................................................................................................. 295
PAVB_03175............................................................................................................................................. 295
PAVB_03176............................................................................................................................................. 296
PAVB_03177............................................................................................................................................. 297
PAVB_03178............................................................................................................................................. 297
PAVB_03179............................................................................................................................................. 298
PAVB_03180............................................................................................................................................. 298
PAVB_03181............................................................................................................................................. 299
PAVB_03182............................................................................................................................................. 300
PAVB_03184............................................................................................................................................. 300
PAVB_03185............................................................................................................................................. 301
PAVB_03186............................................................................................................................................. 302
PAVB_03188............................................................................................................................................. 302
PAVB_03189............................................................................................................................................. 303
PAVB_03190............................................................................................................................................. 304
PAVB_03199............................................................................................................................................. 304
PAVB_03200............................................................................................................................................. 305
PAVB_03201............................................................................................................................................. 305
PAVB_03306............................................................................................................................................. 306
PAVB_03307............................................................................................................................................. 307
PAVB_03308............................................................................................................................................. 308
PAVB_03309............................................................................................................................................. 308
PAVB_03310............................................................................................................................................. 309
PAVB_03313............................................................................................................................................. 310
PAVB_03314............................................................................................................................................. 310
PAVB_03315............................................................................................................................................. 311
PAVB_03316............................................................................................................................................. 311
PAVB_03317............................................................................................................................................. 312
PAVB_03318............................................................................................................................................. 313
PAVB_03319............................................................................................................................................. 313
PAVB_03320............................................................................................................................................. 314
PAVB_03321............................................................................................................................................. 315
PAVB_03323............................................................................................................................................. 315
PAVB_03324............................................................................................................................................. 316
PAVB_03325............................................................................................................................................. 316
PAVB_03326............................................................................................................................................. 317
PAVB_03328............................................................................................................................................. 318
PAVB_03329............................................................................................................................................. 319
PAVB_03331............................................................................................................................................. 319
PAVB_03332............................................................................................................................................. 320
PAVB_03333............................................................................................................................................. 321
PAVB_03334............................................................................................................................................. 321
PAVB_03335............................................................................................................................................. 322
PAVB_04001............................................................................................................................................. 323
PAVB_04002............................................................................................................................................. 323
PAVB_04005............................................................................................................................................. 324
PAVB_04006............................................................................................................................................. 324
PAVB_04007............................................................................................................................................. 325
PAVB_04008............................................................................................................................................. 326
PAVB_04009............................................................................................................................................. 326
PAVB_04010............................................................................................................................................. 327
PAVB_04011............................................................................................................................................. 328
PAVB_04012............................................................................................................................................. 328
PAVB_04013............................................................................................................................................. 329
PAVB_04015............................................................................................................................................. 329
PAVB_04016............................................................................................................................................. 330
PAVB_04018............................................................................................................................................. 331
PAVB_04041............................................................................................................................................. 331
PAVB_04045............................................................................................................................................. 332
PAVB_05003............................................................................................................................................. 332
PAVB_05005............................................................................................................................................. 333
PAVB_05026............................................................................................................................................. 334
PAVB_05027............................................................................................................................................. 334
PAVB_06003............................................................................................................................................. 335
PAVB_06004............................................................................................................................................. 336
PAVB_06005............................................................................................................................................. 336
PAVB_06006............................................................................................................................................. 337
PAVB_06007............................................................................................................................................. 338
PAVB_06009............................................................................................................................................. 338
PAVB_06011............................................................................................................................................. 339
PAVB_06013............................................................................................................................................. 339
PAVB_06015............................................................................................................................................. 340
PAVB_06017............................................................................................................................................. 341
PAVB_06018............................................................................................................................................. 341
PAVB_06019............................................................................................................................................. 342
PAVB_06020............................................................................................................................................. 343
PAVB_07001............................................................................................................................................. 343
PAVB_07002............................................................................................................................................. 344
PAVB_07004............................................................................................................................................. 345
PAVB_07005............................................................................................................................................. 345
PAVB_07008............................................................................................................................................. 346
PAVB_07009............................................................................................................................................. 346
PAVB_07010............................................................................................................................................. 347
PAVB_07013............................................................................................................................................. 348
PAVB_07016............................................................................................................................................. 348
PAVB_07017............................................................................................................................................. 349
PAVB_07021............................................................................................................................................. 350
PAVB_07024............................................................................................................................................. 350
PAVB_08002............................................................................................................................................. 351
PAVB_08003............................................................................................................................................. 352
PAVB_08004............................................................................................................................................. 352
PAVB_08005............................................................................................................................................. 353
PAVB_08006............................................................................................................................................. 353
PAVB_08007............................................................................................................................................. 354
PAVB_08008............................................................................................................................................. 355
PAVB_08009............................................................................................................................................. 355
PAVB_08010............................................................................................................................................. 356
PAVB_08011............................................................................................................................................. 357
PAVB_08012............................................................................................................................................. 357
PAVB_08013............................................................................................................................................. 358
Chapter 9: PBUD events..................................................................................................... 359
PBUD_00001............................................................................................................................................ 359
PBUD_00002............................................................................................................................................ 359
PBUD_00003............................................................................................................................................ 360
PBUD_00004............................................................................................................................................ 360
PBUD_00005............................................................................................................................................ 361
PBUD_00006............................................................................................................................................ 362
PBUD_00007............................................................................................................................................ 362
PBUD_00008............................................................................................................................................ 363
PBUD_00009............................................................................................................................................ 363
PBUD_00010............................................................................................................................................ 364
PBUD_00011............................................................................................................................................ 364
PBUD_00012............................................................................................................................................ 365
PBUD_00101............................................................................................................................................ 366
PBUD_00102............................................................................................................................................ 366
PBUD_00103............................................................................................................................................ 367
PBUD_00104............................................................................................................................................ 368
PBUD_00105............................................................................................................................................ 368
PBUD_00106............................................................................................................................................ 369
PBUD_00111............................................................................................................................................. 370
PBUD_00112............................................................................................................................................ 370
PBUD_00113............................................................................................................................................ 371
PBUD_00114............................................................................................................................................ 372
PBUD_00115............................................................................................................................................ 372
PBUD_00121............................................................................................................................................ 373
PBUD_00122............................................................................................................................................ 374
PBUD_00123............................................................................................................................................ 374
PBUD_00124............................................................................................................................................ 375
PBUD_00125............................................................................................................................................ 375
PBUD_00126............................................................................................................................................ 376
PBUD_00130............................................................................................................................................ 377
PBUD_00131............................................................................................................................................ 377
PBUD_00141............................................................................................................................................ 378
PBUD_00151............................................................................................................................................ 379
PBUD_00152............................................................................................................................................ 379
PBUD_00154............................................................................................................................................ 380
Chapter 10: PCDH events................................................................................................... 381
PCDH_00001............................................................................................................................................ 381
PCDH_00002............................................................................................................................................ 382
PCDH_00003............................................................................................................................................ 382
PCDH_00004............................................................................................................................................ 383
PCDH_00005............................................................................................................................................ 384
PCDH_00006............................................................................................................................................ 384
PCDH_00007............................................................................................................................................ 385
PCDH_00008............................................................................................................................................ 386
PCDH_00009............................................................................................................................................ 387
PCDH_00010............................................................................................................................................ 387
PCDH_00011............................................................................................................................................ 388
PCDH_00012............................................................................................................................................ 388
PCDH_00013............................................................................................................................................ 389
PCDH_00014............................................................................................................................................ 390
PCDH_00015............................................................................................................................................ 390
PCDH_00016............................................................................................................................................ 391
PCDH_00017............................................................................................................................................ 391
PCDH_00018............................................................................................................................................ 392
PCDH_00019............................................................................................................................................ 393
PCDH_00020............................................................................................................................................ 393
PCDH_00021............................................................................................................................................ 394
PCDH_00022............................................................................................................................................ 394
PCDH_00023............................................................................................................................................ 395
PCDH_00024............................................................................................................................................ 395
PCDH_00025............................................................................................................................................ 396
PCDH_00026............................................................................................................................................ 397
PCDH_00028............................................................................................................................................ 397
PCDH_00029............................................................................................................................................ 398
PCDH_00101............................................................................................................................................ 399
PCDH_00102............................................................................................................................................ 399
PCDH_00103............................................................................................................................................ 400
PCDH_00104............................................................................................................................................ 400
PCDH_00105............................................................................................................................................ 401
PCDH_00106............................................................................................................................................ 402
PCDH_00107............................................................................................................................................ 402
PCDH_00108............................................................................................................................................ 403
PCDH_00109............................................................................................................................................ 403
PCDH_00110............................................................................................................................................ 404
Chapter 11: PCXI events..................................................................................................... 405
PCXI_00001.............................................................................................................................................. 405
PCXI_00002.............................................................................................................................................. 406
PCXI_00003.............................................................................................................................................. 406
PCXI_00004.............................................................................................................................................. 407
PCXI_00005.............................................................................................................................................. 408
PCXI_00006.............................................................................................................................................. 409
PCXI_00007.............................................................................................................................................. 410
PCXI_00008.............................................................................................................................................. 411
PCXI_00009.............................................................................................................................................. 412
PCXI_00010.............................................................................................................................................. 412
PCXI_00011.............................................................................................................................................. 413
PCXI_00012.............................................................................................................................................. 414
PCXI_00013.............................................................................................................................................. 415
PCXI_00014.............................................................................................................................................. 416
PCXI_00015.............................................................................................................................................. 416
PCXI_00016.............................................................................................................................................. 417
PCXI_00017.............................................................................................................................................. 418
PCXI_00018.............................................................................................................................................. 418
PCXI_00019.............................................................................................................................................. 419
PCXI_00020.............................................................................................................................................. 420
PCXI_00021.............................................................................................................................................. 420
PCXI_00022.............................................................................................................................................. 421
Chapter 12: PEVTM events................................................................................................. 423
PEVTM00001............................................................................................................................................ 423
PEVTM00002............................................................................................................................................ 423
PEVTM00003............................................................................................................................................ 424
PEVTM00004............................................................................................................................................ 424
PEVTM00005............................................................................................................................................ 425
PEVTM00006............................................................................................................................................ 426
PEVTM00007............................................................................................................................................ 426
PEVTM00008............................................................................................................................................ 427
PEVTM00009............................................................................................................................................ 428
PEVTM00010............................................................................................................................................ 428
PEVTM00011............................................................................................................................................ 429
PEVTM00012............................................................................................................................................ 430
PEVTM00013............................................................................................................................................ 431
PEVTM00014............................................................................................................................................ 431
PEVTM00015............................................................................................................................................ 432
PEVTM00016............................................................................................................................................ 432
Chapter 13: PLICE events.................................................................................................. 435
PLICE00001.............................................................................................................................................. 435
PLICE00002.............................................................................................................................................. 436
PLICE00003.............................................................................................................................................. 437
PLICE00004.............................................................................................................................................. 438
PLICE00005.............................................................................................................................................. 438
PLICE00006.............................................................................................................................................. 439
PLICE00007.............................................................................................................................................. 440
PLICE00008.............................................................................................................................................. 440
PLICE00009.............................................................................................................................................. 441
PLICE00010.............................................................................................................................................. 441
PLICE00011.............................................................................................................................................. 442
PLICE00012.............................................................................................................................................. 443
PLICE00013.............................................................................................................................................. 443
PLICE00014.............................................................................................................................................. 444
PLICE00015.............................................................................................................................................. 444
PLICE00016.............................................................................................................................................. 445
PLICE00017.............................................................................................................................................. 446
PLICE00018.............................................................................................................................................. 446
PLICE00019.............................................................................................................................................. 447
PLICE00020.............................................................................................................................................. 448
PLICE00021.............................................................................................................................................. 448
PLICE00024.............................................................................................................................................. 449
PLICE00025.............................................................................................................................................. 450
Chapter 14: PLOG events................................................................................................... 453
PLOG_00001............................................................................................................................................ 453
PLOG_00002............................................................................................................................................ 454
PLOG_00003............................................................................................................................................ 455
PLOG_00004............................................................................................................................................ 456
PLOG_00005............................................................................................................................................ 457
PLOG_00006............................................................................................................................................ 457
PLOG_00007............................................................................................................................................ 458
Chapter 15: PLOGR events................................................................................................ 459
PLOGR00001............................................................................................................................................ 459
PLOGR00002............................................................................................................................................ 460
PLOGR00003............................................................................................................................................ 460
PLOGR00004............................................................................................................................................ 461
PLOGR10001............................................................................................................................................ 462
PLOGR10002............................................................................................................................................ 463
Chapter 16: PLSTNR events............................................................................................... 465
PLSTNR0001............................................................................................................................................ 465
PLSTNR0002............................................................................................................................................ 465
PLSTNR0003............................................................................................................................................ 466
PLSTNR0004............................................................................................................................................ 467
PLSTNR0005............................................................................................................................................ 467
PLSTNR0006............................................................................................................................................ 468
PLSTNR0007............................................................................................................................................ 468
PLSTNR0008............................................................................................................................................ 469
PLSTNR0009............................................................................................................................................ 470
PLSTNR0010............................................................................................................................................ 470
PLSTNR0011............................................................................................................................................ 471
PLSTNR0012............................................................................................................................................ 471
PLSTNR0013............................................................................................................................................ 472
PLSTNR0014............................................................................................................................................ 473
PLSTNR0015............................................................................................................................................ 473
PLSTNR0016............................................................................................................................................ 474
PLSTNR0017............................................................................................................................................ 475
PLSTNR0018............................................................................................................................................ 475
PLSTNR0019............................................................................................................................................ 476
PLSTNR0020............................................................................................................................................ 476
PLSTNR0021............................................................................................................................................ 477
PLSTNR0022............................................................................................................................................ 478
PLSTNR0023............................................................................................................................................ 478
PLSTNR0024............................................................................................................................................ 479
Chapter 17: PMMGR events............................................................................................... 481
PMMGR00006.......................................................................................................................................... 481
Chapter 18: PMMS events.................................................................................................. 483
PMMS_00001........................................................................................................................................... 483
PMMS_00002........................................................................................................................................... 484
PMMS_00003........................................................................................................................................... 484
PMMS_00004........................................................................................................................................... 485
Chapter 19: PMRCP events................................................................................................ 487
PMRCP00001........................................................................................................................................... 487
PMRCP00002........................................................................................................................................... 488
PMRCP00003........................................................................................................................................... 488
PMRCP00004........................................................................................................................................... 489
PMRCP00005........................................................................................................................................... 490
PMRCP00006........................................................................................................................................... 491
PMRCP00007........................................................................................................................................... 492
PMRCP00008........................................................................................................................................... 493
PMRCP00009........................................................................................................................................... 494
PMRCP00010........................................................................................................................................... 494
Chapter 20: PMUG events.................................................................................................. 497
PMUG_00001........................................................................................................................................... 497
PMUG_00002........................................................................................................................................... 497
PMUG_00003........................................................................................................................................... 498
PMUG_00004........................................................................................................................................... 499
PMUG_00005........................................................................................................................................... 500
PMUG_00006........................................................................................................................................... 500
PMUG_00007........................................................................................................................................... 501
PMUG_00008........................................................................................................................................... 502
PMUG_00009........................................................................................................................................... 502
PMUG_00010........................................................................................................................................... 503
Chapter 21: POMS events.................................................................................................. 505
POMS_00001............................................................................................................................................ 505
POMS_00002............................................................................................................................................ 505
POMS_00003............................................................................................................................................ 506
POMS_00004............................................................................................................................................ 506
POMS_00005............................................................................................................................................ 507
POMS_00006............................................................................................................................................ 508
POMS_00007............................................................................................................................................ 508
POMS_00008............................................................................................................................................ 509
POMS_00009............................................................................................................................................ 509
POMS_00010............................................................................................................................................ 510
POMS_00011............................................................................................................................................ 510
POMS_00012............................................................................................................................................ 511
POMS_00013............................................................................................................................................ 512
POMS_00014............................................................................................................................................ 512
POMS_00015............................................................................................................................................ 513
POMS_00016............................................................................................................................................ 514
POMS_00017............................................................................................................................................ 514
POMS_00018............................................................................................................................................ 515
POMS_00019............................................................................................................................................ 516
POMS_00020............................................................................................................................................ 516
POMS_00021............................................................................................................................................ 517
POMS_00022............................................................................................................................................ 517
POMS_00023............................................................................................................................................ 518
POMS_00024............................................................................................................................................ 519
POMS_00025............................................................................................................................................ 519
POMS_00026............................................................................................................................................ 520
POMS_00027............................................................................................................................................ 521
POMS_00028............................................................................................................................................ 521
POMS_00029............................................................................................................................................ 521
POMS_00030............................................................................................................................................ 522
POMS_00031............................................................................................................................................ 522
POMS_00032............................................................................................................................................ 523
POMS_00033............................................................................................................................................ 523
POMS_00034............................................................................................................................................ 524
POMS_00035............................................................................................................................................ 525
POMS_00036............................................................................................................................................ 525
POMS_00037............................................................................................................................................ 526
POMS_00038............................................................................................................................................ 527
POMS_00039............................................................................................................................................ 528
POMS_00040............................................................................................................................................ 529
POMS_00041............................................................................................................................................ 530
POMS_00042............................................................................................................................................ 531
POMS_00043............................................................................................................................................ 532
POMS_00044............................................................................................................................................ 532
POMS_00045............................................................................................................................................ 533
POMS_00046............................................................................................................................................ 534
POMS_00047............................................................................................................................................ 535
POMS_00048............................................................................................................................................ 536
POMS_00049............................................................................................................................................ 536
POMS_00050............................................................................................................................................ 537
POMS_00051............................................................................................................................................ 538
POMS_00052............................................................................................................................................ 539
POMS_00053............................................................................................................................................ 540
POMS_00054............................................................................................................................................ 541
POMS_00055............................................................................................................................................ 542
POMS_00056............................................................................................................................................ 542
POMS_00057............................................................................................................................................ 543
POMS_00058............................................................................................................................................ 544
POMS_00059............................................................................................................................................ 545
POMS_00060............................................................................................................................................ 546
POMS_00061............................................................................................................................................ 547
POMS_00062............................................................................................................................................ 548
POMS_00063............................................................................................................................................ 549
POMS_00064............................................................................................................................................ 549
POMS_00065............................................................................................................................................ 550
POMS_00066............................................................................................................................................ 551
POMS_00067............................................................................................................................................ 552
POMS_00068............................................................................................................................................ 553
POMS_00069............................................................................................................................................ 554
POMS_00070............................................................................................................................................ 554
POMS_00071............................................................................................................................................ 555
POMS_00072............................................................................................................................................ 556
POMS_00073............................................................................................................................................ 556
POMS_00074............................................................................................................................................ 557
POMS_00075............................................................................................................................................ 557
POMS_00076............................................................................................................................................ 558
POMS_00077............................................................................................................................................ 558
POMS_00078............................................................................................................................................ 559
POMS_00079............................................................................................................................................ 560
POMS_00080............................................................................................................................................ 561
POMS_00081............................................................................................................................................ 562
POMS_00082............................................................................................................................................ 563
POMS_00083............................................................................................................................................ 564
POMS_00084............................................................................................................................................ 565
POMS_00085............................................................................................................................................ 566
POMS_00086............................................................................................................................................ 566
POMS_00087............................................................................................................................................ 567
POMS_00088............................................................................................................................................ 568
POMS_00089............................................................................................................................................ 569
POMS_00090............................................................................................................................................ 569
POMS_00091............................................................................................................................................ 570
POMS_00092............................................................................................................................................ 571
POMS_00093............................................................................................................................................ 571
POMS_00094............................................................................................................................................ 572
POMS_00095............................................................................................................................................ 572
POMS_00096............................................................................................................................................ 573
POMS_00097............................................................................................................................................ 574
POMS_00098............................................................................................................................................ 575
POMS_00099............................................................................................................................................ 576
POMS_00100............................................................................................................................................ 577
POMS_00101............................................................................................................................................ 578
POMS_00102............................................................................................................................................ 579
POMS_00103............................................................................................................................................ 579
POMS_00104............................................................................................................................................ 580
POMS_00105............................................................................................................................................ 581
POMS_00106............................................................................................................................................ 581
POMS_00107............................................................................................................................................ 582
POMS_00108............................................................................................................................................ 583
POMS_00109............................................................................................................................................ 583
POMS_00110............................................................................................................................................ 584
POMS_00111............................................................................................................................................ 584
POMS_00112............................................................................................................................................ 585
POMS_00113............................................................................................................................................ 586
POMS_00114............................................................................................................................................ 586
POMS_00115............................................................................................................................................ 587
POMS_00116............................................................................................................................................ 588
POMS_00117............................................................................................................................................ 588
POMS_00118............................................................................................................................................ 589
POMS_00119............................................................................................................................................ 590
POMS_00120............................................................................................................................................ 591
POMS_00121............................................................................................................................................ 591
POMS_00122............................................................................................................................................ 592
POMS_00123............................................................................................................................................ 593
POMS_00124............................................................................................................................................ 594
POMS_00125............................................................................................................................................ 595
POMS_00126............................................................................................................................................ 596
POMS_00127............................................................................................................................................ 597
POMS_00128............................................................................................................................................ 597
POMS_00129............................................................................................................................................ 598
POMS_00130............................................................................................................................................ 599
POMS_00131............................................................................................................................................ 600
POMS_00132............................................................................................................................................ 601
POMS_00133............................................................................................................................................ 602
POMS_00134............................................................................................................................................ 602
POMS_00135............................................................................................................................................ 603
POMS_00136............................................................................................................................................ 603
POMS_00137............................................................................................................................................ 604
POMS_00138............................................................................................................................................ 605
POMS_00139............................................................................................................................................ 605
POMS_00140............................................................................................................................................ 606
POMS_00141............................................................................................................................................ 607
POMS_00142............................................................................................................................................ 608
POMS_00143............................................................................................................................................ 608
POMS_00144............................................................................................................................................ 609
POMS_00145............................................................................................................................................ 609
POMS_00146............................................................................................................................................ 610
POMS_00147............................................................................................................................................ 611
POMS_00148............................................................................................................................................ 611
POMS_00149............................................................................................................................................ 612
POMS_00150............................................................................................................................................ 612
POMS_00151............................................................................................................................................ 613
POMS_00152............................................................................................................................................ 613
POMS_00153............................................................................................................................................ 614
POMS_00154............................................................................................................................................ 615
POMS_00155............................................................................................................................................ 615
POMS_00156............................................................................................................................................ 616
POMS_00157............................................................................................................................................ 616
POMS_00158............................................................................................................................................ 617
POMS_00159............................................................................................................................................ 617
POMS_00160............................................................................................................................................ 618
POMS_00161............................................................................................................................................ 619
POMS_00162............................................................................................................................................ 619
POMS_00163............................................................................................................................................ 620
POMS_00164............................................................................................................................................ 621
POMS_00165............................................................................................................................................ 621
POMS_00166............................................................................................................................................ 622
POMS_00167............................................................................................................................................ 622
POMS_00168............................................................................................................................................ 623
POMS_00169............................................................................................................................................ 623
POMS_00170............................................................................................................................................ 624
POMS_00171............................................................................................................................................ 625
POMS_00172............................................................................................................................................ 625
POMS_00173............................................................................................................................................ 626
POMS_00174............................................................................................................................................ 626
POMS_00175............................................................................................................................................ 627
POMS_00176............................................................................................................................................ 628
POMS_00177............................................................................................................................................ 628
POMS_00178............................................................................................................................................ 629
POMS_00179............................................................................................................................................ 629
POMS_00180............................................................................................................................................ 630
POMS_00181............................................................................................................................................ 630
POMS_00182............................................................................................................................................ 631
POMS_00183............................................................................................................................................ 631
POMS_00184............................................................................................................................................ 632
POMS_00185............................................................................................................................................ 632
POMS_00186............................................................................................................................................ 633
POMS_00187............................................................................................................................................ 633
POMS_00188............................................................................................................................................ 634
POMS_00189............................................................................................................................................ 635
POMS_00190............................................................................................................................................ 635
POMS_00191............................................................................................................................................ 636
POMS_00192............................................................................................................................................ 636
POMS_00193............................................................................................................................................ 637
POMS_00194............................................................................................................................................ 638
POMS_00195............................................................................................................................................ 638
POMS_00196............................................................................................................................................ 639
POMS_00197............................................................................................................................................ 639
POMS_00198............................................................................................................................................ 640
POMS_00199............................................................................................................................................ 640
POMS_00200............................................................................................................................................ 641
POMS_00201............................................................................................................................................ 642
POMS_00202............................................................................................................................................ 642
POMS_00203............................................................................................................................................ 643
POMS_00204............................................................................................................................................ 643
POMS_00205............................................................................................................................................ 644
POMS_00206............................................................................................................................................ 645
POMS_00207............................................................................................................................................ 645
POMS_00208............................................................................................................................................ 646
POMS_00209............................................................................................................................................ 646
POMS_00210............................................................................................................................................ 647
POMS_00211............................................................................................................................................ 647
POMS_00212............................................................................................................................................ 648
POMS_00213............................................................................................................................................ 648
POMS_00214............................................................................................................................................ 649
POMS_00215............................................................................................................................................ 650
POMS_00216............................................................................................................................................ 650
POMS_00217............................................................................................................................................ 651
POMS_00218............................................................................................................................................ 652
POMS_00219............................................................................................................................................ 652
POMS_00220............................................................................................................................................ 653
POMS_00221............................................................................................................................................ 654
POMS_00222............................................................................................................................................ 654
POMS_00223............................................................................................................................................ 655
POMS_00224............................................................................................................................................ 656
POMS_00225............................................................................................................................................ 656
POMS_00226............................................................................................................................................ 657
POMS_00227............................................................................................................................................ 657
POMS_00228............................................................................................................................................ 658
POMS_00229............................................................................................................................................ 659
POMS_00230............................................................................................................................................ 659
POMS_00231............................................................................................................................................ 660
POMS_00232............................................................................................................................................ 660
POMS_00233............................................................................................................................................ 661
POMS_00234............................................................................................................................................ 662
POMS_00235............................................................................................................................................ 662
POMS_00236............................................................................................................................................ 663
POMS_00237............................................................................................................................................ 663
POMS_00238............................................................................................................................................ 664
POMS_00239............................................................................................................................................ 664
POMS_00240............................................................................................................................................ 665
POMS_00241............................................................................................................................................ 666
POMS_00242............................................................................................................................................ 666
POMS_00243............................................................................................................................................ 667
POMS_00244............................................................................................................................................ 667
POMS_00245............................................................................................................................................ 668
POMS_00246............................................................................................................................................ 668
POMS_00247............................................................................................................................................ 669
POMS_00248............................................................................................................................................ 670
POMS_00249............................................................................................................................................ 670
POMS_00250............................................................................................................................................ 671
POMS_00251............................................................................................................................................ 672
POMS_00252............................................................................................................................................ 672
POMS_00253............................................................................................................................................ 673
POMS_00254............................................................................................................................................ 673
POMS_00255............................................................................................................................................ 674
POMS_00256............................................................................................................................................ 675
POMS_00257............................................................................................................................................ 676
POMS_00258............................................................................................................................................ 676
POMS_00259............................................................................................................................................ 677
POMS_00260............................................................................................................................................ 678
POMS_00261............................................................................................................................................ 678
POMS_00262............................................................................................................................................ 679
POMS_00263............................................................................................................................................ 680
POMS_00264............................................................................................................................................ 680
POMS_00265............................................................................................................................................ 681
POMS_00266............................................................................................................................................ 682
POMS_00267............................................................................................................................................ 683
POMS_00268............................................................................................................................................ 683
POMS_00269............................................................................................................................................ 684
POMS_00270............................................................................................................................................ 685
POMS_00271............................................................................................................................................ 685
POMS_00272............................................................................................................................................ 686
POMS_00273............................................................................................................................................ 686
POMS_00274............................................................................................................................................ 687
POMS_00275............................................................................................................................................ 688
POMS_00276............................................................................................................................................ 689
POMS_00277............................................................................................................................................ 689
POMS_00278............................................................................................................................................ 690
POMS_00279............................................................................................................................................ 691
POMS_00280............................................................................................................................................ 692
POMS_00281............................................................................................................................................ 692
POMS_00282............................................................................................................................................ 693
POMS_00283............................................................................................................................................ 694
POMS_00284............................................................................................................................................ 695
POMS_00285............................................................................................................................................ 695
POMS_00286............................................................................................................................................ 696
POMS_00287............................................................................................................................................ 697
POMS_00288............................................................................................................................................ 697
POMS_00289............................................................................................................................................ 698
POMS_00290............................................................................................................................................ 699
POMS_00291............................................................................................................................................ 699
POMS_00292............................................................................................................................................ 700
POMS_00293............................................................................................................................................ 700
POMS_00294............................................................................................................................................ 701
POMS_00295............................................................................................................................................ 702
POMS_00296............................................................................................................................................ 703
POMS_00297............................................................................................................................................ 703
POMS_00298............................................................................................................................................ 704
POMS_00299............................................................................................................................................ 704
POMS_00300............................................................................................................................................ 705
POMS_00301............................................................................................................................................ 706
POMS_00302............................................................................................................................................ 706
POMS_00303............................................................................................................................................ 707
POMS_00304............................................................................................................................................ 708
POMS_00305............................................................................................................................................ 708
POMS_00306............................................................................................................................................ 709
POMS_00307............................................................................................................................................ 709
POMS_00308............................................................................................................................................ 710
POMS_00309............................................................................................................................................ 711
POMS_00310............................................................................................................................................ 711
POMS_00311............................................................................................................................................ 712
POMS_00312............................................................................................................................................ 713
POMS_00313............................................................................................................................................ 714
POMS_00314............................................................................................................................................ 714
POMS_00315............................................................................................................................................ 715
POMS_00316............................................................................................................................................ 716
POMS_00317............................................................................................................................................ 717
POMS_00318............................................................................................................................................ 717
POMS_00319............................................................................................................................................ 718
POMS_00320............................................................................................................................................ 719
POMS_00321............................................................................................................................................ 719
POMS_00322............................................................................................................................................ 720
POMS_00323............................................................................................................................................ 721
POMS_00324............................................................................................................................................ 722
POMS_00325............................................................................................................................................ 722
POMS_00326............................................................................................................................................ 723
POMS_00327............................................................................................................................................ 724
POMS_00328............................................................................................................................................ 724
POMS_00329............................................................................................................................................ 725
POMS_00330............................................................................................................................................ 726
POMS_00332............................................................................................................................................ 726
POMS_00335............................................................................................................................................ 727
POMS_00338............................................................................................................................................ 728
POMS_00340............................................................................................................................................ 729
POMS_00342............................................................................................................................................ 730
POMS_00344............................................................................................................................................ 730
POMS_00345............................................................................................................................................ 731
POMS_00347............................................................................................................................................ 732
POMS_00348............................................................................................................................................ 732
POMS_00350............................................................................................................................................ 733
POMS_00355............................................................................................................................................ 733
POMS_00356............................................................................................................................................ 734
POMS_00357............................................................................................................................................ 735
POMS_00358............................................................................................................................................ 736
Chapter 22: PSESM events................................................................................................ 737
PSESM00001............................................................................................................................................ 737
PSESM00002............................................................................................................................................ 738
PSESM00003............................................................................................................................................ 738
PSESM00004............................................................................................................................................ 739
PSESM00005............................................................................................................................................ 740
PSESM00006............................................................................................................................................ 741
PSESM00007............................................................................................................................................ 742
PSESM00008............................................................................................................................................ 742
PSESM00009............................................................................................................................................ 743
PSESM00010............................................................................................................................................ 744
PSESM00011............................................................................................................................................ 745
PSESM00012............................................................................................................................................ 746
PSESM00013............................................................................................................................................ 746
PSESM00014............................................................................................................................................ 747
PSESM00015............................................................................................................................................ 748
PSESM00016............................................................................................................................................ 749
PSESM00017............................................................................................................................................ 749
PSESM00018............................................................................................................................................ 750
PSESM00019............................................................................................................................................ 751
PSESM00020............................................................................................................................................ 752
PSESM00021............................................................................................................................................ 752
PSESM00022............................................................................................................................................ 753
PSESM00023............................................................................................................................................ 754
PSESM00024............................................................................................................................................ 755
PSESM00025............................................................................................................................................ 756
PSESM00026............................................................................................................................................ 756
PSESM00027............................................................................................................................................ 757
PSESM00028............................................................................................................................................ 758
PSESM00029............................................................................................................................................ 759
PSESM00030............................................................................................................................................ 759
PSESM00031............................................................................................................................................ 760
PSESM00032............................................................................................................................................ 761
PSESM00033............................................................................................................................................ 762
PSESM00034............................................................................................................................................ 762
PSESM00035............................................................................................................................................ 763
PSESM00036............................................................................................................................................ 764
PSESM00037............................................................................................................................................ 765
PSESM00038............................................................................................................................................ 766
PSESM00039............................................................................................................................................ 766
PSESM00040............................................................................................................................................ 767
PSESM00041............................................................................................................................................ 768
PSESM00042............................................................................................................................................ 769
PSESM00043............................................................................................................................................ 770
PSESM00044............................................................................................................................................ 770
PSESM00045............................................................................................................................................ 771
PSESM00046............................................................................................................................................ 772
PSESM00047............................................................................................................................................ 773
PSESM00048............................................................................................................................................ 774
PSESM00049............................................................................................................................................ 774
PSESM00050............................................................................................................................................ 775
PSESM00051............................................................................................................................................ 776
PSESM00052............................................................................................................................................ 777
PSESM00053............................................................................................................................................ 778
PSESM00054............................................................................................................................................ 779
PSESM00055............................................................................................................................................ 779
PSESM00056............................................................................................................................................ 780
PSESM00057............................................................................................................................................ 781
PSESM00058............................................................................................................................................ 781
PSESM00059............................................................................................................................................ 782
PSESM00060............................................................................................................................................ 782
PSESM00061............................................................................................................................................ 783
PSESM00062............................................................................................................................................ 783
PSESM00063............................................................................................................................................ 784
PSESM00064............................................................................................................................................ 785
PSESM00065............................................................................................................................................ 785
PSESM00066............................................................................................................................................ 786
PSESM00067............................................................................................................................................ 787
PSESM00068............................................................................................................................................ 788
PSESM00070............................................................................................................................................ 789
PSESM00071............................................................................................................................................ 790
PSESM00072............................................................................................................................................ 791
PSESM00073............................................................................................................................................ 793
PSESM00074............................................................................................................................................ 794
PSESM00075............................................................................................................................................ 794
PSESM00076............................................................................................................................................ 795
PSESM00077............................................................................................................................................ 796
PSESM00078............................................................................................................................................ 797
PSESM00089............................................................................................................................................ 798
PSESM00090............................................................................................................................................ 799
PSESM00091............................................................................................................................................ 799
Chapter 23: PSNMP events................................................................................................ 801
PSNMP_I001............................................................................................................................................ 801
PSNMP_I002............................................................................................................................................ 801
PSNMP_I003............................................................................................................................................ 802
PSNMP_I004............................................................................................................................................ 802
PSNMP_I005............................................................................................................................................ 803
PSNMP_E001........................................................................................................................................... 804
PSNMP_E002........................................................................................................................................... 804
PSNMP_E003........................................................................................................................................... 805
PSNMP_E004........................................................................................................................................... 805
PSNMP_E005........................................................................................................................................... 806
PSNMP_E006........................................................................................................................................... 807
PSNMP_E007........................................................................................................................................... 807
PSNMP_E008........................................................................................................................................... 808
PSNMP_E009........................................................................................................................................... 808
PSNMP_E011........................................................................................................................................... 809
PSNMP_E012........................................................................................................................................... 810
PSNMP_W001.......................................................................................................................................... 811
PSNMP_W002.......................................................................................................................................... 811
PSNMP_W003.......................................................................................................................................... 812
PSNMP_W004.......................................................................................................................................... 812
PSNMP_W005.......................................................................................................................................... 813
PSNMP_W006.......................................................................................................................................... 814
PSNMP_W007.......................................................................................................................................... 814
PSNMP_W008.......................................................................................................................................... 815
PSNMP_W009.......................................................................................................................................... 815
PSNMP02601........................................................................................................................................... 816
PSNMP02602........................................................................................................................................... 817
PSNMP02603........................................................................................................................................... 817
PSNMP02604........................................................................................................................................... 818
PSNMP02605........................................................................................................................................... 819
PSNMP02606........................................................................................................................................... 820
P_AMS_0300............................................................................................................................................ 821
LSNMP01003............................................................................................................................................ 821
LSNMP01006............................................................................................................................................ 822
Chapter 24: PSYSM events................................................................................................ 823
PSYSM00001............................................................................................................................................ 823
PSYSM00002............................................................................................................................................ 824
PSYSM00003............................................................................................................................................ 825
PSYSM00004............................................................................................................................................ 826
PSYSM00005............................................................................................................................................ 827
PSYSM00006............................................................................................................................................ 827
PSYSM00007............................................................................................................................................ 828
PSYSM00008............................................................................................................................................ 829
PSYSM00009............................................................................................................................................ 830
PSYSM00010............................................................................................................................................ 831
PSYSM00011............................................................................................................................................ 831
PSYSM00012............................................................................................................................................ 832
PSYSM00013............................................................................................................................................ 833
PSYSM00014............................................................................................................................................ 833
PSYSM00015............................................................................................................................................ 834
PSYSM00016............................................................................................................................................ 835
PSYSM00017............................................................................................................................................ 836
PSYSM00018............................................................................................................................................ 837
PSYSM00019............................................................................................................................................ 838
PSYSM00020............................................................................................................................................ 838
PSYSM00021............................................................................................................................................ 839
PSYSM00022............................................................................................................................................ 840
PSYSM00023............................................................................................................................................ 841
PSYSM00024............................................................................................................................................ 842
PSYSM00025............................................................................................................................................ 843
PSYSM00026............................................................................................................................................ 843
PSYSM00027............................................................................................................................................ 844
PSYSM00028............................................................................................................................................ 845
PSYSM00029............................................................................................................................................ 846
PSYSM00030............................................................................................................................................ 846
PSYSM00031............................................................................................................................................ 847
PSYSM00032............................................................................................................................................ 848
PSYSM00033............................................................................................................................................ 849
PSYSM00034............................................................................................................................................ 850
PSYSM00035............................................................................................................................................ 850
PSYSM00036............................................................................................................................................ 851
PSYSM00037............................................................................................................................................ 852
PSYSM00038............................................................................................................................................ 852
PSYSM00039............................................................................................................................................ 853
PSYSM00040............................................................................................................................................ 854
PSYSM00041............................................................................................................................................ 855
PSYSM00042............................................................................................................................................ 856
PSYSM00043............................................................................................................................................ 857
PSYSM00044............................................................................................................................................ 858
PSYSM00045............................................................................................................................................ 858
PSYSM00046............................................................................................................................................ 859
PSYSM00047............................................................................................................................................ 860
PSYSM00048............................................................................................................................................ 861
PSYSM00049............................................................................................................................................ 862
PSYSM00050............................................................................................................................................ 862
PSYSM00051............................................................................................................................................ 863
PSYSM00056............................................................................................................................................ 864
PSYSM00057............................................................................................................................................ 865
PSYSM00058............................................................................................................................................ 866
Chapter 25: PTELE events................................................................................................. 869
PTELE00001............................................................................................................................................. 869
PTELE00002............................................................................................................................................. 869
PTELE00004............................................................................................................................................. 870
PTELE00005............................................................................................................................................. 871
PTELE00006............................................................................................................................................. 871
PTELE00007............................................................................................................................................. 872
PTELE00008............................................................................................................................................. 872
PTELE00009............................................................................................................................................. 873
PTELE00010............................................................................................................................................. 874
PTELE00011............................................................................................................................................. 874
PTELE00012............................................................................................................................................. 875
PTELE00013............................................................................................................................................. 876
PTELE00014............................................................................................................................................. 876
PTELE00015............................................................................................................................................. 877
PTELE00016............................................................................................................................................. 878
PTELE00017............................................................................................................................................. 879
PTELE00018............................................................................................................................................. 879
PTELE00019............................................................................................................................................. 880
PTELE00020............................................................................................................................................. 881
PTELE00021............................................................................................................................................. 881
PTELE00022............................................................................................................................................. 882
PTELE00023............................................................................................................................................. 883
PTELE00024............................................................................................................................................. 883
PTELE00025............................................................................................................................................. 884
PTELE00026............................................................................................................................................. 885
PTELE00027............................................................................................................................................. 885
PTELE00028............................................................................................................................................. 886
PTELE00029............................................................................................................................................. 887
PTELE00030............................................................................................................................................. 888
PTELE00031............................................................................................................................................. 888
PTELE00032............................................................................................................................................. 889
PTELE00033............................................................................................................................................. 889
PTELE00034............................................................................................................................................. 890
PTELE00035............................................................................................................................................. 891
PTELE00036............................................................................................................................................. 892
PTELE00037............................................................................................................................................. 893
PTELE00038............................................................................................................................................. 895
PTELE00039............................................................................................................................................. 896
PTELE00040............................................................................................................................................. 897
PTELE00041............................................................................................................................................. 898
PTELE00042............................................................................................................................................. 899
Chapter 26: PTRC events................................................................................................... 901
PTRC_00001............................................................................................................................................ 901
PTRC_00002............................................................................................................................................ 901
PTRC_00003............................................................................................................................................ 902
PTRC_00004............................................................................................................................................ 902
PTRC_00005............................................................................................................................................ 903
PTRC_00011............................................................................................................................................. 904
PTRC_00012............................................................................................................................................ 905
PTRC_00013............................................................................................................................................ 905
PTRC_00014............................................................................................................................................ 906
PTRC_00016............................................................................................................................................ 907
PTRC_00019............................................................................................................................................ 907
PTRC_00020............................................................................................................................................ 908
PTRC_00021............................................................................................................................................ 909
PTRC_00022............................................................................................................................................ 909
PTRC_00023............................................................................................................................................ 910
PTRC_00024............................................................................................................................................ 911
PTRC_00025............................................................................................................................................ 912
PTRC_00031............................................................................................................................................ 912
PTRC_00032............................................................................................................................................ 913
PTRC_00033............................................................................................................................................ 914
PTRC_00035............................................................................................................................................ 914
Chapter 27: PTTS events.................................................................................................... 917
PTTS_00001............................................................................................................................................. 917
PTTS_00002............................................................................................................................................. 918
PTTS_00003............................................................................................................................................. 918
PTTS_00004............................................................................................................................................. 919
PTTS_00005............................................................................................................................................. 919
PTTS_00006............................................................................................................................................. 920
PTTS_00007............................................................................................................................................. 921
PTTS_00008............................................................................................................................................. 922
PTTS_00009............................................................................................................................................. 922
PTTS_00010............................................................................................................................................. 923
PTTS_00011............................................................................................................................................. 924
PTTS_00012............................................................................................................................................. 924
PTTS_00013............................................................................................................................................. 925
PTTS_00014............................................................................................................................................. 925
PTTS_00015............................................................................................................................................. 926
PTTS_00016............................................................................................................................................. 927
PTTS_00017............................................................................................................................................. 928
PTTS_00018............................................................................................................................................. 928
PTTS_00019............................................................................................................................................. 929
Chapter 28: P_AMS events................................................................................................. 931
P_AMS05001............................................................................................................................................ 931
P_AMS05004............................................................................................................................................ 931
P_AMS05007............................................................................................................................................ 932
P_AMS05008............................................................................................................................................ 932
P_AMS05009............................................................................................................................................ 933
P_AMS05010............................................................................................................................................ 933
P_AMS05011............................................................................................................................................ 934
P_AMS05012............................................................................................................................................ 934
P_AMS05025............................................................................................................................................ 935
P_AMS05026............................................................................................................................................ 935
P_AMS05027............................................................................................................................................ 936
P_AMS05028............................................................................................................................................ 936
P_AMS05029............................................................................................................................................ 937
P_AMS05030............................................................................................................................................ 937
P_AMS05031............................................................................................................................................ 938
P_AMS05032............................................................................................................................................ 938
P_AMS05033............................................................................................................................................ 939
P_AMS05034............................................................................................................................................ 939
P_AMS05035............................................................................................................................................ 940
P_AMS05036............................................................................................................................................ 940
P_AMS05037............................................................................................................................................ 941
P_AMS05038............................................................................................................................................ 941
P_AMS05039............................................................................................................................................ 942
P_AMS05040............................................................................................................................................ 942
P_AMS05041............................................................................................................................................ 943
P_AMS05042............................................................................................................................................ 943
P_AMS05043............................................................................................................................................ 944
P_AMS05500............................................................................................................................................ 944
P_AMS05501............................................................................................................................................ 945
P_AMS05503............................................................................................................................................ 945
P_AMS05505............................................................................................................................................ 946
P_AMS05506............................................................................................................................................ 946
P_AMS05513............................................................................................................................................ 947
P_AMS05516............................................................................................................................................ 947
P_AMS05017............................................................................................................................................ 948
P_AMS05518............................................................................................................................................ 948
P_AMS05519............................................................................................................................................ 949
P_AMS06010............................................................................................................................................ 950
P_AMS06011............................................................................................................................................ 950
P_AMS06012............................................................................................................................................ 951
P_AMS06013............................................................................................................................................ 951
P_AMS06014............................................................................................................................................ 952
P_AMS06015............................................................................................................................................ 952
P_AMS06016............................................................................................................................................ 953
P_AMS06017............................................................................................................................................ 953
P_AMS06018............................................................................................................................................ 954
P_AMS06020............................................................................................................................................ 954
P_AMS07001............................................................................................................................................ 955
P_AMS07004............................................................................................................................................ 955
P_AMS07008............................................................................................................................................ 956
P_AMS07009............................................................................................................................................ 956
P_AMS07010............................................................................................................................................ 957
P_AMS07011............................................................................................................................................ 957
P_AMS07012............................................................................................................................................ 958
P_AMS07013............................................................................................................................................ 958
P_AMS07014............................................................................................................................................ 959
P_AMS07015............................................................................................................................................ 959
P_AMS07016............................................................................................................................................ 960
P_AMS07017............................................................................................................................................ 960
P_AMS07018............................................................................................................................................ 961
P_AMS07019............................................................................................................................................ 961
P_AMS07020............................................................................................................................................ 962
P_AMS07021............................................................................................................................................ 962
P_AMS07022............................................................................................................................................ 963
P_AMS07023............................................................................................................................................ 963
P_AMS07026............................................................................................................................................ 964
P_AMS07031............................................................................................................................................ 964
P_AMS07032............................................................................................................................................ 965
P_AMS07038............................................................................................................................................ 965
P_AMS07039............................................................................................................................................ 966
P_AMS07040............................................................................................................................................ 966
P_AMS07042............................................................................................................................................ 967
P_AMS07043............................................................................................................................................ 967
P_AMS07044............................................................................................................................................ 968
P_AMS07045............................................................................................................................................ 968
P_AMS07100............................................................................................................................................ 969
P_AMS07101............................................................................................................................................ 969
P_AMS07102............................................................................................................................................ 970
P_AMS07103............................................................................................................................................ 970
P_AMS07104............................................................................................................................................ 971
P_AMS07105............................................................................................................................................ 971
P_AMS07200............................................................................................................................................ 972
P_AMS07201............................................................................................................................................ 972
P_AMS07202............................................................................................................................................ 973
P_AMS07203............................................................................................................................................ 973
P_AMS07204............................................................................................................................................ 974
P_AMS08002............................................................................................................................................ 974
P_AMS08003............................................................................................................................................ 975
P_AMS08004............................................................................................................................................ 975
P_AMS08005............................................................................................................................................ 976
P_AMS08500............................................................................................................................................ 976
P_AMS08501............................................................................................................................................ 977
P_AMS08750............................................................................................................................................ 977
P_AMS09502............................................................................................................................................ 978
P_AMS09506............................................................................................................................................ 978
P_AMS09510............................................................................................................................................ 979
P_AMS09702............................................................................................................................................ 979
P_AMS09704............................................................................................................................................ 980
P_AMS09706............................................................................................................................................ 980
P_AMS09708............................................................................................................................................ 981
P_AMS09802............................................................................................................................................ 981
P_AMS09902............................................................................................................................................ 982
P_AMS14000............................................................................................................................................ 982
P_AMS14001............................................................................................................................................ 983
P_AMS14002............................................................................................................................................ 983
P_AMS14003............................................................................................................................................ 984
P_AMS14004............................................................................................................................................ 984
P_AMS14005............................................................................................................................................ 985
P_AMS14006............................................................................................................................................ 985
P_AMS14007............................................................................................................................................ 986
P_AMS14008............................................................................................................................................ 986
P_AMS14009............................................................................................................................................ 987
P_AMS14010............................................................................................................................................ 987
Chapter 29: P_AMS Alarms................................................................................................ 989
P_AMS_0300............................................................................................................................................ 989
P_AMS_0301............................................................................................................................................ 989
P_AMS_0302............................................................................................................................................ 990
P_AMS_0303............................................................................................................................................ 990
P_AMS_0304............................................................................................................................................ 991
P_AMS_0305............................................................................................................................................ 991
P_AMS_0306............................................................................................................................................ 992
P_AMS_0307............................................................................................................................................ 992
P_AMS_0308............................................................................................................................................ 993
P_AMS_0309............................................................................................................................................ 993
P_AMS_0311............................................................................................................................................ 994
P_AMS_0312............................................................................................................................................ 995
P_AMS_0313............................................................................................................................................ 995
P_AMS_0314............................................................................................................................................ 996
P_AMS_0315............................................................................................................................................ 996
P_AMS_0316............................................................................................................................................ 997
P_AMS_0317............................................................................................................................................ 997
P_AMS_0318............................................................................................................................................ 998
P_AMS_0319............................................................................................................................................ 999
P_AMS_0320............................................................................................................................................ 999
P_AMS_0321............................................................................................................................................ 1000
P_AMS_0322............................................................................................................................................ 1000
P_AMS_0323............................................................................................................................................ 1001
P_AMS_0324............................................................................................................................................ 1001
P_AMS_0325............................................................................................................................................ 1002
P_AMS_0330............................................................................................................................................ 1002
P_AMS_0331............................................................................................................................................ 1003
P_AMS_0332............................................................................................................................................ 1003
P_AMS_0333............................................................................................................................................ 1004
P_AMS_0334............................................................................................................................................ 1004
P_AMS_0340............................................................................................................................................ 1005
P_AMS_0341............................................................................................................................................ 1005
P_AMS_0342............................................................................................................................................ 1006
P_AMS_0350............................................................................................................................................ 1006
P_AMS_0351............................................................................................................................................ 1007
P_AMS_0352............................................................................................................................................ 1007
P_AMS_0353............................................................................................................................................ 1008
P_AMS_0354............................................................................................................................................ 1009
P_AMS_0360............................................................................................................................................ 1009
P_AMS_0365............................................................................................................................................ 1010
P_AMS_0376............................................................................................................................................ 1010
P_AMS_0377............................................................................................................................................ 1011
P_AMS_0378............................................................................................................................................ 1011
P_AMS_0379............................................................................................................................................ 1012
P_AMS_0380............................................................................................................................................ 1012
P_AMS_0381............................................................................................................................................ 1013
P_AMS_0382............................................................................................................................................ 1013
P_AMS_0383............................................................................................................................................ 1014
P_AMS_0384............................................................................................................................................ 1014
P_AMS_0385............................................................................................................................................ 1015
P_AMS_0386............................................................................................................................................ 1015
P_AMS_0387............................................................................................................................................ 1016
P_AMS_0388............................................................................................................................................ 1017
P_AMS_0389............................................................................................................................................ 1017
P_AMS_0390............................................................................................................................................ 1018
P_AMS_0391............................................................................................................................................ 1018
P_AMS_0392............................................................................................................................................ 1019
P_AMS_0393............................................................................................................................................ 1019
P_AMS_0394............................................................................................................................................ 1020
P_AMS_0395............................................................................................................................................ 1020
P_AMS_0396............................................................................................................................................ 1021
P_AMS_0397............................................................................................................................................ 1022
P_AMS_0398............................................................................................................................................ 1022
P_AMS_0399............................................................................................................................................ 1023
P_AMS_1100............................................................................................................................................ 1023
P_AMS_1101............................................................................................................................................ 1024
P_AMS_1102............................................................................................................................................ 1024
P_AMS_1103............................................................................................................................................ 1025
P_AMS_1104............................................................................................................................................ 1025
P_AMS_1105............................................................................................................................................ 1026
P_AMS_1106............................................................................................................................................ 1027
P_AMS_1107............................................................................................................................................ 1027
P_AMS_1120............................................................................................................................................ 1028
P_AMS_9500............................................................................................................................................ 1028
P_AMS_9501............................................................................................................................................ 1029
P_AMS_9502............................................................................................................................................ 1030
P_AMS_9503............................................................................................................................................ 1030
P_AMS_9504............................................................................................................................................ 1031
Chapter 1: Events and associated alarms
overview
Event categories
In Avaya Aura Experience Portal, events trigger alarms. Typically, events trigger alarms that are in the
same category with the same suffix. For example, PASR events generate QASR alarms. Although each
alarm has an associated event, not every event generates an alarm.
This section contains information about Avaya Aura Experience Portal events and their associated
alarms. For each event, the event code, its associated alarm code, event message, description of the
event message, the reason that the event is generated, and proposed solutions are described.
Note:
An alarm message is a subset of an event message. You can find detailed information about the alarm,
such as process name, system name, dates, and times, in the event message.
Events and associated alarms overview
Chapter 2: PADMN events
PADMN00001
Event name PADMN00001
Event text Added {0}
Event level Information event. No alarm is generated.
Trigger component Avaya Aura Experience Portal Administration
Problem description
{0} - Provides information about the component that has been added.
To inform users which server or component has been added.
Proposed Solution
About this task
No corrective action is required.
PADMN00002
Event text Changed {0}
Problem description
{0} - Provides information about what has been changed.
PADMN events
To inform users which server or component has been changed.
Proposed Solution
About this task
PADMN00003
Event text Deleted {0}
Problem description
{0} - Provides information for what has been deleted.
To inform users which server or component has been deleted.
Proposed Solution
About this task
PADMN00004
Event text Unknown category
PADMN00005
Problem description
A database error was encountered from an unknown component. This database error was
logged separately.
Proposed Solution
About this task
PADMN00005
Event text EPM is starting up
Problem description
The EPM is starting up.
Proposed Solution
About this task
PADMN00006
Event text EPM is shutting down
PADMN events
Problem description
The EPM is shutting down.
Proposed Solution
About this task
PADMN00007
Event text EPM has started
Problem description
The EPM has started.
Proposed Solution
About this task
PADMN01001
Event text Login
Event level Information event. No alarm is generated
PADMN01002
Problem description
To inform users about log-in data.
Proposed Solution
About this task
PADMN01002
Event text Logoff
Event level Information event. No alarm is generated
Problem description
To inform users about log-off data.
Proposed Solution
About this task
PADMN01003
Event text Failed log-in attempt for user ({0})
PADMN events
Problem description
{0} - Provides information about the user account.
A user could not log in to the system.
Proposed Solution
About this task
PADMN01004
Event text Account locked for user ({0})
Problem description
The system locked out a specific user account.
Proposed Solution
Procedure
The administrator resets the user password.

If the administrator does not reset the password, the user account will recover after the
configured timeout period that the administrator specified in the Account Lockout
Duration field has expired.
PADMN01005
PADMN01005
Event text Alarm threshold for failed logins exceeded for user ({0})
Associate alarm Name: QADMN01005

details
SNMP Trap ID: 17126
Event level Information event.

Minor alarm is generated by default. You can change the severity
for this alarm by logging on to Experience Portal Manager and using
the Alarm Codes page.
Problem description
A user exceeded the maximum log-in attempts that were configured for the user account.
Proposed Solution
About this task
If this problem persists, unauthorized user could be performing illegal log in attempts.
PADMN01006
Event text Reset password for user ({0})
PADMN events
Problem description
{0} - Provides information for the user account.
The system reset the password for a specific user.
Proposed Solution
About this task
PADMN01007
Event text User ({0}) changed password
Problem description
A specific user has changed the user password.
Proposed Solution
About this task
PADMN01008
Event text Added new user ({0}) for "{1}" role
PADMN01009
Problem description
{1} - Provides information about the user role.
The system has added a new user.
Proposed Solution
About this task
PADMN01009
Event text Changed role from "{0}" to "{1}" for user ({2})
Problem description
{0} - Old user role.
{1} - New user role.
The user role has been changed for a specific user.
Proposed Solution
About this task
PADMN events
PADMN01010
Event text Deleted user ({0})
Problem description
A specific user account has been deleted.
Proposed Solution
About this task
PADMN01011
Event text Invalid Authentication File: {0}
Associate alarm Name: QADMN01011

details
SNMP Trap ID: 17902
Event level Error event.

Major alarm is generated by default. You can change the severity
for this alarm by logging in to Experience Portal Manager and using
PADMN01101
Problem description
This event is generated if either the system is not able to access the ASG authentication file
or the authentication file is corrupted or the product/release does not match.
Proposed Solution
About this task
Replace the ASG authentication file with a valid file.
PADMN01101
Event text Starting all MPPs.
Problem description
All Media Processing Platforms (MPPs) are being started through the EPM interface. The EPM
interface user clicked Start All on the System Monitor Web page.
Proposed Solution
About this task
PADMN01102
Event text Stopping all MPPs.
PADMN events
Problem description
All MPPs are being stopped through the EPM interface. The EPM interface user clicked Stop
All on the System Monitor Web page.
Proposed Solution
About this task
PADMN01103
Event text Restarting all MPPs.
Problem description
All MPPs are being restarted through the EPM interface. The EPM interface user clicked
Restart All on the System Monitor Web page.
Proposed Solution
About this task
PADMN01104
Event text Rebooting all MPPs.
PADMN01105
Problem description
All MPPs are being rebooted through the EPM interface. The EPM interface user clicked
Reboot All on the System Monitor Web page.
Proposed Solution
About this task
PADMN01105
Event text Halting all MPPs.
Problem description
All MPPs are being halted through the EPM interface. The EPM interface user clicked Halt All
on the System Monitor Web page.
Proposed Solution
About this task
PADMN01106
Event text Starting MPP {0}.
PADMN events
Problem description
{0} - The name of the MPP.
A specific MPP is being started through the EPM interface. The EPM interface user clicked
Start on the System Details Web page.
Proposed Solution
About this task
PADMN01107
Event text Stopping MPP {0}.
Problem description
A specific MPP is being stopped through the EPM interface. The EPM interface user clicked
Stop on the System Details Web page.
Proposed Solution
About this task
PADMN01108
Event text Restarting MPP {0}.
PADMN01109
Problem description
A specific MPP is being restarted through the EPM interface. The EPM interface user clicked
Restart on the System Details Web page.
Proposed Solution
About this task
PADMN01109
Event text Rebooting MPP {0}.
Problem description
A specific MPP is being rebooted.through the EPM interface. The EPM interface user clicked
Reboot on the System Details Web page.
Proposed Solution
About this task
PADMN events
PADMN01110
Event text Halting MPP {0}.
Problem description
A specific MPP is being halted through the EPM interface. The EPM interface user clicked Halt
on the System Details Web page.
Proposed Solution
About this task
PADMN01111
Event text MPP {0} being placed in online mode.
Problem description
A specific MPP is being placed in online mode through the EPM interface. The EPM interface
user clicked Online on the System Details Web page.
PADMN01112
Proposed Solution
About this task
PADMN01112
Event text MPP {0} being placed in offline mode.
Problem description
A specific MPP is being placed in offline mode through the EPM interface. The EPM interface
user clicked Offline on the System Details Web page.
Proposed Solution
About this task
PADMN01113
Event text MPP {0} being placed in maintenance mode.
PADMN events
Problem description
A specific MPP is being placed in maintenance mode through the EPM interface. EPM interface
user clicked Test on the System Details Web page.
Proposed Solution
About this task
PADMN01114
Event text Operational information updated for MPP {0}.
Problem description
The operational information has been updated for a specific MPP through the EPM
interface.
Proposed Solution
About this task
PADMN01115
Event text Starting MPP {0}.
PADMN01116
Problem description
The specified MPP was starting up.
Proposed Solution
About this task
PADMN01116
Event text Stopping MPP {0}.
Problem description
The specified MPP was stopping.
Proposed Solution
About this task
PADMN events
PADMN01117
Event text Restarting MPPs {0}.
Problem description
The specified MPPs were restarting.
Proposed Solution
About this task
PADMN01118
Event text Rebooting MPPs {0}.
Problem description
The specified MPPs were rebooting.
PADMN01119
Proposed Solution
About this task
PADMN01119
Event text Halting MPPs {0}.
Problem description
The specified MPPs were halting.
Proposed Solution
About this task
PADMN01120
Event text MPPs {0} placed in online mode.
Problem description
PADMN events
The specified MPPs were placed in the online mode.
Proposed Solution
About this task
PADMN01121
Event text MPPs {0} placed in offline mode.
Problem description
The specified MPPs are placed in the Offline mode.
Proposed Solution
About this task
PADMN01122
Event text MPPs {0} placed in maintenance mode.
PADMN01123
Problem description
The specified MPPs are placed in the maintenance mode.
Proposed Solution
About this task
PADMN01123
Event text Sequentially restarting MPPs {0}.
Problem description
Avaya Aura Experience Portal is sequentially restarting the MPPs that are specified in the
event message.
Proposed Solution
About this task
PADMN01124
Event text Sequentially rebooting MPPs {0}.
PADMN events
Problem description
Avaya Aura Experience Portal is sequentially rebooting the MPPs that are specified in the
event message.
Proposed Solution
About this task
PADMN01125
Event text Avaya Aura Experience Portal system information is not available in
the database.
Problem description
The Avaya Aura Experience Portal system information is not in the EPM local database.
Proposed Solution
About this task
PADMN01126
PADMN01126
Event text Attempting to cancel pending state commands for MPPs

{0}.
Problem description
{0} - The name of the MPPs.
Avaya Aura Experience Portal is canceling the pending state commands for the MPPs that
are specified in the event message.
Proposed Solution
About this task
PADMN01127
Event text Cancelled pending state commands for MPPs {0}.
Problem description
Avaya Aura Experience Portal has cancelled the pending state commands for the MPPs that
are specified in the event message.
PADMN events
Proposed Solution
About this task
PADMN01128
Event text MPPs ({0}) do not have any pending state commands
which can be cancelled.
Problem description
There are no pending state commands for the MPPs that are specified in the event message.
Avaya Aura Experience Portal cannot cancel pending state commands for these MPPs.
Proposed Solution
About this task
PADMN01129
Event text EPM needs to be restarted.
Associate alarm name QADMN01129
PADMN01130
Critical alarm is generated by default. You can change the severity

Problem description
The EPM needs to be restarted.
Proposed Solution
About this task
PADMN01130
Event text Upgrade started for MPPs.
Problem description
Upgrade started for MPPs {0}.
On the Software Upgrade page, the administrator has initiated an upgrade of the specified
MPPs.
Proposed Solution
About this task
PADMN events
PADMN01131
Event text Upgrade cancelled.
Problem description
Upgrade cancelled.
On the Software Upgrade page, the administrator has cancelled an upgrade that was in
progress.
Proposed Solution
About this task
PADMN01401
Event text Viewed Log Report
Problem description
The log report was generated.
PADMN01402
Proposed Solution
About this task
PADMN01402
Event text Unable to retrieve log records from the database.
Problem description
The log records could not be retrieved from the database.
Proposed Solution
About this task
PADMN01403
Event text Unable to retrieve product ID.
Problem description
The product ID could not be retrieved.
PADMN events
Proposed Solution
About this task
PADMN01404
Event text No product ID is set, searching for all product

IDs.
Problem description
No product ID was configured.
Proposed Solution
About this task
PADMN01501
Event text Viewed Alarm Report
Problem description
The alarm report was generated and viewed.
PADMN01502
Proposed Solution
About this task
PADMN01502
Event text Unable to retrieve alarm records from the database.
Problem description
The alarm records could not be retrieved from the database.
Proposed Solution
About this task
PADMN01503
Event text Changed Alarm Status
Problem description
The alarm status has been changed.
PADMN events
Proposed Solution
About this task
PADMN01504
Event text Unable to access SNMP notified status
Problem description
Avaya Aura Experience Portal cannot access the SNMP notified status.
Proposed Solution
About this task
PADMN01801
Event text Saved Alarm Settings.
Problem description
The alarm settings were being saved.
PADMN01802
Proposed Solution
About this task
PADMN01802
Event text Saved Log Settings
Problem description
The log settings were being saved.
Proposed Solution
About this task
PADMN01803
Event text Saved Audit Log Settings
Problem description
The audit log settings were saved.
PADMN events
Proposed Solution
About this task
PADMN02101
Event text License Server URL has been updated to {0}
Problem description
{0} - The Uniform Resource Locator (URL) of the license server.
The license server URL has been updated.
Proposed Solution
About this task
PADMN02102
Event text Unable to save license server url {0} in the database
Event level Fatal event. No alarm is generated.
Problem description
{0} - The URL of the license server.
PADMN02103
The license server URL could not be saved in the database due to a database exception. Other
events contain information about the database exception.
Proposed Solution
Procedure
View the log reports to identify events that contain information about the database
exception.
PADMN02103
Event text Unable to save license information in the database.
Problem description
The license information could not be saved in the database due to a database exception. Other
Proposed Solution
Procedure
exception.
PADMN02104
PADMN events
Event text Unable to reset license information in the

database.
Problem description
The license information could not be reset in the database due to a database exception. Other
Proposed Solution
Procedure
exception.
PADMN02105
Event text License grace period has been updated to {0}.
Problem description
{0} - The license grace period in days.
License grace period has been updated.
Proposed Solution
About this task
PADMN02106
PADMN02106
Event text Unable to save the grace period {0} to the

database.
Problem description
{0} - The grace period in days.
The grace period could not be saved to the database because of a database exception. Other
Proposed Solution
Procedure
exception.
PADMN02301
Event text SQL exception while retrieving report data. {0}
Associate alarm details Name: QADMN02301

SNMP Trap ID: 17902

of this alarm by logging in to Experience Portal Manager and using
PADMN events
Problem description
{0} - Provides information about the SQL exception.
The system encountered an SQL exception while retrieving report data.
Proposed Solution
Procedure
1. Ensure that the database is running properly.

2. If the database is not running properly, restart the database, and then restart the
EPM.
3. If data is corrupted in the database, restore the database from a backup.
PADMN02302
Event text Error while creating a chart {0}
Event level Warning event. No alarm is generated.
Problem description
{0} - Provides information about the problem.
The system encountered a problem while creating a chart.
Proposed Solution
Procedure
If the problem persists, contact Avaya Technical Support.
PADMN02303
PADMN02303
Event text Error while reading system configuration database

{0}
Problem description
The system encountered a problem while reading system configuration database.
Proposed Solution
Procedure
1. Ensure that the database is running properly.

2. If the database is not running properly, restart the database, and then restart the
EPM.
PADMN02304
Event text Purged report data from local database.
PADMN events
Problem description
The PurgeReportDataLocalDB script which purges report data from the local database has
been executed successfully.
Proposed Solution
About this task
PADMN02305
Event text Purged report data for Avaya Aura Experience Portal
system {0} from remote database {1}.
Problem description
{0} - The name of the Avaya Aura Experience Portal system report data is being purged for.
{1} - The name of the remote database report data is being purged from.
The PurgeReportDataExtDB script which purges report data for the specified Avaya Aura
Experience Portal system from the external database has been executed successfully.
Proposed Solution
About this task
PADMN02307
PADMN02401
Event text Error while creating the zip file for the data export
{0}.
Event level Error
Problem description
An unexpected exception occurred while creating a Data Export Report file on the EPM server.
{0} contains a description of the problem that occurred.
Proposed Solution
About this task
Verify that sufficient disk space exists for the $CATALINA_HOME/webapps/VoicePortal/
reports directory.
PADMN02401
Event text SIP\: The root CA certificate is not valid. The

certificate is only valid between {0,date,medium}
{0,time,long} and {1,date,medium} {1,time,long}.
Event level Error event. No alarm is generated.
Problem description
{0}{1} - The date and time period that the root CA certificate is valid.
The system encountered an invalid root CA certification for the SIP connection.
PADMN02402
PADMN events
Event text SIP: The root CA certificate will expire in

{0,number,###0.0} days.
Problem description
{0} - The number of days in which the root CA certificate will expire.
PADMN02403
Associated alarm Name: QADMN02403

details
SNMP Trap ID: 17902
Event text SIP: The root CA certificate will expire in

{0,number,###0.0} days.

Major alarm is generated by default. You can change the severity for
this alarm by logging in to Experience Portal Manager and using the
Alarm Codes page.
Problem description
{0} - The number of days in which the root CA certificate will expire.
PADMN03601
Associated alarm Name: QADMN03601

details
SNMP Trap ID: 17902
PADMN03701
Event text {0} consecutive database errors occurred exceeded

max of {1} accessing the configurable application
variables DB.

Alarm Codes page.
Trigger component Avaya Aura Experience Portal administration of application runtime

variables
Problem description
{0} - Provides the number of consecutive database that have occurred since the last successful
request.
{1} - The maximum number of consecutive database errors that have to occur before an alarm
is generated.
Avaya Aura Experience Portal has unsuccessfully attempted to access the Application
Runtime Variables database tables.
Proposed Solution
Procedure
1. Examine the PADMN36xx log entries that occurred before this entry to determine
which table and what database errors have occurred. The errors should specify the
type of problem that occurred and help determine the best course of action to take
to fix the problem.
2. Try rebooting the EPM. If the problem persists and the database appears corrupt,
that is, the tables are missing or there are errors reading/writing the database, then
restore it from backup.
3. If the problem persists, contact Avaya Technical Support.
PADMN03701
Event text Viewed EPM Trace Report.
PADMN events
Event level Information
Problem description
The EPM interface user used the Trace Viewer page to view a EPM trace.
Proposed Solution
About this task
PADMN03702
Event text Viewed MPP Trace Report.
Event level Information
Problem description
The EPM interface user used the Trace Viewer page to view an MPP trace.
Proposed Solution
About this task
PADMN10001
Event text MPP Maintenance: Caught Unknown exception.
PADMN10002
Problem description
The MPP maintenance utility caught an unexpected exception.
Note:
This is not a fatal event. This event does not affect the running state of the MPP.
Proposed Solution
About this task
Manually purged the records and transcriptions.
PADMN10002
Event text MPP Maintenance: {0} purge failed. Directory '{1}'

does not exist.
Problem description
{0} - Provides information about the purge.
{1} - The name of the directory that does not exist.
The MPP maintenance utility deleted records from the following directories:
$AVAYA_MPP_HOME/logs/records
$AVAYA_MPP_HOME/logs/transcriptions
A problem could exist with the environment variable directory $AVAYA_MPP_HOME or with the
directory $AVAYA_MPP_HOME/logs. Either the variable or the directory was not installed
correctly or has been modified.
The system reported an error if it could not find either one of the above directories.
PADMN events
Proposed Solution
Procedure
1. Verify that the environment variable directory $AVAYA_MPP_HOME points correctly

to the MPP installation directory.
2. Verify that the log directory contains the records and transcription directories.
PADMN10003
Event text MPP Maintenance: {0} purge failed. Failed to convert

Retention Days value '{1}' to an integer.
Problem description
{0} - Provides information about the purge.
{1} - The configured Days value.
The MPP maintenance utility received an invalid value for the retention period parameters.
The MPP maintenance utility uses the following parameters to determine the retention period
for records and transcriptions:
rec.calldatarecordretentionperiod
rec.sesdatarecordretentionperiod
rec.transcriptionsretentionperiod
The values of these parameters must be in integers between 0 and 365. Otherwise, the MPP
utility receives an error.
Note:
PADMN10004
Proposed Solution
Procedure
1. Manually delete the records and transcriptions.

2. Check the values entered in the Retention Period (days) for the Call Details
Records, Session Detail Records, and Transcriptions:
a) On the EPM interface, click Global Settings > Record Handling.
a) Ensure that the values for Retention Period (days) entered for Session Data,
Call Data Record, and transcriptions are in integers between 0 and 365.
b) If the values entered are not valid integers, change the values to integers
between 0 and 365. If the values entered are valid integers, go to step d.
c) On the MPP, type param.php <paramname> to check the value for each
parameter.
where <paramname> is the name of the parameter.
d) If the parameter value on the MPP does not match the parameter value on the
EPM, change the parameter value on the EPM following steps a to c.
e) On the MPP, type param.php <paramname> to ensure that the parameter
value entered on the EPM matches the value on the MPP.
where <paramname> is the name of parameter.
3. If the parameter value on the MPP matches the value on the EPM, and you still
receive this warning event, contact Avaya Technical Support.
PADMN10004
Event text MPP Maintenance: {0} purge failed. Bad Retention

Days value '{1}'. Expected value >= 0.
Problem description
{0} - Provides information about the purging.
{1} - Value of the retention period.
PADMN events
The MPP maintenance utility received an invalid value for the retention period parameters.
The MPP maintenance utility uses the following parameters to determine the retention period
for records and transcriptions:
rec.calldatarecordretentionperiod
rec.sesdatarecordretentionperiod
rec.transcriptionsretentionperiod
The values of these parameters must be in integers between 0 and 365. Otherwise, the MPP
utility receives an error.
Note:
Proposed Solution
Procedure
1. Manually delete the records and transcriptions.

2. Check the values entered in the Retention Period (days) for the Call Details
Records, Session Detail Records, and Transcriptions:
a) On the EPM interface, click Global Settings > Record Handling.
a) Ensure that the values for Retention Period (days) entered for Session Data,
Call Data Record, and transcriptions are in integers between 0 and 365.
b) If the values entered are not valid integers, change the values to integers
between 0 and 365. If the values entered are valid integers, go to step d.
c) On the MPP, type param.php <paramname> to check the value for each
parameter.
where <paramname> is the name of the parameter.
d) If the parameter value on the MPP does not match the parameter value on the
EPM, change the parameter value on the EPM following steps a to c.
e) On the MPP, type param.php <paramname> to ensure that the parameter
value entered on the EPM matches the value on the MPP.
where <paramname> is the name of parameter.
3. If the parameter value on the MPP matches the value on the EPM, and you still
receive this warning event, contact Avaya Technical Support.
PADMN10005
PADMN10005
Event text MPP Maintenance: {0} purge failed. Failed to convert

year/month/day value '{1}' to an integer.
Event level Warning event. No alarm generated.
Problem description
{0} - Provides information about the purging.
{1} - Value of the year/month/day.
The MPP maintenance utility received an invalid value for the format of year/month/day.
The MPP maintenance utility expects the year/month/day value to be in YYYY/MM/DD format
for the following directories:
$AVAYA_MPP_HOME/logs/records
$AVAYA_MPP_HOME/logs/transcription
Note:
Proposed Solution
About this task
The warning event is intended to be an alert that indicates a stray directory might have been
deleted.
PADMN10006
PADMN events
Event text MPP {0} {1} {2} deleted from the MPP Server.
Problem description
{0} {1} and {2} - Provide details to what information has been purged.
The MPP maintenance utility reports the number of files that were deleted.
Proposed Solution
About this task
PADMN10007
Event text MPP Maintenance: Caught exception purging {0}

records: {1}.
Associate alarm name Not applicable
Problem description
{0} - The records that have been purged.
{1} - Detailed information about the exception.
The MPP maintenance utility encountered a problem. The records specified in the message
were not deleted. This event does not affect the running state of the MPP.
Proposed Solution
About this task
Manually purged the records and transcriptions.
PADMN10007
PADMN events
Chapter 3: PADTL events
PADTL00018
Event name PADTL00018
Event text View {0}, {1}, {2}, {3}, {4}
Trigger component Alarm and logging component
Problem description
{0}, {1}, {2}, {3}, {4} - The fields in the log or alarm report.
The View Log/Alarm Report has been generated and audited.
Proposed Solution
About this task
PADTL00101
Event text View Audit Log Report
Problem description
The View Audit Log report has been generated and audited.
PADTL events
Proposed Solution
About this task
PADTL00102
Event text Unable to retrieve audit log records from the

database
Problem description
Either the database table did not exist or the database server encountered problems and was
not running properly.
Proposed Solution
Procedure
1. Ensure that the log report can be retrieved from the Avaya Aura Experience Portal
system.
2. Verify that the database server is running properly.
PADTL00103
Event text Error to get audit logger instance
PADTL00103
Problem description
Either the log server was not running properly or the properties files in Tomcat were invalid.
Proposed Solution
Procedure
1. Ensure that the log server is running properly.

2. Ensure that the properties files in Tomcat are valid. Correct the files if they are not
valid.
3. Restart Tomcat.
PADTL events
Chapter 4: PAIWS events
PAIWS_E001
Event name PAIWS_E001
Event text Caught exception {0}!
Trigger component Application interface web service
Problem description
{0} - The exception message.
An exception error occurred. See the exception message for details.
Proposed Solution
About this task
PAIWS_E002
Event text Caught unknown exception!
Problem description
PAIWS events
Proposed Solution
About this task
PAIWS_E003
Event text Caught exception, message = {0}
Problem description
Proposed Solution
About this task
PAIWS_E004
Event text Thread caught exception, message = {0}
Problem description
PAIWS_E005
The Application interface web service polling thread encountered a problem.
Proposed Solution
Procedure
1. Review log reports on the EPM.

2. Collect log files.
3. Contact Avaya Technical Support.
PAIWS_E005
Event text Error accessing property file
Problem description
The property file for the Application Interface web service could not be found or was not
accessible.
Proposed Solution
About this task
Verify that the property file AppIntfws.properties exists in the directory
$CATALINA_HOME/webapps/axis/WEB-INF/classes/ on the EPM.
PAIWS_E006
PAIWS events
Event text Property file is empty
Problem description
The property file for the Application Interface web service was empty.
Proposed Solution
About this task
PAIWS_E007
Event text Instance is null
Problem description
The system could not create an instance of the Application interface web service.
Proposed Solution
About this task
Verify that the Avaya Aura Experience Portal system is properly installed.
PAIWS_E008
PAIWS_E008
Event text MPP Outcall Web Service returned SUCCESS, but no

Session ID!!!
Trigger component Outcall web service
Problem description
The MPP Outcall web service reported a successful LaunchVXML or LaunchCCXML request,
but there was no session ID associated with the request.
Proposed Solution
Procedure
1. Review log reports on the EPM.

PAIWS_E009
Event text Unsupported Load Leveling method
Problem description
The property file for the Application interface web service contained an invalid value.
PAIWS events
Proposed Solution
About this task
PAIWS_E010
Event text Application Interface web service failed to

initialize
Associated alarm Name: QAIWS_E010

details
SNMP Trap ID: 17902

Problem description
The application interface web service failed to initialize. While in this condition, the web service
does not allow customer applications to request outcalls using launchVXML or to launch
CCXML applications using launchCCXML web service methods.
Proposed Solution
Procedure
1. Verify that Tomcat is running properly.

2. Verify that the database is running properly.
3. Verify that the property file AppIntfWS.properties exists in the directory
PAIWS_E011
PAIWS_E011
Event text Failed Web Service access attempt for user ({0})
Trigger component Avaya Aura Experience Portal Web Services
Problem description
A user could not access the web service.
Proposed Solution
About this task
PAIWS_E012
Event text HTTPD Timeout in /etc/httpd/conf/httpd.conf is set

shorter than max allowed connect timeout for
LaunchVXML requests ({0})
Event level Error event. No Alarm is generated
Trigger component Application Interface web service
Problem description
{0} - The maximum timeout allowed to be specified by a LaunchVXML request. This maximum
value is specified in the file voiceportal.properties.
PAIWS events
Proposed Solution 1 Lower the Experience Portal parameter for

maximum allowed timeout
Procedure
1. Modify the MaxLaunchVXMLConnectTimeout parameter in the

voiceportal.properties file to match the Timeout parameter for HTTPD specified in
the /etc/httpd/conf/httpd.conf file on EPM.
2. Restart Tomcat.
3. Restart EPM.
Proposed Solution 2 Increase the HTTPD timeout

Procedure
1. Modify the parameter Timeout for HTTPD specified in the /etc/httpd/conf/

httpd.conf file to match the MaxLaunchVXMLConnectTimeout parameter in the
voiceportal.properties file on the EPM, auxiliary EPM, and MPP servers.
2. Restart any system where the timeout value is changed.
PAIWS_E013
Event text Connect timeout in LaunchVXML request is too long.

({0})
Event level Error event. No Alarm is generated
Trigger component Application Interface web service
Problem description
{0} - The timeout length specified in the LaunchVXML request has caused this event.
PAIWS_F001
Proposed Solution 1 Decrease the timeout length specified in the

LaunchVXML request
Procedure
1. Specify a smaller value in the LaunchVXML request parameter

connectTimeoutSecs. This value should be less than the parameter
MaxLaunchVXMLConnectTimeout in the voiceportal.properties file on EPM.
2. Resend the LaunchVXML request.
Proposed Solution 2 Increase the Experience Portal parameter for

maximum allowed timeout
Procedure
1. Modify the MaxLaunchVXMLConnectTimeout parameter in the

voiceportal.properties file to allow longer timeouts.
Note:
Increase the Timeout parameter for HTTPD specified in the /etc/httpd/conf/
httpd.conf file on the EPM, auxiliary EPM, and MPP servers as the maximum
allowed timeout for Experience Portal cannot exceed the HTTPD timeout.
2. Restart all systems where the timeout value is changed.
PAIWS_F001
Event name PAIWS_F001
Event text Fatal error occurred while attempting to

communicate with MPP {0}
Associate alarm Name: QAIWS_F001

details
SNMP Trap ID: 17903
Event level Fatal event.
PAIWS events

Problem description
A request that was sent to the specified MPP failed to complete.
Proposed Solution
Procedure
1. Restart the EPM.

2. Restart the specified MPP.
PAIWS_F002
Event name PAIWS_F002
Event text Fatal exception (InterruptedException) occurred

while attempting to communicate with MPP {0}
Associate alarm Name: QAIWS_F002

details
SNMP Trap ID: 17903

Critical alarm is generated by default. You can change the severity for
this alarm by logging on to Experience Portal Manager and using the
Alarm Codes page.
Problem description
The Application interface web service was interrupted unexpectedly when it was waiting for a
response from the specified MPP.
PAIWS_W001
Proposed Solution
Procedure
1. Restart the EPM.

2. Restart the specified MPP.
PAIWS_W001
Event name PAIWS_W001
Event text Unable to determine MPP name from session ID string,

{0}
Problem description
{0} - Session ID.
Avaya Aura Experience Portal was unable to determine the name of the MPP when the web
service method SendCCXMLEvent was received.
Proposed Solution
Procedure
1. Verify that the customer application sends the same session ID with the
SendCCXMLEvent request that the customer application received when
responding to the LaunchCCXML request.
2. Verify that the MPP servers are properly configured either in the DNS or in the /
etc/hosts file on the EPM.
PAIWS events
PAIWS_W002
Event text Unable to determine host address for MPP, {0}
Problem description
Avaya Aura Experience Portal is unable to determine the host address of a specific MPP.
Proposed Solution
About this task
PAIWS_W003
Event text Failed to update MPP Info in local table: MPP = {0}
Problem description
The Application Interface web service could not update its local information about a specific
MPP.
PAIWS_W004
Proposed Solution
About this task
PAIWS_W004
Event text MPP Outcall web Service returned MPP DOWN for MPP =
{0}
Problem description
The Outcall web service indicated that the MPP specified in the message is out of service.
Proposed Solution
About this task
PAIWS_W005
Event text MPP Outcall Web Service returned MPP STOPPED for
MPP = {0}
PAIWS events
Problem description
{0} - The name of the MPP
The Outcall web service indicated that the MPP specified in the message has stopped.
Proposed Solution
About this task
PAIWS_W006
Event text Failed to communicate with the MPP Outcall Web

Service on MPP = {0}
Problem description
Avaya Aura Experience Portal failed to communicate with the Outcall web service on the MPP
that is specified in the event message.
Proposed Solution
Procedure
1. From the EPM, go to System Monitor.

2. Verify that the MPP specified in the message is in the Running state.
PAIWS_W007
PAIWS_W007
Event text Data for this MPP not included in total due to error
= {0}, MPP = {1}
Problem description
{0} - The error code from the MPP Outcall web service.
The MPP encountered a problem when responding to a request for its current resources.
Proposed Solution
About this task
PAIWS_W008
Event text Failed to add MPP Info to local table: MPP = {0}
Problem description
The Application interface web service could not add the MPP information in its local table.
PAIWS events
Proposed Solution
About this task
PAIWS_W009
Event text Already initialized!!!
Problem description
There was another instance of the Application interface web service that was running.
Proposed Solution
About this task
PAIWS_W010
Event text Invalid MPP Stat ID received, ID = {0}, MPP = {1}
Problem description
{0} - The invalid statistic ID code.
PAIWS_W011
An invalid statistic ID code was received.
Proposed Solution
About this task
PAIWS_W011
Event text Failed to remove MPP Info from local table: MPP = {0}
Problem description
The Application Interface web service could not remove the MPP information from its local
table.
Proposed Solution
About this task
PAIWS_W012
Event text Failed to update MPP Info in local table: MPP = {0}
PAIWS events
Problem description
The Application interface web service could not update the MPP information in its local
table.
Proposed Solution
About this task
PAIWS_W013
Event text Failed to query resource info for MPP: MPP = {0}
Problem description
The Application Interface web service could not retrieve the resource information from the
MPP.
Proposed Solution
Procedure
1. From the EPM, go to System Monitor.

2. Verify that the MPP specified in the message is in the Running state.
PAIWS_W014
PAIWS_W014
Event text Error adding MPP Information to collection for: MPP

= {0}, HostNetAddr = {1}
Problem description
{1} - The host network address of the MPP.
A duplicated MPP entry was found.
Proposed Solution
About this task
PAIWS_W015
Event text Unsupported Prefix Type or ToURI string: ToURI = {0}
Problem description
{0} - The toURI string that was received with a LaunchVXML or LaunchCCXML request.
An invalid toURI parameter string was received with the LaunchVXML or LaunchCCXML
request.
PAIWS events
Proposed Solution
About this task
Verify that the customer application is passing a valid string in the toURI parameter.
PAIWS_W016
Event text Find_MPP_with_Resource returned an error. No

resources available.
Problem description
The Application interface web service could not locate Outcall resources to process the
LaunchVXML or LaunchCCXML request.
Proposed Solution
Procedure
1. Use the QueryResources request to determine when resources can become

available.
2. Wait for resources to become available to the customer application, and then try the
request again.
PAIWS_W017
Event text MPP Outcall Web Service returned INVALID URI. MPP =
{0}, ToURI = {1}, FromURI = {2}
PAIWS_W018
Problem description
{1} - The toURI string that was received with the LaunchVXML request.
{2} - The fromURI string that was received with the LaunchVXML request.
An invalid toURI or fromURI parameter was received with the LaunchVXML request.
Proposed Solution
About this task
Verify that the customer application is sending a valid string in the toURI or fromURI
parameter.
PAIWS_W018
Event text MPP Outcall Web Service returned INVALID URL. MPP =
{0}, URL = {1}
Problem description
{1} - The invalid URL parameter that was received with the LaunchVXML or LaunchCCXML.
An invalid URL parameter was received with the LaunchVXML or LaunchCCXML request.
Proposed Solution
About this task
Verify that the customer application is sending a valid URL to the LaunchVXML or
LaunchCCXML request.
PAIWS events
PAIWS_W019
Event text MPP Outcall Web Service returned UNKOWN APPLICATION.

MPP = {0}, Application = {1}
Problem description
{1} - The name of the application.
The application name pararmeter that was sent to the LaunchVXML or LaunchCCXML request
did not match the name of a configured Avaya Aura Experience Portal application.
Proposed Solution
Procedure
1. From the EPM, go to the Applications page.

2. Verify that the application name that is specified in the LaunchVXML or
LaunchCCXML request is properly configured.
PAIWS_W020
Event text MPP Outcall Web Service returned NETWORK REFUSAL.

MPP = {0}
PAIWS_W021
Problem description
The MPP could not process the LaunchVXML request because it could not access the
VoiceXML application on the network.
Proposed Solution
About this task
Verify that the connection between the MPP and the application service is functioning
properly.
PAIWS_W021
Event text MPP Outcall Web Service returned an unrecognized

error = {0}. MPP = {1}
Problem description
{0} - The error code from the MPP.
The MPP Outcall web service encountered an error code that was unrecognizable.
Proposed Solution
About this task
PAIWS events
PAIWS_W022
Event text Find_MPP_with_Resource() returned empty or null

MPPName.
Problem description
The Find_MPP_with_Resource() method failed.
Proposed Solution
About this task
PAIWS_W023
Event text getMPPResourceInfo() returned error.
Problem description
The getMPPResourceInfo() method failed.
Proposed Solution
About this task
PAIWS_W024
PAIWS_W024
Event text correctToURI() returned an error = {0}. Message = {1}
Problem description
{0} - The error code.
{1} - The error message.
An error was encountered during the correction of the toURI string.
Proposed Solution
About this task
PAIWS_W025
Event text MPP Outcall Web Service returned FAILED. MPP = {0}
Problem description
The MPP Outcall web service encountered a failure return code when processing a
LaunchCCXML request.
PAIWS events
Proposed Solution
About this task
PAIWS_W026
Event text MPP Outcall Web Service returned INVALID SESSION ID.
MPP = {0}, Session ID = {1}
Problem description
{1} - The session ID.
The MPP Outcall web service could not locate a valid session that matched the session ID in
the SendCCXMLEvent request.
Proposed Solution
About this task
Verify that the customer application sends the same session ID with the SendCCXMLEvent
request that it received when responding to the LaunchCCXML request.
PAIWS_W027
Event text The provided Session ID could not be mapped to a

known MPP. Session ID = {0}
PAIWS_W028
Problem description
The session ID that was generated with the SendCCXML request could not be mapped to a
valid MPP.
Proposed Solution
Procedure
1. Verify that the customer application sends the same session ID with the
SendCCXMLEvent request that it received when responding to the LaunchCCXML
request.
2. Verify that the MPP servers are properly configured either in the DNS or in the /
etc/hosts file on the EPM.
PAIWS_W028
Event text Find_MPP_with_Resource() returned error. rc = {0}
Problem description
The Find_MPP_with_Resource method encountered an unexpected error.
PAIWS events
Proposed Solution
About this task
PAIWS_W029
Event text Failed to update MPP Stat in local table: MPP = {0}
Problem description
The web service encountered an unexpected error when it attempted to update statistics
records in the local table.
Proposed Solution
About this task
PAIWS_W030
Event text Exception occurred: message = {0}
PAIWS_W031
Problem description
An unexpected exception error occurred.
Proposed Solution
About this task
PAIWS_W031
Event text The system name for the MPP could not be resolved.
MPP = {0}
Problem description
The system could not convert the system name into an IP address.
Proposed Solution
About this task
Verify that the MPP server is properly configured either in the DNS or in the /etc/hosts file
on the EPM.
PAIWS_W032
PAIWS events
Event text Request interface thread has woken up and work is not
complete. Count = {0}
Problem description
{0} - The number of times the thread has been woken up before it was complete.
The thread which manages the web service requests from the Application Interface web
service to the Outcall web service on the MPPs was interrupted while it was waiting for the
request to the MPP to be serviced.
Since the thread was not complete the wait is extended in order for the request to complete.
Proposed Solution
About this task
Contact Avaya Technical Support if these events occur excessively.
PAIWS_W033
Event text There were {0} occurrences of the PAIWS_016 warnings

logged for no resources in the last hour.
Problem description
The Application interface web service could not locate Outcall resources to process the
LaunchVXML or LaunchCCXML request.
PAIWS_W033
Proposed Solution
Procedure
1. Use the QueryResources request to determine when resources can become

available.
2. Wait for resources to become available to the customer application, and then try the
request again.
PAIWS events
Chapter 5: PALOG events
PALOG00001
Event name PALOG00001
Event text Unable to load properties file - {0).
Trigger component Avaya Aura Experience Portal logging issues
Problem description
{0} - The name of the properties file.
The properties file was corrupted.
Proposed Solution
Procedure
Do one of the following:

If the properties file has been modified, revert the file to its original version.
If the properties file has not been modified, reinstall the EPM.
PALOG00002
Event text Unable to find configuration file - {0}.

{0} - The name of the property file.
PALOG events
Problem description
The logging component could not find the configuration file.
Proposed Solution
Procedure
1. Reinstall the EPM.

PALOG00003
Event text Time difference configuration not specified.
Problem description
The time difference configuration could not be found, or an invalid value was specified in the
properties file.
Proposed Solution
Procedure
Check the properties file to ensure that the default value was used.
PALOG00004
PALOG00004
Event text Entering reportBatch.
Event level Debug event. No alarm is generated.
Problem description
Entering batch report.
Proposed Solution
About this task
PALOG00005
Event text Exiting reportBatch - {0}.
Problem description
{0} - Provides information about the batch report.
Exiting batch report.
Proposed Solution
About this task
PALOG events
PALOG00006
Event text Decryption error has occurred.
Problem description
The Avaya Aura Experience Portal system encountered a decryption problem. This problem
could be caused by an unauthorized login or user.
Proposed Solution
About this task
Log entries are being dropped.
PALOG00007
Event text Invalid key has been specified - {0}.
Problem description
{0} - The invalid key.
An invalid key was specified. This problem could be caused by an unauthorized login or
user.
PALOG00008
Proposed Solution
About this task
PALOG00008
Event text Number of report entries to be added {0}.
Problem description
{0} - Number of report entries being added.
To inform users about the number of report entries to be added to the system.
Proposed Solution
About this task
PALOG00009
Event text Invalid host has been specified - {0}: {1}
PALOG events
Problem description
{0} - The name of the invalid host.
Avaya Aura Experience Portal encountered an invalid host. This problem could be caused by
an unauthorized login or user.
Proposed Solution
About this task
PALOG00010
Event text Request is out of date.
Problem description
The requested operation is out of date.
Proposed Solution
Procedure
1. Verify that the times displayed on the application server and the EPM are
synchronized.
2. Use Network Time Protocol (NTP) to perform time synchronization on the
application server and the EPM to ensure that the times on the servers are in sync.
For information about performing time synchronization using NTP, see the Avaya
Aura Experience Portal installation manual you used when you installed your
system.
PALOG00011
PALOG00011
Event text Request is in order.
Problem description
The operational request is in process.
Proposed Solution
About this task
PALOG00012
Event text Unable to get a database connection.
Associate alarm details Name: QALOG00012

SNMP Trap ID: 17902

Major alarm is generated by default. You can change the alarm
severity from the System Configuration > Alarm Codes menu in
EPM.
Problem description
Avaya Aura Experience Portal could not establish a connection with the database.
PALOG events
Proposed Solution
Procedure
1. Ensure that the Avaya Aura Experience Portal database is running properly.
2. Verify that the properties file contains the correct URL for the database and account
number.
3. Restart Tomcat.
4. Restart the EPM.
PALOG00013
Event text Unable to locate the jdbc driver.
Associate alarm details Name: QALOG00013

SNMP Trap ID: 17902

Major alarm is generated by default. You can change the alarm
severity from the System Configuration > Alarm Codes menu in
EPM.
Problem description
Avaya Aura Experience Portal could not locate the jdbc driver.
Proposed Solution
Procedure
Reinstall the EPM.
PALOG00014
PALOG00014
Event text Database error has occurred.
Problem description
Details of the exception were logged with other events.
Avaya Aura Experience Portal encountered a problem with the database.
Proposed Solution
Procedure
1. Verify that the application log is being deleted on a regular basis.
Note:
The application log is deleted when CDR and SDR are deleted.
2. Verify that the Avaya Aura Experience Portal database is running properly.
3. If the database is not running properly, restart Postgres, and then restart the EPM
by entering the service epm restart command.
4. Restore the database from a backup.
PALOG00015
Event text Database error cause.
PALOG events
Problem description
The system encountered a problem with the database.
Proposed Solution
Procedure
1. Verify that the application log is being deleted on a regular basis.
Note:
The application log is deleted when CDR and SDR are deleted.
2. Verify that the Avaya Aura Experience Portal database is running properly.
3. If the database is not running properly, restart Postgres, and then restart the EPM
by entering the service epm restart command.
4. Restore the database from a backup.
PALOG00016
Event text Attempted to log same information twice, second one

dropped.
Problem description
Avaya Aura Experience Portal attempted to log the same information twice. But the second
information was not recorded.
PALOG00017
Proposed Solution
About this task
PALOG00017
Event text Last EPM down time is {0} and there can be some log
data lost since that.
Problem description
{0} - The total EPM down time.
The EPM has been down for the specified time. Some of the log data might have been lost
since the down time.
Proposed Solution
About this task
PALOG events
Chapter 6: PAPP events
PAPP_00001
Event name PAPP_00001
Event text Application {0} reported an error from {1} at {2}

with message: {3} {4}
Associated alarm Name: QAPP_00001

details
SNMP Trap ID: 17901
Event level Warning event.

Trigger component Application Logging Web Service.
Problem description
{0 }- Name of the application defined on the application configuration web page.
{1} - Contains the following two data:
Application Server on which the application was running.
Session ID of the application logging the message.
{2} - The timestamp when the log event was issued on the Application Server.
{3} - Message of the application log event.
{4} - (Optional) Variable Name and Variable Value.
Avaya Aura Experience Portal Application has issued a Warning log event.
PAPP events
Proposed Solution
Procedure

PAPP_00002


details
SNMP Trap ID: 17902

Problem description
Avaya Aura Experience Portal Application has issued a Error log event.
PAPP_00003
Proposed Solution
Procedure

PAPP_00003


name
SNMP Trap ID: 17903

Problem description
Avaya Aura Experience Portal Application has issued a Fatal log event.
PAPP events
Proposed Solution
Procedure

Chapter 7: PASR events
PASR_00001
Event name PASR_00001
Event text Could not find an available ASR server.
Trigger component ASR provider that runs within the MPP SessionManager process
Problem description
An ASR server could not be found to satisfy the needs of the requesting application.
Proposed Solution
Procedure
1. Check the ASR server configurations to ensure that they are valid.
2. Ensure that the language being requested by the application and the language
configured for the ASR servers on the EPM are in sync.
3. Verify that the ASR server is running, that it has the correct language installed, and
that the language is functioning properly.
4. Restart the MPP.
PASR_00002
Event text No available ASR ports on server {0}.
PASR events
Problem description
{0} - The name of the ASR server.
All available ASR ports are busy.
Proposed Solution
Procedure
1. On the EPM, verify that the ASR server configurations are correct.
2. Verify that the ASR server is running properly and that the number of the licenses
has not been exceeded.
3. Restart the MPP.
PASR_00003
Event text Failed to get an ASR port!
Problem description
The Avaya Aura Experience Portal system could not locate an ASR port.
Proposed Solution
Procedure
PASR_00004
2. Verify that the ASR server is running properly and that the number of licenses has
not been exceeded.
3. Restart the MPP.
PASR_00004
Event text ASR server properties changed. Updating servers.
Problem description
The ASR server properties have been changed. The ASR servers are being updated.
Proposed Solution
About this task
PASR_00005
Event text Failed initializing ASR server {0}.
Associate alarm Name: QASR_00005

details
SNMP Trap ID: 17198

PASR events
Problem description
The ASR server could not be initialized due to invalid configuration parameters.
Proposed Solution
Procedure
2. Verify that the ASR server is running properly.
3. Verify that the network connection between the ASR server and the MPP is
established.:
a) On the MPP, verify that you can ping the ASR server from the MPP.
b) On the ASR server, verify that you can ping the Media Resource Control
Protocol (MRCP) Network Address that was configured for the MPP on the
EPM.
4. Restart the MPP.
PASR_00006
Event text Failed to convert parameter {0} to type {1} with

error {2}.
Problem description
{0} - The name of the parameter.
{1} - Provides information for the conversion.
{2} - Provides information for the error message.
An error occurred when trying to process configuration parameters.
PASR_00007
Proposed Solution
Procedure
1. Call into the Avaya Aura Experience Portal system to ensure that the system is
functioning properly.
2. If this event persists or if it is accompanied by other problems that occur on the MPP,
restart the MPP.
established.
a) On the MPP, verify that you can connect to the ASR server from the MPP.
b) On the ASR server, verify that you can ping the MRCP Network Address that
was configured for the MPP on the EPM.
PASR_00007
Problem description
{0} - Provides the exception details.
The ASR server encountered an exception.
Proposed Solution
Procedure
PASR events
2. If this event persists or if it is accompanied by other problems that occur on the MPP,
restart the MPP.
established.
a) On the MPP, verify that you can connect to the ASR server from the MPP.
b) On the ASR server, verify that you can ping the MRCP Network Address that
was configured for the MPP on the EPM.
PASR_00008
Event text Caught an unknown exception!
Problem description
The ASR server encountered an unknown exception.
Proposed Solution
Procedure
PASR_00009
PASR_00009
Event text All ports free, reinitializing server {0} for

configuration change now.
Problem description
{0} - The name of the server.
The ASR server reinitialized due to a configuration change.
Proposed Solution
About this task
PASR_00010
Event text There are {1} ports still in use, reinitializing

server {0} for configuration change later.
Problem description
{1} - Number of ports in use.
See event message for details.
PASR events
Proposed Solution
About this task
PASR_00011
Event text No configuration changes found that require

reinitializing for server {0}.
Problem description
{0} The name of the server.
See the event message for details.
Proposed Solution
About this task
PASR_00012
Event text ASR port count must be greater than 0. Initialize

failed!
PASR_00013
Problem description
The ASR component could not be initialized without an ASR port.
Proposed Solution
Procedure
On the EPM, verify that the ASR server configurations are correct.
PASR_00013
Event text ASR server property changes require a restart.
Problem description
The MPP must be restarted to accept new configurations for the ASR server.
Proposed Solution
About this task
PASR_00014
Event text ASR server {0} has had at least {1} consecutive
errors.
PASR events
Problem description
{1} - The number of the consecutive errors.
This event occurs when the ASR server encountered a certain number of consecutive errors.
These events can impact the performance of the MPP and should be resolved as soon as
possible.
Note:
ASR errors are aggregated on the MPP. When viewing the ASR errors on the EPM, you
might only see one error for the past hour.
Proposed Solution
Procedure
1. Review the $AVAYA_MPP_HOME/logs/process/SessMgr.log on the MPP for a

complete list of errors.
2. Review the log files on the ASR server.
PASR_00015
Event text ASR server {0} has had at least {1} consecutive
errors and has been disabled. It must be restarted.
Problem description
{1} - The number of consecutive errors.
PASR_00016
An excessive number of consecutive errors occurred on the specified ASR server. The MPP
removed the ASR server as a resource and marked the ASR server as disabled. The usage
of other ASR servers in the Avaya Aura Experience Portal system is not being affected.
Note:
ASR errors are aggregated on the MPP. When viewing the ASR errors on the EPM, you
Proposed Solution
Procedure
1. Either use listss.php on the MPP or go to Service Menu > Resources > Speech
Servers to view the status of the ASR server. If the server has a value of false, it is
disabled.
2. Review the $AVAYA_MPP_Home/logs/process/SessMgr.log on the MPP for a
3. Review the log files on the ASR server.
4. After resolving the errors, either restart the ASR server or restart the MPP from the
EPM so that the MPP can re-enable the ASR server.
PASR_00016
Event text Configuration or configuration update of ASR server

{0} failed with reason: {1}.
Problem description
{1} - The reason of failure for the configuration update.
The MPP cannot configure the specified ASR server based on the reason that was specified
in the message.
PASR events
Proposed Solution
About this task
Verify that the configurations of the ASR server are accurate.
PASR_00017
Event text Insufficient number of resources for ASR server:

{0}.
Problem description
{0} - The name of the ASR resources for a given ASR server.
Avaya Aura Experience Portal requires the same number of ASR resources for each ASR
server to be the same as the total number of telephony resources.
Proposed Solution
About this task
On the EPM, verify that the total number of ASR resources equals the total number of telephony
resources for the Avaya Aura Experience Portal system.
PASR_00018
Event text The request to remove ASR server {0} from

configuration completed successfully.
PASR_00019
Problem description
The request to remove the specified ASR server from the system has been completed
successfully.
Note:
There could be a delay in the actual time when the ASR server is being deleted because
the ASR resources might be in use when the deletion request was made.
Proposed Solution
About this task
PASR_00019
Event text ASR server failed {2}
Event level Error or Warning event. No alarm is generated.
Problem description
{2} - The details of the error message.
The ASR server failed because of the reasons indicated in the error message.
PASR events
Proposed Solution
About this task
Depending on the error message, verify the following:
There is enough licenses and ports configured for the ASR server.
The application servers are responding in a timely manner. There could be a fetch timeout
for the external grammars.
The ASR server is responding to the MRCP requests in a timely manner. The timeout
value is governed by the response timeout value that is configured for the ASR server on
the EPM.
Chapter 8: PAVB events
PAVB_00001
Event name PAVB_00001
Event text An unknown exception was caught in {0}
Trigger component MPP vxmlmgr process
Problem description
{0} - Provides information for the problem.
See the event message for details. The MPP daemon will restart the vxmlmgr process.
Proposed Solution
Before you begin
If this problem occurs frequently, do the following:
Procedure
1. From the EPM, set the Voice Browser tracing to Finest.

2. Reproduce the problem.
3. Collect the logs by using the MPP Service Menu or use the getmpplogs.sh
script.
PAVB events
PAVB_00002
Event text Could not establish a connection with

SessionManager. IPC: :Connect failed with {0}
Problem description
{0} - The error code that indicates why the connection failed.
The communication channel could not be established between vxmlmgr and SessionManager
after the SessionManager unexpectedly dropped the communication channel to vxmlmgr.
Proposed Solution
Procedure
1. Ensure that SessionManager is running properly. If not, restart the MPP from the
EPM.
2. Ensure that the $AVAYA_MPP_HOME/config/mppconfig.xml file contains the
correct paths to both executable files and that the process names for both
executable files are correct.
PAVB_00003
Event text Browser execution terminated abnormally with reason

the message {0)
PAVB_00004
Problem description
{0} - The reason for the termination of the VoiceXML interpreter execution.
The VoiceXML interpreter could not process a VoiceXML application.
Proposed Solution
Procedure
Ensure that the VoiceXML application is processed correctly.
PAVB_00004
Event text Encountered exception creating new browser instance:

{0}
Problem description
{0} - The invalid configuration data.
The configuration data for the VoiceXML interpreter is invalid. The invalid configuration data
prevents new browser instances from being created.
Proposed Solution
Procedure
1. Ensure that all of the common VoiceXML Interpreter installation directories exist.
2. Ensure that the environment variable $AVBDIR exists and is set properly.
PAVB events
PAVB_00005
Event text Encountered exception creating voice browser

factory: {0}
Problem description
{0} - The invalid configuration data.
The configuration data for the VoiceXML interpreter is invalid. The invalid configuration data
prevents new browser instances from being created.
Proposed Solution
Procedure
1. Ensure that all of the common VoiceXML Interpreter installation directories exist.
2. Ensure that the environment variable $AVBDIR exists and is set properly.
PAVB_00006
Event text IPC connection failed, error {0}
PAVB_00101
Problem description
{0} - The error code that indicates why the connection failed.
The SessionManager unexpectedly dropped the communication channel to vxmlmgr. This
problem can happen because of network problems or restarting of the SessionManager.
Proposed Solution
About this task
Note:
The system will automatically recover. If it does not recover, the event PAVB_00002
occurs.
PAVB_00101
Event text Cannot create inet resource to fetch document.
Problem description
The VoiceXML interpreter failed to create the inet resource during initialization.
Proposed Solution
Procedure
1. Check the vxmlmgr configurations on the MPP for inet settings and fix invalid
configurations or network settings.
PAVB events
PAVB_00102
Event text Failed to initialize inet
Problem description
The VoiceXML interpreter failed to initialize the global inet object.
Proposed Solution
Procedure
1. Check the vxmlmgr configurations and system environment settings on the MPP.
Fix invalid configurations or network settings.
PAVB_00103
Event text SBinetDestroyResource: inet does not exist
Problem description
The VoiceXML interpreter failed to delete the inet resource. The resource could have been
deleted previously due to other errors.
PAVB_00104
Proposed Solution
Procedure
1. Check other related error messages in the log files.

PAVB_00104
Event text Problem related to the URI while initializing

cookies
Problem description
The VoiceXML interpreter failed to initialize one or more cookies. The cookies might not be
available on the disk or they might have been corrupted.
Proposed Solution
Procedure
1. Check the environment settings on the MPP and other related error messages in
the log files.
PAVB_00106
PAVB events
Event text Failed to initialize socket library
Problem description
The winsock startup Application Programming Interface (API) failed. This event is specific only
to the Windows environment.
Proposed Solution
Procedure
1. Check the Windows settings and fix invalid settings.

2. Check other related error messages in the log files.
PAVB_00107
Event text Could not find Internet Explorer version DLL or

version info not available
Problem description
The VoiceXML interpreter failed to retrieve information about the Internet Explorer (IE) version.
This event is specific only to the Windows environment.
PAVB_00109
Proposed Solution
Procedure
Check the version of Internet Explorer that was installed on the system. Internet
Explorer version 6 (IE6) SP2 or later is required.
PAVB_00109
Event text Internet Explorer version info not available
Problem description
The information of the Internet Explorer (IE) version was not available or incomplete. This event
is specific only to the Windows environment.
Proposed Solution
Procedure
PAVB_00110
Event text Bad Internet Explorer version: {0}.{1}.{2}.{3}
PAVB events
Problem description
{0} {1} {2} {3} - The number or digit of the Internet Explorer (IE) version.
Avaya Aura Experience Portal detected an unsupported version of IE. This event is specific
only to the Windows environment.
Proposed Solution
Procedure
PAVB_00111
Event text Fetch timed out while reading from URL stream
Problem description
The VoiceXML interpreter failed to fetch an URL resource due to a timeout.
Proposed Solution
Procedure
1. Check the URL resource and Web server settings, and fix invalid settings.
2. Check all relevant error messages in the log files.
PAVB_00112
PAVB_00112
Event text Error while parsing URL string {0}
Problem description
{0} - The URL string.
The VoiceXML interpreter failed to parse the URL for the VoiceXML application. The URL string
is not in the correct format.
Proposed Solution
Procedure
Check the URL and the VoiceXML application to ensure that the URL is in a correct
format that links properly to the speech application.
PAVB_00113
Event text Failed to create a stream from the URL {0}
Problem description
The VoiceXML interpreter failed to create a stream object. The MPP could be out of
memory.
PAVB events
Proposed Solution
Procedure
1. Check the memory usage on the MPP to ensure that there is sufficient memory.
PAVB_00128
Event text Failed to close inet, return code = {0}
Problem description
{0} - The return code.
The VoiceXML interpreter failed to close the inet stream.
Proposed Solution
Procedure
1. Check the return code.

PAVB_00131
PAVB_00133
Event text Inet read operation failed with return code = {0}
Problem description
The VoiceXML interpreter failed to read a buffer during fetching.
Proposed Solution
Procedure

PAVB_00133
Event text Inet write operation failed with return code = {0}
Problem description
The VoiceXML interpreter failed to write a buffer during posting.
Proposed Solution
Procedure
PAVB events

PAVB_00134
Event text {0} Inet failed setting cookie jar with return code
= {1}
Problem description
{0} - Source information. For Avaya internal use only.
The VoiceXML interpreter failed to get or set a specific cookie jar on the channel.
Proposed Solution
Procedure
1. Check the environment settings.

PAVB_00136
Event text Inet failed getting absolute name for URL {0} with
return code = {1}
PAVB_00137
Problem description
The VoiceXML interpreter failed to generate the absolute name for the specified URL.
Proposed Solution
Procedure

PAVB_00137
Event text Failed getting inet cookie token
Problem description
The VoiceXML interpreter failed to parse the cookie string to get the token.
Proposed Solution
Procedure
1. Check related error messages in the log files.
PAVB events
2. If you cannot resolve the issue from the information in the error messages, contact
Avaya Technical Support.
PAVB_00138
Event text Could not find '=' in cookiespec = {0}
Problem description
{0} - The cookispec string.
The VoiceXML interpreter failed to locate the equal sign in the cookie string.
Proposed Solution
Procedure

PAVB_00139
Event text Failed getting cookie value, cookiespec = {0}
PAVB_00140
Problem description
The VoiceXML interpreter failed to get the cookie value from the cookie string.
Proposed Solution
Procedure

PAVB_00140
Event text Could not find string ,; in cookiespec = {0}
Problem description
The VoiceXML interpreter failed to find the string ",;" in the cookie string.
Proposed Solution
Procedure

PAVB events
PAVB_00141
Event text Failed getting cookie attribute for attributeSpec =

{0}
Problem description
The VoiceXML interpreter failed to get the cookie attribute from the cookie attribute string.
Proposed Solution
Procedure

PAVB_00142
Event text Could not find '=' in cookie attributeSpec = {0} for
attribute = {1}
Problem description
{0} - The cookie attributeSpec string.
PAVB_00143
{1} - The attribute.

The VoiceXML interpreter failed to find the equal sign in the cookie attribute string.
Proposed Solution
Procedure

PAVB_00143
Event text Failed getting cookie value for attributeSpec = {0}

and attribute = {1} and value = {2}
Problem description
{0} - The attributeSpec string.
{2} - The value of the attribute.
The VoiceXML interpreter failed to get the value for a specific attribute in the cookie
attributeSpec string.
Proposed Solution
Procedure
PAVB events
PAVB_00144
Event text Could not find string ,; in attributeSpec: {0},

attribute: {1}, value: {2}
Problem description
{1} - The attribute name.
{2} - The value of the attribute.
The VoiceXML interpreter failed to locate the string ",:" for the specified attribute in the
attributeSpec string
Proposed Solution
Procedure

PAVB_00146
PAVB_00147
Event text Illegal cookie format for attributeSpec = {0} in

attribute {1}
Problem description
The VoiceXML interpreter failed to parse the attributeSpec string.
Proposed Solution
Procedure

PAVB_00147
Event text Local file {0} does not exist
Problem description
{0} - The name of the local file.
The VoiceXML interpreter failed to locate the requested local file on the MPP.
PAVB events
Proposed Solution
Procedure
Verify that the local file is available on the MPP.
PAVB_00148
Event text Failed opening local file {0}
Problem description
The VoiceXML interpreter failed to open the requested local file or cache the file on the MPP.
Proposed Solution
Procedure
1. Verify that the local file is available on the MPP.

2. Check the cache folder size on the MPP.
PAVB_00149
Event text Failed serializing cache validator - out of memory
PAVB_00151
Problem description
The VoiceXML interpreter failed to allocate memory for the cache validator.
Proposed Solution
Procedure
PAVB_00151
Event text Inet failed to read from local file {0}
Problem description
{0} - The name of the local file.
The VoiceXML interpreter failed to read a buffer from the request local file.
Proposed Solution
Procedure
Check the local file on the MPP to ensure that it is not corrupted or locked.
PAVB events
PAVB_00153
Event text Inet failed to read validator from cache since entry
was locked for url = {0}
Problem description
{0} - The name of the URL that was locked.
The VoiceXML interpreter failed to read the validator from the cache.
Proposed Solution
Procedure

PAVB_00156
Event text Connection to the server succeeded but failed to open

cache entry for URL = {0}, and return code = {1}
Problem description
{0} - The name of the URL.
PAVB_00157

The VoiceXML interpreter failed to open and then close the specified cache entry in the cache
folder.
Proposed Solution
Procedure

PAVB_00157
Event text Document was not modified, but failed updating cache
validator for URL = {0}
Problem description
The VoiceXML interpreter failed to update the cache validator for a VoiceXML application
URL.
Proposed Solution
Procedure

PAVB events
PAVB_00159
Event text Successfully fetched from server but failed writing

to cache for URL = {0}
Problem description
The VoiceXML failed to write a buffer to the cache entry.
Proposed Solution
Procedure

PAVB_00160
Event text Failed fetching data from URL {0} because of time out
Problem description
{0} The name of the URL.
PAVB_00161
A timeout happened while reading data.
Proposed Solution
Procedure
Check the Web server and network traffic to ensure that the connectivity is working
properly.
PAVB_00161
Event text Failed reading data from cache for URL {0}
Problem description
An error occurred while reading a buffer from the cache.
Proposed Solution
Procedure

PAVB events
PAVB_00162
Event text Failed to read from URL {0}
Problem description
The VoiceXML interpreter failed to read buffers from either the cache or the Web server.
Proposed Solution
Procedure

PAVB_00163
Event text Failed closing cache stream for URL {0} and return
code = {1}
Problem description
PAVB_00165

The VoiceXML interpreter failed to close a cache stream.
Proposed Solution
Procedure

PAVB_00165
Event text Failed opening cache entry for URL {0}
Problem description
The VoiceXML interpreter failed to open a cache entry.
Proposed Solution
Procedure

PAVB events
PAVB_00166
Event text Failed to get content length from cache validator for
URL: {0}
Problem description
The VoiceXML interpreter failed to get the size of the cache entry.
Proposed Solution
Procedure

PAVB_00167
Event text Failed to get MIME type from cache validator for URL:
{0}
Problem description
PAVB_00169
The VoiceXML interpreter failed to read from the cache entry due to an incorrect MIME type.
Proposed Solution
Procedure

PAVB_00169
Event text Failed closing cache stream with return code = {0}
Problem description
The VoiceXML interpreter failed to close a cache stream due to an error in the stream
handle.
Proposed Solution
Procedure
PAVB events
PAVB_00170
Event text Failed reading validator from cache with return code
= {0}
Problem description
The VoiceXML interpreter failed to read the cache validator for a cache entry.
Proposed Solution
Procedure

PAVB_00173
Event text Failed creating cache validator
Problem description
The VoiceXML interpreter failed to create the validator object after retrieving content from the
memory.
PAVB_00174
Proposed Solution
Procedure

PAVB_00174
Event text Failed closing cache validator for URL = {0} with
return code = {1}
Problem description
The VoiceXML interpreter failed to close the cache stream for the validator after reading it.
Proposed Solution
Procedure

PAVB events
PAVB_00175
Event text Failed closing cache entry for URL = {0} with return
code = {1}
Problem description
The VoiceXML interpreter failed to force a cache stream to close. The normal attempt failed.
Proposed Solution
Procedure

PAVB_00176
Event text Failed writing to cache validator
PAVB_00178
Problem description
The VoiceXML interpreter failed to write into the cache validator the size and MIME type of the
cache entry.
Proposed Solution
Procedure

PAVB_00178
Event text Failed closing cache stream for URL = {0} and return
code = {1}
Problem description
The VoiceXML interpreter failed to close the cache stream after encountering writing errors.
Proposed Solution
Procedure

PAVB events
PAVB_00179
Event text Failed opening cache stream for write since entry was
locked for URL = {0}
Problem description
The VoiceXML interpreter failed to open the cache stream for writing due to the cache entry
being locked.
Proposed Solution
Procedure

PAVB_00180
Event text Failed writing cache validator - Max cache size

exceeded for URL = {0}
Event level Event event. No alarm is generated.
PAVB_00181
Problem description
The VoiceXML interpreter failed to write to the cache because the maximum cache size has
been exceeded.
Proposed Solution
Procedure
Increase the size limit for the cache folder.
PAVB_00181
Event text Failed writing cache validator to cache for URL = {0}
Problem description
The VoiceXML interpreter failed to serialize the cache validator in the memory.
Proposed Solution
Procedure

PAVB events
PAVB_00183
Event text Failed writing cache validator to cache
Problem description
The VoiceXML interpreter failed to write the cache validator to the memory.
Proposed Solution
Procedure

PAVB_00184
Event text Invalid protocol {0} for new http connection
Problem description
{0} - The name of the invalid protocol.
The VoiceXML interpreter failed to initialize the socket library for the http connection due to an
unsupported connection type. The supported connection types are http and https.
PAVB_00185
Proposed Solution
Procedure
Check the application URL for the correct connection type.
PAVB_00185
Event text Unable to get http connection for url = {0}
Problem description
The VoiceXML interpreter failed to locate information, such as the URL and required properties,
to establish an http connection.
Proposed Solution
Procedure

PAVB_00186
PAVB events
Event text Socket time out
Problem description
The VoiceXML interpreter failed to establish an http connection due to a timeout on the
socket.
Proposed Solution
Procedure
Check network connections.
PAVB_00187
Event text Failed initilizing socket for url = {0}
Problem description
The VoiceXML interpreter failed to establish an http connection due to a socket error.
Proposed Solution
Procedure
PAVB_00188
PAVB_00188
Event text No location specified for redirection of url = {0}
Problem description
The VoiceXML interpreter failed to find the destination address for the redirect request.
Proposed Solution
Procedure
Check Web server settings.
PAVB_00189
Event text Invalid location for redirecting url = {0},

location: {1}
Problem description
{1} - The location of the URL.
Failed to parse the redirected URL for the returned location.
PAVB events
Proposed Solution
Procedure
PAVB_00190
Event text Too many redirects for url = {0}
Problem description
The number of redirects for the URL has exceed the limit.
Proposed Solution
Procedure
Check Web server and system configurations.
PAVB_00191
Event text HTTP Error for url = {0}, Method = {1}, HttpStatus =
{2}, HTTPStatusDescription = {3}
PAVB_00193
Problem description
{1} - The connection method for the URL.
{2} - The status of the http connection.
{3} - The description of the http connection status.
The VoiceXML interpreter failed to open an http stream with the information that was given.
Proposed Solution
Procedure
Check Web server settings and network connections.
PAVB_00193
Event text Invalid encoding for url = {0}, EncodingType = : {1},

DefaultType = {2}
Problem description
{1} - The encoding type for the URL.
{2} - The default type for the URL.
An invalid encoding type was encountered. The supported encoding types are as follow:
multipart/form-data
application/x-www-form-urlencoded
PAVB events
Proposed Solution
Procedure
Check the VoiceXML application and the Web server settings.
PAVB_00194
Event text Invalid HTTP version {0} for url {1}
Problem description
{0} - The version of the http connection.
The VoiceXML interpreter failed to retrieve the correct http version from the buffer.
Proposed Solution
Procedure
PAVB_00195
Event text Failed reading from http stream for url = {0}
PAVB_00196
Problem description
The VoiceXML interpreter failed to read one or more http header information from the
stream.
Proposed Solution
Procedure
PAVB_00196
Event text Invalid http status from url = {0}, Method = {1},
HTTPStatus: {2}
Problem description
{1} - The http connection method.
An invalid http status was encountered.
PAVB events
Proposed Solution
Procedure

PAVB_00197
Event text Undefined http status from url = {0}, http status =
{1}
Problem description
The Voice XML browser failed to read or parse one or more http headers from the stream.
Proposed Solution
Procedure
PAVB_00198
PAVB_00198
Event text Failed getting http header value
Problem description
The VoiceXML interpreter failed to get a valid value for one or more returned http headers.
Proposed Solution
Procedure
PAVB_00200
Event text Error in parsing http header {0} for url = {1}
Problem description
{0} - The http header.
The VoiceXML interpreter failed to parse one or more returned HTTP headers. The headers
were ignored.
PAVB events
Proposed Solution
Procedure
PAVB_00202
Event text Failed getting content type from url = {0}
Problem description
The VoiceXML interpreter failed to get a content type for the opened http stream. The browser
used default content type.
Proposed Solution
Procedure
PAVB_00203
Event text Got negative chunk size from url = {0}
PAVB_00204
Problem description
The VoiceXML interpreter failed to get the correct size for the current data chunk.
Proposed Solution
Procedure

PAVB_00204
Event text Either an empty string to parse or stopped at non

hexadecimal character URL: {0}, ChunkSize: {1}
Problem description
{1} - The size of the data chunk from the network.
The VoiceXML interpreter failed to parse current data chunk from the network.
Proposed Solution
Procedure
PAVB events
PAVB_00208
Event text {0} Invalid rule when creating inet proxy matcher.
Rule = {1}
Problem description
{0} - The invalid rule.
{1} - The description of the rule.
The VoiceXML interpreter failed to create the inet proxy matcher due to an invalid value in the
rule string.
Proposed Solution
Procedure

PAVB_00212
Event text Invalid rule when creating inet proxy matcher. There
is extra space in the rule. Rule = {0}
PAVB_00213
Problem description
{0} - The description of the rule.
The VoiceXML interpreter failed to create the inet proxy matcher due to extra spaces in the
rule string.
Proposed Solution
Procedure

PAVB_00213
Event text Fetch time out when opening timed stream for url =
{0}. Timeout was = {1}
Problem description
{0} - The name of the URL
{1} - The length of the timeout.
The VoiceXML interpreter failed to fetch, read, or write the requested URL due to a fetch
timeout.
PAVB events
Proposed Solution
Procedure
Check Web server settings and network connections, and fix any invalid
configurations.
PAVB_00216
Event text {0} Inet validator had an invalid content = {1}
Problem description
{0} - The name of the inet validator.
{1} - The description of the invalid content.
The VoiceXML interpreter failed to process the inet validator due to an invalid content value.
Proposed Solution
Procedure
PAVB_00218
Event text Inet validator had invalid MIME type = {0}
PAVB_00219
Problem description
{0} - The invalid MIME type.
The VoiceXML interpreter failed to process the inet validator due to an invalid MIME type.
Proposed Solution
Procedure
PAVB_00219
Event text IP Address Error. class: {0}, h_errno: {1},

errnoStr: {2}, errno: {3}
Problem description
{0} - The class of the error.
{1} - The error type.
{2} - The error string.
{3} - The error number.
The UNIX/LINUX native call "gethostbyaddr " failed with an error code.
PAVB events
Proposed Solution
Procedure
configurations.
PAVB_00220
Event text IP Address Error. class: {0}, h_errno: {1}
Problem description
{0} - The class of the error.
{1} - The error type.
The UNIX/LINUX native call "gethostbyaddr " failed without giving an error code.
Proposed Solution
Procedure
configurations.
PAVB_00222
PAVB_00224
Event text Socket Error in function {0}, errorName: {1},

errorCode: {2}
Problem description
{0} - The name of the socket function.
{1} - The name of the error.
A Socket API has failed.
Proposed Solution
Procedure
configurations.
PAVB_00224
Event text Socket Error in function {0}, WSA_ERROR_NAME: {1},

errorCode: {2}
Problem description
{1} - The name of the error.
A winsock API has failed. This event is specific only for the Windows environment.
PAVB events
Proposed Solution
Procedure
configurations.
PAVB_00225
Event text Socket Error in function {0}
Problem description
A Socket API has failed with a unknown error.
Proposed Solution
Procedure
configurations.
PAVB_00226
Event text HTTP connection {0}
PAVB_00227
Problem description
{0} - The http connection.
The http connection has been lost due to an unknown error.
Proposed Solution
Procedure
PAVB_00227
Event text An error occurred sending data over a socket.

Connection aborted
Problem description
The http connection has been aborted. The system tried to reconnect.
Proposed Solution
Procedure
configurations.
PAVB events
PAVB_00230
Event text {0} out of memory while allocating {1}
Problem description
{0} - The name of the inet submodule.
{1} - The resource object.
The VoiceXML interpreter failed to allocate memory for the inet resources.
Proposed Solution
Procedure
Check the memory usage on the MPP to ensure that there is sufficient memory.
PAVB_00305
Event text Unable to resolve host name {0}
Problem description
{0} - The name of the host system.
The UNIX/LINUX native Application Programming Interface (API) "my_gethostbyname_r "
failed.
PAVB_01001
Proposed Solution
Procedure
configurations.
PAVB_01001
Event text Failed writing to cache stream since size exceeded

max size of {0}
Problem description
{0} - The number of the maximum cache size.
The cache folder size has exceeded the size limit.
Proposed Solution
Procedure
Increase the cache folder size limit in the configuration.
PAVB_01004
Event text Invalid cache key since length is 0
PAVB events
Problem description
The VoiceXML interpreter failed to create a cache key object.
Proposed Solution
Procedure
PAVB_01016
Event text Invalid cache folder: {0}
Problem description
{0} - The invalid cache folder.
The cache folder name was invalid. It was longer than 8 characters.
Proposed Solution
Procedure
Check the cache folder name in the configuration. Enter a valid name for the cache
folder.
PAVB_01018
PAVB_01018
Event text Failed adding new cache entry to cache entry table
Problem description
The VoiceXML interpreter failed to insert the cache entry into the cache entry table, which was
a STL map object.
Proposed Solution
Procedure
PAVB_01019
Event text Cache entry invalidated or open by another thread
Problem description
The VoiceXML interpreter failed to open the stream for reading due to an invalid cache entry
or a missing cache file.
PAVB events
Proposed Solution
Procedure

PAVB_01020
Event text Failed initializing cache since configured max cache

entry size of {0} is bigger than configured total
cache size of {1}
Problem description
{0} - The number of the maximum cache entry size.
{1} - The total number of cache size.
Invalid cache settings were encountered.
Proposed Solution
Procedure
Check the cache configurations.
PAVB_01021
PAVB_01021
Event text Failed initializing cache since configured low water

mark of {0} is bigger than configured total cache
size of {1}
Problem description
{0} - The configured low water mark.
{1} - The total number of cache size.
Invalid cache settings were encountered.
Proposed Solution
Procedure
Check the cache configurations.
PAVB_01024
Event text Failed creating cache resource since cache interface

did not exist
Problem description
The VoiceXML interpreter failed to allocate memory to create the cache interface.
PAVB events
Proposed Solution
Procedure
PAVB_01026
Event text Failed reading from cache since the cache was not
opened in read mode
Problem description
Invalid cache mode was encountered.
Proposed Solution
Procedure

PAVB_01027
PAVB_01028
Event text Failed reading from cache since the cache's file
pointer was NULL
Problem description
The file pointer for the cache entry was invalid.
Proposed Solution
Procedure

PAVB_01028
Event text IO Error while reading from cache file stream
Problem description
The API ferror() reported an IO error
Proposed Solution
Procedure
PAVB events
PAVB_01029
Event text Failed writing to cache since the cache was not
opened in write mode
Problem description
Invalid cache mode was encountered.
Proposed Solution
Procedure

PAVB_01030
Event text Failed writing to cache since the cache's file

pointer was NULL
Problem description
The file pointer for the cache entry was invalid.
PAVB_01031
Proposed Solution
Procedure

PAVB_01031
Event text IO Error while writing to cache file stream
Problem description
The API ferror() has reported an IO error.
Proposed Solution
Procedure
PAVB_01032
Event text IO Error while closing cache file stream
PAVB events
Problem description
The API fclose() has reported an error.
Proposed Solution
Procedure
PAVB_01033
Event text Failed creating cache mutex for cache entry details
Problem description
The VoiceXML interpreter failed to create the mutex for the cache entry.
Proposed Solution
Procedure
PAVB_01034
PAVB_01034
Event text Failed locking cache entry detail mutex
Problem description
The VoiceXML interpreter failed to lock the mutex. The mutex might have timed out.
Proposed Solution
Procedure

PAVB_01035
Event text IO Error while opening cache entry details
Problem description
The API fopen() encountered an error.
PAVB events
Proposed Solution
Procedure
PAVB_01037
Event text Failed in mutex start read while opening cache entry
details
Problem description
The VoiceXML interpreter failed to acquire the mutex to start reading from the cache entry.
Proposed Solution
Procedure

PAVB_01038
PAVB_01039
Event text IO Error while opening cache entry details for file
{0}
Problem description
{0} - The name of the file.
The API fopen() has reported an error.
Proposed Solution
Procedure
PAVB_01039
Event text Un-supported file mode while opening cache entry

details - got mode {0}
Problem description
The VoiceXML interpreter did not support the requested cache file mode in Read-Create.
Proposed Solution
Procedure
PAVB events
PAVB_01040
Event text Failed setting stream properties for cache entry
Event level Error event. No alarm generated.
Problem description
The VoiceXML interpreter failed to set the last modified or content size information for the cache
entry.
Proposed Solution
Procedure

PAVB_01041
Event text Failed opening cache entry for entry with cache
key {0}
Associate alarm name N/A
PAVB_01045
Problem description
The VoiceXML interpreter failed to allocate memory for the cache entry.
Proposed Solution
Procedure
PAVB_01045
Event text Failed locking cache entry mutex
Problem description
The VoiceXML interpreter was unable to acquire the lock that was required to process the
cache entry.
Proposed Solution
Procedure

PAVB events
PAVB_01046
Event text Failed unlocking cache entry mutex
Problem description
The VoiceXML interpreter was unable to release the lock that was acquired to process the
cache entry.
Proposed Solution
Procedure

PAVB_01048
Event text Failed creating cache entry
PAVB_01049
Problem description
The VoiceXML interpreter failed to allocate memory to create the cache detail object.
Proposed Solution
Procedure
PAVB_01049
Event text Failed to lock mutex entry table
Problem description
The VoiceXML interpreter was unable to acquire the lock that was required to process the
cache table.
Proposed Solution
Procedure

PAVB events
PAVB_01050
Event text Failed to unlock mutex entry table
Problem description
The VoiceXML interpreter was unable to release the lock that was acquired to process the
cache table.
Proposed Solution
Procedure

PAVB_01051
Event text Avoid double initialization of cache dir
PAVB_01052
Problem description
The VoiceXML interpreter detected an existing cache directory while trying to create one.
Proposed Solution
Procedure
Check the cache folder on the MPP.
PAVB_01052
Event text Failed creating the cache path seq num
Event level Warning event. No alarm generated.
Problem description
The VoiceXML interpreter was unable to allocate memory for the cache path seq number.
Proposed Solution
Procedure
PAVB_01053
PAVB events
Event text Failed creating the cache entry table mux
Problem description
The VoiceXML interpreter was unable to allocate memory for the cache table mutex lock.
Proposed Solution
Procedure
PAVB_01054
Event text Failed creating the cache mutex pool
Problem description
The VoiceXML interpreter was unable to allocate memory to create the cache mutex pool.
Proposed Solution
Procedure
PAVB_01055
PAVB_01055
Event text Failed creating the cache size counter
Problem description
The VoiceXML interpreter was unable to allocate memory to create the cache size counter.
Proposed Solution
Procedure
PAVB_01056
Event text Invalid cache directory: {0}
Problem description
{0} - The invalid cache directory.
The specified cache directory is invalid.
PAVB events
Proposed Solution
Procedure
Check the cache folder on the MPP.
PAVB_01057
Event text Failed creating the cache directory: {0}
Problem description
{0} - The cache directory.
The VoiceXML interpreter was unable to create the cache folder.
Proposed Solution
Procedure
Check system disk usage on the MPP.
PAVB_01058
Event text Failed locking the cache entry table mutex for
reading
PAVB_01059
Problem description
The VoiceXML interpreter was unable to acquire the cache entry table lock for reading
operation.
Proposed Solution
Procedure

PAVB_01059
Event text Failed un-locking the cache entry table mutex
Problem description
The VoiceXML interpreter was unable to release the cache entry table lock for reading
operation.
Proposed Solution
Procedure
PAVB events
PAVB_01065
Event text Failed opening cache entry
Problem description
The VoiceXML interpreter failed to open the cache entry.
Proposed Solution
Procedure

PAVB_01073
Event text Failed to get instance of cache manager to release to

cache pool
PAVB_01074
Problem description
The VoiceXML interpreter failed to release its cache manager to the global cache pool.
Proposed Solution
Procedure
Contact Avaya Technical Support.
PAVB_01074
Event text Failed locking cache pool mutex
Problem description
The VoiceXML interpreter failed to lock the global cache pool.
Proposed Solution
Procedure

PAVB_01075
PAVB events
Event text Failed un-locking cache pool mutex
Problem description
The VoiceXML interpreter failed to release the lock in the global cache pool.
Proposed Solution
Procedure

PAVB_01076
Event text Failed allocating cache pool entry array. Out of

Memory
Problem description
The VoiceXML interpreter failed to allocate memory for the global cache pool.
Proposed Solution
Procedure
PAVB_01077
PAVB_01077
Event text Invalid cache pool pointer
Problem description
The VoiceXML interpreter encountered an invalid pointer when accessing the global cache
pool.
Proposed Solution
Procedure

PAVB_01078
Event text Failed finding free cache in cache pool
Problem description
The VoiceXML interpreter failed to obtain a free cache entry in the global cache pool.
PAVB events
Proposed Solution
Procedure
1. Increase cache pool size.

PAVB_01079
Event text Failed creating cache pool Mutex
Problem description
The VoiceXML interpreter failed to create the lock for cache pool.
Proposed Solution
Procedure
PAVB_01080
Event text Failed creating new cache manager for cache pool
PAVB_01081
Problem description
The VoiceXML interpreter failed to locate an instance of the cache manager.
Proposed Solution
Procedure

PAVB_01081
Event text Failed allocating new cache manager for CachePool
Problem description
The VoiceXML interpreter failed to allocate memory for a new instance of the cache
manager.
Proposed Solution
Procedure
PAVB events
PAVB_01082
Event text Failed creating cache manager for CachePool
Problem description
The VoiceXML interpreter has encountered an unknown error when creating a new instance
of the cache manager.
Proposed Solution
Procedure

PAVB_01083
Event text Did not find a free cache entry in cache pool
Problem description
The VoiceXML interpreter has failed to locate a free cache manager.
PAVB_01084
Proposed Solution
Procedure

PAVB_01084
Event text {0} invalid argument for {1}
Problem description
{0} - The API.
(1) - The list of invalid arguments.
The VoiceXML interpreter encountered a list of invalid arguments for an API.
Proposed Solution
Procedure
PAVB_02001
PAVB events
Event text VXIplatformEnableCall: OSBtel Enablecall failed, rc:

{0}
Problem description
The telephony module API EnableCall() failed with an error.
Proposed Solution
Procedure
PAVB_02002
Event text VXIplatformWaitForCall: OSBtel WaitForCall failed,

rc: {0}
Problem description
The telephony module API WaitForCall() failed with an error.
PAVB_02003
Proposed Solution
Procedure
PAVB_02003
Event text SBobjectCreateResource: Error obtaining reference

object for channel: {0}
Problem description
{0} - The channel for the reference object.
The VoiceXML interpreter failed to obtain a reference channel object.
Proposed Solution
Procedure
PAVB_03001
PAVB events
Event text Unable to load VoiceXML DTD. XML parsing error from
DOM. System Id: {0}, in Line {1}, at Column {2},
Exception Message: {3}, File Content: {4}
Problem description
{0} - The system identifier of the entity where the exception occurred.
{1} - The line number where the exception occurred.
{2} - The column number where the exception occurred.
{4} - The content of the VXML file that causes the exception. Log Viewer may truncate the
content for a large VXML file. The complete content can be found in VB log.
The VoiceXML interpreter might have used a corrupted DTD memory.
Proposed Solution
Procedure
PAVB_03003
Event text XML parse error in File {0} at Line {1} with an XML
Exception {2}, File Content: {3}
Problem description
{0} - The URL of the VXML file that causes the exception.
{1} - The line number where the exception occurred.
PAVB_03006

The VoiceXML interpreter might have used a corrupted DTD memory.
Proposed Solution
Procedure
Contact Avaya Technical Support
PAVB_03006
Event text Defaults VoiceXML document is corrupted - no event

attribute on <link> element
Problem description
The event attribute in the VoiceXML element <link> was missing. The VoiceXML element <link>
resided in the default properties file. The XML file that contained the default settings, such as
timeout and event handlers, might have been corrupted.
Proposed Solution
Procedure
Check the file AVB/Data/defaults.xml to ensure that the <link> element contains the
event attribute.
PAVB events
PAVB_03008
Event text Recognize call to platform failed. Return code = {0}
Problem description
{0} - The VXI error code.
A call to the MPP platform to perform a speech or DTMF recognition has failed. Any reason
that results in a recognition failure on the MPP could have triggered this event.
Proposed Solution
Procedure
PAVB_03009
Event text Platform returned an invalid result from recognition
Problem description
The MPP platform implementation returned an invalid C data structure. The VoiceXML
interpreter expects recognition results from the platform to be in a C data structure. This data
structure returned from the platform might have contained invalid fields.
PAVB_03010
Proposed Solution
Procedure
Ensure that the MPP platform implementation returns a valid data structure to the
VoiceXML interpreter.
PAVB_03010
Event text Platform returned an invalid recognition status code

- {0}
Problem description
{0} - The invalid recognition status code.
The recognition result from the MPP platform contained an invalid status code. The VoiceXML
interpreter did not expect the MPP platform implementation to enter an invalid code for the
status field.
Proposed Solution
Procedure
Ensure that the MPP platform enters a valid recognition status code. For valid
recognition status codes, see the integration guide.
PAVB events
PAVB_03011
Event text Platform returned an invalid recognition mode - {0}
Problem description
{0} - The invalid recognition mode.
The MPP platform implementation returned an invalid recognition mode. The recognition result
contained an unexpected mode of recognition. The valid recognition modes are speech and
DTMF.
Proposed Solution
Procedure
Ensure that the MPP platform returns a valid recognition mode according to the
interface definition document.
PAVB_03013
Event text Platform returned a recognition result of zero size.

A minimum size of one is expected.
Problem description
The VoiceXML interpreter has received an invalid recognition result from the MPP platform. If
the platform returns any recognition result, it must contain at least one result.
PAVB_03020
Proposed Solution
Procedure
Ensure that the MPP platform returns a valid recognition result to the VoiceXML
interpreter.
PAVB_03020
Event text Platform must set at least one slot name in a

recognition result
Problem description
The MPP platform implementation has returned an invalid result to the VoiceXML interpreter.
The VoiceXML interpreter expects slot names to be included in the recognition results. A result
without a slot name definition is an invalid result.
Proposed Solution
Procedure

PAVB events
PAVB_03022
Event text Recognition slot names must be defined with type

string
Problem description
The MPP platform implementation returned an invalid result to the VoiceXML interpreter. All
slot names defined in a recognition result must be a string. Any other type, such as integer,
boolean, or float, is considered to be invalid.
Proposed Solution
Procedure

PAVB_03023
Event text Unable to obtain recognition grammar from the

recognition result
PAVB_03024
Problem description
The following are possible reasons for the event to be triggered:
The platform has not returned a reference to a grammar.
The platform has returned a reference to an inactive grammar.
The platform has returned an invalid grammar reference.
A valid recognition result from the MPP platform must contain a reference to an active
grammar.
Proposed Solution
Procedure

PAVB_03024
Event text Platform call returned an inactive grammar
Problem description
The platform has returned a reference to an inactive grammar. A valid recognition result from
the MPP platform must contain a reference to an active grammar.
Proposed Solution
Procedure
PAVB events
PAVB_03025
Event text Platform call returned a non-existent grammar
Problem description
The MPP platform has returned an invalid grammar reference. A valid recognition result from
the platform must contain a reference to an active grammar.
Proposed Solution
Procedure

PAVB_03026
Event text Record call to platform failed. return code = {0}
PAVB_03027
Problem description
A call from the VoiceXML interpreter to the MPP platform to record user utterance has failed
and an error is returned. The MIME type of the recording was not supported on the MPP
platform.
Proposed Solution
Procedure
Check the recording MIME type in the speech application to ensure that it is supported
on the MPP platform.
PAVB_03027
Event text Platform returned an invalid result from recording
Problem description
The MPP platform created a recording result structure and returned the structure to the
VoiceXML interpreter. This event was triggered when the result structure was invalid due to
incorrect platform implementation.
Proposed Solution
Procedure

PAVB events
PAVB_03028
Event text Platform returned an invalid recording status code -

{0}
Problem description
{0} - Contains the invalid status code.
The status of the recording stated in the recording result structure was invalid. The incorrect
status code was generated by the MPP platform.
Proposed Solution
Procedure

PAVB_03029
Event text VXIVectorGetElement failed to return answer
PAVB_03035
Problem description
The recognition result did not contain an answer object due to the MPP platform
implementation error.
Proposed Solution
Procedure

PAVB_03035
Event text Platform returned a recording result of zero size. A

minimum size of one is expected.
Problem description
The MPP platform returned a recording result object with zero size. The platform must return
a recording result object to the VoiceXML interpreter with a size greater than zero. This problem
could be caused by incorrect MPP platform implementation.
Proposed Solution
Procedure

PAVB events
PAVB_03036
Event text Platform must set aleast one slot name in a recording
result, if it returns a recognition result.
Problem description
The recording result did not contain a slot name. The recording result might contain a
recognition result if the recording was terminated by a user utterance or DTMF key press. In
that case, the MPP platform must return a recognition result with a slot name definition.
Proposed Solution
Procedure

PAVB_03037
Event text Unable to obtain recognition grammar from the

recording result
PAVB_03038
Problem description
The recording result contained a recognition result without a reference to an active grammar.
If the recording was terminated by a user utterance or DTMF key press, the recording result
must contain a recognition result with a reference to an active grammar.
Proposed Solution
Procedure

PAVB_03038
Event text Platform call returned an inactive grammar
Problem description
The MPP platform returned an invalid grammar reference in the recognition result in the
recording. The grammar might not exist or was inactive.
Proposed Solution
Procedure

PAVB events
PAVB_03039
Event text Record function call to platform did not produce a

recording
Problem description
The MPP platform failed to create a recording while processing the VoiceXML <record>
element execution. This could be a result of an internal error in the MPP platform
implementation.
Proposed Solution
Procedure

PAVB_03040
Event text Record function call to platform returned invalid

recording duration. Maximum allowed duration is
three hours
PAVB_03041
Problem description
The execution of the VoiceXML <record>element received an invalid recording duration from
the MPP platform due to one or all of the following reasons:
The recording was too long.
Note:
The recording duration is limited by the resources such as disk space. The recording
time can be unlimited if disk space allows.
The platform did not record an utterance from the user.
Proposed Solution
Procedure

PAVB_03041
Event text Unexpected VoiceXML element type in prompt segment
Problem description
The VoiceXML interpreter has encountered an invalid element inside the <prompt> element.
The speech application contained a VoiceXML document that was not valid according to the
VoiceXML DTD that was used by the VoiceXML interpreter.
PAVB events
Proposed Solution
Procedure
Check the speech application for the invalid document and correct the application.
PAVB_03042
Event text Logic error in VoiceXML document. Invalid SSML

element encountered
Problem description
The VoiceXML interpreter has encountered an SSML element that is invalid according to the
SSML 1.0 specification. The speech application contains a VoiceXML document with invalid
SSML elements in it.
Proposed Solution
Procedure
Check the speech application document for invalid SML elements and correct the
speech application.
PAVB_03043
Event text Interpreter internal property list is corrupted
PAVB_03045
Problem description
The VoiceXML interpreter maintained a VoiceXML property list during the execution of a
document. The interpreter encountered a corrupted or invalid property in the property list. The
speech application might have contained an invalid or corrupted property.
Proposed Solution
Procedure
Use the VoiceXML 2.0 specification as a reference, check the speech application or
defaults.xml file for invalid properties.
PAVB_03045
Event text Initial document is not set or empty
Problem description
The MPP has not sent a start URL to the speech application. The start URL of the speech
application was not set.
Proposed Solution
Procedure
Ensure that the MPP always sends a URL string that is not NULL to the VoiceXML
interpreter as the start URL.
PAVB events
PAVB_03046
Event text Received an exception. Exception = {0}
Event level Event error. No alarm is generated.
Problem description
{0} - The name of the exception.
The VoiceXML interpreter might have sent various exceptions during the execution. All
exceptions were not errors.
Proposed Solution
Procedure

PAVB_03047
Event text Received a fatal exception. Description = {0}
Problem description
PAVB_03048
The VoiceXML interpreter has sent a fatal exception and the application execution was
terminated. The following are possible reasons for the exception:
The recording was too long. The maximum recording duration is one hour.
An application error.
A VoiceXML interpreter internal error.
Platform resource errors, such as ASR server or TTS server was not available.
Proposed Solution
Procedure
1. Check the speech application for the error condition that was indicated in the event
message.
2. Check the MPP for the availability of the resource, if that was indicated in the event
message.
PAVB_03048
Event text Received an out of memory exception
Problem description
A memory exception was received. The system was running out of memory and failed to
allocate sufficient memory to execute the speech application.
Proposed Solution
Procedure
Check system memory on the MPP to ensure that there is sufficient memory to execute
the speech application.
PAVB events
PAVB_03049
Event text ECMA script error exception. Description = {0}
Problem description
{0} - The error description.
JavaScript execution from the VoiceXML page has generated an exception. JavaScript in the
application contained an error.
Proposed Solution
Procedure
Correct the JavaScript error in the speech application.
PAVB_03050
Event text Unexpected jump to a VoiceXML dialog happened
Problem description
An error occurred when processing an invalid VoiceXML document.
PAVB_03051
Proposed Solution
Procedure
Verify and modify the VoiceXML application.
PAVB_03051
Event text Unexpected jump to a VoiceXML document happened
Problem description
Proposed Solution
Procedure
PAVB_03052
Event text Unexpected jump to a VoiceXML element happened
PAVB events
Problem description
Proposed Solution
Procedure
PAVB_03053
Event text Unexpected jump from a VoiceXML return element

happened
Problem description
Proposed Solution
Procedure
PAVB_03055
PAVB_03056
Event text Failed loading VoiceXML platform defaults and

received an interpreter event exception: {0}
Problem description
The VoiceXML interpreter failed to load the MPP platform defaults from the file AVB/Data/
defaults.xml. The VoiceXML interpreter has generated an exception with a name in the event
message. The AVB/Data/defaults.xml file might have been corrupted or the file did not exist.
Proposed Solution
Procedure
Check the file AVB/Datadefaults.xml on the MPP.
PAVB_03056
Event text Failed loading default platform properties
Problem description
The VoiceXML interpreter could not load the default platform properties from the file AVB/Data/
defaults.xml. The property syntax in defaults.xml might be incorrect or the file did not exist.
PAVB events
Proposed Solution
Procedure
Check the default.xml file for the correct property syntax of <property
name="propname" value="propvalue"/>.
PAVB_03057
Event text Number of visited documents exceeded the maximum

limit of {0}
Problem description
{0} - The maximum documents.
The VoiceXML application has exceeded the maximum number of documents it can access in
a single session. It is used to interrupt infinite loops from fetching pages forever. This problem
could be caused by one or all of the following reasons:
The Maximum Documents property in Browser Settings is set to a small number (default
is 500).
An error condition occurred during application execution.
Proposed Solution
Procedure
Check Browser Settings to ensure that the Maximum Documents property is set to a
value that is sufficient for the speech application.
PAVB_03059
PAVB_03059
Event text Application URL is empty
Problem description
The MPP has sent an empty start URL to the VoiceXML interpreter.
Proposed Solution
Procedure
Check the start URL for the speech application to ensure that it is not empty.
PAVB_03060
Event text VoiceXML stack depth exceeded the maximum allowed

limit of {0}
Problem description
The VoiceXML execution has exceeded the maximum limit of execution context depth that was
specified in the client.vxi.maxExeStackDepth property in the VoiceXML interpreter
configuration file. The default value is 5.
PAVB events
Proposed Solution
Procedure
Check the VoiceXML interpreter configuration file to ensure that a sufficient value is
set for the client.vxi.maxExeStackDepth property.
PAVB_03061
Event text error.badfetch - unable to open URI: {0}
Problem description
{0} - The name of the document.
An error has occurred while fetching the document that was specified in the event message.
This could be a timeout issue while fetching the document.
Proposed Solution
Procedure
Ensure that the property in the file fetchtimeout in AVB/Data/defaults.xml is set to a

value that is sufficient for the speech application. The default is 5 seconds.
PAVB_03062
PAVB_03063
Event text error.badfetch - unable to read from URI: {0}
Problem description
An error has occurred while fetching the document that was specified in the event message.
This could be a timeout issue while fetching the document.
Proposed Solution
Procedure
Ensure that the property in the file fetchtimeout in AVB/Data/defaults.xml is set to a

value that is sufficient for the speech application. The default is 15 seconds.
PAVB_03063
Event text error.badfetch - unable to parse contents of URI: {0}
Problem description
The document that was specified in the event message has been fetched successfully, but the
VoiceXML interpreter has encountered a parse error. This problem could be caused by one or
all of the following reasons:
The document contained invalid VoiceXML elements.
The document contained ECMA script error.
The document was corrupted or incomplete.
PAVB events
Proposed Solution
Procedure
Check the speech application URL in the event message and correct the page.
PAVB_03064
Event text error.badfetch.http.{0} URI: {1}
Problem description
{0} - The http error code.
{1} - The name of the resource.
An http error occurred while fetching the resource that was specified in the event message.
The error could be a client error (4xx) or a server error (5xx).
Proposed Solution
Procedure
The the client error number is:

4xx, check the speech application to ensure that the URL is valid.
5xx, check the application server to ensure that it can serve the http request for
the URL that was specified in the event message.
PAVB_03098
PAVB_03098
Event text error.badfetch - unknown http error. URI: {0}
Problem description
An unknown error has occurred while fetching the resource that was specified in the event
message.
Proposed Solution
Procedure

PAVB_03099
Event text error.badfetch - unknown error while fetching {0}
Problem description
PAVB events
An unknown error has occurred while fetching the resource that was specified in the event
message.
Proposed Solution
Procedure

PAVB_03100
Event text Document root is empty (Bad VoiceXML document) for

URL = {0}
Problem description
{0} - The name of the VoiceXML document.
The VoiceXML document that was specified in the event message has an invalid or empty
application attribute.
Proposed Solution
Procedure
Check the document that was specified in the event message to ensure that it contains
a valid application attribute.
PAVB_03101
PAVB_03101
Event text Failed to locate current active VoiceXML document
Problem description
An error occurred when the system was looking for a VoiceXML application based on the
information that was generated from the recognition result. The following are possible reasons
for the error:
The recognition result contained an invalid reference to the VoiceXML document.
The speech application contained an invalid VoiceXML document.
Proposed Solution
Procedure
PAVB_03103
Event text Unable to locate form element for a VoiceXML document
PAVB events
Problem description
for the error:
Proposed Solution
Procedure
PAVB_03104
Event text Unnamed VoiceXML element found
Problem description
for the error:
Proposed Solution
Procedure
PAVB_03105
PAVB_03105
Event text Event count exceeded the maximum allowed count of {0}
Problem description
{0} - The maximum number of events.
The predefined limit of events that each form or VoiceXML item can generate has been
exceeded. The following are possible reasons:
The event count was not set to a reasonable value in the platform configuration.
The VoiceXML execution encountered a recursive error.
Proposed Solution
Procedure
1. Set a reasonable value for the event count in the platform settings.
PAVB_03106
Event text Encountered an empty VoiceXML executable element
PAVB events
Problem description
The VoiceXML interpreter reached an Invalid VoiceXML page.
Proposed Solution
Procedure
Correct the speech application.
PAVB_03107
Event text Detected an unexpected VoiceXML executable element.

This element can't be processed.
Problem description
The VoiceXML Interpreter has encountered an invalid VoiceXML document.
Proposed Solution
Procedure
PAVB_03109
Event text Unable to open URI = {0}
PAVB_03110
Problem description
The voiceXML interpreter failed to open the document that was specified in event message.
The following are possible reasons for the event:
The URL did not exist.
A fetch timeout occurred.
A connection error occurred.
Proposed Solution
Procedure

PAVB_03110
Event text Unable to read from URI = {0}
Problem description
The VoiceXML interpreter failed to read data from the URL that was specified in the event
message due to a fetch timeout.
PAVB events
Proposed Solution
Procedure

PAVB_03111
Event text Unable to parse contents of URI = {0}
Problem description
The following are possible reasons for the event to occur:
The document contained VoiceXML error.
The document contained ECMA script error.
Proposed Solution
Procedure

PAVB_03112
PAVB_03112
Event text Unknown error occurred while parsing the XML

document {0}
Problem description
{0} - The XML document.
An error occurred when parsing an invalid VoiceXML document in the speech application.
Proposed Solution
Procedure
PAVB_03151
Event text Reached an unexpected VoiceXML executable element:

{0}
Problem description
An internal error occurred in the VoiceXML interpreter.
PAVB events
Proposed Solution
Procedure
PAVB_03152
Event text Reached an unnamed internal VoiceXML node
Problem description
An internal error occurred in the VoiceXML interpreter.
Proposed Solution
Procedure
PAVB_03154
Event text Unexpected return value from platform in recording.

return code = {0}
PAVB_03155
Problem description
The MPP platform has returned an unexpected return code to the VoiceXML Interpreter while
recording user utterance.
Proposed Solution
Procedure

PAVB_03155
Event text Failed locating VoiceXML element for the grammar

returned from recording
Problem description
The recording result contained a grammar reference to an invalid VoiceXML document.
Proposed Solution
Procedure
PAVB events
PAVB_03156
Event text Failed locating VoiceXML form associated with the

recognition result
Problem description
The recording result contained a grammar reference to an invalid VoiceXML document.
Proposed Solution
Procedure

PAVB_03158
Event text Unexpected return value from VoiceXML object element

execution. Return value = {0}
PAVB_03160
Problem description
The <object> VoiceXML element execution returned an invalid return code.
Proposed Solution
Procedure

PAVB_03160
Event text Unexpected exit from VoiceXML field element
Problem description
The VoiceXML interpreter encountered an application error when running a VoiceXML
<field>element.
Proposed Solution
Procedure
PAVB events
PAVB_03162
Event text Invalid argument in VoiceXML transfer element
Problem description
The <transfer>VoiceXML element contained an invalid attribute.
Proposed Solution
Procedure
Correct the transfer element syntax in the speech application.
PAVB_03163
Event text VoiceXML transfer returns an unexpected value.

Return value: {0}
Problem description
The MPP platform returned an invalid transfer return code.
PAVB_03164
Proposed Solution
Procedure

PAVB_03164
Event text vxi.tel.transfer.status must be defined with type

integer
Problem description
The transfer status from the MPP platform contained an invalid type due to errors in the platform
implementation. The transfer status must be in integer type.
Proposed Solution
Procedure
Check related error messages in the log files. If you cannot troubleshoot the issue from
the error messages, contact Avaya Technical Support.
PAVB_03165
PAVB events
Event text Unexpected VoiceXML transfer status code: {0}
Problem description
{0} - The transfer status code.
The VoiceXML interpreter has detected an invalid transfer status value in the transfer result
from the MPP platform.
Proposed Solution
Procedure

PAVB_03169
Event text Unexpected exit from the VoiceXML menu element
Problem description
The VoiceXML Interpreter encountered an application error. The VoiceXML <menu> element
execution was not completed.
PAVB_03170
Proposed Solution
Procedure
PAVB_03170
Event text Unknown return code from platform in recognition
Problem description
The VoiceXML interpreter received an invalid return code from the MPP platform due to the
platform implementation error.
Proposed Solution
Procedure

PAVB_03172
PAVB events
Event text Failed locating VoiceXML form element associated

with the recognition answer
Problem description
The recognition result from the MPP platform contained grammar reference to an invalid
VoiceXML form element.
Proposed Solution
Procedure

PAVB_03173
Event text Grammar returned from recognition is invalid
Problem description
The grammar reference in the recognition result is invalid due to the MPP platform
implementation error.
Proposed Solution
Procedure
PAVB_03174
PAVB_03174
Event text Failed obtaining VoiceXML field associated with the

grammar from recognition
Problem description
The recognition result from the platform contained a grammar reference to an invalid VoiceXML
field due to the MPP platform implementation error.
Proposed Solution
Procedure

PAVB_03175
Event text Recognition utterance from the platform is not of

string type
PAVB events
Problem description
The user utterance in the recognition result from the MPP platform was not a string. This could
be caused by the MPP platform implementation error.
Proposed Solution
Procedure

PAVB_03176
Event text Recognition slot names from recognition must be of

string type
Problem description
The recognition result from the MPP platform contained slot name type that was not a string.
This could be caused by the MPP platform implementation error.
Proposed Solution
Procedure

PAVB_03177
PAVB_03177
Event text Recognition confidence values from platform must be

of type float
Problem description
The recognition result from the MPP platform contained confidence type that was not a float.
This could be caused by the MPP platform implementation error.
Proposed Solution
Procedure

PAVB_03178
Event text Invalid recognition slot values from platform
Problem description
The slot values in the recognition result contained invalid slots.
PAVB events
Proposed Solution
Procedure

PAVB_03179
Event text Illegal type of slot values from platform
Problem description
The recognition result contained invalid slot values.
Proposed Solution
Procedure

PAVB_03180
PAVB_03181
Event text Illegal recognition result from platform
Problem description
The recognition result retuned by the MPP platform was invalid.
Proposed Solution
Procedure

PAVB_03181
Event text Failed extracting slot names from recognition result

interpretation
Problem description
The VoiceXML interpreter received an invalid slot name in the recognition result that was
generated by the platform. The recognition slot name must be in a string type.
Proposed Solution
Procedure
Verify and fix the platform implementation.
PAVB events
PAVB_03182
Event text Illegal recognition slot names found
Problem description
The VoiceXML interpreter received an invalid slot name in the recognition result that was
generated by the platform. The recognition slot name must be in a string type.
Proposed Solution
Procedure
Verify and fix the platform implementation.
PAVB_03184
Event text Fetching XML data failed with return code {0}
Problem description
The VoiceXML interpreter failed to fetch the document mentioned in the <data> element due
to an invalid URL that was specified in the "arc" attribute.
PAVB_03185
Proposed Solution
Procedure

PAVB_03185
Event text Fetching XML data failed due to a parse error. DOM
Exception code is: {0}, File Content: {1}
Problem description
The document fetched in the <data>element was an invalid XML document.
Proposed Solution
Procedure

PAVB events
PAVB_03186
Event text Failed to read from URL = {0}
Problem description
The following are possible reasons for the error:
Read operation from a socket failed due to a server error.
Read operation failed due to a timeout.
Proposed Solution
Procedure
Check the fetchtimeout field in the platform settings and set the value to a reasonable
number.
PAVB_03188
Event text XML parsing error from DOM Parser. Error message =
{0}, File Content: {1}
PAVB_03189
Problem description
The parsing of the XML data from <data>element failed.
Proposed Solution
Procedure

PAVB_03189
Event text Unable to find VoiceXML root element in document
Problem description
The application has an invalid root element.
Proposed Solution
Procedure
PAVB events
PAVB_03190
Event text Failed to enable grammar. Error Message: {0}
Problem description
VoiceXML interpreter failed to enable a grammar mentioned in the document. An error occurred
in the ASR resource.
Proposed Solution
Procedure
PAVB_03199
Event text {0}Creating platform channel returned invalid

pointer
Problem description
{0} - Source information. For Avaya internal use only.
The VoiceXML interpreter failed to create an instance of platform channel. This is a serious
platform error.
PAVB_03200
Proposed Solution
Procedure
PAVB_03200
Event text Channel {1} is in use. Failed to add a new channel
Problem description
{1} - The channel in use.
A channel with the same channel ID has already been created by the MPP platform, and the
channel was in use.
Proposed Solution
Procedure

PAVB_03201
PAVB events
Event text {0}Failed to create an instance of platform

abstraction
Problem description
The VoiceXML interpreter has failed to create an abstraction of the MPP platform to
communicate to the resources, such as the telephony, ASR, and TTS servers.
Proposed Solution
Procedure

PAVB_03306
Event text Call to platform to create a grammar returned an

invalid grammar pointer
Problem description
A call to create a grammar to the MPP platform failed and returned an invalid grammar
reference to the VoiceXML interpreter.
PAVB_03307
Proposed Solution
Procedure

PAVB_03307
Event text Loading grammar from a string failed. Return Code:

{0}
Problem description
The grammar that was loaded from the given inline grammar failed due to one or all of the
following reasons:
The inline grammar syntax was incorrect
The language in the given inline grammar was not supported by the MPP platform
Proposed Solution
Procedure

PAVB events
PAVB_03308
Event text Failed to create ASR grammar from a string. Platform

call returned invalid grammar
Problem description
The VoiceXML Interpreter failed to load an ASR grammar from the given inline grammar due
to one or all of the following reasons:
The language specified in the inline grammar was not supported by the platform.
Other errors occurred in the MPP platform or the ASR engine.
Proposed Solution
Procedure

PAVB_03309
Event text Failed to create DTMF grammar from a string. Platform

PAVB_03310
Problem description
The VoiceXML interpreter failed to load a DTMF grammar from the given inline grammar due
to invalid inline grammar format.
Proposed Solution
Procedure
Correct the grammar syntax in the speech application.
PAVB_03310
Event text Failed to create ASR grammar from a string. Platform

Problem description
The VoiceXML interpreter failed to load an ASR grammar from the given inline grammar due
to one or all of the following reasons:
The language specified in the inline grammar was not supported by the MPP platform.
Other errors occurred in the MPP platform or the ASR engine.
Proposed Solution
Procedure
Correct the grammar syntax in the speech application.
PAVB events
PAVB_03313
Event text Failed to connect to the prompt resource
Problem description
An error occurred when connecting to the prompt playback system.
Proposed Solution
Procedure
Check the TTS engine and verify the availability of TTS licenses.
PAVB_03314
Event text Failed to create a new VoiceXML execution context
Problem description
The VoiceXML interpreter could not create an execution context for the current document
execution. The system was running out of memory.
PAVB_03315
Proposed Solution
Procedure
PAVB_03315
Event text error.connection.baddestination
Problem description
The destination specified for the transfer was not valid.
Proposed Solution
Procedure

PAVB_03316
Event text error.connection.noresource
PAVB events
Problem description
No telephone ports were available to complete the current operation.
Proposed Solution
Procedure
1. Ensure that there are available telephony ports on the system.

PAVB_03317
Event text error.connection.noauthorization
Problem description
The user had restricted access to perform the current operation.
Proposed Solution
Procedure
Contact the system administrator to get access for this operation.
PAVB_03318
PAVB_03318
Event text error.connection.noroute {0}
Problem description
The operation failed because the destination was not reachable. This could be caused by one
or all of the following reasons:
The destination format was incorrect.
The destination was incomplete.
Proposed Solution
Procedure

PAVB_03319
Event text error.semantic
PAVB events
Problem description
A semantic error occurred while parsing the document. The document might have contained
invalid elements or ECMA scripts.
Proposed Solution
Procedure
Correct the document that contained the errors.
PAVB_03320
Event text error.unsupported.format {0}
Problem description
{0} - The non-supported audio format.
The VoiceXML interpreter encountered an error due to the non-supported audio format by the
MPP platform.
Proposed Solution
Procedure
Fix the audio format to comply with the format that the MPP platform supports.
PAVB_03321
PAVB_03321
Event text error.unsupported.objectname {0}
Problem description
The <object> element implementation was not supported by the MPP platform.
Proposed Solution
Procedure

PAVB_03323
Event text error.unsupported.transfer.blind
Problem description
Blind transfer was not supported by the MPP platform.
PAVB events
Proposed Solution
Procedure

PAVB_03324
Event text error.unsupported.transfer.bridged
Event level Error event. No alarm is supported.
Problem description
Bridge transfer was not supported by the MPP platform.
Proposed Solution
Procedure

PAVB_03325
PAVB_03326
Event text error.unsupported.uri {0}
Problem description
{0} - The URL format.
The URL format given in the event message was not supported. Only HTTP, HTTPS and FILE
protocols are supported.
Proposed Solution
Procedure

PAVB_03326
Event text error.badfetch {0}
Problem description
The VoiceXML interpreter failed to fetch the document from the URL that was specified in the
event message due to one or all of the following reasons:
A timeout occurred.
A connection error occurred.
PAVB events
Proposed Solution
Procedure

PAVB_03328
Event text error.unsupported.language {0}
Problem description
{0} - The name of the language.
The language that was specified in the event message was not supported by the MPP
platform.
Proposed Solution
Procedure

PAVB_03329
PAVB_03329
Event text TTS resource not available
Problem description
The MPP platform could not provide a TTS resource to the browser for the current channel
due to one or all of the following reasons:
There was a connection error between the MPP platform and the TTS engine.
There was not enough TTS licenses available on the TTS server.
Proposed Solution
Procedure

PAVB_03331
Event text Telephony disconnect failed with return code {0}
PAVB events
Problem description
A call to the platform to disconnect the call has failed with an error code that was specified in
the event message.
Proposed Solution
Procedure

PAVB_03332
Event text Failed to load XML DTD, File Content: {0}
Problem description
Failed to load the DTD for XML validation. The VoiceXML interpreter might have used a
corrupted DTD memory.
Proposed Solution
Procedure
PAVB_03333
PAVB_03333
Event text Could not retrieve absolute path of document at URL:

{0}
Problem description
The VoiceXML interpreter failed to expand the relative URL that was specified in the event
message to an absolute URL.
Proposed Solution
Procedure

PAVB_03334
Event text Could not retrieve size of document at URL: {0}
Problem description
PAVB events
The VoiceXML interpreter failed to get the document size for the URL that was specified in the
event message due to invalid http response for the URL that contained the "Content-length"
header.
Proposed Solution
Procedure

PAVB_03335
Event text Got VoiceXML exception: {0}
Problem description
{0} - The exception error.
The VoiceXML interpreter received a VoiceXML exception that was specified in the event
message.
Proposed Solution
Procedure

PAVB_04001
PAVB_04001
Event text HTTP header Content-Length is not set for the URL:
{0}
Problem description
The inet module detected an invalid http header when fetching a prompt resource through the
URL.
Proposed Solution
Procedure
Check the http settings on the Web server that hosts the resource.
PAVB_04002
Event text Failed to transcode the URL {0} from {1} to {2}
Problem description
{1} - The resource type.
PAVB events
{2} - The resource type.

The prompt module failed to transcode the resource from type {1} to {2}
Proposed Solution
Procedure
Correct invalid types in the resource.
PAVB_04005
Event text Prompt fetch failed from the URL: {0} due to zero
content length
Problem description
The inet module failed to fetch the prompt resource that had an invalid http header.
Proposed Solution
Procedure
Check the http settings on the Web server that hosts the resource.
PAVB_04006
PAVB_04007
Event text Failed to fetch and transcode audio file. URL: {0},
MIME type: {1}, Local file: {2}
Problem description
{1} - The MIME type.
{2} - The local audio file.
The inet module encountered an unknown error when trying to fetch and transcode an audio
file.
Proposed Solution
Procedure

PAVB_04007
Event text Unhandled HTTP return status 404 from prompt queuing
Problem description
The inet module detected an unhandled http return code of 404.
PAVB events
Proposed Solution
Procedure
PAVB_04008
Event text Unhandled HTTP return status 500 from prompt queuing
Problem description
The inet module detected an unhandled http return code of 500.
Proposed Solution
Procedure
PAVB_04009
Event text Channel instance is not set for channel number for
channel: {0}
PAVB_04010
Problem description
{0} - The name of the channel.
The prompt module encountered an invalid reference channel object.
Proposed Solution
Procedure
PAVB_04010
Event text Error Creating Audio Manager instance for channel:

{0}
Problem description
The prompt module failed to allocate memory for a new audio manager object.
Proposed Solution
Procedure
PAVB events
PAVB_04011
Event text Unhandled HTTP return status: {0}
Problem description
{0} - The http status code.
The inet module detected an unhandled http status code.
Proposed Solution
Procedure

PAVB_04012
Event text Queuing Unknown MIME type text message for TTS. MIME
type: {0}, text: {1}
Problem description
PAVB_04013
{1} - The text message.

The prompt module failed to queue a TTS prompt due to an unknown MIME type.
Proposed Solution
Procedure
Verify that the MIME type for the TTS is valid.
PAVB_04013
Event text Unable to get MIME type for URL: {0}
Problem description
The prompt module failed to obtain the MIME type for the URL.
Proposed Solution
Procedure
Check the MIME type setting on the Web server that hosts the resource.
PAVB_04015
PAVB events
Event text Transcoded file found in Prompt Cache with file name:
{0} - No transcoding required.
Problem description
{0} - The name of the transcoded file.
The prompt module found a transcoded file in the prompt cache.
Proposed Solution
Procedure
PAVB_04016
Event text Fetching local file (No http status returned)
Problem description
The prompt module detected a local file.
Proposed Solution
Procedure
PAVB_04018
PAVB_04018
Event text Failed to find the cached file with absolute file
name {0}
Problem description
{0} - The name of the cache file.
The prompt module detected a corrupted cache file with the name that is displayed in the event
message.
Proposed Solution
Procedure
PAVB_04041
Event text URI: {0} could not be resolved by Voice Browser.

Sending to platform as a custom resource.
Problem description
PAVB events
The prompt module was unable to resolve the URL that is being sent to the platform as a
custom resource.
Proposed Solution
About this task
PAVB_04045
Event text Queuing Unknown MIME type audio data. MIME type: {0},
Data size (in bytes): {1}
Problem description
{1} - The size of the data.
The prompt module was queuing an audio data with an unknown MIME type.
Proposed Solution
Procedure
Verify that the MIME type is valid and supported by the MPP.
PAVB_05003
PAVB_05005
Event text ECMA Script Engine is already initialized
Problem description
The JSI module has already been initialized.
Proposed Solution
Procedure
PAVB_05005
Event text ECMA Script engine runtime is not initialized
Problem description
The JSI module has not been initialized.
Proposed Solution
Procedure
PAVB events
PAVB_05026
Event text Maximum allowed branching exceeded in ECMA script

engine. Maximum allowed branches: {0}
Problem description
{0} - The maximum allowed branches.
The maximum allowed branches were exceeded in the ECMA script engine.
Proposed Solution
Procedure
Increase the maximum allowed branches in the MPP configuration file.
PAVB_05027
Event text ECMA Script Engine has reported an error. Error

Message: {0}, JS line#: {1}, Line Text: {2}, Token
Text: {3}
Problem description
{1} - The line number for the JSI.
PAVB_06003
{2} - The text in the line number for the JSI.

{3} - The token text.
The JSI detected an error from the ECMA script engine.
Proposed Solution
Procedure
PAVB_06003
Event text Failed to create grammar from URI: {0} Return code =
{1}
Problem description
The rec module failed to create a grammar object from the URI.
Proposed Solution
Procedure

PAVB events
PAVB_06004
Event text Error creating grammar from a string. platform

returned {0}
Problem description
The rec module failed to create a grammar object from a string with a platform error code.
Proposed Solution
Procedure

PAVB_06005
Event text Channel instance is not initialized for channel

number {0}
Problem description
{0} - The channel number.
PAVB_06006
The rec module detected an invalid reference channel object.
Proposed Solution
Procedure
PAVB_06006
Event text Error in reading grammar from file: {0}, Error code
= {1}
Problem description
The rec module failed to read grammar content from the file with an error.
Proposed Solution
Procedure

PAVB events
PAVB_06007
Event text Error in opening grammar file: {0}, Error code = {1}
Problem description
The REC module failed to open the grammar file with an error.
Proposed Solution
Procedure
Verify that the grammar file is correct and valid.
PAVB_06009
Event text Unable to find grammar file: {0}
Problem description
The rec module failed to locate the grammar file that was listed in the event message.
PAVB_06011
Proposed Solution
Procedure
Verify that the grammar file is correct and valid.
PAVB_06011
Event text Failed to set recognition properties. Platform

returned {0}.
Problem description
{0} - The platform returned code.
The rec module failed to set one or more recognition properties with the platform return code
that was listed in the event message.
Proposed Solution
Procedure
Check all relevant error messages in the log files.
PAVB_06013
PAVB events
Event text Failed to fetch grammar from URL {0}. Read retuned a
size zero.
Problem description
The rec module failed to read grammar file from the URL that was listed in the event
message.
Proposed Solution
Procedure
Verify that the grammar URL is valid.
PAVB_06015
Event text Unhandled HTTP return status: {0}, for URI: {1}
Problem description
{0} - The HTTP return status.
The rec module detected an unhandled HTTP return status when fetching the URL through
the inet module.
PAVB_06017
Proposed Solution
Procedure
Check the http setting on the Web server that hosts the URL.
PAVB_06017
Event text Failed to create grammar from URI: {0}. Platform

returned invalid (NULL) grammar
Problem description
The rec module failed to create a grammar object from the URL due to a platform failure.
Proposed Solution
Procedure

PAVB_06018
PAVB events
Event text Couldn't get a valid input mode from recognizer.

Grammar loading might have failed.
Problem description
The rec module failed to get a valid input mode from the platform.
Proposed Solution
Procedure

PAVB_06019
Event text Recognize call to platform failed. return code: {0}
Problem description
The MPP platform returned an error when performing a speech recognition.
Proposed Solution
Procedure
PAVB_06020
PAVB_06020
Event text Platform call to transform recognition result

failed. return code: {0}
Event level Error code. No alarm is generated.
Problem description
The platform failed to transform the recognition result to the VoiceXML interpreter result
object.
Proposed Solution
Procedure

PAVB_07001
Event text ErrorId: {0}, ErrorStr: {1}, MIME: {2}, File: {3}
PAVB events
Problem description
{0} - The error ID.
{1} - The error string.
The telephony module encountered an unknown error when transcoding an audio file.
Proposed Solution
Procedure
PAVB_07002
Event text URL fetch content size is zero
Problem description
The telephony interface detected an invalid content size when fetching an audio file.
Proposed Solution
Procedure
PAVB_07004
PAVB_07004
Event text Getting reference channel for channel number: {0}
Problem description
{0} - The channel number.
The telephony failed to locate a reference channel object.
Proposed Solution
Procedure
PAVB_07005
Event text Unable to get MIME type for file: {0}
Problem description
PAVB events
The telephony module was unable to obtain the MIME type.
Proposed Solution
Procedure
Check the MIME type setting on the Web server that hosts the file.
PAVB_07008
Event text AVBtelTransferBridge: Failed to set recognition

properties.
Problem description
The telephony module failed to set one or more recognition properties during a bridge
transfer.
Proposed Solution
Procedure
PAVB_07009
Event text FetchAudioFormatInet: mime type: {0}
PAVB_07010
Problem description
The telephony module failed to fetch an audio file through the inet module due to an invalid
MIME type.
Proposed Solution
Procedure

PAVB_07010
Event text FetchAudioFormatInet: Fresh internet file Transcode

URL: {0}, MIME: {1}, VisFile: {2}
Problem description
The telephony module failed to perform transcoding on the URL.
PAVB events
Proposed Solution
Procedure
Verify that the correct MIME type is in the audio file.
PAVB_07013
Event text FetchAudioFormatInet: HTTP status {0} ignored
Problem description
{0} - The http status.
The telephony ignored the http status when fetching an audio file. The audio file can still be
processed
Proposed Solution
About this task
PAVB_07016
Event text FetchAudioFromInet: HTTP status 404 ignored. URL:

{0} will not be processed.
PAVB_07017
Problem description
The telephony has ignored the http status code 404 when fetching an audio file. The audio file
will not be processed.
Proposed Solution
Procedure
PAVB_07017
Event text FetchAudioFromInet: Failed to open URL for: {0}
Problem description
{0} - The name of the audio file.
The telephony interface has failed to open an inet stream when fetching the audio file.
Proposed Solution
Procedure
Check the http setting of the audio file.
PAVB events
PAVB_07021
Event text AVBtelTransferBridge: Couldn't get a valid input

mode from recognizer. Grammar loading might have
failed.
Problem description
The telephony module failed to obtain a valid input mode from the platform during a bridge
transfer.
Proposed Solution
Procedure

PAVB_07024
Event text AVBtelTransferBridge: FetchAudioFromInet() returned

unsuccessfully
PAVB_08002
Problem description
The telephony module encountered an unknown error when fetching audio files during a bridge
transfer.
Proposed Solution
Procedure

PAVB_08002
Event text Error during bridge transfer. Error code = {0}
Problem description
The windows platform implementation returned an error during a a bridge transfer.
Proposed Solution
Procedure
PAVB events
PAVB_08003
Event text Error during recognition. Error code = {0}
Problem description
The windows platform implementation returned an error during a speech recognition.
Proposed Solution
Procedure
PAVB_08004
Event text Problem with input audio device
Problem description
The windows platform implementation encountered an unknown error when using an input
audio device.
PAVB_08005
Proposed Solution
Procedure
PAVB_08005
Event text Unable to allocate {0} bytes for grammar
Problem description
{0} - The number of bytes in memory.
The windows platform implementation was unable to allocate memory when creating a
grammar object.
Proposed Solution
Procedure
PAVB_08006
Event text Error creating grammar from file {0}. Error = {1}
PAVB events
Problem description
{0} - The name of the grammar file.
The windows platform implementation was unable to create a grammar object from the
grammar file.
Proposed Solution
Procedure
PAVB_08007
Event text Error creating grammar from string {0}. Error = {1}
Problem description
{0} - The grammar string.
The windows platform implementation was unable to create a grammar object from the
grammar string.
Proposed Solution
Procedure
PAVB_08008
PAVB_08008
Event text {0}Convertion of JSGF String failed: Mismatched { }

pair in message {1}
Problem description
{0} - The JSGF string.
{1} - The message.
The windows platform implementation was unable to convert a JSGF grammar string.
Proposed Solution
Procedure

PAVB_08009
Event text {0}Convertion of JSGF String failed: Empty { } in

message {1}
PAVB events
Problem description
{1} - The message.
The windows platform implementation has failed to convert a JSGF grammar string due to an
empty entry.
Proposed Solution
Procedure

PAVB_08010
Event text {0}Convertion of JSGF String failed: No support for

mixed DTMF and speech grammars
Problem description
{1} - The message.
The windows platform implementation was unable to convert a JSGF grammar string due to
a mixed DTMF and speech grammar format.
PAVB_08011
Proposed Solution
Procedure
PAVB_08011
Event text {0}Convertion of JSGF String failed: Add word failed

for message {1}
Problem description
{1} - The message.
The windows platform implementation failed to convert a JSGF grammar string due to a failure
when adding grammar words.
Proposed Solution
Procedure
PAVB_08012
PAVB events
Event text Logging system is overloaded. All log and trance

message will be dumped until system has caught up
again
Problem description
The logging module encountered an overloaded state and it has started dumping all log and
trace messages in the log queue until the system was able to function properly.
Proposed Solution
About this task
PAVB_08013
Event text Logging system has caught up and logging will resume
Problem description
The logging module recovered from the overloaded state.
Proposed Solution
About this task
Chapter 9: PBUD events
PBUD_00001
Event name PBUD_00001
Event text Backup server configuration was updated
Trigger component Avaya Aura Experience Portal Backup
Problem description
The setup of backup server was updated and saved.
Proposed Solution
Procedure
PBUD_00002
Event text Start verifying backup server.
PBUD events
Problem description
Start verify backup server by checking mount status.
Proposed Solution
Procedure
PBUD_00003
Event text Backup schedule was updated.
Problem description
The schedule for backup was updated and saved.
Proposed Solution
Procedure
PBUD_00004
Event text Backup user component was updated.
PBUD_00005
Problem description
The custom backup components were updated and saved.
Proposed Solution
Procedure
PBUD_00005
Event text Performing backup operation.
Problem description
Start performing backup operation.
Proposed Solution
Procedure
PBUD events
PBUD_00006
Event text Backup environment was initialized.
Problem description
Backup environment was initialized successfully.
Proposed Solution
Procedure
PBUD_00007
Event text Backup DB interface was initialized.
Problem description
Backup DB interface was initialized successfully.
PBUD_00008
Proposed Solution
Procedure
PBUD_00008
Event text Backup scheduler is running.
Problem description
This info indicates the backup scheduler thread is running.
Proposed Solution
Procedure
PBUD_00009
Event text Backup server was verified successfully.
PBUD events
Problem description
The backup server was verified with mounting successfully.
Proposed Solution
Procedure
PBUD_00010
Event text On-Demand backup operation was executed

successfully.
Problem description
The On-Demand backup operation was performed successfully.
Proposed Solution
Procedure
PBUD_00011
Event text Backup operation was canceled.
PBUD_00012
Problem description
The Backup operation was canceled by the user by clicking Cancel Backup.
Proposed Solution
Procedure
PBUD_00012
Event text Scheduled backup operation was executed

successfully.
Problem description
The scheduled backup operation was executed successfully.
Proposed Solution
Procedure
PBUD events
PBUD_00101
Event text Failed to update backup server configuration.
Problem description
Failed to update and save backup server configuration to the Database.
Proposed Solution
Procedure
1. Review failed messages in the log report.

2. Check if the Postgres service is running and verify the EP DB contains backup
related table.
PBUD_00102
Event text Failed on Backup server verification: {0}.
Problem description
{0} Reason of failure on backup server verification.
PBUD_00103
Failed on backup server verification. This type of warning message is logged in the log report,
or displays on server verification dialog.
Proposed Solution
Procedure
1. Review failed messages in the log report or on the Verify Backup Server popup
dialog.
2. Review the settings on Backup Server page and ensure the entered info is
correct.
3. Verify the backup server is reachable and the backup folder was configured with r/
w permission.
PBUD_00103
Event text Failed to update backup schedule.
Problem description
Failed to update and save backup schedule to Database.
Proposed Solution
Procedure

related table.
PBUD events
PBUD_00104
Event text Failed to save backup custom components.
Problem description
Failed to save backup custom components
Proposed Solution
Procedure

related table.
PBUD_00105
Event text Failed to perform on-demand backup.
PBUD_00106
Problem description
Failed to perform on-demand backup.
Proposed Solution
Procedure

2. Check if the backup server was verified successfully. If the verify is OK, then verify
the custom components contain valid entries.
PBUD_00106
Event text Failed to perform scheduled backup.
Problem description
Failed to perform scheduled backup.
Proposed Solution
Procedure

2. Check if the backup server was verified successfully. If the verify is OK, then verify
the custom components contain valid entries.
PBUD events
PBUD_00111
Event text Backup DB Error: DB Driver not found.
Problem description
Backup DB Error: DB Driver not found.
Proposed Solution
Procedure

2. Check if the EP lib include valid version of Postgres DB driver.
PBUD_00112
Event text Backup DB Error: DB connection failed.
Problem description
Backup DB Error: DB connection failed.
PBUD_00113
Proposed Solution
Procedure

2. Verify if the Postgres is running. If yes, then check if the postgres password was
changed.
PBUD_00113
Event text Failed to initialize Database I/F.
Problem description
Failed to initialize Database I/F.
Proposed Solution
Procedure

2. Verify if Postgres is running. If not, restart Postres service. Also check if EP
database exist.
PBUD events
PBUD_00114
Event text Backup DB Error: Caught SQL Exception.
Problem description
Backup DB Error: Caught SQL Exception.
Proposed Solution
Procedure
1. Review failed detailed messages in the log report.

2. Verify if Postgres is running. If yes, verify if the table vpBackupPams exits in EP
database.
PBUD_00115
Event text Backup DB Error: Accessing DB.
Problem description
Error accessing backup parameters in VoicePortal DB.
PBUD_00121
Proposed Solution
Procedure

2. Verify if VoicePortal DB exists. If yes, then verify the tables of vpBackupParms and
vpBackupProps exist.
PBUD_00121
Event text Error loading EP backup properties.
Problem description
Error loading EP backup properties that include custom components.
Proposed Solution
Procedure
1. Mostly likely, the custom components contain invalid entries. Try to verify and
reconfigure entries from the Custom Components page.
PBUD events
PBUD_00122
Event text Error mounting drive.
Problem description
Error mounting backup drive.
Proposed Solution
Procedure
Go to Backup Server page to verify the parameters setting and click on Verify button
to ensure the backup server can be mounted successfully. If not, verify backup
server.
PBUD_00123
Event text Error unmounting drive.
Problem description
Error unmounting drive.
PBUD_00124
Proposed Solution
Procedure
1. The backup folder and mount point was changed.

PBUD_00124
Event text Error on user authentication.
Problem description
Error on user authentication.
Proposed Solution
Procedure
The username or password was not correct at the mount procedure. Try to go to
Backup Server page to apply correct username/password.
PBUD_00125
Event text Error finding folder {0}.
PBUD events
Problem description
{0} The folder path
Error finding folder.
Proposed Solution
Procedure
This was occurred at backup server verification if the back folder was not found. Try
to go to backup server to ensure the back folder was created properly.
PBUD_00126
Event text Error accessing folder {0} with permission.
Associate alarm details Name: QBUD_00126

SNMP Trap ID: 17901
Event level Error event. Minor alarm is generated by default. You can change
the severity for this alarm by logging on to EPM and using the Alarm
Codes page.
Problem description
{0} The folder path
Error accessing folder {0} with permission.
PBUD_00130
Proposed Solution
Procedure
1. The permission of backup folder in backup server was not set properly, make sure
it has the read and write permission.
2. If the file is an old backup file it may need to be manually deleted.
PBUD_00130
Event text Error copying data to backup server, disk may be

full.
Problem description
Error copying data to backup server, disk may be full.
Proposed Solution
Procedure
Verify the backup server has enough free disk space.
PBUD_00131
Event text Error copying files to backup server: {0}.
PBUD events
Problem description
{0} The backup server address
Proposed Solution
Procedure
The permission of backup folder in backup server was not set properly, make sure it
has r/w permission.
PBUD_00141
Event text Failed to perform EP backup data.
Associate alarm details Name: QBUD_00141

SNMP Trap ID: 17901

for this alarm by logging on to Experience Portal Manager and
using the Alarm Codes page.
Problem description
Failed to perform EP backup data.
Proposed Solution
Procedure
1. Review failed messages in the log report to identify the cause.
PBUD_00151
2. Verify the backup server can be mounted successfully. if yes, perform back up
operation.
3. If back up operation is still failed, try to restart EPM.
PBUD_00151
Event text Error encrypting EP backup data.
Event level Informational event. No alarm is generated.
Problem description
The properties file could not be encrypted.
Proposed Solution
Procedure

2. Verify if there is enough disk space left on the Backup Server.
PBUD_00152
Event text Error deleting the unencrypted EP Properties file.
PBUD events
Problem description
The unecrypted properties file could not be deleted after it has been encrypted.
Proposed Solution
Procedure
PBUD_00154
Event text Error encrypting secret key.
Problem description
The secret key for the EP data file could not be encrypted.
Proposed Solution
Procedure
Chapter 10: PCDH events
PCDH_00001
Event name PCDH_00001
Event text Unable to access configuration data in {0}
Associate alarm Name: QCDH_00001

details
SNMP Trap ID: 17127

Problem description
{0} - The function that was being performed by the CDH scheduler.
The CDH scheduler could not access the database to retrieve data such as schedule
information, status, or the URLs of the MPPs.
Proposed Solution
Procedure
1. During the scheduled download time, use the EPM Log Viewer to monitor the
Reporting category log entries to determine if the problem is reoccurring.
2. If the message contains a database specific error code, consult the documentation
provided by your database vendor.
3. To restore the reporting database:
a) Shutdown Tomcat.
b) Restart the database server.
PCDH events
c) Restart Tomcat.
d) If the problem persists, restore the reporting database from a backup.
4. Export the Reporting category log entries by using the EPM Log Viewer.
PCDH_00002
Event text Unprocessed scheduled event found for today at {0}
Problem description
{0} - The time that the unprocessed scheduled event was found.
The CDH scheduler started to process a scheduled download request.
Proposed Solution
About this task
PCDH_00003
Event text Scheduled event completed
PCDH_00004
Problem description
The CDH scheduler completed the scheduled download request successfully.
Proposed Solution
About this task
PCDH_00004
Event text Exception while processing data from CDH webservice

{0}
Problem description
{0} - Provides information about the exception.
The CDH scheduler encountered problems when downloading CDR or SDR records from an
MPP. This could be caused by network outage during the scheduled download time.
Proposed Solution
Procedure
1. Refer to the PCDH_00010 event on the log report to determine the name of the
affected MPP.
PCDH events
PCDH_00005
Event text Could not connect to CDH webservice at {0}
Problem description
{0} - The URL of the Web service.
The CDH scheduler could not connect to the Web service on the MPP that provided CDR and
SDR data.
Proposed Solution
Procedure
PCDH_00006
Event text SQL exception occurred {0}
Associate alarm details Name: QCDH_00006

SNMP Trap ID: 17902

of this alarm by logging in to Experience Portal Manager and using
PCDH_00007
Problem description
The CDH scheduler encountered a problem when inserting CDR or SDR records to the Avaya
Aura Experience Portal database on the EPM.
Proposed Solution
Procedure
1. During the scheduled download time, use the EPM Log Viewer to monitor the
Reporting category log entries to determine if the problem is reoccurring.
2. If the message contains a database specific error code, consult the documentation
provided by your database vendor.
3. To restore the reporting database:
a) Shutdown Tomcat.
b) Restart the database server.
c) Restart Tomcat.
d) If the problem persists, restore the reporting database from a backup.
4. Export the Reporting category log entries by using the EPM Log Viewer.
PCDH_00007
Event text CDH WebService returned error {0}
Problem description
The Web service on an MPP encountered problems when accessing the CDR and SDR files
on the MPP.
PCDH events
Proposed Solution
Procedure
PCDH_00008
Event text The scheduled event completed with errors. View

log category Call Data Handler for more
information.
Associate alarm Name: QCDH_00008

details
SNMP Trap ID: 17132

Minor alarm is generated by default. You can change the severity for
Alarm Codes page.
Problem description
The CDH scheduler has completed the scheduled download request. However, it encountered
problems when downloading or saving CDR or SDR records from at least one of the MPPs.
Proposed Solution
Procedure
1. Review all the CDH events that occurred during the scheduled download time.
2. Identify all the error events.
PCDH_00009
A CDH error indicates a communication problem between the MPP and the EPM
during the scheduled download time. The error might also indicate database
exceptions when adding CDR or SDR records.
PCDH_00009
Event text Purging CDR records prior to {0}
Event level Information event. No alarms generated.
Problem description
{0} - The timestamp then CDR records were being deleted.
The CDH scheduler was deleting CDR records before the time displayed in the event
message.
Proposed Solution
About this task
PCDH_00010
Event text Getting data from {0}
Problem description
PCDH events
The CDH scheduler started to process CDR and SDR from the specified MPP.
Proposed Solution
About this task
PCDH_00011
Event text Processed {0} CDR records from {1}
Problem description
{0} - Number of CDR records being processed.
The CDH scheduler completed processing CDR records from the specified MPP. The number
of downloaded CDR was displayed in the event message.
Proposed Solution
About this task
PCDH_00012
Event text Processed {0} SDR records from {1}
PCDH_00013
Problem description
{0} - Number of SDR records being processed.
The CDH scheduler completed processing SDR records from the specified MPP. The number
of downloaded SDR was displayed in the event message.
Proposed Solution
About this task
PCDH_00013
Event text Purging SDR records prior to {0}
Problem description
{0} - The timestamp when SDR records were being deleted.
The CDH scheduler was deleting SDR records before the time that was displayed in the event
message.
Proposed Solution
About this task
PCDH events
PCDH_00014
Event text Purging ADR records prior to {0}
Problem description
{0} - The timestamp when ADR records were being deleted.
The CDH scheduler was deleting ADR records before the time that was displayed in the event
message.
Proposed Solution
About this task
PCDH_00015
Event text Processed {0} VXML Log Tags from {1}
Problem description
{0} - The number of the processed VoiceXML log tags.
The specified number of VoiceXML log tags from the specified MPP have been processed.
PCDH_00016
Proposed Solution
About this task
PCDH_00016
Event text Processed {0} CCXML Log Tags from {1}
Problem description
{0} - The number of the processed CCXML log tags.
The specified number of CCXML log tags from the specified MPP have been processed.
Proposed Solution
About this task
PCDH_00017
Event text {0} record version {1} is unsupported.
PCDH events
Problem description
{0} - The CDR, SDR, VoiceXML, or CCXML record.
{1} - The version number that was returned by the CDH web service on the MPP.
The Avaya Aura Experience Portal versions on the EPM and the MPP did not match. The
EPM was upgraded to a specific version, but the MPP was not upgraded.
Proposed Solution
Procedure
Verify that the MPP has been upgraded to a version that matches the version that is
installed on the EPM.
PCDH_00018
Event text Could not download report data from CDH web service.
MPP {0} may require upgrading.
Problem description
Avaya Aura Experience Portal could not download report data from the CDH web service.
The specified MPP might require upgrading.
Proposed Solution
Procedure
Verify that the MPP has been upgraded to a version that matches the version that is
installed on the EPM.
PCDH_00019
PCDH_00019
Event text Report data corruption detected on MPP mppname,

skipping records.
Trigger component CDHScheduler issue
Problem description
Data corruption was detected while downloading report data from the specified MPP. The data
has been skipped.
Proposed Solution
About this task
Verify that the display language is set to English for all switch stations used by the Avaya Aura
Experience Portal system.
Contact Avaya Technical Support if the problem occurs again.
PCDH_00020
Event text Transcript transfer procedure complete {0}
Problem description
{0} - The date that the transcription was generated, and the session ID for the transciption.
The transcription was generated with the specified session ID on the date that was specified
in the event message.
PCDH events
Proposed Solution
About this task
PCDH_00021
Event text Utterances transfer procedure complete {0}
Problem description
{0} - getUtterance. This is the method that was used to log the information event.
The utterance transfer was completed using the getUtterance method.
Proposed Solution
About this task
PCDH_00022
Event text Transcript configure error {0}
Problem description
{0} - Can not get URL by Host Name and the name of the MPP.
PCDH_00023
The transcription client could not convert the name of the MPP into a valid URL.
Proposed Solution
About this task
PCDH_00023
Event text No Transcript service error {0}
Problem description
The transcript web service on the MPP failed due to one of the following:
Could not access the transcript web service to get the transcription file (in XML format).
Could not access the transcript web serve to get the utterance file (in wave format).
Could not find the utterance file (in wave format).
Proposed Solution
About this task
PCDH_00024
Event text Transcript file not found error {0}
PCDH events
Problem description
The session transcription or utterance file might not exist due to one of the following:
The transcription or utterance file did not exist.
Multiple attachments of transcriptions.
The file with a specific session ID did not exist.
Multiple attachments of utterance.
Proposed Solution
About this task
PCDH_00025
Event text Error locating Transcript web service {0}
Problem description
{0} - TranscriptClient. This is the name of the class that was used to locate the transcript web
service.
The TranscriptClient could not locate the transcript web service on the MPP.
Proposed Solution
About this task
PCDH_00026
PCDH_00026
Event text Error to set access privilege {0}
Problem description
{0} - The directory on the EPM that is used to save the trancription XML file.
The TranscriptClient could not access the EPM directory for saving the transcription XML file
that was retrieved from the MPP.
Proposed Solution
About this task
PCDH_00028
Event text Scheduled report output has been generated.

Exception occurred while sending email for
scheduled report {name}
Associate alarm name QCDH_00028
Trigger component Scheduled report
Problem description
{name} Name of the scheduled report.
The e-mail notification for the specified scheduled report could not be sent.
PCDH events
The error details from the SMPT server are listed in the event.
Proposed Solution
About this task
The details of the error generated by the SMTP server are listed in the event.
Procedure
1. Check the settings configured under EPM Servers > Email Server Settings.
2. Ensure that a valid network connection is available to the SMTP server from the
EPM.
PCDH_00029
Event text Exception occurred while creating RSS feed for

scheduled report {0}
Associate alarm name None
Trigger component Triggered by CDH scheduler when creating or update the RSS feed
xml file.
Problem description
{0} - Provides the name of the scheduled report.
An error has occurred while creating or updating the RSS feed notification for the specified
report.
Detailed exception stack trace will follow the error text.
Proposed Solution
About this task
Verify that sufficient disk space exists for the $CATALINA_HOME/webapps/VoicePortal/data/
feeds directory.
PCDH_00101
PCDH_00101
Event text Could not open {0}, the file may not exist.
Problem description
{0} - The record file name.
Avaya Aura Experience Portal could not open the CDR, SDR, or ADR record file.
Proposed Solution
About this task
PCDH_00102
Event text Failed to close file {0}.
Problem description
{0} - The record file name.
Avaya Aura Experience Portal could not close the CDR, SDR, or ADR record file.
PCDH events
Proposed Solution
About this task
PCDH_00103
Event text Invalid start date {0}.
Problem description
{0} - The invalid start date.
The requested start date is invalid.
Proposed Solution
About this task
PCDH_00104
Event text Start date {0} > current Date {1}. Retried {2} times
and failed.
PCDH_00105
Problem description
{0} - The invalid start date.
{1} - The current date.
{2} - The number of retries.
The requested start date is bigger than the current date. The requested start date was either
invalid or the GMT time change has caused a glitch during the one-minute download. For
example, 5:00 p.m. PDT is equivalent to 00:00 GMT for the next day. This error event is logged
when web services failed to process the request after retrying the query up to three times.
The CDH client will resend the request.
Proposed Solution
About this task
PCDH_00105
Event text Insufficient memory available. Exit!.
Problem description
Some processes might be running out of memory. There was insufficient memory available to
allocate for buffer.
Proposed Solution
About this task
Set trap in the CDH web service.
PCDH events
PCDH_00106
Event text Reach buffer limit {0}. buffer allocated {1}, record
size {2}, total records {3}
Problem description
{0} - The maximum buffer that was being allocated.
{1} - The current buffer that was being allocated.
{2} - The current record number.
{3} - The total record number.
The buffers are queuing up to the limit possibly due to busy network traffic.
Proposed Solution
About this task
Set trap in the CDH web service.
PCDH_00107
Event text File I/O Exception for {0}.
Problem description
{0} - The file name.
PCDH_00108
The file listed in the event message was unreadable. This could be caused by corrupted data
or a bad hard drive.
Proposed Solution
About this task
Remove this record and generate a new report.
PCDH_00108
Event text Failed to set directory '{0}'.
Problem description
{0} - The name of the directory.
For internal use only. The CDH web service cannot create a directory to save the record file.
Proposed Solution
About this task
PCDH_00109
Event text Failed to change path '{0}'.
PCDH events
Problem description
{0} - The name of the path.
For internal use only. The CDH web service cannot switch to the specified path to retrieve the
file. This error could happen when the access privilege for the path is manually changed.
Proposed Solution
About this task
1. Verify that the specified path exists.
2. Verify that the access privilege for the path is correct.
PCDH_00110
Event text Scheduled report output has been generated.

Report Name: {0}, Total Records: {1}
Associate alarm details Name: QCDH_00110

SNMP Trap ID: 17902

No alarm is generated by default. However, the administrator can
generate a minor alarm using the Alarm Settings page.
Trigger component Scheduled report
Problem description
{0} - Name of the scheduled report
{1}- Total number of records
The specified scheduled report has completed. When the schedule was created, the Generate
Event notification option was chosen.
Proposed Solution
About this task
Chapter 11: PCXI events
PCXI_00001
Event name PCXI_00001
Event text IPC connection to SessionManager failed at function:

{0} with error code: {1}
Trigger component MPP CCXML process
Problem description
{0} - Failed function type, such as Send Message
{1} - Error code.
A call into the MPP interprocess communication library failed.
Proposed Solution
About this task
This event might or might not indicate a problem. An error event indicates some important
functions failed. For example, a send message failed. A warning event might occur during
normal operation, do not take immediate action. For example, failures might occur during an
attempt to reconnect to the SessionManager after a restart. The CCXML will log a warning
event. The CCXML interpreter waits a few seconds, and then tries to reconnect to the
SessionManager.
Procedure
If this is a warning event, do not take immediate action. If this is an error event and the
problem persists:
a) Stop and restart the MPP from the EPM.
b) If the above action does not correct the problem, reboot the MPP server.
PCXI events
PCXI_00002
Event text Invalid parameter: {0} sent to function: {1} with

value: {2}, defaulting to {3}
Problem description
This event indicated an internal process error.
{0} - The invalid parameter.
{1} - Failed function type, such as 'send message'.
{2} - Value of the parameter listed in {0}.
{3} - Default value of the parameter.
The MPP received an invalid parameter on a function call.
Proposed Solution
Procedure
1. Stop and restart the MPP from the EPM.

Note:
Before contacting Avaya Technical Support, reproduce the problem by setting the
CCXML tracing to Finest.
PCXI_00003
PCXI_00004
Event text No IPC connection, function: {0} failed.
Problem description
The interprocess communication connection failed, or a connection to the SessionManager
could not be established.
Proposed Solution
Procedure

Note:
PCXI_00004
Event text Caught unknown exception in function {0} calling

function {1}
Event level Error or Fatal event. No alarm is generated.
Problem description
{0} - The function that caught an exception.
{1} - The function that was requested.
If the function that caught the unknown exception was Main, this event is a fatal error because
catastrophic problems happened and the cause was indeterminate.
PCXI events
If the function that caught the unknown exception was in SessionRouter, an incoming or
outgoing message could not be properly handled. This problem could be caused by a
nonexistent session that a message referenced.
Proposed Solution
Procedure
1. Restart the MPP from the EPM if one of the following occurred:
The MPP is in a Failed state.
The MPP does not take calls.
This error event is reoccurring.
2. If the error event happened in Main, check the EPM for errors and warnings.
3. If tracing is enabled on the MPP for the CCXML, review the process log for CXI on
the MPP.
4. If the source of the problem cannot be determined, collect all the MPP logs and
contact Avaya Technical Support.
Note:
Before contacting Avaya Technical Support, try to reproduce the problem by
setting the CCXML tracing to Finest.
PCXI_00005
Event text Out of memory! Allocation failed for size: {2} of

type: {1} in function: {0}
Problem description
{2} - Size of the memory.
{1} - Type of memory allocated.
{0} - The function that encountered out of memory.
PCXI_00006
The MPP could not allocate memory.
Proposed Solution
Procedure
1. Check the MPP Resource Status on the EPM.

2. Examine system resource usage by running the Linux top command on the
MPP.
3. Restart the MPP by using the EPM interface.
4. If the problem persists, restart the MPP server.
PCXI_00006
Event text Error from CXI engine! Code: {0} Description: {1}
Problem description
{0} - Error code.
{1} - Description of the error message.
The third-party CCXML interpreter encountered an error.
Note:
Experience Portal uses the OktopousTM ccXML Interpreter. The CCXML URL field is not
applicable for AMS.
Proposed Solution
Procedure
PCXI events
2. If the problem persists, reboot the MPP.

Note:
setting the CCXML tracing to Finest.
PCXI_00007
Event text Error connecting to IPC channel {0}! Code: {1}
Problem description
{0} - The interprocess communication channel that encountered an error.
{1} - Error code.
The CCXML interpreter could not connect to the SessionManager through the interprocess
communication library.
Note:
applicable for AMS.
Proposed Solution
Procedure

PCXI_00008
Note:
setting the CCXML and SessionManager tracing to Finest.
PCXI_00008
Event text Error sending Ready message to SessionManager with

code: {0}
Problem description
{0} - Error code.
The CCXML interpreter could not send a Ready message to the SessionManager after it has
successfully established the interprocess communication connection.
Note:
applicable for AMS.
Proposed Solution
Procedure
1. Verify that the SessionManager status is Running by using one of the following
methods:
Go to the MPP Service Menu.
Type the command stat.php on the MPP.
PCXI events
PCXI_00009
Event text Empty log slot! Logging session {0} to the global
slot.
Problem description
{0} - Number of the logging session.
The SessionManager sent an empty or invalid log slot name to the CCXML interpreter. The
empty or invalid session was logged to the global slot.
Note:
applicable for AMS.
Proposed Solution
Procedure
1. Review the errors or the trace log entries in the SessionManager.

Note:
PCXI_00010
PCXI_00011
Event text Non-existent session: {0} Throwing away message of

type: {1}.
Problem description
{0} - Session number.
{1} - Message type.
A message was received for a session that does not exist. This problem could have been
caused by the following reasons:
Incoming messages still in queue when a session was terminating.
The SessionManager was unaware of a session because the Avaya Aura Experience
Portal system crashed.
Proposed Solution
Procedure
1. Review the log report to identify when this event happened during a session.
If the warning event occurred at the end of a session, the problem could be
benign.
2. If the warning event occurred during a session, stop and restart the MPP from the
EPM.
3. If the problem persists, locate the file $AVAYA_MPP_HOME/Web/default.ccxml
to ensure that it has not been modified or replaced.
PCXI_00011
Event text Failed to route event {0} to a session.
PCXI events
Problem description
{0} - The event that could not be routed to a session.
An event was sent to the CCXML channel that did not map to a session. This could have
occurred when the event was placed in queue before the session was deleted and being read
off after the session was deleted.
Proposed Solution
Procedure

2. Ensure that the file $AVAYA_MPP_HOME/bin/liboktopous.so is installed on
the MPP.
Note:
PCXI_00012
Event text Received invalid message in function: {0} of type:

{1}
Problem description
{0} - The function type.
{1} - Message type, such as Send Message.
This error event occurred when there was a corruption of memory or when the server was
operating in the Degraded state.
PCXI_00013
Proposed Solution
Procedure
1. Verify that the system memory and storage resources are functioning at optimal
level.
3. If restarting the MPP does not resolve the problem, reboot the MPP server.
Note:
PCXI_00013
Event text IPC connection failed. Max number of attempts

reached: {0}.
Problem description
{0} - Maximum number of attempts to establish the interprocess communication connection.
The CCXML process could not establish an interprocess communication connection with the
SessionManager after the maximum allowed retries indicated in the error event.
Proposed Solution
Procedure
PCXI events
2. If restarting the MPP does not resolve the problem, reboot the MPP.
PCXI_00014
Event text IPC connection aborted - application shutting down.
Problem description
The CCXML application stopped when it tried to establish a connection to the
SessionManager.
Proposed Solution
About this task
PCXI_00015
Event text Attempt to use IPC after shutdown initiated.
Problem description
The SystemManager requested to stop the CCXML application when the application tried to
connect to the SessionManager before the application stopped.
PCXI_00016
Proposed Solution
About this task
If this event occurred during a shutdown of the process, no action is required.
Procedure
If this event occurred at other times, restart the CCXML process, and enable trace
logging.
PCXI_00016
Event text CCXML page error in event '{0}': Invalid arg '{1}'.
Problem description
{0} - Description of the event.
{1} - Provides information about the invalid argument.
Either the underlying CCXML browser or the CCXML page encountered a problem. The
CCXML received an invalid argument.
Proposed Solution
Procedure
Ensure that the following two files have not been modified or replaced or that they do
not exist in another directory on the MPP:
$AVAYA_MPP_HOME/Web/default.ccxml
$AVAYA_MPP_HOME/bin/liboktopous.so
PCXI events
PCXI_00017
Event text Handle already exists! Container: {0} ID: {1}.
Problem description
{0} - New internal object.
{1} - Identification of the object that is in the container.
The system encountered a problem when placing a new internal object in the container. The
new object ID conflicted with an existing object ID that was already in the container.
Proposed Solution
Procedure
Restart the CCXML process.
PCXI_00018
Event text Process caught fatal signal: {0}! Attempting clean

shutdown.
Problem description
{0} - Provides information for the fatal signal.
PCXI_00019
The CCXML application received a SIGINT or SIGTERM.
Proposed Solution
About this task
The SystemManager process automatically restarts.
Procedure
Note:
Management tracing to Finest.
PCXI_00019
Event text Setting trace level to: {0}
Problem description
{0} - The trace level that is being set.
There was a change in the debug logging level.
Proposed Solution
About this task
PCXI events
PCXI_00020
Event text Unsupported tag encountered: {0} - this

functionality is not supported by the platform.
Problem description
{0} - The name of the tag.
Avaya Aura Experience Portal encountered a CCXML tag that is not supported by the
platform.
Proposed Solution
About this task
Rewrite the CCXML applications to ensure that it uses only tags that are supported by the
platform.
PCXI_00021
Event text CCXML Interpreter failed to load uri: {0} with error
code: {1}
Problem description
{0} - The URI.
A CCXML URI cannot be loaded. The SessionManager will handle the error.
PCXI_00022
Note:
applicable for AMS.
Proposed Solution
About this task
Verify the following:
The URI has the correct format.
The application server is running properly and is connected to the MPP.
For applications provided by customers, do the following:
Procedure
1. From the EPM, go to Applications, and then click Verify to ensure that the application
server is responding.
2. From the MPP Service Menu, go to Diagnostics to verify that the MPP can ping the
application server.
PCXI_00022
Event text CCXML Interpreter failed to initialize due to

invalid cache directory!
Problem description
The CCXML process uses the directory that is defined in the $AVAYA_CXI_CACHE
environment variable to store cached files. If the $AVAYA_CXI_CACHE environment variable
does not exist or is empty, the CCXML process uses the /tmp directory. The CCXML process
will generate this error event and then exit when both the $AVAYA_CXI_CACHE environment
variable and the /tmp directory are unavailable or invalid.
PCXI events
Proposed Solution
Procedure
1. On the MPP server, do the following:

a) Validate that the directory that is referenced in the $AVAYA_CXI_CACHE
environment variable exists.
b) Verify that the directory in the $AVAYA_CXI_CACHE environment variable has
the rwx permissions for both the linux user avayavp and the group
avayavpgroup.
c) Validate that the $AVAYA_CXI_CACHE environment variable is created in the
$AVAYA_MPP_HOME/config/mpp.sh file. The default value is $
{AVAYA_MPP_HOME}/CXI/cache.
2. Restart the MPP from the EPM.
Chapter 12: PEVTM events
PEVTM00001
Event name PEVTM00001
Event text Event manager is starting...
Trigger component
Problem description
The Event Manager is starting.
Proposed Solution
About this task
PEVTM00002
Event text Event manager has stopped.
Trigger component
Problem description
The Event Manager has stopped.
PEVTM events
Proposed Solution
About this task
PEVTM00003
Event text Trace level has been set to {0}.
Trigger component
Problem description
{0} - The new trace level.
The trace level for the Event Manager has been set to a new value.
Proposed Solution
About this task
PEVTM00004
Event text Invalid trace level.
Trigger component
PEVTM00005
Problem description
The trace level is invalid. The Event Manager cannot generate trace messages. This event
does not affect the proper functioning of the Event Manager or the MPP.
Proposed Solution
Procedure
1. Use the command xml.php to validate the parameter mpp.trace.eventmgr is set to

one of the following: off, fine, finer, or finest.
2. Restart the MPP
3. Reboot the MPP.
PEVTM00005
Event text Keep alive time has been set to {0}.
Trigger component
Problem description
{0} - The new keep alive time.
The keep alive time for the Event Manager has been set to a new value.
Proposed Solution
About this task
PEVTM events
PEVTM00006
Event text Invalid keep alive time.
Trigger component
Problem description
The keep alive time is invalid. It will be set to 30 seconds as the default.
Proposed Solution
Procedure
1. Restart the MPP.

2. Reboot the MPP.
PEVTM00007
Event text Could not lock the stop mutex. Exiting...
Trigger component
Problem description
The Event Manager cannot function properly and must exit because it encountered an internal
error.
PEVTM00008
Proposed Solution
Procedure
1. Restart the MPP.

2. Reboot the MPP.
PEVTM00008
Event text Could not send the process status. Process status is
{0}. Return code is {1}.
Trigger component
Problem description
{0} - The status of the process.
{1} - The returned error code.
Avaya Aura Experience Portal could not sent the status of the Event Manager to the MPP
System Manager.
Proposed Solution
About this task
No action is required if you receive this event when the MPP starts up because the
communication between the Event Manager and the MPP System Manager might not have
been established yet.
Do the following if you receive this event when the MPP is running:
Procedure
1. Verify that the MPP System Manager is running.

2. Restart the MPP.
PEVTM events
3. Reboot the MPP.
PEVTM00009
Event text Could not get message channel to process {0}. Return
code is {1}. Cannot receive events from {0} to send
to the log server.
Trigger component
Problem description
{0} - The name of the process.
A communication channel could not be established between the Event Manager and the MPP
process that was specified in the event message. The events generated by the specified
process cannot be sent to the EPM.
Proposed Solution
Procedure
1. Restart the MPP.

2. Reboot the MPP.
PEVTM00010
Event text Could not register message handler for messages sent
by process {0}. Return code is {1}. Cannot receive
events from {0} to send to the log server.
PEVTM00011
Trigger component
Problem description
Proposed Solution
Procedure
1. Restart the MPP.

2. Reboot the MPP.
PEVTM00011
Event text Could not create communication channels to any

process. Cannot receive events from them to send to
the log server. Exiting...
Trigger component
Problem description
process could not be sent to the EPM. The Event Manager cannot function properly.
PEVTM events
Proposed Solution
Procedure
1. Verify that the MPP is running.

2. Restart the MPP.
3. Reboot the MPP.
PEVTM00012
Event text Could not create a thread to send events to the log
server. Cannot send events to the log server.
Exiting...
Trigger component
Problem description
The Event Manager encountered an internal error and could not create t thread to send events
to the EPM. The events generated by the specified process cannot be sent to the EPM. The
Event Manager cannot function properly.
Proposed Solution
Procedure
1. Restart the MPP.

2. Reboot the MPP.
PEVTM00013
PEVTM00013
Event text Could not stop the threads that received messages
from the following processes: {0}.
Trigger component
Problem description
{0} - The names of the processes.
The EVent Manager could not stop the threads that received events from the specified
processes that were listed in the event message. The Event Manager will eventually stop.
Proposed Solution
About this task
PEVTM00014
Event text Could not stop the threads that sent events to the
log server.
Trigger component
Problem description
The EVent Manager could not stop the threads that send events to the EPM. The Event
Manager will eventually stop.
PEVTM events
Proposed Solution
About this task
PEVTM00015
Event text Received the SIGTERM signal. Stopping...
Trigger component
Problem description
The Event Manager is stopping.
Proposed Solution
About this task
PEVTM00016
Event text Could not set up to accept connections from process

{0}. Return code is {1}. Cannot receive events from
{0} to send to the log server.
Trigger component
Problem description
PEVTM00016

Proposed Solution
Procedure
1. Restart the MPP.

2. Reboot the MPP.
PEVTM events
Chapter 13: PLICE events
PLICE00001
Event name PLICE00001
Event text Unable to contact WebLM server {0}.
Associate alarm details Name: QLICE00001

SNMP Trap ID: 17001

Trigger component Avaya Aura Experience Portal licensing issues
Problem description
The EPM licensing thread could not communicate with the license server the first time. For
subsequent failures, Information event PLICE00006 will be generated until the licensing thread
can communicate with the license server.
Reasons for the failure:
The URL of the license server was not configured correctly.
The Avaya Aura Experience Portal license was not installed on the license server.
If the license server was installed on a separate server, the Tomcat server on the license
server might not be running properly or there were network connection problems.
Proposed Solution
Procedure
1. Verify that the URL of the license server is correct.
PLICE events
2. Verify that the Avaya Aura Experience Portal license is installed on the license
server:
If the license server is installed on a separate server, verify that the license
server is running properly.
If the license server is installed on a separate server, verify that network
connection between Avaya Aura Experience Portal and the license server
has been established.
PLICE00002
Event text License grace period has exceeded.

SNMP Trap ID: 17002

Problem description
The EPM licensing thread could not communicate with the license server, and the license grace
period has been exceeded. For subsequent failures, Information event PLICE00007 will be
generated until the licensing thread can communicate with the license server.
Proposed Solution
Procedure
Verify that the Avaya Aura Experience Portal license is still available on the license
server:
if the license server is installed on a separate server, verify that the license server
is running properly.
PLICE00003
if the license server is installed on a separate server, verify that network

connection between Avaya Aura Experience Portal and the license server has
been established.
PLICE00003
Event text License has expired on {0, date, medium}.

SNMP Trap ID: 17003

Problem description
{0} - The date when the license expired.
The expiration date specified by the Avaya Aura Experience Portal license has expired. For
subsequent failures, Information event PLICE00008 will be generated until the licensing
thread can communicate with the license server.
Proposed Solution
Procedure
1. Verify that the Avaya Aura Experience Portal license has expired.
2. Renew the Avaya Aura Experience Portal license with Avaya.
3. Contact Avaya Technical Support if the above actions do not fix the problem.
PLICE events
PLICE00004
Event text License information is not available in the

database.
Associate alarm Name: QLICE00004

details
SNMP Trap ID: 17004

Problem description
License information could not be found in the Avaya Aura Experience Portal database
because the database was corrupted.
Proposed Solution
Procedure
Ensure that the database is running properly:

If the database is not running properly, restart the database, and then restart the
EPM.
If data is corrupted in the database, restore the database from a backup.
PLICE00005
Event text SQL exception occurred.
PLICE00006

SNMP Trap ID: 17005

Problem description
The event message contains exception details.
The system encountered problems when retrieving or updating licensing information in the
database.
Proposed Solution
Procedure
Ensure that the database is running properly:

If the database is not running properly, restart the database, and then restart the
EPM.
If data is corrupted in the database, restore the database from a backup.
PLICE00006
Event text Unable to contact WebLM server {0}.
Problem description
{0} - The name of the WebLM server.
The EPM licensing thread could not communicate with the license server.
PLICE events
Proposed Solution
About this task
PLICE00007
Event text License grace period has exceeded.
Problem description
The license grace period has been exceeded.
Proposed Solution
About this task
PLICE00008
Event text License has expired on {0, date, medium}.
Problem description
{0} - The date when the license expired.
The expiration date specified by the Avaya Aura Experience Portal license has expired.
PLICE00009
Proposed Solution
About this task
PLICE00009
Event text Able to communicate with WebLM server {0}.
Problem description
The EPM licensing thread reestablished communication with the license server.
Proposed Solution
About this task
PLICE00010
Event text Acquired new licenses from WebLM server {0}.
Problem description
PLICE events
The EPM licensing thread can now acquire new licenses from the license server.
Proposed Solution
About this task
PLICE00011
Event text Licensing is in startup grace period which will

expire on {0, date, medium} at {1, time, long}.
Check the license server for license.
Associate alarm QLICE00011

name
Alarm Codes page.
Problem description
Proposed Solution
About this task
PLICE00012
PLICE00012
Event text Licensing is in startup grace period which will

expire on {0, date, medium} at {1, time, long}. Check
the license server for license.
Problem description
Proposed Solution
About this task
PLICE00013
Event text Avaya Aura Experience Portal license has not been installed on the
WebLM server {0}.
Associate alarm name QLICE00013

Alarm Codes page.
PLICE events
Problem description
The Avaya Aura Experience Portal license was not installed on the specified WebLM
server.
Proposed Solution
About this task
PLICE00014
Event text Avaya Aura Experience Portal license has not been
installed on the WebLM server {0}.
Problem description
The Avaya Aura Experience Portal license was not installed on the specified WebLM
server.
Proposed Solution
About this task
PLICE00015
PLICE00016
Event text Avaya Aura Experience Portal license is now

available on the WebLM server {0}.
Problem description
The Avaya Aura Experience Portal license is now available on the specified WebLM server.
Proposed Solution
About this task
PLICE00016
Event text Licensing is operating in grace period which ends

on {0, date, medium} at {1, time, long}.

Alarm Codes page.
Problem description
{0} - The expiration date for the grace period.
The Avaya Aura Experience Portal license is operating in grace period with the specified
expiration date.
PLICE events
Proposed Solution
About this task
Refer to the associated licensing alarms for corrective action.
PLICE00017
Event text Licensing is operating in grace period which ends on

{0, date, medium} at {1, time, long}.
Problem description
{0} - The expiration date for the grace period.
The Avaya Aura Experience Portal license is operating in grace period with the specified
expiration date.
Proposed Solution
About this task
PLICE00018
Event text The version of the Avaya Aura Experience Portal

license is old. Update the license to a newer
version.

details
PLICE00019
SNMP Trap ID: 17903

Problem description
The Avaya Aura Experience Portal license version is old. You must get an updated license
from Avaya.
Proposed Solution
About this task
Contact Avaya Technical Support to get a new or updated Avaya Aura Experience Portal
license from Avaya.
PLICE00019

license is old. Update the license to a newer
version.
Problem description
The Avaya Aura Experience Portal license is old. You must get an update license from
Avaya.
Proposed Solution
About this task
Get a new or update Avaya Aura Experience Portal license from Avaya.
PLICE events
PLICE00020

license is supported.
Problem description
The Avaya Aura Experience Portal license is supported.
Proposed Solution
About this task
PLICE00021
Event text License is going to expire on {0, date, medium}

{1, time, long}.
Associate alarm name Name: QLICE00021

SNMP Trap ID: 17902

Alarm Codes page.
Trigger component Avaya Aura Experience Portal licensing
PLICE00024
Problem description
{0} - The date when the license will expire.
{1} - The time when the license will expire.
Avaya Aura Experience Portal license is going to expire.
Proposed Solution
Procedure
1. Verify that the Avaya Aura Experience Portal license is going to expire.
2. Renew the Avaya Aura Experience Portal license with Avaya before the license
expires.
3. If you cannot correct the problem, contact Avaya Technical Support.
PLICE00024
Event text Unable to acquire {0} licenses for {1} feature as

license server has only {2} licenses available.
Trigger component Avaya Aura Experience Portal licensing
Problem description
{0} - The number of licenses requested from the license server.
{1} - The name of the license feature.
{2} - The number of licenses available on the license server
The number of licenses available for the specified licensed feature is less than the minimum
number of licenses specified on the licensing web page for the feature mentioned in the
event.
PLICE events
Proposed Solution
Procedure
1. Verify that the license server has sufficient number of licenses available for the
system.
2. Either reduce the number of licenses requested for the feature on the licensing web
page or purchase more licenses from Avaya for the feature.
PLICE00025
Event text {4} license has expired on {0, date, medium} {1,
time, long}. Grace period for this license will end
on {2, date, medium} at {3, time, long}.

details
SNMP Trap ID: 17903

Critical alarm is generated by default. You can change the severity for
Alarm Codes page.
Problem description
{0} - The date when the license will expire.
{2} - The date when the grace period will end.
{3} - The time when the grace period will end.
{4} - Name of the product whose license is going to expire.
License is going to expire for the product mentioned in the event text and the system is
operating in the grace period for this license.
PLICE00025
Proposed Solution
Procedure
1. Verify the license No action required.

2. Renew the product license with Avaya before the license expires.
PLICE events
Chapter 14: PLOG events
PLOG_00001
Event name PLOG_00001
Event text Could not send the event {0} to the event manager.
Management library returned {1}.
Trigger component Event manager
Problem description
{0} - The event code.
The event could not be sent to the Event Manager. The Event Manager might not be running.
The event is not sent to the EPM. This event is logged in one of the MPP process log files.
Proposed Solution
Procedure
1. Verify that the MPP Event Manager is running.

2. Use the stat.php command to view status.
3. Review the process log in the $AVAYA_MPP_HOME/logs/process/EventMgr
directory.
4. Reboot the MPP.
PLOG events
PLOG_00002
Event name PLOGR00002
Event text Could not send the event {0} to the log server. Event
client returned: {1}
Problem description
{0} - The event code.
The MPP could not sent the event to the EPM. This event is logged in one of the Event Manager
log files.
Proposed Solution
Procedure
1. Verify that the logging web service is functioning properly on the EPM.
2. Validate the following parameters on the MPP by using the xml.php command:
mpp.log.netaddress (IP address of the EPM)
mpp.log.logserviceport (The default is 80.)
mpp.log.servicename (NetworkLogServer)
3. Verify that you can ping the EPM from the MPP.
4. Restart the MPP.
5. Reboot the MPP.
6. Restart the EPM.
PLOG_00003
PLOG_00003
Event text Could not send the time when sending an event to the
log server failed to the system manager. The time is
{0}. Management library returned {1}.
Problem description
{0} - The time for the event.
The MPP could not send an event to the EPM. The time of the event was not sent to the System
Manager. This event is logged in one of the Event Manager log files.
Proposed Solution
Procedure
4. Restart the MPP.
5. Reboot the MPP.
6. Restart the EPM.
PLOG events
PLOG_00004
Event text Cannot add the event to the event sender threads
queue because the queue is full. The event will not
be sent to the log server.
Problem description
The Event Manager queue that contains events to be sent to the EPM is full. This is typically
a result of too many events were sent to the EPM or the logging web service on the EPM is
having problems. This event is logged in one of the Event Manager log files. This event is not
sent to the EPM.
Proposed Solution
Procedure
1. On the EPM, verify that the Event Level Threshold to Send to EPM field on the
MPP Settings page is set to Error.
Do not use Info or Warning on a production system or on a system that is running
a heavy call load.
2. Review and resolve the cause for the Error events that were being reported on the
MPP.
6. Restart the MPP.
7. Reboot the MPP.
8. Restart the EPM.
PLOG_00005
Note:
If this event happens too often, set the level of event priority to Error.
PLOG_00005
Event text Events can be added to the event sender threads

queue because the queues low watermark has been
reached. The events will be sent to the log server.
Problem description
The Event Manager queue that contains events to be sent to the EPM was full, but some events
in the queue were sent to the EPM so that events can be put into the queue again. This event
is logged in one of the Event Manager log files. This event is not sent to the EPM.
Proposed Solution
About this task
PLOG_00006
Event text Cannot add the log message to the sender threads
queue because the queue is full. The message will not
be sent to the file.
PLOG events
Problem description
The queue that contains log messages to be sent to the log file is full. This is typically a result
of too many log messages being generated. This event is logged in one of the process log
files. This event is not sent to the EPM.
Proposed Solution
Procedure
1. Set the trace level for MPP subsystems to Off if you are not troubleshooting.
2. Restart the MPP.
3. Reboot the MPP.
PLOG_00007
Event text Log messages can be added to the sender threads

queue because the queues low watermark has been
reached. The messages will be sent to the file.
Trigger component
Problem description
The queue that contains log messages to be sent to the log file was full, but some messages
in the queue were sent to the file so that messages can be put into the queue again. This event
is logged in one of the process log files. This event is not sent to the EPM.
Proposed Solution
About this task
Chapter 15: PLOGR events
PLOGR00001
Event text Could not send log message to process that sends log
messages to log server. MppMgtLib returned {0}.
Problem description
{0} - Error message.
The MPP could not communicate with the System Manager. The System Manager might not
be running. The MPP logged this error event in the log files. This event was not sent to the
Experience Portal Manager.
Proposed Solution
Procedure
1. Restart the MPP daemon.

2. If the problem persists, restart the MPP server.
Note:
PLOGR events
PLOGR00002
Event text Could not send log message to log server. {0}.
Problem description
The MPP could not sent the log message to the logging Web service on the EPM. The MPP
logged this error event in the log files. This event was not sent to the EPM.
Proposed Solution
Procedure
1. Verify that the mpp daemon is running on the MPP.

2. Verify that the logging Web service is functioning properly on the EPM.
3. Validate the following parameters on the MPP by using the command xml.php:
mpp.log.logserviceport (The default is 8080)
5. Restart the MPP.
6. Restart the EPM.
PLOGR00003
PLOGR00004
Event text Could not send log message to log server because
there is no configuration information.
Problem description
This error event could be generated by one of the following reasons:
The logging client on the MPP could not send a log message to the network logging
service on the EPM because there was no logging-related configuration.
The MPP is in the No Configuration state because the EPM has not sent the configuration
to the MPP.
The MPP logged this warning event in the log files. This event was not sent to the EPM.
Proposed Solution
About this task
Follow the steps below to correct the problem:
Procedure
1. Validate the following parameters on the MPP by using the command xml.php:
mpp.log.logserviceport (The default is 8080)
3. Restart the MPP.
4. Restart the EPM.
PLOGR00004
Event text Could not send log message to log server because
there is no appender.
PLOGR events
Problem description
The logging client on the MPP could not send a log message to the network logging service
on the EPM because there was no logging appender.
The MPP logged this error event in the log files. This event was not sent to the EPM.
Proposed Solution
Procedure
1. Restart the mpp daemon.

2. Restart the MPP server.
PLOGR10001
Event text Product ID is not configured.
Problem description
The system could not configure the product ID.
Proposed Solution
About this task
PLOGR10002
PLOGR10002
Event text Error retrieving product ID.
Problem description
The system encountered problems while retrieving the product ID.
Proposed Solution
About this task
PLOGR events
Chapter 16: PLSTNR events
PLSTNR0001
Event name PLSTNR0001
Event text notifyAlarm: Email Notifications are disabled.

Trigger component Avaya Aura Experience Portal Alarm Listeners.
Problem description
E-mail Notifications are disabled for the current alarm.
Proposed Solution
Procedure
None. This is an informational message.
PLSTNR0002
Event text notifyAlarm: Email, first {0} alarm notification

only enabled.

PLSTNR events
Problem description
{0} - The alarm severity. The configuration for the email notification is set so that only the first
alarm at this severity will be sent.
Proposed Solution
Procedure
PLSTNR0003
Event text notifyAlarm: Email, {0} Critical notification

already sent for product id {1} not sending another
notification.

Problem description
{0} - Notification setting (First/All).
{1} - The product id. The configuration for the e-mail notification is set so that the current Critical
alarm will not cause an Email to be sent.
Proposed Solution
Procedure
PLSTNR0004
PLSTNR0004
Event text notifyAlarm: Email sending, {0} Critical

notification for product id {1}.

Problem description
{1} - The product id. The configuration for the email notification is set so that the current Critical
alarm will cause an Email to be sent.
Proposed Solution
Procedure
PLSTNR0005
Event text notifyAlarm: Email sending, {0} Major notification

for product id {1}.

Problem description
{1} - The product id. The configuration for the email notification is set so that the current Major
PLSTNR events
Proposed Solution
Procedure
PLSTNR0006
Event text notifyAlarm: Email sending, {0} Minor notification

for product id {1}.

Problem description
{1} - The product id. The configuration for the email notification is set so that the current Minor
Proposed Solution
Procedure
PLSTNR0007
Event text notifyAlarm: Email, not the first {0} alarm for
product id {1} not sending notification.
PLSTNR0008

Problem description
{0} - The alarm severity.
{1} - The product id. The configuration for the e-mail notification is set so that the current alarm
will not cause an Email to be sent.
Proposed Solution
Procedure
PLSTNR0008
Event text notifyAlarm: Email sending, {0} {1} alarm for

product id {2}.

Problem description
{0} Notification setting (First/All).
{2} - The product id. for which the e-mail notification is being sent.
Proposed Solution
Procedure
PLSTNR events
PLSTNR0009
Event text notifyAlarm: AlarmException occurred in email

listener.

Problem description
An error occurred while attempting to process the alarm.
Proposed Solution
Procedure
PLSTNR0010
Event text notifyAlarm: Email, all {0} alarm notifications

enabled.

Problem description
{0 }- The alarm severity. Indicates that an e-mail notification of the specified severity is being
sent.
PLSTNR0011
Proposed Solution
Procedure
PLSTNR0011
Event text notifyAlarm: Email, unable to get Email Server

settings for {0} from the database

Problem description
{0 }- The email server configuration parameter. The configuration for the e-mail notification is
invalid or not set.
Proposed Solution
Procedure
Verify that the configuration for the e-mail notification is valid and set on the E-mail
Server Settings web page.
PLSTNR0012
Event text notifyAlarm: Exception occurred when sending an

email alarm notification
PLSTNR events
Associate alarm name QLSTNR0012
Event level Error event

Alarm Codes page.
.
Problem description
The Email notification could not be sent due to an exception.
Proposed Solution
Procedure
Verify that the configuration for the e-mail notification is valid and set on the Email
Server Settings web page.
PLSTNR0013
Event text notifyAlarm: Syslog, unable to get Syslog Server

settings from the database.

Problem description
The URL for the SysLog Server is not set.
PLSTNR0014
Proposed Solution
Procedure
Verify that the configuration for the SysLog Server is valid and set on the Alarm Codes
and Change Alarm Delivery Settings web page.
PLSTNR0014
Event text notifyAlarm: Syslog Notifications are disabled.

Problem description
SysLog Notifications are disabled for the current alarm.
Proposed Solution
Procedure
PLSTNR0015
Event text notifyAlarm: Syslog, first {0} alarm notification

only enabled.
PLSTNR events
Problem description
{0 }- The alarm severity. The configuration for the SysLog notification is set so that only the
first alarm at this severity will be sent.
Proposed Solution
Procedure
PLSTNR0016
Event text notifyAlarm: Syslog, {0} Critical notification

already sent for product id {1} not sending another
notification.

Problem description
{0 }- Notification setting (First/All).
{1} - The product id. The configuration for the SysLog notification is set so that the current
Critical alarm will not cause a notification to be sent.
Proposed Solution
Procedure
PLSTNR0017
PLSTNR0017
Event text notifyAlarm: Syslog sending, {0} Critical

notification for product id {1}.

Problem description
Critical alarm will cause a notification to be sent.
Proposed Solution
Procedure
PLSTNR0018
Event text notifyAlarm: Syslog sending, {0} Major notification

for product id {1}.

Problem description
Major alarm will cause a notification to be sent.
PLSTNR events
Proposed Solution
Procedure
PLSTNR0019
Event text notifyAlarm: Syslog sending, {0} Minor notification

for product id {1}.

Problem description
Minor alarm will cause a notification to be sent.
Proposed Solution
Procedure
PLSTNR0020
Event text notifyAlarm: Syslog, not the first {0} alarm for
product id {1} not sending notification.
PLSTNR0021

Problem description
{0 }- The alarm severity.
alarm will not cause a notification to be sent.
Proposed Solution
Procedure
PLSTNR0021
Event text notifyAlarm: Syslog sending, {0} {1} alarm for

product id {2}.

Problem description
{2} - The product id for which the SysLog notification is being sent.
Proposed Solution
Procedure
PLSTNR events
PLSTNR0022
Event text notifyAlarm: AlarmException occurred in syslog

alarm.

Problem description
Proposed Solution
Procedure
PLSTNR0023
Event text notifyAlarm: Syslog, all {0} alarm notifications

enabled.

Problem description
{0 }- The alarm severity. Indicates that a syslog notification of the specified severity is being
sent.
PLSTNR0024
Proposed Solution
Procedure
PLSTNR0024
Event text notifyAlarm: Exception occurred when sending an

syslog alarm notification to syslog server
Associate alarm name QLSTNR0024

Alarm Codes page.
.
Problem description
The SysLog notification could not be sent due to an exception.
Proposed Solution
Procedure
Verify that the configuration for the SysLog Server is valid and set on the Alarm Codes
and Change Alarm Delivery Settings web page.
PLSTNR events
Chapter 17: PMMGR events
PMMGR00006
Event name PMMGR00006
Event text MediaManager received fatal error from subsystem

{0}, resetting process.
Trigger component Media Manager process which includes EndPointMgr and VideoMgr
Problem description
{0} - The component, EndPointMgr or VideoMgr, reporting the fatal error.
This is a fatal error that can only be recovered by restarting the MPP.
Proposed Solution
Procedure
1. Restart the MPP.

2. If the above action does not correct the problem, contact Avaya Technical
Support.
PMMGR events
Chapter 18: PMMS events
PMMS_00001
Event name PMMS_00001
Event text Cannot create message object for {0} due to error
{1}.
Trigger component MPP Management server (MMS) Web service
Problem description
{0} - The interprocess communication object that could not be allocated.
{1} - Error code.
The MMS Web service could not allocate an interprocess communication object.
If the error code is 12, there was insufficient memory to perform the object allocation.
If the error code is any other number, there was an internal problem.
Proposed Solution
Procedure
Note:
PMMS events
PMMS_00002
Event text Cannot connect to {0} due to error {1}.
Problem description
{0} - The name of the process to which MMS Web service cannot connect.
{1} - Error code.
The MMS Web service could not connect to a process. The process was usually the System
Manager. The MMS Web service ignored all incoming commands from the EPM.
Proposed Solution
Procedure
Note:
PMMS_00003
Event text Failed to send command {0} to MPP System Manager due
to error {1}.
PMMS_00004
Problem description
{0} - The command sent.
{1} - Error code.
The MMS Web service could not connect to a process. The process was usually the System
Manager. The MMS Web service ignored all incoming commands from the EPM.
Proposed Solution
Procedure
Note:
PMMS_00004
Event text New command {0} received.
Problem description
{0} - The command that was being sent.
The MMS web service received an incoming command from the EPM.
Proposed Solution
About this task
PMMS events
Chapter 19: PMRCP events
PMRCP00001
Event name PMRCP00001
Event text Task {2} failed because {1} port is not available.
{0}
Trigger component MRCP provider that runs as part of the MPP SessionManager process
Problem description
{2} - Task that failed.
{1} - The name of the unavailable port.
The MRCP connection to the Automated Speech Recognition (ASR) or Text-to-Speech (TTS)
(TTS) server encountered low-level failure.
Proposed Solution
Procedure
3. Ensure that the network connection between the MPP and the ASR server is
established.
4. Verify that you can connect to the ASR server from the MPP.
5. On the ASR server, verify that you can ping the MRCP Network Address that was
configured for the MPP.
PMRCP events
PMRCP00002
Event text Task {2} failed because no {1} RTP port was found.
{0}
Problem description
{1} - The name of the port that was not found.
The MRCP connection to the ASR or TTS server encountered low-level failure.
Proposed Solution
Procedure
established.
PMRCP00003
PMRCP00004
Event text Task {2} failed because {1} port is busy. {0}
Problem description
{1} - The name of the port that was busy.
Proposed Solution
Procedure
established.
PMRCP00004
Event text Task {2} failed because {1} port is not active. {0}
Problem description
PMRCP events
{1} - The name of the port that was not active.

Proposed Solution
Procedure
established.
PMRCP00005
Event text No {2} callback is registered for {1}. {0}
Problem description
{2} - The name of the callback.
{1} - The name of the port.
PMRCP00006
Proposed Solution
Procedure
established.
PMRCP00006
Event text An unknown exception occurred during {1} task {2}.

{0}
Problem description
{1} - Description of the unknown exception.
Proposed Solution
Procedure
PMRCP events
established.
PMRCP00007
Event text Failed sending message {2} to {1} server - socket

error. {0}
Problem description
{0} - The name of the speech server as specified in the EPM.
{1} - Indicates whether the server is an ASR or TTS server.
{2} - The failed message.
Proposed Solution
Procedure
established.
PMRCP00008
PMRCP00008
Event text The connection to the server [{2}] has failed! {0}
Associate alarm Name: QMRCP00008

details
SNMP Trap ID: 17902

Alarm Codes page.
Trigger component MRCP provider that runs as part of the MPP SessionManager
process
Problem description
{0} - The MRCP session details.
The MRCP connection to the server failed.
Proposed Solution
About this task
If this event is followed by PMRCP00009, then Avaya Aura Experience Portal should be
operating properly. Otherwise, follow the steps below to correct the problem:
Procedure
1. Verify that the ASR or TTS server is running properly.

2. Verify that you can ping the ASR or TTS server from the MPP.
3. Verify that you can ping the MPP MRCP Network Address that was configured on
the EPM from the ASR or TTS server.
4. Restart the MPP.
PMRCP events
PMRCP00009
Event text Established connection to the server [{2}]. {0}
Problem description
{0} - The MRCP session details.
The MRCP connection between the MPP and the speech server has been reestablished.
Proposed Solution
About this task
PMRCP00010
Event text The following properties were ignored by the {1}

server: <{2}>. {0}
Problem description
{1} - Indicates whether the server is an ASR or TTS server.
{2} - The list of ignored properties.
PMRCP00010
The property values that were sent to the speech server has been ignored.
Proposed Solution
Procedure
Review the property list to determine whether the ignored property has any impact on
the Avaya Aura Experience Portal operation.
For example, you will get this Warning event if you have specified to use Nuance TTS
Voice Tom, but Tom is not installed on the speech server.
PMRCP events
Chapter 20: PMUG events
PMUG_00001
Event name PMUG_00001
Event text Managed upgrade has started, beginning with MPP:

{0}. See Software Upgrade web page for complete
list.

No alarm is generated.
Problem description
A managed upgrade process has started, beginning with the MPP mentioned. The Software
Upgrade web page contains a complete list of MPPs which will be upgraded.
Proposed Solution
Procedure
PMUG_00002
PMUG events
Event text Managed upgrade has completed. The last MPP

successfully upgraded was: {0}. Any remaining MPPs
failed or were cancelled. See Software Upgrade web
page for complete list.

Problem description
A managed upgrade process has completed, ending with the MPP mentioned. The Software
Upgrade web page contains a complete list of MPPs which upgraded successfully, failed to
upgrade, or were cancelled.
Proposed Solution
Procedure
PMUG_00003
Event text Upgrade failed for MPP {0} with error: "{1}".
Associate alarm details Name: QMUG_00003

SNMP Trap ID: 17902

PMUG_00004
Problem description
{1} - Error details.
An attempt to upgrade the MPP failed.
Proposed Solution
Procedure
Rectify the problem described in the error details and retry the upgrade.
PMUG_00004
Event text Managed upgrade cancellation has been requested.

Problem description
A cancellation request for the current managed upgrade process has been issued.
Proposed Solution
Procedure
PMUG events
PMUG_00005
Event text Managed upgrade recovery has started, beginning

with MPP: {0}. See Software Upgrade web page for
complete list.
Problem description
The recovery of a managed upgrade process has been started, beginning with the MPP
mentioned. A managed upgrade recovery typically occurs for MPP(s) currently in the upgrade
phase of a managed upgrade process when the EPM is restarted, rebooted, or recovers from
a failure.
Proposed Solution
Procedure
PMUG_00006
Event text Started download process for MPP {0}.

PMUG_00007
Problem description
The results of the last managed upgrade have been acknowledged by a system
administrator.
Proposed Solution
Procedure
PMUG_00007
Event text Started download process for MPP {0}.

Problem description
The download phase of a managed upgrade process for the MPP mentioned has started.
Proposed Solution
Procedure
PMUG events
PMUG_00008
Event text Finished download process for MPP {0}.

Problem description
The download phase of a managed upgrade process for the MPP mentioned is completed.
Proposed Solution
Procedure
PMUG_00009
Event text Started upgrade process for MPP {0}.

PMUG_00010
Problem description
The upgrade phase of a managed upgrade process for the MPP mentioned has been
started.
Proposed Solution
Procedure
PMUG_00010
Event text Finished upgrade process for MPP {0}.

Problem description
The upgrade phase of a managed upgrade process for the MPP mentioned has been
completed.
Proposed Solution
Procedure
PMUG events
Chapter 21: POMS events
POMS_00001
Event name POMS_00001
Event text MPP Polling Started
Trigger component Experience Portal Manager
Problem description
The EPM is initializing and starting to poll data from the Media Processing Platforms.
Proposed Solution
About this task
POMS_00002
Event text Exit MPP Polling
Problem description
The EPM is no longer polling data and is terminating.
POMS events
Proposed Solution
About this task
POMS_00003
Event text Sending {0} Start command
Problem description
{0} - The MPP that is being started.
The MPP starts to take calls.
Proposed Solution
About this task
POMS_00004
Event text Start command sent successfully to {0}
Problem description
{0} - The MPP that is being started
POMS_00005
The MPP accepted the command to start and is starting.
Proposed Solution
About this task
POMS_00005
Event text Failed sending Start command to {0} with error {1}
Problem description
The system could not send the Start command, and the MPP ignored the Start command
{0} - The MPP that is being started
{1} - Error returned by MPP or Web Services
Proposed Solution
Procedure
1. Verify that the MPP is communicating properly with the EPM.

2. Restart the MPP.
3. Execute the Start command again.
4. If the problem persists, restart the EPM.
5. Execute the Start command again.
POMS events
POMS_00006
Event text Polling {0} at {1} for heart beat
Event level Not used.
Problem description
Not used.
Proposed Solution
About this task
POMS_00007
Event text Got heartbeat from {0} ({1})
Problem description
Not used.
Proposed Solution
About this task
POMS_00008
POMS_00008
Event text Failed getting heartbeat from {0} with error {1}
Problem description
Not used.
Proposed Solution
About this task
POMS_00009
Event text Sending {0} Stop command with {1} second grace period
Problem description
The MPP received the command to stop taking calls and to clear the configuration.
{0} - The MPP that is being stopped.
{1} - The grace period.
POMS events
Proposed Solution
About this task
POMS_00010
Event text Stop command sent successfully to {0}
Problem description
The MPP received the Stop command and is in the process of stopping.
{0} - the MPP that is being stopped
Proposed Solution
About this task
POMS_00011
Event text Failed sending Stop command to {0}
Problem description
System could not send Stop command to MPP.
POMS_00012
The MPP ignored the Stop command.

{0} - The MPP that is being stopped.
Proposed Solution
Procedure

2. Manually reboot the MPP.
3. Execute the Stop command again.
5. Execute the Stop command again.
POMS_00012
Event text Sending {0} Halt command with {1} second grace period
Problem description
{0} - The MPP that is being halted.
{1} - The grace Period
The MPP received command to stop taking calls and to stop running Linux.
Proposed Solution
About this task
POMS events
POMS_00013
Event text Halt command sent successfully to {0}
Problem description
The MPP received the Halt command and is in the process of halting.
Proposed Solution
About this task
POMS_00014
Event text Failed sending Halt command to {0}
Problem description
The system could not send the Halt command to the MPP.
The MPP ignored the Halt command.
POMS_00015
Proposed Solution
Procedure

3. Execute the Halt command again.
5. Execute the Halt command again.
POMS_00015
Event text Sending {0} Reboot command with {1} second grace
period
Problem description
{0} - The MPP that is being rebooted.
{1} - The grace period
The MPP received the command to stop taking calls. The MPP restarts Linux. The MPP can
be in either the Stop state or Running state depending on the restart configuration.
Proposed Solution
About this task
POMS events
POMS_00016
Event text Reboot command sent successfully to {0}
Problem description
The MPP received the Reboot command and is in the process of rebooting.
Proposed Solution
About this task
POMS_00017
Event text Failed sending Reboot command to {0} with error {1}
Problem description
{1} - Error returned by the MPP or Web Services.
The system could not send the Reboot command.
The MPP ignored the Reboot command.
POMS_00018
Proposed Solution
Procedure

3. Execute the Reboot command again.
5. Execute the Reboot command again.
POMS_00018
Event text Sending {0} Add Stations
Problem description
{0} - The MPP that is receiving stations.
The MPP received the command to register new stations by using configurations that are set
in the configuration history.
Proposed Solution
About this task
POMS events
POMS_00019
Event text Add Stations sent successfully to {0}
Problem description
The MPP received command to register stations and is in the process of registering the
stations.
Proposed Solution
About this task
POMS_00020
Event text Failed sending Add Stations to {0} with error {1}
Problem description
{1} - Error returned by the MPP or Web Services.
The system could not send the Add Station command.
The MPP ignored the Add Station command.
POMS_00021
Proposed Solution
Procedure
1. Verify that the MPP is communicating properly with the EPM. The command
automatically starts again.
2. If the problem persists, restart the MPP.
POMS_00021
Event text Sending {0} Remove Stations with {1} second grace
period
Problem description
{0} - The MPP that is removing stations.
{1} - The grace period.
The MPP received the command to unregister new stations by using configurations that are
set in the configuration history.
Proposed Solution
About this task
POMS_00022
POMS events
Event text Remove Stations sent successfully to {0}
Problem description
The MPP received command to unregister stations and is in the process of unregistering the
stations.
Proposed Solution
About this task
POMS_00023
Event text Failed sending Remove Stations to {0} with error {1}
Problem description
{1} - Error returned by MPP or Web Services.
The system could not send the Remove Stations command.
The MPP ignored the Remove Stations command.
POMS_00024
Proposed Solution
Procedure
1. Verify that the MPP is communicating properly with the EPM. The command
automatically starts again.
2. If the problem persists, restart the MPP.
POMS_00024
Event text Sending {0} Configuration
Problem description
{0} - The MPP that is receiving the configuration.
The system is reconfiguring the MPP by using configurations that are set in the MPP
configuration history.
Proposed Solution
About this task
POMS_00025
Event text Configuration sent successfully to {0}
POMS events
Problem description
{0} - The MPP that is receiving the configuration.
The MPP received the command to reconfigure itself and is in the process of reconfiguring.
Proposed Solution
About this task
POMS_00026
Event text Failed sending Configuration to {0} with error {1}
Problem description
{0} - The MPP receiving configuration.
{1} - Error that is returned by the MPP or Web Services.
The system could not send the Configure command.
The MPP ignored the Configure command.
Proposed Solution
Procedure

2. Restart the MPP.
POMS_00027
4. If the problem still persists, reboot the EPM.
POMS_00027
Event text Sending {0} Trunk Configuration
Proposed Solution
About this task
POMS_00028
Event text Trunk Configuration sent successfully to {0}
Proposed Solution
About this task
POMS_00029
POMS events
Event text Failed sending Trunk Configuration to {0} with error

{1}
Proposed Solution
About this task
POMS_00030
Event text Woke up
Proposed Solution
About this task
POMS_00031
Event text Going to sleep
POMS_00032
Proposed Solution
About this task
POMS_00032
Event text Exception while a sleep
Proposed Solution
About this task
POMS_00033
Event text Updated {1} configuration change(s) on MPP {0}
Problem description
{0} - The MPP that is receiving configuration.
{1} - The subsystems that were modified.
The system downloaded configuration changes to the MPP.
POMS events
Proposed Solution
About this task
POMS_00034
Event text Bad date format in {0} from database table {1}
with key {2}
Associate alarm Name: QOMS_00034

details
SNMP Trap ID: 17133
Event level Internal error.

Problem description
{0} - The name of the component.
{1} - The name of the database table.
{2} - Provides information about the invalid key.
Dates stored in the database are invalid.
Proposed Solution
About this task
Invalid date formats are automatically recovered as Dec. 31, 1969.
Procedure
POMS_00035
POMS_00035
Event text MPP {0} has port(s) {1} that have not been
configured by EPM

details
SNMP Trap ID: 17134

Problem description
{1} - The ports on the MPP that are not configured in the EPM.
The MPP has ports that have not been configured by the EPM.
Proposed Solution
Procedure
1. Review port distribution information by using the EPM Web interface.

If the ports that have not been configured are deleted ports, no action is required.
2. For all other reasons, restart the MPP.
POMS_00036
POMS events
Event text MPP {0} has port(s) {1} that have not been
assigned to it by EPM

details
SNMP Trap ID: 17135

Problem description
{1} - The ports on the MPP that are not assigned to the MPP in the EPM.
The MPP has ports that the EPM has not assigned to it.
Proposed Solution
Procedure

2. Restart the MPP.
POMS_00037
Event text MPP {0} has port(s) {1} that has been assigned to
another MPP by EPM

details
SNMP Trap ID: 17136
POMS_00038

Problem description
{1} - The ports on the MPP that are configured on another MPP in the EPM.
The MPP has ports that the EPM assigned to another MPP.
Proposed Solution
Procedure

2. Restart the MPP.
POMS_00038
Event text Initial EPM Requested state ({0}) is not consistent

with the "{1}" MPP state ({2}); Avaya Aura Experience
Portal System Requested state changed to ({3})
Problem description
{0} - The state that is held by the EPM for the MPP.
{2} - The state that is reported by MPP.
{3} - The new EPM state.
POMS events
When the EPM starts up, the current MPP state is different from the state that the EPM
retrieved. For example, the MPP is currently in the Stopped state, but the EPM remembers
that the MPP is in the Running state.
Proposed Solution
About this task
No action is required. The EPM sets the MPP state to its current state.
POMS_00039
Event text Unknown state ({0}) received from the "{1}" MPP
withcurrent state ({2}) and EPM requested state
({3})
Associate alarm name QOMS_00039

Alarm Codes page.
Problem description
{0} - The state that is held by EPM for the MPP (numeric value).
{2} - The state that is reported by MPP.
{3} - The new EPM state.
When the EPM starts up, it cannot retrieve the MPP current state.
POMS_00040
Proposed Solution
Procedure
Restart the MPP.
POMS_00040
Event text {0} - Unknown exception occurred while "{1}";

Cause \ {2}; Stack \ {3}

details
SNMP Trap ID: 17138

Problem description
{0} - The routine reporting the exception.
{1} - The operation being performed when the exception occurred.
{2} - The cause of the exception.
{3} - The partial stack trace of the exception.
Internal error.
POMS events
Proposed Solution
Procedure
Restart the EPM by entering the service epm restart command.
POMS_00041
Event text {0} - Exception "{1}" occurred while "{2}"; Cause

{3}; Stack \ {4}

details
SNMP Trap ID: 17182

Problem description
{1} - The description of the exception.
{3} - The cause of the exception.
{4} - The partial stack trace of the exception.
Internal error.
POMS_00042
Proposed Solution
Procedure
Restart the EPM by entering the service epm restart command.
POMS_00042
Event text MPP {0} logging attempt to system log failed
Associate alarm details Name: QOMS_00042

SNMP Trap ID: 17204

Problem description
The MPP cannot save log messages to the Avaya Aura Experience Portal database.
Proposed Solution
Procedure
1. Run hostname -i to determine that the hostname is correct. Ensure that this not
<localhost>.
2. If the IP address is incorrect, verify that appLoggingURL in the file
voiceportal.properties is blank or contains the IP address of the EPM.
3. If the IP address is correct, restart the MPP.
POMS events
4. If the problem persists, restart Tomcat on the EPM.
POMS_00043
Event text {0} - Realtime Database is closed; attempting to

reopen
Problem description
{0} - The routine reporting the problem.
An internal database problem occurred.
The EPM is reestablishing a connection.
Proposed Solution
About this task
POMS_00044
Event text {0} - Error opening realtime database {1} ("{2}")
Problem description
{1} - The database error.
POMS_00045
{2} - The text representing the database errors.

The EPM could not establish a connection with the Avaya Aura Experience Portal
database.
Proposed Solution
About this task
POMS_00045
Event text {0} - Error opening realtime database causing OMS

to terminate {1} ("{2}")

details
SNMP Trap ID: 17139

Problem description
The Avaya Aura Experience Portal system could not connect to the Avaya Aura
Experience Portal database.
The EPM could not poll the MPPs.
The system has shut down.
POMS events
Proposed Solution
Procedure
1. Restart the Postgres database.

2. Restart Tomcat.
3. If the problem persists, restore the database from a backup.
5. If the problem persists, reinstall the EPM.
POMS_00046
Event text {0} - Unknown error opening realtime database
Problem description
Experience Portal database. The system has shut down.
The error could not be determined.
Proposed Solution
About this task
POMS_00047
POMS_00047
Event text {0} - Unknown error opening realtime database

causing OMS to terminate

SNMP Trap ID: 17140

Problem description
Experience Portal database.
The EPM could not poll the MPPs.
The system has shut down.
Proposed Solution
Procedure

2. Restart Tomcat.
POMS events
POMS_00048
Event text {0} - Realtime database initialization error

occurred {1} ("{2}")
Problem description
{0} - The routine reporting the exception
{1} - The error code
{2} - The text representing the database errors
The EPM Web interfaces, System Monitor, and MPP Details pages, could not open the Avaya
Aura Experience Portal database.
Proposed Solution
Procedure

2. Restart Tomcat.
POMS_00049
POMS_00050
Event text {0} System Data Module (SDM) initialization error

occurred "{1}"

details
SNMP Trap ID: 17141

Problem description
{1} - The text representing the SDM error
The Avaya Aura Experience Portal system could not connect to the administration
configuration database utility.
Proposed Solution
Procedure
1. Restart Tomcat.
POMS_00050
Event text {0} - Failed getting session for configuration

database (SDM)

details
SNMP Trap ID: 17142
POMS events

Problem description
The Avaya Aura Experience Portal system could not access the configuration database
object.
Proposed Solution
Procedure
1. Restart Tomcat.
POMS_00051
Event text {0} - Failed getting instance of configuration

database (SDM) Manager

details
SNMP Trap ID: 17143

POMS_00052
Problem description
{0} - The routine reporting the exceptions
object.
Proposed Solution
Procedure
1. Restart Tomcat.
POMS_00052
Event text {0} - Failed getting configuration database (SDM)

Avaya Aura Experience Portal System

details
SNMP Trap ID: 17144

Alarm Codes page.
Problem description
object.
POMS events
Proposed Solution
Procedure
1. Restart Tomcat.
POMS_00053
Event text {0} - Failed getting configuration database (SDM)

Avaya Aura Experience Portal System with error
"{1}"

details
SNMP Trap ID: 17145

Alarm Codes page.
Problem description
{1} - The text representing the SDM error.
object.
POMS_00054
Proposed Solution
Procedure
1. Restart Tomcat.
POMS_00054
Event text {0} - Configuration change dates container not

defined

details
SNMP Trap ID: 17146

Problem description
The Avaya Aura Experience Portal system could not access the configuration dates.
Proposed Solution
Procedure
1. Restart Tomcat.
POMS events
POMS_00055
Event text {0} - Configuration change dates resource not

defined

details
SNMP Trap ID: 17147

Problem description
Proposed Solution
Procedure
1. Restart Tomcat.
POMS_00056
Event text {0} - Exception occurred while retrieving

configuration change dates with error "{1}"
POMS_00057

details
SNMP Trap ID: 17148

Alarm Codes page.
Problem description
Proposed Solution
Procedure
1. Save one entry per category for Global Settings, MPP, and other configuration
categories.
2. Restart Tomcat.
POMS_00057
Event text {0} - Exception occurred while retrieving H.323

configuration with error {1}

details
SNMP Trap ID: 17149
POMS events

Problem description
The Avaya Aura Experience Portal system could not access the H.323 configuration data.
Proposed Solution
Procedure
1. Save one H.323 switch.

2. Restart Tomcat.
POMS_00058
Event text {0} - Global Settings container not defined

SNMP Trap ID: 17150

POMS_00059
Problem description
The Avaya Aura Experience Portal system could not access the Global Settings configuration
data.
Proposed Solution
Procedure
1. Restart Tomcat.
POMS_00059
Event text {0} - Global Settings resource not defined

SNMP Trap ID: 17151

Problem description
data.
POMS events
Proposed Solution
Procedure
1. Restart Tomcat.
POMS_00060
Event text {0} - Exception occurred while retrieving global

settings with error "{1}"

SNMP Trap ID: 17152

Problem description
data.
Proposed Solution
Procedure
1. Save Global Settings.

2. Restart Tomcat.
POMS_00061

POMS_00061
Event text {0} - Error retrieving EPM logging host IP

address with error "{1}"

details
SNMP Trap ID: 17153

Problem description
The application server logging host has an incorrect IP address configuration.
Proposed Solution
Procedure
On the application server, update the properties file with the correct host
configuration.
POMS events
POMS_00062
Event text Exception occurred while retrieving User Account

Configuration with error {(1)}

details
SNMP Trap ID: 17154

Problem description
The system encountered an exception when retrieving user account configurations.
Proposed Solution
Procedure
1. Save the VoIP configurations.

2. Restart Tomcat.
POMS_00063
POMS_00063
Event text {0} - VoIP resources not found

SNMP Trap ID: 17155

Problem description
The Avaya Aura Experience Portal system could not access the VoIP configuration data.
Proposed Solution
Procedure

2. Restart Tomcat.
POMS_00064
POMS events
Event text {0} - Exception occurred while retrieving Voice

over IP configuration with error "{1}"

details
SNMP Trap ID: 17156

Alarm Codes page.
Problem description
The Avaya Aura Experience Portal system could not access the VoIP configuration data.
Proposed Solution
Procedure

2. Restart Tomcat.
POMS_00065
Event text {0} - Exception occurred while retrieving TTS

configuration with error "{1}"

details
SNMP Trap ID: 17157
POMS_00066

Problem description
The Avaya Aura Experience Portal system could not access the Text-to-Speech (TTS) (TTS)
configuration data.
Proposed Solution
Procedure
1. Save one TTS Server.

2. Restart Tomcat.
POMS_00066
Event text {0} - Exception occurred while retrieving

application configuration with error "{1}"

details
SNMP Trap ID: 17158

POMS events
Problem description
The Avaya Aura Experience Portal system could not access the application configuration
data.
Proposed Solution
Procedure
1. Save one application.

2. Restart Tomcat.
POMS_00067
Event text {0} - Exception occurred while retrieving ASR


details
SNMP Trap ID: 17159

Problem description
POMS_00068

The Avaya Aura Experience Portal system could not access the Avaya Voice Browser (ASR)
configuration data.
Proposed Solution
Procedure
1. Save one ASR server.

2. Restart Tomcat.
POMS_00068
Event text {0} - Exception occurred while retrieving Media

Processing Platform configuration with error "{1}"

details
SNMP Trap ID: 17160

Alarm Codes page.
Problem description
The Avaya Aura Experience Portal system could not access the MPP configuration data.
POMS events
Proposed Solution
Procedure
1. Save one ASR server.

2. Restart Tomcat.
POMS_00069
Event text MPP configuration has changed on {0}
Problem description
{0} - The date that the configuration was added, modified, or deleted.
The EPM detected that the MPP configuration has been changed.
Proposed Solution
About this task
POMS_00070
Event text ASR configuration has changed on {0}
POMS_00071
Problem description
The EPM detected that the ASR configuration has been changed.
Proposed Solution
About this task
POMS_00071
Event text Application configuration has changed on {0}
Problem description
The EPM detected that the application configuration has been changed.
Proposed Solution
About this task
POMS events
POMS_00072
Event text TTS configuration has changed on {0}
Problem description
{0} - Date the configuration was added, modified or deleted
The EPM detected that the TTS configuration has been changed.
Proposed Solution
About this task
POMS_00073
Event text Voice over IP configuration has changed on {0}
Problem description
The EPM detected that the VoIP configuration has been changed.
POMS_00074
Proposed Solution
About this task
POMS_00074
Event text User configuration has changed on {0}
Problem description
The EPM detected that the user configuration has been changed.
Proposed Solution
About this task
POMS_00075
Event text Global settings configuration has changed on {0}
Problem description
POMS events
The EPM detected that the global settings configuration has been changed.
Proposed Solution
About this task
POMS_00076
Event text H.323 configuration has changed on {0}
Problem description
The EPM detected that the H.323 configuration has been changed.
Proposed Solution
About this task
POMS_00077
Event text {0} - Configuration data exception occurred while

{1} with error "{2}"

details
SNMP Trap ID: 17161
POMS_00078

Problem description
{2} - The SDM error.
The EPM encountered problems while retrieving configuration data from the MPPs.
Proposed Solution
Procedure
1. Save one entry per category for Global Settings, MPP, and other configuration
categories.
2. Restart Tomcat.
POMS_00078
Event text {0} - Realtime data exception occurred while {1}

with error "{2}"

SNMP Trap ID: 17162
POMS events

Problem description
The EPM encountered problems while retrieving real-time data from the MPPs.
Proposed Solution
Procedure

2. Restart Tomcat.
POMS_00079
Event text {0} - Manager exception occurred while {1} with

error "{2}"

SNMP Trap ID: 17163

POMS_00080
Problem description
{2} - The management error.
The EPM encountered problems while retrieving data from the MPPs.
Proposed Solution
Procedure
1. Restart Tomcat.
POMS_00080
Event text {0} - Error committing performance data to

database with error {1} "{2}"

details
SNMP Trap ID: 17164

Problem description
POMS events
The EPM encountered problems storing performance data retrieved from the MPPs in the real-
time database.
Proposed Solution
Procedure
1. Verify that the database has sufficient space.

3. Restart Tomcat.
POMS_00081
Event text {0} - Error deleting performance data before {1}

from database with error {2} "{3}"

details
SNMP Trap ID: 17165

Problem description
{1} - The date before which all data is deleted.
The EPM encountered problems while purging configuration data from the database.
POMS_00082
Proposed Solution
Procedure

2. Restart Tomcat.
Note:
The performance data that is generated after the backup will be lost.
POMS_00082
Event text {0} - Configuration data exception occurred while

fetching data for OMS UI with error "{1}"

details
SNMP Trap ID: 17166

Alarm Codes page.
Problem description
The EPM encountered problems while retrieving configuration data for real-time displays.
POMS events
Proposed Solution
Procedure

2. Restart Tomcat.
POMS_00083
Event text {0} - Realtime data exception occurred while

fetching data for OMS UI with error {1} ("{2}")

details
SNMP Trap ID: 17167

this alarm by logging on to Experience Portal Manager and using
Problem description
{1} - The number representing the database error.
{2} - The text representing the database error.
The EPM encountered problems while retrieving real-time data for real-time displays.
POMS_00084
Proposed Solution
Procedure

2. Restart Tomcat.
POMS_00084
Event text {0} - Manager exception occurred while fetching

data for OMS UI with error "{1}"

details
SNMP Trap ID: 17168

Problem description
{1} - The text representing the error
The EPM encountered problems while processing data for real-time displays.
Proposed Solution
Procedure
1. Restart Tomcat.
POMS events
POMS_00085
Event text {0} - Unknown exception occurred while fetching

data for OMS UI

SNMP Trap ID: 17169

Problem description
The EPM encountered problems while processing data for real-time displays.
Proposed Solution
Procedure
1. Restart Tomcat.
POMS_00086
POMS_00087
Event text {0} - Exception occurred while waiting for MPP poll
"{1}"
Problem description
{1} - The text representing the exception.
The Avaya Aura Experience Portal system encountered problems while waiting for the MPP
to respond to polling request.
Proposed Solution
Procedure
1. Restart Tomcat.
POMS_00087
Event text MPP {0} did not respond to poll request
Problem description
{0} - The name of the MPP that could not respond.
The MPP is marked as not responding to a polling request. The EPM makes multiple attempts
to poll the MPP.
POMS events
Proposed Solution
About this task
POMS_00088
Event text MPP {0} has been marked Not Responding because it
failed to respond to multiple poll requests

details
SNMP Trap ID: 17170

Alarm Codes page.
Problem description
{0} - The MPP that failed to respond.
The MPP did not respond to multiple polling requests.
Proposed Solution
Procedure
1. Verify that the MPP is running properly.

2. Verify that the MPP can be pinged from the EPM.
3. Review the log file for MPP errors that might have occurred before the MPP stopped
responding to the polls.
4. If the MPP is running, manually restart the MPP, and then wait for the poll.
5. If the MPP does not respond:
POMS_00089
a) Reboot the MPP, and wait for the poll.

b) Restart the EPM, and wait for the poll.
c) Reinstall the MPP, and wait for the poll.
Note:
Accept the certificate for the MPP.
POMS_00089
Event text MPP {0} has again responded to polls since its last
successful poll at {1}
Problem description
{1} - The date and time the MPP responded to a heartbeat.
The MPP is responding to polling requests after being marked as not responding.
Proposed Solution
About this task
POMS_00090
Event text {0} - Manager exception occurred while processing

MPP {1} schedule with error "{2}"
POMS events

details
SNMP Trap ID: 17171

Problem description
{1} - The MPP owning the schedule that is being processed.
{2} - The management error.
The Avaya Aura Experience Portal system encountered problems while processing the restart
schedule for an MPP.
Proposed Solution
Procedure
1. Restart Tomcat.
POMS_00091
Event text MPP {0} schedule restart requested
Problem description
{0} - The name of the MPP that is being restarted.
The MPP restarts.
POMS_00092
Proposed Solution
About this task
POMS_00092
Event text MPP {0} removed from OMS polling
Problem description
{0} - The name of the MPP that is being deleted from the real-time database.
The MPP has been deleted from the polling queue.
Proposed Solution
About this task
POMS_00093
Event text MPP {0} is being stopped pending removal from OMS
polling
POMS events
Problem description
{0} - The name of the MPP that is being stopped before being deleted from real-time
database.
The MPP is being stopped before being deleted from the polling queue.
Proposed Solution
About this task
POMS_00094
Event text MPP {0} stations being removed
Problem description
{0} - The name of the MPP that has its stations being removed.
Proposed Solution
About this task
POMS_00095
Event text MPP {0} unexpectedly entered the error state

SNMP Trap ID: 17172
POMS_00096

Problem description
{0} - The name of the MPP that has entered the Error state.
One or more processes on the MPP has failed and could not be restarted or has continued to
fail. The MPP is not accepting calls.
Proposed Solution
Procedure

2. If the problem persists, reboot the MPP from the EPM.
3. If the problem persists, reinstall the MPP.
4. If you cannot reboot the MPP from the EPM, manually reboot the MPP.
POMS_00096
Event text MPP {0} unexpectedly entered degraded state

SNMP Trap ID: 17173

POMS events
Problem description
{0} - The name of the MPP that has entered the Degraded state.
One or more stations cannot be registered.
Proposed Solution
Procedure
1. Verify that the stations are properly configured on the EPM.

2. Verify that the stations are working on the MPPs.
3. If there are problems with the stations, reconfigure the stations, and restart the
affected MPPs one by one to restore access to the stations.
4. If the stations are properly configured, restart the MPP from the EPM.
6. If the problem still persists, reinstall the MPP.
POMS_00097
Event text MPP {0} unexpectedly is starting

SNMP Trap ID: 17174

Problem description
{0} - The MPP that has entered the Starting state.
The MPP was running normally but entered the Starting state unexpectedly
POMS_00098
Proposed Solution
About this task
The MPP might reenter the Running state automatically (if Auto Restart was set for the MPP)
and start taking calls again.
Procedure
1. If the MPP does not reenter the Running state within five minutes, restart the MPP
from the EPM.
POMS_00098
Event text MPP {0} unexpectedly stopped

SNMP Trap ID: 17175

Problem description
{0} - The MPP that has entered the Stopped state.
The MPP was running normally but entered the Stopped state unexpectedly. The MPP can no
longer take calls.
POMS events
Proposed Solution
About this task
Procedure
from the EPM.
POMS_00099
Event text MPP {0} unexpectedly is stopping

SNMP Trap ID: 17176

Problem description
{0} - The MPP that has entered the Stopping state.
The MPP was running normally but entered the Stopping state unexpectedly. The MPP can
no longer take calls.
POMS_00100
Proposed Solution
About this task
Procedure
from the EPM.
POMS_00100
Event text {0} - SQL exception occurred saving MPP {1} with
error {2} ("{3}")

details
SNMP Trap ID: 17177

Problem description
{1} - The MPP that was being saved resulted in database error.
POMS events
The EPM encountered problems while saving the MPP configuration and status data in the
real-time database.
Proposed Solution
Procedure

2. Restart Tomcat.
POMS_00101
Event text MPP {0} was restarted to remove unconfigured

stations {1}
Problem description
{0} - The MPP that was being restarted.
{1} - The unconfigured stations.
When the Avaya Aura Experience Portal starts, the MPP has stations that are not configured
on the EPM. The MPP was restarted to remove the unconfigured stations.
Proposed Solution
About this task
POMS_00102
POMS_00102
Event text Error {1} restarting MPP {0} with unknown or another
MPP's station(s) configured
Problem description
{0} - The MPP that was being restarted.
{1} - The error that occurred when attempting to restart the MPP.
When the Avaya Aura Experience Portal starts, the MPP has stations that are configured on
another MPP. The MPP was restarted to remove the stations.
Proposed Solution
Procedure

POMS_00103
Event text Failed sending List Stations to {0} with error {1}
POMS events
Problem description
{0} - The MPP with the stations.
{1} - The error that occurred attempting to list stations.
The Avaya Aura Experience Portal system encountered problems while retrieving stations
that are provisioned on the MPP.
Proposed Solution
Procedure

POMS_00104
Event text Null result returned sending Add Stations to {0}
Problem description
{0} - The MPP to receive the stations.
The Avaya Aura Experience Portal system encountered problems while downloading stations
to the MPP.
Proposed Solution
Procedure

POMS_00105
POMS_00105
Event text Error {1} returned sending Add Stations to {0}
Problem description
{0} - The MPP that was to receive the stations.
{1} - The error that occurred when attempting to add stations.
The Avaya Aura Experience Portal system encountered problems while downloading stations
to the MPP.
Proposed Solution
Procedure

POMS_00106
Event text Null result returned sending Configuration to {0}
POMS events
Problem description
{0} - The MPP that was to be configured.
The Avaya Aura Experience Portal system encountered problems while downloading
configuration data to the MPP.
Proposed Solution
Procedure

POMS_00107
Event text Error {1} returned sending Configuration to {0}
Problem description
{1} - The error that occurred when attempting to configure MPP.
POMS_00108
Proposed Solution
Procedure

POMS_00108
Event text Null result returned sending Trunk Configuration to

{0}
Proposed Solution
About this task
POMS_00109
Event text Error {1} returned sending Trunk Configuration to

{0}
POMS events
Proposed Solution
About this task
POMS_00110
Event text Null result returned sending Halt command to {0}
Problem description
{0} - The MPP that was to be halted.
The Avaya Aura Experience Portal system encountered problems while halting the MPP.
Proposed Solution
Procedure
1. When the Halt command is reenabled, start the command from the EPM.
2. If the MPP does not halt, manually stop and halt the MPP.
POMS_00111
Event text Error {1} returned sending Halt command to {0}
POMS_00112
Problem description
{0} - MPP that was to be halted
{1} - Error that occurred when attempting to halt the MPP
The Avaya Aura Experience Portal system encountered problems while halting the MPP.
Proposed Solution
Procedure
1. When the Halt command is reenabled, start the command from the EPM.
2. If the MPP does not halt, manually stop and halt the MPP.
POMS_00112
Event text Null result returned sending List Stations to {0}
Problem description
{0} - The MPP that had the stations.
that were provisioned on the MPP.
Proposed Solution
Procedure

POMS events
POMS_00113
Event text Error {1} returned sending List Stations to {0}
Problem description
{1} - The error that occurred when attempting to list stations.
that were provisioned on the MPP.
Proposed Solution
Procedure

POMS_00114
Event text Null result returned sending Reboot command to {0}
POMS_00115
Problem description
{0} - The MPP that was to be rebooted.
The Avaya Aura Experience Portal system encountered problems while rebooting the MPP.
Proposed Solution
Procedure
1. When the Reboot command is reenabled, start the command from the EPM.
2. If the MPP does not reboot, manually reboot the MPP, and start the MPP when it
enters the Stopped state.
POMS_00115
Event text Error {1} returned sending Reboot command to {0}
Problem description
{0} - The MPP that was to be rebooted.
{1} - The error that occurred while attempting to reboot the MPP.
The Avaya Aura Experience Portal system encountered problems while rebooting the MPP.
Proposed Solution
Procedure
1. When the Reboot command is reenabled, start the command from the EPM.
POMS events
2. If the MPP does not reboot, manually reboot the MPP and start the MPP when it
enters the Stopped state.
POMS_00116
Event text Null result returned sending Remove Stations to {0}
Problem description
The Avaya Aura Experience Portal system encountered problems while removing stations
from the MPP.
Proposed Solution
Procedure

POMS_00117
Event text Error {1} returned sending Remove Stations to {0}
POMS_00118
Problem description
{1} - The error that occurred while attempting to remove stations.
The Avaya Aura Experience Portal system encountered problems while removing stations
from the MPP.
Proposed Solution
Procedure

POMS_00118
Event text Null result returned sending Stop command to {0}
Problem description
{0} - The MPP that was to be stopped.
The Avaya Aura Experience Portal system encountered problems while stopping the MPP.
POMS events
Proposed Solution
Procedure
1. When the Stop command is reenabled, start the command from the EPM.
2. If the MPP does not stop, manually reboot the MPP.
3. If the MPP does not enter the Stopped state, reinstall the MPP.
POMS_00119
Event text Error {1} returned sending Stop command to {0}
Problem description
{0} - The MPP that was to be stopped.
{1} - The error that occurred when attempting to stop stations.
The Avaya Aura Experience Portal system encountered problems while stopping the MPP.
Proposed Solution
Procedure
1. When the Stop command is reenabled, start the command from the EPM.
POMS_00120
POMS_00120
Event text Null result returned sending Start command to {0}
Problem description
{0} - The MPP that was to be started.
The Avaya Aura Experience Portal system encountered problems when starting the MPP.
Proposed Solution
Procedure
1. When the Start command is reenabled, start the command from the EPM.
2. If the MPP does not start, manually reboot the MPP and start the MPP from the
EPM when it enters the Stopped state.
POMS_00121
Event text Error {1} returned sending Start command to {0}
Problem description
{0} - The MPP that was to be started.
POMS events
{1} - The error that occurred while attempting to send Start command to the MPP.
The Avaya Aura Experience Portal system encountered problems while starting the MPP.
Proposed Solution
Procedure
1. When the Start command is reenabled, start the command from the EPM.
2. If the MPP does not start, manually reboot the MPP and start the MPP from the
EPM when it enters the Stopped state.
POMS_00122
Event text Configuring MPP {0} failed with no result

SNMP Trap ID: 17183

Problem description
POMS_00123
Proposed Solution
About this task
The configuration downloaded automatically again to the MPP.
Procedure
1. If the configuration cannot be downloaded, manually reboot the MPP and start the
MPP from the EPM when the MPP enters the Stopped state
POMS_00123
Event text Configuring MPP {0} failed with error {1}

SNMP Trap ID: 17184

Problem description
{1} - The error that occurred while attempting to configure the MPP.
POMS events
Proposed Solution
About this task
The configuration is downloaded automatically again to the MPP.
Procedure
1. If configuration cannot be downloaded, manually reboot the MPP and start the MPP
from the EPM when the MPP enters the Stopped state.
POMS_00124
Event text {0} - Encrypt/Decrypt Invalid Key Exception on

port {1} with error {2}

details
SNMP Trap ID: 17185

Problem description
{0} - The routine with decryption problem.
{1} - The port that had the password that cannot be decrypted.
{2} - The error encountered when decrypting password.
The Avaya Aura Experience Portal system encountered problems while encrypting or
decrypting a station password.
POMS_00125
Proposed Solution
Procedure
1. Delete and reenter the stations.

2. If the problem persists, restart the EPM by entering the service epm restart
command.
3. If the problem still persists, reinstall the EPM.
POMS_00125
Event text {0} - Encrypt/Decrypt No Such Algorithm Exception

on port {1} with error {2}

details
SNMP Trap ID: 17186

Problem description
{2} - The error encountered decrypting password.
POMS events
Proposed Solution
Procedure
Reinstall the EPM.
POMS_00126
Event text {0} - Encrypt/Decrypt No Such Padding Exception on

port {1} with error {2}

details
SNMP Trap ID: 17187

Problem description
{2} - The error encountered decrypting password.
Proposed Solution
Procedure
Reinstall the EPM.
POMS_00127
POMS_00127
Event text MPP {0} returns a station/license count of {1} that

differs from the EPM configured count of {2}
Problem description
{1} - The number of stations reported in the MPP heartbeat
{2} - The number of stations that the EPM believes are configured.
The number of configured stations reported by the MPP exceeded the number of stations that
were configured by the EPM.
Proposed Solution
Procedure

2. If the MPP does not start, manually reboot the MPP.
3. When the MPP enters the Stopped state, start the MPP.
POMS_00128
Event text Start/Restart failure; MPP {0} failed to accept

start command after it was stopped
POMS events

details
SNMP Trap ID: 17201

Problem description
The Avaya Aura Experience Portal system encountered problems while restarting the MPP
after the MPP was stopped. The MPP might have rejected the Start command and did not
restart.
Proposed Solution
Procedure

2. If the MPP does not start, manually reboot the MPP.
3. When the MPP enters the Stopped state, start the MPP.
POMS_00129
Event text Stop request to MPP {0} failed. Telephony ports may
still be In Service with MPP {0}. The MPP {0} must
be stopped from the EPM or from the MPP Command Line
Interface to complete the deletion.

details
SNMP Trap ID: 17202
POMS_00130

Alarm Codes page.
Problem description
The Avaya Aura Experience Portal system encountered problems while deleting an MPP. The
MPP could not be deleted because it could not be stopped.
Proposed Solution
Procedure
1. Stop the MPP from the EPM.

The MPP enters the Stopped state.
POMS_00130
Event text MPP {0} did not respond to poll request with error
({1})
Problem description
{1} - The error returned by the Web service.
This error could be caused by security violation or the MPP not responding to poll request.
POMS events
Proposed Solution
Procedure
1. If this problem does not occur intermittently, restart the MPP from the EPM.
2. If you cannot restart the MPP from the EPM, manually reboot the MPP.
POMS_00131
Event text MPP {0} did not respond to poll request with internal
error ({1})
Problem description
{1} - The error generated by EPM environment.
The MPP could not respond to the heartbeat.
Proposed Solution
Procedure
If this problem does not occur intermittently, restart the EPM.
POMS_00132
POMS_00132
Event text MPP {0} did not respond to poll request with error
({1})
Problem description
{1} - The error returned by the MPP.
The MPP could not respond to the heartbeat with an internal description of the following:
The MPP is in an incorrect state for command.
The MPP is unconfigured.
The command does not exist.
The system Manager timed out the previous command.
The MPP configuration update failed.
An internal MPP error occurred.
Proposed Solution
Procedure
1. If this problem does not occur intermittently, restart the MPP from the EPM.
2. If you cannot restart the MPP from the EPM, manually reboot the MPP.
POMS events
POMS_00133
Event text Database error occurred updating real-time data for

MPP {0} with error {1}
Problem description
{1} - The error returned by the MPP.
The system could not update the MPP persistent database due to a database error.
Proposed Solution
About this task
POMS_00134
Event text Database error occurred updating real-time data for

real-time port {0} on {1} with error {2}
Problem description
{0} - The port that could not be written.
{1} - The switch containing the port.
{2} - The error returned by the database.
POMS_00135
The system could not update the port persistent database due to a database error.
Proposed Solution
About this task
POMS_00135
Event text Database error occurred updating change dates for

MPP {0} and resource {1} with error {2}
Problem description
{1} - A resource such as ASR or TTS that could not be updated.
The system could not update the change dates persistent database due to a database error.
Proposed Solution
About this task
POMS_00136
POMS events
Event text Database error occurred updating configuration

change dates for MPP {0} and resource {1} with error
{2}
Problem description
The system could not update the configuration change dates persistent database due to a
database error.
Proposed Solution
About this task
POMS_00137
Event text Database error occurred deleting real-time data for

real-time port {0} on {1} with error {2}
Problem description
{2} - An error returned by the database.
The system could not delete the port persistent database due to a database error.
POMS_00138
Proposed Solution
About this task
POMS_00138
Event text Database error occurred deleting all change dates

for MPP {0} with error {1}
Problem description
{0} - the name of the MPP.
The system could not delete the MPP persistent database due to a database error.
Proposed Solution
About this task
POMS_00139
Event text Database error occurred deleting real-time data for

MPP {0} with error {1}
POMS events
Problem description
The system could not delete real-time data due to a database error.
Proposed Solution
About this task
POMS_00140
Event text {0} consecutive database errors occurred exceeded

maximum of {1} updating the real-time database,
OMS terminating

details
SNMP Trap ID: 17194

Problem description
{0} - The number of the consecutive database errors that occurred.
{1} - The maximum number of errors that can occur before the OMS was terminated.
The OMS could not operate due to too many consecutive database errors.
POMS_00141
Proposed Solution
Procedure
1. Restart Postgres.
2. Restart Tomcat.
POMS_00141
Event text Illegal state exception occurred updating mpp dates

with error {0}
Problem description
{0} - The description of the illegal state exception error.
An illegal state exception occurred.
Proposed Solution
Procedure
2. Restart Tomcat.
POMS events
POMS_00142
Event text Illegal state exception occurred updating

configuration dates with error {0}
Problem description
{0} - The description of the illegal state exception error
Proposed Solution
Procedure
2. Restart Tomcat.
POMS_00143
Event text {0} database errors exceeded maximum of {1} while

updating real-time port database, extra port
failures not logged.
POMS_00144
Problem description
{0} - The current number of the consecutive port failures that were logged.
{1} - The maximum number of the consecutive port failures that can be logged.
Proposed Solution
About this task
POMS_00144
Event text MPP {0} is being halted because last requested state
before not responding was halted
Problem description
The MPP was not in the Halted state. The MPP will be halted to match its state on the EPM.
Proposed Solution
About this task
POMS_00145
POMS events
Event text MPP {0} is being stopped because last requested state
before not responding was stopped
Problem description
The MPP was not in the Stopped state. The MPP will be stopped to match its state on the.
Proposed Solution
About this task
POMS_00146
Event text MPP {0} is being restarted to recover MPP resources
Problem description
The MPP was not in the Restarted state. The MPP will be restarted to match its state on the
EPM.
Proposed Solution
About this task
POMS_00147
POMS_00147
Event text MPP {0} is in the error state, which is different

from its last known state
Problem description
The MPP was in the Error state, which is different from the original state. The MPP will remain
in the Error state.
Proposed Solution
About this task
POMS_00148
Event text MPP {0} is in the Degraded state, which is different

Problem description
The MPP was in the Degraded state, which is different from the original state. The MPP will
remain in the Degraded state.
POMS events
Proposed Solution
About this task
POMS_00149
Event text MPP {0} is in the Starting state, which is different

Problem description
The MPP was in the Starting state, which is different from the original state. The MPP will
remain in the Starting state.
Proposed Solution
About this task
POMS_00150
Event text MPP {0} is in the Stopped state, which is different

POMS_00151
Problem description
The MPP was in the Stopped state, which is different from the original state. The MPP will
remain in the Stopped state.
Proposed Solution
About this task
POMS_00151
Event text MPP {0} is in the Stopping state, which is different

Problem description
The MPP was in the Stopping state, which is different from the original state. The MPP will
remain in the Stopping state.
Proposed Solution
About this task
POMS_00152
POMS events
Event text MPP {0} is in the Running state, which is different

Problem description
The MPP was in the Running state, which is different from the original state. The MPP will
remain in the Running state.
Proposed Solution
About this task
POMS_00153
Event text MPP {0} is in the Halting state, which is different

Problem description
The MPP was in the Halting state, which is different from the original state. The MPP will remain
in the Running state.
Proposed Solution
About this task
POMS_00154
POMS_00154
Event text MPP {0} is in the Rebooting state, which is different

Problem description
The MPP was in the Rebooting state, which is different from the original state. The MPP will
remain in the Rebooting state.
Proposed Solution
About this task
POMS_00155
Event text MPP {0} is in the Booting state, which is different

Problem description
The MPP was in the Booting state, which is different from the original state. The MPP will
remain in the Booting state.
POMS events
Proposed Solution
About this task
POMS_00156
Event text MPP {0} is in the Halted state, which is different

Problem description
The MPP was in the Halted state, which is different from the original state. The MPP will remain
in the Halted state.
Proposed Solution
About this task
POMS_00157
Event text MPP {0} is in the Never Used state, which is

different from its last known state
POMS_00158
Problem description
The MPP was in the Never Used state, which is different from the original state. The MPP will
remain in the Never Used state.
Proposed Solution
About this task
POMS_00158
Event text MPP {0} is in the Bad Install state, which is

different from its last known state
Problem description
The MPP was in the Bad Install state, which is different from the original state. The MPP will
remain in the Bad Install state.
Proposed Solution
About this task
POMS_00159
POMS events
Event text Failed to retrieve configuration change dates for

{0}, changes ignored for current pass
Problem description
The system could not retrieve change dates from the core services System Data Module
(SDM).
The system will try to retrieve the dates in the next update. The previous values will be kept,
and no configuration updates will occur until the change dates are successfully retrieved.
Proposed Solution
About this task
POMS_00160
Event text Failed to retrieve initial configuration change

dates; OMS will terminate!

details
SNMP Trap ID: 17203
Event level Failed event.

Problem description
During startup, the EPM could not retrieve change dates within 10 retrieval attempts.
The OMS will terminate.
POMS_00161
Proposed Solution
Procedure

2. Restart Tomcat.
POMS_00161
Event text MPP appears deleted and is skipped; MPP name (if
known) is {0}
Problem description
{0} - The name of the MPP server.
The MPP that was specified in the message has been deleted from the system.
Proposed Solution
About this task
POMS_00162
POMS events
Event text ASR appears deleted and is skipped; ASR name (if
known) is {0}
Problem description
The ASR server that was specified in the message has been deleted from the system.
Proposed Solution
About this task
POMS_00163
Event text APP appears deleted and is skipped; APP name (if
known) is {0}
Problem description
{0} - The name of the application server.
The application server that was specified in the message has been deleted from the system.
Proposed Solution
About this task
POMS_00164
POMS_00164
Event text TTS appears deleted and is skipped; TTSname (if

known) is {0}
Problem description
{0} - The name of the TTS server.
The TTS server that was specified in the message has been deleted from the system.
Proposed Solution
About this task
POMS_00165
Event text VOIP appears in transition and is skipped
Problem description
The Voice over IP connection is in transition.
POMS events
Proposed Solution
About this task
POMS_00166
Event text USER appears deleted and is skipped; USER name (if
known) is the {0}
Problem description
{0} - The user name.
The user name that was specified in the message has been deleted from the system.
Proposed Solution
About this task
POMS_00167
Event text Global Settings appears in transition and is skipped
POMS_00168
Problem description
The global settings are in transition and are being skipped.
Proposed Solution
About this task
POMS_00168
Event text H.323 switch or port range configuration appears

deleted and is skipped; H.323 name (of known) is {0}
Problem description
{0} - The name of the H.323 switch.
The H.323 stations or the port range configuration that was specified in the message has been
deleted from the system.
Proposed Solution
About this task
POMS_00169
Event text SIP trunk appears deleted and is skipped; SIP name
(if known) is{0}
POMS events
Problem description
{0} - The name of the SIP trunk.
The SIP trunk that was specified in the message has been deleted from the system.
Proposed Solution
About this task
POMS_00170
Event text Database error occurred updating real time data for
SIP trunk {0} with error {1}
Problem description
The Avaya Aura Experience Portal database encountered problems when updating real time
data fro the SIP trunk that was specified in the message.
Proposed Solution
About this task
POMS_00171
POMS_00171
Event text SIP trunk configuration that last changed on {0} was
retrieved from admin database
Problem description
{0} - The date that the SIP trunk configuration was last changed.
The SIP trunk configuration that was changed on the specified time in the message has been
retrieved.
Proposed Solution
About this task
POMS_00172
Event text Exception occurred while retrieving SIP trunk

Problem description
The system encountered a problem when retrieving the SIP trunk configuration.
POMS events
Proposed Solution
About this task
POMS_00173
Event text Deleting SIP to MPP map for nonexistent SIP {0}
Problem description
{0} -
The system we deleting the SIP connection that was specified in the message because the
SIP connection did not exist.
Proposed Solution
About this task
POMS_00174
Event text Error {1} occurred while deleting SIP to MPP map for
nonexistent SIP trunk {0}
POMS_00175
Problem description
{0} - The name of the SIP trunk that does not exist.
The system encountered a problem when deleting the SIP connection that was specified in
the message.
Proposed Solution
About this task
POMS_00175
Event text Database error occurred while deleting SIP trunk

"{0}" with error {1}
Problem description
The EPM local database encountered an error when the system was deleting the SIP trunk
that was specified in the message.
Proposed Solution
About this task
POMS events
POMS_00176
Event text Database error occurred while deleting MPP map for
SIP trunk "{0}" with error {1}
Problem description
The EPM local database encountered an error when the system was deleting the SIP trunk
that was specified in the message.
Proposed Solution
About this task
POMS_00177
Event text SIP trunk {0} removed from OMS polling
Problem description
The specified SIP trunk was removed from the OMS polling.
POMS_00178
Proposed Solution
About this task
POMS_00178
Event text MPP configuration was retrieved from admin database
Problem description
The MPP configuration was retrieved from the EPM local database.
Proposed Solution
About this task
POMS_00179
Event text ASR configuration was retrieved from admin database
Problem description
The ASR configuration was retrieved from the EPM local database.
POMS events
Proposed Solution
About this task
POMS_00180
Event text Application configuration was retrieved from admin

database
Problem description
The application configuration was retrieved from the EPM local database.
Proposed Solution
About this task
POMS_00181
Event text TTS configuration was retrieved from admin database
Problem description
The TTS configuration was retrieved from the EPM local database.
POMS_00182
Proposed Solution
About this task
POMS_00182
Event text VoIP configuration was retrieved from admin database
Problem description
The VoIP configuration was retrieved from the EPM local database.
Proposed Solution
About this task
POMS_00183
Event text User configuration was retrieved from admin database
Problem description
The user configuration was retrieved from the EPM local database.
POMS events
Proposed Solution
About this task
POMS_00184
Event text Global settings configuration was retrieved from

admin database
Problem description
The global setting configuration was retrieved from the EPM local database.
Proposed Solution
About this task
POMS_00185
Event text H.323 configuration was retrieved from admin

database
POMS_00186
Problem description
The H.323 configuration was retrieved from the EPM local database.
Proposed Solution
About this task
POMS_00186
Event text SIP configuration was retrieved from admin database
Problem description
The SIP configuration was retrieved from the EPM local database.
Proposed Solution
About this task
POMS_00187
Event text Administration property for {0} was null; default

value of {1} used
POMS events
Problem description
{1} - The default value for the administration property.
The administration property for the specified server was empty. The default value was used.
Proposed Solution
About this task
POMS_00188
Event text Last change date from MPP {0} for resource {1} has an
unexpected value of {2} and has been initialized
Problem description
{2} - The value of the specified resource.
The MPP that was specified in the event message has been initialized because the resource
of the MPP has an invalid value.
Proposed Solution
About this task
POMS_00189
POMS_00189
Event text Could not execute command "{1}" because MPP {0} is
busy
Problem description
{0} - The name of the MPP server.
{1} - The command.
Avaya Aura Experience Portal cannot execute the specified command in the event message
because the MPP is busy.
Proposed Solution
About this task
POMS_00190
Event text MPPs ({0}) did not execute command "{1}"
Problem description
{0} - The names of the MPPs.
{1} - The command.
POMS events
The MPP that was specified in the event message could not execute the command stated in
the message.
Proposed Solution
About this task
POMS_00191
Event text Could not execute command "{1}" because MPP {0} is
not found (probably deleted)
Problem description
{1} - The command
The system could not execute the command that was specified in the event message because
the MPP could not be found.
Proposed Solution
About this task
POMS_00192
POMS_00193
Event text Could not execute command "{1}" for MPP {0} because
the VMPS has not completed initialization sequence
Problem description
{1} - The command.
The system could not execute the specified command that was in the event message for the
MPP because the EPM did not complete the initialization sequence.
Proposed Solution
About this task
POMS_00193
Event text Could not execute command "{1}" for MPP {0} because
the real time database is not initialized
Problem description
{1} - The command.
The system could not execute the specified command that was in the event message for the
MPP because the EPM local database was not initialized.
POMS events
Proposed Solution
About this task
POMS_00194
Event text Could not execute command "{0}" because EPM MPP state manager
is uniitialized
Problem description
{0} - The command.
The system could not execute the command that was specified in the event message because
the EPM MPP stat manage was not initialized.
Proposed Solution
About this task
POMS_00195
Event text Could not execute command "{0}" for all MPPs because
the VMPS has not completed initialization sequence
POMS_00196
Problem description
The system could not execute the command that was specified in the event message for all
the MPPs because the EPM could not complete the initialization sequence.
Proposed Solution
About this task
POMS_00196
Event text Set MPP {0} mode to offline requested
Problem description
[0} - The name of the MPP.
The system has set the MPP mode to Offline.
Proposed Solution
About this task
POMS_00197
Event text Set MPP {0} mode to test requested
POMS events
Problem description
The system has set the MPP mode to Test.
Proposed Solution
About this task
POMS_00198
Event text Set MPP {0} mode to online requested
Problem description
The system has set the MPP mode to Online.
Proposed Solution
About this task
POMS_00199
POMS_00200
Event text Could not set MPP {0} to "{1}" because MPP is in the
incorrect state (must be either Stopped or Not
Responding)
Problem description
{1} - The requested state.
The system could not set the MPP to the requested state because the MPP was in an incorrect
state. The MPP must be in either the Stopped or Not Responding state.
Proposed Solution
About this task
POMS_00200
Event text Could not set MPP {0} mode to "{1}" because MPP is
not found (probably deleted)
Problem description
{1} - The requested state.
The system could not set the MPP to the requested state because the MPP could not be
found.
POMS events
Proposed Solution
About this task
POMS_00201
Event text Could not set MPP {0} mode to "{1}" because the EPM
has not completed initialization sequence
Problem description
{1} - The requested mode
The system could not set the MPP to the requested state because the EPM has not completed
the initialization sequence.
Proposed Solution
About this task
POMS_00202
Event text Start requested for MPPs: {0}
POMS_00203
Problem description
The request to start the MPPs was received.
Proposed Solution
About this task
POMS_00203
Event text Stop requested for MPPs {0}
Problem description
The request to stop the MPPs was received.
Proposed Solution
About this task
POMS_00204
POMS events
Event text Halt requested for MPPs: {0}
Problem description
The request to halt the MPPs was received.
Proposed Solution
About this task
POMS_00205
Event text Restart requested for MPPs: {0}
Problem description
The request to restart the MPPs was received.
Proposed Solution
About this task
POMS_00206
POMS_00206
Event text Reboot requested for MPPs: {0}
Problem description
The request to reboot the MPPs was received.
Proposed Solution
About this task
POMS_00207
Event text Starting MPPs: {0}
Problem description
The system is starting the MPPs.
POMS events
Proposed Solution
About this task
POMS_00208
Event text Stopping MPPs: {0}
Problem description
The system is stopping the MPPs.
Proposed Solution
About this task
POMS_00209
Event text Halting MPPs: {0}
Problem description
POMS_00210
The system is halting the MPPs.
Proposed Solution
About this task
POMS_00210
Event text Restarting MPPs: {0}
Problem description
The system is restarting the MPPs.
Proposed Solution
About this task
POMS_00211
Event text Rebooting MPPs: {0}
POMS events
Problem description
The system is rebooting the MPPs.
Proposed Solution
About this task
POMS_00212
Event text EPM timed out while executing {0} command in {1} milliseconds
Problem description
{0} - The command.
{1} - The time in milliseconds.
The EPM experienced a time out error when executing the requested command within the
specified milliseconds.
Proposed Solution
About this task
POMS_00213
POMS_00214
Event text EPM timed out while executing {0] command for MPP {1}
in {2} milliseconds
Problem description
{0} - The command.
{2} - The time in milliseconds.
The EPM experienced a time out error when executing the requested command for the MPP
within the specified milliseconds.
Proposed Solution
About this task
POMS_00214
Event text Database updates are again successful since the

previously successful poll on
Problem description
The database updates were successful since the last update.
Proposed Solution
About this task
POMS events
POMS_00215
Event text Sending Remove Trunk {2} to {0} with {1} second grace
period
Problem description
{1} - The grace period in seconds.
A command to remove SIP trunk was sent to the specified MPP.
Proposed Solution
About this task
POMS_00216
Event text Null result returned sending Remove Trunk {1} to {0}
Problem description
POMS_00217
The MPP could not process the request to remove a SIP trunk. No error code was returned.
Proposed Solution
Procedure
Restart the MPP if the attempt to process the request continues to fail.
POMS_00217
Event text Error {1} returned sending Remove Trunk {3} to {0}
(Internal description: {2})
Problem description
{1} - The error code that was returned by the MPP.
The MPP encountered an error when processing the request to remove a SIP trunk.
Proposed Solution
Procedure
Restart the MPP if the attempt to process the request continues to fail.
POMS events
POMS_00218
Event text Remove Trunk {1} sent successfully to {0}
Problem description
The MPP successfully processed the command to remove a SIP trunk.
Proposed Solution
About this task
POMS_00219
Event text Failed sending Remove Trunk [2} to {0] with error
{1}
Problem description
POMS_00220

The MPP could not process the command to remove a SIP trunk due to either on of the
following:
The MPP encountered an error when processing the request to remove a SIP trunk.
The requested command to remove a SIP trunk failed to reach the MPP.
Proposed Solution
Procedure
1. Verify that the MPP is running properly.

2. Ensure that the connection between the MPP and the EPM is functioning
properly.
3. Restart the MPP if the MPP is not running or if the connection is not functioning
properly.
POMS_00220
Event text Deleting SIP ({0}) to MPP map for nonexistent MPP {1}
Problem description
{1} - The name of the MPP that does not exist.
This event occurred when the EPM restarted while deleting a SIP trunk.
POMS events
Proposed Solution
Procedure
POMS_00221
Event text MPP {0} has trunks(s) {1} that have not been
configured by EPM
Problem description
{1} - The name of the extraneous trunks.
The EPM could not recognize some of the trunks that were configured on the MPP.
Proposed Solution
Procedure
Restart the MPP.
POMS_00222
POMS_00223
Event text Exception occurred while retrieving Report

Problem description
The EPM local database encountered a problem when it was retrieving reports.
Proposed Solution
Procedure
Reboot the EPM server if this problem occurs frequently.
POMS_00223
Event text Report Configuration appears in transition and is

skipped
Problem description
The report data did not exist in the EPM local database.
Procedure
POMS events
POMS_00224
Event text Report configuration that last changed on {0} was

Problem description
{0} - The date that the report data was last modified.
The system successfully retrieved from the EPM local database the report configuration that
was last modified on the date specified in the event message.
Proposed Solution
About this task
POMS_00225
Event text Report configuration was retrieved from admin

database
Problem description
The system successfully retrieved the default report data from the EPM local database.
POMS_00226
Proposed Solution
About this task
POMS_00226
Event text Report configuration container not defined
Problem description
The report configuration could not be found in the EPM local database. This event generally
occurs when the report data is being updated.
Proposed Solution
Procedure
POMS_00227
Event text Report configuration resource not defined
POMS events
Problem description
The report configuration could not be found in the EPM local database. This event generally
occurs when the report data is being updated.
Proposed Solution
Procedure
POMS_00228
Event text Configuration database initialization failed with

error {0}
Problem description
The EPM local database is either out of service or inaccessible.
Proposed Solution
Procedure
POMS_00229
POMS_00229
Event text Real time database initialization failed with error

{0} (SQL Error: {1})
Problem description
{1} - The SQL error message.
The system could not connect to the MPP real time management database.
Proposed Solution
Procedure
POMS_00230
Event text Configuration database initialization completed

successfully after error {0}
Problem description
POMS events
The system successfully accessed the EPM local database after encountering a few failed
attempts in accessing the database.
Proposed Solution
About this task
POMS_00231
Event text Real time database initialization completed

Problem description
The system successfully accessed the EPM local database after encountering a few failed
attempts in accessing the database.
Proposed Solution
About this task
POMS_00232
Event text Real time database reinitialization failed with

error {0}
POMS_00233
Problem description
The system could not access the EPM local database after it has successfully connected to
it.
Proposed Solution
Procedure
POMS_00233
Event text Real time database reinitialization completed

Problem description
The system successfully accessed the EPM local database again after encountering a few
failed attempts in accessing the database.
Proposed Solution
About this task
POMS events
POMS_00234
Event text Configuration database is now available after error

{0}
Problem description
The system successfully accessed the EPM local database again after encountering a few
Proposed Solution
About this task
POMS_00235
Event text System Settings configuration that last changed on

{0} was retrieved from admin database
Problem description
{0} - The date that the system settings were last modified.
The system successfully retrieved the system settings that were last changed on the date
specified in the event message.
POMS_00236
Proposed Solution
About this task
POMS_00236
Event text System Settings configuration was retrieved from

admin database
Problem description
The system successfully retrieved the system settings from the EPM local database.
Proposed Solution
About this task
POMS_00237
Event text System Settings container not defined
POMS events
Problem description
The system settings could not be found in the EPM local database. This event generally occurs
when the report data is being updated.
Proposed Solution
Procedure
POMS_00238
Event text System Settings resource not defined
Problem description
Proposed Solution
Procedure
POMS_00239
POMS_00240
Event text System Settings appears in transition and is skipped
Problem description
Proposed Solution
Procedure
POMS_00240
Event text Exception occurred while retrieving System Settings

with error "{0}"
Problem description
The EPM local database encountered a problem when retrieving system settings.
Proposed Solution
Procedure
POMS events
POMS_00241
Event text Avaya Voice Browser configuration that last changed

on {0} was retrieved from admin database
Problem description
{0} - The date that the VoiceXML interpreter configuration was last modified.
The VoiceXML interpreter configuration was last modified on the date specified in the event
message.
Proposed Solution
About this task
POMS_00242
Event text Avaya Voice Browser configuration was retrieved from

admin database
Problem description
The default VoiceXML interpreter configuration was successfully retrieved from the EPM local
database.
POMS_00243
Proposed Solution
About this task
POMS_00243
Event text Avaya Voice Browser container not defined
Problem description
The VoiceXML interpreter configuration could not be found in the EPM local database. This
event generally occurs when the report data is being updated.
Proposed Solution
Procedure
POMS_00244
Event text Avaya Voice Browser resource not defined
POMS events
Problem description
Proposed Solution
Procedure
POMS_00245
Event text Avaya Voice Browser appears in transition and is

skipped
Problem description
Proposed Solution
Procedure
POMS_00246
POMS_00247
Event text Exception occurred while retrieving Avaya Voice

Browser with error "{0}"
Problem description
The EPM local database encountered an error when retrieving the VoiceXML interpreter
configuration.
Proposed Solution
Procedure
POMS_00247
Event text External database initialization completed

Problem description
The external report database was operational after recovering from an error.
Proposed Solution
About this task
POMS events
POMS_00248
Event text External database reinitialization failed with error

{0}
Problem description
The system could not access the external report database after it has successfully connected
to it.
Proposed Solution
Procedure
1. Verify that the external report database is running properly.

2. Ensure that the connection information for the external report database is correct.
3. Verify that the database driver has been properly installed.
4. Verify that the Avaya Aura Experience Portal tables have been created in the
external database.
POMS_00249
Event text External database reinitialization completed

POMS_00250
Problem description
The system successfully accessed the external report database again after encountering a
few failed attempts in accessing the database.
Proposed Solution
About this task
POMS_00250
Event text External database reinitialization failed with error

{0}
Problem description
{0} - The error message from the connection attempt.
The system could not access the external report database after it has been successfully
connected to it.
Proposed Solution
Procedure
Verify that the external report database is running properly and that it is accessible.
POMS events
POMS_00251
Event text External database initialization error occurred {0}

("{1}")
Problem description
{0} - The error message from the connection attempt.
{1} - The description of the error message.
The system could not access the external report database after it has been successfully
connected to it.
Proposed Solution
Procedure
POMS_00252
Event text Connected to external database {0} using JDBC driver

{1}
Problem description
{0} - The URL of the external database.
POMS_00253
{1} - The JDBC driver that was configured for the database.
The system was successfully connected to the external database using the JDBC driver that
was specified in the event message.
Proposed Solution
About this task
POMS_00253
Event text Reconnected after failure to external database {0}

using JDBC driver {1}
Problem description
The system was successfully connected to the external database using the JDBC driver that
was specified in the event message after a few failed attempts in accessing the database.
Proposed Solution
About this task
POMS_00254
POMS events
Event text Connected to external database {0} using JDBC

driver {1} failed with error {2}

details
SNMP Trap ID: 17901

Problem description
(2) - The SQL error.
The system could not connect to the external database using the JDBC driver that was
specified in the event message.
Proposed Solution
Procedure

external database.
POMS_00255
Event text Connected to internal database failed with error {0}

(SQL Error: {1})
POMS_00256
Problem description
{0} - The error message that was returned by the JDBC driver.
{1} - The SQL error.
The system could not be connected to the internal database for reporting.
Proposed Solution
Procedure
POMS_00256
Event text Internal database initialization completed

Problem description
{0} - The SQL error from failed attempt.
The system was successfully connected to the internal database for reporting after
encountering an error.
Proposed Solution
About this task
POMS events
POMS_00257
Event text Internal database reinitialization failed with error

{0}
Problem description
{0} - The SQL error returned from failed attempt.
The system could not access the internal database for reporting after it has been successfully
connected to it.
Proposed Solution
Procedure
POMS_00258
Event text Internal database reinitialization completed

Problem description
{0} - The SQL error from failed attempt.
POMS_00259
The system was successfully connected to the internal database for reporting after
encountering an error.
Proposed Solution
About this task
POMS_00259
Event text Real time database initialization failed with

error {0} (SQL Error: {1})

details
SNMP Trap ID: 17903

Problem description
{0} - The error returned from the JDBC driver.
The system could not connect to the EPM local database.
Proposed Solution
Procedure
Reboot the EPM server to restart the EPM and the EPM local database.
POMS events
POMS_00260
Event text Connected to internal database failed with error

{0} (SQL Error: {1})

SNMP Trap ID: 17903

Problem description
The system could not connect to the EPM local database. The OMS will shut down after three
Proposed Solution
Procedure
POMS_00261
Event text Configuration database initialization failed with

error {0}
POMS_00262

details
SNMP Trap ID:17903

Problem description
{0} - The error returned from the EPM local database management.
The system could not connect to the EPM local database. The OMS will shut down after three
Proposed Solution
Procedure
POMS_00262
Event text Could not insert duplicate Avaya Aura Experience

Portal System {0} into external report database
Problem description
{0} - The name of the Avaya Aura Experience Portal system.
The system could not add a second instance of the Avaya Aura Experience Portal name. An
entry of the Avaya Aura Experience Portal system with a different IP address already exists
in the database.
POMS events
Proposed Solution
Procedure
1. Change the name of the Avaya Aura Experience Portal system that you want to
add.
2. Add the new Avaya Aura Experience Portal system again.
POMS_00263
Event text Reattaching Avaya Aura Experience Portal System {0}

to external report database
Problem description
The system was connected to the external database again because there was a duplicated
Avaya Aura Experience Portal name with a matching IP address in the database.
Proposed Solution
About this task
POMS_00264
POMS_00265
Event text Inserting Avaya Aura Experience Portal System {0} to

external report database
Problem description
The system was connected to the external database and was attempting to add the Avaya
Aura Experience Portal system name.
Proposed Solution
About this task
POMS_00265
Event text Error occurred inserting Avaya Aura Experience

Portal System {0} into external report database, SQL
error is {1}
Problem description
The system could not add the Avaya Aura Experience Portal system to the external database
due to a SQL error.
POMS events
Proposed Solution
Procedure

external database.
POMS_00266
Event text Avaya Aura Experience Portal System {0} inserted

into external report database with ID {1}
Problem description
{1} - The external database ID for the Avaya Aura Experience Portal system that was
added.
The system successfully added the Avaya Aura Experience Portal system in to the external
database.
Proposed Solution
About this task
POMS_00267
POMS_00267
Event text Inserting Avaya Aura Experience Portal System {0}

inserted into external report database with ID {1}
Problem description
{1} - The internal database ID for the Avaya Aura Experience Portal system that was
added.
The system was connected to the internal database and was attempting to add the Avaya
Aura Experience Portal system name.
Proposed Solution
About this task
POMS_00268
Event text Error occurred inserting Avaya Aura Experience

Portal System {0} into local database, SQL error is
{1}
Problem description
POMS events

The system could not add the Avaya Aura Experience Portal system to the internal database
due to a SQL error.
Proposed Solution
Procedure
POMS_00269
Event text Avaya Aura Experience Portal ID {0} suspending

access to external report database (all report data
left intact)
Problem description
{0} - TheAvaya Aura Experience Portal system id.
TheAvaya Aura Experience Portal system is no longer connected to the external database,
but all report data is left intact.
Proposed Solution
About this task
POMS_00270
POMS_00270
Event text Avaya Aura Experience Portal ID {0} exiting external

report database (all report data deleted)
Problem description
The Avaya Aura Experience Portal system was not connect to the external database. All the
report data was deleted from the external database.
Proposed Solution
About this task
POMS_00271
Event text Error occurred while deleting report data for Avaya
Aura Experience Portal ID {0}, SQL error is {1}
Problem description
{0} - The Avaya Aura Experience Portal ID that owns the report data.
The system encountered a problem when deleting the report data from the external
database.
POMS events
Proposed Solution
Procedure
POMS_00272
Event text Error occurred while deleting Avaya Aura Experience

Portal System {0} from external report database, SQL
error is {1}
Problem description
{0} - The Avaya Aura Experience Portal ID.
The system encountered a problem when deleting the Avaya Aura Experience Portal system
from the external database.
Proposed Solution
Procedure
POMS_00273
POMS_00274
Event text Error deleting MPPs ({0}) from internal database

with Avaya Aura Experience Portal ID {1}, SQL error
is {2}
Problem description
{0} - The names of the MPPs that were being deleted.
The system encountered a problem when deleting the specified MPPs from the internal
database.
Proposed Solution
Procedure
POMS_00274
Event text Error deleting MPPs ({0}) from external report

database with Avaya Aura Experience Portal ID {1},
SQL error is {2}
Problem description
POMS events
The system encountered a problem when deleting the specified MPPs from the external
database.
Proposed Solution
Procedure
POMS_00275
Event text Error adding MPPs ({0}) from internal database with
Avaya Aura Experience Portal ID {1}, SQL error is {2}
Problem description
The system encountered a problem when adding the specified MPPs to the internal
database.
Proposed Solution
Procedure
POMS_00276
POMS_00276
Event text Error adding MPPs ({0}) from external report

SQL error is {2}
Problem description
The system encountered a problem when adding the specified MPPs to the external
database.
Proposed Solution
Procedure
POMS_00277
Event text Error deleting all MPPs from external report

SQL error is {1}
POMS events
Problem description
The system encountered a problem when deleting the specified MPPs from the external
database.
Proposed Solution
Procedure
POMS_00278
Event text Error retrieving all MPPs from internal database to

insert into external report database for Avaya Aura
Experience Portal ID {0}, SQL error ({2}) is {1}
Problem description
{2} - The operation (Insert or Add Batch).
The system encountered a problem when either retrieving data of the specified MPPs from the
internal database or adding the data to the external database.
If the operation Insert was displayed in the event message, the system encountered a problem
when retrieving data from the internal database.
If the operation Add Batch was displayed, the system encountered a problem when adding the
data to the external database.
POMS_00279
Proposed Solution
Procedure
If the event message is about the:

Insert operation, reboot the EPM server to restart the EPM and the database.
Add Batch operation, verify that the external database is running and is
accessible.
POMS_00279
Event text Error inserting all MPPs into external report

database for Avaya Aura Experience Portal ID {0}, SQL
error is {1}
Problem description
The system encountered a problem when adding all the MPPs to the external database.
Proposed Solution
Procedure
POMS events
POMS_00280
Event text Error deleting applications ({0}) from internal

database with Avaya Aura Experience Portal System ID
{1}, SQL error is {2}
Problem description
{0} - The names of the applications that were being deleted.
The system encountered a problem when deleting the specified Avaya Aura Experience
Portal applications from the internal database.
Proposed Solution
Procedure
POMS_00281
Event text Error deleting applications ({0}) from external

report database with Avaya Aura Experience Portal ID
POMS_00282
Problem description
The system encountered a problem when deleting the specified Avaya Aura Experience
Portal applications from the external database.
Proposed Solution
Procedure
POMS_00282
Event text Error adding applications ({0}) into internal

SQL error is {2}
Problem description
The system encountered a problem when adding the specified Avaya Aura Experience Portal
applications from the internal database.
POMS events
Proposed Solution
Procedure
POMS_00283
Event text Error adding applications ({0}) from external report

database with Avaya Aura Experience Portal System ID
Problem description
The system encountered a problem when adding the specified Avaya Aura Experience Portal
applications from the external database.
Proposed Solution
Procedure
POMS_00284
POMS_00284
Event text Error deleting all applications from external report

database with Avaya Aura Experience Portal System
Avaya Aura Experience Portal System ID {0}, SQL error
is {1}
Problem description
The system encountered a problem when adding all the specified Avaya Aura Experience
Proposed Solution
Procedure
POMS_00285
Event text Error inserting all applications from internal

database to insert into external report database for
Avaya Aura Experience Portal ID {0}, SQL error ({2})
is {1}
POMS events
Problem description
{2} - The operation (Insert or Add Batch).
An SQL error occurred when either retrieving data of the specified Avaya Aura Experience
Portal applications from the internal database or adding the data to the external database.
If the operation Insert was displayed in the event message, the system encountered a problem
when retrieving data from the internal database.
If the operation Add Batch was displayed, the system encountered a problem when adding the
data to the external database.
Proposed Solution
Procedure
If the event message is about the:

Insert operation, reboot the EPM server to restart the EPM and the database.
Add Batch operation, verify that the external database is running and is
accessible.
POMS_00286
Event text Error inserting all applications into external

report database for Avaya Aura Experience Portal
System ID {0}, SQL error is {1}
Problem description
POMS_00287
The system encountered a problem when copying all the specified Avaya Aura Experience
Proposed Solution
Procedure
POMS_00287
Event text Deleting MPPs ({0}) from internal database for Avaya
Aura Experience Portal System ID {1}
Problem description
The MPPs were being deleted from the internal report database.
Proposed Solution
About this task
POMS_00288
POMS events
Event text Deleting MPPs ({0}) from external report database

for Avaya Aura Experience Portal ID {1}
Problem description
The MPPs were being deleted from the external report database.
Proposed Solution
About this task
POMS_00289
Event text Added new MPPs ({0}) into internal database for Avaya
Aura Experience Portal ID {1}
Problem description
The MPPs were being added to the internal report database.
Proposed Solution
About this task
POMS_00290
POMS_00290
Event text Added new MPPs ({0}) into external report database
Problem description
The MPPs were being added to the external report database.
Proposed Solution
About this task
POMS_00291
Event text Deleted applications ({0}) from internal database

Problem description
{0} - The names of the applications.
POMS events
The specified Avaya Aura Experience Portal applications were being deleted from the internal
report database.
Proposed Solution
About this task
POMS_00292
Event text Deleted applications ({0}) from external report database for Avaya Aura
Experience Portal ID {1}
Problem description
The specified Avaya Aura Experience Portal applications were being deleted from the external
report database.
Proposed Solution
About this task
POMS_00293
POMS_00294
Event text Added new applications ({0}) into internal database

for Avaya Aura Experience Portal System ID {1}
Problem description
The specified Avaya Aura Experience Portal applications were being added to the internal
report database.
Proposed Solution
About this task
POMS_00294
Event text Added new applications ({0}) into external report

database for Avaya Aura Experience Portal ID {1}
Problem description
The specified Avaya Aura Experience Portal applications were being added to the external
report database.
POMS events
Proposed Solution
About this task
POMS_00295
Event text Error {0} ("{1}") fetching Avaya Aura Experience

Portal systems
Problem description
{1} - The description of the error.
An error occurred when retrieving the Avaya Aura Experience Portal systems from the
external database.
Proposed Solution
Procedure

external database.
POMS_00296
POMS_00296
Event text Could not retrieve SIP configuration data due to {0},
skipping merge
Problem description
An error occurred when retrieving the SIP configuration data from the EPM local database.
The SIP modifications were not merged.
Proposed Solution
Procedure
POMS_00297
Event text Could not retrieve MPP configuration data due to {0},
skipping merge
Problem description
POMS events
An error occurred when retrieving the MPP configuration data from the EPM local database.
The MPP modifications were not merged.
Proposed Solution
Procedure
POMS_00298
Event text Could not retrieve H.323 configuration data due to

{0}, skipping merge
Problem description
An error occurred when retrieving the H.323 configuration data from the EPM local database.
The H.323 modifications were not merged.
Proposed Solution
Procedure
POMS_00299
POMS_00300
Event text Could not execute command {0} on staggered MPP {1}
because its in the state {2}
Problem description
{0} - The command that was being executed.
(2) - The state of the MPP when the command was requested.
The specified command could not be executed on the staggered list of MPPs. The specified
MPP that was in its specified state was skipped.
Proposed Solution
About this task
POMS_00300
Event text Cancelled {0} command on staggered MPP {1} that is

currently active (Current MPP state is {2})
Problem description
The cancellation of a requested command could not be executed on the specified MPP.
POMS events
Proposed Solution
About this task
POMS_00301
Event text Cancelled {0} command on staggered MPP {1} that is

waiting to be executed
Problem description
The request command was successfully cancelled on the specified MPP.
Proposed Solution
About this task
POMS_00302
Event text Executed {0} command on staggered MPP {1} (Current

MPP state is {2})
POMS_00303
Problem description
The requested command was being executed on the specified MPP, which was on the
staggered list of MPPs.
Proposed Solution
About this task
POMS_00303
Event text Certificate configuration that last changed on {0}

was retrieved from admin database
Problem description
{0} - The date that the certificates were last modified.
The certificates that were modified on the specified date were successfully retrieved from the
EPM local database.
Proposed Solution
About this task
POMS events
POMS_00304
Event text Certificate configuration was retrieved from admin

database
Problem description
The default list of certificates (not the certificates) was successfully retrieved from the EPM
local database.
Proposed Solution
About this task
POMS_00305
Event text Exception occurred while retrieving Certificates

with error "{0}"
Problem description
The EPM local database encountered an error when retrieving certificates.
POMS_00306
Proposed Solution
Procedure
POMS_00306
Event text Default XML handlers & prompts configuration that

last changed on {0} was retrieved from admin database
Problem description
{0} - The date that the certificates were last modified.
The default XML handlers that were last modified on the specified date have been successfully
retrieved from the EPM local database.
Proposed Solution
About this task
POMS_00307
Event text Default XML handlers & prompts configuration was

POMS events
Problem description
The default list of the XML handlers (not the XML handlers) were successfully retrieved from
the EPM local database.
Proposed Solution
About this task
POMS_00308
Event text Exception occurred while retrieving Default XML

handlers & prompts with error "{0}"
Problem description
The EPM local database encountered an error when retrieving the default XML handlers.
Proposed Solution
Procedure
POMS_00309
POMS_00309
Event text Cancelled {0} command on MPP {1} that is currently

active (Current MPP state is {2})
Problem description
The requested command that was being executed on the specified MPP has been cancelled
by an operator. The specified MPP was left in an undetermined state.
Proposed Solution
About this task
POMS_00310
Event text OMS shutdown initiated due to internal request

with reason {0}

SNMP Trap ID: 17903
Associate alarm name QOMS00310
POMS events

Problem description
{0} - The reason for shutting down the OMS.
The OMS was shutting down due to an unrecoverable problem.
If the error "ms timeout reached while waiting for MPP(s)" was displayed in the event message,
the OMS was being shutdown due to a breakdown in the communication between the EPM
and the MPP. The MPP didnt respond, and the EPM could not gain back its control.
Proposed Solution
About this task
For error messages other than "ms timeout reached while waiting for MPP(s)", reboot the EPM
server to restart the EPM and the EPM local database.
If the error "ms timeout reached while waiting for MPP(s)" was displayed in the event message,
do the following:
Procedure
1. Reboot the EPM server to restart the EPM and the EPM local database.
2. Reboot or restart the specified MPP.
POMS_00311
Event text Error updating applications ({0}) in internal

SQL error is {2}
POMS_00312
Problem description
{0} - The list of applications that were being updated.
An error occurred when updating the Avaya Aura Experience Portal applications in the internal
database.
Proposed Solution
Procedure
POMS_00312
Event text Error updating applications ({0}) in external report

SQL error is {2}
Problem description
An error occurred when updating the Avaya Aura Experience Portal applications in the
external database.
POMS events
Proposed Solution
Procedure
POMS_00313
Event text Updated applications ({0}) in internal database for

Avaya Aura Experience Portal System ID {1}
Problem description
The Avaya Aura Experience Portal applications were updated in the internal database.
Proposed Solution
About this task
POMS_00314
Event text Updated applications ({0}) in external report

database for Avaya Aura Experience Portal ID {1}
POMS_00315
Problem description
The Avaya Aura Experience Portal applications were updated in the external database.
Proposed Solution
About this task
POMS_00315
Event text {0} consecutive database errors occurred exceeding

the maximum of {1} while updating the internal
database

details
SNMP Trap ID: 17902

Alarm Codes page.
Problem description
{0} - The routine that generated the error message.
{1} - The number of failed attempts.
There have been too many consecutive errors encountered when updating the internal
database.
No new error messages will be generated until the database is functioning properly.
POMS events
Proposed Solution
Procedure
POMS_00316
Event text {0} consecutive database errors occurred exceeding

the maximum of {1} while updating the external
database

details
SNMP Trap ID: 17902

Alarm Codes page.
Problem description
{0} - The routine that generated the error message.
{1} - The number of failed attempts.
There have been too many consecutive errors encountered when updating the external
database.
No new error messages will be generated until the database is functioning properly.
POMS_00317
Proposed Solution
Procedure
POMS_00317
Event text Internal database updates are again successful since

the last successful attempt on {0}
Problem description
{0} - The date of the last successful update.
The internal database is accessible again since the date of the last successful update.
Proposed Solution
About this task
POMS_00318
Event text External database updates are again successful since

the last successful attempt on {0}
POMS events
Problem description
{0} - The date of the last successful update.
The external database is accessible again since the date of the last successful update.
Proposed Solution
About this task
POMS_00319
Event text Internal command {2} ({1}) executed from MPP {0}
console
Problem description
{1} - The hexidecimal command.
{2} - The description of the command.
A request such as starting or stopping an MPP was sent from the MPP console.
Proposed Solution
About this task
POMS_00320
POMS_00320
Event text Auto-restart of MPP {0} requested because it stopped

and auto-restarted flag set
Problem description
The MPP restarted after it stopped due to the auto restart configuration for the MPP.
Proposed Solution
About this task
POMS_00321
Event text MPP {0} logging attempt to system log failed a total
of {1} times within the last {2} minutes
Problem description
{1} - The number of failed log attempts.
{2} - The time period when consecutive failures occurred.
POMS events
Multiple failed log attempts were logged in a single entry to limit the number of alarms. The
MPP reported logging issues in each poll. \This event occurs when one of the following
happens:
There is a large number of logging attempts from multiple MPPs happening at the same
time.
A networking problem that prevents the MPP from logging to the system log of the system
log is offline.
Proposed Solution
Procedure
1. Verify that the network is functioning properly.

2. Restart the MPP.
3. If the system log is out of service, restart the EPM.
POMS_00322
Event text Illegal SIP Proxy {0} configuration for MPP {1} with
{2} channels with {3} outbound channels
Problem description
{0} - The name of the SIP proxy.
{1} - The number of configured channels.
{2} - The number of outbound channels that were configured.
The channel configuration was not supported by the MPP. This is an internal error.
POMS_00323
Proposed Solution
Procedure
POMS_00323
Event text {0} command on MPP {1} timed out in {2} seconds
Problem description
{0} - The command the was being executed.
{2} - The timeout period.
The specified MPP accepted a command such as start or stop; however, it did not execute the
command within the timeout period.
Proposed Solution
Procedure
1. Try the command again.

2. If the MPP times out again, restart the MPP.
POMS events
POMS_00324
Event text Avaya Aura Experience Portal System System {0}

contains insufficient available slots within
current MPP ID range of {1} - {2}

details
SNMP Trap ID: 17902

Alarm Codes page.
Problem description
{1} {2} - The current MPP ID range.
The system does not have enough slots for the MPP IDs that were specified in the range.
Proposed Solution
About this task
POMS_00325
Event text EPM and 2nd EPM configuration that last changed on
{0} was retrieved from admin database.
POMS_00326
Problem description
{0} - The date that the configuration for both the primary and auxiliary EPM was last
changed.
The configuration that was last changed on the specified date for both the primary and auxiliary
EPM was retrieved from the Avaya Aura Experience Portal database.
Proposed Solution
About this task
POMS_00326
Event text EPM and 2nd EPM configuration was retrieved from
admin database
Problem description
{0} - The date that the configuration for both the primary and auxiliary EPM was last
changed.
The configuration that was last changed on the specified date for both the primary and auxiliary
EPM was retrieved from the Avaya Aura Experience Portal database.
Proposed Solution
About this task
POMS events
POMS_00327
Event text Exception occurred while retrieving EPM and 2nd EPM
Problem description
The system encountered a problem while retrieving configurations for both the primary EPM
and auxiliary EPM.
Proposed Solution
About this task
POMS_00328
Event text EPM {0} did not respond to poll request with error
{1}
Problem description
{0} - The name of the EPM.
The specified EPM did not respond to a poll request.
POMS_00329
Proposed Solution
About this task
POMS_00329
Event text EPM {0} has been marked Not Responding because it
failed to respond to multiple poll requests
Associated alarm Name: QOMS_00329

details
SNMP Trap ID: 17902

Alarm Codes page.
Problem description
The specified EPM is not responding to multiple poll requests.
Proposed solution
Procedure
1. Verify that the auxiliary EPM is running properly and that the certificate has been
accepted.
2. If the auxiliary EPM still doesn't respond, follow the steps below to reauthorize the
primary EPM from the auxiliary EPM.
a) Log in to the auxiliary EPM using the administrator role.
b) Change directory by entering the /opt/Avaya/VoicePortal/Support/
VP-Tools/ command.
POMS events
c) Enter the setup_vpms.php command.
POMS_00330
Event text EPM {0} has again responded to polls since its last
successful poll at {1}
Problem description
{1} - The date and time when the EPM was successfully polled.
The specified EPM is now responding to poll requests since the last successful poll.
Proposed Solution
About this task
POMS_00332
Event text Failed to update MPP IDs in external report database,

with error "{0}"
Problem description
{0} - The SQL error encountered.
POMS_00335
The system failed to update MPP IDs in the external database.
Proposed Solution
Procedure

external database.
POMS_00335
Event text Admin URL {0} and creation time {1} in external
database do not match admin URL {2} and creation
time {3} in internal database. Exiting the
cluster.

details
SNMP Trap ID: 17902

Alarm Codes page.
Problem description
{0} - Avaya Aura Experience Portal system's admin URL stored in external database.
{1} - Avaya Aura Experience Portal system's creation time stored in external database.
{2} - Avaya Aura Experience Portal system's admin URL stored in local database.
{3} - Avaya Aura Experience Portal system's creation time stored in local database.
POMS events
The Avaya Aura Experience Portal system's admin URL and creation time do not match those
stored in the external database. As a result, the Avaya Aura Experience Portal system is
forced to suspend access to the external database.
Proposed Solution
Procedure
Attempt to re-join the external database.
POMS_00338
Event text Could not find Avaya Aura Experience Portal System
{0} in external database. Exiting the external
database.

details
SNMP Trap ID: 17902

Alarm Codes page.
Problem description
{0} - The Avaya Aura Experience Portal system name.
Unable to find the Avaya Aura Experience Portal system in the external database. As a result,
the Avaya Aura Experience Portal system is forced to suspend access to the external
database.
POMS_00340
Proposed Solution
Procedure
Attempt to re-join the external database.
POMS_00340
Event text Table "{0}" is missing required column "{1}" in

external database.

details
SNMP Trap ID: 17902

Problem description
{0} - The name of the table with the missing column.
{1} - The name of the missing column.
A database table is missing a required column.
Proposed Solution
Procedure
Execute the appropriate Avaya Aura Experience Portal database upgrade script to
add the missing column.
POMS events
POMS_00342
Event text Failed retrieving prompt list from MPP "{0}" with
error {1}
Trigger component HttpGetPromptList - retrieves list of application prompts configured at

runtime.
Problem description
{1} - The http or MPP error returned from the request
HTTP error was returned from a request to an MPP for a list of previously downloaded prompts
Proposed Solution
About this task
This problem is generally caused by either an incorrectly configured security certificate, failed
MPP, or an MPP containing a pre-Avaya Aura Experience Portal 5.0 software release.
Procedure
1. Verify that the security certificate is properly accepted.

2. If the MPP has failed, restart or reboot the MPP.
3. If the MPP still fails, contact Avaya support organization.
4. Update the MPP if the MPP contains a previous version of Avaya Aura Experience
Portal software
POMS_00344
POMS_00345
Event text "Sending prompts to {0}" where {0} is the list of

MPPs that are to receive the prompts.
Trigger component New or modified prompts are to be downloaded to the MPP.
Problem description
Proposed Solution
About this task
POMS_00345
Event text "Prompts successfully sent to {0}" where {0} is the

list of MPPs that have successfully received the
prompts.
Trigger component New or modified prompts have been successfully downloaded to the
MPP.
Problem description
Proposed Solution
About this task
POMS events
POMS_00347
Event text Licensing configuration that last changed on {0} was

retrieved from WebLM.
Event level Info
Trigger component Experience Portal Manager.
Problem description
{0} = date changed
Proposed Solution
Procedure
N/A (informational only).
POMS_00348
Event text Application prompt configuration that last changed

on {0} was retrieved from prompt database.
Event level Info
Problem description
{0} = date changed
POMS_00350
Proposed Solution
Procedure
POMS_00350
Event text Video configuration was retrieved from admin

database.
Event level Info
Problem description
{0} = date changed
Proposed Solution
Procedure
POMS_00355
Event text Null pointer exception occurred retrieving {0} from

configuration database during operation {1} with
error {2} and cause {3}
POMS events
Problem description
{0} - Type of data being retrieved.
{1} - The operation being executed.
{2} - Error details.
{3} - Exception details.
A null pointer exception occurred while attempting to retrieve data from the configuration
database. This is an internal error.
Proposed Solution
Procedure
POMS_00356
Event text EPM disk use in the partition(s) of the following

directories has exceeded configured threshold of
{0}%:{1}

details
SNMP Trap ID: 17902

Alarm Codes page.
POMS_00357
Problem description
{0} - The maximum configured threshold.
{1} - Monitored directories whose partitions have exceeded maximum configured threshold.
EPM disk use in the partition(s) of one or more monitored directories has exceeded maximum
configured threshold.
Event logging, audit logging, and report downloads is disabled when the disk space for the
partition(s) exceeds the maximum threshold
Proposed Solution
Procedure
Free up disk space for the partition(s) which have exceeded the maximum threshold,
or increase the maximum configured threshold.
Note:
Event logging, audit logging, and report download is re-enabled once the disk space
reaches the low disk threshold.
POMS_00357

SNMP Trap ID: 17901

directories has exceeded configured low threshold
of {0}%: {1}.
Event level Info
Problem description
{0} = configured low threshold percentage, {1} = partition names
POMS events
Proposed Solution
Procedure
Raise the low threshold level in EPM Settings page, or reduce disk usage by purging
the files that are not required.
POMS_00358
Associate alarm name QOMS_00358

directories has returned below configured low
threshold of {0}%: {1}.
Event level Info
Problem description
{0} = configured low threshold percentage, {1} = partition names
Proposed Solution
Procedure
Chapter 22: PSESM events
PSESM00001
Event name PSESM00001
Event text Network error occurred on CCXML message channel,

error = {0}
Trigger component MPP SessionManager process
Problem description
The connection between the SessionManager and CCXML processes encountered problems.
The CCXML process was either stopping or restarting.
Proposed Solution
Procedure
If the SessionManager cannot establish a connection to the CCXML interpreter, use

one of the following methods to verify that the CCXML interpreter is running:
Review the home page of the MPP Service Menu.
Run the command stat.php on the MPP.
Restart the MPP.
PSESM events
PSESM00002
Event text Network error occurred on VXML message channel,

error = {0}
Problem description
The connection between the SessionManager and vxmlmgr processes encountered problems.
The vxmlmgr process was either stopping or restarting.
Proposed Solution
Procedure

Restart the MPP.
PSESM00003
Event text Connect to CCXML process message channel failed with

error {0}
PSESM00004
Problem description
The SessionManager could not connect to the CCXML process message channel. The
CCXML process is not running.
Proposed Solution
Procedure

Restart the MPP.
PSESM00004
Event text Connect to VXML process message channel failed with

error {0}
Problem description
The SessionManager could not connect to the vxmlmgr process message channel. The
vxmlmgr process is not running.
PSESM events
Proposed Solution
Procedure

Restart the MPP.
PSESM00005
Event text Unable to get CCXML message channel {0}, error = {1}
Problem description
{0} - The CCXML message channel.
The SessionManager could not get the channel object for the CCXML. This problem occurred
due to one of the following reasons:
The MPP installation was not completed successfully.
The SessionManager could not create or open a special file in the directory
$AVAYA_MPP_HOME/tmp.
Proposed Solution
Procedure
1. Reinstall the MPP.

PSESM00006
Note:
Session and CCXML tracing to Finest.
PSESM00006
Event text Unable to register CCXML message channel {0}, error

= {1}
Problem description
{0} - The CCXML message channel.
The SessionManager could not register the callback method for the CCXML channel object.
This problem occurred due to one of the following reasons:
The SessionManager encountered configuration problems.
Proposed Solution
Procedure

Note:
PSESM events
PSESM00007
Event text Unable to get VXML message channel {0}, error = {1}
Problem description
{0} - The VXML message channel.
The SessionManager could not get the channel object for the vxmlmgr. This problem occurred
due to one of the following reasons:
The SessionManager could not create or open a special file in the directory
$AVAYA_MPP_HOME/tmp.
Proposed Solution
Procedure

Note:
PSESM00008
PSESM00009
Event text Unable to register VXML message channel {0}, error =

{1}
Problem description
{0} - The VXML message channel.
The SessionManager could not register the callback method for the VXML channel object. This
problem occurred due to one of the following reasons:
The SessionManager encountered configuration problems.
Proposed Solution
Procedure

Note:
PSESM00009
Event text Unable to send message to CCXML channel, error = {0}
Problem description
PSESM events
The SessionManager could not send a message to the CCXML message channel. The
connection between the SessionManager and CCXML processes encountered problems. The
CCXML process was either stopping or restarting.
Proposed Solution
Procedure

Restart the MPP.
PSESM00010
Event text Unable to send message to VXML channel, error = {0}
Problem description
The SessionManager could not send a message to the VXML message channel. The
connection between the SessionManager and VXML processes encountered problems. The
VXML process was either stopping or restarting.
Proposed Solution
Procedure

PSESM00011

Restart the MPP.
PSESM00011
Event text ASR connect to server {0} failed to initialize with

error {1}
Problem description
{0} - The name of the Media Processing Platform (ASR) server.
The ASR provider could not connect to the ASR server due to invalid configurations or a
problem on the ASR server.
Proposed Solution
Procedure
established.
PSESM events
PSESM00012
Event text ASR provider error {0} with description {1}
Problem description
The ASR provider could not connect to the ASR server due to invalid configurations or a
problem on the ASR server.
Proposed Solution
Procedure
established.
PSESM00013
Event text Timeout waiting for ASR Server {0} to initialize.
PSESM00014
Problem description
The SessionManager encountered time out while waiting for the ASR provider to initialize. The
timeout problem occurred due to invalid configurations or a problem on the ASR server.
Proposed Solution
Procedure
established.
PSESM00014
Event text TTS connect to server {0} failed to initialize with

error {1}
Problem description
{0} - The name of the Text-to-Speech (TTS) (TTS) server.
The TTS provider could not connect to the TTS server due to invalid configurations or a problem
on the TTS server.
PSESM events
Proposed Solution
Procedure
1. On the EPM, verify that the TTS server configurations are correct.
2. Verify that the TTS server is running properly.
3. Verify that the network connection between the TTS server and the MPP is
established.
4. Verify that you can connect to the TTS server from the MPP.
5. On the TTS server, verify that you can ping the MRCP Network Address that was
PSESM00015
Event text Timeout waiting for TTS Server {0} to initialize.
Problem description
The SessionManager encountered timeout while waiting for the TTS provider to initialize. The
timeout problem occurred due to invalid configurations or a problem on the TTS server.
Proposed Solution
Procedure
established.
PSESM00016
4. Verify that you can connect to the TTS server from the MPP.
5. On the TTS server, verify that you can ping the MRCP Network Address that was
PSESM00016
Event text Unable to create telephony play record endpoint,

telephony error {0}
Problem description
The SessionManager could not allocate a telephony endpoint to perform play and record
operations. This event occurred because the MPP ran out of network resources and therefore
could not create sockets.
Proposed Solution
Procedure
On the EPM, ensure that the configurations and IP addresses for the VoIP and H.323
connections are correct.
PSESM00017
Event text Unable to create telephony speech dialog object,

telephony error {0}
PSESM events
Event level Warning message. No alarm is generated.
Problem description
The SessionManager could not allocate a telephony endpoint to perform streaming operations
to the voice server. This event occurred because the MPP ran out of network resources and
therefore could not create sockets.
Proposed Solution
Procedure
On the EPM, ensure that the configurations and IP addresses for the VoIP and H.323
connections are correct.
PSESM00018
Event text Could not start ASR session on Server {0}, error =
{1}
Problem description
The SessionManager could not start the ASR session because the ASR provider encountered
the problems.
PSESM00019
Proposed Solution
Procedure
1. Review the log reports on the EPM for additional ASR provider errors.
2. Review the SessionManager process logs by using the Logs page on the MPP
Service Menu.
PSESM00019
Event text Unable to create ASR port, attempted to connect to

the following servers: {0}
Associate alarm Name: QSESM00019

details
SNMP Trap ID: 17076

Alarm Codes page.
Problem description
The SessionManager could not create an ASR port object for the operation. The ASR provider
encountered the problems.
Proposed Solution
About this task
Review the log reports on the EPM for additional ASR provider errors.
Review the SessionManager process logs by using the Logs page on the MPP Service
Menu.
PSESM events
PSESM00020
Event text Could not start TTS session on Server {0}, error =
{1}
Problem description
The SessionManager could not start the TTS session because the TTS provider encountered
the problems.
Proposed Solution
Procedure
1. Review the log reports on the EPM for additional TTS provider errors.
Service Menu.
PSESM00021
Event text Unable to create TTS port object, failed with

error {0}

details
SNMP Trap ID: 17078
PSESM00022

Problem description
The SessionManager could not create a TTS port object for the operation. The TTS provider
encountered the problems.
Proposed Solution
Procedure
1. Review the log reports on the EPM for additional TTS provider errors.
Service Menu.
PSESM00022
Event text Caught Exception {0} in {1} with context: {2}
Problem description
{0} - The exception.
{1} - The location that the error occurred.
{2} - Information such as the Session ID or the Call ID.
The SessionManager encountered an internal error. The error is not fatal, but it might affect a
callers session.
PSESM events
Proposed Solution
Procedure
1. If you encounter this error frequently:

a) Reproduce the problem by setting the SessionManager tracing to Finest, and
generating the log file.
b) Contact Avaya Technical Support.
2. If you encounter this error infrequently and the error does not affect the operation
of the Avaya Aura Experience Portal system, do the following:
a) Gather the event information in the SessionManager logs on the MPP.
b) Forward the logs to Avaya Technical Support for future solutions.
PSESM00023
Event text Caught Exception {0} in main, exiting

SessionManager.
Problem description
{0} - The exception that was caught in Main.
The SessionManager is not operational because it encountered a problem when it was
running.
The MPP System Manager (mpp daemon) will automatically restart the SessionManager
process.
Proposed Solution
Procedure
PSESM00024
Note:
Before contacting Avaya Technical Support, try to reproduce the problem by setting
the SessionManager tracing to Finest, and generating the log file.
PSESM00024
Event text Connection to (CCXML,VXML) process, failed with

error {0}
Event level Error message. No alarm is generated.
Problem description
The SessionManager could not connect to either the CCXML or the vxmlmgr process during
initialization because either the CCXML, the vxmlmgr, or both processes were not running
properly.
Proposed Solution
Procedure
1. Verify that both the CCXML and the vxmlmgr processes are running using one of
the following methods:
2. Restart the MPP.
PSESM events
PSESM00025
Event text Error has occurred with connection to process {0}

with error {1}, unable to process calls.
Problem description
{0} - Either the CCXML or the VXML process.
Active calls ended because the connection between the SessionManager and the CCXML or
the VXML has not been established. This problem occurred because either the CCXML, the
vxmlmgr, or both processes were not running properly.
Proposed Solution
Procedure
2. Restart the MPP.
PSESM00026
Event text Unable to reconnect to (CCXML,VXML) process,

SessionManager is exiting.
PSESM00027
Problem description
The SessionManager is exiting because it could not establish a connection with either the
CCXML or the vxmlmgr. This problem occurred because either the CCXML, the vxmlmgr, or
both processes were not running properly.
Proposed Solution
Procedure
2. Restart the MPP.
PSESM00027
Event text Unable to create path {0}
Problem description
{0} - The path that could not be created.
The SessionManager could not create a directory path for a file due to permission problem or
a disk error, such as out of disk space.
PSESM events
Proposed Solution
Procedure
1. Verify that the SessionManager has the correct level of file and directory
permissions.
2. Verify that disk space is sufficient.
PSESM00028
Event text Error {0} opening file {1}.
Problem description
{1} - The name of the log file.
The SessionManager could not open a log file due to permission problem or a disk error, such
as out of disk space.
Proposed Solution
Procedure
permissions.
PSESM00029
PSESM00029
Event text Error {0} writing to file {1}.
Problem description
{1} - The name of the log file.
The SessionManager could not write to a log file due to a permission problem or a disk error,
such as out of disk space.
Proposed Solution
Procedure
permissions.
PSESM00030
Event text ASR provider {0} failed to load with error {1}
PSESM events
Problem description
{0} - The name of the ASR provider.
The SessionManager could not load the shared object from the $AVAYA_MPP_HOME/bin/
mrcpasr.so file because the file was missing or permissions for the file were set
incorrectly.
Proposed Solution
Procedure
1. Verify that the file $AVAYA_MPP_HOME/bin/mrcpasr.so exists and that the

permissions for the file are set correctly.
Note:
Session and CCXML tracing to Finest. Generate the log file and contact Avaya
Technical Support.
PSESM00031
Event text ASR provider {0} error, 'CreateProvider' returned

NULL
Problem description
The SessionManager could not create the ASR provider object from the $AVAYA_MPP_HOME/
bin/mrcpasr.so file because this is an invalid ASR provider shared object.
PSESM00032
Proposed Solution
Procedure

Note:
PSESM00032
Event text Invalid ASR provider {0}, unable to find

'CreateProvider' symbol
Problem description
The SessionManager could not create the ASR provider object from the
$AVAYA_MPP_HOME/bin/mrcpasr.so file because this is an invalid ASR provider shared
object.
Proposed Solution
Procedure

PSESM events
Note:
PSESM00033
Event text ASR provider {0} failed to initialize with error {1}
Problem description
The SessionManager could not initialize the ASR provider.
Proposed Solution
Procedure
Service Menu.
PSESM00034
Event text TTS provider {0} failed to load with error {1}
PSESM00035
Problem description
{0} - The name of the TTS provider.
The SessionManager could not load the TTS shared object from the file $AVAYA_MPP_HOME/
bin/mrcptts.so because the file was missing or permissions for the file were set
incorrectly.
Proposed Solution
Procedure
1. Verify that the file $AVAYA_MPP_HOME/bin/mrcptts.so exists and that the

Note:
Technical Support.
PSESM00035
Event text TTS provider {0} error, 'CreateProvider' returned

NULL
Problem description
PSESM events
The SessionManager could not create the TTS provider object from the file
$AVAYA_MPP_HOME/bin/mrcptts.so because this is an invalid TTS provider shared
object.
Proposed Solution
Procedure

Note:
PSESM00036
Event text Invalid TTS provider {0}, unable to find

Problem description
The SessionManager could not create the TTS provider object from the file
$AVAYA_MPP_HOME/bin/mrcptts.so because this is an invalid TTS provider shared
object.
Proposed Solution
Procedure

PSESM00037
Note:
PSESM00037
Event text TTS provider {0} failed to initialize with error {1}
Problem description
The SessionManager could not initialize the TTS provider.
Proposed Solution
Procedure
2. Review the SessionManager process logs using the Logs page on the MPP Service
Menu.
Note:
setting the Session and TTS tracing to Finest, and generating the log file.
PSESM events
PSESM00038
Event text Telephony provider {0} failed to load with error {1}
Problem description
{0} - The name of the telephony provider.
{1} - Provides information for the event or alarm.
The SessionManager could not load the telephony provider shared object from the
$AVAYA_MPP_HOME/bin/VoIP.so file because the file was missing or permissions for the
file were set incorrectly.
Proposed Solution
Procedure
1. Verify that the file $AVAYA_MPP_HOME/bin/VoIP.so exists and that the

2. Restart the MPP.
Note:
Technical Support.
PSESM00039
PSESM00040
Event text Telephony provider {0} error, 'CreateProvider'

returned NULL
Problem description
The SessionManager could not create the telephony provider object from the file
$AVAYA_MPP_HOME/bin/VoIP.so because this is an invalid telephony provider shared
object.
Proposed Solution
Procedure

Note:
PSESM00040
Event text Invalid Telephony provider {0}, unable to find

Problem description
PSESM events
The SessionManager could not create the telephony provider object from the file
$AVAYA_MPP_HOME/bin/VoIP.so because this is an invalid telephony provider shared
object.
Proposed Solution
Procedure

Note:
PSESM00041
Event text Telephony MakeCall to CalledURI {0} failed with

error {1}
Problem description
{0} - The failed URI.
The telephony provider reported an error.
Proposed Solution
Procedure
1. Review log reports on the EPM for additional telephony provider errors.
PSESM00042
Note:
setting the Session tracing to Finest, and generating the log file.
PSESM00042
Event text Playfile with file {0} failed on EndPoint {1} with
error {2}.
Problem description
{1} - The name of the endpoint.
Proposed Solution
Procedure
Note:
Session tracing to Finest and Telephony tracing to Finer. Generate the log
file and contact Avaya Technical Support.
PSESM events
PSESM00043
Event text Record with file {0} failed on EndPoint {1} with
error {2}
Problem description
{1} - The name of the endpoint.
Proposed Solution
Procedure
Note:
Session tracing to Finest and Telephony tracing to Finer. Generate the log
file and contact Avaya Technical Support.
PSESM00044
Event text TTS operation failed with error {0} on TTS Server {1}
PSESM00045
Problem description
The TTS provider reported an error.
Proposed Solution
Procedure
1. Review log reports on the EPM for additional TTS provider errors.
Note:
Session and ASR tracing to Finest. Generate the log file and contact Avaya
Technical Support.
PSESM00045
Event text ASR SetParameter failed with error {0} on ASR Server
{1}
Problem description
The ASR provider reported an error.
PSESM events
Proposed Solution
Procedure
1. Review log reports on the EPM for additional ASR provider errors.
Note:
Technical Support.
PSESM00046
Event text LoadGrammar for grammar {0} failed with error {1} on
ASR Server {2}
Problem description
{0} - The failed grammar.
Proposed Solution
Procedure
PSESM00047
Note:
Technical Support.
PSESM00047
Event text ActivateGrammar of Grammar {0} failed with error {1}

on ASR Server {2}
Problem description
{0} - The failed grammar.
Proposed Solution
Procedure
Note:
Technical Support.
PSESM events
PSESM00048
Event text StartRecognition failed with error {0} on ASR Server

{1}
Problem description
Proposed Solution
Procedure
Note:
Technical Support.
PSESM00049
Event text StartDtmfCollection failed with error {0}
PSESM00050
Problem description
Proposed Solution
Procedure
Note:
setting the Session tracing to Finest and Telephony tracing to Finer, and
PSESM00050
Event text No application configured for call with DNIS {0}
Problem description
{0} - The DNIS number.
The SessionManager could not locate a speech application that was configured with the called
number or DNIS.
PSESM events
Proposed Solution
Procedure
1. On the EPM, verify that the DNIS is configured correctly with a speech
application.
2. On the EPM, review the Call Detail report to verify that the DNIS used for the
application is the correct number recorded for the call.
PSESM00051
Event text Unable to initialize status shared memory segment,

error code {0}.
Problem description
The SessionManager could not create a shared memory segment that was used by the System
Manager for reporting status to the EPM. This problem occurred due to permission errors.
The SessionManager starts, but the MPP heartbeat does not capture station or call
information.
Proposed Solution
Procedure

PSESM00052
Note:
setting the Session tracing to Finest, and generating the log file.
PSESM00052
Event text Unable to add station {0} on switch {1}, AddStations

failed with error {2}
Problem description
{0} - The name of the H.323 connection on the EPM.
{1} - The name of the private branch exchange (PBX).
The SessionManager could not add a station to the PBX because the addition of stations
exceeded the maximum number of stations allowed on the PBX.
Proposed Solution
Procedure
1. Go to the EPM interface.

2. On the H.323 Connections Web page, verify that the Phone Number and
Password configurations are correct.
3. On the MPP Server Web page, check the number that you entered in the Maximum
Simultaneous Calls field.
4. Ensure that the number of stations that you plan to add to the PBX does not exceed
the number that you entered in the Maximum Simultaneous Calls field.
PSESM events
5. If the configuration on the EPM interface is correct, compare the Port Distribution
Web page on the EPM with the Telephony Web page on the MPP Service Menu to
ensure that the information on both pages is in sync.
PSESM00053
Event text Remove station {0} on switch {1} failed with error
{2}
Problem description
{0} - The name of the station.
{1} - The name of the PBX.
The SessionManager could not remove a station from the PBX because either the station was
not added or it was already removed.
Proposed Solution
Procedure

2. On the H.323 Connections Web page, verify that the Phone Number and
Password configurations are correct.
3. On the Port Distribution Web page, verify that the port that you want to use for the
station is not currently allocated to an MPP.
4. If the port is currently allocated to an MPP, go to the MPP Service Menu.
5. Review the Telephony Resources to verify whether this port is in use or not.
6. If the port is in use, restart the MPP on the System Monitor Web page.
PSESM00054
PSESM00054
Event text SIP connections not supported with this telephony

provider.
Problem description
This event is triggered when a SIP connection is configured on the EPM while an H.323
provider is configured on the MPP.
The H.323 provider on the MPP only supports configurations of an H.323 connection.
Proposed Solution
Procedure
1. Remove the SIP connection.

2. Run the script setEPVoip.sh on the MPP to change the MPP telephony provider
from H.323 to SIP.
PSESM00055
Event text Error {0} trying to create {1} for path {2}.
Problem description
{0}- The error message.
PSESM events
{1} - The file name.

{2} - The name of the path.
The system encountered a problem when trying to create a file for the specified path.
Proposed Solution
About this task
PSESM00056
Event text CreateCall failed with error {0}
Problem description
The telephony provider reported a problem.
Proposed Solution
Procedure
Note:
setting the Session and tracing to Finest and Telephony tracing to Finer, and
PSESM00057
PSESM00057
Event text Invalid SessionHandle {0} for CreateCall
Problem description
{0} - Invalid SessionHandle details.
The SessionManager encountered an internal problem.
Proposed Solution
Procedure
Note:
the Session tracing to Finest, and generating the log file.
PSESM00058
Event text Session Manager is initialized and ready.
Problem description
The SessionManager is initialized and ready. No AddStation has been called.
PSESM events
Proposed Solution
About this task
PSESM00059
Event text Session Manager is shutting down with reason {0} and
grace period {1}
Problem description
{0} - The reason for shutting down.
{1} - The grace period that was configured on the system.
The SessionManager is shutting down.
Proposed Solution
About this task
PSESM00060
Event text Attempting to reconnect to (CCXML,VXML) app

process.
PSESM00061
Problem description
The SessionManager is trying to reconnect to either the CCXML or the vxmlmgr process.
Proposed Solution
About this task
PSESM00061
Event text Connection to (CCXML,VXML) process has been

reestablished, processing call now.
Problem description
The SessionManager has reestablished connection with either the CCXML or the vxmlmgr
process. The SessionManager is processing calls.
Proposed Solution
About this task
PSESM00062
Event text Add Stations complete, total stations {0}
PSESM events
Problem description
{0} - The total number of added stations.
The SessionManager completed an AddStation request and reported the total number of
added stations.
Proposed Solution
About this task
PSESM00063
Event text Remove Stations complete, total stations {0}
Problem description
{0} - The total number of deleted stations.
The SessionManager completed a RemoveStation request and reported the total number of
deleted stations.
Proposed Solution
About this task
PSESM00064
PSESM00064
Event text TTS provider error {0} with description {1}
Problem description
The TTS provider encountered a problem while trying to connect to the TTS server. This
problem occurred due to an invalid configuration or a problem on the TTS server.
Proposed Solution
Procedure
1. On the EPM, verify that the TTS configurations are correct.

2. Ensure that the TTS server is running.
PSESM00065
Event text Caught Exception {0} during initialization,

SessionManager cannot start.
PSESM events
Problem description
{0} - The exception caught during initialization.
The SessionManager encountered a problem during initialization. The SessionManager could
not run.
Proposed Solution
Procedure
Note:
the Session tracing to Finest, and generating the log file.
PSESM00066
Event text Telephony Subsystem Error: All Stations Out-Of-

Service.
Associate alarm name QSESM00066

Alarm Codes page.
Problem description
The MPP could not take incoming calls because all stations assigned to the MPP were out of
service.
PSESM00067
Proposed Solution
Procedure

2. On the Port Distribution Web page, identify the ports that have been assigned to
the MPP.
3. Ensure that the private branch exchange (PBX) and the MPP are communicating
properly.
4. On the H.323 Connections Web page, verify that the configurations for the IP
Address, Phone Numbers, Passwords, and ports for the PBX are correct.
5. On the VoIP Web page, verify that the VoIP Network Address configured for the
MPP is correct.
6. Verify that the PBX is running properly.
PSESM00067
Event text Unable to add trunk {0}, AddTrunk failed with error
{1}
Problem description
The SIP connection cannot be added. This event is triggered when multiple SIP trunks are
being configured on the MPP. Avaya Aura Experience Portal 3.0.1 supports only one SIP
trunk.
Proposed Solution
Procedure
PSESM events
2. On the SIP Connections Web page, remove additional SIP connections that are
configured on the EPM.
PSESM00068
Event text Fetch error attempting to access application {0}
Associate alarm details Name: QSESM00068

SNMP Trap ID: 17901

Problem description
The CCXML or VXML browser encountered an error when trying to download a page from the
application specified in the event message. An event is generated for each application page.
The event is sent to the EPM only when application changes occur or when the MPP is
restarted.
Proposed Solution
Procedure
1. From the EPM, review events that were generated by the CCXML Browser, VXML
Browser, or SessionManager around the same time that this event was
generated.
2. For additional information, review the following log files:
$AVAYA_MPP_HOME/logs/process/SessMgr
$AVAYA_MPP_HOME/logs/process/CXI
PSESM00070
$AVAYA_MPP_HOME/logs/process/VB
PSESM00070
Event text Application errors occurred for application {0}

{1} {2}

details
SNMP Trap ID: 17901

Problem description
The CCXML or VXML browser encountered an error when executing a CCXML or VXML
application.
Proposed Solution
Procedure
1. From the EPM, review events that were generated by the CCXML Browser, VXML
Browser, or SessionManager around the same time that this event was
generated.
2. For additional information, review the following log files:
$AVAYA_MPP_HOME/logs/process/SessMgr
$AVAYA_MPP_HOME/logs/process/CXI
PSESM events
$AVAYA_MPP_HOME/logs/process/VB
PSESM00071
Event text CCXML or VXML timeout event occurred for session ID

{0}
Problem description
The CCXML or vxmlmgr process could not respond to the SessionManager within an expected
time frame. The SessionManager will terminate the session. This happens when the CCXML
or vxmlmgr process encounters a problem when executing an application.
Proposed Solution
About this task
If this event occurs frequently, do the following:
Procedure
1. Enable the following tracing:

CCXML Browser = Finest
SessionManager = Finest
Voice Browser Platform = Finest
All other Voice Browser categories = Finer
All other categories = Off
2. When the event occurs again, collect log files that are generated close to the time
when this event is generated to avoid roll over of the log files. If you expect roll over
to occur, modify the MPP Settings for the Trace Logger to increase the Log File
Maximum Size and Number of Logs to Retain.
PSESM00072
3. Send the log files to Avaya Technical Support.
Proposed Soution
About this task
If this event occurs infrequently and the error does not affect the operation of the Avaya Aura
Experience Portal System, do the following:
Procedure
1. From the MPP, gather the event information in the SessionManager, CXI, and VB
logs.
2. Send the logs files to Avaya Technical Support.
PSESM00072
Event text Timeout waiting for release of session resources,

session ID {0}, resource map {1}
Problem description
{1} - The session resources.
The Session Manager was unable to release certain session resources at the end of a call
because the resources specified in the event message were not released within an expected
time frame. The SessionManager terminated the specified resources.
PSESM events
Proposed Solution
About this task
If this event occurs frequently, do the following:
Procedure
1. Enable the following tracing:

CCXML Browser = Finest
SessionManager = Finest
Voice Browser Platform = Finest
All other Voice Browser categories = Finer
All other categories = Off
2. When the event occurs again, collect log files that are generated close to the time
when this event is generated to avoid roll over of the log files. If you expect roll over
to occur, modify the MPP Settings for the Trace Logger to increase the Log File
Maximum Size and Number of Logs to Retain.
3. Send the log files to Avaya Technical Support.
Proposed Solution
About this task
If this event occurs infrequently and the error does not affect the operation of the Avaya Aura
Experience Portal system, do the following:
Procedure
1. From the MPP, gather the event information in the SessionManager, CXI, and VB
logs.
2. Send the logs files to Avaya Technical Support.
Proposed Solution
About this task
Contact Avaya Technical Support if this problem persists.
PSESM00073
PSESM00073
Event text Place Call Failed due to all channels busy.

details
SNMP Trap ID: 17901

Problem description
{1} - The session resources.
No outbound channels were available when the SessionManager placed an outbound call
through the telephony provider. For example, the bridge transfer or the CCXML application
attempted to make an outbound call.
Proposed Solution
About this task
If all of the channels are configured as Inbound/Outbound, increase the number of telephony
ports on your Avaya Aura Experience Portal system.
If there is a mix of Inbound-Only ports and Inbound/Outbound ports, do the following:
Procedure
1. Review the call volume on the Avaya Aura Experience Portal system.
2. Determine if there are inbound ports available.
3. If there are inbound ports available, change some of the Inbound-Only ports to
Inbound/Outbound ports.
PSESM events
PSESM00074
Event text Place Call Failed for Outcall web service due to all
channels busy, application {0}.
Problem description
{0} - The name of the application that was specified in the outcall request.
The SessionManager rejected a VXML outcall request to place an outbound call because all
outbound channels are in use. If there are more than one MPP in the Avaya Aura Experience
Portal system, the EPM will route the outbound request to another MPP.
Proposed Solution
About this task
If this error occurs frequently and the Outcall request fails, consider adding more ports to the
Avaya Aura Experience Portal system.
PSESM00075
Event text Invalid Trunk configuration downloaded for trunk

{0}, channels = {1}, {2}
Event level Error Event. No alarm is generated.
Problem description
{0} - The EPM name for the trunk.
{1} - The number of channels for the trunk.
PSESM00076
{2} - The number of outbound channels for the trunk.

Session Manager detected invalid settings for the number of channels for the SIP trunk.
Proposed Solution
About this task
The EPM is designed to prevent invalid configuration for a SIP Connection.
If this error occurs, do the following:
Procedure
1. Delete the SIP connection on the EPM.

2. Add the SIP connection again on the EPM.
3. Contact Avaya Technical Support if disconnecting and reconnecting the SIP
connection does not resolve the problem.
4. Create a database backup for the Avaya Aura Experience Portal system.
5. Send the database backup to Avaya Technical Support for analysis.
PSESM00076
Event text "SharedUUI - UUI from application {0} [{1}] too large
for Call ID {2}, UCID {3}, Max size {4}"
Event level Warning event. No alarm is generated
Problem description
{0} - The EPM name for the application.
{1} - The Shared UUI string that was set by the application.
{2} - The Call ID for the outbound call.
{3} - The UCID for the call.
{4}- The maximum UUI length.
The combination of both the UUI/AAI that was set by the application and the UCID has
exceeded the Maximum UUI Length that was configured on the Applications page on the
PSESM events
EPM. If the encoded Shared UUI exceeds the maximum UUI length, the MPP will first drop the
UCID unless the UCID was set by the application. If the maximum UUI length is still exceeded,
then the SIP UUI Header is left empty. Functions such as a transfer can still be performed.
Proposed Solution
Procedure
1. From the EPM, go to Applications.

2. Click the name of the application.
3. Click Advanced Parameters.
4. Review the value of Maximum UUI Length. This value is dependent on the data
length that is supported on your network. Avoid setting this value to a value that is
greater than what the network can support. Otherwise the data will be lost.
5. Review the Transport UCID in Shared Mode field. If this field is enabled, ensure
that the application is taking this length into account. Verify that the application is
properly setting the UUI/AAI so that the maximum UUI length is not exceeded.
PSESM00077
Event text SharedUUI - UUI from application {0} [{1}] in invalid

format for Call ID {2}
Problem description
{0} - The EPM name for the application.
{1} - The Shared UUI string that was set by the application.
{2} - The Call ID.
The AAI or UUI data set by an application has invalid format. When this error occurs, no AAI/
UUI data can be sent in the SIP message. But functions such as a transfer can still be
performed.
PSESM00078
Proposed Solutions
When an application is configured with an Operation Mode set to Shared UUI, the data format
of the UUI/AAI should be set to <ID1>,<Data1>;<ID2>,<Data2>. If the data is improperly
formatted, the SessionManager cannot encode the data. The data cannot be sent in the SIP
message.
Procedure
1. If the SessionManager should not be operating in the Shared UUI mode, do the
following:
a) From the EPM, go to Applications.
b) Click the name of the application.
c) Click Advanced Parameters.
d) Verify that the Operation Mode field is set to Service Provider.
e) If the Operation Mode field is set to Service Provider, contact Avaya Technical
Support.
2. If the SessionManager should be operating in the Shared UUI mode, do the
following:
a) Verify that the data of the UUI/AAI set by the application has the format of
<ID1>,<Data1>,<ID2>,<Data2>.
b) Review the trace messages in the SessionManager log files for additional
information. If tracing for SessionManager was not enabled, reproduce the
problem with SessionManager tracing set to Finest.
PSESM00078
Event text Network Service (dialog) URL failed security pattern

match URL: [{0}] Pattern: [{1}]
Problem description
{0} - The application URL that was passed on to the SIP invite.
PSESM events
{1} - The Dialog URL Pattern that was used to verify the application URL.
You might encounter this event if the applications that are configured on the EPM have a value
of Yes in the Network Media Service field and a regular expression value in the optional
Dialog URL Pattern field. This event is logged when the application URL that was passed on
to the SIP invite fails to match the security pattern. In this case, the VXML URI that was
specified for the application in the EPM is used instead of the URL that was passed on to the
SIP invite.
Proposed Solutions
Procedure
1. Validate that the Avaya Aura Experience Portal system is not being improperly
used. The Dialog URL Pattern field is provided as a security measure to prevent
a SIP invite that runs invalid applications on your Avaya Aura Experience Portal
system.
2. If the application URL is valid, verify that the value entered in the Dialog URL
Pattern field is a proper regular expression that matches your application URL.
PSESM00089

Event text Unable to create session, max threshold of {0}
reached.
Event level Minor
Trigger component MPP
Problem description
{0} = max session threshold
PSESM00090
Proposed Solutions
Procedure
PSESM00090

Event text Could not establish a connection to the following
application server(s): {0}
Event level Minor
Trigger component MPP
Problem description
{0} = application server(s) the MPP was unable to connect to.
Proposed Solutions
Procedure
Check the application server(s) in question and determine why a connection could not
be established.
PSESM00091
PSESM events
Event text Connection to the following application server(s) has been

reestablished: {0}.
{0} = application servers which have reconnected.
Proposed Solution
About this task
Chapter 23: PSNMP events
PSNMP_I001
Event name PSNMP_I001
Event text Critical alarms are present on the EPM.
Trigger component SNMP Agent
Problem description
Unacknowledged critical alarms are present on the EPM.
Proposed Solution
Procedure
1. From the EPM, go to Alarm Manager.

2. Resolve condition causing the alarm.
3. Retire all the Critical alarms.
PSNMP_I002
Event text Major alarms are present on the EPM.
Problem description
Unacknowledged major alarms are present on the EPM.
PSNMP events
Proposed Solution
Procedure

PSNMP_I003
Event text Minor alarms are present on the EPM.
Problem description
Unacknowledged minor alarms are present on the EPM.
Proposed Solution
Procedure

PSNMP_I004
Event text No alarms are present on the EPM. Status: Green.
PSNMP_I005
Problem description
No alarms are present on the EPM. Status: Green.
Proposed Solution
Procedure
PSNMP_I005
Event text Error occurred while trying to retrieve alarms.

Description: {0}
Problem description
Error occurred while trying to retrieve alarms.
{0} - Description
Proposed Solution
Procedure
PSNMP events
PSNMP_E001
Event name PSNMP_E001
Event text SNMP Agent has encountered an error while sending

notification to the EPM. Error Message: {0}
Problem description
SNMP Agent has encountered an error.
See Event text for details.
{0} - Error Message
Proposed Solution
Procedure
Please contact Avaya support.
PSNMP_E002
Event text SNMP Agent failed to add new operation from XML to
storage array.
Problem description
SNMP Agent failed to add new operation from XML to storage array.
PSNMP_E003
Proposed Solution
Procedure
There is possibly an error in the $AVAYA_EPM_HOME/SNMP/AvLoadMibInit.xml

file. Please contact Avaya support.
PSNMP_E003
Event text SNMP Agent failed to add new application from XML to
storage array.
Problem description
SNMP Agent failed to add new application from XML to storage array.
Proposed Solution
Procedure
There is possibly an error in the $AVAYA_EPM_HOME/SNMP/AvLoadMibInit.xml

file . Please contact Avaya support.
PSNMP_E004
Event text Failed to update SNMP Agent Configuration
Trigger Component SNMP Agent
PSNMP events
Problem description
Failed to update SNMP Agent Configuration
Proposed Solution
About this task
SNMP Agent configuration values read from the Avaya Aura Experience Portal database are
invalid.
Procedure
1. Verify the SNMP Agent settings are correct.

2. If the problem persist then please contact Avaya support.
PSNMP_E005
Event text Failed to retrieve Agent Configuration. Error

Message: {0}
Problem description
Failed to retrieve Agent Configuration. {0} - Error Message
Proposed Solution
Procedure
PSNMP_E006
PSNMP_E006
Event text SNMP Agent query returned no results. Error Message:

{0}
Problem description
SNMP Agent query returned no results. {0} - Error Message
Proposed Solution
Procedure
Verify the SNMP Agent settings are correct. If the problem persists, please contact
Avaya support.
PSNMP_E007
Event text SNMP Agent has encountered an error while loading the
Avaya Load MIB. Error Message: {0}
Problem description
SNMP Agent has encountered an error while loading the Avaya Load MIB.
{0} - Error Message
PSNMP events
Proposed Solution
Procedure
PSNMP_E008
Event text SNMP Agent has encountered an exception while determining the
hostname of MPP/Aux EPM. Error Message: {0}
Problem description
SNMP Agent has encountered an exception while determining the hostname of MPP/Aux .
EPM. {0} - Error Message
Proposed Solution
Procedure
1. Please verify the configured Aux EPM / MPP have a valid hostname or IP
address.
2. Please contact Avaya support.
PSNMP_E009
Event text SNMP Agent has encountered an SQL Exception. Error

Message: {0}
PSNMP_E011
Problem description
SNMP Agent has encountered an SQL Exception.
{0} - Error Message
Proposed Solution
Procedure
PSNMP_E011
Event name Name:PSNMP_E011
Event text Failed at SUM download operation, Return Code =

{0}
Associate alarm Name: QSNMP_E011

details
SNMP Trap ID: 17902

Alarm Codes page.
Problem description
{0} - The return code from the failed operation. The SUM download has failed.
PSNMP events
Proposed Solution
Procedure
Retry the operation.
PSNMP_E012
Event text Failed at SUM upgrade operation, Return Code =

{0}
Associate alarm details Name: QSNMP_E012

SNMP Trap ID: 17902

Problem description
{0} - The return code from the failed operation. The SUM upgrade has failed.
Proposed Solution
Procedure
Retry the operation.
PSNMP_W001
PSNMP_W001
Event name PSNMP_W001
Event text SNMP Agent has encountered an error while loading the
Avaya Load MIB. Message: {0}
Problem description
SNMP Agent has encountered an error while loading the Avaya Load MIB.
{0} - Message.
Proposed Solution
Procedure
PSNMP_W002
Event text SNMP Agent has encountered an error while retrieving

the Server host name.
Problem description
SNMP Agent has encountered an error while retrieving the Server host name.
PSNMP events
Proposed Solution
Procedure
1. Verify if the system has a valid hostname or IP address.

2. Contact Avaya support.
PSNMP_W003
Event text SNMP Agent has encountered an error while sending an

NMS type SNMP notification. Message: {0}
Problem description
SNMP Agent has encountered an error while sending an NMS type SNMP notification. {0} -
Message
Proposed Solution
Procedure
1. Verify SNMP Destination configurations on the EPM.

PSNMP_W004
PSNMP_W005
Event text SNMP Agent has encountered an error while trying to

send an SNMP request or accepting an SNMP response.
Message: {0}
Trigger Component SNMP Agent
Problem description
SNMP Agent has encountered an error while trying to send an SNMP request or accepting an
SNMP response. {0} - Message
Proposed Solution
About this task
SNMP Agent configuration values read from the Avaya Aura Experience Portal database are
invalid.
Procedure
1. Make sure the SNMP Agent is up and running.

2. Make sure the community name used is correct.
3. Contact Avaya support.
PSNMP_W005
Event text NMP Agent Getstatus has encountered an error.

Message: {0}
Problem description
SNMP Agent Getstatus has encountered an error. {0} - Message
PSNMP events
Proposed Solution
Procedure
1. Verify that the EPM service on EPM is running.

PSNMP_W006
Event text SNMP Agent download has failed to start. Message: {0}
Problem description
SNMP Agent download has failed to start.
{0} - Message
Proposed Solution
Procedure
PSNMP_W007
Event text SNMP Agent download failed to retrieve download or

upgrade status. Message: {0}
PSNMP_W008
Problem description
SNMP Agent download failed to retrieve download status.
{0} - Message
Proposed Solution
Procedure
PSNMP_W008
Event text SNMP Agent has failed during the download process.
Message: {0}
Problem description
SNMP Agent has failed to stop the download or the upgrade process while deleting a file.
{0} - Message
Proposed Solution
Procedure
PSNMP_W009
PSNMP events
Event text SNMP Agent has encountered an error while finding/

reading property file. Message: {0}
Problem description
SNMP Agent has encountered an error while finding/reading property file.
{0} - Message
Proposed Solution
Procedure
PSNMP02601
Event name PSNMP02601
Event text SNMP: INADS Notification has been sent to {0},

Severity: {1}, Event Message: {2}
Trigger component SNMP traps
Problem description
{0} - The protocol transport type and servername (or IP address) where the notification was
sent.
{1} - The severity of the alarms that caused this notification to be sent, where {1} can be MIN
for minor, MAJ for major, or CRITICAL for critical alarms.
{2} - The text associated with the alarm that caused this notification to be generated.
SNMP notification has been successfully sent to an INADS (SSG) type of configured
destination.
PSNMP02602
Proposed Solution
About this task
PSNMP02602
Event text SNMP: NMS Notification has been sent to {0},

Problem description
{0} - The protocol transport type and server name (or IP address) where the notification was
sent.
SNMP notification has been successfully sent to an NMS type of configured destination.
Proposed Solution
About this task
PSNMP02603
PSNMP events
Event text SNMP: Failed to send INADS Notification to {0},

Problem description
{0} The protocol transport type and server name (or IP address) where the notification was
sent.
The Avaya Aura Experience Portal system could not send an SNMP Notification to an INADS
(SSG) type of configured destination.
Proposed Solution
Procedure
1. Verify that the configuration for this SNMP trap destination is correct.
The information to verify includes server name or IP address, transport type, port
number, SNMP version, and community and security strings.
2. Verify that the configuration on the destination device matches the configuration on
the Avaya Aura Experience Portal system. Also verify that the destination device
is operating correctly.
PSNMP02604
Event text SNMP: Failed to send NMS Notification to {0},

PSNMP02605
Problem description
sent.
The Avaya Aura Experience Portal system could not send an SNMP notification to an NMS
type of configured destination.
Proposed Solution
Procedure
PSNMP02605
Event text Sending Test alarm Notification
Associate alarm details Name: QSNMP02605

SNMP Trap ID: 17205

PSNMP events
Problem description
The Avaya Aura Experience Portal system is sending test alarm notification to all configured
destinations.
Proposed Solution
Procedure

2. Retire all the test alarms.
PSNMP02606
Event text SNMP: INADS Notification has been sent to {0}, All
Alarms have been cleared, Event Message: {1}
Problem description
sent.
{1} - The message.
An INADS notification has been sent to a destination. Avaya Aura Experience Portal clears
all the alarms.
Proposed Solution
About this task
P_AMS_0300
P_AMS_0300
Event name P_AMS_0300
Associated alarm Q_AMS_0300
Event text Internal Component Shutdown
Trigger component Session Controller (SC)
Problem description
The Avaya Media Server platform has been shutdown.
Proposed Solution
About this task
Start the Avaya Media Server platform.
LSNMP01003
Event name LSNMP01003
Event text SNMP: Failed to send INADS Notification to {0},

Problem description
{0} The protocol transport type and server name (or IP address) where the notification was
sent.
The Avaya Aura Experience Portal system could not send an SNMP Notification to an INADS
(SSG) type of configured destination.
PSNMP events
Proposed Solution
Procedure
LSNMP01006
Event name LSNMP01006
Event text SNMP: INADS Notification has been sent to {0}, All
Alarms have been cleared, Event Message: {1}
Problem description
sent.
{1} - The message.
An INADS notification has been sent to a destination. Avaya Aura Experience Portal clears
all the alarms.
Proposed Solution
About this task
Chapter 24: PSYSM events
PSYSM00001
Event name PSYSM00001
Event text MPP System Manager initialization of mgt library

failed with error {0} for config file {1}.
Associate alarm Name: QSYSM00001

details
SNMP Trap ID: 17026

Alarm Codes page.
Trigger component MPP System Manager issues
Problem description
{1} - The name of the configuration file.
The MPP system configuration file was corrupted or contained XML syntax errors.
No alarm can be generated because the System Manager process, which is responsible for
sending events to the Experience Portal Manager (EPM), could not be started.
This error event could not be sent to the EPM. The event will be logged in the MPP process
log for the System Manager in the directory $AVAYA_MPP_HOME/logs/process/SysMgr.
PSYSM events
Proposed Solution
Procedure
Review the log file $AVAYA_MPP_HOME/tmp/mgtlib.mppsysmgr.out for

configuration file errors.
PSYSM00002
Event text MPP System Manager initialization failed with

error {0} for config file {1}.

details
SNMP Trap ID: 17027

Alarm Codes page.
Problem description
The MPP System Manager could not complete the initialization of its internal subsystems.
sending events to the EPM, could not be started.
PSYSM00003
Proposed Solution
About this task
The events that occurred prior to this event described the problems that generated this
event.
Procedure
Review the following directories for events that occurred before this error event:
$AVAYA_MPP_HOME/logs/process/SysMgr
$AVAYA_MPP_HOME/tmp/mgtlib.mppsysmgr.out
PSYSM00003
Event text MPP System Manager cannot access config file {1} due
to error {0}.
Problem description
{0) - The error message.
The MPP System Manager could not access the required MPP configuration file.
sending events to the EPM, could not be started.
PSYSM events
Proposed Solution
Procedure
Ensure that the configuration file $AVAYA_HMPP_HOME/config/mppconfig.xml

exists and that the avayavp user has read access permissions to this configuration
file.
PSYSM00004
Event text Cannot create message object for {0} due to error
{1}.
Event level Error event or Warning event. No alarm is generated.
Problem description
{0} - The component for which the message object cannot be created.
The MPP System Manager could not allocate an interprocess communication object.
Proposed Solution
Procedure
1. If the error code is 12, there is insufficient memory to perform the object
allocation.
2. If the error code is any other number, an internal error occurred.
PSYSM00005
PSYSM00005
Event text Cannot register message callbacks for {0} due to

error {1}.
Problem description
{0} - The name of component.
The MPP System Manager could not complete the initialization of an interprocess
communication object. This is an internal error.
Proposed Solution
Procedure
Note:
the Management tracing to Finest, and generating the log file.
PSYSM00006
Event text Cannot accept message connection from {0} due to

error {1}.
PSYSM events
Problem description
{0} - The name of component.
The MPP System Manager could not initialize the Linux interprocess communication
subsystem. The System Manager could not accept commands from the MPP Service Menu
or perform diagnostic command lines. This is an internal error.
Proposed Solution
Procedure
Note:
PSYSM00007
Event text Cannot publish MPP configuration data; {0} due to

error {1}.
Problem description
{0} - Configuration data details.
The MPP System Manager could not access the file $AVAYA_MPP_HOME/config/
globalparams. The file contained global parameter settings that were required for local MPP
processes.
PSYSM00008
Proposed Solution
Procedure
1. Stop the MPP.

2. Delete the $AVAYA_MPP_HOME/config/globalparams file.
3. Ensure that the $AVAYA_MPP_HOME/config directory has read/write
permissions.
4. Restart the MPP.
PSYSM00008
Event text MPP startup aborted; process {0} failed to start

due to error {1}.

details
SNMP Trap ID: 17033

Problem description
The process named in the event message could not start. The MPP startup was aborted
because StopOnFail was configured for the process named in the event message.
PSYSM events
Proposed Solution
Procedure
1. On the EPM, review the log report to identify events that occurred before this fatal
event. The prior events describe the process failures.
2. On the MPP, review the process log for the process named in the event message
for additional event and trace messages.
PSYSM00009
Event text During MPP startup, process {0} failed to start

due to error {1}.
Associate alarm details Name: QSYSM00009

SNMP Trap ID: 17034
Event level Error event. Minor alarm generated.
Problem description
{0} - The process that failed.
The MPP process could not start.
Proposed Solution
Procedure
1. Review the file $AVAYA_MPP_HOME/config/mppconfig.xml.

2. Identify the executable for the listed MPP process.
PSYSM00010
3. Ensure that the executable of the MPP process has the correct path and correct
executable privileges.
PSYSM00010
Event text Failed to execute system {0} due to error {1}.
Problem description
{0} - The system command that could not be executed.
The MPP System Manager could not process the Reboot or Halt command.
Proposed Solution
Procedure
1. On the MPP, type ps -ef | grep mppmon .

2. Ensure that the mppmon process is running.
3. If the mppmon process is not running, review the /var/log/messages file to
identify errors that caused the mppmon to exit.
4. Reboot or halt the MPP from the command line on the MPP.
PSYSM00011
Event text An unknown command {0} was issued from the MMS.
PSYSM events
Problem description
{0} - Details of the unknown command.
The MPP System Manager could not process commands that were sent from the EPM, MPP
Service Menu, or diagnostic command line. This is an internal error.
Proposed Solution
Procedure
Note:
PSYSM00012
Event text The command {0} issued from the MMS was ignored
because the MPP was in the wrong running state.
Problem description
{0} - Details of the command.
The MPP System Manager could not process commands that were sent from the EPM, MPP
Service Menu, or diagnostic command line. This is an internal error.
PSYSM00013
Proposed Solution
Procedure
Wait for the current MPP operation to complete before sending a new command.
PSYSM00013
Event text The command {0} issued from the MMS was ignored
because the MPP requires further configuration.
Problem description
{0} - Details of the command.
The MPP System Manager could not process the requested command because the required
configuration parameter was not downloaded.
Proposed Solution
Procedure
Download the MPP configuration parameters before sending commands.
PSYSM00014
PSYSM events
Event text Failed to send a message {0} to {1} due to error

{2}.
Problem description
{0} - The message sent.
{1} - The process to which the message was sent.
The MPP System Manager could not send a message to the process listed in the event
message. This is an internal error.
Proposed Solution
Procedure
Note:
PSYSM00015
Event text Failed to issue command {0} to process {1} due to

error [2}.
Problem description
{0} - The command issued.
{1} - The process to which the command was sent.
PSYSM00016

The MPP System Manager could not send a message to the process listed in the event
message. This is an internal error.
Proposed Solution
Procedure
Note:
PSYSM00016
Event text Failed to respond to MMS heartbeat request due to

error [1}.
Problem description
The MPP System Manager could not respond to a heartbeat request that was sent from the
MMS Web service. This is an internal error.
Proposed Solution
Procedure
PSYSM events
Note:
PSYSM00017
Event text Failed to create process {0} due to error {1}.

SNMP Trap ID: 17041

Problem description
{0} - The process that could not be started.
The MPP System Manager could not start the process that was listed in the event message.
Proposed Solution
Procedure
1. Review the $AVAYA_MPP_HOME/config/mppconfig.xml file.

2. Identify the executable for the listed MPP process.
3. Ensure that the executable of the MPP process has the correct path and correct
executable privileges.
PSYSM00018
PSYSM00018
Event text Failed to send signal {0} to process {1} due to

error {2}.

details
SNMP Trap ID: 17042

Problem description
{0} - The failed signal.
{1} - The process to which the failed signal was sent.
The MPP System Manager could not stop the process that was listed in the event message.
Proposed Solution
Procedure
1. If the process continues to run after the MPP System Manager sends the Stop
signal, stop the MPP.
2. If the process named in the event message cannot be stopped from the command
line, reboot the MPP.
PSYSM events
PSYSM00019
Event text Unexpected exception {0} occurred in {1}.
Problem description
{0} - The exception details.
{1} - The operation.
The MPP System Manager could not complete the operation listed in the event message. This
is an internal error.
Proposed Solution
Procedure
Note:
PSYSM00020
Event text MPP Process {0} stopped sending keep-alive messages.

Terminating the process.
PSYSM00021
Problem description
{0} - The MPP process that stopped sending keep-alive messages.
The MPP System Manager terminated the process because the process was not responding.
The MPP System Manager restarts the process if the maximum number of restart attempts
has not been exceeded. This is an internal error.
Proposed Solution
Procedure
1. On the EPM, review log reports for additional errors that might have been reported
by the process named in the event message.
2. On the MPP, review logs for the process named in the event message for additional
event or trace messages in the directory $AVAYA_MPP_HOME/logs/process.
PSYSM00021
Event text MPP Process {0} stopped unexpectedly. Restarting the

process.
Problem description
{0} -The MPP process that stopped unexpectedly.
The MPP System Manager restarts an MPP process because the process was terminated
unexpectedly and the maximum number of restart attempts has not been exceeded. This is
an internal error.
Proposed Solution
Procedure
PSYSM events
3. On the MPP, review core files from the process named in the event message in the
directory /tmp/core.
4. Contact Avaya Technical Support if you cannot correct the problem after reviewing
the log and core files.
Note:
Before contacting Avaya Technical Support, collect all of the logs and core
files.
PSYSM00022
Event text MPP Process {0} stopped unexpectedly. Restart

count of {1} exhausted.

details
SNMP Trap ID: 17045

Problem description
{0} - The process that stopped unexpectedly.
{1} - The maximum number of restart attempts.
The MPP System Manager could not restart an MPP process because the process was
terminated unexpectedly and the maximum number of restart attempts has been exceeded.
This is an internal error.
PSYSM00023
Proposed Solution
Procedure
3. On the MPP, review core files from the process named in the event message in the
directory /tmp/core.
4. Contact Avaya Technical Support if you cannot correct the problem after reviewing
the log and core files.
Note:
Before contacting Avaya Technical Support, collect all of the logs and core
files.
PSYSM00023
Event text MPP Process {0} initialization failed with error

{1}.

details
SNMP Trap ID: 17046

Problem description
{0} - The process that could not be initialized.
PSYSM events
The MPP System Manager could not complete internal initialization for the process named in
the event message. The named process could not be managed or run by the System
Manager.
Proposed Solution
Procedure
1. Review error logs for the process in the file $AVAYA_MPP_HOME/logs/process/

SysMgr.
2. Identify errors that occurred prior to this fatal event.
PSYSM00024
Event text Memory allocation failure during {0}.
Problem description
{0} - Detailed information about the operation.
The MPP System Manager could not allocate sufficient memory for the operation.
Proposed Solution
About this task
Follow the steps below to correct the problem:
Procedure
1. From the EPM interface, stop the MPP.

2. Reboot the MPP.
PSYSM00025
PSYSM00025
Event text MPP configuration failure in {0}, configuration data

is empty.
Problem description
{0} - The configuration command that failed.
The MPP System Manager could not process the configuration command because the
command did not contain any configuration data.
Proposed Solution
About this task
PSYSM00026
Event text MPP Cpu use has reached {0} percent, exceeding
the configured threshold of {1} percent.

SNMP Trap ID: 17049
Problem description
{0} - Percentage that the MPP CPU usage has reached.
PSYSM events
{1} - The maximum percentage that is allowed.

The MPP server CPU usage has exceeded the maximum configured threshold.
Proposed Solution
Procedure
1. Conduct test calls to ensure that the performance of the speech application has not
been affected negatively.
2. If you frequently receive this event, the MPP CPU usage has reached or exceeded
its full capacity.
PSYSM00027
Event text MPP Memory use has reached {0} percent, exceeding
the configured threshold of {1} percent.

SNMP Trap ID: 17050
Problem description
{0} - The percentage that the MPP memory usage has reached.
{1} - The maximum percentage that is allowed.
The MPP server memory usage has exceeded the maximum configured threshold.
Proposed Solution
Procedure
PSYSM00028
2. If you frequently receive this event, the MPP Memory usage has reached or
exceeded its full capacity.
PSYSM00028
Event text MPP filesystem {0} disk use has reached {1}
percent, exceeding the configured threshold of {2}
percent.

details
SNMP Trap ID: 17051

Alarm Codes page.
Problem description
{0} - The filesystem on the MPP.
{1} - The percentage that the MPP disk usage has been reached.
{2} - The maximum percentage of disk usage that can be reached.
The MPP server disk usage has exceeded the maximum configured threshold.
Proposed Solution
Procedure
2. If you frequently receive this event, the MPP Disk usage has reached or exceeded
its full capacity.
PSYSM events
PSYSM00029
Event text The MPP process {0} cannot be stopped in its current
state {1}.
Problem description
{0} - The process that cannot be stopped.
{1} - The current state of the process.
The MPP System Manager cannot stop a process because the process is not in a running
state.
Proposed Solution
Procedure
1. If the process is in a running state and cannot be stopped, stop the MPP.
2. If the process cannot stop after you have stopped the MPP, review the System
Manager log file $AVAYA_MPP_HOME/logs/process/SysMgr to identify errors
that are associated with this process.
3. If you cannot find other errors that are associated with this process, reboot the
MPP.
PSYSM00030
Event text The MPP process {0} reports it has entered a degraded
state.
PSYSM00031
Problem description
{0} - Process that entered the Degraded state.
The process listed in the event message is not operating at full capacity.
Proposed Solution
Procedure
1. Stop and restart the MPP.

2. If the process that was degraded is the SessionManager, review the port distribution
on the EPM to ensure that all configured ports are in service.
3. Check the Automated Speech Recognition (ASR) or Text-to-Speech (TTS) (TTS)
server configurations for reported problems.
4. If the process that was degraded is vxmlmgr, verify the status of all the application
servers to ensure that they are operating properly.
PSYSM00031
Event text The MPP process {0} reports it has entered the
fatal state. Will stop/restart all MPP processes.

details
SNMP Trap ID: 17902

Alarm Codes page.
PSYSM events
Problem description
{0} - Process that reported the Fatal state.
The communication between one or more MPP processes failed. The MPP stops and restarts
to restore full functionality.
This error can occur with either one of the following situations:
If the error event PSESM00026 occurs, the SessionManager enters a Fatal state and the
MPP processes will restart.
If the number of out-of-service telephony ports reaches the Fatal threshold (with error
event PTELE00036) and the ports stay out-or-service for five minutes, the
SessionManager process enters the Fatal state and the MPP processes will restart.
Proposed Solution
Procedure
PSYSM00032
Event text MPP System Manager restarting after abnormal

shutdown.
Problem description
The MPP System Manager stopped unexpectedly and restarted automatically after it
stopped.
This problem might have been caused by a power outage.
PSYSM00033
Proposed Solution
Procedure
1. On the MPP, identify core files for mppsysmgr in the directory /tmp/core.
2. If core files exist, use the getmpplogs.sh script to collect core and log files.
Note:
For information on how to use the getmpplogs.sh script, see Troubleshooting
Avaya Avaya Aura Experience Portal 4.1.
PSYSM00033
Event text MPP cpu use ({0} percent) has fallen below the
configured low threshold of {1} percent.
Problem description
{0} - The percentage of the MPP CPU usage.
{1} - The minimum configured threshold for CPU usage.
The MPP CPU usage has returned to normal after exceeding the maximum configured
threshold.
This event only occurs after the event PSYSM00026.
Proposed Solution
About this task
PSYSM events
PSYSM00034
Event text MPP memory use ({0} percent) has fallen below the
Problem description
{0} - Percentage of the MPP memory usage.
{1} - Minimum configured threshold for memory usage.
The MPP memory usage has returned to normal after exceeding the maximum configured
threshold.
Proposed Solution
About this task
PSYSM00035
Event text MPP filesystem {0} disk use {1} percent has fallen
below the configured low threshold of {2} percent.
Problem description
{0} - The filesystem on the MPP.
PSYSM00036
{1} - The percentage of the MPP disk usage.

{2} - The minimum configured threshold for disk usage.
The MPP disk has returned to normal after exceeding the maximum configured threshold.
Proposed Solution
About this task
PSYSM00036
Event text New MPP command {0} in state {1} - new state = {2}
Event level Information event requested by the EPM. No alarm is generated.
Problem description
{0} - The command generated by the EPM.
{1} - The current state of the MPP.
{2} - The state that the MPP will be in after the EPM command completes.
The EPM sent a command to the MPP System Manager through the MmsServer web
service.
Proposed Solution
About this task
PSYSM events
PSYSM00037
Event text New MPP command {0} in state {1} - new state = {2}
(invoked from MPP command line interface)
Problem description
{0} - The command generated by the EPM.
{1} - The current state of the MPP.
{2} - The state that the MPP will be in after the EPM command completes.
The system administrator invoked a command to the MPP System Manager through the MPP
command line interface.
For example, a command line can be running the script start.php.
Proposed Solution
About this task
PSYSM00038
Event text Error {0} downloading document {1} to {2}
Problem description
PSYSM00039
{1} - The URL of the document.

{2} - The directory to which the document was copied.
The System Manager could not download the specified document from the EPM. The
document is an application error handler file for the CCXML or VXML application.
Proposed Solution
Procedure
PSYSM00039
Event text Successfully downloaded document {0} to {1}
Problem description
{0} - The URL of the document.
{1} - The directory to which the document was copied.
The document was downloaded successfully as specified in the event message.
Proposed Solution
About this task
PSYSM events
PSYSM00040
Event text Failed to write certificate file {0}
Problem description
{0} - The name of the file that could not be written.
The System Manager could not save the SES certificate file to the local server. If the MPP and
SES are configured for TLS communications, the MPP might not be able to establish SIP
connections.
Proposed Solution
Procedure
1. Check permissions on existing certificate files in the directory

$AVAYA_MPP_HOME/web/mpp.crt.
2. Remove existing certificate files ses*.pem.
Proposed Solution
Procedure
PSYSM00041
PSYSM00041
Event text Failed to install certificate file {0}
Problem description
{0} - The command that failed.
The System Manager could not install the MPP/application server certificate file. This certificate
file must be installed through an openssl hash-link file in order for the MPP to establish a TLS
connection with the application server.
Proposed Solution
About this task
Procedure
1. Remover the existing application certificate and the link to the certificate.
Proposed Solution
Procedure
PSYSM events
PSYSM00042
Event text Execution of handler directory cleaning script {0}

failed with error {1}
Problem description
{0} - The name of the script.
The System Manager could not run the script that cleans the VXML/CCXML error handler
directory. The script is used to clean deprecated handler files. It does not affect handlers that
are being downloaded.
Proposed Solution
About this task
Procedure
1. On the MPP, go to the directory $AVAYA_MPP_HOME/web/handlers.

2. Verifier file permissions for these handler files.
Proposed Solution
Procedure
PSYSM00043
PSYSM00043
Event text Failure attempting to retrieve signed certificate

from authority : {0}
Problem description
{0} - The URL of the authority on the EPM.
The System Manager could not retrieve a signed MPP/SES certificate from the authority
service that is running on the EPM. The MPP/SES cannot establish a TLS connection for
communication.
Proposed Solution
About this task
Procedure
1. From the EPM, restart the EPM service using the command service epm
restart.
Proposed Solution
Procedure
PSYSM events
PSYSM00044
Event text MPP System Manager starting with resource limits {0}
Problem description
{0} - The list of system resources and the limit values.
This event can be used for debugging purpose. The event message displays system resources
and processes that the MPP System Manager uses and starts.
Proposed Solution
About this task
PSYSM00045
Event text Network configuration error for interface {0} : {1}
Problem description
{0} - The network interface name. For example, eth0.
{1} - Description of the error.
The MPP detected a potential network configuration or performance problem. For example,
the network is running at half-duplex. Network problems might cause performance or call
quality issues on the MPP.
PSYSM00046
Proposed Solution
Procedure
1. Use the LINUX command ethtool or ifconfig to verify network configuration

on the MPP and to identify network errors. Use the ethtool command to modify
network configuration.
2. Verify that network configuration on other network switches or remote servers, such
as the speech servers, that are used by the MPP are properly configured.
PSYSM00046
Event text Failed to delete certificate {0} : error {1}
Problem description
{0} - The name of the certificate.
The MPP System Manager encountered a problem when deleting an old certificate from the
MPP. Although having old certificates on the MPP should not impact the operation of the MPP,
old certificates might pose a security risk.
Proposed Solution
About this task
To remove an old certificate:
Procedure
1. From the EPM, stop the MPP.

2. On the MPP, stop the MPP and httpd services by using the /sbin/service mpp
stop and /sbin/service httpd stop commands.
PSYSM events
3. Remove the certificate file that was specified in the error message.
4. Start the MPP and httpd services by using the /sbin/service mpp start
and /sbin/service httpd start commands.
5. From the EPM, start the MPP.
PSYSM00047
Event text Failed to uninstall certificate {0} : error {1}
Problem description
{0} - The name of the certificate.
The MPP System Manager encountered a problem when uninstalling an old certificate from
the MPP. Although having old certificates on the MPP should not impact the operation of the
MPP, old certificates might pose a security risk.
Proposed Solution
About this task
To remove an old certificate:
Procedure
1. From the EPM, stop the MPP.

2. On the MPP, stop the MPP and httpd services by using the /sbin/service mpp
stop and /sbin/service httpd stop commands.
3. Remove the link that was specified in the error message.
4. Start the MPP and httpd services by using the /sbin/service mpp start
and /sbin/service httpd start commands.
PSYSM00048
5. From the EPM, start the MPP.
PSYSM00048
Event text Network interface {0} is {1}
Event level Information or error event. No alarm is generated.
Problem description
{0} - The name of the network interface. For example, eth0.
{1} - The network status.
If this is an Information event, positive network changes occurred. For example, the network
interface is UP or the network is now running full-duplex.
If this is an Error event, negative network changes occurred. For example, the network interface
is down.
Proposed Solution
About this task
If this is an Information event, no corrective action is required.
If this is an Error event, do the following:
Procedure
1. Use the LINUX command ethtool or ifconfig to verify network configuration

on the MPP and to identify network errors. Use the ethtool command to modify
network configuration.
2. Verify that network configuration on other network switches or remote servers, such
as the speech servers, that are used by the MPP are properly configured.
PSYSM events
PSYSM00049
Event text Cannot stop all processes. MPP Reboot needed.
Problem description
The system could not successfully stop the MPP processes. Before the MPP can be
successfully started, the system must be rebooted.
Proposed Solution
Procedure
1. Use the stat.php command to observe the processes that could not be
stopped.
2. Collect all the MPP logs.
3. Reboot the MPP server.
4. If Auto Restart is not configured for the MPP, start the MPP from the EPM.
5. Verify the MPP is properly answering calls.
6. Send the collected logs to Avaya Technical Support for analysis.
PSYSM00050
Event text MPP logging disk partition usage reached high

threshold. Trace logging disabled.
PSYSM00051
Problem description
The system has detected that the disk usage for MPP logging has reached the high threshold
level. No more trace logging will be added until the disk usage drops below the low threshold
level.
Proposed Solution
Procedure
Reduce the MPP Trace levels.
Proposed Solution
Procedure
Reduce the MPP log file maximum log file size and/or number of log files to retain.
Proposed Solution
Procedure
Reduce the retention period for transcript and/or Session Data, Call Data Records, and
Application data.
PSYSM00051
Event text MPP logging disk partition usage now below low
threshold. Trace logging now enabled.
PSYSM events
Problem description
The system has detected that the disk usage for MPP logging has fallen below the low
threshold level. Trace logging will be resumed.
Proposed Solution
About this task
There is no further action required. However, it is an indication that trace logging was disabled.
So there are several possible remedies to prevent this condition in the future.
Procedure
Reduce the MPP Trace levels.
Proposed Solution
Procedure
Reduce the MPP log file maximum log file size and/or number of log files to retain.
Proposed Solution
Procedure
Reduce the retention period for transcript and/or Session Data, Call Data Records, and
Application data.
PSYSM00056
PSYSM00057
Event text MPP disk use ({0} percent) has exceeded the

SNMP Trap ID: 17901
Event level Error Event. Minor alarm generated.
Trigger component MPP System Manager issues.
Problem description
{0} - Percentage that the MPP disk usage has reached.
{1} - The minimum percentage that is allowed.
The MPP server disk usage has exceeded the minimum configured threshold.
Proposed Solution
Procedure
2. If you frequently receive this event, the MPP disk usage has reached or exceeded
its minimum threshold.
PSYSM00057
Event text MPP cpu use ({0} percent) has exceeded the

SNMP Trap ID: 17901
PSYSM events
Problem description
{0} - Percentage that the MPP CPU usage has reached.
The MPP server CPU usage has exceeded the minimum configured threshold.
Proposed Solution
Procedure
1. Conduct test calls to ensure that the performance of the speech application is not
affected negatively.
2. If you frequently receive this event, the MPP CPU usage has reached or exceeded
PSYSM00058
Event text MPP memory use ({0} percent) has exceeded the

SNMP Trap ID: 17901
Event level Error Event. Minor alarm generated.
Trigger component MPP System Manager issues.
Problem description
{0} - The percentage that the MPP memory usage has reached.
The MPP server memory usage has exceeded the minimum configured threshold.
PSYSM00058
Proposed Solution
Procedure
2. If you frequently receive this event, the MPP disk usage has reached or exceeded
PSYSM events
Chapter 25: PTELE events
PTELE00001
Event name PTELE00001
Event text Configuration Error: {0}
Trigger component MPP telephony provider that runs as part of the SessionManager
process
Problem description
{0} - Provides information about the configuration problem.
The telephony process might not be able to take calls due to a configuration problem, such as
an invalid or missing parameter.
Proposed Solution
Procedure
1. Review the details in the event message.

2. Identify the configuration problem.
PTELE00002
Event text Network Error {0}
PTELE events
process
Problem description
{0} - Provides information about the network error.
Network error that caused a telephony problem.
Proposed Solution
Procedure
Verify that the network connection is active and operating correctly.
PTELE00004
Event text Media Error: {0}
Event level Information or error event. No alarm is generated.
process
Problem description
{0} - Information about the media problem.
Unable to establish a connection. For example, there could be a codec mismatch between
Communication Manager and the MPP.
Proposed Solution
About this task
Verify the EPM configuration with the Configuration Note.
PTELE00005
PTELE00005
Event text Signaling Error: {0}
process
Problem description
{0} - Provides information about the signaling problem.
The system could not send a call-signaling message or decode an incoming call-signaling
message.
Proposed Solution
Procedure
Restart the MPP.
PTELE00006
Event text Call Error: {0}
process
Problem description
{0} - Provides information about the calling problem.
PTELE events
The system encountered a problem while managing an incoming or outgoing call. For example,
the system could not make outbound calls.
Proposed Solution
Procedure
Restart the MPP.
PTELE00007
Event text Call Force Cleared: {0}
process
Problem description
{0} - Provides details about the event.
An error occurred in the Q931 signaling in H.323 between the MPP and Communication
Manager.
Proposed Solution
Procedure
PTELE00008
PTELE00009
Event text Place Call Failed Due To All Channels Busy {0}
process
Problem description
{0} - Provides details about the event.
The telephony process could not initiate an outbound call because all stations assigned to the
MPP were busy.
Proposed Solution
Procedure
If this event occurs frequently, consider upgrading your Avaya Aura Experience Portal
system with more stations.
PTELE00009
Event text Exception Caught: {0}
Associate alarm Name: QTELE00009

details
SNMP Trap ID: 17196

process
Problem description
{0} - Provides information for the event.
The system encountered an internal error.
PTELE events
Proposed Solution
Procedure
Restart the MPP.
PTELE00010
Event text Error Opening File {0} Errno {1}
process
Problem description
{0} - The name of the file that cannot be opened.
{1} - Provides information about the event.
The system could not open a file for playing a prompt or recording a message.
Proposed Solution
Procedure
1. Verify that the MPP disk space is available.

2. Verify that the prompt files exist.
PTELE00011
PTELE00012
Event text Error Writing To File {0} Errno {1}
process
Problem description
{0} - The name of the file to which the system could not write.
The system could not write to a file.
Proposed Solution
Procedure
Verify that the MPP disk space is available.
PTELE00012
Event text Error Reading From File {0} Errno {1}
process
Problem description
{0} - The name of the file that the system could not read.
The system could not read from a file.
PTELE events
Proposed Solution
Procedure
Verify that the file exists.
PTELE00013
Event text An Internal Error Has Occurred: {0}
process
Problem description
Proposed Solution
Procedure
Restart the MPP.
PTELE00014
Event text Gatekeeper Discovery Failed on Channel {0} Due To {1}
PTELE00015
process
Problem description
The system could not find a gatekeeper to register a specified extension.
Proposed Solution
Procedure
Verify that the extension configuration and network connectivity are correct.
PTELE00015
Event text Gatekeeper Discovery Rejected on Channel {0} Due To

{1}
process
Problem description
The Communication Manager (CM) gatekeeper rejected a gatekeeper location that was
requested for the specified station.
PTELE events
Proposed Solution
Procedure
Security denial: Wrong password configured.
Invalid alias: Invalid extension configured.
Resource unavailable: CM lacks resources or licenses.
Duplicate alias: Station already registered.
Terminal excluded: Invalid extension.
PTELE00016
Event text Gatekeeper Registration Failed on Channel {0} Due To

{1}
process
Problem description
The MPP could not send a registration request to the private branch exchange (PBX) or did
not receive a response from the PBX.
Proposed Solution
Procedure
PTELE00017
PTELE00017
Event text Gatekeeper Registration Rejected on Channel {0} Due

To {1}
process
Problem description
The PBX rejected a registration request for the specified station.
Proposed Solution
Procedure
Security denial: Wrong password configured.
Invalid alias: Invalid extension configured.
Resource unavailable: CM lacks resources or licenses.
Duplicate alias: Station already registered.
Terminal excluded: Invalid extension.
PTELE00018
PTELE events
Event text Gatekeeper Unregistration Requested on Channel {0}

Due To {1}
process
Problem description
The PBX requested to unregister a specified extension.
Proposed Solution
Procedure
Verify that the extension is not registered by another server.
PTELE00019
Event text Gatekeeper Unregistration Rejected on Channel {0}

Due To {1}}
process
Problem description
The PBX rejected a request to unregister a specified extension.
PTELE00020
Proposed Solution
About this task
PTELE00020
Event text CCMS Connection Failed on Channel {0} Due To {1}
process
Problem description
A network error occurred on the call-signaling channel.
Proposed Solution
Procedure
Restart the MPP.
PTELE00021
Event text Ras Timer Expired on Channel {0} Due To {1}
PTELE events
process
Problem description
The MPP telephony resource could not receive a response from the PBX for a registration
message.
Proposed Solution
Procedure
Verify that the network configuration and the connection to the MPP are correct.
PTELE00022
Event text Ras Message Error {0} on Channel {1}
process
Problem description
An error occurred while the MPP telephony resource tried to send or receive a registration
message.
PTELE00023
Proposed Solution
Procedure
Verify that the extension configuration is correct.
PTELE00023
Event text Mrcp Media Negotiation Failed Due To {0}
process
Problem description
The Automated Speech Recognition (ASR) server or Text-to-Speech (TTS) (TTS) server could
not support the configured codec.
Proposed Solution
Procedure
Verify that the MPP, ASR server, and TTS server configurations are correct.
PTELE00024
Event text Call Handler Initialization Failed {0}
PTELE events

details
SNMP Trap ID: 17197

Alarm Codes page.
process
Problem description
The system encountered an internal fatal error.
Proposed Solution
Procedure
Restart the MPP.
PTELE00025
Event text Config Param {0} Not Found {1}
process
Problem description
The configuration parameter did not exist.
PTELE00026
Proposed Solution
Procedure
Verify that the configuration data on the EPM is correct.
PTELE00026
Event text Config Parm {0} Has Invalid Value {1} {2}
process
Problem description
{1} and {2} - Provides information about the event.
The configuration parameter had an invalid value.
Proposed Solution
Procedure
Change the configuration data on the Experience Portal Manager (EPM) to a valid
value.
PTELE00027
PTELE events
Event text Mrcp Media Error: {0}
process
Problem description
The system could not establish an RTP connection with the ASR server or TTS server.
Proposed Solution
Procedure
1. Verify that the network connection for the MRCP is established.

2. Verify that the ASR server or TTS server is available.
PTELE00028
Event text Media Error {0} On Channel {1}
process
Problem description
The system could not establish an RTP connection with the PBX.
PTELE00029
Proposed Solution
Procedure
Verify that the network connection and the connection for the MPP are correct.
PTELE00029
Event text Station Command {0} On Channel {1} Attempted in

Invalid State {2}
process
Problem description
{2} - The invalid state.
Proposed Solution
Procedure
Restart the MPP.
PTELE events
PTELE00030
Event text Channel {0} In Service
process
Problem description
The system successfully registered a specified extension.
Proposed Solution
About this task
PTELE00031
Event text Channel {0} Out of Service in State {1} {2}
process
Problem description
{1} - The state that the channel went out of service.
{2} - The registration IP address on the switch.
The system could not register a specified extension.
PTELE00032
Proposed Solution
Procedure
1. Review log files to identify additional errors that are related to this problem.
2. Ensure that the MPP can ping the registration IP address.
3. Ensure that the MPP can be pinged from the registration IP address.
4. Verify the PBX configurations to ensure that there are enough IP_API_A licenses
and that all the stations are configured correctly.
PTELE00032
Event text Trunk {0} In Service
process
Problem description
{0} - The name of the SIP trunk that is assigned through the EPM.
The assigned SIP trunk is ready to receive calls.
Proposed Solution
About this task
PTELE00033
PTELE events
Event text Trunk {0} Out of Service in State {1}

details
SNMP Trap ID: 17902

Alarm Codes page.
process
Problem description
{0} - The name of the SIP trunk that is assigned through the EPM.
{1} - The state that the trunk went out of service.
This event is triggered when a SIP trunk is in the Out-Of-Service state or when multiple SIP
trunks are being configured on the MPP. Avaya Aura Experience Portal supports only one
SIP trunk.
Proposed Solution
Procedure
1. From the EPM, go to VoIP Connections.

2. Click the SIP tab.
3. Disable additional SIP connections that are configured on the EPM.
PTELE00034
Event text Percentage of Channels Out of Service {0} Has

Exceeded Warning Level of {1}
PTELE00035
process
Problem description
{0} - The percentage of the allocated ports that are out of service at the time of the event.
{1} - The percentage that was configured for the Warning Trigger on the EPM.
The MPP reports this warning event when the percentage of the SIP and H.323 channels that
failed exceeded the percentage that was configured for the Warning Trigger on the EPM.
Proposed Solution
Procedure
1. From the EPM, review the log reports for errors that were reported by the MPP.
2. From the EPM, go to Port Distribution for additional errors.
3. Review log files in the directory $AVAYA_MPP_HOME/logs/process/SessMgr/
SessionManager.log* files for additional messages.
4. On the EPM, set the trace level for Telephony to Finer.
5. Restart the MPP.
6. Review log files after the ports go out of service.
PTELE00035

Exceeded Error Level of {1}

details
SNMP Trap ID: 17901

Alarm Codes page.
PTELE events
process
Problem description
{1} - The percentage that was configured for the Error Trigger on the EPM.
The MPP reports this error event when the percentage of the SIP and H.323 channels that
failed exceeded the percentage that was configured for the Error Trigger on the EPM.
Proposed Solution
Procedure
5. Restart the MPP.
PTELE00036

Exceeded Fatal Level of {1}

details
SNMP Trap ID: 17902

Alarm Codes page.
PTELE00037
process
Problem description
{1} - The percentage that was configured for the Fatal Trigger on the EPM.
The MPP reports this error event when the percentage of the SIP and H.323 channels that
failed exceeded the percentage that was configured for the Fatal Trigger on the EPM.
Proposed Solution
Procedure
5. Restart the MPP.
PTELE00037
Event text TLS Initialization Failed {0}
process
Problem description
{0} - The reason for the failure.
PTELE events
At start up, the MPP SessionManager initializes TLS if the required security certificates are
received from the EPM. This error event occurs when there is incorrect or missing configuration
for the certificates.
Note:
TLS is required by the SessionManager Telephony provider only if the SIP connection is
configured to use TLS.
Proposed Solution
Procedure
1. On the EPM, verify that the configuration on the Security Certificate page is
correct.
3. On the MPP, run the following commands and verify that the files referenced by the
parameters exist.
xml.php | grep mpp.ses.public.cert.file
xml.php | grep mpp.ses.private.cert.file
xml.php | grep mpp.ses.private.key.file
4. If the above parameters and files do not exist, do the following:
a) Set the tracing for MPP System Manager to Finest.
b) Restart the MPP
c) Review the file $AVAYA_MPP_HOME/logs/process/SysMgr/
logfile.log for problems relating to downloading the SES certificate files.
5. If the above parameters and files exist, do the following:
a) Remove the files.
b) Restart the MPP from the EPM.
Proposed Solution
Procedure
PTELE00038
PTELE00038
Event text Add Trunk {0} Failed Due to Invalid Transport {1}
process
Problem description
{0} - The name of the trunk.
{1} - The transport type
The SessionManager Telephony provider could not add a SIP trunk that was configured to use
TLS. At start up, the MPP SessionManager could not initialize TLS. This error event occurs
when there is incorrect or missing configuration for the certificates.
Note:
TLS is required by the SessionManager Telephony provider only if the SIP connection is
configured to use TLS.
Proposed Solution
Procedure
1. On the EPM, verify that the configuration on the Security Certificate page is
correct.
3. On the MPP, run the following commands and verify that the files referenced by the
parameters exist.
xml.php | grep mpp.ses.public.cert.file
xml.php | grep mpp.ses.private.cert.file
xml.php | grep mpp.ses.private.key.file
4. If the above parameters and files do not exist, do the following:
a) Set the tracing for MPP System Manager to Finest.
PTELE events
b) Restart the MPP

c) Review the file $AVAYA_MPP_HOME/logs/process/SysMgr/
logfile.log for problems relating to downloading the SES certificate files.
5. If the above parameters and files exist, do the following:
a) Remove the files.
b) Restart the MPP from the EPM.
Proposed Solution
About this task
Contact Avaya Technical Support if this problem persists.
PTELE00039
Event text Station Configuration Error [0} Station {1}
process
Problem description
{1} - The H.323 port that failed.
The station that was specified in the event message might have an invalid configuration. The
MPP might not be able to detect this condition until a call comes in through the specified H.323
port.
For example, if the error message {0} in the event message stated that "No display Module
configured," you should verify that the H.323 station that was set up on the PBX has the Display
Module configured according to the information given in the Avaya Aura Experience Portal
Configuration Note.
PTELE00040
Proposed Solution
About this task
Verify that the H.323 ports are configured according to the information given in the Avaya Aura
Experience Portal Configuration Note.
You can download the Configuration Note from the Avaya Support web site.
PTELE00040
Event text Max Stations Exceeded {0}
process
Problem description
The telephony configuration that was sent by the EPM exceeded the maximum number of
H.323 ports and SIP channels that an MPP can support.
Proposed Solution
About this task
Typically, this problem should not occur at customer sites.
Procedure
1. Reduce the number of ports or channels that are configured for the Avaya Aura
Experience Portal system.
PTELE events
PTELE00041
Event text "Speech Server TLS Connection Failed, Issuer: {0},

Subject: {1}, Error: {2}" where:
{0} - the Issuer (Example: Issuer: C=AL, ST=Babruysk, O=ACME Inc.,
CN=Vasya Pupkin)
{1} - Subject, (Example: Subject: C=AL, ST=Babruysk, O=ACME Inc.,
CN=Vasya Pupkin, or anything)
{2} - Reason of error in string

details
SNMP Trap ID: 17902
Event level Major alarm is generated by default. You can change the severity for this
alarm by logging in to Experience Portal Manager and using the Alarm
Codes page.
Trigger Avaya Aura Experience Portal has configured the speech server using
component protocol: MRCP V2 with TLS.
Problem description
MPP failed to make TLS connection to speech server with MRCP V2.
Proposed Solution
Procedure
1. Verify Avaya Aura Experience Portal has configured trusted certificate for Nuance
speech server for TLS connection.
2. Verify the Nuance speech server also has the same valid certificate in the directory:
$NSSSVRSDK/certs.
3. Restart MPP to resync the TLS connection.
PTELE00042
PTELE00042
Event text SIP Proxy TLS Connection Failed, Issuer: {0}, Subject: {1}, Error:
{2}
Associate alarm details Name: QTELE00042
SNMP Trap ID: 17902
Event level Error event. Major alarm is generated.
Trigger component Avaya Aura Experience Portal has configured the SIP proxy
server using protocol: TLS.
Problem description
MPP failed to make TLS connection to SIP proxy server.
{0} = Issuer, {1} = Subject, {2} = Reason for error.
Proposed Solution
Procedure
1. Verify that the Experience Portal certificate is added to the SIP proxy server.
2. Verify that the Experience Portal link on the SIP proxy server is configured as
TLS.
3. Verify that Experience Portal is configured with a trusted certificate for SIP
Connection.
4. Restart the MPP to re-sync the TLS connection.
PTELE events
Chapter 26: PTRC events
PTRC_00001
Event name PTRC_00001
Event text Traces download request was received.
Trigger component Trace WS
Problem description
Traces download request was received from EPM trace client.
Proposed Solution
Procedure
PTRC_00002
Event text Trace file was opened successfully.
PTRC events
Problem description
Trace file was opened successfully.
Proposed Solution
Procedure
PTRC_00003
Event text Trace {0} was sent successfully.
Problem description
{0} Trace file name
The trace with specified file name was sent (back to client) successfully.
Proposed Solution
Procedure
PTRC_00004
PTRC_00005
Event text Trace {0} for "{1}" was received successfully.
Trigger component EPM Trace client
Problem description
{0} Trace file name
{1} Process component (For example, SessMgr, VXI).
The specified trace file from specified process was received successfully.
Proposed Solution
Procedure
PTRC_00005
Event text Trace List ({0}) for "{1}" was received

successfully.
Problem description
{0} Number of files in the list
Trace List (with size) for specified process was received successfully.
PTRC events
Proposed Solution
Procedure
PTRC_00011
Event text Trace {0} in "{1}" was not found, the file may not
exist.
Trigger component Trace Client
Problem description
{0} Trace name
The trace file in specified process was not found, the file may not exist.
Proposed Solution
Procedure
1. The specified trace may not be generated yet, or may have been purged by MPP.
2. User can ignore this warning message.
3. No corrective action is required.
PTRC_00012
PTRC_00012
Event text Could not open file {0} in "{1}".
Problem description
{0} Trace file name
{1} Process component
Could not open the trace file in the specified process.
Proposed Solution
Procedure
1. There is access privilege for the specified file. Login to the MPP to check the process
folder has correct owner, group and correct access privileges.
PTRC_00013
Event text Could not close file {0}.
PTRC events
Problem description
{0} Trace file name
The trace web service could not close the specified file.
Proposed Solution
Procedure
1. This error should not occur only if the file was corrupted at the file I/O operation or
power failure.
2. User can restart MPP to retry trace retrieval to see if this happen again.
PTRC_00014
Event text Trace Invalid date range {0}.
Problem description
{0} date in string
The trace web service receives invalid date from requested client.
Proposed Solution
Procedure
1. This error is used for debug purpose in development cycle and it should not occur
on release system.
2. No corrective action is required.
PTRC_00016
PTRC_00016
Event text Trace retrieval exception.
Problem description
An exception was occurred at trace retrieval with exception detail.
Proposed Solution
Procedure
1. Review failed messages in the log report to identify the real cause. Some of them
are related to DB access. Please refer the DB associated error.
PTRC_00019
Event text Could not set URL by hostname "{0}".
Problem description
{0} MPP host name
The trace client could not set URL with specified MPP hostname.
PTRC events
Proposed Solution
Procedure
The configured MPP may no longer be valid, go to System Monitor page to verify MPP
state. Reconfigure MPP.
PTRC_00020
Event text Error connecting trace web service for {0} with
exception: {1}.
Trigger component EPM trace client
Problem description
{1} Exception message
The trace client caught exception while communicating with trace web service with specified
process.
Proposed Solution
Procedure

2. Make sure MPP is up running, also verify httpd service is running as well.
3. Also verify the installed S/W version are matched on both EPM and MPP. If not,
reinstall EP system.
PTRC_00021
PTRC_00021
Event text Error from trace web service with status {0}.
Problem description
{0} Error status
The trace client requests a trace list with specified process, but receives with error status.
The error can be:
Trace not found, Null file, or File I/O error.
Proposed Solution
Procedure

2. Identify the cause of error from the log report. User can ignore the error of Trace
not found (because trace may not be generated yet). For null file, the client may
accidentally sent null string for trace (but should not occur). For File I/O error, this
can be generated by SOAP interface due to disconnect during trace transfer.
PTRC_00022
Event text Soap I/O Error with no attachment for trace {0} from
"{1}".
PTRC events
Problem description
{0} Trace file.
The trace client sent request for trace retrieval and the operation was complete. But the
returned status indicating trace attachment was zero.
Proposed Solution
Procedure
1. Make sure both EPM and MPP were installed the same S/W releases (Because
SOAP WSDL interface may be changed). If not, reinstall the EP system.
PTRC_00023
Event text Illegal multi-attachments for trace {0} from "{1}".
Problem description
{0} Trace file name.
The trace client received illegal multi-attachments for specified trace from specified process.
This error was due to mismatch WSDL interface to cause miscommunication between client
(EPM) and trace web service (MPP).
PTRC_00024
Proposed Solution
Procedure
1. Make sure both EPM and MPP were installed the same S/W releases. If not, reinstall
the EP system.
PTRC_00024
Event text Error to set access privilege {0}
Problem description
{0} Directory path.
The trace client attempts to modify access privilege on the created trace folder that contains
retrieved traces but got denied. This error can be ownership and user group were modified
after EP system was installed or the installed OS grant different ownership.
Proposed Solution
Procedure
1. Verify the trace folder for retrieved trace has correct ownership and access privilege.
If not, try to change manually to see if the problem goes away.
2. If problem still exists, contact Avaya Technical Support.
PTRC events
PTRC_00025
Event text The limit of trace access users in properties was not
in boundary (between {0} and {1}). Use default {2}.
Problem description
{0} 1 User.
{1} Max users.
{2} Default number of users allowed.
The limit of trace access users in properties was not in boundary (between 1 and 3). Use default
2.
This is just warning message.
Proposed Solution
Procedure
PTRC_00031
Event text DB Error accessing subsystem: DB Driver not found.
PTRC_00032
Problem description
The trace client attempts to initialize DB interface, but caught an exception of DB Driver not
found.
This could only occur at the incomplete system installation or upgrade, and consequently cause
postgres driver was not installed or installed with incorrect version.
Proposed Solution
Procedure
1. Try to reinstall the EP system.

2. If the reinstall cannot resolve the issue, contact Avaya Technical Support.
PTRC_00032
Event text DB Error accessing subsystem: DB connection failed.
Problem description
The trace client attempts to initialize DB interface, but caught an exception of DB
connection.
This could occur if the postgres password was changed recently after EPM is running.
Proposed Solution
Procedure
1. Login to the EPM system, got $CATALINA_HOME/lib/config. Verify the modified

date of the file voice.properties. If the date indicates this file was modified recently,
edit this properties to verify that postgres password. If everything is correct, restart
postgres service and restart EPM.
PTRC events
2. If the above solution can not resolve the issue from the information in the error
messages, contact Avaya Technical Support
PTRC_00033
Event text Failed to initialize Database I/F.
Problem description
The trace client attempt to access data from EP table, but was failed at initializing Database.
This error is associated with PTRC_00031 or PTRC_00032 events.
Proposed Solution
Procedure
1. Check the solution in PTRC_00031 and PTRC_00032.

PTRC_00035
Event text DB Error: Accessing data from EP database.
PTRC_00035
Problem description
Error accessing data from EP database.
The row data can not be retrieved from the table. The table may contain invalid data.
Proposed Solution
Procedure
1. This error message should not occur on release system. If it occurs, log on to the
EPM and log into postgres database to verify the table sdSubsystem contains valid
entries for MPP. If not, try to reconfigure the MPP from theMPP server.
PTRC events
Chapter 27: PTTS events
PTTS_00001
Event name PTTS_00001
Event text Could not find an available TTS server.
Trigger component MPP TTS provider that runs as part of the SessionManager process
Problem description
The system could not locate a TTS server that can process commands requested by a speech
application.
Proposed Solution
Procedure
1. On the Experience Portal Manager (EPM), verify that the configuration for the TTS
servers and the language selected for the application are correct. Ensure that the
language used by the application is among the languages that are supported by the
TTS server.
2. If your Avaya Aura Experience Portal configuration uses multiple TTS servers, you
can use the Session Web page on the MPP Service Menu to view the IP address
of the TTS server that was used for a call.
3. Restart the MPP.
PTTS events
PTTS_00002
Event text No available TTS ports on server {0}.
Problem description
The system could not locate an available TTS port.
Proposed Solution
Procedure
1. Verify that the configuration for the TTS server is correct.

2. Restart the MPP.
PTTS_00003
Event text Failed to get a TTS port!
Problem description
An error occurred while trying to get a TTS port.
PTTS_00004
Proposed Solution
Procedure

2. Restart the MPP.
PTTS_00004
Event text TTS server properties changed. Updating servers.
Problem description
The system is updating the TTS server due to configuration changes.
Proposed Solution
About this task
PTTS_00005
Event text Failed initializing TTS server {0}.
Associate alarm Name: QTTS_00005

details
SNMP Trap ID: 17199
PTTS events

Alarm Codes page.
Problem description
The system could not initialize the TTS server due to invalid configuration parameters.
Proposed Solution
Procedure

2. Restart the MPP.
PTTS_00006
Event text Failed to convert parameter {0} to type {1} with

error {2}.
Problem description
{0} and {1} - Provide information about the parameter.
The system could not process configuration parameters.
PTTS_00007
Proposed Solution
Procedure

2. Restart the MPP.
PTTS_00007
Problem description
The TTS provider encountered an exception. See the event message for details of the
exception.
Proposed Solution
Procedure
1. If this error event persists or if it is accompanied by other problems that occurred

on the MPP, restart the MPP.
established. On the MPP, verify that you can ping the TTS server from the MPP. On
the TTS server, verify that you can ping the MRCP Network Address that was
configured for the MPP on the EPM.
PTTS events
PTTS_00008
Event text Caught an unknown exception!
Problem description
The TTS provider encountered an exception. See the event message for details of the
exception.
Proposed Solution
Procedure
1. If this error event persists or if it is accompanied by other problems that occurred

on the MPP, restart the MPP.
established. On the MPP, verify that you can ping the TTS server from the MPP. On
the TTS server, verify that you can ping the MRCP Network Address that was
configured for the MPP on the EPM.
PTTS_00009
Event text All ports free, reinitializing server {0} for

configuration change now.
PTTS_00010
Problem description
Proposed Solution
About this task
PTTS_00010
Event text There are {1} ports still in use, reinitializing

server {0} for configuration change later.
Problem description
{1} - The number of ports that are in use.
Proposed Solution
About this task
PTTS events
PTTS_00011
Event text No configuration changes found that require

reinitializing for server {0}.
Problem description
Proposed Solution
About this task
PTTS_00012
Event text TTS port count must be greater than 0. Initialize

failed!
Problem description
The TTS server could not be initialized with zero ports.
PTTS_00013
Proposed Solution
Procedure
Verify the TTS port configuration on the EPM.
PTTS_00013
Event text TTS server property changes require a restart.
Problem description
The MPP must be restarted due to new TTS server configurations.
Proposed Solution
Procedure
If the MPP configuration indicates a status of MPP restart needed, restart the MPP.
PTTS_00014
Event text TTS server {0} has had at least {1} consecutive
errors.
PTTS events
Problem description
This event occurs when the TTS server encountered a certain number of consecutive errors.
These events can impact the performance of the MPP and should be resolved as soon as
possible.
Note:
TTS errors are aggregated on the MPP. When viewing the TTS errors on the EPM, you might
only see one error for the past hour.
Proposed Solution
About this task
Review the log files in the $AVAYA_MPP_HOME/logs/process/SessMgr directory on
the MPP for a complete list of errors."
Review the log files on the TTS server.
PTTS_00015
Event text TTS server {0} has had at least {1} consecutive
errors and has been disabled. It must be restarted.
Problem description
An excessive number of consecutive errors occurred on the specified TTS server. The MPP
removed the TTS server as a resource and marked the TTS server as disabled. The usage of
other TTS servers in the Avaya Aura Experience Portal system is not being affected.
PTTS_00016
Note:
ASR errors are aggregated on the MPP. When viewing the TTS errors on the EPM, you
Proposed Solution
Procedure
1. Either use listss.php on the MPP or go to Service Menu > Resources > Speech
Servers to view the status of the TTS server. If the server has a value of false, it is
disabled.
2. Review the $AVAYA_MPP_Home/logs/process/SessMgr.log on the MPP for a
3. Review the log files on the TTS server.
4. After resolving the errors, either restart the TTS server or restart the MPP from the
EPM so that the MPP can re-enable the TTS server.
PTTS_00016
Event text Configuration or configuration update of TTS server

{0} failed with reason: {1}.
Problem description
{1} - The description of the problem.
Avaya Aura Experience Portal could not configure the specified TTS server due to the reason
stated in the message.
PTTS events
Proposed Solution
Procedure
Verify that the configuration for the TTS server is correct.
PTTS_00017
Event text Insufficient number of resources for TTS server:

{0}.
Problem description
Avaya Aura Experience Portal requires the same number of TTS resources for each TTS
server to be the same as the total number of telephony resources.
Proposed Solution
About this task
On the EPM, verify that the total number of TTS resources equals the total number of telephony
resources for the Avaya Aura Experience Portal system.
PTTS_00018
Event text The request to remove TTS server, {0}, from

configuration completed successfully.
PTTS_00019
Problem description
The request to remove the specified ASR server from the system has been completed
successfully.
Note:
There could be a delay in the actual time when the ASR server is being deleted because
the TTS resources might be in use when the deletion request was made.
Proposed Solution
About this task
PTTS_00019
Event text TTS server failed {2}
Problem description
{2} - The details of the error message.
The TTS server failed because of the reasons indicated in the error message.
PTTS events
Proposed Solution
About this task
Depending on the error message, verify the following:
There is enough licenses and ports configured for the ASR server.
The application servers are responding in a timely manner. There could be a fetch timeout
for the external grammars.
The ASR server is responding to the MRCP requests in a timely manner. The timeout
value is governed by the response timeout value that is configured for the ASR server on
the EPM.
Chapter 28: P_AMS events
P_AMS05001
Event name P_AMS05001
Event Type INFO
Event text SC Controller Initialized.
Problem description
Session Controller is initialized.
Proposed Solution
About this task
P_AMS05004
Event Type ERROR
Event text SessionEngine event queue is full. Details: Session

<SessionId>
Problem description
Session event queue is full.
P_AMS events
Proposed Solution
About this task
Notify next level support.
P_AMS05007
Event Type WARNING
Event text CStoreNamedHandler received a corrupt message.
Problem description
A corrupt message was received.
Proposed Solution
About this task
P_AMS05008
Event Type WARNING
Event text CStoreNamedHandler received an unknown event.

Details:Session=<SessionId>
Problem description
An unknown event was received.
P_AMS05009
Proposed Solution
About this task
P_AMS05009
Event Type WARNING
Event text ConfMPNamedHandler received a corrupt message.
Problem description
Proposed Solution
About this task
P_AMS05010
Event Type WARNING
Event text ConfMPNamedHandler received an unknown event.

Details: Session=<SessionId>
Problem description
P_AMS events
Proposed Solution
About this task
P_AMS05011
Event Type WARNING
Event text IvrMPNamedHandler received a corrupt message.
Problem description
Proposed Solution
About this task
P_AMS05012
Event Type WARNING
Event text IvrMPNamedHandler received an unknown event.

Details:Session<SessionId>
Problem description
P_AMS05025
Proposed Solution
About this task
P_AMS05025
Event Type ERROR
Event text The platform is not licensed.
Problem description
License key is not configured.
Proposed Solution
About this task
Configure license key.
P_AMS05026
Event Type ERROR
Event text Configured license key is invalid.
Problem description
Invalid license key.
P_AMS events
Proposed Solution
About this task
Configure valid license key.
P_AMS05027
Event text Redundant license servers may not be properly configured.
Problem description
The license server configuration may contain an error, or a license server may have started
recently.
Proposed Solution
About this task
Check license server configuration.
P_AMS05028
Event Type WARNING
Event text License pool empty. Details: No license available

for pool [<SessionId>] with (<confId>) total
licenses and 0 available.
Problem description
No licenses available for the pool.
P_AMS05029
Proposed Solution
About this task
P_AMS05029
Event Type INFO
Event text Licenses are now available for the pool[<SessionId>]

with (<confId>) total licenses and <confId>
available.
Problem description
Licenses are now available for the pool.
Proposed Solution
About this task
P_AMS05030
Event Type WARNING
Event text License pool threshold reached Details: License pool

[<SessionId>] with (<confId>) total licenses has
reached its alarm threshold..
Problem description
License pool has reached its alarm threshold..
P_AMS events
Proposed Solution
About this task
P_AMS05031
Event Type INFO
Event text License pool threshold cleared Details: License pool

[<SessionId>] with (<confId>) total licenses has
fallen below its alarm threshold.
Problem description
License pool has fallen below its alarm threshold.
Proposed Solution
About this task
P_AMS05032
Event text License Reservation Failed. License reservation {1} failed

because of many connections {2}.
Problem description
{1} Name of the license reservation.
{2} Number of connections.
There are too many license blocks allocated by server from its license server.
P_AMS05033
Proposed Solution
About this task
Maximum 30 number of blocks can be allocated to a server 30. Increase the license block size
to reduce the number of license blocks needed.
P_AMS05033
Event text Invalid license command. The invalid license command was
<command name>.
Problem description
An internal error occurred parsing the license request.
Proposed Solution
About this task
P_AMS05034
Event text License pool failure. The failed license command was <Name
of the failed license command>.
Problem description
The platform failed to license the service.
P_AMS events
Proposed Solution
About this task
P_AMS05035
Event text License Server Request Failure. License server request

failed for {0} count {1}.
Problem description
{0} - Request name
{1} - Number of request
A request made to the license server client failed.
Proposed Solution
About this task
P_AMS05036
Event text Request received for unlicensed service. License request

failed for {0} count {1}.
Problem description
{0} - Service name
{1} - Request number
The requested service is not licensed.
P_AMS05037
Proposed Solution
About this task
Add licensing for the requested service, update service translations, or externally redirect
similar requests away from the server.
P_AMS05037
Event text No Service Mapping for Request. The SIP Request-URI was
<SIP Request-URI name> for GSLID <GSLID>.
Problem description
No service installed to process the request.
Proposed Solution
About this task
Update service translations, or externally redirect similar requests from the server.
P_AMS05038
Event text No Service Mapping for Relay Event. The service name was
<service name> for GSLID <GSLId>.
Problem description
P_AMS events
Proposed Solution
About this task
Notify application development about this internal event error.
P_AMS05039
Event text No Service Mapping for Chat Event. The SIP To header was
<SIP To heander name> for GSLID <GSLID>.
Problem description
Proposed Solution
About this task
P_AMS05040
Event text No Service Mapping for Received Event. The SIP To header
was <SIP To header name> for GSLID <GSLID>.
Problem description
P_AMS05041
Proposed Solution
About this task
P_AMS05041
Event text No Service Mapping for Session Create. The service name
was <Service name> for GSLID <GSLID>.
Problem description
Proposed Solution
About this task
P_AMS05042
Event text Unable to license service. The service name was <Service
name>, the async license request was for <license names>
licenses.
Problem description
Service is not licensed.
P_AMS events
Proposed Solution
About this task
License or redirect the affected request.
P_AMS05043
Event text Foreign server connected to cluster. The foreign server

address is <foreign server address>.
Problem description
The cluster is not properly configured or a foreign server is improperly configured to connect
to the cluster.
Proposed Solution
About this task
Verify if the local cluster configuration includes the correct servers. If the cluster is properly
configured then verify the configuration of the identified foreign sever.
P_AMS05500
Event Type SWERR
Event text SessionEngine index mapping table is full. Details:

Session <sessionId>.
Problem description
SessionEngine mapping table is full.
P_AMS05501
Proposed Solution
About this task
P_AMS05501
Event Type SWERR
Event text Attempt to clear event that has already been cleared.
Details: Session <confId>, Event [<sessionId>] with
trid <confId> (%p). Remaining entries = <confId>.
Problem description
Event has already been cleared.
Proposed Solution
About this task
P_AMS05503
Event Type SWERR
Event text MMC Dialogue session resource is missing. Session

<sessionId>.
P_AMS events
Problem description
Session resource is missing.
Proposed Solution
About this task
P_AMS05505
Event Type SWERR
Event text No session identifier for trid. Details: Session

<ConfId>, TRID [<sessionId>], Event\n<sessionId>\n.
Problem description
No session identifier found.
Proposed Solution
About this task
P_AMS05506
Event Type SWERR
Event text MCConnectionRo ute TID size exceeds array limit.
P_AMS05513
Problem description
TID size exceeds array limit.
Proposed Solution
About this task
P_AMS05513
Event Type SWERR
Event text MCConnectionPoolEntry name has too many characters.

Details: Name <confId>, limit <confId>
Problem description
Name has too many characters.
Proposed Solution
About this task
P_AMS05516
Event Type SWERR
Event text Session Event Timeout Details: Status reception

timeout <confId> expired for session <confId>.
Terminating session.
P_AMS events
Problem description
Session event timed out.
Proposed Solution
About this task
P_AMS05017
Event Type INFO
Event text SEHKillConference terminated a conference.

Details:Conference=<confid>
Problem description
Conference was killed.
Proposed Solution
About this task
P_AMS05518
Event Type SWERR
P_AMS05519
Event text Session VarTable is not NULL in service setup.

Details: File <sessionId>, line <confId>.
Problem description
VarTable is not NULL.
Proposed Solution
About this task
P_AMS05519
Event Type SWERR
Event text Session Event Timeout Details: CStore response

timeout expired for session <confId>. Terminating
session.
Problem description
Cstore response timed out.
Proposed Solution
About this task
P_AMS events
P_AMS06010
Event Type INFO
Event text SIPMC Initialized.
Trigger component SIPMC
Problem description
The SIPMC process is initialized.
Proposed Solution
About this task
P_AMS06011
Event Type INFO
Event text Controller <Registered | UnRegistered> Details:

REFID:<refid> Domain:<domain> Version:<ver>
Comp:<comp>.
Problem description
The Session Controller registration status.
Proposed Solution
About this task
Check session controller (SC) status.
P_AMS06012
P_AMS06012
Event Type WARNING
Event text Session Aborted. Details: ENGID:<engineid>

Reason:<reason> GSLID<gslid>.
Problem description
A session is aborted with given reason.
Proposed Solution
About this task
Check and correct the abort reason.
P_AMS06013
Event Type WARNING
Event text INVITE authentication. Details:<Reason>.
Problem description
An outbound INVITE failed during authentication.
Proposed Solution
About this task
Check and correct the failed reason.
P_AMS events
P_AMS06014
Event Type WARNING
Event text Untrusted Access. Details:<Actions taken>.
Problem description
An incoming INVITE from untrusted domain is rejected or redirected.
Proposed Solution
About this task
Check and verify actions taken by SIPMC.
P_AMS06015
Event Type WARNING
Event text SIP Registration Failed. Details:<Reason>.
Problem description
The SIP registration attempt has failed.
Proposed Solution
About this task
Check and correct the failed reason.
P_AMS06016
P_AMS06016
Event Type INFO
Event text Route State Change. Details: <Domain>

<IPaddress>:<Port>: <Transport> State Changed to
<RouteState>.
Problem description
Route State changes as a result of server ping.
Proposed Solution
About this task
Informational.
P_AMS06017
Event Type ERROR
Event text Verification of SIP TLS connection failed. Detail:

The IP Address:<IP address> on the X509 Certificate
does not match the remote server IP Address:<IP
address>.
Proposed Solution
About this task
Verify remote IP address and certificate.
P_AMS events
P_AMS06018
Event Type ERROR
Event text Unable to digitally authenticate remote certificate.

Detail:<certificate detail>.
Problem description
Unable to digitally authenticate remote certificate.
Proposed Solution
About this task
Verify if remote signing CA is include d in the Avaya MS trusted certificate authority.
P_AMS06020
Event Type ERROR
Event text TLS Handshake Failed. Detail: Local IP:<IP address>

and Remote IP:<IP address> Reason:<reason>.
Problem description
TLS handshake failed with given reason.
Proposed Solution
About this task
Verify TLS certificate and cipher configuration.
P_AMS07001
P_AMS07001
Event Type ERROR
Event text Invalid Engine State.
Trigger component IvrMP
Problem description
Request issued in wrong state.
Proposed Solution
About this task
Check related service functionality.
P_AMS07004
Event Type ERROR
Event text Invalid Resource State.
Problem description
A URL resource is being updated and found to be in an invalid state.
Proposed Solution
About this task
Report incident.
P_AMS events
P_AMS07008
Event Type ERROR
Event text Invalid Path.
Problem description
A configured path is invalid or does not exist.
Proposed Solution
About this task
Verify the that the reported path is valid.
P_AMS07009
Event Type ERROR
Event text URL Resource Failure.
Problem description
A URL resource could not be retrieved.
Proposed Solution
About this task
Check related service functionality and availibity of the reported URL.
P_AMS07010
P_AMS07010
Event Type ERROR
Event text Invalid Extension.
Problem description
An invalid file extension was encountered.
Proposed Solution
About this task
P_AMS07011
Event Type ERROR
Event text Invalid URL.
Problem description
A provided URL was invalid.
Proposed Solution
About this task
P_AMS events
P_AMS07012
Event Type ERROR
Event text Invalid Resource State.
Problem description
A URL resource is being updated and found to be in an invalid state.
Proposed Solution
About this task
Report incident.
P_AMS07013
Event Type ERROR
Event text Resource Locate Failure.
Problem description
A resource could not be found.
Proposed Solution
About this task
Check related service functionality and locate and install the reported resource.
P_AMS07014
P_AMS07014
Event Type ERROR
Event text Resource Allocation Failure.
Problem description
A required MRCP resource could not be allocated.
Proposed Solution
About this task
Verify MRCP pool configuration and availability of the reported resource.
P_AMS07015
Event Type ERROR
Event text Invalid Parameter.
Problem description
An invalid template parameter was used.
Proposed Solution
About this task
Verify related service functionality for the reported parameter that was improperly formatted.
P_AMS events
P_AMS07016
Event Type ERROR
Event text Codec Not Counted.
Problem description
A CODEC being used is not being accounted.
Proposed Solution
About this task
Report incident.
P_AMS07017
Event Type ERROR
Event text Resource Length Exceeded.
Problem description
Too many resources for SDP parsing.
Proposed Solution
About this task
Report incident.
P_AMS07018
P_AMS07018
Event Type ERROR
Event text Invalid Request Event.
Problem description
An attempt was made to pause an engine that was in a state that does not allow a pause.
Proposed Solution
About this task
P_AMS07019
Event Type ERROR
Event text Invalid Media Address.
Problem description
A remote address is already in use or is invalid.
Proposed Solution
About this task
Check related SDP for an invalid remote address or formatting.
P_AMS events
P_AMS07020
Event Type ERROR
Event text Invalid Media Address
Problem description
An MRCP resource request failed.
Proposed Solution
About this task
Check MRCP pool configuration and associated resource availability.
P_AMS07021
Event Type ERROR
Event text Collect attempted for unleased engine
Problem description
A Collect request was issued for an engine that has been released.
Proposed Solution
About this task
P_AMS07022
P_AMS07022
Event Type ERROR
Event text Request Queue Full
Trigger component IVR Media Processor (IvrMP)
Problem description
The request queue has exceeded its provisioned limit.
Proposed Solution
About this task
Verify configuration of MAX_QUEUED _REQUESTS is appropriate for the service being
used.
P_AMS07023
Event Type ERROR
Event text Play Attempted for Unleased Engine
Problem description
A Play request was issued for a released engine.
Proposed Solution
About this task
P_AMS events
P_AMS07026
Event Type ERROR
Event text Play Request Error
Problem description
An error occurred parsing a Play request.
Proposed Solution
About this task
Check log details and related service functionality.
P_AMS07031
Event Type ERROR
Event text Text-To-Speech Not Allocated
Problem description
A text-to-speech request was issued for an engine that does not have a text-to-speech
resource allocated.
P_AMS07032
Proposed Solution
About this task
Check related service functionality that is using text-to-speech without first allocating a text-to-
speech resource.
P_AMS07032
Event Type ERROR
Event text Digit Detector Resource Allocation Failed
Problem description
A digit detection resource allocation failed.
Proposed Solution
About this task
Report incident.
P_AMS07038
Event Type ERROR
Event text Record Request Error
Problem description
Parsing of a Record request failed.
P_AMS events
Proposed Solution
About this task
Check log detail and related service functionality.
P_AMS07039
Event Type ERROR
Event text Engine State Error
Problem description
An engine failed to transition from an intermediate state.
Proposed Solution
About this task
Report incident
P_AMS07040
Event Type ERROR
Event text Invalid State Change
Problem description
An invalid engine state change was requested.
P_AMS07042
Proposed Solution
About this task
Report incident
P_AMS07042
Event Type ERROR
Event text Invalid Remote Media
Problem description
An error occurred processing remote audio media SDP.
Proposed Solution
About this task
Check logs for improperly formatted SDP from an attempted client connection.
P_AMS07043
Event Type ERROR
Event text Invalid Record State
Problem description
A Record request was issued to an engine in a state that cannot perform the request.
P_AMS events
Proposed Solution
About this task
P_AMS07044
Event Type ERROR
Event text MRCP Resource Failed
Problem description
A provisioned MRCP resource is not responding and is unavailable.
Proposed Solution
About this task
Use log detail to identify the failed MRCP resource and either repair the resource or remove it
from any containing pool.
P_AMS07045
Event Type ERROR
Event text Unsupported Audio Sample Rate. Sampling rate of

<rate> is unsupported. The resource was <resource
name>.
P_AMS07100
Problem description
A prompt resource is encoded with a sampling rate that is not supported by the platform.
Proposed Solution
About this task
The media file should be re-sampled to a rate of 8KHz before being used with the platform.
P_AMS07100
Event Type WARNING
Event text Engine Lease Error
Problem description
A request was received for an engine that has been released.
Proposed Solution
About this task
P_AMS07101
Event Type WARNING
Event text Invalid Adjust State
P_AMS events
Problem description
An Adjust request was issued for an engine in a state that cannot process an adjust.
Proposed Solution
About this task
There must be a prompt in progress for an Adjust to succeed. Check related service
functionality.
P_AMS07102
Event Type WARNING
Event text Invalid Transaction Identifier
Problem description
An invalid TID was received.
Proposed Solution
About this task
Report incident
P_AMS07103
Event Type WARNING
Event text Engine Recovered
P_AMS07104
Problem description
An engine was recovered following a remote component failure.
Proposed Solution
About this task
Identify and report the component failure event.
P_AMS07104
Event Type WARNING
Event text AVI File Read Error
Problem description
An AVI file was unreadable.
Proposed Solution
About this task
Locate the resource that could not be opened and verify that the file is valid.
P_AMS07105
Event Type WARNING
Event text MRCP Resource Allocation Failure
P_AMS events
Problem description
An MRCP resource request failed.
Proposed Solution
About this task
Check the MRCP pool configuration and related resource availability.
P_AMS07200
Event Type INFO
Event text Component Initialized
Problem description
The IvrMP process is initialized.
Proposed Solution
About this task
No action.
P_AMS07201
Event Type INFO
Event text Component Terminated
P_AMS07202
Problem description
The IvrMP process has been terminated.
Proposed Solution
About this task
No action.
P_AMS07202
Event Type INFO
Event text Engine Sanity Timeout.
Problem description
An engine has timed out because of inactivity.
Proposed Solution
About this task
Report incident.
P_AMS07203
Event Type INFO
Event text Engine Pool Size Increased
P_AMS events
Problem description
An engine has been allocated.
Proposed Solution
About this task
No action.
P_AMS07204
Event Type INFO
Event text MRCP Resource Recovered
Problem description
A failed MRCP resource has been restored to active service.
Proposed Solution
About this task
No action.
P_AMS08002
Event Type INFO
Event Level Minor
Event text ConfMP Initialization Details: ConfMP Initialized
Trigger component ConfMP
P_AMS08003
Problem description
ConfMP Initialized.
Proposed Solution
About this task
P_AMS08003
Event Type INFO
Minor
Event text ConfMP Shutdown Details: ConfMP Shutting down
Problem description
ConfMP shut down.
Proposed Solution
About this task
P_AMS08004
Event Type INFO
Minor
Event text Conference shutdown details: confid=<confid>
P_AMS events
Problem description
Conference was shut down due to MSLink loss.
Proposed Solution
About this task
P_AMS08005
Event Type INFO
Event Level Minor
Event text Party shutdown Details: confid=<confid>

party=<partyid>.
Problem description
Party was shut down due to MS.
Proposed Solution
About this task
P_AMS08500
Event Type WARNING
Event text Unknown message Details: <hostname> : <message type>
P_AMS08501
Event Level Minor
Problem description
Proposed Solution
About this task
P_AMS08501
Event Type WARNING
p
Minor
Event text Connection Loss
Problem description
Proposed Solution
About this task
P_AMS08750
Event Type ERROR
Event text SWERR:Failed to start media timer
P_AMS events
Problem description
Proposed Solution
About this task
P_AMS09502
Event Type INFO
Event text Registration Successful. Domain: <d> Client: <c>

Client Version: <CV> Protocol: <p> Sid: <s> Tid:
<t>
Trigger component CStore
Problem description
Successful client connection to CStore.
Proposed Solution
About this task
P_AMS09506
Event Type INFO
Event text CStore Initialized or Shutdown
P_AMS09510
Problem description
CStore Initialized or Shutdown
Proposed Solution
About this task
P_AMS09510
Event Type INFO
Event text Timeout waiting for response from peer. Waited

<millisecs> ms tid: <t>
Problem description
CStore Peer Mirror messaging has timed out.
Proposed Solution
About this task
Check for network problems between CStore peers.
P_AMS09702
Event Type WARNING
Event text Auto Ingest Failed on file: <file>
P_AMS events
Problem description
Auto Ingest Failed.
Proposed Solution
About this task
P_AMS09704
Event Type WARNING
Event text Invalid filename format for Auto Ingest. Format

should be: =namespace=mailbox=filename.ext
Problem description
Invalid filename format for Auto Ingest
Proposed Solution
About this task
Use the correct format.
P_AMS09706
Event Type WARNING
Event text Get File by HTTP Failed. Unable to open URL: <url>
P_AMS09708
Problem description
Access of content to be ingested through HTTP has failed.
Proposed Solution
About this task
Check network or notify next level support.
P_AMS09708
Event Type WARNING
Event text Unable to read URL: <url> and save to <filename>.
Problem description
Ingest of content through HTTP has failed.
Proposed Solution
About this task
Check network or notify next level support
P_AMS09802
Event Type ERROR
Event text Registration Failed. Incompatible versions.

Received: <version> Expected: <version> Domain: <d>
Client: <c> Client Version: <cv> Protocol: <p> Sid:
<s> tid: <t>
P_AMS events
Problem description
Incompatible connection attempt to the CStore
Proposed Solution
About this task
Upgrade client software
P_AMS09902
Event Type ERROR
Event text SWERR: Content delivery request failed to enqueue

for <cntid>
Problem description
Email delivery of requested content failed.
Proposed Solution
About this task
P_AMS14000
Event Type INFO
Event text StreamSource Initialized
P_AMS14001
Trigger component StreamSource
Problem description
Proposed Solution
About this task
P_AMS14001
Event Type INFO
Event text StreamSource Shutting down
Problem description
Proposed Solution
About this task
P_AMS14002
Event Type ERROR
Event text The IvrMP connection has dropped for server.
Problem description
P_AMS events
Proposed Solution
About this task
P_AMS14003
Event Type WARNING
Event text New IvrMP connection has been made
Problem description
Proposed Solution
About this task
P_AMS14004
Event Type INFO
Event text Changes to channel [<sessionId>] detected.
Problem description
P_AMS14005
Proposed Solution
About this task
P_AMS14005
Event Type ERROR
Event text RSS URL Fetch/Process Failed: <sessionId>
Problem description
Proposed Solution
About this task
P_AMS14006
Event Type INFO
Event text RSS URL Fetch/Process Failed: <sessionId>
Problem description
P_AMS events
Proposed Solution
About this task
P_AMS14007
Event Type ERROR
Event text RSS XML document parsing failed. Check document

format.
Problem description
Proposed Solution
About this task
P_AMS14008
Event Type ERROR
Event text RSS URL fetch failed. File is invalid: <sessionId>
P_AMS14009
Problem description
Proposed Solution
About this task
P_AMS14009
Event Type WARNING
Event text RSS channel parsing revealed no valid items.
Problem description
Proposed Solution
About this task
P_AMS14010
Event Type INFO
Event text SHOUTCast Configuration Updated: Primary URL:

<sessionId> Backup URL: <sessionId> Key: <sessionId>
P_AMS events
Problem description
Proposed Solution
About this task
Chapter 29: P_AMS Alarms
P_AMS_0300
Event text Internal Component Shutdown
Problem description
Proposed Solution
About this task
P_AMS_0301
Event text Pool Unavailable (SIPMC)
Problem description
Invalid or missing node configuration for available SIP UserAgent (SIPMC) process.
P_AMS Alarms
Proposed Solution
About this task
Verify the configuration of SIP UserAgent (SIPMC) within the cluster and if a SIP UserAgent
(SIPMC) is running.
P_AMS_0302
Event text Pool Unavailable (ContentStore)
Problem description
Invalid or missing node configuration for available Content Store (CStore) process.
Proposed Solution
About this task
Verify the configuration of Content Store (CStore) within the cluster and if a Content Store
(CStore) is running.
P_AMS_0303
Event text Pool Unavailable (ConferenceMediaProcessor)
P_AMS_0304
Problem description
Invalid or missing node configuration for available ConferenceProcess or process.
Proposed Solution
About this task
Verify configuration of Conference Media Processor (ConfMP) within the cluster and if a
Conference Media Processor (ConfMP) is running.
P_AMS_0304
Event text Pool Unavailable (IVRMP)
Problem description
Invalid or missing node configuration for available process.
Proposed Solution
About this task
Verify configuration of IVR Media Processor (IvrMP) within the cluster and if an IVR Media
Processor (IvrMP) is running.
P_AMS_0305
Event text Platform Locked
P_AMS Alarms
Problem description
The Avaya Media Server platform has been locked and does not accept new calls.
Proposed Solution
About this task
Unlock the Avaya Media Server platform.
P_AMS_0306
Event text Primary CPLINK Connection Failed
Problem description
The secondary Shared Global Context connection is in use because the primary connection
is down.
Proposed Solution
About this task
Verify network connectivity and status of primaryAvaya Media Server platform.
P_AMS_0307
Event text All CPLINK Connections Are Down
P_AMS_0308
Problem description
Both the primary and secondary Shared Global Context connection is down.
Proposed Solution
About this task
Configure a valid license key and restart the Avaya Media Server platform.
P_AMS_0308
Event text Missing License Key
Problem description
There are no license keys which are configured for the Avaya Media Server.
Proposed Solution
About this task
Verify network connectivity and status of primary and secondary Avaya Media Server
platform.
P_AMS_0309
Event text Invalid License Key
P_AMS Alarms
Problem description
The configured license key is not valid.
Proposed Solution
About this task
P_AMS_0310
Event text Applications are locked
Problem description
One or more configured applications are locked.
Proposed Solution
About this task
Unlock any locked applications.
P_AMS_0311
Event text Multiple license servers are active
P_AMS_0312
Problem description
Redundant license servers may have restarted, or may not be properly configured.
Proposed Solution
About this task
This condition can occur when a redundant license server has been restarted, or, when
redundant license servers are improperly configured.
When there is no configuration error, the warning clears itself when any existing licenses
on this node are refreshed.
If there is a configuration error, then this warning persists until you correct the license
server configuration on this node and restart the Avaya Media Server.
P_AMS_0312
Event text License Threshold Reached
Problem description
A license has exceeded the provisioned license alarm threshold percentage.
Proposed Solution
About this task
Reconfigure the system with additional licenses or servers to avoid an out of license condition
during periods of high demand.
P_AMS_0313
P_AMS Alarms
Event text License Exhausted
Problem description
A license resource is exhausted.
Proposed Solution
About this task
Reconfigure the system with additional licenses or servers to avoid out of license conditions
during periods of high demand.
P_AMS_0314
Event text Platform Pending Locked
Problem description
The Avaya Media Server platform has been pending locked and does not accept new calls.
Proposed Solution
About this task
Unlock the Avaya Media Server platform.
P_AMS_0315
P_AMS_0316
Event text Applications are pending locked
Problem description
One or more configured applications is pending locked.
Proposed Solution
About this task
Unlock all pending locked applications.
P_AMS_0316
Event text Diameter Not Licensed
Problem description
Diameter is enabled but is not licensed.
Proposed Solution
About this task
Configure a Diameter license or disable Diameter in the system configuration.
P_AMS_0317
P_AMS Alarms
Event text Foreign server connected to cluster
Event level Major event
Problem description
A foreign server not provisioned in the cluster is connected to the cluster link connection of this
server.
Proposed Solution
About this task
Verify the cluster configuration. If correct, identify the foreign server from the event log and
verify its configuration.
P_AMS_0318
Event text MAS instance is not licensed
Event level Critical event.
Problem description
Either no license key has been configured or the license key does not contain a valid instance
license for MAS.
Proposed Solution
About this task
P_AMS_0319
P_AMS_0319
Event text Backup server not synchronized.
Problem description
This inactive server is not synchronized with its peer active server.
Proposed Solution
About this task
This inactive server is not synchronized with the peer active server.
P_AMS_0320
Event text Internal Component Shutdown (SIPMC)
Trigger component SIP UserAgent (SIPMC)
Problem description
Proposed Solution
About this task
P_AMS Alarms
P_AMS_0321
Event text SIP Offline
Problem description
SIP incorrect configuration or SIP IP/Port is in use.
Proposed Solution
About this task
Verify SIP IP or Port Configuration and restart the Avaya Media Server platform.
P_AMS_0322
Event text Session Controller Connection Lost
Problem description
The session controller has been shutdown.
Proposed Solution
About this task
Verify if Session Controller (SC) is running.
P_AMS_0323
P_AMS_0323
Event text All configured SIP routes are down
Problem description
All the defined SIP routes are determined unavailable.
Proposed Solution
About this task
Verify route settings and network connectivity to the proxy.
P_AMS_0324
Event text At least one SIP domain unroutable
Problem description
At least one configured domain does not have SIP routes detected online.
Proposed Solution
About this task
Verify the route settings and network connectivity to the proxy.
P_AMS Alarms
P_AMS_0325
Event text Missing SIP TLS Configuration or Certificate
Problem description
SIP TLS is enabled without certificate provisioning or SIP TLS is disabled under media security
enforced policy.
Proposed Solution
About this task
Verify certificate provisioning, media security policy, and TLS transport configuration.
P_AMS_0330
Event text Internal Component Shutdown (IvrMP)
Problem description
Proposed Solution
About this task
P_AMS_0331
P_AMS_0331
Event text MRCP Resources Locked
Problem description
All MRCP resources are locked.
Proposed Solution
About this task
Unlock all the locked MRCP resources or all the associated resource types (a resource must
have a defined type before it raises an alarm).
P_AMS_0332
Event text MRCP Resource locked.
Problem description
One or more MRCP resources are locked.
P_AMS Alarms
Proposed Solution
About this task
Unlock all the locked MRCP resources or all the associated resource types (a resource must
have a defined type before it raises an alarm).
P_AMS_0333
Event text Internal Component Startup (IvrMP)
Problem description
The Avaya Media Server IvrMP is initializing.
Proposed Solution
About this task
This alarm is cleared when the IVR Media Processor (IvrMP) component completes
initialization.
P_AMS_0334
Event text MRCP Resource Failed (IvrMP)
P_AMS_0340
Problem description
One or more MRCP resources have failed health checks.
Proposed Solution
About this task
Restore proper functionality of MRCP resources or deactivate or remove them from the pool.
P_AMS_0340
Event text Internal Component Shutdown (ConfMP)
Trigger component Conference Media Processor (ConfMP)
Problem description
Proposed Solution
About this task
P_AMS_0341
Event text Hardware Performance Issue
P_AMS Alarms
Problem description
NIC driver problem, or other hardware performance issue.
Proposed Solution
About this task
Check for HyperThreading (which must be disabled), network driver, disk operations, and so
on.
P_AMS_0342
Event text ConfMP MSLINK Inactive
Problem description
Command link from SC is inactive
Proposed Solution
About this task
Verify if SC is operational.
P_AMS_0350
Event text Internal Component Shutdown (ContentStore)
Trigger component Content Store (CStore)
P_AMS_0351
Problem description
Proposed Solution
About this task
P_AMS_0351
Event text Storage Volume is Approaching Capacity
Problem description
The disk containing the Storage Root is at or near capacity.
Proposed Solution
About this task
Check disk space utilization on StorageRoot drive.
P_AMS_0352
Event text Mirror Messaging Connection Unavailable
P_AMS Alarms
Problem description
Content Store is configured with a Peer Master Content Store; but ContentStore is not
connected to Peer Master Content Store.
Proposed Solution
Procedure
1. Check mirror connection configuration through the console.

2. Check connectivity to peers.
3. If mirroring is not desired then clear the IP Address of Peer Master Content Store
parameter on the console.
P_AMS_0353
Associated alarm P_AMS_0353
Event text Data Synchronization in Progress
Problem description
Synchronization is in progress and that data may still be in the process of being copied with
the peer Content Stores.
Proposed Solution
About this task
Check the connections that are configured with peer Content Stores.
P_AMS_0354
P_AMS_0354
Event text Data Source Server Unavailable
Problem description
The connection to the Data Source server cannot be established.
Proposed Solution
About this task
1. Check the Data Source Server configuration through the Console.
2. Verify that the correct IP Address of the Data Source server is specified.
P_AMS_0360
Event text Internal Component Shutdown (StreamSource)
Problem description
Proposed Solution
About this task
P_AMS Alarms
P_AMS_0365
Event text Database Overload
Trigger component DB
Problem description
The platform database queue is too long, and there is database overload.
Proposed Solution
About this task
Contact next level of support.
P_AMS_0376
Event text The system is shutting down
Trigger component Start/Restart Manager (SRP)
Problem description
The Avaya Media Server service was intentionally stopped, or could not start successfully.
Proposed Solution
About this task
Wait until the Avaya Media Server service is completely stopped, then restart it.
P_AMS_0377
P_AMS_0377
Event text The system is down.
Problem description
The Avaya Media Server service was stopped.
Proposed Solution
About this task
Start or restart the Avaya Media Server service.
P_AMS_0378
Event text A component has terminated abnormally
Problem description
Dependent upon the specific component that is terminated.
Proposed Solution
About this task
Dependent upon the specific component that terminated.
P_AMS Alarms
P_AMS_0379
Event text A component could not be started
Problem description
The .exe file corresponding to the component could not be found in the Avaya Media Server
binaries folder, or the process creation system call failed.
Proposed Solution
About this task
1. Do one of the following:
Install the missing .exe file into the Avaya Media Server binaries folder.
Attempt to determine and resolve the system call failure.
2. Restart the Avaya Media Server service.
P_AMS_0380
Event text A component has exited too many times
Problem description
The possible cause is specific to the component.
P_AMS_0381
Proposed Solution
About this task
Determine the reason why the component is exiting and resolve the problem. Refer to alarm
and trace logs if available.
P_AMS_0381
Event text Disk space usage for a disk on the system has
exceeded the configured HWM
Problem description
Too many files are being maintained on the system, or some component or process is writing
continuously to the file system.
Proposed Solution
About this task
Delete any unnecessary files and verify that no component or process is writing continuously
to the file system.
P_AMS_0382
Event text CPU usage has exceeded the configured HWM
P_AMS Alarms
Problem description
Some components or processes are executing a tight loop without yielding the CPU, possibly
because it is deadlocked.
Proposed Solution
About this task
Determine which components or processes are using an excessive amount of CPU, and kill
those components or processes.
P_AMS_0383
Event text System integrity failure
Problem description
Refer to alarm and trace logs for possible causes.
Proposed Solution
About this task
Dependent upon the actual cause.
P_AMS_0384
Event text One or more network interface adapters have

disappeared from the network configuration
P_AMS_0385
Problem description
A network cable has come loose, unplugged, or faulty or the interface has been explicitly
disabled.
Proposed Solution
About this task
If not explicitly disabled, check the cable and its connections at both ends.
P_AMS_0385
Event text The system monitor thread failed to start. Disk and
CPU usage will not be monitored.
Problem description
The system is running with insufficient virtual memory.
Proposed Solution
About this task
Stop unnecessary processes or services and restart the Avaya Media Server service
P_AMS_0386
P_AMS Alarms
Event text WebLM Connection Failed.
Event level Critical alarm
Problem description
WebLM server is down or unreachable.
Proposed Solution
About this task
Check status of configured WebLM server, and verify network connectivity to the WebLM
server.
P_AMS_0387
Event text Missing Product License.
Trigger component Start/Restart Manager)(SRP)
Problem description
One or more configured products is not licensed on the WebLM server.
Proposed Solution
About this task
Check status of configured WebLM server, and verify network connectivity to the WebLM
server.
P_AMS_0388
P_AMS_0388
Event text Missing Feature License.
Event level Major alarm
Problem description
One or more configured features is not licensed on the WebLM server.
Proposed Solution
About this task
If required, configure the feature licenses on the WebLM server, else set the configured
maximum license count to 0 for unlicensed features.
P_AMS_0389
Event text Missing License Instance.
Event level Warning alarm
Problem description
One or more configured license instances could not be acquired.
P_AMS Alarms
Proposed Solution
About this task
Verify that the configured license counts are correct, and the configured amount is available
on the WebLM server.
P_AMS_0390
Event text Missing License Key. There are no license keys

configured for the AMS platform.
Problem description
There are no license keys configured.
Proposed Solution
About this task
Configure a valid license key.
P_AMS_0391
Event text Invalid License Key.
P_AMS_0392
Problem description
The configured license key is not valid.
Proposed Solution
About this task
Configure a valid license key.
P_AMS_0392
Event text License Server Shutdown.
Problem description
License Server has been shut down.
Proposed Solution
About this task
Start the License service.
P_AMS_0393
Event text License Server Passive Mode.
P_AMS Alarms
Problem description
License Server is in passive mode.
Proposed Solution
About this task
Check system configuration.
P_AMS_0394
Event text License Threshold Reached.
Problem description
One or more license keys reached or exceeded the license alarm threshold.
Proposed Solution
About this task
Reconfigure the system with additional licenses.
P_AMS_0395
P_AMS_0396
Event text License Exhausted.
Problem description
One or more license resources is exhausted.
Proposed Solution
About this task
Reconfigure the system with additional licenses.
P_AMS_0396
Event text License Expiry.
Problem description
One or more license keys will expire soon.
Proposed Solution
About this task
Check license expiration data, system date on the server, and if necessary, order a new
license.
P_AMS Alarms
P_AMS_0397
Event text License Expired.
Problem description
One or more license keys has expired.
Proposed Solution
About this task
Check license expiration data, system date on the server, and if necessary, order a new
license.
P_AMS_0398
Event text License Server Redundancy Connection Failure.
Problem description
The standby license server cannot open the ping connection to the active license server.
P_AMS_0399
Proposed Solution
About this task
Refer to license server trace log for failure reason. Check network connections and settings.
P_AMS_0399
Event text License Grace Period Active.
Problem description
Licenses have expired or WebLM server could not be contacted.
Proposed Solution
About this task
If licenses have expired, configure new licenses on the WebLM server.
If the licences have not expired, verify connectivity to the WebLM server.
P_AMS_1100
Event text Internal Component Shutdown (DiamC).
Trigger component DIAMETER
P_AMS Alarms
Problem description
The AMS platform has shut down.
Proposed Solution
About this task
Start the AMS platform.
P_AMS_1101
Event text Diameter Offline.
Problem description
The Diameter capability is unavailable.
Proposed Solution
About this task
Verify the Diameter configuration, and restart the AMS platform.
P_AMS_1102
Event text Session Controller Offline.
P_AMS_1103
Problem description
DiamC is not connected to the Session Controller.
Proposed Solution
About this task
Verify that the Session Controller is running.
P_AMS_1103
Event text Database Offline.
Trigger component DATABASE
Problem description
The connection with the Database is unavailable.
Proposed Solution
About this task
Verify that the Database is running.
P_AMS_1104
P_AMS Alarms
Event text Peer Route Offline.
Problem description
There is no Diameter peer route available.
Proposed Solution
About this task
Verify the route configuration and/or network.
P_AMS_1105
Event text Soap Server Offline.
Problem description
DiamC is not connected to the Soap Server.
Proposed Solution
About this task
Verify that the Soap Server is running.
P_AMS_1106
P_AMS_1106
Event text Diameter archive table is inconsistent, repairing.
Problem description
Database/machine was not shut down properly while writing was in progress.
Proposed Solution
About this task
Repair diameter archive table.
P_AMS_1107
Event text Missing Diameter TLS Configuration or Certificate.
Problem description
Diameter TLS is enabled without certificate provisioning.
P_AMS Alarms
Proposed Solution
About this task
Verify certificate provisioning and TLS transport configuration.
P_AMS_1120
Event text SoapServer Port Bind Failure.
Trigger component SOAP SERVER
Problem description
SoapServer Port is unavailable.
Proposed Solution
About this task
Close the application using the SoapServer port, or configure the SoapServer to use another
port.
P_AMS_9500
Event text One or more services is down.
Trigger component SYSTEM MONITOR
P_AMS_9501
Problem description
A critical system service was stopped or was unable to start successfully.
Proposed Solution
Procedure
1. Put the system in the Pending Lock state.

2. When the system is ready, restart the AMS Platform.
3. Unlock the AMS server.
4. Contact Avaya Support if the problem persists.
P_AMS_9501
Event text High Availability Peer Unavailable.
Problem description
The configured high availability peer is not responding.
Proposed Solution
Procedure
1. Verify that the configured high-availability peer is powered on and that Media Server
Status is Started.
2. Verify that the two servers are on the same subnet, and have network connectivity
between them.
3. Verify that the configured high-availability peer is paired with this server.
P_AMS Alarms
P_AMS_9502
Event text High Availability Service Address Failure.
Problem description
The IP address of the configured high availability service could not be configured for this
server.
Proposed Solution
Procedure
1. The IP address of the configured service may be in-use by another server on the
network.
2. Verify that the service address is not used and that the address is configured on the
connected LAN.
3. Verify that the service address mask is configured and valid for the LAN.
P_AMS_9503
Event text High Availability Server Shut Down.
P_AMS_9504
Problem description
The media server service on the configured high availability server is not running.
Proposed Solution
Procedure
1. Start the media service on the configured high availability server.

Or
2. Disable the high availability feature.
P_AMS_9504
Event text High Availability Configuration Error.
Problem description
The high availability service configuration is incorrect.
Proposed Solution
Procedure
1. Disable or re-configure the High Availability service.

2. When enabled, two servers must be configured using the Server Designation
screen. There must be one primary server and one backup server configured.
P_AMS Alarms

AEP Events and Associated Alarm

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AEP Events and Associated Alarm

Uploaded by

Copyright:

Available Formats

Avaya Aura Experience Portal events and

All non-Avaya trademarks are the property of their respective owners,

Contact Avaya Support

Chapter 1: Events and associated alarms overview........................................................ 37

Event text Added {0}

Event level Information event. No alarm is generated.

Trigger component Avaya Aura Experience Portal Administration

Event text Changed {0}

Event level Information event. No alarm is generated.

Trigger component Avaya Aura Experience Portal Administration

To inform users which server or component has been changed.

Event text Deleted {0}

Event level Information event. No alarm is generated.

Trigger component Avaya Aura Experience Portal Administration

Event text Unknown category

Event level Information event. No alarm is generated.

Trigger component Avaya Aura Experience Portal Administration

Event text EPM is starting up

Event level Information event. No alarm is generated.

Trigger component Avaya Aura Experience Portal Administration

Event text EPM is shutting down

Event level Information event. No alarm is generated.

Trigger component Avaya Aura Experience Portal Administration

Event text EPM has started

Event level Information event. No alarm is generated.

Trigger component Avaya Aura Experience Portal Administration

Event text Login

Event level Information event. No alarm is generated

Trigger component Avaya Aura Experience Portal Administration

Event text Logoff

Event level Information event. No alarm is generated

Trigger component Avaya Aura Experience Portal Administration

Event text Failed log-in attempt for user ({0})

Event level Information event. No alarm is generated.

Trigger component Avaya Aura Experience Portal Administration

Event text Account locked for user ({0})

Event level Information event. No alarm is generated.

Trigger component Avaya Aura Experience Portal Administration

The administrator resets the user password.

Associate alarm Name: QADMN01005

Event level Information event.

Trigger component Avaya Aura Experience Portal Administration

Event text Reset password for user ({0})

Event level Information event. No alarm is generated.

Trigger component Avaya Aura Experience Portal Administration

Event text User ({0}) changed password

Event level Information event. No alarm is generated.

Trigger component Avaya Aura Experience Portal Administration

Event text Added new user ({0}) for "{1}" role

Event level Information event. No alarm is generated.

Trigger component Avaya Aura Experience Portal Administration

Event level Information event. No alarm is generated.

Trigger component Avaya Aura Experience Portal Administration

Event text Deleted user ({0})

Event level Information event. No alarm is generated.

Trigger component Avaya Aura Experience Portal Administration

Event text Invalid Authentication File: {0}

Associate alarm Name: QADMN01011

Event level Error event.

Trigger component Avaya Aura Experience Portal Administration

Event text Starting all MPPs.

Event level Information event. No alarm is generated.

Trigger component Avaya Aura Experience Portal Administration

Event text Stopping all MPPs.