jupiter is hosed?

**dswartz** · 01-12-2009 10:59 AM

Hmmm, interesting. I was poking through my logs, and I see a flurry of registration failures up until 10:32 or so, when I switched to sip. I switched back and now it's okay. The suggestion to check via telnet to port 5060 is not really reliable, since that's going to use TCP, and not UDP. Sure it proves jupiter is up and reachable, but says nothing about whether it is not accepting SIP registration requests from me or not.

**gbh2o** · 01-12-2009 11:19 AM

You don't happen to still have anything set to codeblue do you? I remember seeing someone post their sample * settings that still had a codeblue reference for either host, fromdomain or something. I thought it odd at the time and then saw comments last night about it causing registration problems.

**dswartz** · 01-12-2009 11:37 AM

Aha, yes, in fact fromdomain is still codeblue! I don't remember being told to change that, but being BYOD, that's not surprising. I had changed the host and registration guys. Should it be the same name (e.g. sip or jupiter or whatever?)

**dswartz** · 01-12-2009 11:40 AM

Well, that isn't the answer

I changed fromdomain from codeblue to jupiter (.voipwelcome.com) and now it won't register. Voipo guys? What should fromdomain be?

**dswartz** · 01-12-2009 11:43 AM

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!)

Voipo guys, if you want to look at jupiter now, I've left my system set to register to jupiter and it is consistently failing...

The registrations are failing with:

SIP/2.0 401 Unauthorized

**burris** · 01-12-2009 11:51 AM

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!)

Voipo guys, if you want to look at jupiter now, I've left my system set to register to jupiter and it is consistently failing...

Why not try sip.voipwelcome.com...and see if the problems don't clear up.
Maybe jupiter isn't quite ready yet..

**dswartz** · 01-12-2009 11:52 AM

Burris, did you read the thread? That was what I WAS doing. Daryl says jupiter is fine...

**gbh2o** · 01-12-2009 02:20 PM

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.

**dswartz** · 01-12-2009 02:24 PM

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.