Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

4.1.3 Sub Transient Connection Attempt

the event log on my sub is filling up with 'transiet connection attempt' errors. I had a problem this morning where the pub/sub sql was not replication, as users were not able to un callfwd phones. I found Doc id 43581, and I stopped/started the CDL service on pub, and ran dblhelper to reinitialize. that has fixed the problems for now, but I am concerned about the sub errors. I recently applied SR6 also. any help as to what is causing these errors. thanks

Hall of Fame Super Red

Re: 4.1.3 Sub Transient Connection Attempt

Hi Pete,

Sounds like quite the day so far! Did the "transient connection attempt" errors subside after the replication issue was fixed? Can you look at the Mac address/addresses referenced in the errors to determine if it is just one phone or many?

Can you post one of the complete errors if this is still going on as these can be attributed to different issues. These are usually some sort of connectivity problem but with ATA's and VG248's they are config issues.

Let us know,


New Member

Re: 4.1.3 Sub Transient Connection Attempt


thanks for your quick response. yes, the errors are still filling the event log. Here is a sample

Event Type: Error

Event Source: Cisco CallManager

Event Category: None

Event ID: 3

Date: 1/16/2008

Time: 12:06:52 PM

User: N/A

Computer: MBNPCCM2


Error: DeviceTransientConnection - Transient connection attempt.

Connecting Port: 2000

Device name [Optional].: SEP0019E74488CB

Device IP address.:

Device type.

[Optional]: 115

Reason Code [Optional].: 1

App ID: Cisco CallManager

Cluster ID: MBNPCCM1-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..

Interesting thing is that it is always this MAC address, as well as two MAC addresses for ATA's

Hall of Fame Super Red

Re: 4.1.3 Sub Transient Connection Attempt

Hi Pete,

To eliminate part of the problem, for the ATA's you need to either configure or disable Line 2 on each ATA.

What is SEP0019E74488CB? Can you look into it and perhaps remove it until you can track it down and look for the actual problem.

Hope this helps!


PS: I also remember one time where we had ATA's configured but not actually connected where we got a bunch of these errors.