 bmize13
join:2006-04-17 Dallas, GA
·ViaTalk
| Trouble with the Trons?
I have just received notice that my service is being move to the new network today, and wanted to ask the question of you who are already there; "What do I need to be aware of?" Are there consistent errors that crop up after being transferred?
Honestly, I'm really kinda sad about the move... For the past month or two, my service has been rock solid. Reminds me of a guy I knew back when I was in the Navy... He always said, "It ain't broke. It just don't work right." My service hasn't been broken lately. Seems like every time it settles down, something happens to unsettle it. I'd like to stay ahead of the curve in this case, so I'm soliciting any advice from the new network folks. |
|
 dcurrey
join:2004-06-29 | If you don't get one way audio on calls or DTMF problems right away you should be good to go. |
|
 bombashack
join:2002-01-04 Annapolis, MD
| reply to bmize13 I'm an old BYOD customer, who just switched. I received my Grandstream provisioned adapter and immediately had problems. I'm on the East Coast and it was pointed to Galvatron. With Galvatron, I had erratic behavior. It sometimes worked fine, other times issues such as no incoming audio, calls routed straight to VM. Support provisioned me on Chicago 1a then Chicago 1f; both worked fine for calls but when checking VM, the server did not understand the DTMF tones (VM password). I've now got provisioning disabled and the adapter pointed to Megatron. I've been on Megatron for ~36 hrs and all seems fine. If you were hoping for better news, then sorry... |
|
  VTBrendan Viatalk Premium join:2005-06-27 Clifton Park, NY
| reply to bmize13 said by bmize13 :I have just received notice that my service is being move to the new network today, and wanted to ask the question of you who are already there; "What do I need to be aware of?" Are there consistent errors that crop up after being transferred? Honestly, I'm really kinda sad about the move... For the past month or two, my service has been rock solid. Reminds me of a guy I knew back when I was in the Navy... He always said, "It ain't broke. It just don't work right." My service hasn't been broken lately. Seems like every time it settles down, something happens to unsettle it. I'd like to stay ahead of the curve in this case, so I'm soliciting any advice from the new network folks. Hi,
Unless you see something from the get go you should be fine. The majority of our users have no issues at all. Problems arise when certain router or home network configurations have an issue with the audio stream being shifted around instead of going through our switches directly, however those can all be worked out. Once up and running on the new system, people have been having a smoother go of it, as we're getting significantly less service related calls on a % basis from those successfully migrated.
-Brendan |
|
 unknvoip
join:2006-07-25 Rochester, NY
·ViaTalk
| I am curious as to if I have been migrated, or not. I always register to one of the Trons and I had to have my DTMF setting changed to Auto to control voicmail from my phone, but I never was notified that I was being migrated.
My server setting is currently 'East', but I have had it set to 'Central' as well and still end up registering on a 'Tron'.
Did I undergo a stealth migration? |
|
 jay_rm
join:2002-04-12 Netville
·Fox Valley Internet
·ViaTalk
| reply to bmize13 I've been BYOD'ing the 'trons for a month or so with no issues. I'm running one line on Megatron and the other on Galvatron.
Although, I have not been 'officially' switched until very recently, I suspect there will be no difference between 'official' and 'un-official' with BYOD. -- 3500/512 5.7 GHz Motorola Canopy Wireless; FoxValley.net "Peace through superior firepower" |
|
 bmize13
join:2006-04-17 Dallas, GA
·ViaTalk
edit: October 8th, @09:49PM
| reply to bmize13 Seriously... I *KNEW* it would happen. Service is sailing along, everything works... Then, BAM! Upgrade, and now no incoming at all. Calls do not go to voice-mail, they don't fail over... Just dead air, then a busy signal.
Why the hell can't they just leave well enough alone?
*sigh* Time to go take time to fill out a ticket. Then, it'll be time to answer the obligatory, "how is your network configured?"
*THIS* is why the service isn't ready for prime time.
Edited to add: Line One is also no longer working.
Seriously, VT... This isn't much of an upgrade from my view. |
|
 bmize13
join:2006-04-17 Dallas, GA
·ViaTalk
edit: October 8th, @10:19PM
| reply to bmize13 Decided to call Tech Support... Yeah, like I'm going to get through.
"There are currently Forty Zero Callers in front of you."
(Seriously... Forty Zero. Is that like 400?)
Edited to add: Got through to Steven in about 5 minutes. He made some changes, and I was able to see line one again. He said it was a port problem, though he didn't elaborate. Thought it would be fixed. Hung up, tried to call my VT line, and got "All Circuits are busy." Tried a few minutes later, and got dead air again for 30 seconds until another busy signal. Tried several more times, and consistently got the dead-air.
Am on hold (again) (Number 37 in the queue), and will ask them to call my line before hanging up again. |
|
 bmize13
join:2006-04-17 Dallas, GA
·ViaTalk
| reply to bmize13 30 minutes on hold, then get a rep... Nothing they can do. He said that AT&T is rerouting my traffic to a different port. I can make outgoing, but I'm "unreachable" incoming. Works fine on Cable.
I have to say that I'm not convinced it's not their upgrade. Everything was perfect until they upgraded me to the new network. Coincidence? I honestly don't think so. Yet, I know that the VT's will come in and tell me all sorts of stuff about how they can't control AT&T, and it has nothing to do with the upgrade, etc... All I know is, I worked perfectly until the upgrade, and now not at all.
Funny thing, too... I ordered DSL specifically to handle VT, as *VT* said it would be much more reliable than Comcast.
Best I can say is that this is BS. If AT&T blocks VT, I'm thinking it's lights out for them. As I said, I just don't buy that as the end-all answer.
Yeah... It pisses me off. Such a HUGE waste of my time to try and figure all this out...
My BIG question is this; If it showed "Unreachable" on VT's end, why did Steven let me get off the phone with the impression that all was great?
Thanks for the upgrade. |
|
  ptrowski Got Helix? Premium join:2005-03-14 Putnam, CT clubs: | I use AT&T DSL with VT and can tell you quality and stability are much better than when I was on cable. |
