Information contained in this document is believed to be accurate and reliable at the time
of printing. However, due to ongoing product improvements and revisions, AudioCodes
cannot guarantee accuracy of printed material after the Date Published nor can it accept
responsibility for errors or omissions. Updates to this document can be downloaded from
This document is subject to change without notice.
Date Published: March-11-2021
WEEE EU Directive
Pursuant to the WEEE EU Directive, electronic and electrical waste must not be disposed of
with unsorted waste. Please contact your local recycling authority for disposal of this product.
Customer Support
Customer technical support and services are provided by AudioCodes or by an authorized
AudioCodes Service Partner. For more information on how to buy technical support for
AudioCodes products and for contact information, please visit our website at
AudioCodes continually strives to produce high quality documentation. If you have any
comments (suggestions or errors) regarding this document, please fill out the Documentation
Feedback form on our website at https://online.audiocodes.com/documentation-feedback.
Stay in the Loop with AudioCodes
Document Name
OVOC Documents
Migration from EMS and SEM Ver. 7.2 to One Voice Operations Center
One Voice Operations Center IOM Manual
One Voice Operations Center Product Description
- ii -
Notice
OVOC | Alarms Monitoring Guide
Document Name
One Voice Operations Center User’s Manual
Device Manager Pro Administrator's Manual
One Voice Operations Center Alarms Monitoring Guide
One Voice Operations Center Performance Monitoring Guide
One Voice Operations Center Security Guidelines
One Voice Operations Center Integration with Northbound Interfaces
Device Manager for Third-Party Vendor Products Administrator's Manual
Device Manager Agent Installation and Configuration Guide
ARM User’s Manual
Documents for Managed Devices
Mediant 500 MSBR User's Manual
Mediant 500L MSBR User's Manual
Mediant 500Li MSBR User's Manual
Mediant 500L Gateway and E-SBC User's Manual
Mediant 800B Gateway and E-SBC User’s Manual
Mediant 800 MSBR User’s Manual
Mediant 1000B Gateway and E-SBC User’s Manual
Mediant 1000B MSBR User’s Manual
Mediant 2600 E-SBC User's Manual
Mediant 3000 User’s Manual
Mediant 4000 SBC User's Manual
Mediant 9000 SBC User's Manual
Mediant Software SBC User's Manual
- iii -
Notice
OVOC | Alarms Monitoring Guide
Document Revision Record
LTRTDescription
41617
■ Added Teams Subscription Alarm; Teams Connection Alarm; UMP Users
Floating License Register Failure Alarm32
Floating License Failure to Send Usage Report Alarm33
Floating License Failure to Send Extended Usage Report Alarm33
Floating License Service Shutdown Alarm34
Floating License Manage Devices above Allow Maximum35
Floating License Registered Devices Requests Capacity35
Alarms Overflow36
Alarms Forward Overflow37
FQDN Resolve Event37
PM Timeout Event38
PM Token Pool is Empty39
PM Polling Status Event39
PM Batch Overflow Alarm42
PM Has No SNMP Connection43
FlexPool License Usage43
Teams Subscription Alarm44
Teams Connection Alarm46
UMP Users Scheduler Time Exceeded Alarm47
URI Exceeded Storing Limit Event48
Low IO Rate Performance Event49
4 Voice Quality Package Alarms51
OVOC QoE - Failed Calls Alarm51
OVOC QoE – Poor Voice Quality Alarm52
OVOC QoE - Average Call Duration Alarm54
OVOC QoE - License Key Alarm55
OVOC QoE - System Load Alarm56
Call Details Storage Level Change57
Call Quality Monitoring Connection Status Alarm58
OVOC QoE - Skype for Business SQL Server Connection Lost Alarm59
OVOC QoE - Active Directory Server Connection Lost Alarm60
OVOC QoE - Media Bandwidth Alarm60
OVOC QoE - Rule Max Concurrent Calls Alarm62
Report Schedulers Time Event63
Report Schedulers Load Alarm64
Report Schedulers Execution Event65
5 Device Manager Alarms66
Registration Failure Alarm66
IP Phone Survivable Mode Start Alarm66
IP Phone Lync Login Failure Alarm67
Endpoint License Alarm68
Endpoint Server Overloaded Alarm69
IP Phone Speaker Firmware Download Failure69
- vi -
Content
OVOC | Alarms Monitoring Guide
IP Phone Speaker Firmware Upgrade Failure70
IP Phone Conference Speaker Connection Failure71
IP Phone General Local Event71
IP Phone Web Successive Login Failure72
IP Phone Requires Reset73
Jabra Firmware Upgrade Failed74
VIP Endpoint is Not Registered or Offline74
VIP Endpoint is Disconnected75
Remote Control Battery Drained76
Remote Control is not Connected76
USB Port Shutdown due to over Current Exceeded77
6 OVOCManaged Devices Alarms79
Support Matrix79
Common Device Alarms92
Board Fatal Error92
Entity Configuration Change93
Configuration Error94
Initialization Ended95
Board Resetting Following Software Reset95
Feature Key Related Error96
Gateway Administrative State Changed96
No Free Channels Available98
Gatekeeper/Proxy not Found or Registration Failed99
Ethernet Link Down Alarm101
System Component Overloaded102
Active Alarms Table Overflow103
Operation State Change [Node]104
Keep Alive Trap105
NAT Traversal Alarm106
Enhanced BIT Status Trap107
Threshold of Performance Monitored Object Exceeded108
HTTP Download Result108
IPv6109
SAS Emergency Mode Alarm110
Software Upgrade Alarm111
NTP Server Status Alarm111
LDAP Lost Connection112
SSH Connection Status [Event]113
OCSP Server Status Alarm113
Media Process Overload Alarm114
Ethernet Group Alarm114
Media Realm BW Threshold Alarm115
71
73
- vii -
Content
OVOC | Alarms Monitoring Guide
Certificate Expiry Notification116
Web User Access Disabled117
Proxy Connection Lost117
IDS Policy Alarm119
IDS Threshold Cross Notification120
IDS Blacklist Notification121
Proxy Connectivity122
Web User Activity Log Trap123
HTTP Proxy Service Alarm124
Answer-Seizure Ratio Threshold Alarm125
Average Call Duration Threshold Alarm126
Network Effectiveness Ratio Threshold Alarm127
IP Group No Route Alarm128
TLS Certificate Expiry Alarm129
NGINX Configuration is not Valid131
NGINX Process is not Running132
Remote Monitoring Alarm132
SDR Server Alarm133
KPI Threshold Crossing134
Clock Configuration Alarm135
Debug Recording Activation Alarm135
Specific Hardware Alarms136
Temperature Alarm136
Fan Tray Alarm137
Power Supply Alarm138
HA System Alarms140
HA System Fault Alarm140
HA System Configuration Mismatch Alarm145
HA System Switch Over Alarm146
Hitless Software Upgrade Alarm146
Redundant Board Alarm147
HA Network Watchdog Status Alarm148
License Key Hitless Upgrade Alarm149
HA Network Mismatch Alarm150
HA Network Monitor Alarm151
HA Ethernet Group Alarm152
License Pool Alarms152
License Pool Infra Alarm152
License Pool Application Alarm154
License Pool Over Allocation Alarm155
Floating License Alarms156
Floating License Alarm - Not Enough Memory to Allocate 'Custom' Profile156
Cloud License Manager Alarm157
Flex License Manager Alarm160
Mediant 2600 E-SBCand Mediant 4000 Alarms SBC161
- viii -
Content
OVOC | Alarms Monitoring Guide
DSP Farms Mismatch Alarm161
Mediant 9000 and Software SBC Alarms162
Cluster HA Alarm162
Media Transcoder Network Failure163
Media Transcoder Software Upgrade Failure164
Media Transcoder High Temperature Failure165
Media Transcoder Fan Tray Module Failure166
Media Transcoder Power Supply Module Failure167
Cluster Bandwidth Utilization Alarm167
Media Cluster Alarm169
Remote Interface Alarm170
AWS Security Role Alarm171
CDR Server Alarm172
Metering Alarm173
MP-1288 Alarms174
Module Service Alarm174
Module Operation Alarm175
Port Service Alarm176
MSBR Alarms178
WAN Link Alarm178
Power Over Ethernet Status [Event]178
Wireless Cellular Modem Alarm179
Wireless Cellular Modem Status Changed180
Data Interface Status180
NQM Connectivity Alarm181
NQM RTT Alarm182
NQM Jitter Alarm182
NQM Packet Loss Alarm183
NQM MOS CQ Alarm184
NQM MOS LQ Alarm185
Mediant 3000 Hardware Alarms186
PEM Module Alarm186
SA Module Missing Alarm187
User Input Alarm188
TM Inconsistency188
TM Reference Status189
TM Reference Change190
PSTN Trunk Alarms190
D-Channel Status190
SONET Section LOF Alarm191
SONET Section LOS Alarm192
SONET Line AIS Alarm193
SONET Line RDI Alarm194
SONET/SDN IF Failure Alarm194
Trunk LOS Alarm195
- ix -
Content
OVOC | Alarms Monitoring Guide
Trunk LOF Alarm196
Trunk AIS Alarm197
Trunk RAI Alarm197
V5.2 Interface Alarm198
SONET Path STS LOP Alarm199
SONET Path STS AIS Alarm200
SONET Path STS RDI Alarm200
SONET Path Unequipped Alarm201
SONET Path Signal Label Alarm202
DS1 Line Status Alarm202
DS3 RAI Alarm204
DS3 AIS Alarm204
DS3 LOF Alarm205
DS3 LOS Alarm205
NFAS Group Alarm206
B Channel Alarm207
Analog Port Alarms208
Analog Port SPI Out of Service208
Analog Port High Temperature208
Analog Port Ground Fault Out-of-Service Alarm209
Dial Plan File Replaced Trap209
Analog Line Left Off Hook Alarm210
Microsoft Platform Alarms210
Component Unreachable211
Component Restart211
Component Performance Counter General212
Component Performance Counter Service213
Component Service Status214
Component Event Viewer215
Component Event Viewer Past Hours215
Component Event Viewer Dropped216
Certificate Expired217
CloudBond Disk Space218
User Management Pack 365 (UMP) Alarms219
UMP Tenant License Threshold Alarm219
UMP User License Threshold Alarm219
UMP Super Admin Authentication Fail Event220
UMP Azure AD Sync Alarm221
UMP Office 365 Failure Alarm222
UMP Office 365 Command Execution Event222
UMP User Settings Fail Event223
UMP End User Authentication Fail Event224
CloudBond 365 Alarms224
Commit License Failed224
Admin License Expired225
- x -
Content
OVOC | Alarms Monitoring Guide
CCE Appliance Alarms226
Alarm – Admin System Cloud Status226
CCEAppliance Certificate Expired Alarm227
CCE Wrong Operating Alarm228
CCE Wrong Settings Alarm229
CCE Disk Space Alarm230
CCE Windows License Alarm231
SBA Alarms232
Alarm – CPU Status232
SBA Memory Status233
SBADisk Space Alarm234
SBACertificate Expired235
Alarm – Performance Counter236
SBA Services Status Alarm237
SmartTAP Alarms238
Alarm – Component Unreachable238
SmartTAPEvent – Component Restart239
Event – Component Resource Failed239
Alarm - Component Resource Threshold Exceeded242
Alarm – Connection Failure244
Call Recording Error Event246
Alarm – Certificate Expired249
Alarm – Component Event Viewer Dropped249
Alarm – Component Performance Counter General250
Alarm – Component Service Status252
Alarm – Disk Space254
7 ARM Alarms255
Disk Size Illegal255
Disk Space Usage255
ARM License About to Expire256
ARM License has Expired257
ARM License Session Number258
ARM License Missing259
Quality Change259
ARM Configurator Reload260
ARM Router Reload261
ARMRouting Rule Match262
ARMConfiguration Inconsistency262
Operation State Changed (Router)263
Operation Status Changed [Node]265
Operation Status Changed [Peer Connection]267
Operation Status Changed [LDAP Server]268
Operational Status Changed [Active MQ]269
Limit Reached270
- xi -
Content
OVOC | Alarms Monitoring Guide
Router Using Other Configurator270
NTP Sync Status271
No Available Routers272
Registration Status Resync Threshold273
External Web Service274
Disk Usage Alarm275
CAC Usage277
- xii -
CHAPTER1Introduction
1Introduction
This document describes alarms that are raised on OVOC and its managed entities. These
alarms are displayed in the One Voice Operations Center Web interface Active Alarms table.
Supported alarms / events can fall into one of these three categories:
■ Standard traps: traps originated by the media gateway / server - all the standard traps are
treated are events.
■ Proprietary alarms / events: traps originated by the media gateway / server and defined in
the gateway proprietary MIB.
■ OVOC alarms / events: traps originated by OVOC application and defined in the OVOC
proprietary MIB.
To determine which traps are defined as Events refer to 'Alarm Name' or 'Alarm Title' fields in
the table. All the events are marked with [Event] prefix in the OVOC Active Alarms table and
Alarms History windows.
OVOC | Alarms Monitoring Guide
Each alarm / event described in this section includes the following information:
Alarm FieldDescription
Alarm Title (Name)The alarm name, as it appears in the OVOC Active Alarms and
History tables.
DescriptionDocumented description of the alarm.
SNMP Trap NameNOTIFICATION-TYPE Name as it appears in the MIB.
SNMP OIDNOTIFICATION-TYPE OID as it appears in the MIB. Corrective
Action Possible corrective action when applicable. - 1
Alarm SourcePossible values of sources if applicable to a specific alarm. This
value is displayed from the variable-binding
tgTrapGlobalsSource
Alarm TypeAlarm type according to ITU X.733 definition. This value is
displayed from the variable-binding tgTrapGlobalsType.
Probable CauseAlarm probable cause according to ITU X.733 definition. This
value is displayed from the variable-binding
tgTrapGlobalsProbableCause.
Additional InfoAdditional information fields provided by MG application,
depending on the specific scenario. These values are displayed
from tgTrapGlobalsAdditionalInfo1,
tgTrapGlobalsAdditionalInfo2 and
tgTrapGlobalsAdditionalInfo3. The document includes a few
- 1 -
CHAPTER1Introduction
Alarm FieldDescription
OVOC | Alarms Monitoring Guide
examples of the possible values of this field.
Alarm SeverityConditionText
Possible severity value
. This value is
displayed from the
variable-binding
tgTrapGlobalsSeverity.
Condition
upon which
the alarm is
raised for
the specific
severity.
There may
Textual description of specific
problem. This value is displayed
from the variablebinding
tgTrapGlobalsTextualDescriptio
n. The document includes a few
examples of the possible values
of this field.
be several
conditions
for each
severity.
Corrective
Action
Possible
corrective
action
when
applicable.
- 2 -
CHAPTER2 Standard Events
2Standard Events
Cold Start
Alarm FieldDescription
DescriptionSNMPv2-MIB: A coldStart trap signifies that the SNMP entity, supporting a
notification originator application, is reinitializing itself and that its
configuration may have been altered.
SNMP AlarmcoldStart
SNMP OID1.3.6.1.6.3.1.1.5.1
Alarm Title[Event] Cold Start
OVOC | Alarms Monitoring Guide
Alarm Source-
Alarm TypeCommunication Alarm
Probable
Cause
SeverityClear
Additional
Info1,2,3
Corrective
Action
Other
-
-
Link Down
Alarm FieldDescription
DescriptionSNMPv2-MIB: A linkDown trap signifies that the SNMP entity, acting in an
agent role, has detected that the ifOperStatus object for one of its
communication links is about to enter the down state from some other
state (but not from the notPresent state). This other state is indicated by
the included value of ifOperStatus.
SNMP Alarm[Event] linkDown
- 3 -
CHAPTER2 Standard Events
Alarm FieldDescription
SNMP OID1.3.6.1.6.3.1.1.5.3
Alarm TitleLink Down
Alarm TypeCommunication Alarm
Alarm Source-
OVOC | Alarms Monitoring Guide
Probable
Cause
SeverityMajor
Additional
Info1,2,3
Corrective
Action
Other
-
-
Link Up
Alarm FieldDescription
DescriptionSNMPv2-MIB: A linkUp trap signifies that the SNMP entity, acting in an
agent role, has detected that the ifOperStatus object for one of its
communication links left the down state and transitioned into some
other state (but not into the notPresent state). This other state is
indicated by the included value of ifOperStatus.
SNMP Alarm[Event] linkUp
SNMP OID1.3.6.1.6.3.1.1.5.4
Alarm TitleLink Up
Alarm Source-
Alarm TypeCommunication Alarm
Probable
Cause
SeverityClear
Additional-
Other
- 4 -
CHAPTER2 Standard Events
Alarm FieldDescription
Info1,2,3
OVOC | Alarms Monitoring Guide
Corrective
Action
-
Entity Configuration Change
Alarm FieldDescription
DescriptionEntity-MIB: An entConfigChange notification is generated when the value
of entLastChangeTime changes.
SNMP Alarm[Event] entConfigChange
SNMP OID1.3.6.1.2.1.47.2.0.1
Alarm TitleEntity Configuration Change
Alarm TypeEquipment Alarm
Alarm Source-
Probable
Cause
SeverityInfo
Additional
Info1,2,3
Corrective
Action
Other
-
-
Authentication Failure
Alarm FieldDescription
DescriptionSNMPv2-MIB: An authenticationFailure trap signifies that the SNMP entity
has received a protocol message that is no properly authenticated. While
all implementations of SNMP entities MAY be capable of generating this
trap, the snmpEnableAuthenTraps object indicates whether this trap will
be generated.
- 5 -
CHAPTER2 Standard Events
Alarm FieldDescription
SNMP Alarm[Event] authenticationFailure
SNMP OID1.3.6.1.6.3.1.1.5.5
Alarm TitleAuthentication Failure
Alarm Source-
Alarm TypeCommunication Alarm
OVOC | Alarms Monitoring Guide
Probable
Other
Cause
SeverityMajor
Additional
-
Info1,2,3
Corrective
-
Action
- 6 -
CHAPTER3 Management Alarms
3Management Alarms
EMS Trap Receiver Binding Error
Alarm FieldDescription
DescriptionThis alarm is generated during server startup if an error
occurs indicating that the SNMP trap receiver port is
already taken.
Corrective ActionRun netstats command to verify which application uses
the alarms reception port (by default UDP post 162).
■ OVOC application: If it's busy, check which application
uses this port. If it's not freed by OVOC application,
restart the OVOC server application as described in
the OVOC Server IOM.
■ Other network management application: change
OVOC application and all managed gateways' default
alarm reception ports.
Media GatewaysAll the gateways managed by OVOC
GW Connection Alarm
Alarm FieldDescription
DescriptionOriginated by OVOC when an SNMP Timeout occurs for the first time
in the Media Gateway.
- 7 -
CHAPTER3 Management Alarms
Alarm FieldDescription
SNMPAlarmacEMSNodeConnectionLostAlarm
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.3
Alarm TitleGW Connection Alarm
Alarm SourceMedia Gateway
Alarm TypeCommunications Alarm
Probable CauseCommunications Subsystem Failure
SeverityCritical
Additional InfoWhen an SBA is configured, displays the 'SBA Description' field.
Corrective ActionCommunication problem: Try to ping the gateway to check if there
OVOC | Alarms Monitoring Guide
is network communication.
■ Default gateway alive: Open the network screen. Check the
default gateway IP address and ping it.
■ SNMP Community Strings: Verify that the community string
defined in OVOC for the gateway matchs the actual gateway
community strings. To check the community string, right-click
on the gateway, select the 'Details' menu. Default community
strings: read = public, write = private.
■ Hardware Problem: Check that the gateway is alive according to
the LEDs. Verify that network and power cables are in place and
plugged in.
Media GatewaysAll the gateways managed by OVOC
GW Mismatch Alarm
Alarm FieldDescription
DescriptionActivated when OVOC detects a hardware, software, predefine or
configuration mismatch.
■ Software Mismatch: Activated when OVOC detects a software
version mismatch between the actual and the previous definition of
the Media Gateway (for example, Version 4.0.353 instead of the
previously defined 4.0.278). This is also the case when the new
version is not defined in the Software Manager.
- 8 -
CHAPTER3 Management Alarms
Alarm FieldDescription
SNMPAlarmacEMSNoMismatchNodeAlarm
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.9
Alarm TitleGW Mismatch Alarm
OVOC | Alarms Monitoring Guide
■ Hardware Mismatch: Activated when OVOC detects a hardware
mismatch between the actual and the previous definition of a Media
Gateway.
■ Configuration Mismatch: Activated when OVOC detects a
configuration mismatch between the actual parameter values
provisioned and previous parameter values provisioned.
Alarm Source
■ Media Gateway/Software
■ Media Gateway/Hardware
■ Media Gateway/Configuration
Alarm TypeEquipment Alarm
Probable
Other
Cause
SeverityClear
Additional Info-
Corrective
Action
■ Software Mismatch:
✔ Define the detected version in the OVOC Software Manager
✔ Perform a Software Upgrade on the gateway with one of the
supported versions.
■ Hardware Mismatch:
✔ Perform remove / add a device in order to resync OVOC and the
gateway status
✔ Verify in the Software Manager that an appropriate version
exists for the hardware type displayed in the error message
■ Configuration Mismatch:
✔ Run Configuration Verification command in order to compare
OVOC configuration and actual MG configuration:
-MG configuration is incorrect: use configuration download to
update MG with correct configuration saved in OVOC database.
- 9 -
CHAPTER3 Management Alarms
Alarm FieldDescription
OVOC | Alarms Monitoring Guide
-MG is correct, OVOC is not updated: use configuration upload
to save a correct MG configuration in OVOC database.
■ Check the Actions Journal for recent updates of the gateway.
Media
Gateways
All the gateways managed by OVOC.
Configuration Mismatch
Alarm FieldDescription
DescriptionThis alarm is raised when there are missing or incorrect parameters
values received from a managed entity.
SNMPAlarmacEMSConfigurationMismatchNodeAlarm
SNMP OID.1.3.6.1.4.1.5003.9.20.3.2.0.7
Alarm TitleConfiguration Mismatch
Alarm SourceOVOC Mgmt
Alarm TypeOther
Probable
Cause
SeverityMinor
Additional Info-
Corrective
Action
Other
-
OVOC Server Started
Alarm FieldDescription
DescriptionEvent raised each time the OVOC server is started or restarted (warm
DescriptionThe usage size (in %) on the disk partition of the #application type #ap-
plication name is ‘Dangerously High’ or ‘Almost Full’.
SNMPAlarmacEMSNotEnoughDiskSpaceAlarm
SNMPOID.1.3.6.1.4.1.5003.9.20.3.2.0.12
AlarmTitleDisk Space Alarm
AlarmTypeEquipment Alarm
AlarmSourceOVOC Mgmt
Probable CauseStorage Capacity Problem
Severity
■ More than 70% - minor
■ 80-90 – major
■ More than 90 - critical
Alarm Text{0}% of the disk is used in data partition. Free some disk space to avoid
system failure.
- 11 -
CHAPTER3 Management Alarms
Alarm FieldDescription
Additional Info
OVOC | Alarms Monitoring Guide
Corrective
Action
Free disk space
Software Replaced
Alarm FieldDescription
DescriptionOriginates when OVOC discovers a software version replace between
board versions, for example, from V4.6.009.004 to V4.6.152.003 (when
both versions are managed by OVOC ). Software Replace old version :
<old version> new version <new version>.
SNMPAlarmacEMSSoftwareReplaceAlarm-
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.14
Alarm Title[Event] Software Replaced
Alarm SourceOVOC Mgmt
Alarm TypeCommunications Alarm
Probable
Cause
SeverityInfo
Additional InfoIf you initiated a performance measurements polling process before
Corrective
Action
Media
Gateways
Other
you initiated the software replacement process, the polling process is
stopped.
No action should be taken; this is an information alarm.
All the gateways managed by OVOC.
Hardware Replaced
Alarm FieldDescription
DescriptionOriginated when OVOC discovers a different gateway (according to the
- 12 -
CHAPTER3 Management Alarms
Alarm FieldDescription
SNMP AlarmacEMSHardwareReplaceAlarm
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.15
Alarm Title[Event] Hardware Replaced
Alarm TypeEquipment Alarm
Alarm SourceMedia Gateway
OVOC | Alarms Monitoring Guide
MAC address) to what was initially defined, while the Hardware Type
remains the same.
Hardware Replace is discovered by the MAC address and performed
during Board Started trap.
DescriptionOriginated when HTTP access is disabled by OVOC hardening; however
OVOC manages media gateways that require HTTP access for software
upgrade. Originated on server startup.
SNMP AlarmacEMSHTTPDisabled
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.16
Alarm Title[Event] HTTP/HTTPS Access Disabled
Alarm TypeEnvironmental Alarm
- 13 -
CHAPTER3 Management Alarms
Alarm FieldDescription
Alarm SourceOVOC Mgmt
OVOC | Alarms Monitoring Guide
Probable
Cause
SeverityMajor
Additional
Info
Corrective
Action
Media
Gateways
Application Subsystem Failure
-
Separate the gateways between two OVOC servers (secured &
unsecured)
Gateways using the HTTP server for the software upgrade procedure:
MediaPacks, Mediant 1000, Mediant 2000, Mediant 3000
PM File Generated
Alarm FieldDescription
DescriptionOriginated when a PM file is generated in the OVOC server, and it can be
retrieved by a higher level management system.
SNMP AlarmacEMSPmFileGenerate
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.18
Alarm Title[Event] PM File Generated
Alarm SourceOVOC Mgmt
Alarm TypeOther
Probable
Cause
SeverityInfo
Additional
Info
Corrective
Action
Other
The performance summary data from<start polling interval time>
to<timeStempFileTo> of media gateway<nodeIPAdd> was saved in PM
file <fileName>.
-
- 14 -
CHAPTER3 Management Alarms
Alarm FieldDescription
OVOC | Alarms Monitoring Guide
Media
Gateways
All Gateways
PM Polling Error
Alarm FieldDescription
DescriptionOriginated when a History PM stops collecting performance summary
data from MG. Possible reasons are: NTP synchronization lost,
Connection Loss, SW Mismatch, etc.
SNMPAlarmacEMSPmHistoryAlarm
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.19
Alarm Title[Event] PM Polling Error
Alarm SourceOVOC Mgmt
Alarm TypeOther
Probable
Cause
SeverityMinor
Additional Info-
Corrective
Action
Other
Verify in the 'Description' (see above) the reason why the PM history
stopped.
■ When the reason is 'NTP synchronization lost', verify that the
gateway and the OVOC server machine are synchronized to the same
NTP server and have accurate time definitions.
■ When the reason is 'Software Mismatch', you can stop the PM
history collection until the new version is added to the Software
Manager.
■ When the reason is 'Connection Loss' between the OVOC server and
the gateway, polling continues automatically when the connection is
re-established; the purpose of the alarm in this case is to inform
users of missing samples.
Note: The alarm continues to activate every 15 minutes unless you fix
the problem or manually stop PM polling of the gateway.
- 15 -
CHAPTER3 Management Alarms
Alarm FieldDescription
OVOC | Alarms Monitoring Guide
Media Gateways
All Gateways
Cold Start Missed
Alarm FieldDescription
DescriptionOriginated when Carrier Grade Alarm System recognizes coldStart trap
has been missed.
SNMP AlarmacEMSNodeColdStartMissedEvent
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.20
Alarm Title[Event] Cold Start Missed
Alarm Source-
Alarm TypeOther
Probable
Cause
SeverityClear
Additional
Info
Corrective
Action
Media
Gateways
Receive failure
-
-
All the managed Gateways
GW Backup Event
Alarm FieldDescription
DescriptionThis alarm is raised when an AudioCodes device configuration file
cannot be retrieved due to insufficient disk space or periodic backup
operation failure.
SNMP AlarmacEMSMGBackupEvent
- 16 -
CHAPTER3 Management Alarms
Alarm FieldDescription
SNMP OID.1.3.6.1.4.1.5003.9.20.3.2.0.21
Alarm TitleGW Backup Event
Alarm Source<Device IP address>
Alarm TypeOther
Probable CauseOther
Additional Info-
OVOC | Alarms Monitoring Guide
Alarm SeverityConditionText
Minorperiodic backup
failed due to
insufficient disk
space
Minorperiodic
backupbackup
failed
Indeterminateperiodic backup
success
Security Alarm
Backup file from IP:{0} with MG
name: {1} was not retrieved
due to low OVOC Mgmt disk
space.
Periodic Backup operation
failed for MG {0}
with IP:{1}
backup file: {file} from ip: {ip}
with mg name: {name} was
successfully retrieved.
Corrective
Action
Check disk and
free some
space.
Alarm FieldDescription
DescriptionActivated when one or more RADIUS servers are not reachable. When
none of the RADIUSservers can be reached, a Critical Severity alarm is
generated.
SNMP AlarmacEMSSecurityAlarm
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.23
Alarm TitleSecurity Alarm
Alarm SourceOVOC Mgmt/ Radius <#>
- 17 -
CHAPTER3 Management Alarms
Alarm FieldDescription
Alarm TypeProcessing Error Alarm
OVOC | Alarms Monitoring Guide
Probable
Cause
SeverityMinor, Major, Critical
Additional
Info
Corrective
Action
Media Gateways
Other
-
-
-
Security Event
Alarm FieldDescription
DescriptionThis event is generated when a specific user is blocked after reaching the
maximum number of login attempts, or when the OVOC failed to sync
OVOC and Mediant 5000 / 8000 users.
SNMP AlarmacEMSSecurityEvent
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.24
Alarm Title[Event] Security Event
Alarm SourceOVOC Mgmt/ User Name,
OVOC Mgmt/ User Sync
Alarm TypeOther
Probable
Cause
SeverityIndeterminate
Additional
Info
Corrective
Action
Other
-
-
- 18 -
CHAPTER3 Management Alarms
Alarm FieldDescription
OVOC | Alarms Monitoring Guide
Media Gateways
-
Topology Update Event
Alarm FieldDescription
DescriptionThis event is issued by OVOC when a Gateway or Region is
added/removed/updated in OVOC and includes the following
information:
■ Action: Add / Remove / Update GW or Region
■ Region Name
■ GW Name
■ GW IP
Note: For opening an EMS client in the MG context, the gateway IP
address should be provided.
SNMPAlarmacEMSTopologyUpdateEvent
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.25
Alarm Title[Event] Topology Update
Alarm SourceOVOC Mgmt
Alarm TypeOther
Probable CauseOther
SeverityIndeterminate
Additional InfoAdditional Info 1 field will include following details:
Region: X1 'X2' [GW: Y1 'Y2' 'Y3' 'Y4']
X1 = Region ID (unique identifier in the OVOC data base used for region
identification)
X2 = Region name as it defined by OVOC operator
Y1 = GW ID (unique identifier in the OVOC data base used for GW
identification)
Y2 = GW Name as it defined by OVOC operator
Y3 = GW IP as it defined by OVOC operator
Y4 = GW Type as it identified by OVOCduring the first connection to the
- 19 -
CHAPTER3 Management Alarms
Alarm FieldDescription
OVOC | Alarms Monitoring Guide
gateway. If first connection was not successful during the add
operation, it will trigger an 'Add GW' event with Unknown GW type, and
'Update GW' event once the initial connection to the gateway has been
success full. The following gateways will be supported: MP,M1K, M2K,
M3K, M5K, M8K
Region details will always be part of the alarm, while GW info will be
displayed when event is gateway-related.
All the fields related to the gateway will always be displayed to allow
easy parsing.
DescriptionThis event is issued by OVOC when the Topology File is updated on the
OVOC server machine. The Topology file is automatically updated upon
the addition /removal of a Media Gateway or upon updates to the Media
Gateway properties. For more information, refer to the Northbound
Integration Guide.
SNMP NameacEMSTopologyFileEvent-
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.26
- 20 -
CHAPTER3 Management Alarms
Alarm FieldDescription
Alarm Title[Event] Topology File
Alarm SourceOVOC Mgmt
Alarm TypeOther
OVOC | Alarms Monitoring Guide
Probable
Cause
SeverityIndeterminate
Additional
Info
Corrective
Action
Media Gateways
Other
File Name: MGsTopologyList.csv
-
-
Synchronizing Alarms Event
Alarm FieldDescription
DescriptionThis event is issued when the OVOC is not able to retrieve the entire
missing alarms list from the History table. Information regarding the
number of retrieved alarms, and number of alarms OVOC failed to
retrieve is provided in the Additional Info field.
SNMPAlarmacEMSSyncAlarmEvent
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.27
Alarm Title[Event] Synchronizing Alarms
Alarm SourceOVOC Mgmt
Alarm TypeOther
SeverityIndeterminate
Probable
Cause
Additional InfoRetrieved x missed alarms, failed to retrieve y alarms.
Other
- 21 -
CHAPTER3 Management Alarms
Alarm FieldDescription
OVOC | Alarms Monitoring Guide
Corrective
Action
Media
Gateways
-
-
Synchronizing Active Alarms Event
Alarm FieldDescription
DescriptionThis event is issued when OVOC is not able to perform synchronization
with the History alarms table, and instead performs synchronization
with the Active Alarms Table.
SNMPAlarmacEMSSyncActiveAlarmEvent -
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.28
Alarm Title[Event] Synchronizing Active Alarms
Alarm SourceOVOC Mgmt
Alarm TypeOther
Probable
Cause
SeverityIndeterminate
Additional Info-
Corrective
Action
Media Gateways
Other
-
-
OVOC License Key Alarm
Alarm FieldDescription
DescriptionThis alarm is raised when the OVOC License key has expired or the OVOC
management license (License key) on the device is missing.
GW management is not
covered by current OVOC
Mgmt Application License
Suppressed Alarm <Name>
Alarm FieldDescription
DescriptionThis alarm is sent when the OVOC suppresses alarms (of the same alarm
type and alarm source), once the number of such alarms reaches a
configured threshold level in a configured interval (configured in the
- 23 -
CHAPTER3 Management Alarms
Alarm FieldDescription
SNMPAlarmacEMSAlarmSuppression
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.42
Alarm TitleThe name of the suppressed alarm
Alarm SourceOVOC Mgmt or OVOC QoE/<IP address_Managed Entity>
Alarm TextAlarm Suppression activated
Alarm TypeOther
OVOC | Alarms Monitoring Guide
OVOC Alarms Settings screen). When this alarm is sent, such alarms are
not added to the OVOC database and are not forwarded to configured
destinations.
Probable
Cause
SeverityIndeterminate
Status
Changes
Additional Info-
Corrective
Action
Threshold crossed.
The alarm is cleared when in the subsequent interval, the number of
such alarms falls below the configured threshold. Once the alarm is
cleared, then these alarms are once more added to the OVOC database
and forwarded to configured destinations.
Investigate the recurrence of such alarms.
OVOC Keep Alive Alarm
Alarm FieldDescription
DescriptionThis alarm indicates that an SNMP Keep-alive trap has been sent from
OVOC to a third-party destination such as a Syslog server to indicate
OVOC liveness (configured in the OVOC Alarms Settings window).
SNMP AlarmEMSKeepAliveAlarm
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.45
Alarm TitleOVOC Keep Alive Alarm
- 24 -
CHAPTER3 Management Alarms
Alarm FieldDescription
Alarm SourceOVOC Mgmt
Alarm TextManagement Keep-Alive
OVOC | Alarms Monitoring Guide
Default
Severity
Alarm TypeOther
Probable
Cause
Corrective
Action
Indeterminate
Other
-
Pre-provisioning Alarm
Alarm FieldDescription
DescriptionThis alarm is generated when the operation for pre-provisioning the
device upon initial connection to OVOC fails.
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.46
AlarmTitlePre-Provisioning
AlarmSourceOVOC Mgmt
AlarmTypeoperational/Violation
Probable CauseThe template file could not be applied to the device because there was a
mismatch between the template file and the device’s existing ini file or
there was a mismatch between the device type and the firmware file
applied to the device.
SeverityCritical
Additional Info-
Corrective
Action
■ When this alarm is raised, you cannot reload configuration or
firmware files to the device as it has already been connected to
OVOC. Instead download these files to the device using the Software
Manager and then use the 'Software Upgrade' action.
OR
- 25 -
CHAPTER3 Management Alarms
Alarm FieldDescription
OVOC | Alarms Monitoring Guide
■ Remove the device from OVOC and then reconnect it i.e. repeat the
pre-provisioning process.
Media Gateways
All gateways managed by OVOC.
Endpoint Publish Alarm
Alarm FieldDescription
DescriptionThis alarm is raised when problems arise with the SIP Publish reporting
for voice quality metrics (port 5060) from endpoints (RFC 6035).
■ When a SIP Publish message is missing mandatory parameter/s
required by OVOC to handle this message.
■ When SIP Publish message time is not synchronized with OVOC
DescriptionThis alarm is issued in one of the following cases:
- 26 -
CHAPTER3 Management Alarms
Alarm FieldsDescription
SNMP AlarmacEMSDiskSpaceAlarmCheck
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.51
AlarmTitleDisk Space Alarm
AlarmSourceOVOC Mgmt
AlarmTypeEquipment Alarm
Probable CauseStorage Capacity Problem
OVOC | Alarms Monitoring Guide
■ The Archive Logs directory capacity has reached {0}%.
■ The Oracle partition capacity has reached {0}%.
Severity
■ 70% < Minor
■ 80% < Major
■ 90% < Critical
Additional Info-
Corrective
Action
■ The Archive Logs directory: Free space in
/ACEMS/NBIF/emsBackup/DBEMS/archivelog/ to avoid system
failure.
■ The Oracle partition: Free space using the command rm -f
/oracle/DIAG/diag/rdbms/dbems/dbems/trace/*.tr* to avoid
system failure.
Media Gateways
-
Oracle Disk Space Alarm
Alarm FieldDescription
DescriptionThis alarm is issued when the Oracle partition capacity has reached
{0}%.of its disk capacity.
SNMP AlarmacEMSNotEnoughOracleSpaceAlarm
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.52
AlarmTitleOracle Disk Space Alarm
- 27 -
CHAPTER3 Management Alarms
Alarm FieldDescription
AlarmSourceOVOC Mgmt
AlarmTypeEquipment Alarm
Probable CauseStorage Capacity Problem
OVOC | Alarms Monitoring Guide
Severity
■ 70% < Minor
■ 80% < Major
■ 90% < Critical
Additional Info-
Corrective
Action
Media Gateways
Free space using the command rm -f
/oracle/DIAG/diag/rdbms/dbems/dbems/trace/*.tr* to avoid system
failure.
-
License Alarm
Alarm FieldDescription
DescriptionThis alarm is issued when the OVOC License approaches or reaches it's
expiration date or OVOC server machine ID is no longer valid.
SNMP AlarmacLicenseAlarm
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.53
Alarm TitleLicense Alarm
Alarm SourceOVOC Mgmt
Alarm TypeOther
Probable
Cause
Additional
Info
Other
Info1:
■ Machine ID In The License Is {0}
■ Expiration Date In The License Is {0}
- 28 -
CHAPTER3 Management Alarms
Alarm FieldDescription
OVOC | Alarms Monitoring Guide
Alarm
Severity
CriticalThe license
MajorThe license
Condition<text>Corrective Action
expiration
date is less
than equal to
7 days.
expiration
date is more
than 7 days
and less than
equal to 30
days.
■ OVOCLicense is
about to expire
in {0} days.
■ OVOC License is
about to expire
in 1 day.
■ OVOC License
Will Expire
Today
OVOC License is
about to expire in
{0} days.
Contact your AudioCodes partner ASAP. Note that when notification that this license has
expired is received, the server
remains connected for a few
minutes in order to allow the forwarding traps to northbound
destinations.
ClearThe license
expiration
date is
greater than
30 days.
Synchronizing Alarms
Alarm FieldDescription
DescriptionThis event is sent out to an SMMP NBI using user defined alarms
forwarding rules once the NMS has activated the ReSync Alarms feature.
SNMP Alarmac OCReSyncEvent
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.58
Alarm Title[Event] Synchronizing Alarms
Alarm SourceOVOC Mgmt
Alarm TypeOther
- 29 -
CHAPTER3 Management Alarms
Alarm FieldDescription
SeverityIndeterminate
OVOC | Alarms Monitoring Guide
Probable
Cause
Additional
Info
Corrective
Action
Media
Gateways
Other
-
-
-
QoE Sip Message Status Alarm
Alarm FieldDescription
DescriptionAlarm is raised when device notify OVOC that it stop sending SIP mes-
sages. cleared when it notify that it continue sending SIP messages
DescriptionThis alarm is raised when IP phones are added to OVOC and as a result
OVOC | Alarms Monitoring Guide
licenses are extended beyond the pre-existing tenant allocation; where
there are insufficient licenses currently allocated to the phone’s
designated tenant. In this case, OVOC checks the number of free
available licenses (licensees that are not assigned to any tenant) and
then takes 5% of the current tenant allocation (a minimum of five, or the
remaining licenses) and dynamically adds them to the phone’s tenant.
The licenses are taken from the OVOC License “Managed Endpoints”
feature license if the endpoint is managed by IP Phone Manager Pro or
from the “Voice Quality Endpoints" feature if the phones are managed in
the OVOC for Voice Quality (“QOE Supported” in OVOC Web). If both of
these license features are managed for the endpoint, the license is taken
according to the license availability for the respective tenant license
allocation. For example, if the endpoint is licensed for both of these
categories and there also insufficient licenses allocated for both
categories, then the dynamic license allocation is separately executed
and therefore separate events are raised.
SNMP AlarmfloatingLicenseExtended
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.61
Alarm TitleFloating License Extended
Alarm SourceThe tenant on which the license is extended.
Alarm TypeOther
SeverityIndeterminate (info)
Probable
Cause
Other
Floating License Device Report Alarm
Alarm FieldDetails
DescriptionThis alarm is raised when the device does not send a usage report for
[calc duration] minutes or more to OVOC.
SNMP AlarmacClmDeviceReportAlarm
- 31 -
CHAPTER3 Management Alarms
Alarm FieldDetails
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.62
Alarm TitleFloating license Device missing report
Alarm SourceFloating license/Device#[Device Id]
Alarm TypeCommunication
SeverityMajor
OVOC | Alarms Monitoring Guide
Probable
Cause
Other
Floating License Register Successful Event
Alarm FieldDescription
DescriptionThis alarm is raised when OVOC successfully registers to Floating License
at [DNS address].
SNMP AlarmacClmRegisterSuccessfulEvent
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.63
Alarm TitleFloating license Cloud Service registration successful
Alarm SourceFloating license
Alarm TypeCommunication
SeverityInfo
Probable
Cause
Other
Floating License Register Failure Alarm
Alarm FieldDescription
DescriptionThis alarm is raised when OVOC fails to register to Floating License Cloud
Service at [DNS address], Reason: [Error description or timeout]
SNMP AlarmacClmRegisterFailureAlarm
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.64
- 32 -
CHAPTER3 Management Alarms
Alarm FieldDescription
Alarm TitleFail to register to Cloud Service
Alarm SourceFloating license
Alarm TypeCommunication
SeverityCritical
OVOC | Alarms Monitoring Guide
Probable
Cause
Communications Protocol Error
Floating License Failure to Send Usage Report Alarm
Alarm FieldDescription
DescriptionThis alarm is raised when OVOC fails in two attempts to send usage
report to Floating LIcense Cloud Service Service. This service shuts down
if the problem not fixed by the configured period (default 90 days).
Note: this time period is configured by AudioCodes on the Floating
License Service.
SNMP AlarmacClmFailToSendUsageReportAlarm
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.65
Alarm TitleFailed to send usage report to Cloud Service
Alarm SourceFloating license
Alarm TypeCommunication
SeverityMajor
Probable
Cause
Communications Protocol Error
Floating License Failure to Send Extended Usage Report Alarm
Alarm FieldDescription
DescriptionThis alarm is raised when OVOC fails to send usage reports to the
Floating License Cloud Service . This alarm is raised one week prior to the
shutdown date (default90 days).
Note: this time period is configured by AudioCodes on the Floating
- 33 -
CHAPTER3 Management Alarms
Alarm FieldDescription
SNMP AlarmacClmFailToSendUsageReportExtendedAlarm
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.66
Alarm TitleFailed to send usage report to Floating License Cloud Service
Alarm SourceFloating license
Alarm TypeCommunication
Alarm TextOVOC failed to send usage report to Floating License Cloud Service.
SeverityCritical
OVOC | Alarms Monitoring Guide
License Service.
Service will shutdown if problem not fixed by 90 days
Probable
Cause
Communications Protocol Error
Floating License Service Shutdown Alarm
Alarm FieldDescription
DescriptionFloating License service shutdown, reason: failure to communicate with
cloud service for [(ovocNoResponseHours-144) *60/
ovocReportIntervalMin] minutes.
SNMP AlarmacClmServiceShutdownAlarm
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.67
Alarm TitleService Shutdown
Alarm SourceFloating license
Alarm TypeCommunication
SeverityCritical
Probable
Cause
Application Subsystem Failure
- 34 -
CHAPTER3 Management Alarms
Floating License Manage Devices above Allow Maximum
Alarm FieldDescription
DescriptionThis alarm is raised when the maximum number of devices managed by
the floating license is reduced to less than the currently registered count
(the number of devices that have registered to OVOC and the Floating
License service and are currently managed by the floating license). For
example, if there are 30 devices registered and are currently managed by
the floating license in OVOC, and then the maximum number of devices
supported by the license is reduced to 20 devices, then this alarm will be
raised.
approaching its maximum
value according to the setting
for the Flex Pool OVOC Web
Configuration parameter
"Alarm Threshold Percentage"
(default 85%).
FlexPool
license
parameter
[name] is over
license limit.
FlexPool
license
parameter
[name] is
approaching
maximum
utilization.
Corrective
Action
Renew floating
license or reduce
current
consumption.
Renew floating
license or reduce
current
consumption.
Teams Subscription Alarm
Alarm FieldDescription
DescriptionThis alarm is raised when the Teams Calls Notifications subscription cre-
ation or renewal process fails for any reason.
SNMP AlarmacTeamsSubscriptionAlarm
SNMP OID.1.3.6.1.4.1.5003.9.20.3.2.0.90
Alarm SourceOVOC Mgmt/Device
Alarm TitleTeams Subscription Alarm
Alarm TypeCommunications Alarm
Probable
Cause
Additional
Info1
Communications Subsystem Failure
Additional
Info2
- 44 -
CHAPTER3 Management Alarms
Alarm FieldDescription
OVOC | Alarms Monitoring Guide
Alarm
Severity
ConditionAlarm Text
CriticalFailed to renew
(create new
initial)
subscription,
when the
previously
created
subscription
has expired.
Failed to create
initial
subscription
MajorFailed to renew
subscription;
previously
created
subscription
has been active
for less than 24
hours (between
0 to 24 hours) .
Corrective
Action
Subscription failed. No active subscription exists
Subscription failed. Previously
created subscription is active for less
than 24 hours. Expires at DATETIME
MinorFailed to renew
subscription;
previously
created
subscription
has been active
for less than 48
hours (between
48 and 24
hours).
ClearSubscription
successfully
created or
renewed.
Subscription failed. Previously
created subscription is active for less
than 48 hours. Expires at DATETIME
Subscription created successfully.
Expires at DATETIME
- 45 -
CHAPTER3 Management Alarms
Teams Connection Alarm
Alarm FieldDescription
DescriptionThis alarm is raised when calls notifications cannot be received
SNMP AlarmacTeamsConnectionAlarm
SNMP OID.1.3.6.1.4.1.5003.9.20.3.2.0.89
Alarm SourceOVOC Mgmt/Device
Alarm TitleTeams Connection Alarm
Alarm TypeCommunications Alarm
OVOC | Alarms Monitoring Guide
from MS Cloud due to connection and Calls Notifications subscription issues.
Probable
Cause
Additional
Info1
Additional
Info2
Alarm
Severity
CriticalAny network
Communications Subsystem Failure
ConditionAlarm TextCorrective Action
connection issue
with Microsoft
Teams
Failure of MS Token
creation from
Microsoft Graph API
The Subscription
does not exist or
the expired
Connection to
Microsoft Teams
Cloud has been lost
Connection to
MS Teams
Cloud Has
Been Lost
■ Troubleshoot the
network
components such as
firewall, DNS,
certificates.
■ Verify that the client
credentials
configured for the
device added in
OVOC are identical
to those defined by
customer in Azure.
ClearThe network issue
is solved
Connection to
MS Teams
- 46 -
CHAPTER3 Management Alarms
Alarm FieldDescription
UMP Users Scheduler Time Exceeded Alarm
Alarm FieldDescription
DescriptionThis alarm is raised when there is a timeout for the Active Directory con-
OVOC | Alarms Monitoring Guide
Cloud Has
MS Token created
successfully after
failed attempts
New subscription
created/renewed
successfully
nection and when this action fails for UMP for a specific customer.
Been Established
SNMP AlarmacUMPUsersSchedulerAlarm
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.86
Alarm Source
■ OVOC QoE/UMP User Sync
■ OVOC QoE/ 'name of the specific customer'
Alarm TitleUMP Users Scheduler Time Exceeded Alarm
Alarm TypeProcessing Error Alarm
Probable
Cause
■ If cause type is CLEARED:
✔ UMP Users sync task was restarted
✔ UMP Users sync task for customer: 'name of the specific
customer' was restarted.
■ If cause type is not CLEARED:
✔ UMP Users sync task was terminated due to exceeded time
running.
Additional
Info1
Additional
Info2
✔ UMP Users sync task for customer: 'name of the specific
customer' was failed.
- 47 -
CHAPTER3 Management Alarms
Alarm FieldDescription
OVOC | Alarms Monitoring Guide
Alarm SeverityConditionAlarm Text
Minor
ClearedUMPUser
■ UMPusers
synchronization
timeout
■ UMP users
synchronization
for a specific
customer failed
Synchronization
success full
■ UMP Users sync task was
■ UMP Users sync task for
■ UMP Users sync task was
■ UMP Users sync task for
URI Exceeded Storing Limit Event
terminated due to
exceeded time running
customer: 'name of the
specific customer' was
failed.
restarted
customer: 'name of the
specific customer' was
restarted.
Corrective
Action
Check the
connection
with the Active Directory.
Alarm FieldDescription
DescriptionThis alarm is raised when the URI Storing Limit of 2000 has been
exceeded.
SNMP AlarmacURIExceededStoringLimitEvent
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.87
Alarm SourceOVOC Mgmt/URI Summary
Alarm TitleURI Exceeded Storing Limit Event
Alarm TypeProcessing Error Alarm
Probable
Cause
Additional
Info1
Additional
Info2
Other
- 48 -
CHAPTER3 Management Alarms
Alarm FieldDescription
OVOC | Alarms Monitoring Guide
Alarm
Severity
WarningCount of
ConditionAlarm Text
URI Storing Limit of 2000 was exceeded.Reduce the
Caller and
Callee URI's
that
matched
the
provided
regexp has
exceeded
the limit.
Low IO Rate Performance Event
Alarm FieldDescription
Corrective
Action
storing
limit. Note
that this
value
cannot be
changed by
users as it is
a system
property
value.
DescriptionThis alarm is raised when the I/O rate falls below the expected rate and as
a result reduces disk speed. For example, an I/O rate decreases to 27.9
MB/s. The OVOC server runs dd command each watchdog iteration
(every 30 sec) in case the I/O rate falls below the expected I/O rate.
SNMP AlarmacLowIORatePerformanceEvent
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.88
Alarm SourceOVOC Mgmt
Alarm TitleLow IO Rate Performance Event
Alarm TypeCommunications Alarm
Probable
Cause
Additional
Info1
Other
Example: Expected I/O rate 160 MB/s sent from 10.3.180.194
Additional
Info2
Alarm
Severity
ConditionAlarm TextCorrective Action
- 49 -
CHAPTER3 Management Alarms
Alarm FieldDescription
OVOC | Alarms Monitoring Guide
CriticalThe I/O rate(
calculated by
the dd command) fell
10% below
the expected
I/O rate.
MajorThe I/O rate(
calculated by
the dd
command)
fell 40%
below the
Expected /IO
rate.
I/O rate decreased to xx MB/Check network
and storage performance.
I/O rate decreased to xx MB/sCheck network
and storage
performance.
- 50 -
CHAPTER4 Voice Quality Package Alarms
4Voice Quality Package Alarms
OVOC QoE - Failed Calls Alarm
Alarm FieldDescription
DescriptionThis alarm is raised when the % number of failed calls for
the managed node or link crosses the threshold and is
cleared when the failed calls ratio returns below the
threshold value. The description field includes the info:
Failed X1% of calls, X2 of X3 calls.
The threshold for this alarm is set in the QoE Status and
Alarms Details window.
SNMPOIDacVoice QualityRuleFailedCallsAlarm
OVOC | Alarms Monitoring Guide
SNMPAlarm1.3.6.1.4.1.5003.9.20.3.2.0.30
Alarm TitleVoice Quality - Failed Calls Alarm
Alarm SourceOVOC QoE/Device/Link/Site/Endpoint
Alarm TypeQuality of service alarm.
Probable
Cause
Additional InfoCritical or Major severity threshold is Y%:
The minimum or maximum threshold is crossed.
■ Critical Threshold: 10 % of calls (default)
■ Major Threshold: 2 % of calls (default)
Where Y% is the % failed calls per managed node or link
that is measured for a total time of 180 minutes period
(three hours) and according to “Monitoring Frequency
Min”. For example, if this parameter is set to 15 minutes,
sampling is performed at 15:15 (from 12:15 to 15:30) and
then at 15:30 (from 12:30 to 15:30) and so on.
Alarm SeverityConditionText
CriticalThis alarm is raised
when Y % of calls (representing the configured critical
Y% of failed
calls has
crossed the
"Critical"
- 51 -
Corrective
Action
Investigate
the source
(device or link)
of the failed
CHAPTER4 Voice Quality Package Alarms
Alarm FieldDescription
OVOC | Alarms Monitoring Guide
threshold) made by
the managed node or
link for the sampled
period fail (see above).
MajorThis alarm is raised
when Y % of calls (representing the configured major
threshold)made by
the managed node or
link for the sampled
period fail (see above).
ClearCleared when the
failed calls ratio
returns below the
threshold value for
the sampled period.
thresholdcalls.
Y% number of
failed calls for
has crossed
the "Major"
threshold.
-
OVOC QoE – Poor Voice Quality Alarm
Alarm FieldDescription
DescriptionThis alarm is raised when the % number of poor quality
calls polled for the managed node or link crosses the
threshold and is cleared when the poor quality calls ratio
returns below the threshold value. The description field
includes the info: Poor Quality X1% of calls, X2 of X3 calls.
The threshold for this alarm is set in the QoE Status and
Alarms Details window.
SNMPOID1.3.6.1.4.1.5003.9.20.3.2.0.31
SNMPAlarmacVoiceQualityRulePoorQualityCallsAlarm
Alarm TitleVoice Quality – Voice Quality Alarm
Alarm SourceOVOC QoE/Device/Link/Site/Endpoint
Alarm TypeQuality of service alarm
Probable
Cause
The minimum or maximum threshold is crossed.
- 52 -
CHAPTER4 Voice Quality Package Alarms
Alarm FieldDescription
Additional InfoCritical or Major severity threshold is Y%:
■ Critical Threshold: 10% of calls (default).
■ Major Threshold: 2% of calls (default)
Where Y% is the % poor quality calls per managed node or
link that is measured for a total time of 180 minutes
period (three hours) and according to “Monitoring
Frequency Min”. For example, if this parameter is set to 15
minutes, sampling is performed at 15:15 (from 12:15 to
15:15) and then at 15:30 (from 12:30 to 15:30) and so on.
OVOC | Alarms Monitoring Guide
Alarm SeverityConditionText
CriticalThis alarm is raised
when Y% (representing
the configured critical
threshold) of calls
Y% calls have
crossed the
"Critical"
threshold.
made by the managed
node or link for the
sampled period (see
above)are of poor
quality.
MajorThis alarm is raised
when Y %
(representing the
configured major
Y% calls have
crossed the
"Major"
threshold.
threshold) of calls by
the managed node or
link for the sampled
period (see above)are
of poor quality.
Corrective
Action
Investigate
the source
(device or link)
of the poor
quality calls.
ClearCleared when the poor
quality calls ratio
returns below the
threshold value for the
sampled period (see
above).
- 53 -
-
CHAPTER4 Voice Quality Package Alarms
OVOC QoE - Average Call Duration Alarm
Alarm FieldDescription
DescriptionThis alarm is raised when the average call duration time
threshold for the managed node or link is crossed and is
cleared when the average call duration time ratio returns
below the threshold value. The description field includes
the info: Average Call Duration is Y sec.
The threshold for this alarm is set in the QoE Status and
Alarms Details window.
Alarm TitleVoice Quality – Average Call Duration Alarm
OVOC | Alarms Monitoring Guide
Alarm SourceOVOC QoE/Device/Link/Site/Endpoint
Alarm TypeQuality of service alarm
Probable
Cause
Additional Info
The minimum or maximum threshold is crossed.
■ Critical Threshold: average call duration of 3 seconds
(default).
■ Major Threshold: average call duration of 5 seconds
(default)
Where measured per managed node or link for a total
time of 180 minutes period (three hours) and according to
“Monitoring Frequency Min”. For example, if this
parameter is set to 15 minutes, sampling is performed at
15:15 (from 12:15 to 15:15) and then at 15:30 (for 12:3015:30) and so on.
Alarm SeverityConditionText
Corrective
Action
CriticalThis alarm is raised
when the average call
duration for the
managed node or link
for the sampled period
(see above)falls to the
configured critical
- 54 -
Average Call
Duration
"Critical"
threshold
has been
reached.
Investigate
the source
(device or
link)
reporting the
excessive
average call
CHAPTER4 Voice Quality Package Alarms
Alarm FieldDescription
threshold value.duration.
OVOC | Alarms Monitoring Guide
MajorThis alarm is raised
when the average call
duration for the
managed node or link
for the sampled period
(see above)falls to the
configured major
threshold value.
ClearCleared when the
average call duration
returns below the
threshold value for the
sampled period (see
above)
Average Call
Duration
"Major"
threshold
has been
reached.
OVOC QoE - License Key Alarm
Alarm FieldDescription
-
DescriptionThis alarm is sent in the following circumstances:
■ When the number of devices connected to the OVOC approaches or
reaches license capacity (shown as 'Devices Number' in OVOC server
Manager License screen).
■ When the number of sessions running on the OVOC approaches or
reaches license capacity (shown as 'Voice Quality Sessions' in the
OVOC Server Manager License screen).
SNMP AlarmacVoice QualityLicenseKeyAlarm
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.33
Alarm TitleVoice Quality License key alarm
Alarms
Source
Alarm TypeOther
Probable
Cause
OVOC QoE
Key Expired
- 55 -
CHAPTER4 Voice Quality Package Alarms
Alarm FieldDescription
Additional
Info
OVOC | Alarms Monitoring Guide
Corrective
Action
Alarm
Severity
CriticalThe number of currently running ses-
MajorThe number of currently running
Contact your AudioCodes representitve to obtain the required license
key.
ConditionText
sions/devices has reached 100% of the
Voice Quality servers license capacity.
sessions/devices has reached 80% of
Voice Quality servers license capacity.
Current
server load
reached
100% of
VOICE
QUALITY
License capacity.
Current
server load
reached
80% of
Voice
Quality
License
capacity.
Corrective
Action
-
-
ClearThe number of currently running
sessions/devices has dropped below
80% of Voice Quality servers license
capacity.
Clearing
currently
active
device
alarm.
-
OVOC QoE - System Load Alarm
Alarm FieldDescription
DescriptionThis alarm is sent when the Voice Quality system capacity is high and the
system consequently becomes overloaded. Three levels are supported:
■ Major -> Events are not stored. Trend Info will not be displayed.
■ Critical -> Green calls are not stored.
■ Minor - > Events are not stored for green calls. Trend Info will not be
- 56 -
CHAPTER4 Voice Quality Package Alarms
Alarm FieldDescription
SNMP AlarmacVoice QualityCallDroppedAlarm
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.34
OVOC | Alarms Monitoring Guide
displayed.
Alarm Title
Alarm SourceOVOC QoE
Alarm TypeQuality of service alarm
Probable
Cause
SeverityMINOR/ MAJOR/ CRITICAL
Additional
Info
■ Voice Quality – System Load Alarm
AlarmProbableCauseType.THRESHOLDCROSSED
■ Medium load level is reached - {0}%, {1} calls of {2}. /
■ High load level is reached - {0}%, {1} calls of {2}. /
■ Approaching maximal system capacity - {0}%, {1} calls of {2}.
Corrective
Action
Reduce the system load.
Call Details Storage Level Change
Alarm FieldDescription
DescriptionThis alarm is sent when the operator changes the Call Details Storage
Level from one level to another.
SNMP AlarmacVoice QualityClientLoadFlagAlarm
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.35
Alarm TitleVoice Quality – Call Details Storage Level has been changed.
Alarm SourceOVOC QoE
Alarm TypeQuality of service alarm
Probable
Cause
Threshold crossed
- 57 -
CHAPTER4 Voice Quality Package Alarms
Alarm FieldDescription
SeverityIndeterminate
OVOC | Alarms Monitoring Guide
Additional
Info
Corrective
Action
-
-
Call Quality Monitoring Connection Status Alarm
Alarm FieldDescription
DescriptionThis alarm is sent when connectivity is lost between the managed device
and Voice Quality Package server.
SNMP AlarmacSEMConnectionStatusAlarm
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.36
Alarm TitleVoice Quality – OVOC QoE - Connection Status Alarm
Alarm SourceOVOC QoE/Device
Alarm TypecommunicationsAlarm
Probable
Cause
Additional
Info
communicationsSubsystemFailure
One of the following reasons will appear:
■ Server Time: {0}, Device Time: {1}.
■ Please check your NTP Configuration in Device.
■ NTP Servers are not configured in the Device.
■ Please make sure that time in OVOC QoE Server and Device is
properly synchronized.
■ NTP configuration is correct, please check your network conditions
(Firewalls, Ports, etc .) and make sure that NTP sync of OVOC QoE
Server and/or Devices is performed correctly.
■ You have complex network configuration in OVOC Mgmt/OVOC QoE
server. Please refer to OVOC Mgmt client / Help menu / OVOC Mgmt
Configuration frame to verify network configuration.
Alarm
ConditionTextCorrectiveAction
- 58 -
CHAPTER4 Voice Quality Package Alarms
Alarm FieldDescription
Severity
OVOC | Alarms Monitoring Guide
CriticalInsufficient
memory buffer.
Connection loss
between OVOC
and the device.
ClearServer and Device
are not
synchronized.
Connection is
established
between the
device and OVOC.
Synchronization
between server
and device.
There isn't enough
buffer size to
allocate for main
messages queue of
this board.
OVOC QoE
connection lost.
Server Time: {0},
Device Time: {1}.
OVOC QoE
connection
established. Server
and Device are now
Synchronized.
Server and Device
are now
Synchronized.
The OVOC server has
reached its maximum
management capacity.
Contact AudioCodes
Customer Support.
Check your network
configuration on both the
device and OVOC server.
Check your NTP
Configuration in device.
-
-
OVOC QoE - Skype for Business SQL Server Connection Lost
Alarm
Alarm FieldDescription
DescriptionThis alarm is sent when there is no connectivity with the Lync SQL Server
database.
SNMP AlarmacMSLyncConnectionAlarm
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.37
Alarm TitleVoice Quality AD Lync Connection Alarm
Alarm SourceOVOC QoE/Device
Alarm TypeCommunications alarm
- 59 -
CHAPTER4 Voice Quality Package Alarms
Alarm FieldDescription
OVOC | Alarms Monitoring Guide
Probable
Cause
SeverityCritical
Additional
Info
Corrective
Action
Communications sub-system failure
-
Check the Lync SQL server for problems.
OVOC QoE - Active Directory Server Connection Lost Alarm
Alarm FieldDescription
DescriptionThis alarm is sent when there is no connectivity with the Active Directory
LDAP server.
SNMP AlarmacVoice QualityMSLyncADServerAlarm
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.38
Alarm TitleVoice Quality MS Lync AD Server Alarm
Alarm SourceOVOC QoE/Active Directory
Alarm TypeCommunications alarm
Probable
Cause
SeverityCritical
Additional
Info
Corrective
Action
Communications sub-system failure
■ Voice Quality - AD Lync connection alarm
Check the MS Lync AD server for problems.
OVOC QoE - Media Bandwidth Alarm
Alarm FieldDescription
DescriptionThis alarm is sent when the media bandwidth for the node
- 60 -
CHAPTER4 Voice Quality Package Alarms
Alarm FieldDescription
or link falls below or exceeds the threshold values configured in the QoE Status and Alarms Details window.
SNMPOID1.3.6.1.4.1.5003.9.20.3.2.0.43
SNMPAlarmacVoice QualityRuleBandwidthAlarm
Alarm TitleVoice Quality Rule Bandwidth Alarm
Alarm SourceVOC QoE/Device/Link/Site/Endpoint
Alarm TypeQuality of service alarm
OVOC | Alarms Monitoring Guide
Probable
Threshold crossed
Cause
Additional Info
■ Critical Threshold: 10 Kb/ sec (default).
■ Major Threshold: 5 Kb/ sec (default)
Where measured per managed node or link for a total
time of 180 minutes period (three hours) and according
to “Monitoring Frequency Min” For example, if this
parameter is set to 15 minutes, sampling is performed at
15:15 (from 12:15 to 15:15) and then at 15:30 (for 12:3015:30) and so on.
Alarm SeverityConditionText
CriticalThis alarm is raised
when the maximum
bandwidth for the
Maximum
Bandwidth of
X Kb/sec
sampled period (see
above) reaches the
configured critical
threshold value.
MajorThis alarm is raised
when the maximum
bandwidth for the
Maximum
Bandwidth of
X Kb/sec
sampled period (see
above) reaches the
configured major
threshold value.
Corrective
Action
Check the
node's or
link's maximum bandwidth capacity
matches the
required capacity.
- 61 -
CHAPTER4 Voice Quality Package Alarms
Alarm FieldDescription
OVOC | Alarms Monitoring Guide
ClearCleared when the max-
imum bandwidth for
the sampled period
increases above the
configured thresholds
for the sampled period
(see above).
-
OVOC QoE - Rule Max Concurrent Calls Alarm
Alarm FieldDescription
DescriptionThis alarm is sent when the maximum concurrent calls for
the node or link falls below or exceeds the threshold values configured in QoE Status and Alarms Details window.
Where measured per managed node or link for a total
time of 180 minutes period (three hours) and according
to “Monitoring Frequency Min”. For example, if this
parameter is set to 15 minutes, sampling is performed at
15:15 (from 12:15 to 15:15) and then at 15:30 (from 12:30
to 15:30) and so on.
Alarm SeverityConditionText
Corrective
Action
CriticalThis alarm is raised
when the number of
Max Concurrent Calls of
- 62 -
Check that the
node's or link's
CHAPTER4 Voice Quality Package Alarms
Alarm FieldDescription
OVOC | Alarms Monitoring Guide
concurrent calls
reaches the configured critical
threshold for the
sampled period (see
above).
MajorThis alarm is raised
when the number of
concurrent calls
reaches the configured major
threshold for the
sampled period (see
above)..
ClearThis alarm is raised
when the number of
concurrent calls falls
within the configured
threshold for the
sampled period (see
above).
Xmaximum num-
ber of concurrent calls
matches the
required capacity.
Max Concurrent Calls of
X
-
Report Schedulers Time Event
Alarm FieldDescription
DescriptionThis event is raised when the Reports Scheduler misses a scheduled
execution time.
SNMPOID1.3.6.1.4.1.5003.9.20.3.2.0.82
SNMPAlarmacReportSchedulersTimeEvent
Alarm TitleReport Schedulers Time Event
Alarm SourceOVOC QoE/Report Scheduler
Alarm TypeOther
Probable
Cause
Other
- 63 -
CHAPTER4 Voice Quality Package Alarms
Alarm FieldDescription
OVOC | Alarms Monitoring Guide
Alarm SeverityConditionText
MajorThe sched-
uler misses
the execution time.
Example : Scheduler ZAdmin_predefined Has Missed his Execution
Time, Schedulers Next Run: 2019-1222 05:00:00.0, While Current Time:
Sun Dec 22 05:00:20 GMT 2019
Corrective
Action
-
Report Schedulers Load Alarm
Alarm FieldDescription
DescriptionThis alarm is raised when the Report Scheduler's buffer reaches
maximum it's capacity.
SNMPOID1.3.6.1.4.1.5003.9.20.3.2.0.83
SNMPAlarmacReportSchedulersLoadAlarm
Alarm TitleReport Schedulers Load Alarm
Alarm SourceOVOC QoE/Report Scheduler
Alarm TypeOther
Probable
Cause
Alarm SeverityConditionText
CRITICALSchedulers Exe-
MAJORSchedulers Exe-
Other
cution Queue
has reached maximum buffer
capacity.
cution Queue
has reached 80%
of its maximum
buffer capacity.
Schedulers Queue Has
Reached His Max Buffer
Capacity= <buffersize>,
New Schedulers Will Not
Be Executed
Schedulers Queue Has
Reached 80% Of His Max
Buffer Capacity=<buffersize> , His Current Queue
Size=<buffersize>
Corrective
Action
Reduce the
number of
scheduled
reports.
- 64 -
CHAPTER4 Voice Quality Package Alarms
Report Schedulers Execution Event
Alarm FieldDescription
DescriptionThis event is raised when the execution of the report that is attached
to the Scheduler fails.
SNMPOID1.3.6.1.4.1.5003.9.20.3.2.0.84
SNMPAlarmacReportSchedulersExecutionEvent
Alarm TitleReport Schedulers Execution Event
Alarm SourceOVOC QoE/Report Scheduler
Alarm TypeOther
OVOC | Alarms Monitoring Guide
Probable
Cause
Alarm SeverityConditionText
CriticalExecution of
Other
report which
is attached
to the scheduler fails.
Example:
culation of report result has been
failed ; schedulerName=Test_Topology_Trend ; reportName=TestTrend_
Report ; executionTime=Wed Dec 11
06:46:00 GMT 2019 ; actualRunTime=Wed Dec 11 06:46:00 GMT
2019
SchedulerExecuter: Cal-
Corrective
Action
-
- 65 -
CHAPTER5 Device Manager Alarms
5Device Manager Alarms
Registration Failure Alarm
Alarm FieldDescription
DescriptionThis alarm is raised when a SIP registration (with a PBX) for the IP Phone
fails.
SNMP AlarmIPPhoneRegisterFailure
SNMPOID1.3.6.1.4.1.5003.9.20.3.2.0.39
Alarm TitleRegistration Failure
Alarm SourceIP Phone
OVOC | Alarms Monitoring Guide
Alarm TypecommunicationsAlarm(1)
Probable
Cause
SeverityCritical
Corrective
Action
communicationsProtocolError(5)
The problem is typically not related to the phone, however to the server.
The user/phone may not be defined, or may be incorrectly defined, or
may previously have been defined but the username (for example) may
have been changed, causing the registration to fail. Make sure the
username and password credentials are identical in the server and
phone, and weren't changed; server-phone credentials must be
synchronized. Make sure the server is responsive.
IP Phone Survivable Mode Start Alarm
Alarm FieldsDescription
DescriptionThis alarm is raised when the IP Phone enters Survivable mode state with
limited services in the Microsoft Lync environment.
SNMP AlarmIPPhoneSurvivableModeStart
OID1.3.6.1.4.1.5003.9.20.3.2.0.40
Alarm TitleSurvivable Mode Start
- 66 -
CHAPTER5 Device Manager Alarms
Alarm FieldsDescription
Alarm SourceIP Phone
Alarm TypeOther(0)
OVOC | Alarms Monitoring Guide
Probable
Cause
SeverityMajor
Corrective
Action
other (0)
The problem is typically not related to the phone, but to the server or
network. Make sure all servers in the enterprise's network are up. If one
is down, limited service will result.
IP Phone Lync Login Failure Alarm
Alarm FieldDescription
DescriptionThis alarm is raised when the IP Phone fails to connect to Microsoft Lync
Server during sign in.
SNMP AlarmIPPhoneLyncLoginFailure
OID1.3.6.1.4.1.5003.9.20.3.2.0.41
Alarm TitleLync Login Failure
Alarm SourceIP Phone
Alarm TypecommunicationsAlarm(1)
Probable
Cause
SeverityCritical
Additional
Info
Corrective
Action
communicationsProtocolError(5)
TlsConnectionFailure
NtpServerError
This alarm may typically occur if the user is not registered - or is
registered incorrectly - in the Lync Server. Make sure that username,
password and PIN code are correctly configured and valid in the Lync
Server. Try resetting them. Try redefining the user.
- 67 -
CHAPTER5 Device Manager Alarms
Endpoint License Alarm
Alarm FieldDescription
DescriptionThis alarm is issued for the following scenarios:
SNMP AlarmacEndpointLicenseAlarm
OVOC | Alarms Monitoring Guide
Table 5-1: Endpoint License Alarm
■ When the number of endpoints currently running on the Voice
Quality server (shown as 'IP Phones Number' under 'Voice Quality' in
the OVOC Server Manager License screen) approaches or reaches its
license capacity.
■ When the number of managed endpoints currently running on the
OVOC server (shown in the License screen License screen)
approaches or reaches its license capacity.
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.48
Alarm TitleEndpoint License Alarm
Alarm SourceVoice Quality/Management
Alarm TypeOther
Probable
Cause
Additional
Info
Corrective
Action
Key Expired
Endpoint License capacity {0} devices.
Contact your AudioCodes partner ASAP
Alarm SeverityConditionTextCorrective Action
CriticalCurrently connected
devices are equivelant to
100% of Endpoints
License capacity.
Currently running
devices reached
100% of Endpoints
License capacity.
-
MajorCurrently connected
devices are equivelant to
reached 80% of Endpoints
License capacity.
ClearClearing currently activeClear - Clearing-
- 68 -
Currently running
devices reached
80% of Endpoints
License capacity.
-
CHAPTER5 Device Manager Alarms
Alarm FieldDescription
Endpoint Server Overloaded Alarm
Alarm FieldDescription
DescriptionThis alarm is issued when the Voice Quality Endpoint server process is
SNMP AlarmacEndpointServerOverloadAlarm
SNMP OID1.3.6.1.4.1.5003.9.20.3.2.0.49
OVOC | Alarms Monitoring Guide
alarmcurrently active
alarm.
overloaded with RFC 6035 Publish messages. This causes new RFC 6035
SIP PUBLISH messages () to be dropped from the queue for this process.
Alarm TitleEndpoint Server Overloaded Alarm
Alarm TextVoice Quality Endpoint Server Overloaded! New Publish Messages
Dropped
Alarm SourceVoice Quality
Alarm TypeOther
Probable
Cause
SeverityCritical
Corrective
Action
Queue Size exceeded
Reduce the endpoint traffic load on the OVOC server.
IP Phone Speaker Firmware Download Failure
Alarm FieldDetails
DescriptionThis alarm is raised when the phone fails to download the HRSspeaker
Alarm TitleUSB port shutdown due to over current exceeded
Alarm TypePhysical Violation
Probable
Cause
Input Device Error
- 77 -
CHAPTER5 Device Manager Alarms
Alarm FieldDescription
OVOC | Alarms Monitoring Guide
Additional
Info1
Additional
Disconnect the USB device from the phone and press OK to re enable the
USB port.
Make sure that the USB port is used for USB headset only.
Info2
Alarm
Severity
ConditionAlarm TextCorrective Action
CriticalThis alarm is activ-
ated when the
USB port on the
android device
shuts down for
30 seconds, due
to a current
surge.
ClearUSBport
connection is
restored.
This alarm is activated upon
USB shutdown for 30 seconds,
due to over current exceeded.
See above
- 78 -
CHAPTER6 OVOCManaged Devices Alarms
6OVOCManaged Devices Alarms
Support Matrix
The table below categorizes all of the device alarms and indicates to which devices they are
applicable. For each category, under the adjacent “Supported Device Types” column, all of the
common supported alarms for this category are listed. For each individual alarm, under the
adjacent “Supported Device Types” column, if all of the common alarms are supported “As
above” is noted; however, if only specific devices support this alarm, then these device types
are listed.
Alarm TypeSupported Device Types
Common AlarmsAll the alarms in Section Common Alarms are supported by all
AudioCodes devices.
OVOC | Alarms Monitoring Guide
Specific Hardware
Alarms
Temperature Alarm
on page136
Fan Tray Alarm on
page137
Power Supply Alarm
on page138
■ Mediant 2600 E-SBC
■ Mediant 4000 SBC
■ Mediant 1000
■ MP-1288
■ Mediant 1000
■ Mediant 2600
■ Mediant 4000
■ MP-1288
■ Mediant 1000
■ Mediant 2600
■ Mediant 4000
■ MP-1288
■ Mediant 1000
HA System Alarms
■ Mediant 2600
■ Mediant 4000.
■ Mediant 500 E-SBC
■ Mediant 800B GW & E-SBC
■ Mediant 3000/TP-6310
■ Mediant 3000/TP-8410
- 79 -
CHAPTER6 OVOCManaged Devices Alarms
Alarm TypeSupported Device Types
OVOC | Alarms Monitoring Guide
■ Mediant 2600 E-SBC
■ Mediant 4000 SBC
■ Mediant 4000B SBC (3 x MPM)
■ Mediant 9000 SBC
■ Mediant VE SBC
■ Mediant SE SBC
HA System Fault
Alarm on page140
HA System
Configuration
Mismatch Alarm on
page145
HA System Switch
Over Alarm on
page146
Hitless Software
Upgrade Alarm on
page146
Redundant Board
Alarm on page147
As above
As above
As above
■ Mediant 2600 E-SBC
■ Mediant 4000 SBC
■ Mediant SE SBC
■ Mediant VE SBC
As above
HA Network
As above
Watchdog Status
Alarm on page148
HA Network
As above (except Mediant 3000)
Watchdog Status
Alarm on page148
Cluster HA Alarm on
page162
■ Media Transcoding Cluster feature (Mediant 9000 SBC and
Mediant VE SBC)
HA Network■ Mediant VE SBC on AWS
- 80 -
CHAPTER6 OVOCManaged Devices Alarms
Alarm TypeSupported Device Types
OVOC | Alarms Monitoring Guide
Mismatch Alarm on
page150
HA Network Monitor
Alarm on page151
HA Ethernet Group
Alarm on page152
License Pool Alarms
License Pool Infra
Alarm on page152
License Pool
Application Alarm on
page154
■ Mediant SE SBC on AWS
As above
As above (except Mediant 3000)
Supported by all devices from Version 7.0, except for the Mediant
2000 and Mediant 3000. In addition, the Transcoding session
license is applicable only to the Mediant Virtual Edition and Mediant 9000.
As above
As above
License Pool Over
Allocation Alarm on
page155
Floating License
Alarms
Cloud License
Manager Alarm on
page157
Floating License Alarm
- Not Enough Memory
to Allocate 'Custom'
Profile on page156
Flex License Manager
Alarm on page160
Mediant 2600 ESBCand Mediant 4000
Alarms SBC
As above
Refer to the OVOC Release Notes for device support information.
Supported for the Floating License "Cloud" mode.
Supported for the Floating License "Cloud" mode.
Supported for the Floating License "FlexPool" mode.
DSP Farms Mismatch■ Mediant 2600 E-SBC
- 81 -
CHAPTER6 OVOCManaged Devices Alarms
Alarm TypeSupported Device Types
Alarm on page161■ Mediant 4000 SBC
OVOC | Alarms Monitoring Guide
■ Mediant 9000 SBC
Mediant 9000 and
Software SBC Alarms
Media Transcoder
Network Failure on
page163
Media Transcoder
Software Upgrade
Failure on page164
Media Transcoder
High Temperature
Failure on page165
Media Transcoder Fan
Tray Module Failure
on page166
■ Mediant VE SBC
■ Mediant SE SBC
■ Mediant CESBC
■ Media Transcoding Cluster feature (Mediant VE SBC and
Mediant 9000 SBC)
■ Elastic Media Cluster feature (Mediant CE SBC)
■ Media Transcoding Cluster feature (Mediant 9000 and
Mediant VE SBC)
■ Elastic Media Cluster feature (Mediant CE SBC)
■ Media Transcoding Cluster feature (Mediant 9000 and
Mediant VE SBC)
■ Media Transcoding Cluster feature (Mediant 9000 and
Mediant VE SBC)
Media Transcoder
Power Supply Module
Failure on page167
Cluster Bandwidth Utilization Alarm on
page167
Media Cluster Alarm
on page169
Remote Interface
Alarm on page170
AWS Security Role
Alarm on page171
CDR Server Alarm on
page172
■ Media Transcoding Cluster feature (Mediant 9000 and
Mediant VE SBC)
■ Media Transcoding Cluster feature (Mediant 9000 and
Mediant VE SBC)
■ Elastic Media Cluster feature (Mediant CE SBC)
■ Elastic Media Cluster feature (Mediant CE SBC)
■ Elastic Media Cluster feature (Mediant CE SBC)
■ Mediant VE SBC and Mediant CESBC
■ As above
- 82 -
CHAPTER6 OVOCManaged Devices Alarms
Alarm TypeSupported Device Types
OVOC | Alarms Monitoring Guide
Metering Alarm on
page173
MP-1288 Alarms
Module Service Alarm
on page174
Module Operation
Alarm on page175
Port Service Alarm on
page176
MSBR Alarms
WAN Link Alarm on
page178
■ Mediant VE when deployed through the AWS Marketplace
■ MP-1288 (not supported by the OVOC License Pool Manager)
As above
As above
As above
Mediant 1000B MSBR, Mediant 800 MSBR Mediant MSBR 500L
and Mediant 500 MSBR (for version 7.2 and later, MSBR and ESBC are separate applications that reside on the same host
platform1)' Mediant 500Li MSBR
As above
Power Over Ethernet
Status [Event] on
page178
Wireless Cellular
Modem Alarm on
page179
Wireless Cellular
Modem Status
Changed on page180
Data Interface Status
on page180
NQM Connectivity
Alarm on page181
Mediant 800 MSBR
■ Mediant 500 MSBR
■ Mediant 500L MSBR
■ Mediant 800 MSBR
■ Mediant 500 MSBR
■ Mediant 500L MSBR
■ Mediant 800 MSBR
As above
Mediant 800 MSBR
1
Refer to SBC-Gateway-MSBR Series Release Notes for details.
- 83 -
CHAPTER6 OVOCManaged Devices Alarms
Alarm TypeSupported Device Types
OVOC | Alarms Monitoring Guide
NQM RTT Alarm on
page182
NQM Jitter Alarm on
page182
NQM Packet Loss
Alarm on page183
NQM MOS CQ Alarm
on page184
NQM MOS LQ Alarm
on page185
Mediant 3000
Hardware Alarms
PEM Module Alarm
on page186
Mediant 800 MSBR
Mediant 800 MSBR
Mediant 800 MSBR
Mediant 800 MSBR
Mediant 800 MSBR
■ Mediant 3000/TP-6310
■ Mediant 3000/TP-8410
As above
SA Module Missing
Alarm on page187
User Input Alarm on
page188
TM Inconsistency on
page188
TM Reference Status
on page189
TM Reference Change
on page190
PSTN Trunk Alarms
As above
As above
As above
This alarm applies only to the Mediant 3000 using the BITs
Synchronization Timing mode.
As above
■ Mediant 500 Gateway & E-SBC
■ Mediant 500 MSBR
■ Mediant 800B Gateway & E-SBC
■ Mediant 800B MSBR
■ Mediant 1000B Gateway & E-SBC
- 84 -
CHAPTER6 OVOCManaged Devices Alarms
Alarm TypeSupported Device Types
OVOC | Alarms Monitoring Guide
■ Mediant 3000
For version 7.2 and later, MSBR and E-SBC are
separate applications that reside on the same host
platform1)
D-Channel Status on
page190
SONET Section LOS
Alarm on page192
SONET Line AIS Alarm
on page193
SONET Line RDI Alarm
on page194
SONET/SDN IF Failure
Alarm on page194
Trunk LOS Alarm on
page195
As above
■ Mediant 3000/TP-6310
■ Mediant 3000/TP-6310
■ Mediant 3000/TP-6310
■ Mediant 3000/TP-6310
■ Mediant 500 E-SBC
■ Mediant 500 MSBR
■ Mediant 800B Gateway & E-SBC
■ Mediant 800B MSBR
■ Mediant 850 MSBR
■ Mediant 1000B MSBR
■ Mediant 1000B GW & E-SBC
■ Mediant 3000/TP-8410
Trunk LOF Alarm on
page196
■ Mediant 500 E-SBC
■ Mediant 500 MSBR
■ Mediant 800B Gateway & E-SBC
■ Mediant 800B MSBR
■ Mediant 850 MSBR
1
Refer to SBC-Gateway-MSBR Series Release Notes for details.
- 85 -
CHAPTER6 OVOCManaged Devices Alarms
Alarm TypeSupported Device Types
OVOC | Alarms Monitoring Guide
■ Mediant 1000B MSBR
■ Mediant 1000B GW & E-SBC
■ Mediant 3000/TP-8410
Trunk AIS Alarm on
page197
Trunk RAI Alarm on
page197
■ Mediant 500 E-SBC
■ Mediant 500 MSBR
■ Mediant 800B Gateway & E-SBC
■ Mediant 800B MSBR
■ Mediant 850 MSBR
■ Mediant 1000B MSBR
■ Mediant 1000B GW & E-SBC
■ Mediant 3000/TP-8410
■ Mediant 500 E-SBC
■ Mediant 500 MSBR
■ Mediant 800B Gateway & E-SBC
■ Mediant 800B MSBR
■ Mediant 850 MSBR
■ Mediant 1000B MSBR
V5.2 Interface Alarm
on page198
SONET Path STS LOP
Alarm on page199
SONET Path STS AIS
Alarm on page200
SONET Path STS RDI
Alarm on page200
SONETPath
Unequipped Alarm on
page201
■ Mediant 1000B GW & E-SBC
■ Mediant 3000/TP-8410
■ Mediant 3000/TP-8410
■ Mediant 3000/TP-6310
■ Mediant 3000/TP-6310
■ Mediant 3000/TP-6310
■ Mediant 3000/TP-6310
- 86 -
CHAPTER6 OVOCManaged Devices Alarms
Alarm TypeSupported Device Types
OVOC | Alarms Monitoring Guide
SONETPathSignal
LabelAlarmon
page202
SONETPathSignal
LabelAlarmon
page202
DS1 Line Status Alarm
on page202
DS3 AIS Alarm on
page204
DS3 LOF Alarm on
page205
DS3 LOS Alarm on
page205
NFAS Group Alarm on
page206
■ Mediant 3000/TP-6310
■ Mediant 3000/TP-6310
As above
■ Mediant 3000/TP-6310
■ Mediant 3000/TP-6310
■ Mediant 3000/TP-6310
As above
B Channel Alarm on
page207
Analog Port Alarms
As above
■ Mediant 500 E-SBC
■ Mediant 500L E-SBC
■ Mediant 500 MSBR
■ Mediant 500L MSBR
■ Mediant 500L GW & E-SBC
■ Mediant 800B Gateway & E-SBC
■ Mediant 800B MSBR
■ Mediant 850 MSBR
■ Mediant 1000B MSBR
■ Mediant 1000B GW & E-SBC
■ (for version 7.2 and later, MSBR and E-SBC are separate
- 87 -
CHAPTER6 OVOCManaged Devices Alarms
Alarm TypeSupported Device Types
OVOC | Alarms Monitoring Guide
applications that reside on the same host platform1)
Analog Port SPI Out of
Service on page208
Analog Port High
Temperature on
page208
Analog Port Ground
Fault Out-of-Service
Alarm on page209
Dial Plan File Replaced
Trap on page209
Analog Line Left Off
Hook Alarm on
page210
Microsoft Platform
Alarms
As above
As above
As above
As above
As above
■ CloudBond Mediant 800B
■ CloudBond Mediant Server
■ CCE Appliance Mediant 800B
Component
Unreachable on
page211
Component Restart
on page211
Component
Performance Counter
General on page212
Component
Performance Counter
Service on page213
Component Service
■ CCE Appliance Mediant Server
As above
As above
As above
As above
As above
1
Refer to SBC-Gateway-MSBR Series Release Notes for details.
- 88 -
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.