jupiter is hosed?

[dswartz]

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]

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]

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]

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]

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

[Xponder1]

http://forums.voipo.com/showthread.php?t=1038

Just in case you missed it.

[burris]

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

I must have mis-read. I thought you wrote..

codeblue and not sip...

Sorry..

[dswartz]

Now, I do see I'm using fromdomain as the original codeblue.voipo.com, but I don't know if that can be the issue, since jupiter sometimes works for me and then suddenly not (and sip always works...)

[Xponder1]

Unless something is wrong wouldn't you be connecting to Zeus if your using sip.voipwelcome.com ? I am just wondering how your using sip.voipwelcome.com and always ending up on jupiter. I have tried to catch up on the forums here and from what I read it should only fail-over to other servers which would indicate a problem. Not trying to insult you just trying to understand.

C:\Logic>pathping sip.voipwelcome.com

Tracing route to sip.voipwelcome.com [74.52.58.50]
over a maximum of 30 hops:
  0  Logic-desktop [192.168.1.110]
  1  Router [192.168.1.1]
  2  ppp-70-128-127-254.dsl.tulsok.swbell.net [70.128.127.254]
  3  dist1-vlan50.tul2ok.sbcglobal.net [69.152.80.66]
  4  bb1-g1-0-2.tul2ok.sbcglobal.net [69.152.81.40]
  5  69.220.8.91
  6  151.164.251.162
  7  te1-4-10G.ar2.DAL2.gblx.net [67.16.131.185]
  8  The-Planet.GigabitEthernet7-3.ar2.DAL2.gblx.net [64.208.170.198]
  9  te9-2.dsr01.dllstx3.theplanet.com [70.87.253.14]
 10  76.fd.5746.static.theplanet.com [70.87.253.118]
 11  vl1.car02.dllstx6.theplanet.com [12.96.160.23]
 12  zeus.voipwelcome.com [74.52.58.50]

Computing statistics for 300 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Logic-desktop [192.168.1.110]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  Router [192.168.1.1]
                                0/ 100 =  0%   |
  2    7ms     0/ 100 =  0%     0/ 100 =  0%  ppp-70-128-127-254.dsl.tulsok.swbell.net [70.128.127.254]
                                0/ 100 =  0%   |
  3  ---     100/ 100 =100%   100/ 100 =100%  dist1vlan50.tul2ok.sbcglobal.net[69.152.80.66]
                                0/ 100 =  0%   |
  4    7ms     0/ 100 =  0%     0/ 100 =  0%  bb1-g1-0-2.tul2ok.sbcglobal.net [6
9.152.81.40]
                                0/ 100 =  0%   |
  5   17ms     0/ 100 =  0%     0/ 100 =  0%  69.220.8.91
                                0/ 100 =  0%   |
  6   30ms     0/ 100 =  0%     0/ 100 =  0%  151.164.251.162
                                0/ 100 =  0%   |
  7   82ms     0/ 100 =  0%     0/ 100 =  0%  te1-4-10G.ar2.DAL2.gblx.net [67.16
.131.185]
                                0/ 100 =  0%   |
  8   18ms     0/ 100 =  0%     0/ 100 =  0%  The-Planet.GigabitEthernet7-3.ar2.
DAL2.gblx.net [64.208.170.198]
                                0/ 100 =  0%   |
  9  ---     100/ 100 =100%   100/ 100 =100%  te9-2.dsr01.dllstx3.theplanet.com
[70.87.253.14]
                                0/ 100 =  0%   |
 10  ---     100/ 100 =100%   100/ 100 =100%  76.fd.5746.static.theplanet.com [7
0.87.253.118]
                                0/ 100 =  0%   |
 11  ---     100/ 100 =100%   100/ 100 =100%  vl1.car02.dllstx6.theplanet.com [1
2.96.160.23]
                                0/ 100 =  0%   |
 12   18ms     0/ 100 =  0%     0/ 100 =  0%  zeus.voipwelcome.com [74.52.58.50]


Trace complete.

C:\Logic>

C:\Logic>ping jupiter.voipwelcome.com

Pinging jupiter.voipwelcome.com [208.43.97.218] with 32 bytes of data:

Reply from 208.43.97.218: bytes=32 time=53ms TTL=52
Reply from 208.43.97.218: bytes=32 time=52ms TTL=52
Reply from 208.43.97.218: bytes=32 time=52ms TTL=52
Reply from 208.43.97.218: bytes=32 time=52ms TTL=52

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

