I just purchased this ATA a month ago (firmware 1.0.1-022) .......loaded up my providers info, unit registers fine, calls work fine, but noticed that the Caller ID was not working correctly. After complaining to my provider that their service for the Caller ID was not working, they tell me everything is fine on their end. I then realized that it was the SPA112 with the issue! Thus, I download the lastest firmware (1.1.0-011) & do the upgrade..............now the darn thing will not register to my SIP Provider! I thought that maybe a setting or something might have change, but after triple checking all the settings, everything is corrrect. I register with another provider which registers fine & the caller ID now works. Being that I prepaid with the original provider for a year of service, I downgrade to the old firmware to use the service, but I still don't have Caller ID. It was very important that I had the 'Keep Nat Alive- On' function which was why I purchased this ATA to being with. Am I missing something with this upgraded firmware? Did anyone else have an issue with registration problems after upgrading to this new firmware? Thanks for any help, insight or thoughts.
Could be an issue with your provider's software. See this corresponding thread I had started:
I had the same problem this morning after an update of SP112 from firmware 1.0.1 to 1.1: no more SIP registration so no voice services.
Using a protocol analyser, I have found: the SIP REGISTER Request is no more issued after the firmware upgrade.
This is confirmed by the [Voice] page in the device: Registration failed.
- if downgrade to 1.0.1 or 1.0.6: perfectly working again
- 1.1.0: not working
I have checked that the DNS resquest (on voip.vtx.ch) is working properly but is returning an alisa (CAME) first. This
seems to destatibilize the SPA112 because if I enter the SIP Proxy directly in IP (184.108.40.206) it works perfectly again !
So workaround in my case: enter SIP Proxy as IP address, without use of DNS resolution
I would think Cisco has a regression on this firmware on DNS resolution function.
Yes, that was the problem/issue.............now the unit registers fine! I bought this Cisco ATA because I was expecting it to be the best named company out there for communications, but now after these few mishaps that I am having with these constant firmware upgrades.........I think that I will be looking somewhere else for my next ATA. My thanks to everyone who took the time to drop me a line & offered help!
I have opened a case by Cisco Small Business Support for software bug. We are Cisco partner for years and using the professional products line with very high success. This is the first time we try to use a Small Business product...
I will update here later.
Hi Chr, Oliver, and Community,
I replicated this in my lab and have filed CDETS# CSCtz15420 against this issue.
I have also alerted the Product Manager.
any news, when this will be fixed and a new firmware released?
I am also affected
I tested the *beta* firmware 1.2.0-019 last week. This bug is corrected. But no idea if / when this will be made available to all.
We also started to test T.38 fax capability on a TELES VoIP plateform with different fax machines up to 33.6 kb/s. Seems to be good until now.
I'm also having a problem simular to that as well. The person I'm calling can't here me, but I can here them.