VOIPo server change?

[burris]

While you may find it disappointing, I think the point Tim is trying to make here is that the ideal VoIP service will make the changes in the background without the customer's knowledge, resulting in always-optimal service, minimal downtime, etc. One of the common complaints about ViaTalk's service (at least 1-2years ago) was the 'which server is working best right now' game. When I had CallVantage, I never knew how many servers they ever had or if the server handling my 'line' ever changed--the address my device connected to was hidden in the 'administration portal', and there was never an option in the control panel to view or change it. Service was nearly flawless. IMO, this is a good move, and should be followed by removal of any reference to 'which' server one is connected to from the vPanel. After all, one should only need to know whether or not they are connected.

I totally agree. Removing the BYODers from the equation, all the rest should remain provisioned and VOIPo should have ultimate control with regards to the connectivity. I never understood the reasons for Tim to offer so many tweaks that might affect a proper connection.
I have mentioned many times over the years, that those few providers who had in-house control of the connection parameters, almost never had the problems of those that went crazy allowing the users to run amok.
If I remember, Tim wanted it to be this way and I hope he returns to making it so..
I think VOIPo should remain a 100% provisioned service and maybe risk losing a few customers who will go and screw up some other network in their quest for their Holy Grail of VOIP.

[fisamo]

... a few customers who will go and screw up some other network in their quest for their Holy Grail of VOIP.

Hey! I resemble that remark!

[KenH]

I still would like an answer from VOIPo support or management. Is the Proxy setting on BYOD devices being ignored?

[VOIPoBrandon]

I still would like an answer from VOIPo support or management. Is the Proxy setting on BYOD devices being ignored?

This is correct, because you are setting the specific proxy you are connecting to which is sip-byod.voipwelcome.com (regardless) of what your proxy setting is set to, unless you are one of the VOIP old timers.

This is simply a registrar server however which is just a server that maintains your registration state, there is a lot more that goes into the infrastructure however as far as call termination and origination.

Hopefully this gives you a bit more clarification.

Thanks and have a great weekend!

[KenH]

This is correct, because you are setting the specific proxy you are connecting to which is sip-byod.voipwelcome.com (regardless) of what your proxy setting is set to, unless you are one of the VOIP old timers.

This is simply a registrar server however which is just a server that maintains your registration state, there is a lot more that goes into the infrastructure however as far as call termination and origination.

Hopefully this gives you a bit more clarification.

Thanks and have a great weekend!

Brandon,

I guess I am one of the "old timers"

Perhaps I should have been more explicit. I have "sip-east01.voipwelcome.com" set as proxy on my ATA yet vPanel indicates that I'm connected to your central server.

Thanks.

[voipinit]

^ x2

Indicating central, set to east, I am a grandfathered BYOD'er.

[VOIPoTim]

I still would like an answer from VOIPo support or management. Is the Proxy setting on BYOD devices being ignored?

No not for grandfathered BYOD users.

You can verify with a traceroute.

I'm not 100% sure but as far as the display in vPanel I believe it just looks at the connection anda matches up the hostname so if the hostname is not the exact ones we're using in provisioning, it'll how the default (Central). We update DNS for old hostnames in case anyone is using them even after we stop using them provisioning wise so if it doesn't recognize an old one it'll display incorrectly.

[chpalmer]

C:\>tracert 67.228.77.18

Tracing route to sip-byod.voipwelcome.com [67.228.77.18]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 172.31.125.1
2 13 ms 17 ms 10 ms 24.113.35.1
3 11 ms 12 ms 14 ms 24-113-127-41.wavecable.com [24.113.127.41]
4 13 ms 12 ms 11 ms 64.146.249.93
5 13 ms 15 ms 13 ms 66.119.192.209
6 14 ms 21 ms 15 ms te1-3.cer01.seattle-datacenter.com [206.81.80.140]
7 84 ms 81 ms 85 ms te2-3.cer01.wdc01.washingtondc-datacenter.com [67.228.118.238]
8 115 ms 115 ms 116 ms te9-6.dar01.dal01.dallas-datacenter.com [208.43.118.193]
9 127 ms 115 ms 118 ms po1.fcr04.dal01.dallas-datacenter.com [66.228.118.214]
10 121 ms 115 ms 116 ms sip-byod.voipwelcome.com [67.228.77.18]

Trace complete.

C:>tracert west01.voipwelcome.com

Tracing route to west01.voipwelcome.com [174.37.45.134]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 172.31.125.1
2 15 ms 12 ms 14 ms 24.113.35.1
3 11 ms 11 ms 11 ms 24-113-127-41.wavecable.com [24.113.127.41]
4 16 ms 12 ms 13 ms wavebroadband-gw.g11-0.oly-cor0.noanet.net [64.146.232.253]
5 15 ms 13 ms 13 ms srp3-0.wtn-cor0.noanet.net [66.119.192.25]
6 213 ms * 12 ms te1-3.cer01.seattle-datacenter.com [206.81.80.140]
7 90 ms 82 ms 82 ms te2-3.cer01.wdc01.washingtondc-datacenter.com [67.228.118.238]
8 115 ms 115 ms 117 ms te9-6.dar01.dal01.dallas-datacenter.com [208.43.118.193]
9 136 ms 119 ms 117 ms po1.fcr04.dal01.dallas-datacenter.com [66.228.118.214]
10 117 ms 117 ms 115 ms sip-central01.voipwelcome.com [174.37.45.134]

