jupiter is hosed?

Just adding to the previous

Code:

---

C:\Logic>ping codeblue.voipo.com

Pinging codeblue.voipo.com [174.132.131.131] with 32 bytes of data:

Reply from 174.132.131.131: bytes=32 time=19ms TTL=52
Reply from 174.132.131.131: bytes=32 time=18ms TTL=52
Reply from 174.132.131.131: bytes=32 time=18ms TTL=52
Reply from 174.132.131.131: bytes=32 time=18ms TTL=52

Ping statistics for 174.132.131.131:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 19ms, Average = 18ms

C:\Logic>

---

So from what I see
codeblue.voipo.com = 174.132.131.131
sip.voipwelcome.com = 74.52.58.50
jupiter.voipwelcome.com = 208.43.97.218
zeus.voipwelcome.com = 74.52.58.50
mars.voipwelcome.com = 74.55.78.82

sip.voipwelcome.com != 174.132.131.131
codeblue.voipo.com != jupiter.voipwelcome.com
74.52.58.50 != 174.132.131.131
74.52.58.50 != 208.43.97.218
208.43.97.218 != 174.132.131.131

I guess now you have me confused :) Here is the issue:

I had registered with jupiter and it was working fine. Last night through this AM, calls were failing over to my cellphone, since I was apparently not registering successfully. I switched back to sip and it worked fine. I then switched back to jupiter and it was fine too there, but only for a bit, and then failed again (and is not registering at all anymore, just like last night.) The only place codeblue enters this discussion is because that is still from my fromdomain in my SIP config (and no-one has told me what to change it to, if anything.) Is that clearer?

I am opening a ticket as requested.

deleted ....................

Quote:

---

Originally Posted by dswartz

Actually, that may be a red-herring, as I changed fromdomain back to codeblue.voipo.com and it still won't register with jupiter (exactly the same failure mode as earlier today!)

---

Hope you get it resolved for your system. AFAIK, I've had continuous registration today. I certainly can't say what are really the right settings, and I'm not sure that there has ever been a VOIPo sponsored configuration posted. I remember back 'when', when several posted their initial setups for the carrier system. I currently have both 'host' and 'fromdomain' set to central01.voipwelcome.com and seem to be having no registration problems. [And, of course, the same in the registration string.]

I'm definitely NOT an expert... I just looked at my settings and I noticed that under the outgoing settings I have insecure=invite and under the incoming side I have insecure=very :( Oh well.... I blunder about a lot! Maybe that's the true secret of my success. :)

I'm pretty sure I changed fromdomain to jupiter.voipwelcome.com and it didn't help (also doesn't explain why this worked earlier and always works with sip - sigh...) I can't use central01 right now, since I have a 173.x.x.x IP address which used to be a bogon and voipo can't access it :( I'm trying to get verizon to get to the bottom of this.

Quote:

---

Originally Posted by dswartz

I'm pretty sure I changed fromdomain to jupiter.voipwelcome.com and it didn't help (also doesn't explain why this worked earlier and always works with sip - sigh...) I can't use central01 right now, since I have a 173.x.x.x IP address which used to be a bogon and voipo can't access it :( I'm trying to get verizon to get to the bottom of this.

---

Good luck! But, I'll bet you stand a much better chance of getting it resolved with Verizon than I would with Embarq here. Embarf seems to live in their own isolated world and does things however it suits them... to hell with standards. :(

I believe in the other thread that Tim indicated some association in a registration hash with the fromdomain setting... it almost sounded like codeblue might only work the 'old' folks. Maybe like some of the other cleanup they've had to do from the original coders.?

Per request, I switched back to sip. Just to be safe, I changed fromdomain to sip.voipwelcome.com. Registered right up. I tested incoming and that is fine. Can't check outgoing until I get home. I would avoid jupiter for the time being :(

Quote:

---

Originally Posted by dswartz

Per request, I switched back to sip. Just to be safe, I changed fromdomain to sip.voipwelcome.com. Registered right up. I tested incoming and that is fine. Can't check outgoing until I get home. I would avoid jupiter for the time being :(

---

Yeah since it's a beta server it won't be quite as stable....yet.

I have a VOIPO provisioned ATA and support moved me to Jupiter last week to resolve some other issues. Today, I can't get the ATA to register to Jupiter at all.

I had thought VOIPO had a load balancer in front of their servers so that we didn't have to worry about which server is up/down/working.

Quote:

---

Originally Posted by rcboats24

I have a VOIPO provisioned ATA and support moved me to Jupiter last week to resolve some other issues. Today, I can't get the ATA to register to Jupiter at all.

I had thought VOIPO had a load balancer in front of their servers so that we didn't have to worry about which server is up/down/working.

---

Jupiter isn't a production server so it's not in the mix.

No one should have been moved there in provisioning...only voluntarily at this point.

We are growing extremely fast right now though so there could have been a miscommunication about that. I'm going to check now to make sure no one else was provisioned there.