[cisco-voip] DeviceTypeMismatch for phone that works fine

Wes Sisk wsisk at cisco.com
Sun Apr 16 20:10:35 EDT 2006


Erick,

I appreciate your zest and apologize for the colloquialism.  We use  
'recreate' is when TAC or other Cisco personnel setup the same  
hardware, software, versions, and scenario in our internal labs.  We  
try to follow the exact same actions as you to see which specific  
step causes the behavior in question.

During normal registration the 7920 correctly reports that it is a  
typemodel=30002.  There is some unique state transition that happened  
to this phone so it reported typemodel=7 during registration.   
Without having logs from the 7920 itself the only indication of the  
previous state transitions of the 7920 are the CCM traces.   
Specifically the Last= statement is the phone's report to CM of why  
it last unregistered from CM.  That gives us some insight on the most  
recent states of the phone to attempt to isolate the erroneous code  
executing path.

/Wes


On Apr 16, 2006, at 4:39 PM, Erick Bergquist wrote:

Is there steps to do the re-create process on cisco somewhere or can  
you send me the steps if it is something other then deleting phone  
from CCM and adding it back as a new device?  I am seeing the same  
thing across 3-4 clients with 7920s. Some that upgraded and some that  
were installed on a 4.x version from the get-go.

The one I looked at was ICMP-Unreach for last reason but I figured  
they may have just went out of wireless reach, etc. I'll see if I can  
look at some of the others if the trace files are still around or  
wait for the next occurance.

Thanks Wes.

----- Original Message ----
From: Wes Sisk <wsisk at cisco.com>
To: Erick Bergquist <erickbe at yahoo.com>
Cc: ciscovoip <cisco-voip at puck.nether.net>
Sent: Saturday, April 15, 2006 11:01:15 AM
Subject: Re: [cisco-voip] DeviceTypeMismatch for phone that works fine

When 7920's were first released to run with CM 3.x they emulated a
7960 (typemodel=7).  Later the 7920 received their own typemodel=30002.
The 7920 was not a valid device id until CMv3.3.2es41.  3.3(2)spC
came before support for 7920 was added.

I see the  phone claims to be running load 4.0(02.00) in the ALARM
message.  that's pretty clearly a 7920 load so it's not another model
phone with a case of mistaken identity.

7920 load 2.0 is just recently release, open a TAC case please so we
can setup a recreate.  To clarify exactly when this happens - is the
unregister reason always 'Last=CM-ICMP-Unreach' or does it even
happen when you power the phone off/on (Last=Initialized) or reset
the phone from CCMAdmin (Last=ResetRestart)?

/Wes

On Apr 14, 2006, at 4:39 PM, Erick Bergquist wrote:

Anyone ever see a error on devicetypemismatch for a phone that has
been working on system previously and programmed for awhile? This is
a 7920 phone which I can understand will come and go depending on
wireless, but a device mismatch error? This is on 4.1(3)sr1 and I
checked for bugs and release notes and nada on devicetypemismatch.

Any one have list of database device types or know what 30002 is?

Event Type:    Error
   Event Source:    Cisco CallManager
   Event Category:    None
   Event ID:    3
   Date:        4/14/2006
   Time:        1:50:55 PM
   User:        N/A
   Computer:    CALLMANAGER
   Description:
   Error: DeviceTypeMismatch - Device type mismatch.
     Name of device.: SEP0014F2C86427
     UNKNOWN_PARAMTYPE:Device type: 7
     UNKNOWN_PARAMTYPE:Database device type: 30002
     App ID: Cisco CallManager
     Cluster ID: StandAloneCluster
     Node ID: x.x.x.x
   Explanation: Device type passed on by the indicated device does not
   match the database configuration.
   Recommended Action: Verify database configuration for the indicated
   device..

FROM CCM DETAILED TRACES:

