Is anyone else experiencing intermittent issues with caller id via the fxo port? I'm running firmware version 2.3.1(14).
After rebooting the UC320 the first call received will display the correct caller id but any call received thereafter will only display as being from "fxo1". Reboot the 320 and again, the first call received will again display the correct caller id but thereafter back to fxo1.
I've run the FXO impedance matching tool and inserted the correct values from the test but this is still occuring. As far as I recall it was fine before I installed the release candidate. Caller ID from the SIP trunks is fine. Anyone else having similar problems or any suggestions to fix this?
Paul (and/or Jack),
Thanks for you question on the support community on this issue.
Couple questions if I may...
1) Was the fxo caller id working before upgrading to 2.3.1(14) and after upgrade it stopped presenting the caller id after the first call?
2) If a previous version did present the caller id correctly can you confirm what version?
3) Please open a support case with Cisco Small Business Support Center:
There are additional fxo debug tools in firmware version 2.3.1(14). The support team can request the correct syslog settings to help identify the caller-id issue.
Just to update - Fabulous service from Cisco with this problem - I received a pmf file today from them which has fixed this problem.
Thank you very much guys - I know in other messages I've complained about the length of time it takes for things to get done, specifically, new features at Cisco but absolutely no such complaint when it comes to fixing an issue with a supported feature.
Wonderful service guys.
Hmm... Good question, if you let me have your email address I could email it to you or maybe someone from Cisco could pick this up and help Clive and anyone else with this problem by giving them access to the file? Tobi Asonibare at Cisco emailed me the pmf file.
Extract from Tobi's email:
"The PMF changes the call id method from ETSI FSK with PR (UK) to "ETSI DTMF with PR" and we've had a TME test it to be working in the UK."
So I'm assuming this may be of help to people only in the UK.
Let me know if I can help.