Other person can't hear me.
Stewart:
Quote from: bbarker on October 15, 2011, 09:54:28 pm
I've noticed it often happens on my first call of the day.
I don't know what to make of this, but try making your first call each day with a different provider. If it still fails, we'll know that it's almost certainly not provider related. If you normally use GV and make the first call with e.g. Callcentric, you could pretend that the connection is not good (even though it's fine) and call back using GV to save most of the charges.
Alternatively, when you get up, make a test call. One choice would be 1-909-390-0003 (an echo test), which would confirm that audio is working in both directions. Perhaps better, call your own voice mail, which would test incoming audio and outbound DTMF (it's IMO unlikely that DTMF would work but not voice).
On a failing call, especially one with no incoming audio, it would be useful to see the OBi Call Status. You need to view the page before disconnecting the call.
Quote from: bbarker on October 15, 2011, 09:54:28 pm
I've tried the port forwarding as suggested and my net connection isn't busy when this happens.
Please provide details of your setup, even if you did that earlier -- a reader is more likely to help you if you don't make him read through 50+ posts. For example: "My WRT54GL running Tomato has UDP ports 5060-5061 and 16600-16999 forwarded to the static private address of the OBi. Router connects to Comcast via a SB5101 modem."
bbarker:
Quote from: Stewart on October 16, 2011, 03:11:22 am
One choice would be 1-909-390-0003 (an echo test)...
I just tried the echo test and it worked normally. I'll keep trying it and get more info if it fails. I've looked at the call log, but hadn't thought of checking the call status while connected. BTW, one time I had a "failed" call that required DTMF and it didn't work even though I could clearly hear their prompts.
Quote from: Stewart on October 16, 2011, 03:11:22 am
Please provide details of your setup, even if you did that earlier --
I have a 2Wire 2701HG-B combo DSL modem/router. I have ports 5060-5061 and 16600-16998 (both UDP & TCP) forwarded to my Obi110.
Not sure if it matters, but last night I updated my firmware to 1.3.0 (Build: 2586).
Thanks for the help.
QBZappy:
Quote from: bbarker on October 16, 2011, 09:52:32 am
Not sure if it matters, but last night I updated my firmware to 1.3.0 (Build: 2586).
That certainly may change everything. Hopefully it will fix the problem, If not you will have to continue trouble shooting.
At this stage the OBinai techs must know most if not all the possible reasons for possible call failure since they must be looking into this. I would suggest that you email the OBi support. They may resolve this more quickly for you.
subie:
Been having this exact problem for a long long time as well. Wife is also extremely fed up and I'm also at the point where I might have to start paying "the man" again for a land line. But I am so against paying at&t that I am even looking into cell phone boosters like the zBoost so that at least we can use our cell phones in our house.
Just upgraded to the latest 2586 firmware. I'm doubtful it fixes anything as the release notes only shows one thing it fixes which seems unrelated.
neilio:
Quote from: Everton on October 11, 2011, 01:07:05 pm
It is interesting that the problem you are having is NOT one-way audio, but the fact that your audio decreases after about 2 to 3 minutes into a call. <snip> It is interesting that you identify a potential issue that could be giving rise to this issue. See below (you are also using a specific brand of DDWRT-Milkfish, also you have tested without) the router
Actually, I've tried this using the default firmware for two different routers (ASUS RT-N16 and Netgear N600) as well as DD-WRT and TomatoUSB. Also, I've tried hooking the OBI directly to my cable modem so it gets the externally visible IP and still have the problem. I get both the 2-3 minute dropped audio issue as well as 1-way audio from the very beginning of the call.
I really wanted to make this work, but as you can see I've done a ton of troubleshooting with no solution. I gave up and went back to my 3102. I can appreciate this works for most people, but that's the way bugs go - they're not always reproducible by everyone.
Maybe I got a bad device, I don't know, but I didn't buy the OBI so I could waste weeks trying to chase down an issue that, for me, is highly reproducible. Doing packet captures and other deep network stuff shouldn't be necessary to properly use the OBI, and expecting end-users to know how to do this is ridiculous.
Navigation
[0] Message Index
[#] Next page
[*] Previous page