Weird CallerID problem: phone shows it, logs don't
ipse:
Me neither, but thanks for looking into it!
I contacted support, but they got stuck the same way, thinking I'm complaining about missing PeerName.
Playing with RingDelay didn't make a difference - only made it worse as it takes longer to see CallerID for screening.
I remember reading in these forums that RingDelay > 4000ms does not result in longer display delay, but that's not what I'm seeing.
ipse:
Hate to bump this post, but I'm losing my mind...how can I get CallerID on the cordless phone attached to the Obi and NOT in the logs, therefore NOT blocked by my dump list?
In my particular case it looks like Obi does NOT log calls without Caller Name...so my attempts to set a block list fail, as all there is in the logs and passed to Obi is a date stamp.
Am I alone?
PS For all these I got a number recorded in the phone CallerID....yet Obi did nothing to block:
Call 10 05/25/2013 20:04:56
Terminal ID LINE1 PHONE1
Peer Name
Peer Number
Direction Inbound Inbound
20:04:56 Ringing
20:05:23 Call Connected
20:05:41 End Call
Call 11 05/25/2013 18:06:56
Terminal ID LINE1 PHONE1
Peer Name
Peer Number
Direction Inbound Inbound
18:06:56 Ringing
18:06:58 Call Connected
18:16:32 End Call
Call 12 05/25/2013 18:06:33
Terminal ID LINE1 PHONE1
Peer Name
Peer Number
Direction Inbound Inbound
18:06:33 Ringing
18:06:35 Call Connected
18:06:37 End Call
ianobi:
Do you get any Peer Numbers logged in Status > Call History for any incoming calls on the Line Port?
I'm assuming that you live in North America. As you know the CallerID is sent between the first and second ring. RingDelay is an issue, but you have tried that - I suggest leave around 4000 while changing other settings.
Perhaps the first ring is not being detected? You might try a lower setting for:
Physical Interfaces > LINE Port > Ring Detection > RingThreshold
Less likely, but just possible, you might try a lower setting for:
Physical Interfaces > LINE Port > Ring Detection > RingValidationTime
Another factor that might delay ring detection, so affecting CallerID detection, might be other devices connected in parallel with your OBi110.
ipse:
So the main thing is that the CallerID info DOES show on the Panasonic cordless attached to the Phone port. So settings are definitely OK.
The question is: how can I get calls that are logged on the phone (so CallerID info WAS passed on by Obi) but NOT on the Obi110?
Second very important observation is that ALL calls that carry Caller Name (Peer Name) show up in the logs correctly. If I was to guess, I would say this is a bug where the Caller Name missing causes the Caller Number (Peer Number) to get skipped in the logs.
Like I said, the main driver for this quest for paradise is to make use of my Telemarketer block list. No ID = no block.
PS Oh, and yes, the timers and all are set similar to what you indicated. Obi support was less than helpful, insisting that my problem is CallerID NOT being passed to the phone. On the contrary.
Call 5 05/28/2013 15:45:34
Terminal ID LINE1 PHONE1
Peer Name
Peer Number
Direction Inbound Inbound
15:45:34 Ringing
15:46:01 Call Connected
15:46:20 End Call
Call 10 05/27/2013 15:14:04
Terminal ID LINE1 PHONE1
Peer Name RYAN LAMONTAGNE
Peer Number xxx59xxx53
Direction Inbound Inbound
15:14:04 Ringing
15:14:31 Call Connected
15:15:07 End Call
ianobi:
"Weird" is the right word to describe this problem!
Quote
So the main thing is that the CallerID info DOES show on the Panasonic cordless attached to the Phone port. So settings are definitely OK.
The question is: how can I get calls that are logged on the phone (so CallerID info WAS passed on by Obi) but NOT on the Obi110?
This does not prove that the settings in the OBi are correct. The OBi has passed the call through to the Phone Port and your Panasonic is clever enough to extract the CallerID from the call. You will also probably find the CallerID of the last incoming call shown here:
Status > PHONE & LINE Status > LastCallerInfo for both the Phone Port and Line Port.
Again this does not mean that the OBi has processed the CallerID information.
Quote
Second very important observation is that ALL calls that carry Caller Name (Peer Name) show up in the logs correctly. If I was to guess, I would say this is a bug where the Caller Name missing causes the Caller Number (Peer Number) to get skipped in the logs.
This is very weird indeed. It's quite common for Caller Name to be missing. I have never heard of that preventing CallerID being recorded as Peer Number.
I have already suggested all of the settings that I know affect the receiving of CallerID, so now I'm out of ideas. ???
Navigation
[0] Message Index
[*] Previous page