I am using the Obi100 with google voice. Frequently, the person I am calling cannot hear me very well and tells me we have a bad connection. But I can hear them fine. This happens only intermittently.
I already tried forwarding ports and putting the obi in the DMZ. QOS didn't help. And I am not downloading/uploading anything else at the time of phone calls.
Other ideas?
When this happens to me I reboot the Obi. That usually fixes it. I don't know why it happens either.
Thanks, I'll try that. How often do you need to reboot it? Also, is there a way to reboot it through the web interface or do I always have to unplug it?
Obviously, there shouldn't be a need to reboot the OBi periodically for proper operation, but...
If you log into the OBi at the IP address returned by dialing ***1, there's a Reboot button in the upper right corner.
This thread provides a VBS script and discusses a method for rebooting the OBi on a schedule:
http://www.obitalk.com/forum/index.php?topic=1152.0
OR you can do a ***9 from the attached phone and do a reboot :)
Same thing happens to me a few times a week where I call someone and they can not hear me. I don't reboot but call right back and have no trouble. Drives me nuts, but what can you do when it is free, ask for a refund :)
Joe Sica
This happens to me about once a week, it is totally random, I do not reboot my obi unless I upgrade the firmware. It does not seem like it is related to how long the device has been running. In fact I am not even sure if this is a Google chat problem or obi problem. Whenever this happen, I always report it to Google (go to Google Voice/call history, find the call history entry, check the "call quality" box with "person cannot hear you", this seems to be a very wild spread problem, hope it get fixed
Same problem here, the other person cannot hear me on some calls. I have done the port forwarding but it doesn't help. Interesting insight: even when I can't get a GV call to work with the Obi (because the other person can't hear me), I can still make a GV call through gmail and then the other person *does* hear me (even though the ports are still forwarded to the Obi and not the computer running gmail). So I'd say it's a problem in the Obi boxes.
Anybody know if GV has UPnP ability? If so, enabling UPnP on the router might help.
Same thing happens to mine a couple of times a week. All I do is call them back and everything's fine. I hope they fix the problem soon.
Quote from: heydan on August 12, 2011, 06:45:16 AM
Same problem here, the other person cannot hear me on some calls. I have done the port forwarding but it doesn't help. Interesting insight: even when I can't get a GV call to work with the Obi (because the other person can't hear me), I can still make a GV call through gmail and then the other person *does* hear me (even though the ports are still forwarded to the Obi and not the computer running gmail). So I'd say it's a problem in the Obi boxes.
Hi Heydan,
Thanks for the finding. We like to look into this problem.
Next time, when you cannot get GV to work, but your Gmail call phone works, can you please contact Obihai support at support@obihai.com with your 9-digit OBi number? so we can have a remote diagnostic, please also not trying to reboot the device, thank you,
- Obihai support
Obihai support,
Any idea why I haven't received a response to my email requests on 8/5 (2) and 8/7 for assistance with distorted audio through the Auto Attendant? I sent you a considerable amount of information about the problem including a couple of Syslog's and offered to make the OBi available for remote debugging, but never got a reply.
Hi RonR,
We apologize if you have emails to us that remains unanswered.
We will look into all your past emails and will address them if any of them sits unattended.
Thanks for all your timely assistance to our OBi users in the forum, it is much appreciated.
- Obihai support
Heydan and ObiSupport,
If this problem is eventually solved, please let the rest of us know here in this thread. I am having the very same problem. Port forwarding in the router has not resolved this either.
Thanks!
Ditto..
Joe Sica
I have the same problem. Port forwarding or/and QoS in the router no help. I hope the problem will be fixed as soon as possible.
We have had this problem as well. 3 different OBI firmwares (last 2 production and 1 Beta), much frustration and complaints from other family members. It happens at least 3-4 times per week, intermittent. I'm getting pleas to get rid of the OBI. Reboot also does not seem to resolve it. Has anyone had this problem on one of the older firmwares? Mine is newer, I've had this problem on the 1.2.1 2289 and 2384 releases, plus a beta in between which was supposed to help. I think I'll need to go back to our Cisco SPA3102 without GV until there is a solution.
Same here
The most frustrating is after you have been on hold for 20min. just to hear the other person say hello, hello, and when they can't hear you they just hang up. This happended twice in a row to me :'( Tomorrow I have a appointment with comcast. I will try to get them to install a splitter directly off of my modem bypassing the router. I will post back it this works.
>
Well, Comcast showed up. I was told by both the internet and tv departments at Comcast that they have a cat 5 splitter but it could only be installed by a technician. Then the tech showed up and said they have no such thing as a cat 5 splitter. What a waste time!
>
any suggestions out there to eliminate these dropped outgoing voice events? Unhooking the computer and pluging the Obi into the modem is not an option for me.
Quote from: voicemail on August 15, 2011, 05:38:01 PM
Tomorrow I have a appointment with comcast. I will try to get them to install a splitter directly off of my modem bypassing the router. I will post back it this works.
There is no such thing. The cable modem has one Ethernet port. If you need to connect more than one device, you connect a router to that single Ethernet port and the router provides the additional Ethernet ports.
Quote from: OBiSupport on August 12, 2011, 10:52:32 AM
Hi RonR,
We apologize if you have emails to us that remains unanswered.
We will look into all your past emails and will address them if any of them sits unattended.
Thanks for all your timely assistance to our OBi users in the forum, it is much appreciated.
- Obihai support
Still no reply to "DMP Problem" emails dated 7/20 and 8/2 and "pli/Mpli Expansion" email dated 8/7.
I have the same problem. I can hear them well, but they can not hear me 50% of the time. When the person who I can not hear me dialed the second time, it went fine. This is very annoying.
I've heard a considerable amount of complaints from homebase (my house) about other party answering the phone call unable to hear the google voice service. Sometimes I can't hear the person calling us.
Yes, it is very random and I to have tried the QOS method, forwarding ports and read that if this occurs then it could be a NAT issue with the router. Clearly, this is really an issue with either the device or the "best effort" service Google Voice provides. Has anyone tried any of the other VOIP companies that the OBITalk works with? I'm thinking of just paying for VOIP as I my google voice experience has been less than steller! Again it was free service... so.. can't complain too much but it is not consistent.
I have a Dlink DGL-4500 gamer router.
Advanced -UDP Endpoint Filtering set to Address Restricted
Advanced -TCP Endpoint Filtering set to Port And Address Restricted
Advanced - Firewall - SIP box is unchecked. I've had it checked before but doesn't see to make a difference. This was advice regarding removing any NAT issue from the router.
Gaming Rules:
Google Voice Obi IPaddress TCP port 5222 set to always allow
QOS Game Fuel Rules used:
Obi Gtalk UDP Prority:50 Local IP Range: Obi IPaddress Remote IP Range:74.125.0.0 - 74.125.255.255 UDP ports 1 / 65535 local and remote
Obi Gtalk TCP Prority:50 Local IP Range: Obi IPaddress Remote IP Range:74.125.0.0 - 74.125.255.255 UDP ports 1 / 65535 local and remote
I did have specific port ranges before but it didn't seem to matter so I opened it all up for QOS.
I called my friend this morning by using my phone (through OBi110 and GV). But she can't hear me and I can hear her. Then I called her by using my computer through GV, every thing was fine. It seems OBi problem, not GV problem.
Have same problem here. Called someone this morning and they couldn't hear me. Called right back and all was fine. Then a bit later, I called a number that required me to be on hold for a live person. I waited and waited, only to find that when the live person finally picked up, they couldn't hear me. Not cool!
I have the same problem today, twice: one in the middle of an interview. I had to call the interviewer back.
Check this thread:
http://www.obitalk.com/forum/index.php?topic=1130.0
The family users have revolted. Out goes the Obi110, in goes the Cisco SPA3102. It was (not) fun while it lasted. I'll post here if I have the same problems, but I doubt it will happen.
Please let me know also I am having the same issue. :'(
still have this one way audio problem. Very random. How does obi110 with google voice work? Does obi110 still talk to the obitalk network using sip and at the same time talking to googlevoice using xmpp? If a port 5060 is opened is it for the googlevoice or is it for obitalk? Since I can see my obi110 device having green color online, thus I would think there is some communication between the obi110 and obitalk. Anyone knows the answers?
Same problem. Configuration: Cox cable service, SurfBoard SB5101U cable modem, wrt160nv3 router, OBihai 110 connected to two Google Voice account, and to a landline. Wife is demanding a solution.
I have this problem across more than one ISP and with multiple routers.
What's causing it? Is it the OBI or is it GV?
Its 100% the Obi. I have been using Google Voice without the Obi for a year and never had this problem.
This is really frustrating to spend $50 on a device for the purpose of getting GV and it doesnt work!
Quote from: jmsnyc on September 21, 2011, 02:51:30 PM
Its 100% the Obi. I have been using Google Voice without the Obi for a year and never had this problem.
This is really frustrating to spend $50 on a device for the purpose of getting GV and it doesnt work!
If you are 100% sure it is the device, why not contact OBiSupport and let them know that their product is defective and you would like to get your $50 back. I'm sure they would oblige. My question to you is, if it was an issue with the device, why haven't see an avalanche of complaints from OBI users? Secondly, if you have an VOIP provider on SP2 (or SP1), have you experience any audio issues?
You should be aware that Google Voice was not setup to be your primary phone or standalone phone system. If you are not happy, return the product and stop bitching, since I have not had any audio issues whatsoever!! I'm sure your Landline company will be more than happy to accept your $40+ per month.
Quote from: DaveSin on September 21, 2011, 03:05:44 PM
If you are 100% sure it is the device, why not contact OBiSupport and let them know that their product is defective and you would like to get your $50 back. I'm sure they would oblige. My question to you is, if it was an issue with the device, why haven't see an avalanche of complaints from OBI users? Secondly, if you have an VOIP provider on SP2 (or SP1), have you experience any audio issues?
You should be aware that Google Voice was not setup to be your primary phone or standalone phone system. If you are not happy, return the product and stop bitching, since I have not had any audio issues whatsoever!! I'm sure your Landline company will be more than happy to accept your $40+ per month.
stop bitching??? i am simply looking for a solution as to why the other caller can't hear me... whether or not its a standalone phone it should still work - basic functionality is that a phone conversation is suppose to be two way - to imply that because its a cheap solution one sided conversations should be acceptable is just idiotic... and just because you are not having any issues, there are a few other threads on this so other people are experiencing this
i have not been paying ma bell for probably the past 10 years, other voip providers have worked fine and there are other cheap options, each with its own flaws but at least basic phone functionality works... i.e. magicjack, netduo etc
and like i said i have been using google voice without the obihai and it worked fine...
I'm not saying the device is defective, I am saying there is something wrong that is preventing, on an inconsistent basis for the other party from hearing me. It could be hardware, firmware or even an incorrect setting on my device. I am just posting on this forum trying to find a solution.
I'm having exactly the same issue. One third of my calls through GV ended up with the other party complaining about breaking up audio. Sometimes the voice was good for the first minute and it started to break up. I've tried a lot of suggestions (port fordwarding, DMZ, QOS) with 2 different RGs and none of them helped. I'm having 2 lines, one is GV and the other is callcentric. The callcentric one is better in quality but the voice still breaks up sometimes. I've monitored this forum for quite a while and looks like it's not my own issue.
I am having the same problem and it is not trough Gvoice ,just sip and pstn line,also the people here should focus on technical problems trying to help each other and then the life will be beautiful again. :o
I just want to mention that I contacted support and they pushed a firmware update. I had updated recently (less than a month ago) so I am not sure if it was different than what I had.
I am not sure if the problem is resolved because it happens sporatically but I will post again if it reoccurs.
Quote from: jmsnyc on September 26, 2011, 05:34:55 PM
I just want to mention that I contacted support and they pushed a firmware update.
Is this the version you are currently using?:
SoftwareVersion 1.3.0 (Build: 2532)
Quote from: RonR on September 26, 2011, 05:38:24 PM
Quote from: jmsnyc on September 26, 2011, 05:34:55 PM
I just want to mention that I contacted support and they pushed a firmware update.
Is this the version you are currently using?:
SoftwareVersion 1.3.0 (Build: 2532)
I think that is what I was using.
1.3.0 (Build: 2558)
Quote from: jmsnyc on September 26, 2011, 05:58:54 PM
Quote from: RonR on September 26, 2011, 05:38:24 PM
Quote from: jmsnyc on September 26, 2011, 05:34:55 PM
I just want to mention that I contacted support and they pushed a firmware update.
Is this the version you are currently using?:
SoftwareVersion 1.3.0 (Build: 2532)
I think that is what I was using.
1.3.0 (Build: 2558)
Hmm, wonder when/if we'll see this in the wild.
Tom
I still have issues.
I just tried to make a call and I could not hear the callee nor could she hear me. I then tried to call myself on my cell and the same thing happened.
I am thinking Obihai has firmware bugs.
Also, is call waiting disabled by default? It does not work either, just goes to voicemail if I am on the phone. Or does GV not support it?
Update: It is enabled by default under Physical Interfaces Phone Port but it does not work.
Up until now I thought the person calling me heard the ring but just didn't hear my voice after I answered. Today, the person calling me couldn't hear me after I answered (happens more and more frequently these days). I then hung up and re-dialed the person who had just called me. The outgoing call was successful. I learned that on the first attempt the person calling me not only didn't hear my voice but didn't hear a ring. However, my cellphone and the phone I have plugged into the OBi110 both definitely rang.
Quote from: jmsnyc on September 26, 2011, 06:43:19 PM
Also, is call waiting disabled by default? It does not work either, just goes to voicemail if I am on the phone. Or does GV not support it?
Call Waiting works with Google Voice here. For it to work you would have to have:
Voice Services -> SPx Service -> MaxSessions : 2
and only have one of those 2 sessions in use (i.e. just one Google Voice call in progress).
Quote from: RonR on September 26, 2011, 06:59:50 PM
and only have one of those 2 sessions in use (i.e. just one Google Voice call in progress).
Just to clarify what you are saying. If I am talking to someone using Google Voice and someone calls my Google Voice number, it would not work because 2 calls would be in progress?
The incoming call would be the second session and should arrive at the OBi and signal call waiting.
I just made an outgoing call on Google Voice and then called my Google Voice number from my cell phone. I heard the call waiting signal and could use the Flash button to switch calls.
Ok. Thanks. Seems to work for me too.
I'm having the same problem. Half of my calls this morning were uni-directional -- either they couldn't hear me or I couldn't hear them.
Software Version: 1.3.0 (Build: 2575)
Glad someone passed this thread on to me or I wouldn't have known this was a more widespread issue. Same problems here with my audio cutting out about 2-3 minutes into the call. I switched back to my SPA3102 until there's a fix - hopefully OBI is aware and working on one?
<<I'm having the same problem. Half of my calls this morning were uni-directional -- either they couldn't hear me or I couldn't hear them.>>
We have the same problem for some time now,after a little while in the talking is getting uni-directional or one of the party hear a very slow and modified voice,and for the last days is getting worst. All of us having this sort of problems have to switch to other devices or the vendor is going to fix them????That is the basic function not fussy setting just PSTN-OBI110-0BI110-PSTN call.
The problem has been very consistent: when I call out from my OBi110 (hardware version 2.8, software version 1.3.0 (Build: 2575)) to another party, I hear them fine, but they report bad or non-existent audio.
I need to do some more testing before reporting on the characteristics of the party I am calling,
but I can note the following:
- when a specific called party is using an OBi100, the problem occurs on almost every call; but not always immediately
- when I call that specific party using the OBiTalk network (i.e. **9NNNNNNNNN), the problem does not occur
This suggests the problem has something to do with Google Voice.
Darn. I see my problem is widely shared, and no answer yet. I've been thinking it was a problem of slow upload speed (my DSL, as usual, has fast download but slow upload speeds) because I can usually hear the other person, but they can't hear me, or they hear me badly broken.
Is it possible that's the problem?
My wife is so frustrated with OBi (after also being frustrated by MagicJack for intermittent poor voice quality) that I've promised to call AT&T tomorrow and renew the old land line. Reluctantly, I'll put the OBi in my box of unused computer gear, and hope for a solution in future.
Gotta do what you gotta do...
Quote from: obeeonecanoebee on October 06, 2011, 09:00:03 PMI've been thinking it was a problem of slow upload speed (my DSL, as usual, has fast download but slow upload speeds) because I can usually hear the other person, but they can't hear me, or they hear me badly broken.
Is it possible that's the problem?
Doubtful - I have a 7mb upload link plus I have QOS set up and I still see the problem. Also, I can't reproduce this issue using another VoIP adapter (a linksys SPA3102) or via soft phone.
I gave up on the OBI for now as we need to have a working line, but I'll open a ticket with support to see if this can be escalated. I recommend anyone else here with this issue do the same.
I too have intermittent problems with the other party not hearing me. Also, when someone calls me, much of the time I cannot hear them say hello, but can hear subsequent speech. I'm using the Obi100 with GV.
I can't believe this thread. There are more than 50 posts, yet not a single person has taken even a modest effort to troubleshoot the problem!
It's clear that many thousands of OBi customers, the vast majority, enjoy clear phone calls. However, there is also compelling evidence that in some circumstances, the OBi is less robust than other ATAs or software, resulting in no or poor quality outgoing audio.
If we can accurately report what goes wrong, then Obihai can find the bug or weakness and fix it. In the meantime, the details will likely suggest a workaround to mitigate the problem.
This isn't rocket science. The OBi might be improperly coding the audio, sending corrupted or improperly timed RTP, having intermittent networking issues, or triggering a problem at the provider. Or, maybe it's some other issue I haven't thought of.
As a start, do you have the problem with multiple providers, e.g. Callcentric as well as GV? On both incoming and outgoing calls? When you are reasonably certain that the problem is not on the other end, e.g. calling a corded phone connected to a landline? Does it affect bridged calls, as well as calls from the Phone port? During a bad call, can you make a concurrent good call (using a softphone or other VoIP device)? Via the same provider and server? To the same destination?
Next, take a look at what the OBi is sending. Using a dumb hub or a PC with two NICs, set up your PC so it can "see" the OBi's traffic. Capture the packets with Wireshark. When you have a bad call, save the RTP in a file and listen to it. If bad, look at the payloads for clues. If good, check the stream for timing or other technical problems. If there are none, check whether e.g. a concurrent ping to the provider's server shows severe jitter or packet loss.
Of course, I have no idea what may be going wrong here; my specific suggestions may be inappropriate for the problem at hand. However, keep your eyes open and think about what may be happening. Pretend you're a doctor and determine what's wrong with the patient. Don't just report that he's sick.
FYI - for me, it's been difficult to track down as I have zero problems using any other adapter (SPA2102 and 3102) as well as the soft phone. It's just the OBI100 hardware itself that has this issue, and for me it happens on all channels (SIP1/2 and GV). I haven't tried Obitalk yet, but as I can't reproduce this issue with any other configuration it's pretty obvious at least something relating to OBI is at fault here, though for why I don't know.
You couldn't know this as you probably haven't seen my earlier posts, but I've posted a number of times with troubleshooting info and attempts to fix this issue. I'm sure at least some others have done so, too. So please don't go assuming that people are just bitching without actually trying to troubleshoot.
Neilio, assuming that the trouble occurs on a reasonably large percentage of your calls, i.e. it would only take a few tests to reproduce the problem, would you be willing to connect the OBi via your PC, so you could take a capture that you or someone else could analyze?
Quote from: neilio on October 11, 2011, 10:10:11 AM
FYI - for me, it's been difficult to track down as I have zero problems using any other adapter (SPA2102 and 3102) as well as the soft phone. It's just the OBI100 hardware itself that has this issue, and for me it happens on all channels (SIP1/2 and GV). I haven't tried Obitalk yet, but as I can't reproduce this issue with any other configuration it's pretty obvious at least something relating to OBI is at fault here, though for why I don't know.
You couldn't know this as you probably haven't seen my earlier posts, but I've posted a number of times with troubleshooting info and attempts to fix this issue. I'm sure at least some others have done so, too. So please don't go assuming that people are just bitching without actually trying to troubleshoot.
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. You are the only one, to my knowledge, that have this specific issue. If this was a systemic issue (Firmware, hardware), I would expect a significant amount of OBi users to have the same problem. I have read a number of your posts and you keep harping back to the fact that you have no problem with your SPA3102, nor your PAP2. 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:
Quote
Just tried running the OBI "directly" connected to the modem and still had the sound drop out. The only thing I can think of is that I'm connecting the OBI to the mode via power line ethernet — I wonder if that could be what's causing the sound drop issue.
I've moved the OBI to be directly connected via ethernet to the router and will see if that helps.
I am considering reverting back to firmware Maintenance Release 1.2.1(2289). Anyone know if this has the same audio problem? I don't recall any issues during it's use, but I am not a volume user.
I have had the same problem since I got my OBi in March of this year with every firmware, from orig to current...
Joe Sica
ModelName OBi110
MACAddress 9cadef00073d
SerialNumber 88B01NA00YHS
OBiNumber 200 494 NNN
HardwareVersion 2.8
SoftwareVersion 1.3.0 (Build: 2586) (I wish the software version was available from the ObiTalk portal)
The "other person can't hear me" problem is gone (or perhaps in remission), possibly as a result
of a recent software update. I will continue to monitor and post (my wife is being very tolerant, but
I am pressing my luck).
I often have calls where the other person can't hear me and occasionally I can't hear them. I hang up and call back and everything is OK. I don't think it's ever happened twice in a row. I've noticed it often happens on my first call of the day.
I've tried the port forwarding as suggested and my net connection isn't busy when this happens. Any other suggestions? Is there any diagnostic info I can provide that might help track down this problem?
Quote from: bbarker on October 15, 2011, 09:54:28 PMI'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 PMI'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."
Quote from: Stewart on October 16, 2011, 03:11:22 AMOne 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.
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.
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.
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.
Quote from: neilio on October 18, 2011, 01:19:26 PM
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.
Does this mean that reverting to 3102 fixes the problem? I have had the OBI110 since March when the rush happened and I have experienced this issue with every FW. The worst part for me is the dropped calls. After 10 - 15 minutes into a call I hear a terrible noise and then the call drops. Some times the other party hears a noise. Some times they just loose the call.
BTW I just had to warranty my 110 because it stopped working entirely (OBI tech support is great! It was painless. Best RMA procedure I've EVER had). I was hoping the new device wouldn't do these things. Well, it does. I'm thinking that it must be Google Voice and not the OBI110. I'm certain that the Obihai staff can reproduce these issues. If it were under their control I imagine they would either do something about it. The weird fact is that they haven't openly said that it is Google Voice and not the OBI. This is why we are all scratching our heads and waving torches at Obihai. There should be some public recognition of these issues and an explanation to the best of their abilities.
Quote from: S--F on October 19, 2011, 04:00:55 PM
Does this mean that reverting to 3102 fixes the problem?
Yep - I've had the 3102 in place for about 10 days and had zero issues. I'm starting to wonder if I should RMA mine as well.
We would like to work with you to get to the root of the problem.
I have PM'd you both to see about doing this.
If anyone else is experiencing this issue please contact support@obihai.com.
We will get it resolved.
Thanks!
I've been reading through all of the forum discussions on this. I have been experiencing the call dropping since the beginning of October and have had the device since August. It drops my calls after about 3-10 minutes. It doesn't matter how many times I call the person back or they call me, it still drops. I am not a technical person. So I am afraid I don't understand any of the language like port forwarding and such. Can anyone help me out in trying to figure out what is happening or explaining in layman's terms how to test the device or how to move back to an old firmware update? I only have Google voice through the Obi because I can't afford anything else as I am in grad school. I would appreciate any help as it is getting the point where I can't talk to family members or friends back home.
I will contact support as well. But I am afraid I won't understand what they tell me to try. I just fall short at computer issues.
Thank you!
Hi,There is some time since we have those problems(two Obi110 in Romania and one in Australia)
The obihai is exchanging e-mails with me trying to fix that.
I put the coppy of my last email send to them in weekend,maybe helps finding a common culprit of that.
>>>>>
Hi
1.I did,even I took out the AU Obi line, still happening .
2.LINE port have been used for most of the time just on the Romanian obis
3.For now I don't change firmware living it as t he last resort to try
4.Calling local numbers -not distorsions,I called different combination ,From mobil-short call to Obi-Sp1-call back tru **8 xx-mobil-call other number again tru Sp1 -everything ok
5.Is nothing to do with the complexity of the call,the basic scenario which trigger the problem is Phone Obi Au-Obi(s)Ro-Line out.
After i do the first call as above,the first call from Ro mobile-ObiRO-ObiAU-phone/or callout has:
a)on Romanian obi distorsions on AA and
b) call droping,distorsion and reduction of volume ,most of the time he can notice that after hearing a noise like a ,,cling" and that happening variabil in time on each call but never ccome back to normal during the call.
c)From that on doesn't matter which one is calling the problems persist till all Obis are reboot
!!! If is only Romanian party calling Australia we didn't notice to happen,this is probably why we thought ,,sometimes they works fine for a period of time"
It is a strange behavior ,hope that helps to ,,eradicate" the problem!
Have Nice Weekend!
from the bottom of the.....Globe
Paul Costea
+1, having issues, looking for an answer. I can hear the caller fine, but they can't hear me so well. I bypassed my Obi and used Google Voice direct from my computer and the audio was fine. I guess I'll try that support email next time I have an issue, and see if Obi staff can troubleshoot it.
+2... this has been going on for WEEKS... come ON OBItalk... give us a solution!!! I hear them FINE but my words are cutting out CONSTANTLY... it's MADDENING!!!!!!!!!!!!!!! ???
i have the same issue now on googlevoice.(i can hear just fine while the other party cant hear me)
in fact today the obi rebooted in the middle of a call.
i am having the same issue with google voice. i can hear other party just okay but they cant hear me clear.
rebooting obi is not helping at all. I had to switch to web to place the calls.
I'm having the same problem, I can hear fine and the other party says I'm breaking up. My Comcast internet speeds are 25mbps down and 4mbps up, from SB6120 modem and Linksys wrt54G router running Tomato firmware and QoS turned off.
I just bought the Obi100 and am using it with Google Voice. I will continue my evaluation for another 2 weeks but if this cannot be resolved I will return it as my wife is upset and refuses to use it with this problem. I currently have Vonage and no such problem with it. I's like to use the Obi/GV connection as the price is right, but not with the current performance. Since I'm seeing that this problem has been reported for months with no solution, I'm not encouraged that this will be my replacement VoIP service.
dhfobi,
Here's something easy to try:
1. Dial *** 0
2. Enter option 27 and press #
3. Press 1 to set a new value
4. Enter a value of 1 and press #
5. Press 1 to confirm/save
6. Hang up
7. Wait for the OBi to reboot
This will change the Ethernet port on the OBi from 10 mb/s half-duplex to 100 mb/s full duplex. This helps in some cases.
"This will change the Ethernet port on the OBi from 10 mb/s half-duplex to 100 mb/s full duplex. This helps in some cases."
Thanks,
I've done it. How on the Obi100 web page can I see the port settings?....Assuming I can.
You can't. It's a hidden setting only available from the IVR configuration menu. You can confirm it took by executing Option 27 again and hearing that the value is now 1 rather than 0 (the default value).
Quote from: RonR on January 29, 2012, 08:03:37 PM
You can't. It's a hidden setting only available from the IVR configuration menu. You can confirm it took by executing Option 27 again and hearing that the value is now 1 rather than 0 (the default value).
Got it, thanks again
Quote from: dhfobi on January 29, 2012, 08:07:33 PM
Quote from: RonR on January 29, 2012, 08:03:37 PM
You can't. It's a hidden setting only available from the IVR configuration menu. You can confirm it took by executing Option 27 again and hearing that the value is now 1 rather than 0 (the default value).
Got it, thanks again
No help,...... any other suggestions? I've read to setup a separate subnet for the OBi, and/or port forward ports to the device, are any of these, solutions to the 'audio breakup' problem?!?
My Vonage service fortunately is working fine and is what my wife is using so I have another couple of weeks to evaluate the OBi/GV system before my 30 day return option expires.
Any suggestions would be appreciated.
You can add me to the list of people with the same problem. I frequently call receptionists and they answer with the name of the company and then say "hello, hello" and hang up. This happens 1-2 times a week. One time I was on a conference call that went for like an hour. I listened the whole time and then tried to chime in at the end and realized that nobody could hear me. Very frustrating. I am going to have to get rid of this device if a problem is not found soon. It otherwise works very well.
My Obi110/GV setup was working fine for more than a month. I then started having this problem. It happens intermittently so it it is very difficult to trouble shoot.
Drives my wife (and her sister who can't hear) nuts.
Reading this thread there appears to be allot of ideas but really no known user solution.
I'm wondering how prevalent is the problem. Have I just hit a bad stretch due to internet traffic or some such?
One alternative would be to abandon the free Google Voice and switch to another SIP. Is there a problem with that? Can the obi setup approach the quality of POTS .
Somewhat frustrated. :'(
Comments?
Quote from: richardcoop on March 12, 2012, 05:44:39 AM
My Obi110/GV setup was working fine for more than a month. I then started having this problem. It happens intermittently so it it is very difficult to trouble shoot.
Drives my wife (and her sister who can't hear) nuts.
Reading this thread there appears to be allot of ideas but really no known user solution.
I'm wondering how prevalent is the problem. Have I just hit a bad stretch due to internet traffic or some such?
One alternative would be to abandon the free Google Voice and switch to another SIP. Is there a problem with that? Can the obi setup approach the quality of POTS .
Somewhat frustrated. :'(
Comments?
This thread has been ongoing and unresolved for close to 8 months and I too continue to experience the problem sporadically. We call or pickup a call and although we hear the other party perfectly, they cannot hear us at all, that is it's not that we're broken up, but we are not heard at all. If we or they call back, the problem is gone.
Has anyone isolated the problem to the OBi or GV? Is this problem unique to GV and are other service providers not experiencing this problem or is this associated with the OBi device and independent of service provider.
My system is Comcast high speed internet via an SB6120 modem feeding a Linksys wRT54GS running Tomato firmware with QoS on or off which makes no difference. My rates are high, 20mbps down and 4mbps up, which is way more than adequate for VoIP and I have virtually nothing else going on when I experience the problem.
I am willing to change service providers if someone can say with assurance that the problem is with GV and not my OBi100.
I need to do something as the situation is becoming unbearable and if there is no solution I may reluctantly have to return to Vonage. >:(
BTW I have port forwarded the associated ports to the Obi100 and have set the ethernet port to full duplex as previously suggested.
Any final thoughts?
dhfobi,
It seems that you have been persistent in trying to find what is causing this. As a final test, you might consider signing up with a SP like voipms (or any other reliable/reputable high quality SP) on a pay as you go rate. For less than $5 for one month you will be able to know if GV is the culprit. You should be able to have an answer in the first day of use. I think there are even some SPs which provide a small credit to try them. I think that might be the only way that you will know for sure. Then you can decide what you need to do. I hope you report your findings here if you decide to go that route.
As you noted this is an old thread. Lots of people would be interested.
Not a bad idea at all, and I was hoping someone else had done that over the past months this problem has been reported.Unfortunately it can work fine for weeks and suddenly several calls in a row have the problem. I wonder if those previously reporting in have either decided to live with it or left the forum and returned to their previous telephone service provider.
Any of you still tuned in?
QBZappy,
We have this from earlier in the thread:
Title: Re: Other person can't hear me.
Post by: jeremyan on September 26, 2011, 02:19:04 PM
I'm having exactly the same issue. One third of my calls through GV ended up with the other party complaining about breaking up audio. Sometimes the voice was good for the first minute and it started to break up. I've tried a lot of suggestions (port fordwarding, DMZ, QOS) with 2 different RGs and none of them helped. I'm having 2 lines, one is GV and the other is callcentric. The callcentric one is better in quality but the voice still breaks up sometimes. I've monitored this forum for quite a while and looks like it's not my own issue.
I have seen lots of things tried in software but maybe it is hardware problem(s).
Quote from: richardcoop on March 12, 2012, 07:50:32 PM
I have seen lots of things tried in software but maybe it is hardware problem(s).
It's worth people noting their OBi's HardwareVersion in regards to this problem.
I've never had any of these problems and I'm running units that are over a year old here:
HardwareVersion : 2.8
I have hardware version 2.8 also, but components can have some variation.
My hardware version is 3.4
The maximum operating temperature of the obi is 45C (113F). I moved the obi 110 from on top of my warm router.
Lets see if that helps.
Quote from: richardcoop on March 13, 2012, 11:24:27 AM
The maximum operating temperature of the obi is 45C (113F). I moved the obi 110 from on top of my warm router.
Lets see if that helps.
Good luck, but don't hold your breath ;)
Mine is not on top of anything and the room temp is ~65F
So far the voice quality has been better but now I have a new problem. People call, the phone rings and I can't pickuo. The caller is directed to voice mail and I am talking to a dead phone.
I and my wife are at our wits end.
Quote from: richardcoop on March 13, 2012, 03:36:52 PM
I and my wife are at our wits end.
My wife has gone over the edge already, I however are more forgiving,..... up to a point.
35 people have reported the "Other person can't hear me problem" but there has yet to be an investigation and results reported back to this thread. What does it take to get the OBi tech support to investigate and respond? If nothing other than to say "we have exhaustedly investigated these reports and can say with assurance that this is not an Obi problem" That would be acceptable if true and would end this thread an send us elsewhere for the solution. I have Checked the GV forum and other than users not turning the mic on, on their computer, no one is complaining about this problem.
This has been happening to me too. Randomly. But, today, on all my calls, no one on the other end can hear me.
I have not changed anything on my router, etc., and it was working before.
Also, I forwards ports (listed below) to my Obi110 (I have a WNR3500L)
TCP Ports: 6800, 5222, 5223
UDP Ports: 5060, 5061, 16600 to 16998
Allow Incoming on UDP Port: 10000
I also just used my Obi110 (via Google Voice) to call my cell, and I can not hear my voice on the cell.
I have reboot'd Obi110 serveral times (i.e. did not unplug Obi110)
Found Solution --- FYI -- My PROBLEM started today Mar. 14, 2012 ---
For some reason, the OBi110 is sending out packets on PORT 19305 today.
So, I added port 19305 into my QoS rule and everything worked.
I just received my obi100 today and I am having the exact same problem.
I can hear them fine, they here my voice broken up.
No Solution?
Is it a hardware issue???
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.
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???
Quote from: winger13 on April 12, 2012, 11:10:31 AMI 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.
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!
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.
If this helps anyone:
I have Netgear WNDR3700 router. I have been using OBi for about a year, I never had this stuttering problem. Last week, I purchased a backup router that was on sale "Belkin F7D7301 Share Max N300 Wireless N+ Router", and loaded Tomato firmware on it (tomato-K26USB-1.28.7497.1MIPSR2-Toastman-RT-Ext.trx). I started to observe this stuttering problem, immediately only on Google Voice on SP1. When I call my Obi from work or cell phone, there is terrible stuttering, it is impossible to understand the AA prompts. I enabled QoS, did not help. I also have SP2 service from CallCentric, it worked OK but with some degradation in quality.
I immediately removed the Belkin and started using Netgear, then, problem disappeared.
When I have more time, I will try Belkin again, maybe with different firmware.
Edit on 5/21/2012: Enabling Qos with Default settings in Toastman's Firmware caused this problem. I also switched to another version of Toastman 7498.1 release. I do not see this problem any more, QoS disabled.
FWIW, I've never tried any of the Toastman releases, but I have been using tomato-K26USB-1.28.9054MIPSR2-beta-Ext.trx for the past year with OBi's and haven't experienced any problems.
Having the same problem.. but when i call from my computer on GV its the same problem.. so im hoping its GV and not my obi
I have the same problem reported in this thread. Here is my email trail with Obihai Support Team. I am sorry that in the end I still do not have a resolution.
Me
==
We have the following two problems
a) Many times we can hear the other party but they cannot hear us. I have tried to restart the Obi100 by pulling the power and putting it back it in.I have tried to restart with ***9 and then 1 to reboot. But the issue still exists
b) Many times there is lot of crackling in the sound we hear.
I have set up Google Voice on SP1 and Voip.ms on SP2.
Thanks in advance but let me know whether you need any other information
Obihai Support Team
===============
Do the remote end not hearing you at all or do they hear you choppy ?
What is your internet link ? DSL / Cable / Satellite ?
What is your upload/download bandwidth ?
Try to set/configure QoS on your router.
Set it to give highest priority for OBi, and give "upload badwidth" to 100Kbps.
Google Voice requires usage of 100Kbps bandwidth, so this amount needs to be "reserved" for OBi.
Typically the QoS setting is for what ip address of the device.
Reboot your router after you change this setting, to make sure that it is remembered.
For QoS configuration, please look at your router's manual. Here is an example for Linksys router model:
http://www.voipmechanic.com/setting-qos-voip-linksys.htmMe
==
Thank you very much for your prompt answer.
I have a DSL connection with 6MBPS download and 500kbps upload. It has been working ok till around last month. We have started having this problem recently. When I searched on internet, I saw the following thread and seems lot of people have reported the same issue
http://www.obitalk.com/forum/index.php?topic=1316.0
Obihai Support Team
===================
Configure your router to allow outgoing packets on UDP port 19305.
You can also try to put OBi's IP address in your router's DMZ.
Me
==
I have added UDP port 19305 to the list of ports to be forwarded to the Obi100. I had already added 5060, 5061 and 16000 - 16991. I will see how it goes.
Thank you very much for the answer.
Me
==
I added the ports, as shown in the picture below. (192.168.1.2 is the Obi100 device). Still no luck. It is always the other party that is not able to hear us. This is only on some calls, There are calls where both parties can hear well.
<picture> DD-WRT --> NAT/QOS --> Port Range Forwarding page </picture>
Next I am going to add the Obi100 to the DMZ and see whether that works. Thanks for your answer.
I want to bother you with another issue I have. The line is choppy sometimes. I am guessing that this happens if the internet bandwidth is in use by other applications like NetFlix. I wanted to confirm that this can be resolved either by increasing the bandwidth - a higher MBPS or QOS. My current bandwidth is 6 MBPS down and 500 KBPS up DSL conection.
Obihai Support Team
===================
Our instruction in
http://www.obihai.com/FAQ.html#ports-to-keep-open-on-my-router
is to allow outgoing packets on these ports.
Not port forwarding them to OBi (incoming)
For choppy audio, set QoS for your router.
Give OBi highest priority and bandwidth amount of 100KbosMe
==
Well opening the ports and port forwarding aren't they the same? When a request comes from internet to Obi100 on port 19305, the port forwarding allows access to that port on Obi100, which in other words means that that port is open.
I am trying to place the Obi100 on DMZ for few days. I will know whether that works
Thanks for your answer.
Me
==
I have put the Obi100 in DMZ. So no port is blocked. I am still having the problem of other person not able to hear from my phone. I reset the Obi100 to factory defaults and just set up Google Voice. I still have the problem.
I have been using Obi100 since early last year from the time Obi100 came out and I have been using the same router since then. I have not had this problem till sometime last month. And when I visited Obihai facebook page, I find that an update was pushed out. Is it possible for me to roll back to the firmware prior to that? I never had this issue at that time.
Thanks
Obihai Support Team
====================
You need to allow outgoing packets on udp port 19305.
When you do "Port Forwarding", that is incoming packets.
You can leave OBi in the DMZ.
The current firmware that you have, 2711, is good. There is no reason to downgrade.
Me
==
Thanks for your mail. I have done the things you suggested. I am still having the same problem of other party not able to hear anything at all. Is there anything else that I can try? I am afraid right now I have hit a wall and it seems like I have try some other product. It has been working well till last month. Thanks for your time.
sramaswamy,
You didn't mention, however I assume you are having problems with both the GV & voipms. Just a few things to see if there is anything unusual:
1) While in an active call look at the call status and note the codec being used and the other info. Test using both SPs.
2) As a last resort set up the OBi at a friends house and see if it can be reproduced there. (This is a pain, I know)
3) If you could get your hands on another brand of ATA you could compare and conclude if it is a router or ATA related problem.
Disconnect the OBi and check the following (OBi not involved in anything):
4) Does making a call using a soft phone client work properly when connected directly to voipms?
5) Does calling the GV number using a cell phone, making the call directly to the computer work properly?
Good luck.
Thanks for your answer.
I do not use the voip.ms much. So I am not sure whether I have the problem with that as well. I did not have these problems all these time - that is about 10 months. It just started last month and that too only on some calls.
I will try to follow up on what you have written. But again the problem is that the google voice through Obi100 does work sometimes. So not entirely sure if it works from another place it is certain that it always works.
sramaswamy,
Just so you know even real voip pros sometimes with all their expertise sometimes are baffled by some problems and must live with connections which are not stable/reliable. I was on another site (DSL Reports) recently, and I read a reply from one of the senior voip gurus there which made me laugh because I thought I was the only one doing this. I assumed that the real pros could resolve these things. He was checking daily if the connection to his commercial voip service provider was active. For some reason it was not reliable. The reason it made me laugh is because I had a similar problem with voipms. I had to figure out a way to reboot my PBX automatically everyday, yet this still did not work. For some reason it now seems to be stable again, and don't ask me what I changed.
Every family seems to have a designated technical guy. It seems that it might be you in this case. One way or another you will be resolving this issue. Keep us posted.
QBZappy
Before I write anything else, I am sorry if I came of as dismissive in my reply. That was not the intent in my answer. I appreciate someone devoting the time to read through post and being helpful. I also understand that there is lot of interconnected technologies - internet connection, the router, other devices, modem and not to speak of software updates. Any of it could have changed in the last month. Considering my knowledge is limited, any input is most welcome.
Now following up on your suggestion, I did the following:
Since GrooveIP does almost the same thing as Obi100, I decided to try that out. I got a new google voice number on a different gmail account, installed GrooveIP on an android phone. I connected through the Wi-fi connection on the same router. Guess what, I have the same issue. I can hear the other party and they can't hear me.
So the above almost rules out any issue with the Obi100 and its settings. The next candidate to investigate is the router. Is it blocking the outgoing data? But I have placed the Obi100 in DMZ - to the best of my knowledge I think. Still investigating. Any pointers from anybody most welcome
I think the most likely reason for the other person not able to hear is the upload bandwidth saturation. It looks if there is no upload bandwidth available, then the other person cannot hear. I thought the audio will be choppy and not total silence. Since I have DSL the upload bandwidth is somewhere between 400 - 500 KBPS. The home uses online service like Netflix. Does service like Netflix take up so much upload bandwidth? I guess I will try to upgrade my internet connection and see whether that resolves the issue.
Upgrading your service and applying QoS to the upstream will help.
Expose VoIP Problems Using Wireshark (http://www.linuxjournal.com/article/9398)
I have the exact same problem.. NO ONE can hear me when I call them or even if they call me on GV. Bandwidth is not an issue with me as I have 30Mb down and 4Mb up. I have also done everything in this long forum too.One thing I did notice is that Comcast did a firmware update on my modem and the next day everything started going south. I am without a phone and can not call comcrap now so I will maybe see about a online chat tomorrow. I used the phone Wednesday evening before I went to be an all was fine...then on Thursday I called my friend and from that pointe no one could hear me....
I am thinking the new cable modem firmware and the defauly "NATP" is enabled also there new "firewall" could be part of the issue too. I have a Netgear WNDR3700 and the OpenWrt Backfire 10.03.1 firmware which has been fine until Thursday when I went to make my first call of the day.
I think comcrap updated my modem Wednesday/Thursday overnight, because I check the modem status almost every 2-3 days.
Anyone got any other ideas??? ??? ???
If your cable modem has more than one Ethernet port, it's probably now set up as a router and causing your trouble. Assuming that you are using only one of the Ethernet ports, it should be possible for you to turn off the router function and get back to the functionality you had before the "upgrade".
Check the WAN IP address of your Netgear router. If it is a private address (192.168.x.x, 10.x.x.x, or 172.[16-31].x.x), the modem is doing NAT and is likely the problem. Try turning off any firewall or NAT functions. You may need to reboot modem and router to regain Internet access. Once that's working, confirm that the router WAN IP is now a public address, then reboot your OBi and retest. However, before trying the above, find out how to restore the modem to factory settings, in case the changes you make somehow prevent you from accessing the Net.
I can report that with my Obi202 I'm having the same problem, where maybe 20% of calls, everything works fine and then after several minutes of talking, the other person can't hear me any more but I can hear them.
Today we had one call where they called and couldn't hear us at all once we answered.
We're got to different GV lines on the 202 and it happens on both.
It seems worse since I moved the Obi behind/downstream from the router. I'm going to try it in front of the router and see if that makes a difference.
Add me to the list where receiving party does not hear, but I am able to hear them after calling them.
Setup is dialing from an Obi202 as a router connected directly to Comcast Cable Modem with sufficient b/w, the LAN port connected to wireless Cisco Valet Router; call is connected via the Obi network (i.e. to another Obi110 endpoint).
For me calls placed via GV (actually Simonics) works fine in both directions. I would figure no ports needed to be messed with since, Obi202 is first device on network before my wireless router. Not sure if I should change the Obi202 into Bridge mode, if that would help out - something to try.
Just recently changed devices to Obi202 from an Obi 100, which worked flawlessly before and I know recently a new f/w was released for the Obi 1x0 series. I am going to return to original setup with the Obi100 to see if I see the issue again.
Well it has to be some kind of setting on my Obi202 because it is definitely device specific, in my case, since after changing back to my Obi110, calls via the Obi network audio was bidirectional and worked perfectly.
Can't think of what it can be as of yet, very strange that it works with GV but not Obi network.
Any ideas??
Obi202:
HardwareVersion
1.3
SoftwareVersion
3.0.0 (Build: 3397)
This is crap
Same issue for me. I will be having a conversation and the other person will say "Your breaking up" which only a few seconds later is followed by "I can't hear you", "are you there", followed by them hanging up. I can hear them as clear as a bell with no choppiness or interruption, but they can't hear me. I had the cable company come out and look over my configuration, check the cable modem, everything looked good. I use Skype occasionally for overseas calls and do not experience outages. I'd sure like to fix this since I am using the phone partially for business in a home office, and this don't make me look good. I may be forced to go back to a standard old, reliable land line, but I hope not.
Configuration:
Ambit cable modem model: U10C018
Apple Airport Extreme direct wired to the Obi.
Average d/l speed: 27Mb/s
Average u/l speed: 5Mb/s
Hello. I have been searching the internet for this very problem. I call someone and we talk for about 3-5 minutes and they cannot hear me anymore so I hang up and call them back. The same thing that all of you are reporting. However, I am not an OBI customer. I use Teltub, GV, RCN (internet Provider) and a Linksys PAP2T-NA ATA device. I have changed routers 3 times and same problem. I temporarily discontinued GV; no different. I tried many different settings in Teltub and my adapter; same crap.
I'm posting here to let you know that this problem is not confined to OBI. Maybe it has something to do with the Linksys PAP2T-NA ATA device. Maybe Linksys is OBI's vendor for the Obi adapters and they use the PAP2T in an Obi box. I'm stumped like the rest of you. Thanks.
Quote from: dhfobi on April 14, 2012, 09:37:54 AM
Thanks for your dissertation as it is insightful and helpful.
You are welcome. If you and your friends need dissertation assistance, do not hesitate but contact us at theessayservice (https://theessayservice.org/).
It seems that you have been persistent in trying to find what is causing this. As a final test, you might consider signing up with a SP like voipms (or any other reliable/reputable high quality SP) on a pay as you go rate. For less than $5 for one month you will be able to know if GV is the culprit. You should be able to have an answer in the first day of use. I think there are even some SPs which provide a small credit to try them. I think that might be the only way that you will know for sure. Then you can decide what you need to do. I hope you report your findings here if you decide to go that route.
My Obi110/GV setup was working fine for more than a month. I then started having this problem. It happens intermittently so it it is very difficult to trouble shoot.
Drives my wife (and her sister who can't hear) nuts.
Reading this thread there appears to be allot of ideas but really no known user solution.
I'm wondering how prevalent is the problem. Have I just hit a bad stretch due to internet traffic or some such?
One alternative would be to abandon the free Google Voice and switch to another SIP. Is there a problem with that? Can the obi setup approach the quality of POTS .
Somewhat frustrated