Connectivity Issues with sip.voipwelcome.com

**dtrose** · 03-16-2012 08:56 AM

Has anyone else been having registration / connectivity issues using sip.voipwelcome.com both yesterday (Thurs 15 March) and today (Fri 16 March). Received several calls to Failover number yesterday and today and also (at times) cannot place outbound calls.

**tritch** · 03-16-2012 10:16 AM

Yes. There's definitely a problem with their BYOD server starting yesterday and today. My father just called to tell me he's having random registration loss and connectivity issues on both lines of the ATA connected to the BYOD server. I'm connected to their main SIP server (sip-central01.voipwelcome) and am not experiencing this issue at all. Voipo please fix!

**Bink** · 03-16-2012 10:23 AM

I can confirm this issue as well. Shame. It would appear sip.voipwelcome.com does not have the same high availability as their other VoIP servers. I wonder how long it’ll be down for.

FWIW, this thread is should be moved to the BYOD sub-forum.

**tritch** · 03-16-2012 10:40 AM

This was my main concern as well when I put my father on BYOD. It appears the BYOD server doesn't get the same attention or monitoring for problems as their main servers. Has anyone opened up a support ticket?

**stenger** · 03-16-2012 11:03 AM

I have been having non stop issues with sip.voipwelcome.com this entire week. I even sent a ticket in about the issue but they told me there were no network issues and closed the case since they won't troubleshoot BYOD. I know the issue is not on my end since I still have a perfectly functional sip line working on the same BYOD from another service provider. While I am not happy to be having issues I'm glad it's not just me.

**VOIPoTim** · 03-16-2012 11:07 AM

Everything is fine on our monitoring and we only have 4 help desk tickets in our main queue (for everything) so there are no signs of a widespread issue for BYOD.

It's very possible there could be intermittent connectivity for some users somewhere along the way though.

We are looking into it more, but don't see any issues on out end at this time.

If anyone is having issues with it, please open a help desk ticket by e-mailing support@voipo.com with your info.

**Bink** · 03-16-2012 11:32 AM

At least for the last 30 minutes, the service appears to have gone back to normal for me.

**SpaethCo** · 03-16-2012 11:34 AM

*NOTE: All times are CDT

It's not an IP network / latency problem -- it's definitely a problem with SIP processing by the server. The first time I started showing registration timeouts is at 18:26 on 3/12.

3/13 - Intermittent problems starting at 9:05:17, clearing up at 17:07:00
3/14 - Intermittent problems starting at 10:35:40, clearing up at 15:36:30
3/15 - Intermittent problems starting at 10:07:28, clearing up at 14:45:51 starting at 23:10:114, clearing at 23:35:49
3/16 - See the log output below -- this is what i mean by intermittent problems.

Here's the log out of something that is definitely not Asterisk:

Code:

