Inbound not working since last evening sometime (maybe 9:30 or so). Restarted asterisk, no joy. No devices showing as registered in vpanel. Switched back to sip and all is well.
Printable View
Inbound not working since last evening sometime (maybe 9:30 or so). Restarted asterisk, no joy. No devices showing as registered in vpanel. Switched back to sip and all is well.
Services are up and functional - there has been no outages reported by our monitoring software.
Are you sure this was not Asterik, ISP or Firewall related on your side?
To confirm this on your side: a simple "telnet jupiter.voipwelcome.com 5060" will help you determine if the service is up or down.
Well, everything else was working. Even a restart of the daemon didn't help. Registered with sip and it worked. I just tried re-registering with jupiter and now it works :(
No problem. In the future - if you suspect the service to be down, try connecting with a raw telnet to confirm. This will help you determine if it's the service or Asterik itself.Quote:
Originally Posted by dswartz
Hmmm, not as simple as that, I'm afraid. I run smokeping to monitor various servers (including yours), and during the problematic time, there was no indication of jupiter being down, which would seem to exonerate a firewall or ISP issue. If this happens again, I will run some more thorough tests...
Maybe it was just me hoarding resources with my * based account? ;-) I was using jupiter from 10:40 for more than 35 minutes [Yeah, no more time-outs]. Inbound was working fine before and after that time range for me.Quote:
Originally Posted by dswartz
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.
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.
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?)
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?
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
Why not try sip.voipwelcome.com...and see if the problems don't clear up.Quote:
Originally Posted by dswartz
Maybe jupiter isn't quite ready yet..
Burris, did you read the thread? That was what I WAS doing. Daryl says jupiter is fine...
http://forums.voipo.com/showthread.php?t=1038
Just in case you missed it.
I must have mis-read. I thought you wrote..Quote:
Originally Posted by dswartz
codeblue and not sip...
Sorry..
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...)
Codeblue is an old server. You should be using sip.voipwelcome.com
This has nothing to do with Jupiter. The server is perfectly fine.
If you continue to face issues - please open a support ticket.
FYI, I had an issue with jupiter last night as well.
Dylan, please re-read the thread. I am NOT using codeblue, I'm using jupiter. And it isn't working. The question I asked was what I should be using for the fromdomain field in my SIP config, since I still have codeblue.voipo.com there, but that doesn't seem to keep sip.voipwelcome.com from working.
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.
Code: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>
Code: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>
Just adding to the previous
So from what I seeCode: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>
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 ....................
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.]Quote:
Originally Posted by dswartz
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.
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. :(Quote:
Originally Posted by dswartz
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 :(
Yeah since it's a beta server it won't be quite as stable....yet.Quote:
Originally Posted by dswartz
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.Quote:
Originally Posted by rcboats24
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.
Tim, I using an * box, currently without problem registering with jupiter. Is there any need for me to abandon it? Switching for me is merely changing 4 small test chunks, so I can move easily. I actually believe it is _more_ trouble free for me, when it is working. I could just activate my so far unused 2nd Founder account and stick it there for testing instead, with absolutely no real impact. Just let me know what you'd prefer I do.Quote:
Originally Posted by VOIPoTim
EDIT: I guess I should clarify that it is central01 with which I am registering, not jupiter since I see that it actually resolves to a different IP? I'm beginning to get confused on which tests are where!
I can concur. Yesterday; my 2nd adapter (BYOD Linksys RT31P2 was not registered. I changed the settings back to texas; sip.voipwelcome.com and it registered fine. As of right now. 11:42 PM Mountain Time; I switched it back to Jupiter, and NO GO! At 11:44 pm I switched back to sip.voipwelcome.com and it syncs up and works. later....mike.....