jupiter is hosed?

[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.

[gbh2o]

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.?

[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

[VOIPoTim]

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.