Other person can't hear me.
hoa2long:
Well unfortunately my uncle is the newest victim to this head-scratching dilemma. His 110 was going fine for the last 2 months or so and then this occurred. The call could go through but the recipient could not hear anything. I try calling him back on my obi110 and he could hear me fine. I am hoping it's not a hardware issue but as of now there seemed to be no pin-point solution just yet.
winger13:
On occasion, my wife places a test call to my work #, and silence. Once she calls me back, no problems.
I am new to OBI, but what level of service are we (customers) expecting to have from tech support? IS it low-level since we only paid $50'ish for the device???
MichiganTelephone:
Quote from: winger13 on April 12, 2012, 11:10:31 am
I am new to OBI, but what level of service are we (customers) expecting to have from tech support? IS it low-level since we only paid $50'ish for the device???
I'm going to take a wild guess and say that reading every thread in these forums is not the highest priority for Obihai Support right now, since they are basically focused on getting the OBi202 ready to ship. So posting here probably does not constitute a support request.
I've always suggested that the best way to get support is to e-mail support@obihai.com and include the 9 digit OBiTALK number from the bottom of your device and a CLEAR description of the problem, including what you have already tried. I will also note that Obihai has more or less said that if you choose to configure your OBi device manually rather than use the OBiTALK portal, it limits their ability to help you. So if you choose manual configuration, your support request may gravitate to the bottom of the pile, so to speak.
With the OBi202, I've had a couple of minor issues (though no problems whatsoever with Google Voice, except for the recent weekend when almost everybody was having issues because Google screwed something up) and in both cases they have been able to push a beta firmware build to my device that fixed the issue. That simply would not be possible if I had followed the bad advice given by one person on these forums that tries to discourage everyone from using the portal (just because HE finds it easier not to use it. Then he wonders why his support requests get ignored sometimes. Duh!).
Having said that, there may be reasons that a person cannot get Google Voice to work that are simply beyond Obihai's control. I always say, if possible, try taking your device to the home of a friend (preferably one using a different ISP than the one you use) and see if you still have the problem. If not, it's likely either your ISP, the crappy cable or DSL modem they provided, or your router. Or, you may have configured something incorrectly.
I will also point out that I have never had to forward ports from our router directly to any VoIP hardware device to make it work. So if you're having to do that, that again indicates you may just have a router issue. One thing you can temporarily try is connecting the OBi directly to the cable or DSL modem (bypassing the router entirely) to see if that makes a difference. If it does, it's highly likely that it's your router (or an improper setting in your router).
I'm not saying that when 35 people have an issue that's not significant, but remember that there are thousands of satisfied Obihai users and most of us just aren't seeing the problems you're reporting. And I am pretty sure that Obihai isn't seeing the issue at their location, or they'd be trying to fix it. You have to know what's causing a problem before you can fix it, and you have to know that the problem exists, which they actually may not if relatively few people have bothered to file an actual support request rather than just carping in this forum. There will always be a few people who can't get a a particular networked device to work, and the reasons can be anything from a bad network cable (NOT as rare as you might think!) to a crummy or misconfigured router to a problem with the ISP's service or modem. Obihai can't control (nor even detect) many of those kinds of situations, nor can any other networked device manufacturer. Remember, though, that VoIP is much more impacted by severe packet loss than just about any other type of networked service, and that's a problem only your ISP (or you, if it's a bad cable in your home) can fix.
oregonobi101:
have had this problem persistently.
I will buy the obi202 if it fixes this. It is for sale on Amazon TODAY. But I will wait for someone else to jump first who is more of an expert on these things. I think it's $74 on Amazon which is still a bargain, especially if it fixes this annoying issue!
dhfobi:
Quote from: MichiganTelephone on April 12, 2012, 03:11:40 pm
I will also point out that I have never had to forward ports from our router directly to any VoIP hardware device to make it work. So if you're having to do that, that again indicates you may just have a router issue. One thing you can temporarily try is connecting the OBi directly to the cable or DSL modem (bypassing the router entirely) to see if that makes a difference. If it does, it's highly likely that it's your router (or an improper setting in your router).
MichiganTelephone:
I'm glad to hear that as I never could understand why it should be necessary to forward ports with a NAT operating router. I forwarded ports recommended in various posts, but now that my system performance seems to have stabilized, I may try to remove the forwards and see if I notice any performance hit. The problem of not being heard is very annoying to me and particularly to my spouse, so I don't want to aggravate the problem.
Although the number of people experiencing this problem is minimal as a percentage of total users, it is none the less real, and hopefully the cause will be stumbled upon and fixed in the future. I'm reasonably sure it is not a hardware problem in my case as I am using a Linksys router running Tomato firmware with QoS enabled, into an SB6120 modem on Comcast HS Internet service. All of which worked perfectly with Vonage. I'm not suggesting the problem is attributable to the OBi100 device as it could be GV's problem, but I am hoping the cause will be found and resolved, and until that time I will live with it.
Thanks for your dissertation as it is insightful and helpful.
Navigation
[0] Message Index
[#] Next page
[*] Previous page