08-25-2011 10:52 AM - edited 03-21-2019 04:34 AM
Hi there,
I heard a rumor that the UC320 does not support caller id on Analog DID trunks. Can someone confirm? I cannot seem to find this in supporting documents.
I am a sales engineer and do not have a specific scenario, just curious. Thanks!
08-25-2011 12:02 PM
Hi Daniel,
Yes, the UC320W supports caller ID on inbound FXO trunks. There was a bug not too long ago where in certain environments Caller ID wasn't working. It has been addressed in the latest release.
Cheers,
Chris
11-28-2011 06:38 PM
Hi Christopher,
Unfortunately caller ID is not working on many telephone service providers, not sure if the bug was fixed as I am having issues with my UC320W and caller ID on FXO line is not working, just showing "fxo1"
I am located in Montreal/Canada and my TSP is Videotron.
11-29-2011 10:10 AM
The caller ID does NOT work and there is currently no solution. I opened a case with Cisco yesterday and this was the response I got after 3 hours. Extremely frustrating to have to tell my customers that they cannot have caller ID.
11-29-2011 01:21 PM
Hi Brenden,
I saw your case was erroneously closed, SBSC management has been notified, and your case has been reopened & escalated. A support engineer should be in contact soon. I want to apologize for your experience.
We will continue to collect data, analyze the data, and optimize the software and hardware. Often times there are a number of environmental factors that impact the detection of Caller ID signaling. There is an active ongoing effort to drive out caller ID issues.
Chris
11-30-2011 09:22 AM
Is working for me now,
Good news, I did another downgrade to 2.1.2, did a reset to factory defaults, updated to 2.1.3 and now is working. I also called my TSP (in the same time I was reseting the unit) and complained about caller ID issues, it started to work right after that, in other words not sure where the problem was, uc320? or TSP? or maybe both.
Many thanks to Christopher and BMany for the help and follow up.
11-30-2011 09:49 AM
Interesting that you had to downgrade to upgrade. I have a sneaky suspicion that your CID was not enabled in your TSP's switch. We were able to get my lab UC320 (where we are the service provider) to recognize on-net and off net CID by running the impedence test.
As of now, my case is still open until I can confirm that this solution works for our customers.
Thank you to everyone who has contributed so far!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide