VOIPo EAST still being routed to CENTRAL?

[sr98user]

SIP server just sets up the call. The voice traffic actually goes through the media gateway which could be anywhere in the country. If the voice quality is not good (echo, muddled, etc), its not due to the SIP server. Unless your voice traffic is proxied through the SIP server, which is not the case for most of the users.

[Russell]

The voice traffic actually goes through the media gateway which could be anywhere in the country.

Yes, those "media gateway" which need 60K+ ports to be forwarded :-).

[MisterEd]

Yes, those "media gateway" which need 60K+ ports to be forwarded :-).

I just turned off all my VOIPo port forwarding to see what happens. So far it's been solid and I've had no loss of audio on any calls. I think the "fix" of my "no audio" problems were due to my Fios Actiontec router and not the port forwarding. I replaced the router with a Buffalo w/DD-WRT and it's been good so far.

[MisterEd]

SIP server just sets up the call. The voice traffic actually goes through the media gateway which could be anywhere in the country. If the voice quality is not good (echo, muddled, etc), its not due to the SIP server. Unless your voice traffic is proxied through the SIP server, which is not the case for most of the users.

Then why are they interested in ping times, trace routes and latency to the assigned server when there is a problem? The first thing that was done when I was having problems back in the beginning was to move me to the EAST server instead of CENTRAL because of better pings & traceroutes. My orignal problems were echos, delays and lousy voice quality which are the most common voip problems. I have a Fios 25/15 Mbit connection so it wasn't my bandwidth.

[JimDog]

Then why are they interested in ping times, trace routes and latency to the assigned server when there is a problem?

Because the SIP servers set up the call between your adapter and the media gateway, too much latency could cause failed calls if something times out. It's also a good indicator of ISP problems in general.

[MisterEd]

Because the SIP servers set up the call between your adapter and the media gateway, too much latency could cause failed calls if something times out. It's also a good indicator of ISP problems in general.

Maybe the most of the primary media gateways for EAST are clustered closer to the EAST servers and CENTRAL to the CENTRAL servers etc. I've never had failed calls, only audio issues, and was told by support that moving me to EAST servers should help since ping and traceroute were much better. Vonage did the same thing ... when audio was bad they would switch you to a different server.

[sr98user]

Maybe the most of the primary media gateways for EAST are clustered closer to the EAST servers and CENTRAL to the CENTRAL servers etc. I've never had failed calls, only audio issues, and was told by support that moving me to EAST servers should help since ping and traceroute were much better. Vonage did the same thing ... when audio was bad they would switch you to a different server.

I am not sure why they would do that. My media gateway does not change when my SIP server changes. I think the media gateway is selected based on the area code and exchange. Unless your audio is proxied through the SIP Server.

[tritch]

I am not sure why they would do that. My media gateway does not change when my SIP server changes. I think the media gateway is selected based on the area code and exchange. Unless your audio is proxied through the SIP Server.

Probably because the East SIP servers are connected on a private network to Dallas.

East is a little different since it connects to Dallas via a private network so it's rock solid in that sense.

I would think those having a more direct route (less hops/latency) to the SIP Servers in East would be preferred and cause less problems in general as opposed to connecting to the SIP servers at Central (Dallas) over the public network.