cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1495
Views
0
Helpful
4
Replies

Device Mismatch Ascom device

leulaciah1
Level 1
Level 1

Hi,

I'm trying to register a Ascom device in a CUCM 9.1.2. I upload a Ascom cop in order to CUCM recognize the Device type. After that, I reset TFTP server and also CUCM. In the device list appear, but the CUCM reject the registration saying Device mismatch:

00002202.013 |15:12:30.681 |AppInfo  |CcmCcmdbHelper::getDeviceNumPlanMapRecordsGivenDevicePkid - FAILED device pkid(efc03ff8-a2c2-f95d-d9f6-13208ae3b4d0)

00002202.014 |15:12:30.681 |AppInfo  |CcmCcmdbHelper::getDnAndMwiData - getNumPlanAndDeviceNumPlanMapRecordsGivenDevicePkid() device pkid(efc03ff8-a2c2-f95d-d9f6-13208ae3b4d0) returned FALSE (= no items).

00002202.015 |15:12:30.681 |AppInfo  |GetMaxCallForDevice: cannot find entry in ProductSupportsFeature table for product 485 and protocol 11feature SUPPORTS_FEATURE_RESTRICT_MAX_CALLS

00002202.016 |15:12:30.681 |AppInfo  |GetMaxCallForDevice: cannot find entry in ProductSupportsFeature table for product 485 and protocol 99feature SUPPORTS_FEATURE_RESTRICT_MAX_CALLS

00002202.017 |15:12:30.681 |AppInfo  |$URI CcmdbStationRegistrationProfileBuilder::getSipExtensionByDeviceName: Disambiguation Policy - deviceName=SEPFFFFFFFF4523, sipprofile.name=Standard SIP Profile, sipprofile.tkuridisambiguationpolicy_m=URIDISAMBIGUATIONPOLICY_DNIFONLYDIGITSTARPLUS [4]

00002202.018 |15:12:30.681 |AppInfo  |AS-SIP Default NS =

00002202.019 |15:12:30.681 |AppInfo  |AS-SIP From Device Row , fksipprofile = fcbc7581-4d8d-48f3-917e-00b09fb39213

00002202.020 |15:12:30.681 |AppInfo  |AS-SIP From sip profile row , ns pkid =

00002202.021 |15:12:30.681 |AppInfo  |AS-SIP No namespace found

00002202.022 |15:12:30.681 |AppInfo  | AS-SIP getResourcePriorityNameSpace FAIL

00002202.023 |15:12:30.681 |AppInfo  |SIPStationD(1) - UA type determined to be generic, but device type in the database is not one of the generic models.

00002202.024 |15:12:30.681 |AppInfo  |DeviceTypeMismatch - Device type mismatch between the information contained in the device's TFTP configuration file and what is configured in Unified CM Administration for that device Name of device:SEPFFFFFFFF4523 Device type:336 Database device type:598 App ID:Cisco CallManager Cluster ID:StandAloneCluster Node ID:CUCMPRUEBA

00002202.025 |15:12:30.681 |AlarmErr |AlarmClass: CallManager, AlarmName: DeviceTypeMismatch, AlarmSeverity: Error, AlarmMessage: , AlarmDescription: Device type mismatch between the information contained in the device's TFTP configuration file and what is configured in Unified CM Administration for that device, AlarmParameters:  DeviceName:SEPFFFFFFFF4523, DeviceType:336, DBDeviceType:598, AppID:Cisco CallManager, ClusterID:StandAloneCluster, NodeID:CUCMPRUEBA,

00002202.026 |15:12:30.681 |AppInfo  |EndPointTransientConnection - An endpoint attempted to register but did not complete registration Connecting Port:5060 Device name:SEPFFFFFFFF4523 Device IP address:10.34.42.10 Device type:336 Reason Code:32 Protocol:SIP Device MAC address:EEEEEEEE4523 IPAddressAttributes:0 LastSignalReceived:SIPRegisterInd StationState:wait_register App ID:Cisco CallManager Cluster ID:StandAloneCluster Node ID:CUCMPRUEBA

If I register it as SIP third party, the device is registered properly. But I need to use the cop file to use advance functions.

Do you have any idea what could happen?

Many thanks

4 Replies 4

Jaime Valencia
Cisco Employee
Cisco Employee

If you installed a cop file to add support for a new endpoint, a cluster reboot is mandatory before you can actually use it and get anything registered.

You only mention you have restarted TFTP, but that's not enough.

HTH

java

if this helps, please rate

Hi,

I've also reboot the CUCM 3 times but it happens the same.

Regards,

Leire

Are you sure the .cop you installed is meant to enable the specific device you're trying to use??

HTH

java

if this helps, please rate

Bowen Qin
Level 1
Level 1

You will also need a cisco license on Ascom