UK PSTN caller-id not passed by Obi110
ianobi:
@ azrobert
Quote
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.
I wondered the same thing, so I did a couple of tests. My landline does not have CallerID enabled, so I modified your rule to:
LINE port->InboundCallRoute-> {(<" :>):ph}
I tried a double inverted comma followed by space and two single inverted commas followed by space. In both cases my phone rang with no problem. I'm guessing that the OBi simply does not recognise or decode the " in a digitmap and ignores the space, so it sees both as nothing on the left of the colon and replaces it with nothing on the right side of the colon.
Further testing shows that this rule:
LINE port->InboundCallRoute-> {<" :>:ph}
Does indeed stop the phone ringing. Now the " is not in a digitmap and the OBi does seem to try to match it as a "literal". I'm guessing the rule for the OP to try would be:
LINE port->InboundCallRoute-> {<" :>(xx.):ph}
Using both a double inverted comma followed by space and then trying two single inverted commas followed by space.
Having said all that, I can't be sure if the " is coming in via the PSTN line or is being added by the OBi to try to clarify what it shows as LastCallerInfo.
It's beer o'clock here, so too late for further research, but looking forward to comments from anyone who has stayed awake this far :)
drgeoff:
Quote from: DeanUK on November 08, 2014, 06:16:46 am
CallerIDTrigger = After First Ring (which is the setting used in the UK XML file v2.4)
That is incorrect. The UK XML file should be updated to properly reflect SIN227. (http://www.sinet.bt.com/sinet/SINs/pdf/227v3p6.pdf)
The UK 'full' setting should be 'after polarity reversal and before first ring' but the Obi does not offer that.
drgeoff:
@DeanUK
Try rebooting the phone. And if DECT, the base-station too. Ie mains plug out and batteries out.
DeanUK:
I’ve done all config up to this point using the Obi110 locally (192.168.1.3), with the settings on Auto Provisioning set to “Disable”, even though the device had previously been registed to the ObiTalk portal, though reset to factory defaults many times since then. I have always rebooted the Obi110 after making any changes to parameters. The phone is a very basic POTs/PSTN phone (not DECT) with no power supply, just one lead to the Obi110. The BT Caller display unit which has one lead to the phone and one lead to the Ob110 – no power except batteries.
After my last post I rebooted the Obi110, loaded the UK V2.4 XML file, and then decided to use the ObiTalk portal to configure service for Localphone and for Google Voice, which prompted a firmware upgrade to build 2872. I hoped this 2872 might resolve the issue but still no caller-id.
Now looking at the ObiTalk Obi Expert Config pages, it says Phone port -> CallerIDMethod FSK(Bell 202), but when I look at settings locally on webpage at 192.168.1.3 it says Phone port -> CallerIDMethod FSK (V.23). Highly confusing – I thought they would at least be in sync. Assuming the local settings are correct, I then tried incoming calls using:
a) double apostrophe followed by space char
LINE port -> InboundCallRoute-> {<" :>(xx.):ph} result - no ringing of phone
b) two single apostrophes followed by space char
LINE port -> InboundCallRoute-> {<’’ :>(xx.):ph} result - no ringing of phone
azrobert:
This is the way I got it to work:
{(<[^0-9][^0-9]@:>xx.):ph}
I couldn't get it to match a single quote or a space.
[^0-9] will match anything except a digit.
@ will match anything.
You should use:
{(<[^0-9][^0-9]@:>xx.):ph},{ph}
Navigation
[0] Message Index
[#] Next page
[*] Previous page