Syslog or SNMP trap notification of database purging activities is not sent

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m (1 revision)
(→Syslog or SNMP trap notification of database purging activities is not sent)
 
(One intermediate revision not shown)
Line 1: Line 1:
 +
{{Template:Required Metadata}}
== Syslog or SNMP trap notification of database purging activities is not sent ==
== Syslog or SNMP trap notification of database purging activities is not sent ==
Line 22: Line 23:
|-
|-
! '''Release'''
! '''Release'''
-
| Release 7.0(1)
+
| Release 7.0, Release 5.0
|-
|-
! '''Associated CDETS #'''
! '''Associated CDETS #'''

Latest revision as of 10:37, 23 April 2010

Syslog or SNMP trap notification of database purging activities is not sent

Problem Summary The Unified CCX system does not send Syslog notification or SNMP trap notification of purging activities.
Error Message The following message appears in the MIVR log:

%MIVR-SS_TEL-7-UNK:Call.rejected(TRIGGER_MAX_SESSION)

Possible Cause The Unified CCX Alarm Service is not running, Syslog is not configured, or SNMP service is not configured.
Recommended Action

Complete the following steps:

  1. Make sure that the Unified CCX Alarm Service is running.
  2. Make sure that Syslog is properly configured.
  3. Make sure that SNMP service is properly configured on the Unified CCX server.
Release Release 7.0, Release 5.0
Associated CDETS # None.

Rating: 0.0/5 (0 votes cast)

Retrieved from "http://docwiki.cisco.com/wiki/Syslog_or_SNMP_trap_notification_of_database_purging_activities_is_not_sent"
Personal tools