The new SPA112 ATA is not allowing caller id to be displayed on inbound calls.
ATA has been updated to firmware Spa112-Spa122_1.0.2_006_FW and has been configured for callcentric.
( in USA).
any suggestions ?
Solved! Go to Solution.
Can you get a debug log so we can see if the unit receives the call ID in the From of the SIP message?
Details on obtaining log at
I have the same problem. I am using an SPA112 with callcentric. I contacted callcentric and they said that they are sending the caller ID info to me, and they appear to be doing so. I looked at my web interface on the Voice Info page while calling my number, and sure enough the caller ID shows on the VOice info page, so yes the SPA112 is receiving the caller ID data. But, I tried 2 different phones with caller ID display and receieved and INCOMPLETE DATA message on one of the caller ID's. SO it seems that the SPA112 is not sending the caller ID info it has to the phone set properly. Can we get a CISCO engineer to verify?
I think this issue has something to do with impedance and frequency output of the data to the caller ID module of the phone set.
I just opened a case with the Cisco Small Business Support Center. They have now confirmed that this is a known issue that has been reproduced and is impacting multiple customers.
Unfortunately they have no ETA for the fix and said to keep an eye on the firmware downloads page.
My Panasonic cordless phones show no caller ID at all, and my AT&T Model 436 Caller ID box shows "LINE ERROR" when the Caller ID info is transmitted after the first ring. This leads me to believe that the issue is in the FSK signaling to the analog phones.
I'm using VoIP.ms rather than CallCentric so this is impacting multiple VoIP carriers (which makes sense based on the behavior).
Thanks for getting this moving, it sucks to not have caller id.
I'm using an Elastix PBX (Asterisk) and when my IP phones that are in a ring group got caller id, but my analog Panasonic wireless handsets stopped getting it, it was easy to figure out where the problem was. The caller ID worked before I upgraded the firmware on my SPA112 to 1.0.2(006). I guess I'll roll back to 1.0.1.022. Hopefully the fix doesn't take to long since they've been able to reproduce the issue in the lab.
It seems to be intermittent with both firmwares.. I hope Cisco doesn't drag their feet on this one like they did with the other ATA's where a fix was promised for over a year and nothing. My chinese knockoff Linksys PAP2 even has working caller id.
Unfortunately for us, this is a new product so there aren't many of us to complain about it. I'm hoping this issue is being treated as a high priority one. Caller ID is important for most businesses and even for home users.
So far, I have not been able to get any more information on this. I have been told that I will be contacted by an engineer in tier 2 support but that has not happened yet.
Message was edited by: Jim Keagy
Jim, I appreciate your follow up and intend on hitting the forum frequently until this is resolved.
I'm not sure how a company like Cisco can let a product go to market with no caller id, pretty sad.
Hi, My name is Eric Moyers. I am a Network Support Engineer in the Cisco Small Business Support Center.
Sir what is your case number? I looked above but did not see it listed. I can personally check on this case and make sure that this is escalated for you, if it has not already been done. I can then email you back with the reults.
Cisco Network Support Engineer
SBSC Wireless and Surveillance SME
I called in this morning and was informed that my case is still in the process of being escalated and there are no other updates right now.
Cisco was short staffed this week like many other companies. I doubt we will hear anything else on this until Tuesday January 3 at the earliest.
Hello Mr.Keagy, Sorry for the delay in getting this escalated over the Holidays.. But I have escalated this today, If you have not heard anything from them by end of day tomorrow, please e-mail me and let me know.
If it wasn't bad enough to have callerid broken, now my SPA112 has stopped working twice this week. It just decides to stop providing dial tone. When you browse to the Voice section on the web interface it simply says "Voice module not ready.". When I try to reboot it from the web interface it says
"Changes cannot be applied while calls are in progress. Please try again when phones are idle.", although there are NO calls in progress. Logs show nothing. I just turned on debug level syslogs to see if I can catch this nice one in the future.
I haven't experienced the "Voice module not ready" and no dial tone issue yet. Have you opened a support ticket with Cisco for this issue?
Also I would like to than Eric for escalating my Caller ID ticket. Hopefully I will hear good news from an engineer tomorrow.
No support ticket yet, as I don't have any logs to submit to them.
I don't want to hijack this thread with other issues, so let's see what Eric can come up with on the caller id issue.
Perhaps the next firmware can resolve both of my issues, or maybe I purchased a dud.
Alright, the locking up problem was caused by a faulty CallerID Superfecta module in my Elastix PBX passing an HTML doc as the Caller ID Name.
You can read about it here if you care: https://supportforums.cisco.com/thread/2123978
At any rate, the SPA112 shouldn't LOCK UP when receiving erroneous caller id info either!
Perhaps this is linked to the caller id issue we're having in this thread.
I don't think it is related to your HTML Caller ID name issue.
It appears that the SPA112 does receive the Caller ID correctly. Even after Caller ID fails to come through over the phone, it still shows up under the "Last Caller Number" in the web interface. I doubt that both VoIP providers mentioned here would have anymajor configuration issues with their Caller ID setup as both have been around for several years now and are known for reliable service. This kind of issue would have been caught by now, since so many of their customers run Asterisk and would have seen and reported this behavior from looking at their console or logs.
Also, I'm not getting the hangs and voice module not ready issues.
However, your issue should still be reported as it creates a condition where emergency calls might not go through... basically a DoS attack on the ATA. Like you said, it shouldn't hang due to getting bad Caller ID data.
I still think the issue is with the FSK signaling sent theough the FXS ports, based on the behavior. However, this is speculation and it could be something else.
I did get a call back from a support engineer at Cisco... the problem was acknowledged again, but at this time they haven't given me a bug ID or description of what is actually going on. I'm expecting this information soon, but have been told that it could take a few days before they get it back from engineering. In other words, no updates, but the case has been escalated and is going in the right direction.
The Caller ID issue has been reported to Engineering & Development teams. The Developer reports they have a handle on the root cause, so it is only a matter of time before a fix is found, and added to a forthcoming Maintenance Release firmware.
I just received the Cisco SPA112 yesterday and set it up successfully with my provider VoIP.ms. I noticed that my phones weren't receiving caller ID info and found this thread while searching for causes. Today, after testing it by calling myself from another phone over and over again, the caller ID info finally came through once. However, the caller ID info hasn't come through any time after that. I do know that the SPA112 is receiving the caller ID info because I can see it in the web interface. It's just not sending it to my phones. I don't know if that helps but I thought I'd mention it. I'm anxiously waiting for a fix.
Richard De Guzman wrote:
Today, after testing it by calling myself from another phone over and over again, the caller ID info finally came through once. However, the caller ID info hasn't come through any time after that.
Those are the results I have been getting all along. Sometimes it works, but usually it does not. The exact behaviror seems to depend on what equipment is attached to the SPA 112 because all Caller ID equipment handles errors differently. Some will display an error message, and some will display nothing at all.
This issue has also been reported with the SPA122 which uses the same firmware. The only difference with that devices is that it has a built in router.
I tried to get updates from Cisco several times this week and have not had a single call back or reply to any of the emails that I sent. If any of the Cisco employees that monitor this board could provide an update, it would be greatly appreciated.
I was trying to at least get a bug ID since I don't want to post the trouble ticket number in a public forum. So far I haven't even been able to get that information.
Any ETA on this fix? I'm getting tired of the wife nagging me about not having caller ID. She won't even answer the phone now.
I noticed that Call Waiting Caller ID does work with the unit I have. (Only tested it once). I can't belive this product was released without working caller id.
Yes, this is getting very frustrating & is ridiculous. It is very irresponsible for a company like Cisco to release a inferior and defective product like this.
Obviously Cisco released the product prematurely to the public without adequate field testing.
I noticed this thread/ticket is almost a month old now and we haven't heard anything back in weeks! Cisco is going to have to close this gap and prove themselves soon or it insinuates small business support is between low priority and non-existent.
I just bought this ATA and I'm shocked such a basic feature was not tested before release. I might have to add this example of terrible QA to the history books (Wikipedia) under SPA112/122.