04/14/2006 13:50:55.776 CCM|New connection accepted. DeviceName=, TCPPid
= [1.100.132.3085], IPAddr=x.x.x.x, Port=0, Device
Controller=[0,0,0]|<CLID::StandAloneCluster><NID::x.x.x.x><CT::0,0,
0,0.0><IP::><DEV::>
04/14/2006 13:50:55.792 CCM|StationInit: (0000000) alarmSeverity=2
text="25: Name=SEP0014F2C86427 Load=4.0(02.00) Last=CM-ICMP-Unreach"
parm1=2049(801)
parm2=1234(4d2).|<CLID::StandAloneCluster><NID::x.x.x.x><CT::1,100,
119,1.2520693><IP::x.x.x.x><DEV::>
04/14/2006 13:50:55.808 CCM|StationInit: (0000000) InboundStim -
StationRegisterMessageID: Msg Size(received, defined) = 48,
56|<CLID::StandAloneCluster><NID::x.x.x.x><CT::1,100,119,1.2520694>
<IP::x.x.x.x><DEV::>
04/14/2006 13:50:55.808 CCM|StationInit: (0000000) InboundStim -
StationRegisterMessageId [Normal Device priority]:
|<CLID::StandAloneCluster><NID::x.x.x.x><CT::1,100,119,1.2520694><I
P::x.x.x.x><DEV::>
04/14/2006 13:50:55.808 CCM|Processing StationReg. regCount: 1
DeviceName=SEP0014F2C86427, TCPPid = [1.100.132.3085],
IPAddr=x.x.x.x, Port=0, Device
Controller=[1,118,2344]|<CLID::StandAloneCluster><NID::10.117.30.10><CT:
:1,100,119,1.2520695><IP::x.x.x.x><DEV::SEP0014F2C86427>
04/14/2006 13:50:55.808
CCM|dBProcs::readStationRegistrationProfileByDeviceName
started|<CLID::StandAloneCluster><NID::x.x.x.x>
04/14/2006 13:50:55.808 CCM|dBProcs - hash find device start, num of
Caching Entries = 307|<CLID::StandAloneCluster><NID::x.x.x.x>
04/14/2006 13:50:55.808 CCM|dBProcs - hash find device end, num of
Caching Entries = 307|<CLID::StandAloneCluster><NID::x.x.x.x>
04/14/2006 13:50:55.808 CCM|StationD:    (0002344) ClusterSecurityMode =
(0) DeviceSecurityMode =
(1)|<CLID::StandAloneCluster><NID::x.x.x.x><CT::1,100,119,1.2520695
> <IP::x.x.x.x><DEV::SEP0014F2C86427>
04/14/2006 13:50:55.808 CCM|DeviceTypeMismatch - Device type mismatch.
Name of device.:SEP0014F2C86427 UNKNOWN_PARAMTYPE:Device type:7
UNKNOWN_PARAMTYPE:Database device type:30002 App ID:Cisco CallManager
Cluster ID:StandAloneCluster Node
ID:x.x.x.x|<CLID::StandAloneCluster><NID::x.x.x.x><CT::AlarmSE
P0014F2C86427><DEV::SEP0014F2C86427>
04/14/2006 13:50:55.808 CCM|StationD:    (0002344)
registrationProfile_discovery_DbStationRegistrationProfileRes sent
StationOutputRegisterReject|<CLID::StandAloneCluster><NID::x.x.x.x>
<CT::1,100,119,1.2520695><IP::x.x.x.x><DEV::SEP0014F2C86427>
04/14/2006 13:50:55.808 CCM|StationD:    (0002344) RegisterReject
text='Error: Device type
mismatch'.|<CLID::StandAloneCluster><NID::x.x.x.x><CT::1,100,119,1.
2520695><IP::x.x.x.x><DEV::SEP0014F2C86427>
04/14/2006 13:50:55.823 CCM|StationInit:   TCPPid =
[1.100.132.3085]Socket Broken.
DeviceName=SEP0014F2C86427,IPAddr=10.117.40.79, Port=0x0, Device
Controller=[1,118,2344]|<CLID::StandAloneCluster><NID::x.x.x.x><CT:
:1,100,132,3085.1><IP::><DEV::>
04/14/2006 13:50:55.823 CCM|Closing Station connection
DeviceName=SEP0014F2C86427, TCPPid = [1.100.132.3085],
IPAddr=x.x.x.x, Port=0, Device
Controller=[1,118,2344]|<CLID::StandAloneCluster><NID::x.x.x.x><CT:
:1,100,132,3085.1><IP::><DEV::>



_______________________________________________
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