Printable View
It would appear VOIPo is now selecting the server for all customers, including grandfathered BYOD'ers. I guess some of the obeisant whining got to them. I never had a reason to complain, especially since my device had a failover server option. The good side is they can now switch us off a downed server just like the provisioned users. At least that's how it appears, anyway.
We did remove the "selection option" in the control panel. It was just causing too many support issues.
Things like us moving users for specific reasons when something was going on and them then getting hostile about being moved "without permission" or users that may just have a bad connection to one that support would move off of it and they'd move it back, etc.
Overall it causes more issues than it should. We need to manage our network in the best way and since users don't have all the same info we have about things that are happening, there is almost a "power struggle" with users wanting things one way even if they know it could affect their service negatively (things like latency or know bad connections to certain ISPs, etc).
Grandfathered BYOD users can still use hostnames. The selector was always just for provisioned users.
We have a few other vPanel changes that I'll post about (including this one) a little later.
Thanks for clarifying Tim.
The reason I was wondering is because I have east set as the hostname in the ATA and vpanel-devices shows me on central.
I also see the DTMF and routing voice thru VOIPo server options are gone.
https://secure.voipo.com/preferences/advanced
That kind of stinks. I liked having the flexibility to be able to change it myself vs having to email support. Boo!
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 agree with fisamo. I was with Viatalk when we would chase the best working server. I got tired of that rat race and switched to the calm world of CallVantage. With CallVantage all I had to do is pick up the phone and talk. It always worked and there was never a reason to consider which server I was connected to. Voipo will be a winner if they can replicate the "boring" CallVantage service.
True, it is impossible to load balance for optimal service if the loads are constantly changing via customer actions who don't know what the loads are. It is a good change, not a bad one.
Same indication as voipinit here.
Why is vPanel indicating "Connected To VOIPo Central" when my ATA is configured to east?
I understand the idea behind it, but I liked having the flexibility if I needed it, that's all.
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.Quote:
Originally Posted by fisamo
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.
Hey! I resemble that remark! :)Quote:
Originally Posted by burris
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.Quote:
Originally Posted by KenH
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,Quote:
Originally Posted by VOIPoBrandon
I guess I am one of the "old timers":rolleyes:
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.
^ x2
Indicating central, set to east, I am a grandfathered BYOD'er.
No not for grandfathered BYOD users.Quote:
Originally Posted by KenH
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.
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.
:eek: :D 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=1668Quote:
Originally Posted by chpalmer
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.
I was just laughing due to the routing... From Seattle to DC then to Dallas...
Never know how the nets gonna route ya!
;)
I just posted http://forums.voipo.com/showthread.p...4014#post14014 with updated info in case anyone else is wondering about west/future changes.
Thanks for the explanation Tim.Quote:
Originally Posted by VOIPoTim
Ken
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?
I suggested a simple system long ago. See last page of http://forums.voipo.com/showthread.p...status+on-lineQuote:
Originally Posted by tritch
I was unaware this had been suggested before.Quote:
Originally Posted by gbh2o
BTW, I'm unable to access your link, I get the message "you do not have permission to access this page Pre-Launch Alpha Archives"
That area is the real pre-launch dialogs.
Lots of detailed things I don't think the average owner would volunteer.
Tim was very transparent and it was all very interesting.
Sorry about that! ;-) It _was_ over two and a half years ago; I just remembered the discussion and hadn't even checked to see if it was in the alpha period. My how time flies when you're having fun with VOIPo! LONG before the massive data center geographic build outs.Quote:
Originally Posted by tritch
I think the concept is still valid, perhaps more so these days.