Way too many audio dropouts?

**VOIPoTim** · 04-08-2009 01:57 PM

Hi Rick,

I'm told that your STUN server was still set to The Planet in Dallas which we've been having major latency issues with this past week. More than likely this was the cause.

We've moved your STUN server to the Washington DC node as well.

Let us know if this clears things up for you.

**burris** · 04-08-2009 03:27 PM

Originally Posted by VOIPoTim

Hi Rick,

I'm told that your STUN server was still set to The Planet in Dallas which we've been having major latency issues with this past week. More than likely this was the cause.

We've moved your STUN server to the Washington DC node as well.

Let us know if this clears things up for you.

I see on the provisioned config that both of mine are still going to 74.52.58.50

What is the IP for the DC Stun server or are you going to push it out?

However, I haven't had any problems at all.

**VOIPoTim** · 04-08-2009 03:45 PM

Originally Posted by burris

I see on the provisioned config that both of mine are still going to 74.52.58.50

What is the IP for the DC Stun server or are you going to push it out?

However, I haven't had any problems at all.

We'll be pushing it out soon, but basically all the SIP servers will also be running STUN as well so the user will be using the one they're registered to. That way it eliminates any external dependencies.

You can use central01.voipwelcome.com or east01.voipwelcome.com.

For provisioned users, this will be pushed out soon.

**burris** · 04-08-2009 04:11 PM

I have both of my boxes provisioned and they work so well, I'm not fooling with them..

**ralfaro** · 04-08-2009 06:40 PM

Originally Posted by VOIPoTim

Hi Rick,

I'm told that your STUN server was still set to The Planet in Dallas which we've been having major latency issues with this past week. More than likely this was the cause.

We've moved your STUN server to the Washington DC node as well.

Let us know if this clears things up for you.

It sure looks like that did the trick. I have had several long conversations since Brandon asked me to power cycle with not single dropout. In fact, I think the audio is actually a little better than what it was especially with regard to being almost perfectly full duplex and I don't think it is my imagination either. Thanks much for the quick fix.

RA

**VOIPoTim** · 04-08-2009 06:42 PM

Originally Posted by ralfaro

It sure looks like that did the trick. I have had several long conversations since Brandon asked me to power cycle with not single dropout. In fact, I think the audio is actually a little better than what it was especially with regard to being almost perfectly full duplex and I don't think it is my imagination either. Thanks much for the quick fix.

RA

Yeah I'm not surprised. The new network should deliver much better quality and stability overall.

**orum** · 04-08-2009 07:08 PM

Would this cause incoming calls to go "nowhere"? I am having reports from family and friends that they call our number and get no ringing or voicemail.

Dan

**VOIPoTim** · 04-08-2009 07:14 PM

Originally Posted by orum

Would this cause incoming calls to go "nowhere"? I am having reports from family and friends that they call our number and get no ringing or voicemail.

Dan

Go ahead and open a support ticket if you see this and we can check it out for you.

**ralfaro** · 04-18-2009 12:15 PM

Update as of Friday, 04/17/09:
Looks like something broke again as the audio dropouts are back again, along with another issue that was previously fixed as well. Ticket MAX-542997. No response on this as of yet. Everything was working so well too, so not sure what might have happened.

RA