OBI110, UK PSTN Call Barring
ianobi:
Quote
2. Status > PHONE & LINE Status > Line Port Status > LastCallerInfo
Shows:
'' 12345678901
(Phone Port Status shows the same).
I can save you some time here! The format for LastCallerInfo is:
'CallerName' CallerID
'' (that is two ') simply indicates that no CallerName was received. The space between '' and CallerID is just a separator. So that looks normal - I don't think it's even possible to get CallerName from British Telecom.
Often if a CallerID is received via voip with no CallerName, OBi will use CallerID as CallerName for the Phone Port LastCallerInfo and will show as:
'012345678912' 012345678912
For some reason it shows '' 012345678912 when received via PSTN.
Just a shot in the dark, but it might be worth trying a RingDelay of around 2500. I know CallerID is delivered much faster than that, but it may take the OBi a finite time to process it. After that it's time to start poking around with all them other pesky settings!
Edit - I see you have already worked most of this out!
ukuser:
Thanks for that LastCallerInfo info. Ian, I was so disappointed that it wan't a bug!
This is getting frustrating! The worst thing is the results of my meddling are not consistent.
I have set the following:
Physical Interfaces->Line Port->InboundCallRoute {(01234567890):},{ph}
Physical Interfaces->Line Port->RingDelay 2500
Physical Interfaces->Line Port->CallForwardOnNoAnswerRingCount 5
Physical Interfaces->Line Port->AnonymousCallBlockEnable Yes
Physical Interfaces->Line Port->DetectPolarityReversal No (makes no difference if set to Yes)
Physical Interfaces->Line Port->ACImpedance 370+620//310nF (was something else, makes no difference anyway!)
Physical Interfaces->Line Port->FSK(V.23) was Bell 202
Everything else is set to default.
(1) When I ring in from my mobile the very first time after making changes and rebooting the OBI, the call is handled correctly. The line appears to go dead as far as the mobile is concerned, the DECT attached to the OBI never rings and I can see from the OBI leds that it hasn't routed the Line to the Phone. The call is logged correctly (Peer Number correct). LastCallerInfo correct for both Phone and Line ports. Lovely!
(2) Then I ring in again. This time the OBI routes the call to the DECT. There is no number in the Call history. LastCallerInfo is correct for the Line Port but not the Phone port. Horrible!
(3) I try again with the same result (but this time LastCallerInfo is correct for both ports and is logged in Call History).
(4) Reboot the OBI. Having made no changes to above configuration.
Ring in again. Result is as (3) above; ie. no good.
I have had this behaviour many times now; that is, if I set parameters, reboot and ring in it seems to work the first time but never subsequently. If I just reboot without having updated any parameters first it doesn't work.
At any rate it seems the CallerId is getting recognised all the time (so the h/w Line parameters must be pretty close) but it's just not being handled correctly under certain conditions.
Confused and tired! All suggestions and moral support appreciated!
PS: I cannot find anyone in the UK who has successfully managed PSTN call barring which I find strange as the OBI has been out for a couple of years now.
ianobi:
Are you sure that provisioning has been disabled? Are the changes you are making to settings "sticking"?
Quote
(3) I try again with the same result (but this time LastCallerInfo is correct for both ports and is logged in Call History).
I have never seen this before. If the number is in Call History, then any rules pertaining to that number have always worked.
Quote
I cannot find anyone in the UK who has successfully managed PSTN call barring which I find strange as the OBI has been out for a couple of years now.
I have used many devices to connect to the Line Port and CallerID and associated rules have always worked. I admit I have never connected to British Telecom, but they do nothing unusual as far as I know. I'm sure we have used call barring for someone in the UK.
This really has worked for some people:
Quote
Clutching at straws here, but other users have reported that any of the settings under Line Port > Ring Detection may have some effect on CallerID.
Two last resorts are put in a support ticket to Obihai or see if Amazon will swap it. Although I'm not convinced it's faulty.
It's Friday evening, so I'm heading towards the pub soon. This voip stuff can drive you to drink! Hoping to hear better news from you soon :)
ukuser:
Are you sure that provisioning has been disabled? Are the changes you are making to settings "sticking"?
Yes, ITSP and OBITalk provisioning are both disabled. After I reboot I always refresh and check my settings are as expected.
I'm sure we have used call barring for someone in the UK.
Well, that's encouraging!
Although I'm not convinced it's faulty.
Neither am I, strangely! Most other things I've played with work fine!
Just for fun I set:
Physical Interfaces->Line Port->InboundCallRoute to nothing, blank, not a sausage. No routing from Line to Phone at all.
Guess what? Yes, the OBI still routes the Line port to the Phone!
There's something going on there I just don't understand as I thought the only way for the Line to route to the Phone port was if "ph" appeared as a target somewhere in the InboundCallRoute string. (I cannot see any other default Line routing settings.)
so I'm heading towards the pub soon
Enjoy!
Thanks for all your help. Am going to play with setting AA as the target rather than ph now.
ianobi:
I think I may have added to the confusion in this thread. If call barring is working correctly, then CallerID will not show in Call History. This is because the call has not been allowed into the OBi so cannot be recorded.
I have now done a factory reset on my brain, so let’s look at some cases with incoming calls from 01234567890. This is how it should work:
Physical Interfaces->Line Port->InboundCallRoute: ph
Shows in Call History > Peer Number? Yes.
Shows in Line Port > LastCallerInfo? Yes
Caller gets? Ringing tone.
OBi phone rings? Yes.
Physical Interfaces->Line Port->InboundCallRoute: {01234567890:},{ph}
Shows in Call History > Peer Number? No.
Shows in Line Port > LastCallerInfo? Yes
Caller gets? Ringing tone.
OBi phone rings? No.
Physical Interfaces->Line Port->InboundCallRoute: {01234567890:aa},{ph}
Shows in Call History > Peer Number? Yes.
Shows in Line Port > LastCallerInfo? Yes
Caller gets? Ringing tone followed by auto attendant.
OBi phone rings? Only if caller chooses Option 1 from auto attendant menu.
Notes:
The third case above may be the most useful for testing CallerID and showing that it is being used correctly.
In this case, {01234567890:},{ph}, you cannot stop the British Telecom exchange from sending ringing to your OBi110. The rule merely tells the OBi to direct the call to nowhere, so the OBi phone does not ring.
Be careful of LastCallerInfo. The last number it has recorded stays there until it records another number or the OBi is rebooted, in which case it goes back to blank.
{01234567890:} is ok for one number, extra parenthesis only needed if you want more than one number in the list – they do no harm if only one number.
If you delete ph and leave the Line Port InboundCallRoute blank your OBi110 has no instruction so it rings the phone as a default strategy. To prevent all calls received from ringing the phone this rule is needed:
Physical Interfaces->Line Port->InboundCallRoute: {}
I suggest the way forward may be to do a factory reset on your OBi. Then only change:
Physical Interfaces->Line Port->CallerIDDetectMethod = FSK(V.23)
Then start testing again.
Apologies if I was not clear before. Human Brains and OBi110s both need rebooting from time to time :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page