cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
235
Views
0
Helpful
2
Replies

Tango Mobile Device COP Integration

dontraister
Level 1
Level 1

We have installed the cmterm-TangoMobile-11.0v1-sip.k3 COP file on a CUCM 11.5 system. After adding a Device for a User we are unable to Register to this device from the Application Server. We get the following in a Svc Trace that indicates it cannot recognize the typemodel being passed in the Registration message:

05758193.003 |20:34:09.031 |AppInfo  |SIPStationD(11039) - getTypeModel: User-Agent header is NULL, assuming PREFERRED_VENDOR_UA, useCepnForContact false
05758193.004 |20:34:09.031 |AppInfo  |SIPStationD(11039) - model=36234, mUaType=6
05758193.005 |20:34:09.031 |AppInfo  |SIPStationD(11039) - Register instanceId (MAC addr) =NULL
05758193.006 |20:34:09.031 |AppInfo  |SIPStationD(11039) - Register deviceName (database key) =TGOMMASTERSON
05758193.007 |20:34:09.031 |AppInfo  |SIPStationD(11039) - DevStat-Start    : transport UDP, model 36234
05758193.008 |20:34:09.031 |AppInfo  |SIPStationD(11039) - No Supported header
05758193.009 |20:34:09.031 |AppInfo  |SIPStationD(11039) - setDefaultOptions: INFO - user agent 6
05758193.010 |20:34:09.031 |AppInfo  |CcmdbStationRegistrationProfileBuilder::init - No typemodel table-entry for device TGOUSER.
05758193.011 |20:34:09.031 |AppInfo  |CcmdbStationRegistrationProfileBuilder::getBasicRegistrationProfile::init() - failed rc(1)
05758193.012 |20:34:09.031 |AppInfo  |Non-Cisco entity registration lookup failed. Recycling registration to digest challenge the endpoint.

The information is passed in the Contact Header of the SIP Registration message:

;+u.sip!model.ccm.cisco.com="36234";+u.sip!devicename.ccm.cisco.com="TGOUSER"

I was reading about other Third Party SIP device COP installation and they indicated we should restart the Tftp Service. We tried this and it did not fix the issue. An article on the Jabber COP says to restart the entire CUCM. We have not been able to schedule this yet.

Any thought on this would be greatly appreciated. Thanks.

2 Replies 2

Jaime Valencia
Cisco Employee
Cisco Employee

After adding support for a new device, you need to perform a cluster reboot.

Restarting the TFTP only works if all you're adding are files to the TFTP, not modifying the DB for new endpoints.

HTH

java

if this helps, please rate

Thanks Jamie.