OBI110, UK PSTN Call Barring
ianobi:
One more thing to eliminate is that the Phone Port may be giving a false answer and then dropping out. The four seconds before "End Call" is the same as your RingDelay, if still at default. Therefore, it is four seconds before the OBi tries to ring the Phone Port.
You could try this:
Physical Interfaces->Line Port->InboundCallRoute: aa
This should divert all incoming calls to the auto attendant after the RingDelay. This would eliminate any Phone Port problems if calls still fail.
ukuser:
Physical Interfaces->Line Port->InboundCallRoute: aa
That works a treat! Absolutely reliable. Call history shows AA transferring to PHONE1 (which keeps ringing until I answer it as you'd expect) and then "Call Connected".
(Note: I terminated the call from the test mobile. The Obi phone did not revert to dial tone however, just silence until I hung up. Call History shows the call terminating when I hung up the Obi phone. Line disconnect (ie. LINE "End Call") was not registered when I hung up the mobile.)
So I'm now thinking that a Line Disconnection is probably NOT happening?!
It seems there is a very short period of time to answer the call which the AA achieves easily but not the Obi Phone. Ring delay is currently set at 0. (CallerId seems to work OK at this setting.)
Obviously, with (ph rather than aa) I want the Obi phone to keep ringing for ages (not just once or twice if I'm lucky) until the BT/TalkTalk exchange answering machine kicks in (if it ever does, I've no idea when the exchange would consider the call "answered" now).
Where to look next? All Phone settings are at default currently.
We're making progress Ian! Many thanks.
ianobi:
I wonder if there is something odd about your DECT base station. Is it possible to swap it for a corded phone for testing?
If there is a small "glitch" as the ringing is sent to the phone then it might be seen as a "HookFlash" - a way of putting calls on hold etc. Try increasing:
Physical Interfaces > PHONE Port > Timers > HookFlashTimeMin to say 150.
I don't think it will make much difference, but the following would be more standard for UK phones:
Physical Interfaces > PHONE Port > Port Settings > Impedance: 320+(1050||230nF)
Physical Interfaces > PHONE Port > Port Settings > CallerIDMethod: FSK(V.23)
Using:
Physical Interfaces->Line Port->InboundCallRoute: aa
does CallerID work reliably?
Hope we solve this soon - there's not much more left to try ???
ukuser:
I wonder if there is something odd about your DECT base station. Is it possible to swap it for a corded phone for testing?
You read my mind! It's a newish Panasonic DECT which I get the feeling that people have fewest problems with. First thing this a.m. I got an old corded phone out but I have yet to find its power brick (big shock!). Will look again if necessary.
Try increasing:
Physical Interfaces > PHONE Port > Timers > HookFlashTimeMin to say 150.
Will give it a go, but see later.
Physical Interfaces > PHONE Port > Port Settings > Impedance: 320+(1050||230nF)
Physical Interfaces > PHONE Port > Port Settings > CallerIDMethod: FSK(V.23)
That's what they're set to currently, along with:
Physical Interfaces > PHONE Port > Port Settings > CallerIDTrigger After Polarity Reversal
* With these PHONE settings (and LINE InboundCallRoute ph) I now get:
Perfect operation but only if I answer the Obi phone absolutely immediately it rings (same thing as having AA do the answering I guess). If I leave it a second longer then call history shows LINE1 End Call about 7 or 8 secs after "Ringing". This at least is repeatable! That 7 or 8 secs is a mystery as RingDelay is set to 0! It is about right as the Phone LED starts flashing about 7 secs after the Line LED. (Where does the delay come from? It eats into the (unconfigurable) 21 secs that TalkTalk give you before their voicemail cuts in).
Physical Interfaces->Line Port->InboundCallRoute: aa
does CallerID work reliably?
Yes. CallerID seems very reliable.
Note: Physical Interfaces >PHONE Port > Port Settings are important it seems. With them set as above, when the mobile hangs up the Obi phone returns to a dial tone. Nice!
Now trying Physical Interfaces > PHONE Port > Timers > HookFlashTimeMin to say 150
ukuser:
Well, no luck with Physical Interfaces > PHONE Port > Timers > HookFlashTimeMin 150
Where I am now:
When I call in to the OBI:
LINE LED flashes.
There is then a 5 or 6 second (guess)delay before the PHONE LED starts flashing. (Don't know where this delay comes from)
There is then a small (1s) delay before the Obi phone starts ringing (normal DECT delay).
If I answer immediately, the call is connected perfectly.
If I delay answering, the phone might ring again but can only hear dial tone. Call history then shows LINE "End Call" approx 7 to 9s after "Ringing"
Physical Interfaces >LINE Port > RingDelay is 0
Physical Interfaces >LINE Port > InboundCallRoute is ph
Physical Interfaces >LINE Port > DigitMap is default (xxxxxxxS4|1xxxxxxxxxx|xx.)
Physical Interfaces > PHONE Port > Port Settings > Impedance: 320+(1050||230nF)
Physical Interfaces > PHONE Port > Port Settings > CallerIDMethod: FSK(V.23)
Physical Interfaces > PHONE Port > Port Settings > CallerIDTrigger After Polarity Reversal
Physical Interfaces > PHONE Port > Timers > HookFlashTimeMin 150
So the questions are:
1. What is delaying the routing of Line port to the Phone port for so long? Maybe it's just a bit slow and this is the normal operation - unlikely as it manages to route to the AA instantly. (Thinks: Digitmaps involved somewhere? They're all at default US settings now.)
2. What is timing out such that I must answer the Obi Phone so quickly? Is there a state where, if the phone is not answered quickly something on the exchange line (eg: Polarity Reversal or some such) makes the Obi think the caller has hung up.
Time before TalkTalk voicemail cuts in = 21s approx.
Time for Obi to start ringing DECT about (9 + 1) =10 secs (max)
So should get at least 10 secs of dect ringing worst case.
Mustn't forget: When call fails, Call History does log the call "Inbound" to the phone and logs correct CallerId. It has tried to route Line to Phone but it just doesn't give a long enough time for DECT phone to pick up.
Time for a cup of tea and a think!
Many thanks Ian.
Navigation
[0] Message Index
[#] Next page
[*] Previous page