Weird CallerID problem: phone shows it, logs don't

(1/3) > >>

ipse:
I discovered a weird issue today with my Obi110: I got an unwanted call from 1-647-258-3214 (telemarketer) and the cordless phone is displaying the number.
When I went into the Obi to update my Telemarketer list, there is NO record of the call in the logs.
This has happened twice today already.
No, it's not the RingDelay value, as the CallerID was passed just fine to the phone.

Any ideas? I'm on the latest 2774 load.

CoalMinerRetired:
Does your Google Voice (Or CallCentric or VoIP.MS or Anveo or whatever) call history show the call?

If no to the above, then possibly it's a SIP scanner. Search for that term on here, some current posts and explaination.

ipse:
The call comes in on the landline...it's an Obi110 which still has the POTS connected.
But the weird part is that *69 dials it just fine...so it's Obi the does not log it or act upon it.

Did telemarketers just got smarter :) just kidding, as I said the info is passed on by the line.

giqcass:
I don't have the 110 so I don't know a lot about it but are you looking at call logs through the web portal or connected to the OBi directly?  I had thought it might be having trouble connecting to the portal which may account for the CID not showing up there.

ianobi:
The OBi110 will route the call from the Line Port to the Phone Port whether or not it sees CallerID. In this case it looks like the phone is recording the CallerID allowing call back etc.

If the CallerID does not show up in the Status > Call History > Peer Number, then the OBi110 has not processed the CallerID information. I would have another look at RingDelay, CallerIDDetectMethod etc.

Navigation

[0] Message Index

[#] Next page