OBI110, UK PSTN Call Barring
ukuser:
Wow, thanks for the clarification Ian and on a Bank Holiday too!
Factory reset - Done. Call history etc. cleared.
Set auto provisioning to disabled for ObiTALK and ITSP
Set Physical Interfaces->Line Port->CallerIDDetectMethod = FSK(V.23)
Nothing else changed at all. All routing and DigitMaps left at default everywhere.
Rebooted.
Physical Interfaces->Line Port->InboundCallRoute: ph Tick :)
Ring in:
Shows in Call History > Peer Number? Yes. Tick
Shows in Line Port > LastCallerInfo? Yes Tick
Caller gets? Ringing tone. :( Only once then cuts off. (Just as if call was blocked!)
OBi phone rings? Yes. :( but only once then cuts off.
Ring in again to check repeatability:
Shows in Call History > Peer Number? Yes. Tick
Shows in Line Port > LastCallerInfo? Yes Tick
Caller gets? Ringing tone. :( Only once then cuts off.
OBi phone rings? Yes. :( Once then cuts off.
Noticed: Telephone line LED on Obi extinguished for a few minutes after this test.
Ring in again to check LED.
Same results again. LED extinguishes for 2mins approx. (but I can dial out from DECT nonetheless - LED flashes as soon as I take the DECT off hook).
This is no good as I'm using my mobile to ring in and it is effectively blocked when it shouldn't be!
Will now try from partner's mobile:
Same result: All calls are now terminating from any number it seems. This did not happen before!
Clutch at straws.
Set Physical Interfaces->Line Port->ACImpedance 370+620//310nF
No effect
Change RingDelay from 4000 to 2500
No effect.
Stumped! but press on rewardless.
Set:
Physical Interfaces->Line Port->InboundCallRoute: {01234567890:},{ph}
Ring in on either blocked or unblocked phone:
No difference in behaviour. Caller is cut off after one ring; DECT phone rings once then stops.
This is crazy! I can't cope with inconsistent behaviour like this. I'm going to take a break and try and get back to where I was yesterday when I could at least receive calls correctly.
Will post again later! Meantime, thanks again Ian.
ianobi:
FYI - the ultimate hardware reset is the paper clip method:
1. With a paper clip (or similar) depress the reset pin located on the back of the OBi.
2. While keeping the reset pin depressed, plug-in the power cord.
First, the Power LED will turn red, then become solid green.
Keep depressing the reset pin while this is occurring.
3. After 10 seconds, the Power LED will start to flash green (slowly).
You may now release the reset pin.
4. Within 5 seconds, the Power led will start to flash green rapidly for about 3 seconds.
5. Next the Power LED will change to red briefly indicating the OBi is now rebooting.
The factory reset is now complete.
ukuser:
Day 3!
FYI - the ultimate hardware reset is the paper clip method:
Thanks Ian, that's just what I tried. I even tried setting things up through the website rather than locally. (Now that IS clutching at straws!)
Sadly, nothing made any difference.
With a default setup (no blocking at all but FSK V.23 line protocol selected), incoming calls are cut off immediately, the Obi phone rings once and the Phone LED goes out for a minute or two.
I've sent an email to support & am getting ready to hunker down for the long haul!
Keep those tips/suggestions coming Ian, they're very welcome.
En passant:
1) Page 38 of the admin guide (LINE (FXO) Port Configuration Options): Codes ***090 and ***092 work as advertised.
Codes ***091 (FXO State) says Invalid option - mighty strange?!
2) I noticed that there are no default AA messages set up and page 38 of the admin guide (Customized AA Prompt Recording Options) isn't helpful as there is a code missing which you think should be 1000 but isn't.
Bob
ianobi:
Quote
With a default setup (no blocking at all but FSK V.23 line protocol selected), incoming calls are cut off immediately, the Obi phone rings once and the Phone LED goes out for a minute or two.
I wonder if your OBi is wrongly seeing some sort of "disconnect signal". Try unchecking both of these in your Line Port settings:
DetectPolarityReversal
DetectDisconnectTone
Quote
1) Page 38 of the admin guide (LINE (FXO) Port Configuration Options): Codes ***090 and ***092 work as advertised.
Codes ***091 (FXO State) says Invalid option - mighty strange?!
I have never tried that before! I get exactly the same as you, so it's weird but maybe not significant.
Quote
2) I noticed that there are no default AA messages set up and page 38 of the admin guide (Customized AA Prompt Recording Options) isn't helpful as there is a code missing which you think should be 1000 but isn't.
The default messages do not show in the section Voice Services > Auto Attendant > Auto Attendant 1 Prompts. I think they only show if you set up non-default messages. What happens when you dial "**0" ? You should get "Welcome to OBi Attendant" followed by options 1, 2 and 3.
ukuser:
Try unchecking both of these in your Line Port settings:
DetectPolarityReversal
DetectDisconnectTone
1st try: Success! Obi phone range twice, I answered it and got connected to my mobile.
Call History shows PHONE1 "Call Connected" then "End Call"
2nd try: Failure. Caller hears line disconnecting immediately. Obi Phone rang once.
Call History shows LINE1 "End Call" occurring 4 secs after "Ringing".
So you're right; unless I answer very quickly a line disconnect is being erroneously detected.
Maybe I need to meddle with the other PSTN Disconnect Detection parameters.
***091 - I get exactly the same as you,
Good to know, thanks.
Auto Attendant 1 Prompts. I think they only show if you set up non-default messages.
OK, thanks.
What happens when you dial "**0" ? You should get "Welcome to OBi Attendant" followed by options 1, 2 and 3.
OH Right, I see now. Yes, that happens. Forgive my lack of cognitive functioning!
Well, many thanks again Ian. I'm going to revisit the BT SINs to try and figure out where that line disconnect is coming from (as I write my oscilloscopes are begging to be used but I'm ignoring them for the moment).
Bob
Navigation
[0] Message Index
[#] Next page
[*] Previous page