01-17-2012 04:09 PM - edited 03-21-2019 05:12 AM
CallerId issues...
Reloaded firmware 2.1.2 -> Factory Defaulted system -> Still No CallerID
Loaded latest firmware same issue.
I can see the info in the logs... (logs included) any suggestions
I've included the 2 pics to show what is being displaying on the phone screen.
The other query is when the phone rings, I see the lamp flashing but no label on the screen stating which line is ringing
I expected the screen that overlays showing the CallerID would also state the ringing lines label. I've included to pics before and after shots.
Any help appreciated..
Regards.
---Log Output--
Jan 16 16:13:15 UC320W user.debug voice: fxo cnddwrap_feed parse ok 0447484699
Jan 16 16:13:15 UC320W user.debug voice: -- Caller ID:
-- Name = (null)
-- Remote Number = 0447484699
-- Dialable Number = (null)
-- No Number Reason = (null)
-- No Name Reason = (null)
-- Message Waiting = (null)
-- Date and Time = 01/16 16:13
Jan 16 16:13:15 UC320W user.debug voice: FXO:CNDD name=, number=0447484699
Jan 16 16:13:15 UC320W user.debug voice: FXO[1]:Stop CNDD
Jan 16 16:13:15 UC320W user.debug voice: FXO:CNDD Name= Phone=0447484699; rt=0
Jan 16 16:13:15 UC320W user.debug voice: FXO[1]:Report:sesssion=424c96b8;cst=3
Jan 16 16:13:15 UC320W user.debug voice: [1]->10.1.1.1:6060(449)
Jan 16 16:13:15 UC320W user.debug voice: NOTIFY sip:10.1.1.1:6060 SIP/2.0
Via: SIP/2.0/UDP 10.1.1.1:5081;branch=z9hG4bK-527d35c4
From: <sip:fxo1@10.1.1.1>;tag=8f7c9a9137d2728ao1
To: <sip:10.1.1.1>
Call-ID: 9bae4c4-a7cfde04@xxx.xxx.xxx.xxx
CSeq: 59769 NOTIFY
Max-Forwards: 70
Event: fxo-port-state;fxo1;0;2;fxo1;0447484699;0;;;1;2;96394b09-3134a470@xxx.xxx.xxx.xxx;10.1.1.1:6060;
User-Agent: Cisco/UC320W-2.1.4(3)
Allow-Events: talk, hold, conference, x-spa-cti
Content-Length: 0
01-17-2012 09:55 PM
Hello Vanessa,
Have you installed a caller id box in between your ISP's main analog line and the UC320 to see if caller id is coming from the ISP? How is the POTS lines being delivered to the premise? Via T-1 with an IAD or directly from the SP like ATT or Verizon?
We had the same issue with an Adtran IAD where the caller id box showed the caller id coming through, but never displayed on the SPA phones.
We needed to open a case with Cisco SB TAC to resolve the issue. I do not remember the version that solved it, but Cisco has is working.
Hope this helps.
Bert Wilhelm
01-17-2012 11:25 PM
There just standard POTS lines(PSTN), CallerID was working with this equipment...., The Voip CallerID's are perfect...
I orignally had a digum card and Cisco 942 phones all worked well, but not easy item to sell.
The UC320W simply sweet easy to program just a lot of limitations, compared to asterix/elastics.... but a sellable item...Looks good, performs well, I like to use what I promote...
Caller ID on all Lines..
01-18-2012 09:48 AM
Hi Vanessa,
I suggest (re-)running the impedance matching on each of your FXO ports. You can find this on the FXO ports page of the UC320W configuration utility.
If you are still having problems with caller ID after adjusting the impedance, then I suggest a call to the Cisco Small Business Support center where an engineer can perform some low level captures to look at the caller ID signal from the telco.
Thanks,
Chris
01-24-2012 12:44 AM
FYI.
Raised a case with Cisco...
There is a bug in the code they are trying to fix, they are aware of the problem.
Cisco attemnpting fixing the issue by.
Running the impedance matching....
and lowering to FXO Gain on Receive by 5db.
Hit and miss...
Didn't work for me....
Regards
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