dslreports logo
    All Forums Hot Topics Gallery


how-to block ads

Search Topic:
share rss forum feed


reply to idbit

Re: Choppy sound quality. Connecting IP phone directly to modem.

I wanted to update this old thread. I had a really hard time getting my computer to connect to the internet when feeding off the Yealink's built-in router. After trying a lot of different things, I finally solved it.

The problem was with one of the Yealink's default settings. In the network settings for the router, you can set the beginning and ending IP range for the PC connection. The default setting for beginning IP was: So the computer took that IP: The problem is that is also the IP address of the router itself, so they conflict. I had seen that early on and thought that was okay. I thought the two IP's were actually supposed to match. Eventually, somebody set me straight. So in the Yealink's network settings, I changed the beginning IP for the PC connection to: The computer then took on IP and everything was fine after that.

Maybe there was something I did wrong that caused the Yealink router to assign its own IP as the beginning IP for the PC connection. Maybe not. But if anybody is having problems connecting to the internet using the Yealink router, this might be the problem.


Saint-Hubert, QC

How about the choppy calls, do you still have this issue?



said by Dan_voip:

How about the choppy calls, do you still have this issue?

The phone is working great now. It's connected straight to the cable modem. Nothing else is using the network besides the phone and the pc connected to its lan port. This is my first VOIP experience. So I'm loving it. Everything is so instantaneous. The phone is great. The sound quality is great. The configuration possibilities are crazy.

I'm also really impressed with how quick the phone is to reboot whenever I change the network setup. At first, I was going back and forth between connecting the Yealink directly to modem and connecting the Yealink to my old router. Every time I would do that, the IP assigned to the phone would change. So I would have to reboot the phone. All the times I rebooted, I never had a problem. It would start up, accept its new IP and network config, and just work, all in a matter of a few seconds. I must have gone through that drill 30 or 40 times and the Yealink never blinked. I don't know if that's typical for SIP phones. But from my experience with anything related to networks, things usually aren't that easy.