What causes an echo on VoIP?
96410
So many things can cause echo that there is no magic bullet.  Lets try some basics.  Get rid of the cordless for a little bit and put an old fashioned,wired decent quality handset in its place. Is the echo constant or intermittent ?  Some people have it while others don't?  Always the same people?  Does it happen more during peak internet usage times?  Do you notice latency (longer delays in your voice getting to them and visa versa) along with the echo?  Feed me more info and I will try and help.\n\n\nFeb 22 4:43 PM -  How much delay in the echo? This would give clues as to where the echo is originating. I am having a hard time coming up with a cause that would be within your control.  The speed question the provider asked you is a red herring.  The fattest voice codec is only 64kbs so the lowest upload speed would suffice. Is the ATA attached to a router or straight to the cable modem?  Did you change out the phone cord when you changed the phones out?\n\nFeb 23 702 PM  -  That is probably the culprit.  (I hope) The long rj11 cord combined with its poor condition (if I am right) would cause an impedance mismatch.  Normal impedance in the US is 600 ohms.  Everything is tuned to have all sounds come together when the system is at 600 ohms.  When it is off a little, some of the callers voice gets reflected back up the line.  The echo would be about 3/4 to 1 second after the caller speaks for this to have been the culprit. I am keeping my fingers crossed for you because if it still persists you will have to fight with the provider to get them to fix their problem.  If you need to pursue this further I can set you up with an account and a test number to prove that it is not your internet connection.\n\n  email voip AT rapheal DOT no-ip DOT com\n\nFeb 24 8:00 PM Still have my fingers crossed for you
475134
sounds like a virus...
460321
Sounds like an ISP or local computer problem. None of the rest of us seem to be having any trouble or the screams would be all over the net. This is even still in Beta and it works great.
550294
Description\nThe /usr/sbin/ping command sends an Internet Control Message Protocol (ICMP) ECHO_REQUEST to obtain an ICMP ECHO_RESPONSE from a host or gateway. The ping command is useful for:\n\nDetermining the status of the network and various foreign hosts. \nTracking and isolating hardware and software problems. \nTesting, measuring, and managing networks.\nIf the host is operational and on the network, it responds to the echo. Each echo request contains an Internet Protocol (IP) and ICMP header, followed by a timeval structure, and enough bytes to fill out the packet. The default is to continuously send echo requests until an Interrupt is received (Ctrl-C).\n\nThe ping command sends one datagram per second and prints one line of output for every response received. The ping command calculates round-trip times and packet loss statistics, and displays a brief summary on completion. The ping command completes when the program times out or on receipt of a SIGINT signal. The Host parameter is either a valid host name or Internet address.\n\nBy default, the ping command will continue to send echo requests to the display until an Interrupt is received (Ctrl-C). The Interrupt key can be changed by using the stty command.\n\nBecause of the load that continuous echo requests can place on the system, repeated requests should be used primarily for problem isolation.\n\nFlags\n\n-c Count Specifies the number of echo requests, as indicated by the Count variable, to be sent (and received). \n-w timeout This option works only with the -c option. It causes ping to wait for a maximum of 'timeout' seconds for a reply (after sending the last packet). \n-d Starts socket-level debugging. \n-D This option causes a hex dump to standard output of ICMP ECHO_REPLY packets. \n-f Specifies flood-ping option. The -f flag "floods" or outputs packets as fast as they come back or one hundred times per second, whichever is more. For every ECHO_REQUEST sent, a . (period) is printed, while for every ECHO_REPLY received, a backspace is printed. This provides a rapid display of how many packets are being dropped. Only the root user may use this option. \n\nNote: This can be very hard on a network and should be used with caution. Flood pinging is only permitted by the root user. The -f flag is incompatible with the -i Wait flag. \n-I a.b.c.d Specifies that the interface specified by a.b.c.d is to be used for outgoing IPv4 multicasts. The -I flag is an uppercase i. \n-o interface Specifies that interface is to be used for outgoing IPv6 multicasts. The interface is specified in the form 'en0', 'tr0' etc. \n-i Wait Waits the number of seconds specified by the Wait variable between the sending of each packet. The default is to wait for one second between each packet. This option is incompatible with the -f flag. \n-L Disables local loopback for multicast pings. \n-l Preload Sends the number of packets specified by the Preload variable as fast as possible before falling into normal mode of behavior (one per second). The -l flag is a lowercase l. \n-n Specifies numeric output only. No attempt is made to look up symbolic names for host addresses. \n-p Pattern Specifies up to 16 'pad' bytes to fill out the packet you send. This is useful for diagnosing data-dependent problems in a network. For example, -p ff fills the packet with all 1's. \n-q Specifies quiet output. Nothing is displayed except the summary lines at startup time and when finished. \n-r Bypasses the routing tables and sends directly to a host on an attached network. If the Host is not on a directly connected network, the ping command generates an error message. This option can be used to ping a local host through an interface that no longer has a route through it. \n-R Specifies record route option. The -R flag includes the RECORD_ROUTE option in the ECHO_REQUEST packet and displays the route buffer on returned packets. \n\nNote: The IP header is only large eno
914265
Difficult to give any advice really as you say you have tried everything. If the audio is OK in  other use then we can presume the settings are Fine. It "could" be a simple bad connection, does the person you are talking to have the same problem?, is it always distorted no matter who is on line?  All I can suggest is to look at the FAQ's on MSN site, see if anyone else has the same problem. It could be your PC/Video Card is just not up to spec to deal with video calls. Try it without video, see if that helps and close any other programmes running in the background. Best of Luck
401205
i had the same problem when i first got Vonage. i discovered that my cable was going out while i was at work, and that lost the connection with vonage. has your cable gone down and come back up without you knowing?
518202
There is a great possibility that your Internet connection is slow, if you are using a dial up connection this problem will be often. try to restore ur Audio settings and try connecting ur mic again.\nGood luck.
62569
you might try resetting it through the yahoo messenger audio wizard. Thats the easiest way to know if your sound card is working properly without doing a bunch of tech stuff.
539213
IMO it's the DNS server [which translates names into ip numbers]. Call your ISP - it may be their problem, not yours.
1067227
run a splicer from the box outside to the phone router. If they are on the same line, the signal gets weakened.We had the same problem and giving them each thier own dedicated line fixed the issue
669435
It could be a flakey modem board, or it could be your telephone connection that is flakey.  If you hear lots of crackles and pops when you use the telephone, then it would be your connection.  If you complain, the phone company may be able to switch you to another set of wires to clean up your connection.\n\nIf your telephone connection is good, then tell your DSL provider about your problem to see if you can swap for another DSL modem.
378625
If the timing out is casued by the phone ringing, there's a device you can get, (not sure where but I saw one, once) that allows phones to work with out interupting internet connections. If there other reasons for it, you might want to talk to an expert, such as the Geek Squad at Best Buy.
291038
voip is voice over internet protocol\n\nwhat are you talking about?
472991
ip address is not the issue.  You may try, at a command prompt,type " ipconfig /flushdns ".   It could be  a dns problem, OR some ISPs actually block the voip protocol.  check with your isp.  It is not legal in the U.S> to do so, but some do anyway.
597144
remove the base boost on microphone setting.\ni use it and don't get errors or autotypes.\nyou're broadband conntection doen't matter it's a software issue. did you go to the microphone voice training and traing your speller? go and train your mic.\nfrom what i see you may have the smart keys enabled...\nalso make sure you updated your software. if its pirated. you'll have similar glitches that are unfixible cause they are trojans.
3513
VoIP is made to be used with high speed internet.  you will never get good results on dial-up
618468
If the problem is not resolved even after restarting the computer, try reinstalling your sound card drivers.Then run the Yahoo! Audio Setup Wizard.