Cisco ATA 186 "Device is not trusted"

[samer_waleed]

Hi All,

After upgrading Call Manager from 6.x to 7.1.3 our Cisco ATA 186  is not working and when looking at the configuration page for the Cisco ATA 186  it states "Device is not trusted". Can anyone please explain why this is happen.

Thank you.

[Clifford McGlamry]

I believe the trust you're referring to referst to PKI.  That's a non issue.

Check the following:

1.  Open the internal web page on the ATA186.  http:// address of device>/dev 

     a.  Does it have the right TFTP info?

     b.  Doest if have the right CCM info?

     c.  Does the firmware version on the unit match what is in the device defaults on CCM? 

There is a known issue regarding firmware upgrades to this class of devices that happens at about CUCM 7.1(3) You can do an off line upgrade, or use a work around to get it to upgrade, but both are a pain.

Cliff

Please rate helpful posts    

[samer_waleed]

Thank you

all info are ok. I upgraded it to 7.1.5

and still the error.

[Clifford McGlamry]

Given that you're providing almost no information that can be used to help you, it's hard to do much more than guess.  The only suggestion I can make is that you do a reset to factory defaults on the ATA. 

If that does not address your issue, you'll need to open a TAC case, or start providing a lot more information on this thread (such as logs, screen shots of settings, etc.). 

Cliff

[Emilio Manzaneque · Accepted solution]

Hello,

I had the same problem and I solved it in this way:

• 1.        In my PC I installed WinAgents TFTP server

http://www.winagents.com/en/downloads/download-tftp-server.php

2.       From sk_example.txt template, located in zip version of ATA firmware, I made my own configuration file (my_conf.txt), making, on the original file, the following changes:

upgradecode:3,0x301,0x0400,0x0200,10.201.3.11,69,0x020514a,ATA030204SCCP090202A.zup

Where 10.201.3.11 is my CUCM TFTP server

Also, I made other changes for fit the ATA configuration to my case (Spanish ring tones, etc)

UIPassword:[My password]

ConnectMode:0x90002400

AudioMode:0x00150015

ialTone:1,30958,0,4895,0,1,0,0,0

DialTone2:2,29780,30743,1252,1384,1,0,0,1000,0,0

BusyTone:1,30958,0,1757,0,0,1600,1600,0

ReorderTone:100,1,30958,1757,0,0,0,0,2,1600,1600,1600,4800,0,0,1,0

RingBackTone:1,30958,0,1757,0,0,12000,24000,0

CallWaitTone:1,30831,0,5493,0,0,2400,2400,4800,0,0

AlertTone:1,30467,0,5970,0,0,480,480,1920,0,0

• 2.        With cfgfmt tool, also included in firmware file zip version, I did my own atadefault.cfg:

cfgfmt -sccp -tptag.dat my_conf.txt atadefault.cfg

• 3.        Then, I uploaded my atadefault.cfg to my TFTP server (my PC).
• 4.        From ATA Web configuration page, I changed the alternate TFTP field with my PC IP.

ATAs load the default CM firmware, 3.2.4 in my case, and after registered in the CM cluster (7.1.5) without problems.