[Mar 16 09:08:46] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE!  Last qualify: 3345
[Mar 16 09:08:56] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Reachable. (37ms / 5000ms)
[Mar 16 09:10:06] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE!  Last qualify: 37
[Mar 16 09:10:18] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Reachable. (1704ms / 5000ms)
[Mar 16 09:11:28] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE!  Last qualify: 1704
[Mar 16 09:13:01] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Reachable. (3410ms / 5000ms)
[Mar 16 09:14:11] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE!  Last qualify: 3410
[Mar 16 09:16:08] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE!  Last qualify: 6290
[Mar 16 09:16:16] NOTICE[28461] chan_sip.c:    -- Registration for 'MyVOIPoNUM@sip.voipwelcome.com' timed out, trying again (Attempt #1)
[Mar 16 09:16:38] NOTICE[28461] chan_sip.c:    -- Registration for 'MyVOIPoNUM@sip.voipwelcome.com' timed out, trying again (Attempt #2)
[Mar 16 09:16:58] NOTICE[28461] chan_sip.c:    -- Registration for 'MyVOIPoNUM@sip.voipwelcome.com' timed out, trying again (Attempt #3)
[Mar 16 09:17:18] NOTICE[28461] chan_sip.c:    -- Registration for 'MyVOIPoNUM@sip.voipwelcome.com' timed out, trying again (Attempt #4)
[Mar 16 09:17:22] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Reachable. (3785ms / 5000ms)
[Mar 16 09:18:32] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE!  Last qualify: 3785
[Mar 16 09:20:06] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Reachable. (4248ms / 5000ms)
[Mar 16 09:21:13] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Lagged. (6815ms / 5000ms)
[Mar 16 09:21:15] NOTICE[28461] chan_sip.c:    -- Registration for 'MyVOIPoNUM@sip.voipwelcome.com' timed out, trying again (Attempt #1)
[Mar 16 09:21:33] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE!  Last qualify: 6815
[Mar 16 09:21:35] NOTICE[28461] chan_sip.c:    -- Registration for 'MyVOIPoNUM@sip.voipwelcome.com' timed out, trying again (Attempt #2)
[Mar 16 09:21:55] NOTICE[28461] chan_sip.c:    -- Registration for 'MyVOIPoNUM@sip.voipwelcome.com' timed out, trying again (Attempt #3)
[Mar 16 09:22:05] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Reachable. (1846ms / 5000ms)
[Mar 16 09:22:15] NOTICE[28461] chan_sip.c:    -- Registration for 'MyVOIPoNUM@sip.voipwelcome.com' timed out, trying again (Attempt #5)
[Mar 16 09:22:35] NOTICE[28461] chan_sip.c:    -- Registration for 'MyVOIPoNUM@sip.voipwelcome.com' timed out, trying again (Attempt #6)
[Mar 16 09:24:15] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE!  Last qualify: 425
[Mar 16 09:24:58] NOTICE[28461] chan_sip.c:    -- Registration for 'MyVOIPoNUM@sip.voipwelcome.com' timed out, trying again (Attempt #1)
[Mar 16 09:25:18] NOTICE[28461] chan_sip.c:    -- Registration for 'MyVOIPoNUM@sip.voipwelcome.com' timed out, trying again (Attempt #2)
[Mar 16 09:25:38] NOTICE[28461] chan_sip.c:    -- Registration for 'MyVOIPoNUM@sip.voipwelcome.com' timed out, trying again (Attempt #3)
[Mar 16 09:27:27] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Reachable. (2026ms / 5000ms)
[Mar 16 09:28:33] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Lagged. (5925ms / 5000ms)
[Mar 16 09:28:46] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Reachable. (2678ms / 5000ms)
[Mar 16 09:31:42] NOTICE[28461] chan_sip.c:    -- Registration for 'MyVOIPoNUM@sip.voipwelcome.com' timed out, trying again (Attempt #1)
[Mar 16 09:31:58] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE!  Last qualify: 233
[Mar 16 09:32:02] NOTICE[28461] chan_sip.c:    -- Registration for 'MyVOIPoNUM@sip.voipwelcome.com' timed out, trying again (Attempt #2)
[Mar 16 09:32:30] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Reachable. (2659ms / 5000ms)
[Mar 16 09:33:36] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Lagged. (6207ms / 5000ms)
[Mar 16 09:33:49] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Reachable. (2776ms / 5000ms)
[Mar 16 09:42:03] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Lagged. (5741ms / 5000ms)
[Mar 16 09:42:13] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Reachable. (699ms / 5000ms)
[Mar 16 09:49:20] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Lagged. (5294ms / 5000ms)
[Mar 16 09:49:31] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Reachable. (641ms / 5000ms)
[Mar 16 10:16:50] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE!  Last qualify: 2169
[Mar 16 10:17:04] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Reachable. (4634ms / 5000ms)
[Mar 16 10:34:12] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Lagged. (5510ms / 5000ms)
[Mar 16 10:34:27] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Reachable. (4988ms / 5000ms)
[Mar 16 10:52:35] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Lagged. (6203ms / 5000ms)
[Mar 16 10:52:49] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Reachable. (4536ms / 5000ms)
[Mar 16 11:12:13] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE!  Last qualify: 2257
[Mar 16 11:12:25] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Reachable. (2036ms / 5000ms)
[Mar 16 11:18:36] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE!  Last qualify: 36
[Mar 16 11:18:51] NOTICE[28461] chan_sip.c:    -- Registration for 'MyVOIPoNUM@sip.voipwelcome.com' timed out, trying again (Attempt #1)
[Mar 16 11:19:10] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Reachable. (4396ms / 5000ms)
[Mar 16 11:20:20] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE!  Last qualify: 4396
[Mar 16 11:21:12] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Reachable. (1566ms / 5000ms)
[Mar 16 11:21:15] NOTICE[28461] chan_sip.c:    -- Registration for 'MyVOIPoNUM@sip.voipwelcome.com' timed out, trying again (Attempt #2)
[Mar 16 11:22:22] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE!  Last qualify: 1566
[Mar 16 11:22:34] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Reachable. (2178ms / 5000ms)
[Mar 16 11:51:10] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE!  Last qualify: 1741
[Mar 16 11:51:22] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Reachable. (2158ms / 5000ms)
[Mar 16 11:58:37] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE!  Last qualify: 2203
[Mar 16 11:59:31] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Reachable. (3453ms / 5000ms)
[Mar 16 12:00:41] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE!  Last qualify: 3453
[Mar 16 12:00:55] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Reachable. (3858ms / 5000ms)
[Mar 16 12:03:05] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE!  Last qualify: 144
[Mar 16 12:03:17] NOTICE[28461] chan_sip.c:    -- Registration for 'MyVOIPoNUM@sip.voipwelcome.com' timed out, trying again (Attempt #1)
[Mar 16 12:03:18] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Reachable. (2868ms / 5000ms)
[Mar 16 12:03:37] NOTICE[28461] chan_sip.c:    -- Registration for 'MyVOIPoNUM@sip.voipwelcome.com' timed out, trying again (Attempt #3)
[Mar 16 12:04:28] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE!  Last qualify: 2868
[Mar 16 12:04:56] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Reachable. (2256ms / 5000ms)
[Mar 16 12:05:54] NOTICE[28461] chan_sip.c:    -- Registration for 'MyVOIPoNUM@sip.voipwelcome.com' timed out, trying again (Attempt #1)
[Mar 16 12:07:09] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE!  Last qualify: 2884
[Mar 16 12:07:43] NOTICE[28461] chan_sip.c: Peer 'VOIPo' is now Reachable. (4553ms / 5000ms)

Traceroute looks good:

Code:

traceroute to sip.voipwelcome.com (67.228.190.149), 30 hops max, 40 byte packets
 1  triton.pagethrower.com (69.65.12.139)  0.050 ms  0.073 ms  0.068 ms
 2  69.65.12.137 (69.65.12.137)  2.136 ms  2.134 ms  2.497 ms
 3  p122.csr2.Chi3.Servernap.net (66.252.0.157)  0.836 ms  0.767 ms  0.701 ms
 4  xe-5-0-0.er1.Chi2.Servernap.net (66.252.0.70)  1.821 ms  1.814 ms  1.809 ms
 5  te1-7.bbr01.eq01.chi01.networklayer.com (206.223.119.63)  2.124 ms  2.121 ms  2.114 ms
 6  * * *
 7  ae0.dar01.sr01.dal01.networklayer.com (173.192.18.253)  29.587 ms  30.020 ms  30.013 ms
 8  po2.fcr04.sr05.dal01.networklayer.com (66.228.118.218)  27.972 ms  27.797 ms  27.731 ms
 9  67.228.190.149-static.reverse.softlayer.com (67.228.190.149)  29.879 ms  30.217 ms  30.149 ms

Latency and packet delivery looks great:

Code:

--- sip.voipwelcome.com ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 99006ms
rtt min/avg/max/mdev = 29.865/30.452/36.203/1.232 ms

**VOIPoTim** · 03-16-2012 11:53 AM

E-mail this info to tier2@voipo.com and an engineer will be able to take a look for you.

**chrisb009** · 03-17-2012 06:42 AM

I too have been experiencing issues with the BYOD server. I'd much rather be on their (sip-central01.voipwelcome) server than this (sip.voipwelcome.com) server. I have had nothing but on going issues with this BYOD service since I signed up. I just signed up for a total of four years and am considering cancelling and requesting a refund. I don't have any issues with other SIP providers I currently use (3 other providers total) only VOIPo. Makes sense its VOIPo’s BYOD server and not my setup/equipment.