A new ATA gets rejected by Callmanager

Answered Question
Sep 8th, 2010

Just upgraded our cluster to  7.1.5.31900-3 and now a new ATA 186 won't register with CCM. Tried another brand new one to no avail. It would get an IP address that is pingable but won't allow web access to it with an error "Invalid access". Hooked up a working ATA to the same jack and it came up just fine. I suspect both ATA have some outdate firmware but do not know how to get over this issue.

Any help would be greatly appreciated.

Yefim

I have this problem too.
0 votes
Correct Answer by David Smith about 6 years 2 months ago

OK, then you're going to have to download  the 3.2.4 firmware from CCO, then TFTP the ATA.cnf.xml file from your current call manager to your PC, modify the ATA.cnf.xml file so that it's less than 4K in size...change the configuration in the file to reflect ATA030204SCCP090202A.zup firmware. Then configure the ATA manually using an analog phone to change the TFTP server to your PC's IP address,  put the new .cnf.xml file in your TFTP root, start up your TFTP sever on your PC and let the ATA upgrade to 3.2.4.

After this is done, manually change the ATA TFTP address back to CUCM, and let it re-register using the hosted .cnf.xml file.

Directions for pulling a file down from CUCM to your PC using TFTP via windows cmd prompt:

tftp get ATA.cnf.xml ATA.cnf.xml

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/tftp.mspx?mfr=true

Here's a guide on how to manually configure the ATA using a connected analog phone:

http://www.cisco.com/en/US/partner/products/hw/gatecont/ps514/products_configuration_example09186a00800c3a50.shtml#task3

If you have any issues feel free to open a TAC case.

Good luck

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
neil-jones Wed, 09/08/2010 - 08:46

ATA 186’s need to be at code rev 3.2.4 in order to work  reliably with the Call Manager 7

You can check the firmware by going to:

http://ATA ip  address/DeviceInfo

You can manually upgrade the ATA with an analog phone plugged in to it

David Smith Wed, 09/08/2010 - 09:16

Yefim,

Since you upgraded to 7.X CUCM and are now seeing this issue, you're most likely hitting:

CSCsd44357

/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} ATA186 Auto-Registration Fails if XMLDefault file exceeds 4k in Size

Like the previous poster mentioned, you need 3.2.4 to support a .cnf.xml file size greater than 4K.

So, you need to follow the workaround and make the .cnf.xml configuration file less than 4K, then upgrade the firmware to 3.2.4.

Release Note:

Since ATA cannot download config file "ATA.cnf.xml" from CCM if its size is over 4k,
ATA cannot get the load information in it  to start upgrating the new firmware.

As a workaround to upgrade the patch, the custom could  temporarily decrease  the config file size to 4k or smaller, such as only keep one CCM in CM group, disable all build-in Phone Services (for CCM 7.x).

Another workaround:  generate the atadefault.cfg which also includes a load information, and save this file to TFTP network locale path, for example "\United_States\atadefault.cfg". ATA will try this file if it cannot get cnf.xml

Good luck

Correct Answer
David Smith Wed, 09/08/2010 - 09:35

OK, then you're going to have to download  the 3.2.4 firmware from CCO, then TFTP the ATA.cnf.xml file from your current call manager to your PC, modify the ATA.cnf.xml file so that it's less than 4K in size...change the configuration in the file to reflect ATA030204SCCP090202A.zup firmware. Then configure the ATA manually using an analog phone to change the TFTP server to your PC's IP address,  put the new .cnf.xml file in your TFTP root, start up your TFTP sever on your PC and let the ATA upgrade to 3.2.4.

After this is done, manually change the ATA TFTP address back to CUCM, and let it re-register using the hosted .cnf.xml file.

Directions for pulling a file down from CUCM to your PC using TFTP via windows cmd prompt:

tftp get ATA.cnf.xml ATA.cnf.xml

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/tftp.mspx?mfr=true

Here's a guide on how to manually configure the ATA using a connected analog phone:

http://www.cisco.com/en/US/partner/products/hw/gatecont/ps514/products_configuration_example09186a00800c3a50.shtml#task3

If you have any issues feel free to open a TAC case.

Good luck

y-sapozhnikov Fri, 09/10/2010 - 06:12

I'd like to thank everybody for your input. I ended up opening a TAC case.

Thanks,

Yefim

jilfersalam Sun, 11/07/2010 - 00:26

Hi Yefim,

Was this issue resolved? It would be helpful if you can post the TAC findings, and the steps on how this issue was resolved.

Jilfer

y-sapozhnikov Mon, 11/08/2010 - 07:20

Here is the steps:

CSCsd44357    ATA186 Auto-Registration Fails if XMLDefault file exceeds 4k in Size

Now to get over this bug you would need to follow these steps.

1. Download the firmware ( only the ZIP file) from cisco

2. Extract file to a location. Make sure you have a ZUP file there.

3. Open command prompt on XP machine and runt this command

Tftp get XmlDefault.cnf.xml

You would get an XML file. Or use any TFTP daemon to get this file from CM.

4. Edit this XML file to the file below or you can skip step 2 and use the file below.

Important thing is to make sure that IP

address of CUCM is populated and make sure we have the correct firmware version there.

  priority="0">

2000

IP ADDRESS OF YOUR TFTP SERVER

ATA030204SCCP090202A.zup

1

0

Save the file as XMLDefault.cnf.xml using notepad ( all files)

5. configure a TFTP server using any tool , and put these files ( firmware and xml default) on a TFTP location.

6. From ATA gui point it to this TFTP server.

Or another option if we have a large deployment just Change option 150 to our TFTP server temporarily .

jilfersalam Mon, 11/08/2010 - 08:17

Thanks for the reply, we did this yesterday. Actually did both methods, the one creating a config file by the cfgfmt.exe as well as the xml edit method...both worked. But for ATA's with firmware version 3.1.0, only the method u described worked.

Actions

This Discussion