Obi100 not working right - newbie needs help.
lhm.:
Find that SIP ALG setting and disable it.
Jackson:
Quote from: wilbur on December 19, 2014, 04:12:39 pm
thanks, Jackson, for the tip.
I was really hoping someone in this forum could help.
Usually many would chime in.
Try this:
Quote
Switching your OBi's Ethernet ports to 100 mb/s full duplex:
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
How to verify the current setting of the OBi's ethernet ports 10 or 100 mb/s full duplex:
1. Dial *** 0
2. Enter option 27 and press #
At this point the OBiMAN will read back the current value:
0= 10 mb/s
1= 100 mb/s
Maybe try opening up some ports in your router:
Quote
Allow Outgoing:
TCP Ports: 6800, 5222, 5223
UDP Ports: 5060, 5061, 10000 to 11000, 16600 to 16998, 19305
Allow Incoming on UDP Port: 10000
zorlac:
I have Comcast throttling my modem to only 3Mb cause I'm cheap & VOIP works fine.
A 100Mb connection from an obi box to the router is WAY overkill IMO.
This is a repost from SteveInWA.
You can troubleshoot this by using the VoIP simulator test on this website.
Select your location and use the G.711 codec, which is the most demanding of a quality internet connection. The test will simulate an actual end-to-end VoIP conversation, and will show you a MOS score that reflects factors such as jitter, latency and drop-outs, in addition to raw speed. This is the only valid test of an internet connection's suitability for VoIP -- sites like speedtest.net can't do this. If your score is below 4.0, you will need to beat on your internet provider to fix their crappy service. If your score is 4.0 or higher, and you continue to have problems, there is a small chance you have defective network hardware or cables, but more likely, it's PP's fault.
SteveInWA:
Quote from: Jackson on December 19, 2014, 05:59:36 pm
Quote from: wilbur on December 19, 2014, 04:12:39 pm
thanks, Jackson, for the tip.
I was really hoping someone in this forum could help.
Usually many would chime in.
These things start out sounding so simple, so "vanilla"...and then I read:
Quote
I'm using a Belkin router with Tomato firmware
I have rarely messed with the Tomato settings, and it has been working fine for 2+ years.
Even though I managed to install the firmware on the router I'm not very network savvy, so any help you could give me would really be appreciated.
and, then I picture 5 pages of network troubleshooting posts.
RE: the 100Mbps full duplex setting: It's not that 10Mbps isn't sufficient under ordinary circumstances (sorry for the double negative). I haven't had to mess with it personally, but I believe it dates back some years ago to a firmware bug that was causing call quality issues if the box wasn't forced to full-duplex via this setting. I dunno if it's relevant any more.
Mango:
Quote from: lhm. on December 19, 2014, 04:19:28 pm
Find that SIP ALG setting and disable it.
He's using Google Voice, which uses XMPP, not SIP.
Quote from: Jackson on December 19, 2014, 05:59:36 pm
Maybe try opening up some ports in your router:
He has a Tomato router, so all ports are open by default. Also, blocked ports would typically manifest as one-way or no audio, not garbled audio. If some of the audio arrives, then the port is open.
To Wilbur:
Poor outgoing audio quality on both incoming and outgoing calls is 99% of the time due to some other device on your LAN using too much upload bandwidth. You can test for this by disabling wireless on your router, and unplugging all wired devices (except your OBi) and making a test call. If the symptoms do not appear, the problem can be solved permanently by setting up QoS.
If your NetTalk Duo and the Echo test always work properly, it is possible that you're the 1%. By any chance were all the test calls you made in the same area? If you make a long distance call, does the problem still occur? It is theoretically possible that Google Voice's routing to your town has problems, however the odds of this happening are fairly remote.
Either the problem will go away with no other devices connected to the internet, OR the VoIP simulator test will show poor results, OR the problem will not appear when you make a long distance call. I can't think of anything else that would cause these symptoms.
Navigation
[0] Message Index
[#] Next page
[*] Previous page