Cisco Support Community
Community Member

DeviceTransientConnection - ReasonCode 1

I have a customer that is getting thousands of the messages below in the event log. Can someone explain the reason code (1) and what may be happening? Any help is appreciated. Thanks in advance. - Cary

Error: DeviceTransientConnection - Transient connection attempt.

Connecting Port: 2000

Device name [Optional].: SEP000CCEC05CB1

Device IP address.:

Device type. [Optional]: 8

Reason Code [Optional].: 1

App ID: Cisco CallManager

Cluster ID: AIMCCM1-Cluster

Node ID:

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 a connection.

Recommended Action: No action is required if this event was issued as a result of a normal device rehome..


Re: DeviceTransientConnection - ReasonCode 1

Reason Code 1 means Unknown

Enum Definitions -Reason Code [Optional]. Value Definition

1 Unknown

2 NoEntryInDatabase

3 DatabaseConfigurationError

4 DeviceNameUnresolveable

5 MaxDevRegExceeded

6 ConnectivityError

7 InitializationError

8 DeviceInitiatedReset

9 CallManagerReset

10 DeviceUnregistered

Try using Software Bug Toolkit to search for possible bugs under Featured Tools.

If unsuccessful try contacting TAC.

Hall of Fame Super Silver

Re: DeviceTransientConnection - ReasonCode 1

What type of devices are your phones?

Try installing the latest devPack. I had the same problem with 7961/41 devices.


Community Member

Re: DeviceTransientConnection - ReasonCode 1

If this is a message u r seeing after an upgrade or something, install the latest service release for this version of Callmanager.

If this is not after an upgrade, then check the replication between your Callmanagers. run DBLHelper and check and resynch the replication.

In Callmanager check whether this phone SEP000CCEC05CB1 is actually registered or not. If it is registered and even then u r getting these messages, then this is due to some replication issue, that the phone is trying to register with the Primary Callmanager and is not able to and then it is registering with the Secondary CM.

CreatePlease to create content