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!
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...
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..?
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?
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.
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.
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.
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.
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!
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.
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
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)
I would not reccomend using 1.2.1 I keep having random problems with them in the field including dissapearing and not showing up in arp. We keep having to have our customers hold the reset button in to get them to come back up I have 11 of them on my bench that have done this. I am working on reproducing it here, but we have gone back to 1.1.0. and had to do a truck roll to every one that we installed with 1.2.1
yes we can do it via tftp by simply plugging in the spa. The issue is that it takes somewhere between 2 and 30 minutes for it to get all its files and upgrade.
I have my files splt into 3 different ones
spa112.cfg has the upgrade rule to push firmware and profile rule to go to spa112-110.cfg
spa112-110.cfg has all my default configs and points profile rule b to the mac specific file.
Doing this often requires finding the ip address and doing an admin/resync or power cycling several times.
The PAP2t was so much better. We can provision one in less than a minute every time
You should be aware that there's a regression in 1.2.1 where users that attempt to use DTMF - like dialing towards IVRs, etc - will have problems because the ATA does not mute the calling parties original DTMF audio as generated by their telephone. This results in double digits, etc. I've got case open, and are working with them on that and several other issues.
Bob, have you gotten any update since August about the DTMF issue in v1.2.1?
I've just recently been running into this issue with a handful of the SPA122s that I upgraded from v1.1.0 to v1.2.1. I have two ATAs sitting side by side with the two different firmware revisions, and even with identical configurations, they absolutely behave differently.