07-27-2007 12:31 AM - edited 03-14-2019 10:48 PM
Hi hi,
Anyone has encountered this error in the CCM's event viewer? The phone is showing nothing on the screen and the buttons are not enabled. But in the CCM it shows the phone is registered. The phones are pingable from the CCM. Anyone has encountered this before?
Event Type: Error
Event Source: Cisco CallManager
Event Category: None
Event ID: 3
Date: 7/27/2007
Time: 4:09:51 PM
User: N/A
Computer: CM2
Description:
Error: StationEventAlert - Station alert.
TCP ProcessID: 5.100.139.692
Device Text: 32: Name=SEP001641E66534 Load= 2.1.1.0 : Invalid SCCP message! : Invalid length
Param1: 0
Param2: 0
App ID: Cisco CallManager
Cluster ID: StandAloneCluster
Node ID: 1.1.1.1
Explanation: Station device sent an alert to Cisco CallManager.
Recommended Action: Ensure that the configuration for identified device is proper..
08-02-2007 05:50 AM
There are some possible reasons that this problem occurs:
There can be replication issues between Cisco CallManager databases. In order to check this, run the DBLHelper app to check good replication. This is ideally located in c:\program files\cisco\bin\.
If the phones unregister across an Internet connection, this behavior can be expected once in a while. IP telephony design recommends end-to-end QoS configuration, which is something that is out of your control if you use the Internet.
The Spanning Tree Protocol (STP) is not configured on the switch so there are loops.
Cisco CallManager misses keepalives, therefore phones unregister.
The phone loads.
In order to resolve this issue, try to increase the keepalive timer on the Cisco CallManager in order to rule out a keepalive timeout issue. Go to the ccmadmin web page and under Service > Service Parameters, choose the server(s) that the IP phones are registered with. In Service*, choose Cisco CallManager. Change the value of Station Keep Alive Interval (sec)* to 45.
08-02-2007 09:22 PM
Thanks man for your inputs.
Will check this out!
Appreciate it!
05-21-2008 07:08 PM
Did you find what was causing your issue.
05-21-2008 10:17 PM
Hi,
That was really some time ago, but I think we just RMA the phone and the new one worked fine.
HTH,
Eugene
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide