So I have three OBI202 ATAs doing nothing, and one running on a second line. The reason is I have had too many problems with them. Having problems with an OBI seems to be a very rare occurrence so, I figured I would post to see if someone might know what is going wrong, and how I can make them work for me. I could put at least two into use right away if they worked correctly. Using other VoIP products from Grandstream work flawlessly as far as call quality goes (DP750 & HT802). The OBI firmware level is recent but I don’t have access to it right now (because I did a firmware update on the router last night and it rebooted, now it has no IP LOL).
First, I want to say that my internet connection is consistently stable and low latency. My MOS score is almost always 4.4 and ping time to the ISP internet gateway is about 11 ms. There is no SIP ALG in use and I never have SIP or RTP connection tracking issues in the firewall. The VoIP RTP proxies for TekTalk and voip.ms are also physically very close. The devices are behind the firewall and use the WAN port for connectivity to the LAN.
TekTalk ~11ms (Toronto)
Voip.ms ~11ms (Toronto)
Anveo ~19ms (Montreal)
Anveo Direct (Variable, direct RTP media)
The issues:
Summary:
- Looses IP address
- Echo Suppression
- Echo bubble (I really don’t know what else to call this LOL)
#1 – Looses IP address
If I reboot my router, the OBI states via the phone IVR that it doesn’t have an IP address. The IP can be statically or dynamically configured, it makes no difference. It can be directly connected to the router or have a switch in between. The speed between the OBI and what it is connected to is negotiated correctly all the way through from the ATA to the bridged DSL modem. The Ethernet cables have been changed and this can be reproduced on three different OBI202s and three routers (routers are all Mikrotik). The firmware has been upgraded many times over the last two years and made no difference. The only way to get it back on the network that I have found, is to power cycle the OBI. For reference the router is a Mikrotik RB850Gx2 and I have also used a Mikrotik RB450G. This issue has been mentioned in the OBI forums by others. The exact IVR message is "Network status. IP address not available. Reason 00"
#2 - Echo suppression
The OBI will use very aggressive echo suppression (not talking about cancellation). The person on the other end of the call will be talking and can't hear the person on the FXS port until they have stopped talking. If the person on the FXS port wants to be heard they can speak very loudly but then can't hear the person on the other end of the call as it is now suppressing them. The call essentially becomes simplex. The RTP streams are still going in both directs its just aggressive attenuation of the audio. This doesn’t happen on a severe level all the time but you can hear it attenuating most of the time on and off throughout the call, even VoIP OBI ATA to VoIP native DECT with only Asterisk in between. (It also does it OBI to PSTN.) Adjusting the gains on the ATA provided some relief but if one end of the call the other speaks too loudly it goes into "simplex mode", otherwise it does it at less aggressive level.
#3 - Echo bubble
I really don't know what to call this. Sometimes we can be on the phone and we will get a loud delayed echo for a second or so. It doesn’t happen very often but it's disruptive. It can happen more than once in a call but, it usually happens at the beginning of the phone call and may happen later as well. I attribute the initial “echo bubble” to the echo canceller training it's self up.
So that’s it. I tried to be as detailed as possible. Hopefully something sticks out.
↧