[cisco-voip] device type mismatch from call manager..
Go0se
me at go0se.com
Wed Aug 4 14:50:14 EDT 2010
Just a thought, a common mistake I've seen is building a 7941G or 7961G as a
7941G-GE or 7961G-GE or vice versa.
Thanks,
Go0se
My blog:
http://atc.go0se.com
--------------------------------------------
Help Hopegivers International
Feed the orphans of Haiti and India
http://www.hopegivers.org
--------------------------------------------
-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ed Leatherman
Sent: Wednesday, August 04, 2010 11:59 AM
To: Cisco VOIP
Subject: [cisco-voip] device type mismatch from call manager..
All,
I'm getting a Device type mismatch syslog message about a specific device,
which seems straight forward enough - but when I go hunting for the device
in call manager to see what model it's configured as, it doesn't find the
device. Is this normal? I expected to find a 7962 that was configured as a
7961 by accident or something similar that I could correct.
CM 7.1.5
Aug 4 12:33:39 10.192.2.12 405102: Aug 04 16:33:39.265 UTC :
%CCM_CALLMANAGER-CALLMANAGER-3-DeviceTypeMismatch: Device type mismatch.
Name of device.:SEP0011211161EE Device type.:7 Database device type:255 App
ID:Cisco CallManager Cluster ID:OWP-PUB-Cluster Node ID:owp-sub-a Aug 4
12:33:39 10.192.2.12 405101: Aug 04 16:33:39.251 UTC :
%CCM_CALLMANAGER-CALLMANAGER-3-StationEventAlert: Station alert.
Protocol:SCCP TCP ProcessID:2.100.9.389509 Device Text:6:
Name=SEP0011211161EE Load=8.1(2.0)File Not Found Param1:2048
Param2:-113854710 App ID:Cisco CallManager Cluster ID:OWP-PUB-Cluster Node
ID:owp-sub-a Aug 4 12:33:39 10.192.2.12 405848: : ccm: 405053: Aug 04
16:33:39.251 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-StationEventAlert:
Station alert. Protocol:SCCP TCP ProcessID:2.100.9.389509 Device Text:6:
Name=SEP0011211161EE Load=8.1(2.0)File Not Found Param1:2048
Param2:-113854710 App ID:Cisco CallManager Cluster ID:OWP-PUB-Cluster Node
ID:owp-sub-a
I ran a sql query both on the publisher and the subscriber that is sending
the error message, couldn't find anything in the device table for this one:
admin:run sql select * from device where name="SEP0011211161EE"
It just returns an empty set. How can there be a device type mismatch if
there is nothing in the database for it?
--
Ed Leatherman
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
More information about the cisco-voip
mailing list