Trace complete.

C:\>tracert sip-east01.voipwelcome.com

Tracing route to sip-east01.voipwelcome.com [208.43.68.151]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 172.31.125.1
2 11 ms 10 ms 11 ms 24.113.35.1
3 15 ms 9 ms 11 ms 24-113-127-41.wavecable.com [24.113.127.41]
4 13 ms 15 ms 14 ms ip-64-184-129-237.noanet.net [64.184.129.237]
5 17 ms 12 ms 13 ms te1-3.cer01.seattle-datacenter.com [206.81.80.140]
6 81 ms 81 ms 93 ms te2-3.cer01.wdc01.washingtondc-datacenter.com [67.228.118.238]
7 86 ms 81 ms 81 ms po1.fcr01.wdc01.washingtondc-datacenter.com [208.43.118.134]
8 83 ms 81 ms 85 ms sip-east01.voipwelcome.com [208.43.68.151]

Trace complete.


Looks like my flight lands in DC whether or not its my destination...

[VOIPoTim]

C:\>tracert 67.228.77.18

Tracing route to sip-byod.voipwelcome.com [67.228.77.18]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 172.31.125.1
2 13 ms 17 ms 10 ms 24.113.35.1
3 11 ms 12 ms 14 ms 24-113-127-41.wavecable.com [24.113.127.41]
4 13 ms 12 ms 11 ms 64.146.249.93
5 13 ms 15 ms 13 ms 66.119.192.209
6 14 ms 21 ms 15 ms te1-3.cer01.seattle-datacenter.com [206.81.80.140]
7 84 ms 81 ms 85 ms te2-3.cer01.wdc01.washingtondc-datacenter.com [67.228.118.238]
8 115 ms 115 ms 116 ms te9-6.dar01.dal01.dallas-datacenter.com [208.43.118.193]
9 127 ms 115 ms 118 ms po1.fcr04.dal01.dallas-datacenter.com [66.228.118.214]
10 121 ms 115 ms 116 ms sip-byod.voipwelcome.com [67.228.77.18]

Trace complete.

C:>tracert west01.voipwelcome.com

Tracing route to west01.voipwelcome.com [174.37.45.134]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 172.31.125.1
2 15 ms 12 ms 14 ms 24.113.35.1
3 11 ms 11 ms 11 ms 24-113-127-41.wavecable.com [24.113.127.41]
4 16 ms 12 ms 13 ms wavebroadband-gw.g11-0.oly-cor0.noanet.net [64.146.232.253]
5 15 ms 13 ms 13 ms srp3-0.wtn-cor0.noanet.net [66.119.192.25]
6 213 ms * 12 ms te1-3.cer01.seattle-datacenter.com [206.81.80.140]
7 90 ms 82 ms 82 ms te2-3.cer01.wdc01.washingtondc-datacenter.com [67.228.118.238]
8 115 ms 115 ms 117 ms te9-6.dar01.dal01.dallas-datacenter.com [208.43.118.193]
9 136 ms 119 ms 117 ms po1.fcr04.dal01.dallas-datacenter.com [66.228.118.214]
10 117 ms 117 ms 115 ms sip-central01.voipwelcome.com [174.37.45.134]

Trace complete.

C:\>tracert sip-east01.voipwelcome.com

Tracing route to sip-east01.voipwelcome.com [208.43.68.151]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 172.31.125.1
2 11 ms 10 ms 11 ms 24.113.35.1
3 15 ms 9 ms 11 ms 24-113-127-41.wavecable.com [24.113.127.41]
4 13 ms 15 ms 14 ms ip-64-184-129-237.noanet.net [64.184.129.237]
5 17 ms 12 ms 13 ms te1-3.cer01.seattle-datacenter.com [206.81.80.140]
6 81 ms 81 ms 93 ms te2-3.cer01.wdc01.washingtondc-datacenter.com [67.228.118.238]
7 86 ms 81 ms 81 ms po1.fcr01.wdc01.washingtondc-datacenter.com [208.43.118.134]
8 83 ms 81 ms 85 ms sip-east01.voipwelcome.com [208.43.68.151]

Trace complete.


Looks like my flight lands in DC whether or not its my destination...

Forgot about that. West would be the exception....it's been offline since http://forums.voipo.com/showthread.php?t=1668

We're reviewing west coast options and all that traffic is in Dallas. The problem is that we've seen a few times where there's been some latency since the connections from west are connecting to core stuff back in Dallas through the public internet. There were a few occasional timeouts with database queries, etc.

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

We may put something back online for west coast users in the future, but none should have an issue with Dallas. We're still looking at Seattle since we can hit Dallas on the private network then vs the public internet, but it just has a lot of latency in terms of the public internet side that customers would connect to it on.

The goal is to avoid the public internet whenever possible for all internal stuff and handoffs.

[chpalmer]

I was just laughing due to the routing... From Seattle to DC then to Dallas...

Never know how the nets gonna route ya!