Invalid SCCP message!

Unanswered Question
May 30th, 2007

Hello I have three remote sites that are very similar in configuration and layout. Each site has a gateway using MGCP and SRST with a VPN connection over the internet (T1 or DSL). Periodically 2 of my 3 sites are failing and this is the message that I get in the trace and event viewer:

Error: StationEventAlert - Station alert.

TCP ProcessID:

Device Text: 32: Name=SEP001930C8F22A Load= SCCP41.8-2-2SR3S : Invalid SCCP message! : Invali

Param1: 0

Param2: 0

App ID: Cisco CallManager

Cluster ID: StandAloneCluster

Node ID:

Explanation: Station device sent an alert to Cisco CallManager.

Recommended Action: Ensure that the configuration for identified device is proper..

The phones will reset soon after I receive this message. However, the gateway is fine and stays up.

TAC is stumped. Any ideas?



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
gogasca Wed, 05/30/2007 - 23:51

Mmm, do you have the SR number?

The sites directly connected to the CCM never unregister or reset?

I had a case last year in which customer was getting the same errors and was a duplex mismatch in the VPN path.

I would recommend to gather sniffer trace CCM and SDL traces from CCM to see what exactly is happening.

ouhakheme Thu, 05/31/2007 - 03:57


No the phones at the main site never unregister either.

I will start those traces and see what comes up!


neesharm Thu, 05/31/2007 - 00:07

have you alreday tried removing tftp caching from Advance TFTP service parameters:

"Enable Caching of Constant and Bin Files at Startup" set to False

"Enable Caching of Configuration Files" set to False

"Build CNF files" set to Build All

Restart the TFTP service after making the changes.

ouhakheme Thu, 05/31/2007 - 08:20

Just FYI, Disabling the tftp cache did not solve the problem.

rschwendeman Wed, 05/21/2008 - 19:10

Did you find a answer to your issue, I am running into the same issue with IP Communicator over a vpn connection.

ouhakheme Thu, 05/22/2008 - 07:18

The final answer was that the phones were loosing keepalives somewhere. Enough so that the phone would restart, the invalid SCCP message was just a byproduct.

In the end there wasn't too much that we could do about it.


This Discussion