VOIPo server change?

[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!

[KenH]

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.

Thanks for the explanation Tim.

Ken

[VOIPoTim]

I just posted http://forums.voipo.com/showthread.p...4014#post14014 with updated info in case anyone else is wondering about west/future changes.

[tritch]

As a grandfathered BYOD user, I appreciate Tim in allowing me to continue to use my own ATA. The ability to tweak my dial plan as well as my DTMF settings to eliminate my talk-off issue are important to me. The recent announcement to discontinue all support for BYOD hasn't affected me personally since I've never had to open a ticket for my SPA2102. The only drawback I've had to using a non-provisioned ATA is my device lacks an option of automatic failover to another server whenever there's been a problem with the node that I'm connected to (central01). This leads me to my comments below....

A number of posts on this forum (and DSLR) related to Voipo being down and/or devices not registered have been due to node problems that users are simply unaware of at the time. A classic example is the PDU issue a few days ago that affected central01 users. The ability to rule out a node as the cause of registration failures versus an ISP or router issue would be of benefit to all BYODers and other users. For me personally, whenever I see my ATA unregistered, I'm always having to go to this forum or DSLR just to see if others are reporting the same problem. Is it Voipo? Is it my ISP? Is it my router?

I would love to see a simple network status window or tab in vPanel that shows the current working status of all nodes. This would definitely help me anytime I see registration failures.

Tim, would there be problem or objection to implementing this feature in vPanel?

[gbh2o]

I would love to see a simple network status window or tab in vPanel that shows the current working status of all nodes. This would definitely help me anytime I see registration failures.

Tim, would there be problem or objection to implementing this feature in vPanel?

I suggested a simple system long ago. See last page of http://forums.voipo.com/showthread.p...status+on-line