Weird CallerID problem: phone shows it, logs don't
ipse:
Quote from: ianobi on February 10, 2013, 02:15:23 am
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.
Thanks ianobi...here's the mistery: it seems the numbers that don't get logged (and BTW, call logs are only available if logging into the device, not through the Obitalk page...) are showing a quotation mark and a space before the number.
As I said, the info DOES get passed to my cordless set which is smart enough to parse them out! I DO see tha info on the phone, but NOT in the Obi logs and also Obi cannot process them (I have a blacklist).
Snapshot from the LINE and PHONE status.
PHONE and LINE Port Status
Port Statushelp
Parameter Name Phone Port Status
State On Hook
LoopCurrent 0 mA
VBAT 57 V (12.1 V)
TipRingVoltage 45 V
LastCallerInfo '' 1732784xxxx
Line Port Status
On Hook
0 mA
48 V
'' 1732784xxxx
Call log:
Call 1 02/10/2013 11:38:45
Terminal ID LINE1 PHONE1
Peer Name
Peer Number
Direction Inbound Inbound
11:38:45 Ringing
11:39:02 End Call
ianobi:
That's interesting. I tried simulating the same situation coming in from an sp and the " xxxx shows up correctly. However, I'm having trouble working out how to simulate this on an incoming call to the Line Port.
Are "normal" calls to the Line Port showing the correct Peer Number?
This may take a day or two!
ipse:
I think I jumped the gun: the double-quotation marks are actually 2 single quotation marks and the space...well, just a delimiter.
Which basically means: "there is no peer name available" (blank). Damn! I thought I was onto something.
@ianobi, yes, other calls show up ALWAYS (but they might be POTS-POTS not VoIP-POTS...).
I went back and forth betwen 2765 and 2774 and it's the same.
I plan to set the RingDelay to some 5-6sec value and see if that changes anything in terms of Obi recording the number - passing it on is not the issue. But that would suck, as I have Talking CallerID which helps me screen the calls :)
Oh technology...where are the days of the rotary phones :0)
ianobi:
I'm sure that you are thinking on the right lines. I would have thought that the first ' ' should have resulted in a blank Peer Name, but the Peer Number should have been recorded in Call History.
A few questions to be answered yet!
Oh for the days of rotary phones, loop/disconnect dialling and strowger telephone exchanges - then you could really see what was happening :D
ianobi:
Further testing on incoming calls to the Line Port of OBi110 seems to show:
1. CallerID present, no CName present - Peer Number and Peer Name both show CallerID.
2. CallerID present, CName '' (two single quotation marks followed by space) - Peer Number shows CallerID, Peer Name shows '' (two single quotation marks followed by space).
3. CallerID present, CName " " (a space contained by two double quotation marks) - Peer Number shows CallerID, Peer Name is blank.
The only difference between calls arriving at the Line Port and calls arriving via voip on an sp seems to be number 1. calls via voip on an sp with no CName show Peer Name blank as you would expect.
I have no idea what this proves :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page