DeviceTransientConnection Reason Code 1

[reillytucker]

Hi.

Have been getting loads of "Transient connection attempts errors". Weh this happens the phone has the message 'registering with ccm'....

It seems to happen randomly to a couple of 7960 IP phones (not all) connected via vpn. I can't work out what is causing this. The VPN's are very reliable. You can still ping the phone when this message occurs. Troubleshooted this one to death. Tried deleting phone from database/replaced phone. I'm sure this is a network issue. Its driving me nuts.

Application Log Error 3:-

Error: DeviceTransientConnection - Transient connection attempt.
Connecting Port: 2000
Device name [Optional].: SEP0015FA62A9B8
Device IP address.: 10.24.5.200
Device type. [Optional]: 7
Reason Code [Optional].: 1
App ID: Cisco CallManager
Cluster ID: SMP-CCM-01-Cluster
Node ID: 172.16.24.10
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..

The phones that have the issues are on the end of a vpn to peoples homes. I know thats not great but I wasn't expecting it to be that unreliable.

The setup is:-
Main Office: Cisco PIX 515e ver 7.2.
Remote Home: Cisco 877w ver ios 12.4
Cisco CCM: 4.1(3)sr3c (in its on vlan/network)

Any ideas. Anything I should look at. You think its the PIX messing with the connection? Would it be better to terminate the home VPN's on our vpn3000 boxes? The reason code is unknown so thats not much help.

Any ideas? Cheers.

 

[whykap]

What kind of circuit do the users that their phones drop have at home?

From what you are describing it sounds like a VPN issue between the sites that you are having failures.

Call manager is not going to tell you why the phones lost registration, therefore the generic error message.

Have you actually verified that the vpn connection does not drop the same time the phone reboots?

Something is causing it to lose connection to the call manager.

Another thing to look at could be the 7960 phone load you are running (I would look at this after Verification that the VPN is set up and functioning right.

 

[reillytucker]

Cheers.
The connection is a Zen adsl 8meg.

I can confirm that the vpn does not go down when the phone looses registration. Yeah its most likely vpn issues however, even if it were a slight drop in connection it would be fair that the phone would re-register not hang for hours with loads of these events in the cm servers logs?

The phone load is new I think (Version 7.2(4.0))

For example the phones down now but I can ping and view the phones web page from the ccm server.

The debug display on the phones web page has loads of:- Code:8103, P:0, S:12300800

Heres a clue frmo the ccm trace
10/05/2006 09:36:46.132 CCM|StationInit: TCPPid = [1.100.132.12383]Socket Broken. DeviceName=SEP0015FA62A9B8,IPAddr=10.24.5.200, Port=0x0, Device Controller=[1,118,12377]|<CLID::SMP-CCM-01-Cluster><NID::172.16.24.10><CT::1,100,132,12383.1><IP::><DEV::>

The firewall and routers don't show any denys. Maybe my brainwave to have IP phones at home was the wrong idea. I would have been happy with 90% reliabilty. This sucks! Thanks for your help ;-)

 

[JayD77]

Run Ethereal on one of those phone and see if they got any Keep alive from the CCM. also see if there is any TFTP or TCP errors.