1 edit | reply to VTBrendan
Re: No sound on most outbound calls - Viatalk = no help PM sent. I also (yesterday) sent a follow-up email to CS describing the symptoms again, voipdabbler's solution (disable STUN server), and requesting that they change this setting in my VT-provisioned PAP2T. So far the latter hasn't happened, because stun.vtnoc.net keeps getting re-enabled. 
Edit: forgot to mention my router. It's a D-link DGL-4300. I believe you've mentioned trouble with D-link routers. Worked fine with the old VT server setup.  |
|
1 edit | reply to VTBrendan
Is there a list of D-link routers that you are now having problems with since your 'upgrade'? It would be nice to know since I have one and have had nothing but problems with the ViaTalk service since I got a 'you've been upgraded message'. I have an open ticket that support has not updated since July 23rd. TRO-61122. Is there some setting to change in the router to get it to work? I find it ironic that before the upgrade I rarely had a problem but now it's been nothing but problems. |
|
|
|
| I just called home, was talking to the wife for about 2 minutes. Then I couldn't hear her, we were disconnected. She called me back and told me that when I was talking it went to a fast busy signal. What's up with that? |
|
dipswichPremium
join:2003-06-27
Raleigh, NC Reviews:
 ·ViaTalk
 ·RoadRunner Cable
 ·AT&T U-Verse
 ·Clear Wireless
| reply to VTBrendan
said by TheKrell:as per your suggestion in a newer thread, disabled STUN entirely. All problems were instantly resolved, and calls now complete faster too. said by VTBrendan:It seems almost counter-intuitive but if it works, it works. STUN does not work to traverse symmetric NAT routers. Enabling it behind a symmetric NAT router can easily break other methods which may be successful. The STUN algorithm provides the wrong answer and is a well known (and published) limitation of STUN and symmetric NAT. STUN is a only tool in the toolbox, and sometimes it's the wrong one.
The reason some routers (like the D-Link DI-series) are problems for ViaTalk are that they shipped in symmetric NAT mode, a very restrictive mode that makes it almost impossible to configure VoIP without manual port forwarding or proxying (the old servers). "Gaming mode" switches the D-Link routers to "full cone NAT" where STUN works for traversal.
The problem right now is that the frameworks (read up on ICE and rfc3489bis) to solve the various NAT types aren't official, and it will take some time before routers are upgraded or replaced to implement a new, complete standard. Until then, a solution such as the new ViaTalk architecture will require many users to go beyond "plug & play" to get their service to work.
ViaTalk is thinking ahead with the new server platform, but I really question the choice to go forward with converting everyone over so early in the game:
•ViaTalk assumes persons have access to the Internet gateway or to router administration. What if someone uses ViaTalk at work (where symmetric NAT is prevalent) or frequently moves a provisioned device to differently NATed networks?
•ViaTalk assumes people are willing to work to get the service back on track or don't mind unknowingly missing calls until they discover their service broke as a result of the change.
•ViaTalk dismisses the reason SPI and symmetric NAT routers exist-- security. Blindly instructing "turn off SPI" or "enable gaming mode" to get the service working without discussing the security implications, however minor, isn't very responsible.
•It isn't like the old servers can go away anytime soon (symmetric NAT routers and fax-to-email or call-recording subscribers can't move to new severs).
•Granted, many routers have some bad implementations of SPI and SIP ALG putting some of the blame on their manufacturers, I'd think that ViaTalk would want the service to work flawlessly for the most user setups, including some router brands with serious market share.
•If the new architecture is being deployed to address quality problems, then that indicates the old servers, still required for many, are having issues that aren't getting fixed. |
|
| reply to nitecourt
Phone was ringing. I answered. It sounded like a dial tone but a different pitch for about 2 seconds. (Not fax or modem.) Then fast busy signal. I had to call the caller back. |
|