|
 digger16309
join:2007-06-26 00001
·VOIPo
·ViaTalk
| said by ptrowski :I use AT&T DSL with VT and can tell you quality and stability are much better than when I was on cable. I have Comcrap and I've never had an ISP-related issue with VoIP of any flavor. |
|
 digger16309
join:2007-06-26 00001
·VOIPo
·ViaTalk
| reply to bmize13 said by bmize13 :I have to say that I'm not convinced it's not their upgrade. Everything was perfect until they upgraded me to the new network. Coincidence? I honestly don't think so. Of course it's the upgrade.
Don't let them Jedi-Mindtrick you into believing otherwise.
VOIPo |
|
  ptrowski Got Helix? Premium join:2005-03-14 Putnam, CT clubs:
·AT&T DSL Service
·ViaTalk
| said by digger16309 :said by bmize13 :I have to say that I'm not convinced it's not their upgrade. Everything was perfect until they upgraded me to the new network. Coincidence? I honestly don't think so. Of course it's the upgrade. Don't let them Jedi-Mindtrick you into believing otherwise. VOIPo Was anyone denying it was? I didn't think so. -- "A religious war is like children fighting over who has the strongest imaginary friend."
Have you been touched by his noodly appendage? »www.venganza.org |
|
 digger16309
join:2007-06-26 00001
·VOIPo
·ViaTalk
| said by ptrowski :said by digger16309 :said by bmize13 :I have to say that I'm not convinced it's not their upgrade. Everything was perfect until they upgraded me to the new network. Coincidence? I honestly don't think so. Of course it's the upgrade. Don't let them Jedi-Mindtrick you into believing otherwise. VOIPo Was anyone denying it was? I didn't think so. My comment was definitely not directed at you ptrowski.
Read his posts. VT's latest blame went to AT&T. All was working well before the "upgrade". Yet, VT says it is not the upgrade. Blame the customer's setup, which has not changed. Not surprising, really.
It's amazing how the "majority of users" are not having any problems with the upgrade but there are several recent posts in the entirety of this forum about very long tech support waits.
Oh, sorry, if you call right now, wait times are averaging 5 minutes. This is also known as the ViaTalk Tech Support Principle. Just the act of reading that the wait is 2 hours makes it 5 minutes. |
|
  ptrowski Got Helix? Premium join:2005-03-14 Putnam, CT clubs:
·AT&T DSL Service
·ViaTalk
| AT&T modems can be set up in bridging mode or PPOe. So it could be the way the modem is configured. So in reality it very well could be that way.
The best idea would be for bmize to post in the AT&T direct forum and David and they guys can tell him exactly what is going on.
When you change the architecture of your system, there are bound to be issues that arise. I have yet to ever see a major upgrade go completely as planned. With Voip the variables are even potentially worse as in theory everyone's set up can be different.
The wait times, well that is anyone's call.  |
|
  VTBrendan Viatalk Premium join:2005-06-27 Clifton Park, NY
edit: October 9th, @12:10PM
| reply to digger16309 If you make a change to a ton of peoples setups, which requires tweaking to say 5%, it creates a large uptick in support requests for a short period of time. We've been spreading it out over a long period of time to mitigate the effect of that to some degree.
The poster is saying it's working over cable and not AT&T. That makes it sound to me like its a problem with the combination of the two, specifically its likely related to the way audio is routed to different locations on the new system, and it is very likely something that can be worked out.
Bmize, do you know if the AT&T modem has any routing or higher level networking functions integrated into it?
As a side note, currently the wait time for a callback is about 14 minutes.
-Brendan |
|
 digger16309
join:2007-06-26 00001
·VOIPo
·ViaTalk
| reply to ptrowski said by ptrowski :When you change the architecture of your system, there are bound to be issues that arise. That's fine. I'm just going by what was stated in June, saved for posterity.
»Re: log |
|
 digger16309
join:2007-06-26 00001
·VOIPo
·ViaTalk
| reply to VTBrendan said by VTBrendan :The poster is saying it's working over cable and not AT&T. The OP can fight for himself, but while I'm here...
I recognize it is not very clear in this thread, but it was working over cable 6 weeks ago, and then on the old system over AT&T DSL after that. It was only after the "upgrade" that the OP started having problems (again).
»Line One Not Working |
|
  ptrowski Got Helix? Premium join:2005-03-14 Putnam, CT clubs: | "Should be" does not equate to will be. Obviously Brendan was wrong. You know what? It happens. For some of us it was practically seamless.
And yes, the OP can fight for himself. I don't think he needs you derailing the thread either. |
|
 digger16309
join:2007-06-26 00001
·VOIPo
·ViaTalk
| said by ptrowski :"Should be" does not equate to will be. Obviously Brendan was wrong. You know what? It happens. For some of us it was practically seamless. And yes, the OP can fight for himself. I don't think he needs you derailing the thread either. I am most certainly not derailing the thread.
Read the OP's posts.
It's a transition issue. The transition was not seamless to the OP. VT wrongly (again, and as usual) blamed the OP's setup, which played perfectly nicely with the old system. Yet, the OP is told it is an AT&T problem and basically, too bad.
The only reason I brought the old thread back was to remind people how absolutely preposterous it was to ever even think that the transition to new servers would be "seamless". Of course Brendan was wrong. He was always going to be wrong on that point. Hope is not a business strategy, not a winning one anyway.
I understand your frustration in continuing to defend VT despite the indefensible, but don't take it out on me. |
|