06-20-2012 04:07 AM - edited 03-21-2019 09:48 AM
I have had provision spa122 with new beta firmware spa122-1-2-0-028.bin.
In other topic i saw that spa122 is taking too long to provision. I figure out why is that so: every time (even if I put spa122 with latest firmware) spa122 upgrading firmware over and over again. Config files takes about 1-1,5 minutes and it is configured, but firmware upgrade takes about 7 minutes and here is the problem. I've tried everything...
So, my question is: HOW TO STOP SPA122 SO THAT SHE DOESN'T TAKES FIRMWARE MORE THAN ONCE?
Spa2102 upgrades firmware only 1. time provisioning, I need for spa122 to do upgrade only 1. time!
06-27-2012 03:43 PM
The taking too long to provision has been addressed by dev for the 1.2.0 release that will be coming out in a couple of weeks. It should resolve the upgrade over and over issue...
07-23-2012 02:11 PM
Its been a few weeks, where are we on the new firmeware for this issue?
07-31-2012 02:53 AM
I have about a dozen of these units waiting for a stable version of the firmware to appear, meanwhile I am using a Grandstream alternative, which in fairness will probably stick with if the SPA122 continues on its current path, so, wher is ver.1.2.0..?
08-03-2012 11:34 AM
What Grandstream are you using? I can't have my techs taking 20 minutes per job waiting for the 112 to upgrade, and we
are almost out of our pap2t's that worked great.
How are the Grandstreams at upgrading and configuring via http or tftp?
08-03-2012 11:57 AM
Hi, I am using the Handytone 502 (2 x FXS) , but also now have quite a few GXW4004/8 units which are great (4 and 8 x FXS), all easy to configure and none of the registration or quality issues we ahve in the current SPA range. Not so keen on the Grandstream IP phones but as far as the gateways are concerned they make a good alternative for the pap2t.
08-03-2012 12:42 PM
Is the firmware update coming out or do I start testing with another device? If I change and it works we won't come back until they stop making them.
Worst part is I have over 100 of the spa112's sitting here that dont work.
08-03-2012 01:18 PM
The upcoming release will be posted within 2 weeks. Thank you.
08-14-2012 12:21 PM
Will that release include fixes to the DTMF problem that crept back into the Beta releases as well as the other issues? I've got 1.2.1.004, and that one's not quite ready for prime time.
08-15-2012 09:46 AM
Are we still on track for a Friday release?
If not does anyone have a large number of PAP2T's they want to sell. We will also do a trade of some useless spa112.
08-15-2012 10:18 AM
Firmware 1.2.1 was released on 13 Aug 2012. It is currently on the cisco.com site
08-15-2012 10:55 AM
Fine, but please tell me what special military clearance I need to get passed the "Forbidden Download" message for both firmware and release notes? This really is getting beyond a joke!
08-15-2012 11:06 AM
Good question. What's even more disturbing is that I had to sign yet another Beta Firmware agreement Friday for version 1.2.1.004. I tested that FW on Monday, and reported back the issues still present. They are supposed to be looking at three major issues I have tickets open for. Meanwhile, they released 1.2.1.??? on Friday - before they even sent me the link to pick up the Beta.
08-20-2012 08:17 AM
Dont upgrade to 1.2.1 I have have problems with every one that went into the field. I left 3 plugged in in my lab over the weekend and 1 was down and would not reconnect. It required a full reset to get it to connect. I also have had 2 stop requesting DHCP 1.1.0 was a much better production firmware, we had issues provisioning it but never had issues in the field. I have about 100 deployed so far we have never replaced on with 1.1.0 but have had to replace very one (about 10) that went out with 1.2.1
08-22-2012 06:57 AM
So, can we use this fw 1.2.1 or you do not recommend it??
Nomado VoIP provider
Best Quality Rate of VoIP (datanews.com)
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: