I'm happy to report that this issue was finally resolved. Although the problem may have been somewhat tricky, Voipo support saw it through to the end and solved the "no audio" issue I was having when calling Voipo to Voipo. Many thanks.
RA
I'm happy to report that this issue was finally resolved. Although the problem may have been somewhat tricky, Voipo support saw it through to the end and solved the "no audio" issue I was having when calling Voipo to Voipo. Many thanks.
RA
I asked that same question and was told that there were basically NAT issues but the ultimate solution was to use stun. It wa a weird probelm because it only was an issue when calling certain numbers and those numbers happened to be running GrandStreams and the issue only started when I switched from a GrandStream to a pap2t. It took them a while to figure it out so it would be interesting if someone could give some detailed info on what exactly it was and how they fixed it.
RA
Not in defense of the support group, but I think the issues are far greater than simply telling you what they found.
If you consider that they are handling 1000s of customers, many with all kinds of convoluted setups--while going through a rough period with the adapters, it's a wonder they keep everything going as well as they do.
They are coming from behind, since the original thrust was to use the 502s and require them to be placed before the routers, if any, or they would not be able to offer direct support.
Now with the PAP2Ts, you virtually need a router, and that now presents a whole different path for support.
They have their hands full, but in time, I think they may be able to draw a breath and have some standard(an oxymoron)procedures and scripts to take care of most problems quickly.
Although I have a wireless router because of my needs, I suppose I have been quite lucky from the beta days until now, as my service is excellent in every respect...and my WAF is the best it has been in 4 years of VOIP.![]()
Update: This issue is back again and not sure why or what else to do. All ports that I have been asked to forward are forwarded, and apparently, we are still on stun, but the "no audio" business is back when calling a certain number. It is a Linksys pap2t on this end behind a Linksys wrt310n running ddwrt, and a GrandStream on the other end also behind a router, but can't recall brand and model. Note that I have qos enabled via the mac address of the pap2t, but I don't think that should interfear.
RA
Bookmarks