Outgoing calls through LINE port are dropping
ChrisThompson:
Quote from: RonR on August 18, 2011, 10:42:25 am
Try a different telephone (as well as its connecting cable) on the OBi's PHONE Port. It appears the OBi is detecting a Hook Flash and OnHook condition from your telephone.
When you press # to get a direct connection to the LINE Port, the OBi isn't using your Internet connection.
Sorry, I meant the calls were dropping when using the LINE port; I mixed up PHONE and LINE. The call dropping sounds like a dead silence for about two-three seconds, then a low frequency "CLICK" or "CLUNK" then a dial-tone.
I understand it's not using the internet, so that leads me to believe it's something weird going on in the OBI. When I connect my cordless phone directly to the LINE, I never have a problem.
I noticed the FLASH thing there to, and I have no clue why that would show up. My phone is a DECT 6.0. I have a wireless router running at 2.4ghz and 5ghz (dual band). My OBI is in the basement, two floors away from my phone, and one floor away from the base station. Again, I've never had any issues with calls in the same setup but with the phone base plugged directly in to the LINE without the OBI.
ChrisThompson:
Quote from: infin8loop on August 18, 2011, 05:02:02 pm
If the other suggestions don't work out for you then you might try increasing the Physical interface -> LINE port -> DetectFarEndLongSilence / SilenceTimeThreshold value from the default 60 seconds.
See thread http://www.obitalk.com/forum/index.php?topic=1164.msg7364#msg7364 where it was suggested to me.
I'll give that a shot. The dropped calls do happen most of the time during conference calls. Is the silence detection just for the MIC (i.e., my voice) or does it also listen to the incoming audio, because I get drops when other people are talking but I may not be talking. I'm often on MUTE during conference calls for long periods of time, certainly more than a minute.
RonR:
Quote from: ChrisThompson on August 18, 2011, 11:28:31 pm
Quote from: RonR on August 18, 2011, 10:42:25 am
Try a different telephone (as well as its connecting cable) on the OBi's PHONE Port. It appears the OBi is detecting a Hook Flash and OnHook condition from your telephone.
Sorry, I meant the calls were dropping when using the LINE port; I mixed up PHONE and LINE. The call dropping sounds like a dead silence for about two-three seconds, then a low frequency "CLICK" or "CLUNK" then a dial-tone.
I understood how you're calling and I still think you should plug in a simple corded telephone and disconnect and remove power from the cordless phone to see if the problem goes away.
infin8loop:
Quote from: ChrisThompson on August 18, 2011, 11:31:54 pm
The dropped calls do happen most of the time during conference calls. Is the silence detection just for the MIC (i.e., my voice) or does it also listen to the incoming audio, because I get drops when other people are talking but I may not be talking. I'm often on MUTE during conference calls for long periods of time, certainly more than a minute.
My understanding is the silence detection is for the other side of the conversation (what you are hearing), not your voice.
I wonder if maybe the volume coming in from the other side of your conference calls is too low to consistently exceed the threshold that is considered "not silence". If that doesn't make your head hurt, as it does mine, then maybe it's just me.
To adjust the silence detection:
Physical interface -> LINE port -> PSTN Disconnect Detection ->
1. DetectFarEndLongSilence (checked = on, unchecked = off, default = on)
if the above is "on" then:
1.a SilenceDetectSensitivity (low, medium or high, default = medium)
1.b SilenceTimeThreshold (a value in seconds, default = 60)
So, what does all this mean? Here's my guess. Either turn DetectFarEndLongSilence off, or leave it on and adjust one or both of the other two. The manual indicates SilenceDetectSensitivity "Low" means harder to detect silence and "High" means easier to detect silence. I'm not positive if you'd want "High" or "Low" because the voices in my head are arguing with each other as to what this really means. I've fall'in into an infiniteloop and can't get up (notice I did not include the word it). It's like chosing between the blue pill and the red pill (the obvious blue pill jokes aside). I'd pick blue, er, I mean I'd pick SilenceDetectSensitivity "Low" harder to detect silence (chuckle, "harder"). Geez, it's after 11 am and I've not had any coffee. So your actual mileage may vary. I love when people say that (YAMMV) when they aren't really sure what they're talking about. It's like "Well, it worked for me. I don't know what your problem is."
Navigation
[0] Message Index
[*] Previous page