Production Migration

We'll be announcing the migration to production systems in the next few days. Just need to do a little more testing.

For those feeling very adventurous and are willing to risk some issues coming up, feel free to try it yourself.

All you need to do is just register to zeus.voipwelcome.com. This is one of several switches which users will be load balanced on when we're done.

This also has the new CDR system in it which is instant and provides call status, etc.

Once we're ready next week for the full migration, we'll post more info for everyone else.

For those using provisioned ATAs, it'll be automatic for you.

Quote:

---

Originally Posted by VOIPoTim

All you need to do is just register to zeus.voipwelcome.com. This is one of several switches which users will be load balanced on when we're done.

---

Yup, successfully registered to zeus.voipwelcome.com and got dial tone instantly. Did a 1 min test call and it worked fine, will need to do more tests later..

Nope, sorry, but failed to register with the residential account sitting on PBXes.

"NOTICE[14363] chan_sip.c: Failed to authenticate on REGISTER to '25281nnnnn@zeus.voipwelcome.com'

Back to codeblue! It still works great.

Both lines are doing fine so far on the new zeus. Later... Mike....

Moved my byod line over for testing. :) Ill do some softphone testing tomorrow...

So does vpanel work for this?

Quote:

---

Originally Posted by chpalmer

Moved my byod line over for testing. :) Ill do some softphone testing tomorrow...

So does vpanel work for this?

---

Yes, should be no issues.

Moved mine too. Inbound works fine. Outbound I can't test until I get home.

Shows no working device. But registered fine. :)

Same thing here, calls work, and asterisk says I'm registered, but no devices on vpanel...

Yes, the devices thing in vPanel was just a temporary troubleshooting area. It is still specific to codeblue.

For those of you using this early, please let us know if you notice any issues with features.

Dropped it from my PBXes account since it wouldn't work with the 'zeus.voipwelcome.com'.

Added it to a local PBXiaF box. Same problem. Works great with codeblue, but will not register with 'zeus.voipwelcome.com'. Incoming is fine, but no outbound due to registration failure

Outbound calling works.

Tried to register but my PAP2 says 'can't connect to login server' :(

Norm got me all fixed up !!

Quote:

---

Originally Posted by VOIPoTim

Yes, the devices thing in vPanel was just a temporary troubleshooting area. It is still specific to codeblue.

---

Please retain the devices thing in Vpanel when migrated to production if possible.

zeus.voipwelcome.com also didn't work for me on a Zoom.

I think that pretty much rules me out from using it.

Quote:

---

Originally Posted by gbh2o

zeus.voipwelcome.com also didn't work for me on a Zoom.

I think that pretty much rules me out from using it.

---

Please open a ticket and we'll reset you SIP password and it'll resync.

Some of the very early accounts were setup using a very sloppy method that our previous developer used storing 2 passwords...one encryped...one unencrypted. So when we merge into the new system, there are two passwords. So essentially codeblue and the new cluster has different passwords for you.

Codeblue will be offline in the very near future and everyone will be on the new platform which is much more stable and doesn't have things like this in the mix.

This currently affects about 80 users. (Same issues Montano had earlier BTW)

Quote:

---

Originally Posted by VOIPoTim

Please open a ticket and we'll reset you SIP password and it'll resync.

Some of the very early accounts were setup using a very sloppy method that our previous developer used storing 2 passwords...one encryped...one unencrypted. So when we merge into the new system, there are two passwords. So essentially codeblue and the new cluster has different passwords for you.

---

I think we ran into that problem somewhere else too. Will throw in a ticket.

Quote:

---

Originally Posted by gbh2o

I think we ran into that problem somewhere else too. Will throw in a ticket.

---

Yeah it's one of those things where the way it was setup, it was using one password for some things and the other password for another even within codeblue.

Quote:

---

Originally Posted by myvoip07

Please retain the devices thing in Vpanel when migrated to production if possible.

---

Id love to see this too...


:D

All I did was change the proxy to zeus on BOTH my Linksys RT31P2 and My Grandstream; rebooted both; and they both came right up. haven't seen any issues so far. Later.... Mike.....

Anyone else got X-Lite working on zeus yet?

On the new system with my PIAF box. Tim had to reset my password, but once he did so, all was good in the land of voipo...

Thanks, Tim!

I just tested X-Lite on my Mac Leopard from zeus.voipwelcome.com and it worked fine. Version 3.0 release 1014k build 47051

Norm

Yeah, X-Lite with the default settings worked for me as well. Phone number as User and Auth User. No other changes outside of defaults.

Are you seeing issues with it?

Now that my password has been reset, it plays nicely on each of the Zoom, PBXiaF system and PBXes account (the normal resting place for it) again.

mercy buckets!

