Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

ATA 186 TFTP Provisioning and CCM 3.1.3(a)

I just have one question:

Can you or can you not provision/upgrade ATA 186's via TFTP using CCM 3.1.3(a)?

I have over 100 ATA's to get upgraded to image version 2.15ms, and I don't want to have to do them manually (call me crazy!). All of them right now have a 2.15.bl bootload image on them, and I need to get rid of that.

This is what I can do:

If I create my binary file called ATAxxxxxxxxxxxx, it will take my other settings, but it will not upgrade the image. I have come to the conclusion that either I'm not setting something correctly in that file, or that it's just not possible to upgrade the ATA boxes using TFTP in my version of CallManager (maybe something to do with the fact that 3.1 has to have them in as 7960 phones?).

I opened up a TAC case regarding this issue, and the tech immediately told me to upgrade to 3.2, which (to me) doesn't seem like much of a solution, since we have 700 IP phones and 200 VGC phones that work nicely with 3.1. Although I understand that in 3.2 you can insert an ATA as an ATA 186 phone, there must be some way of getting it to provision successfully with 3.1.

I have run the prserv.exe utility, and see the ATA receive the binary file successfully, but for the life of me, it won't upgrade its image (the image is sitting in the TFTP directory on the TFTP server, and the binary file points to it).

Any help would be greatly appreciated.

TMH

  • Other Collaboration Voice and Video Subjects
5 REPLIES
Cisco Employee

Re: ATA 186 TFTP Provisioning and CCM 3.1.3(a)

I haven't tested this to see if it works, but you can try creating an ATAdefault.cnf.xml file in the TFTPPath and in it put:

ata186-v2-15-ms-whatever.zup

If that doesn't work then try looking at a sniffer trace of an ATA 186 while resetting it to see which files it tries to get from the TFTP server.

New Member

Re: ATA 186 TFTP Provisioning and CCM 3.1.3(a)

I tried it - didn't work.

In the sniffer, it only successfully registers with CCM if it uses the SEPxxxxxxxxxxxx.cnf.xml file. Even if I create an ATAxxxxxxxxxxxx.cnf.xml file, or the atadefault.cnf.xml file, the ATA will take it, but I get DB Config errors and it will not upgrade the image (see output below). I'm thinking here that if there is an ATAxxxxxxxxxxx.cnf.xml file, it wants to register with CCM as an ATA, which I can't do in my version.

__

Wed Jan 08 10:07:17 2003 Hello from ata0008a3f4663f@192.168.221.85 (0-1)

Build 020726a: v2.15.bl ata186

>> Skinny <<

useUserInd = 1

useUserInd = 1

useUserInd = 1

useUserInd = 1

tftpIp=c0a8ea0c

tftp(0xc0a8ea0c,ATA0008a3f4663f.cnf.xml)

tftp: 66

tftp<66> ok!

read xml successful

found ATA0008a3f4663f.cnf.xml

Connecting to c0a8ea0c port 2000: -1 0...

tftpIp=c0a8ea0c

tftp(0xc0a8ea0c,ATA08a3f4663f01.cnf.xml)

[0]Connect to c0a8ea0c ok! Socket: 7

REG:ATA0008a3f4663f

tftp: -10

tftp(0xc0a8ea0c,SEP08a3f4663f01.cnf.xml)

tftp: 2257

tftp<2257> ok!

|->RegRej[0]:Error: DB Config

read xml successful

found SEP08a3f4663f01.cnf.xml

Connecting to c0a80c0c port 2000: -1 0...

[1]Connect to c0a80c0c ok! Socket: 10

Connecting to c0a8860c port 2000: -1 10...

[1]Connect to c0a8860c ok! Socket: 11

REG:SEP08a3f4663f01

TCP recv err[0]

sck<10:11>

Connecting to c0a8ea0c port 2000: -1 52...

[0]Connect to c0a8ea0c ok! Socket: 12

REG:ATA0008a3f4663f

|->RegRej[0]:Error: DB Config

TCP recv err[0]

sck<10:11>

Connecting to c0a8ea0c port 2000: -1 52...

[0]Connect to c0a8ea0c ok! Socket: 13

REG:ATA0008a3f4663f

|->RegRej[0]:Error: DB Config

TCP recv err[0]

sck<10:11>

REG:SEP08a3f4663f01

|->RegAck[1]

SkVer: P00303010107

PhNo:3174

LiNo:1

Connecting to c0a8ea0c port 2000: -1 52...

[0]Connect to c0a8ea0c ok! Socket: 14

REG:ATA0008a3f4663f

|->RegRej[0]:Error: DB Config

0:30;0,0,0,0,

TCP recv err[0]

sck<10:11>

Connecting to c0a8ea0c port 2000: -1 52...

[0]Connect to c0a8ea0c ok! Socket: 15

REG:ATA0008a3f4663f

|->RegRej[0]:Error: DB Config

TCP recv err[0]

sck<10:11>

Connecting to c0a8ea0c port 2000: -1 52...

[0]Connect to c0a8ea0c ok! Socket: 16

REG:ATA0008a3f4663f

|->RegRej[0]:Error: DB Config

TCP recv err[0]

sck<10:11>

Connecting to c0a8ea0c port 2000: -1 52...

[0]Connect to c0a8ea0c ok! Socket: 17

REG:ATA0008a3f4663f

|->RegRej[0]:Error: DB Config

TCP recv err[0]

sck<10:11>

Connecting to c0a8ea0c port 2000: -1 52...

[0]Connect to c0a8ea0c ok! Socket: 18

REG:ATA0008a3f4663f

1:00;0,0,0,0,

|->RegRej[0]:Error: DB Config

Cisco Employee

Re: ATA 186 TFTP Provisioning and CCM 3.1.3(a)

Okay. So can you try to trigger the upgrade using the SEPxxxxxxxxxxxx.cnf.xml file?

New Member

Re: ATA 186 TFTP Provisioning and CCM 3.1.3(a)

I am not sure that you would like to upgrade your ATA to version 2.15MS if you are using 3.1.3a

I have tried it on serveral boxes and it does not work. You only get one line (one port) for the ATA box.

Take a look at

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm#AdditionalDetails

As you can see the 2.15 has NA status for 3.1.3a.

New Member

Re: ATA 186 TFTP Provisioning and CCM 3.1.3(a)

We haven't had any issues with not getting the second port when using the 2.15MS image at all...I have @50 of them out right now working great with the latest 2.15MS image...

TMH

191
Views
0
Helpful
5
Replies
This widget could not be displayed.