Ok, been running my Obi202 with CAT5 for Internet connectivity and MUCH fewer blanking issues. All week I had 2 reported incidents of voice "blanking" and both were brief in length of time (less than 2 seconds). On the down side, I found my wife using her cell phone at her desk where she usually uses the landline. So, not sure she used the phone as much as past weeks.
Great! Right? Well, this week, I also had 2 incidents where calls were not working either in or out of my home number (this Obi202). The first time a reboot fixed the issue. The second time I was writing up a ticket to submit to Obihai support, and the problem cleared up on it's own.
The 2nd incident seems like it might have been a GV issue. But, the 1st one seemed like a problem with my device since the reboot fixed it.
I also had one other incident where my wife says she called someone and the voice quality was horrible. It was so choppy from both ends that she couldn't communicate at all and just hung up. She rebooted the Obi202 and things were all better after that.
So, I've created a script to reboot my Obi202 each morning at 4:30am. I'm hoping that might help to resolve any issues where I find out later that things haven't been working all day and a reboot fixes the problem.
From a statistics point of view, I am seeing very few packet drops. There have been a couple. But, they happen like at most 1 per call. And, have seen less than 5 or so for the week. However, I do see packet underruns. The numbers are a lot higher for them. And, when one of the "blanking" events was reported, the only number that increased was underruns.
I very nice feature would be to keep the "Call Status" final stats for each call. I wouldn't think it would be hard to modify the "Call History" to show those stats if the final stats snapshot were kept for each call. This would help to debug what things went wrong when a problem occurs. My wife can usually tell me who she was talking to when "things went wrong".
Regards,
sjmyst