ViaTalk → New servers not working BYOD... again

As the title says.
BYOD, SPA2102, LinkSys WRT54GSv4 forwarding ports.
Was working, now just dead air when dialing.

Switched to chicago server, works, but cannot hear ring when dialing out.

Friday I was on chicag-1c and had my failover number ring a few times.

Not sure whats going on.

TJ

Chugging along here on optimusprime (BYOD with asterisk). Just made a couple of calls.

Using optimusprime as well. No problems all weekend.

optimusprime is great... but those of us on the East coast need a similarly working server that doesn't require a transcontinental internet trip.

}Davoice

+1 here on a trixbox.

Cheers,
Kermee

The transcontinental round trip should not matter. I use providers whose media gateway is in the east coast (voicepulse connect) and have both SIP and media servers on the east coast (Callcentric, Gizmoproject, Vbuzzer ...) and the call quality is as good as Viatalk.

Try out the left coast server. You can always switch to another server if the call quality is bad.

What new servers? I didn't get any emails. I've been having issues with newyork-2.

East Coast, West Coast, Left or Right.....
which is which?
prime, mega, and galva still no worky.
chicago-1i still no ring outbound.

TJ

On optimusprime. Inbound and outbound audio and DTMF are ok. Getting rings on outbound calls and others hear the ring when calling my number.

See ya...

d.c.

Now I have nothing. Any server one way audio.
Wife just called me from cellphone upset.

The saga continues.

Wow, you are experiencing the same d@am thing I went through with my innomedia ata. I tried all the old and new servers and had the same problems, no outbound ring, incoming calls busy, dead air when dialing, all of that.

After two months of horrible daily outages I broke down and called to order the viatalk ata. I was told $30.00 plus shipping and then found out after reading on the forum that it wasn't to "buy" the ata, but to activate it.

Anyhow, they sent out their ata and changed the password on my account without telling me, so I was completely down for 2 whole days before I could get through and talk to someone who knew what was going on. In the mean time my wife was dealing with our newborn at home all day long and the phone was constantly going down. This went on for over 2 months and when they changed the password last week I finally had it. I went to T-mobile and signed up for their @home service and will be canceling my viatalk contract that still has 13 months on it. Now I have to send back an unopened adapter and probably eat the 40 bucks. At this point, with my wife at home all day with a new baby I just need a phone that "works".

This will be my last rant, but I have to say that I haven't dealt with such a disorganized company in a long time. Their operations guys don't talk to customer support, customer support doesn't talk to billing, billing doesn't talk to the customer, the list just goes on and on... It's like the AT&T of old was reborn into the new voip world.

I keep reading Brenden's posts about improvements and it sure seems that they are trying to make headway, but in reality it just hasn't been effective for a whole lot of us.

As I posted in another thread, I think my issue with the old servers is because I set my codec for G729 for the new servers. As a SR refugee, the Innomedia was set for G729 as the preferred codec. If you did not reset the codec to G711u, you would have experienced the same one way audio as me. Last night the light bulb went on for me and I changed back to G711u, and chicago servers are working well. I have not tried the new servers yet.

I also broke down and will be trying one of the new GS ATA's. According to VT, that should help eleiminate my problems. You should have opened the package and tried it.

As far as my overall opinion of VT... I am very pleased. Sure, I have had my problems, but the group here has always been helpful, and the suggestions from the VT people here have been welcome. I do not like that I get a better response to issues here over the ticket process, but it is what it is. No company is perfect, but VT sure has it more together then TB/SR ever did. I wish I had switched sooner from TB, and would do it again if I had to.

TJ

I think the inno box calls it by a different name but I tried switching between G729 and G711u codecs as the new servers support the lower bitrate one, but neither did any good. I might have had one or two days good service after making the change, but then it was back to the same set of problems.

Hopefully the change will hold for you.

What 'new' servers? I also did not receive information on new servers, I recall there was a beta group of servers some time ago.

I know of: Richmond, Newyork, Chicago, Sanjose, Houston -but these are not new servers. And, I've been happy for a long time (in voip terms) on the same server. So is it time for me to find the password and review telnet procedures for my ATA? Is something about to change?

There has been alot of talk about them. Galvatron, Megatron...

Thx: I'm now up to speed on the new Galvatron, Megatron servers.

But the question I have seems unanswered: Though these servers are 'in production', what is the life expectancy of the old servers? What happens to BYOD on the old servers, will the old servers resolve to the new servers without end-user input?

If/when they remove the old servers, I would guess (and it is just a guess, as I don't work for VT) that they would just point the legacy DNS names to the new servers (so that anyone who has the old server names "hard coded" in their BYOD adapter would continue to have things work). The reason I'm guessing they will do this, is that it's very cheap to maintain the legacy DNS entries on their DNS server, and that is in fact what they did when they last changed their server names (i.e. when they went to their "regional names", the old names they previously used continued to resolve to valid servers).

So (my guess) is that anyone who is using an old/legacy server name will continue to be OK, subject to a single minor disruption as their adapter switches over to the new IP of the DNS entry. Of course, if your ATA can't handle the routing done by the new servers, you may have a problem when this happens. And if you were foolish enough to hard code the IP address of your server/proxy (vs using the DNS name of the proxy), all bets are off. But if I were to guess, I would suspect that the vast majority of us BYOD users will just "seamlessly" switch over to a new servers whenever VT gets around to changing which IP addresses the legacy server names (in DNS) point to...

Thanks, just that many of us are conditioned that migrations are never as uneventful as they logically should be. Then one day we are surprised with dead service and WAF is in the toilet.

Edit: Nevermind...wife shut ringer off on all the phones.

How about Galvatron? It's in Chicago I think. I have two accounts with VT and was using Optimus for one and Galva for the other just in case something happened. But when I did a tracert to galvatron and saw it was across the country I switched both to optimus. I'm on Comcast and thanks to CRAN all my traffic seems to get routed through LA which just happens to be where optimusprime is. So that cuts out more than half the hops compared to galvatron.