If I hook up another adapter to the test bed and use the password I am now regestered with, will it mess up my VOIPo line when I go back to it??

Quote:

---

Originally Posted by burris

If I hook up another adapter to the test bed and use the password I am now regestered with, will it mess up my VOIPo line when I go back to it??

---

Only one at a time will work, but it won't affect your ability to switch back to codeblue.

Version 3 build 41150 Im getting registration error 408 Request Timeout.

I have the newest build.


I have another ATA on here with the line Im trying on also. Could that affect it?

Fired it up on my SPA 2102...it registered immediately...calls worked in and out...

Only unusual thing was as soon as it registered and I went off hook to dial out, I got a stutter tone. I would imagine that you might have VM enabled in the test bed as I have mine disabled in my VOIPo account..

Not too shabby. ;)

Quote:

---

Originally Posted by chpalmer

Version 3 build 41150 Im getting registration error 408 Request Timeout.

I have the newest build.


I have another ATA on here with the line Im trying on also. Could that affect it?

---

It shouldn't. You're using zeus.voipwelcome.com and not zeus.voipo.com?

Someone asked how many servers they can choose from....

For those wondering, all core machines are now going to use the voipwelcome domain in their hostname. It's nothing special, just an anonymous domain to be used in headers so resellers won't have clients potentially seeing VOIPo.

Here's some additional background... When we move everyone, you'll be using sip.voipo.com and that'll be the only option to connect to. Once we fully roll it out, it will then automatically distribute people if needed and handle failover. No 50 servers choices like VT unfortunately.

Our setup is a little different in that VT using Asterisk is VERY limited in terms of how many users can use each server. Many of VT's problems (my opinion/theory only) are likely caused by loads. Asterisk just isn't designer for carriers and the creator of it will even tell you that. Ever notice how things are going well with VT and then someone "outs" the working server and it goes downhill? It's because Asterisk can't handle large loads. Ever wonder why VT moves people without them knowing sometimes? They have to fight to distribute loads. Since it's user-controlled, there's another variable that makes it hard to do this. Asterisk doesn't do well when it hits a few hundred simultaneous calls. It then gets very flaky and inconsistent. Ever wonder why random issues come up and then later they just go away on their own?

We use Asterisk for voicemail which it's fine for, but for everything else, we use a carrier-grade softswitch (OpenSER) which can handle tens of thousands of requests per second and just proxies everything that's designed for carriers. Voicepulse uses it, Cisco uses it as the base for some of their commerical systems, etc.

OpenSER does not handle media at all...it's just a proxy that sets up the connections. In most cases, we are handing off the media now to remote gateways. In some cases that we do handle media, OpenSER doesn't handle it, but it can be distributed to a cluster of weighted telco-grade switches or softswitches vs having to go through the server (like Asterisk). That's where load issues typically come into play.

We've been using OpenSER since day 1 and hopefully you've seen how mcuh more reliable it can be. It doesn't do as much in some ways and that's the beauty of it.

So with us, just a few telco grade softswitches on the frontend with the way we have things setup can addresss the same load that 100 Asterisk servers could. Asterisk is great for businesses, PBX solutions, and for functionality/features. It's not good for large-scale setups though.

Quote:

---

Originally Posted by VOIPoTim

It shouldn't. You're using zeus.voipwelcome.com and not zeus.voipo.com?

---

Right. This is probably a network issue on my end and to prove that Im going to evict the "gamer" off my desktop shortly and try from there...


I copy paste everything just because I dont trust my eyeballs sometimes.


The RT31P2 Ive got on that line is behaving. ;)

Twas a DNS issue.

Ive never had the dns fields under options/advanced/network populated before. Suddenly I need it so maybe my router...

Oh well. Fixed for now...

uhm,
my utstarcom F1000 registers with zeus through pbxes.com
I know for sure that I've made a couple of 1800-555-8355 today; however, I do not see any new entries in call log
tried both "Call History" and "Old Call Logs"
one other thing, "Devices" shows "You do not currently have any devices registered to our servers!" yet I was able to call out:confused:

Quote:

---

Originally Posted by voxabox

one other thing, "Devices" shows "You do not currently have any devices registered to our servers!" yet I was able to call out:confused:

---

yeah that is not working for zeus.voipwelcome.com, it was a nice option to have hope they bring it back. Per Tim in another post it was merely for troubleshooting/debug purpose enabled on codeblue.voipo.com

Quote:

---

Originally Posted by myvoip07

yeah that is not working for zeus.voipwelcome.com, it was a nice option to have hope they bring it back. Per Tim in another post it was merely for troubleshooting/debug purpose enabled on codeblue.voipo.com

---

Yeah, it was a great 1st step for the _user_ to confirm if _he_ had problems before bothering the support staff ;-)