Losing audio on incoming calls
RonR:
Quote from: M105 on April 30, 2011, 06:24:47 pm
Yes I ran the Obi110 with Gizmo5 SIP for about 3 weeks before they went away. No problems.
Unfortunately, that doesn't vindicate your router. There's a lot of different server software packages out there (Asterisk, OpenSER, etc.), a lot of different ways to configure each, and a lot of different clients (PAP2's, OBi's, etc.). Different NAT implementations (there's several ways to do it) in different routers can behave well with most of the combinations but then fail with a particular one. It's a bit of a crap shoot. Using STUN servers and port forwarding can often help, but some still fail in certain circumstances.
M105:
Not trying to "vindicate" the router Ron. The man asked me a question and I answered it. I am not ready to throw the router away either. It is a very nice piece of equipment with a 400mw wireless radio. If there is a way to solve the issue with router settings then that is what I seek. It will save me and about a million other AT&T customers from having to ditch an excellent piece of hardware.
Your "solution" is noted: Replace the router and crap shoot a new model. I got it, okay? It may be my only choice but I don't give up that easily.
RonR:
Sorry, M105, I wasn't trying to push you in any direction and didn't mean any offense. I've had a good bit of experience with router issues and VoIP over the past several years and was only meaning to emphasize "It's a mine-field out there!" in this area.
M105:
Solved:
Using the Netopia 3347-02-1006 (AT&T Bellsouth) router with the OBi100/110. The Obi seems to be sensitive to the ethernet port switch on this and other routers. It will randomly lose the incoming audio stream and sometimes drop calls completely. This is more of a switch issue than a routing issue. This Netopia router has the capability to isolate a single ethernet port and "wire" it directly to the WAN port. Although this is done with router settings it essentially plugs the OBi directly into the DSL modem.
------------
In the expert/configure/advanced settings, set up two virtual LANS (VLANS). Both will be "port" type, not global.
Name the first VLAN "MAIN" and include ethernet ports 1,2, and 3 but not 4. Also include ssid and uplink. Leave the priority and promote check boxes empty.
Name the second VLAN "Ethernet_4" and include only ethernet port 4 and uplink. Leave the priority and promote check boxes empty.
Be sure to enable VLANS and individually enable both VLANS and save/reboot. Plug the ethernet cable for the Obi into ethernet port #4 on the router.
This router requires no other setting changes or port forwarding. The default firewall and other settings work fine. The only downside to this solution is that it isolates the Obi from the rest of the network. When it is plugged into port #4 you cannot access the Obi's web interface from other computers on the "main" network. The Obi can however still be configured through the Obihai portal on the web. It can also be accessed locally by temporarily plugging it into one of the other ethernet ports.
------------
This is posted with the hope that it will help others with similar issues. My research indicates that the Obi is very sensitive to ethernet port timings when operating in Google Voice mode. I would urge the developers to look into this issue and perhaps adjust the firmware to make the unit more tolerant.
RonR:
Quote from: M105 on May 03, 2011, 08:16:57 am
This is more of a switch issue than a routing issue. This Netopia router has the capability to isolate a single ethernet port and "wire" it directly to the WAN port. Although this is done with router settings it essentially plugs the OBi directly into the DSL modem.
Haven't you simply bypassed the router/firewall on Ethernet port 4? Nothing in the Ethernet port has changed. You're simply feeding port 4 from the input to the router/firewall (the modem) rather than the output of the router/firewall. In my mind, this is a confirmation that the router/firewall is the culprit.
Navigation
[0] Message Index
[#] Next page
[*] Previous page