This document describes the Registration failed: Error:
DB Config VG248 error message that appears every two seconds
and provides the steps necessary to troubleshoot it.
Cisco recommends that you have knowledge of these topics:
The information in this document is based on the Cisco Unified
Communications Manager (CallManager) 4.x.
The information in this document was created from the devices in a
specific lab environment. All of the devices used in this document started with
a cleared (default) configuration. If your network is live, make sure that you
understand the potential impact of any command.
Technical Tips Conventions for more information on document
Cisco VG248 displays this error message:
WARNING: SCCP:Registration failed: Error: DB Config.
On the Cisco Unified Communications Mananger (CallManager), the
Application Event Log displays this error message:
Event Type: Error
Event Source: Cisco CallManager
Event Category: None
Event ID: 3
Time: 8:39:17 PM
Error: DeviceTransientConnection - Transient connection attempt.
Connecting Port: 2000
Device name [Optional].:
Device IP address.: 10.26.1.7
Device type. [Optional]: 255
Reason Code [Optional].: 6
App ID: Cisco CallManager
Cluster ID: Cisco-CCM1-Cluster
Node ID: Cisco-CCM1
Explanation: A connection was established and immediately dropped before
completing registration. Incomplete registration may indicate a device is
rehoming in the middle of registration. The alarm could also indicate a device
misconfiguration,database error, or an illegal/unknown device trying to attempt
Recommended Action: No action is required if this event was issued as a result
of a normal device rehome..
These error messages are displayed when one or more ports of the VG248
are enabled but are not configured in the Cisco Communications Manager
In order to overcome this problem, find out if any of the ports that
are enabled on VG248 are not configured in the Cisco Communications Manager
(CallManager). If so, disable those particular ports in the VG248.