SPA 500 series - TFTP Firmware Upgrade Problem with FW 7.4.3a

[jingt0829]

Hello,

I am having problems with firmware upgrade by using TFTP server.

I tested with SPA 504G and 502G, both of them came with firmware 7.4.3a by default.

The CNF config is:(xxx.xxx.xxx.xxx represents the IP address of my TFTP server)

    <Profile_Rule ua="na">/spa$MA.cfg</Profile_Rule>
    <Upgrade_Rule ua="na">( $SWVER ne 7.4.7 )? tftp://xxx.xxx.xxx.xxx/sw/spa50x-30x-7-4-7.bin</Upgrade_Rule>

What I found is:

• If I leave the phones with default firmware  7.4.3a, the phones can download config, but firmware can not be upgraded.
• If I manually change the default firmware to other version, e.g 7.4.6, then the firmware can be upgraded to 7.4.7 without any issue.
  

Is there anything wrong with firmware 7.4.3a, any restriction ?

Does anyone have the same problem ?

Any help will be appreciated, thanks in advance.

Jing

[stpaulalex]

I just deployed about 30 4's and 8's that came with 7.4.3a.  Upgraded firmware over TFTP with no problem.  I'm working on a homework assignment, so I really dont have time right now to go into detail, but I may have posted what I did on stpaultechies.com.

-Alex

[jingt0829]

Thanks a lot for your reply, Alex.

If you can post your cfg file, that will be great.

BTW, I am using Asterisk.

Thanks again

Jing

[Kevin Tomomitsu]

Yeah, we ran accross the same problem on 7.4.3, what

we ended up doing is manually upgrading to 7.4.6 which then allowed the phone to use the upgrade URL to

upgrade via TFTP to 7.4.7. You may want to take the phones to the lates firware which is 7.4.8. we are in the process of upgrading our phones.

[Steven DiStefano]

DONT TAKE 7.4.8 please

https://supportforums.cisco.com/message/3322253#3322253

[stpaulalex]

In either spa50XG.cfg or spaxxxxxxxx.xml, this line controls the upgrade:

/spa.bin

For the initial provisioning, I think I put this in the individual xml files for each phone.  Just make sure the spa.bin file exists on the TFTP server in the root directory.  You can really use any name for this; just make sure it matches.  I decided to use spa.bin for the current fleet-wide release, and spa7xx.bin for any alterations.

[Patrick Born]

Jing,

Here's a simple config file that will help you upgrade from a factory-fresh 7.4.3(a) phone.
I've also attached the source so you can easily edit the names and IP addresses to suit your environment.:

http://www.sipura.net/xsd/SPA5X5G-SIP" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.sipura.net/xsd/SPA5X5G-SIP http://www.sipura.net/xsd/SPA5X5G-SIP/SPA5X5G-SIP-7-4-7.xsd">

  No
  No

  10.10.10.10
  3

  http://192.168.2.244/sw/spa/spa50x-30x-7-4-6.bin

  300
  http://192.168.2.244/Cisco/SPA504G/$MA.cfg

  StationName
  StnDspNme

  1
  8002
  private
  private
   
  --removed--
  290
  Yes
  Yes
  BS8002
  --removed--
  --removed--
  No
 
  Yes
No

For this sample, my DHCP server sends OPTION 66 that contains only a TFTP server:

causing my SPA504G phone to look for  tftp://Cisco/SPA504G/phoneMAC.cfg:

The phone then loads the config and requests an upgrade using the path that I defined in the config:

Regards,

Patrick

----------

[Patrick Born]

Hi Jing,

The 7.4.3(a) firmware can be troublesome to upgrade, depending on your upgrade rule.

The issue was around the (a) suffix and the logic test in an upgrade rule.

We've improved the process in subsequent firmware releases.

Upgrade SPA phones from 7.4.3(a) using one of the following methods:

• http://phoneIP/admin/upgrade?tftp://serverIP/path/firmware.bin     // can be tftp or http
• Use a simple upgrade rule:

http://serverIP-FQDN/path/spa50x-30x-N-N-N8.bin>

• Use the exe file to upgrade an individual phone

Once the phone is upgraded beyond 7.4.3(a) you can use more sophisticated rules such as:

("$SWVER" != "7.4.7")? http://serverIP-FQDN/path/spa50x-30x-N-N-N.bin>

Regards,

Patrick

----------

One reference document to locate SPA phone resources

[jingt0829]

Hi Patrick

I tried the first method by removing the condition part. It worked.

Thank you very much for your help.

I have seen the post in regarding to unstable firmware 7.4.8, so I didn't bother to try it. I will still use 7.4.7 for now.

Thanks for your reply, Alex.

Thank you everyone.

Cheers.

Jing