Can't talk to cell phones with 202

(1/3) > >>

ajaxmike:
If I connect the 202 directly to the internet modem, then all is good.  If I connect it to a port on the router, with nothing else connected (even wirelessly), calls with cell phones are broken up.  Router is Netgear WNDR3700, which is benchmarked as really fast.  I set the router QoS to give the MAC address of the 202 highest priority.

Rather than keep trying different routers, I wonder if I can just place the 202 in front of the router so that the voip traffic never even reaches the router.  If so how do I set this up?  Also, will the 202 slow down my network if it is used this way?
 

drgeoff:
Try setting the OBi to 100 Mbit/s full duplex.  http://www.obitalk.com/forum/index.php?topic=2642.msg17170#msg17170

Shale:

Yes, it should work. Yes it will slow things down. Part of that will be QOS, and part will be a longer path. Try it. The faster your network, the more significant the slowing will be.

Do as drgeoff  said.

In setting this up, you can either have the OBi in bridge mode, or you can have your router not issuing DHCP addresses. You can try both, but the simplest, at least initially, will be bridge mode on the OBi.

We need more reports on this. Take notes as you try configurations. Check http://www.obihai.com/OBiAdminGuide.htm, which says Instead of acting as a router, the OBi202/OBi302 can be set to work as a 3-port switch. One of the ports is internal and is used by the OBi202/OBi302 CPU only, while the two external ports (labelled as Internet and LAN) can be connected to other devices. This mode of operation is known as the bridge mode. In this mode, all the router features, such DHCP server, firewall and port forwarding, will not take effect. The QoS policy in this case is hardwired such that the native voice and related traffic will always have highest priority (this behavior is not configurable). Furthermore, accessing the OBi device management web pages from either of the two external ports is always allowed.

Does the term VLAN mean anything to you? That can a way of implementing QOS for some routers. I have only recently become aware, and my knowledge is limited. So I cannot tell you how you could use it, but it seems intriguing.

Also see https://www.google.com/#q=site:obitalk.com+%22bridge+mode%22+qos I cannot try it, because my modem is integral with my router, and there is no bridge mode available from it.

ajaxmike:
Quote from: drgeoff on October 13, 2013, 08:28:59 am

Try setting the OBi to 100 Mbit/s full duplex.  http://www.obitalk.com/forum/index.php?topic=2642.msg17170#msg17170


Thanks for your suggestion. I tried it, but no luck. A cell phone conversation was perhaps better (or maybe just my imagination), but still unacceptable.  When connected directly to a cable modem the voice quality of the OBi202 is pristine, even with cell phones.

I bought the OBi to replace a Linksys ATA which had the same problem, so the problem is clearly the router.  It's a gigabit router and really fast for everything else, it just doesn't seem to like cell phones on voip.

ajaxmike:
Here is an update (spent all day working on this).

I was unable to get bridge mode working, so I used router mode.  I was able to get the following config to work:

       Cable modem >> OBi202 >> Netgear WNDR3700 >> LAN

The OBi default LAN is 192.168.10.xxx.  The Netgear reset itself to 10.0.0.1, which worked, but my LAN was already set for 192.168.1.xxx.  The Netgear would not accept 192.168.1.1, so I changed the OBi to 10.0.0.1 and returned the Netgear to 192.168.1.1.  Everything works.

I did an internet speed test and found the speed to be about 1/3 (10Mbs) of what I usually see (30Mbps),  I made sure that the port speed was set to 100Mbps (it was/is) but no improvement. Interestng that this is an undocumented option. It is Sunday evening on a holiday weekend, so perhaps traffic is a bit heavier than usual, so i will test again mid week.

My nagging questions are:

1) Is the LAN operating at 1GB/s in this config?
2) Is the WAN limited to 10Mb/s by the OBi?

Navigation

[0] Message Index

[#] Next page