C:\Logic>pathping jupiter.voipwelcome.com

Tracing route to jupiter.voipwelcome.com [208.43.97.218]
over a maximum of 30 hops:
  0  Logic-desktop [192.168.1.110]
  1  Router [192.168.1.1]
  2  ppp-70-128-127-254.dsl.tulsok.swbell.net [70.128.127.254]
  3  dist1-vlan60.tul2ok.sbcglobal.net [69.152.80.130]
  4  bb1-g5-0-0.tul2ok.sbcglobal.net [69.152.80.242]
  5  69.220.8.81
  6  asn2828-XO.eqdltx.sbcglobal.net [151.164.249.134]
  7  te-3-0-0.rar3.dallas-tx.us.xo.net [207.88.12.2]
  8  te-4-0-0.rar3.atlanta-ga.us.xo.net [207.88.12.1]
  9  207.88.14.117.ptr.us.xo.net [207.88.14.117]
 10  207.88.14.118.ptr.us.xo.net [207.88.14.118]
 11  207.88.183.54.ptr.us.xo.net [207.88.183.54]
 12  border1.te7-2-bbnet2.wdc008.pnap.net [216.52.127.98]
 13  te1-1.cer01.wdc01.washingtondc-datacenter.com [66.151.100.66]
 14  po1.fcr01.wdc01.washingtondc-datacenter.com [208.43.118.134]
 15  east01.voipwelcome.com [208.43.97.218]

Computing statistics for 375 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Logic-desktop [192.168.1.110]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  2-Wire [192.168.1.1]
                                0/ 100 =  0%   |
  2    7ms     0/ 100 =  0%     0/ 100 =  0%  ppp-70-128-127-254.dsl.tulsok.swbe
ll.net [70.128.127.254]
                                0/ 100 =  0%   |
  3  ---     100/ 100 =100%   100/ 100 =100%  dist1-vlan60.tul2ok.sbcglobal.net
[69.152.80.130]
                                0/ 100 =  0%   |
  4    7ms     0/ 100 =  0%     0/ 100 =  0%  bb1-g5-0-0.tul2ok.sbcglobal.net [6
9.152.80.242]
                                0/ 100 =  0%   |
  5   18ms     0/ 100 =  0%     0/ 100 =  0%  69.220.8.81
                                0/ 100 =  0%   |
  6   18ms     0/ 100 =  0%     0/ 100 =  0%  asn2828-XO.eqdltx.sbcglobal.net [1
51.164.249.134]
                                0/ 100 =  0%   |
  7   18ms     0/ 100 =  0%     0/ 100 =  0%  te-3-0-0.rar3.dallas-tx.us.xo.net
[207.88.12.2]
                                0/ 100 =  0%   |
  8   49ms     0/ 100 =  0%     0/ 100 =  0%  te-4-0-0.rar3.atlanta-ga.us.xo.net
 [207.88.12.1]
                                0/ 100 =  0%   |
  9   49ms     0/ 100 =  0%     0/ 100 =  0%  207.88.14.117.ptr.us.xo.net [207.8
8.14.117]
                                0/ 100 =  0%   |
 10   51ms     0/ 100 =  0%     0/ 100 =  0%  207.88.14.118.ptr.us.xo.net [207.8
8.14.118]
                                0/ 100 =  0%   |
 11   56ms     0/ 100 =  0%     0/ 100 =  0%  207.88.183.54.ptr.us.xo.net [207.8
8.183.54]
                                0/ 100 =  0%   |
 12   51ms     0/ 100 =  0%     0/ 100 =  0%  border1.te7-2-bbnet2.wdc008.pnap.n
et [216.52.127.98]
                                0/ 100 =  0%   |
 13  ---     100/ 100 =100%   100/ 100 =100%  te1-1.cer01.wdc01.washingtondc-dat
acenter.com [66.151.100.66]
                                0/ 100 =  0%   |
 14  ---     100/ 100 =100%   100/ 100 =100%  po1.fcr01.wdc01.washingtondc-datac
enter.com [208.43.118.134]
                                0/ 100 =  0%   |
 15   51ms     0/ 100 =  0%     0/ 100 =  0%  east01.voipwelcome.com [208.43.97.
218]

Trace complete.

C:\Logic>

[gbh2o]

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.