UK PSTN caller-id not passed by Obi110
drgeoff:
My OBi110 is on a BT PSTN line and Caller ID work perfectly to my phone (Gigaset S445). Settings are as yours for FSK(V.23) but CallerIDTrigger is "Before first ring". RingDelay is set to 250 (milliseconds).
ianobi:
I don't think that you have any problem with your original UK default Line Port settings. Your OBi is correctly decoding the CallerID. This is what is being received on your Line Port:
' followed by another ' followed by a space, followed by CallerID.
Between the first ' and second ' is the place holder for CName. CName is often missing so the first and second ' appear together as there is nothing to put in between.
LastCallerInfo is reporting the whole string - CName space CallerID. In Call History Peer Number is accurately showing CallerID as decoded by the OBi110. If CName was present, then it would appear under Peer Name in Call History.
The question here is why your OBi110 is not forwarding CallerID to the Phone Port in the correct format for your phone. I suggest trying:
Physical Interfaces > PHONE Port > Port Settings > CallerIDMethod = FSK(V.23)
Physical Interfaces > PHONE Port > Port Settings > CallerIDTrigger = Before First Ring
I hope that helps narrow the problem down somewhat.
(Posted before I saw drgeoff's post!)
DeanUK:
Drgeoff and Ianobi, I have now tested your suggested settings:
Physical Interfaces > PHONE Port > Port Settings > CallerIDMethod = FSK(V.23)
Physical Interfaces > PHONE Port > Port Settings > CallerIDTrigger = Before First Ring
With ring delay set to 250 ms but unfortunately still no caller-id appearing on the phone. I’ve now tested using:
CallerIDTrigger = Before First Ring
CallerIDTrigger = After First Ring (which is the setting used in the UK XML file v2.4)
CallerIDTrigger = After Polarity Reversal (which is a frequently mentioned setting for UK caller-id).
With each of these settings the phone always rings out, but no caller-id shown. I’ve also found an old BT Caller Display 50 device that I’ve inserted in series with the phone, and repeated the three trigger types above, but same result – no caller-id on either BT unit or phone. Perhaps I have a fault on the Obi?
Ianobi – thanks for the explanation about cname, makes sense.
azrobert:
This is the suggestion I gave you:
LINE port->InboundCallRoute-> {(<" :>xx.):ph}
The quote in the rule is a single double quote. ianobi's explanation indicates this should be 2 single quotes, so I don't understand how the phone would ring using the above rule.
Do you configure the OBi110 locally or thru OBiTalk?
drgeoff:
Quote from: DeanUK on November 07, 2014, 10:13:53 am
One thing i've noticed is that in the Call History log, when I make an outbound call the dialled number appears under both the LINE1 and PHONE1 columns. When I make an inbound call the Peer Number only is shown under LINE1, and the PHONE1 column is blank.
Those observations are normal. Nothing amiss.
Navigation
[0] Message Index
[#] Next page
[*] Previous page