PDA

View Full Version : 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:

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

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:

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

SpaethCo
03-19-2012, 09:27 AM
I bumped the ticket again. After no issues over the weekend, problems started up again this morning.

I went back through my logs - I only lose registration on weekdays, and this all started right around the beginning of this month.

SpaethCo
03-19-2012, 11:47 AM
For now I've just disabled registration and enabled call forwarding in vPanel for all calls to a SIP URI on my system. Since the SIP URI forwarding happens on the production nodes at least incoming calls are not impacted by the issues on byod. For outbound calls I've tightened up some of my timeout values so that it will roll forward onto other SIP trunks when the byod server slows down.

I don't make a ton of calls so I haven't had extensive testing with this configuration, but so far so good. Still hoping the issues get resolved for SIP processing on the BYOD server.

tritch
03-19-2012, 12:41 PM
I bumped the ticket again. After no issues over the weekend, problems started up again this morning.

I went back through my logs - I only lose registration on weekdays, and this all started right around the beginning of this month.

Just curious....did Tier 2 support indicate that the issue had been resolved prior to today? If so, did they provide any details?

I was going to open a support ticket (for my father), but it seems pointless if they already know it's impacting a large number of customers.

dtrose
03-19-2012, 12:47 PM
My ticket is still open from Friday at 1p


Just curious....did Tier 2 support indicate that the issue had been resolved prior to today? If so, did they provide any details?

I was going to open a support ticket (for my father), but it seems pointless if they already know it's impacting a large number of customers.

stenger
03-19-2012, 01:26 PM
I too had almost no or limited issues over the weekend. Having said that I also don't sit at my desk with my BYOD device as much on the weekend. Starting this morning however I am back to having the same problems. In fact over the last 25 minutes my sip service has gone down numerous times. Still having no issues with another service provider on the same device. It seems to continue to be very random when the service fails but it does go to the "failover" solution during these outages.

SpaethCo
03-19-2012, 01:40 PM
The ticket response simply said they would update the ticket with any of their findings. That was Friday, and that's the last update.

burris
03-19-2012, 04:54 PM
If you look at their Tweet site, it indicates that they cleared up those problems yesterday.

SpaethCo
03-19-2012, 11:53 PM
No, sir, they did not.


[Mar 19 12:31:33] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 38
[Mar 19 12:32:04] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (34ms / 500ms)
[Mar 19 12:36:05] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 37
[Mar 19 12:36:15] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (35ms / 500ms)
[Mar 19 12:37:16] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 35
[Mar 19 12:37:26] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (39ms / 500ms)
[Mar 19 12:41:27] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 35
[Mar 19 12:41:48] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (37ms / 500ms)
[Mar 19 12:46:49] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Lagged. (916ms / 500ms)
[Mar 19 12:46:59] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (35ms / 500ms)
[Mar 19 12:53:00] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 38
[Mar 19 12:53:10] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (35ms / 500ms)
[Mar 19 13:15:12] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 54
[Mar 19 13:15:44] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (41ms / 500ms)
[Mar 19 14:08:48] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 42
[Mar 19 14:09:20] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (43ms / 500ms)
[Mar 19 14:12:21] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 39
[Mar 19 14:13:15] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (41ms / 500ms)
[Mar 19 14:15:16] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 86
[Mar 19 14:15:48] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (270ms / 500ms)
[Mar 19 14:16:49] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 270
[Mar 19 14:17:22] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (333ms / 500ms)
[Mar 19 14:18:23] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 333
[Mar 19 14:23:19] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (426ms / 500ms)
[Mar 19 14:24:20] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 426
[Mar 19 14:25:14] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (476ms / 500ms)
[Mar 19 14:39:16] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 35
[Mar 19 14:39:26] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (34ms / 500ms)
[Mar 19 14:40:27] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 34
[Mar 19 14:40:48] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (54ms / 500ms)
[Mar 19 14:50:49] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 37
[Mar 19 14:51:10] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (42ms / 500ms)
[Mar 19 15:07:12] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Lagged. (870ms / 500ms)
[Mar 19 15:07:23] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 870
[Mar 19 15:07:33] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (419ms / 500ms)
[Mar 19 15:19:35] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 42
[Mar 19 15:20:07] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (39ms / 500ms)
[Mar 19 15:52:09] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Lagged. (547ms / 500ms)
[Mar 19 15:52:19] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (40ms / 500ms)
[Mar 19 15:58:20] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 40
[Mar 19 15:58:52] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (36ms / 500ms)
[Mar 19 16:02:53] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 36
[Mar 19 16:03:03] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (42ms / 500ms)
[Mar 19 16:04:04] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 42
[Mar 19 16:05:09] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (40ms / 500ms)
[Mar 19 16:06:10] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 40
[Mar 19 16:06:20] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (39ms / 500ms)
[Mar 19 16:08:21] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 34
[Mar 19 16:10:43] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (42ms / 500ms)
[Mar 19 16:20:45] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 37
[Mar 19 16:21:06] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (39ms / 500ms)
[Mar 19 16:23:07] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 36
[Mar 19 16:23:28] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (165ms / 500ms)
[Mar 19 16:39:29] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Lagged. (673ms / 500ms)
[Mar 19 16:39:39] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (37ms / 500ms)
[Mar 19 16:43:41] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 38
[Mar 19 16:43:51] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (35ms / 500ms)
[Mar 19 17:05:52] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 41
[Mar 19 17:06:02] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (37ms / 500ms)
[Mar 19 18:31:07] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 34
[Mar 19 18:31:17] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (152ms / 500ms)
[Mar 19 18:32:18] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 152
[Mar 19 18:35:13] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (425ms / 500ms)
[Mar 19 19:03:55] NOTICE[10033] chan_sip.c: Peer 'voipms-chi' is now UNREACHABLE! Last qualify: 3
[Mar 19 19:04:41] NOTICE[10033] chan_sip.c: Peer 'voipms-chi' is now Reachable. (58ms / 5000ms)
[Mar 19 21:25:21] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 34
[Mar 19 21:25:31] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (34ms / 500ms)
[Mar 19 23:05:36] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 36
[Mar 19 23:05:57] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (39ms / 500ms)
[Mar 19 23:06:58] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 39
[Mar 19 23:07:09] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (304ms / 500ms)
[Mar 19 23:09:10] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 40
[Mar 19 23:09:20] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (36ms / 500ms)
[Mar 19 23:15:21] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Lagged. (595ms / 500ms)
[Mar 19 23:15:31] NOTICE[10033] chan_sip.c: Peer 'VOIPo' is now Reachable. (36ms / 500ms)

That's all chan_sip events after noon today. Here's the peers I'm qualifying:


Name/username Host Dyn Nat ACL Port Status
VOIPo/XXXXXXXXXX 67.228.190.149 5060 OK (38 ms)
voipms-dal 74.54.54.178 5060 OK (22 ms)
voipms-chi 64.120.22.242 5060 OK (3 ms)
vitel-outbound 64.2.142.17 5060 OK (27 ms)
vitel-inbound 64.2.142.116 5060 OK (27 ms)
flowroute2 70.167.153.130 5060 OK (68 ms)
flowroute1 216.115.69.144 5060 OK (53 ms)
callcentric/1777XXXXXXXX 204.11.192.23 5080 OK (30 ms)

Again, this only affects the BYOD server, and it is *NOT* network related -- if I run a continuous ping there is no deviation in latency or packet loss while the SIP processing problems occur. The standard provisioned ATA servers (Central01 / East01) are still processing traffic normally.

Liebestod
03-20-2012, 06:47 AM
I was unable to make outgoing calls this morning. There have been intermittent incoming call issues (callers going directly into voice mail/forwarded) for the past two weeks as well.

Opened a new ticket this morning for the outgoing call issue.

Previous to this, service has been flawless.

Mark

VOIPoBrandon
03-20-2012, 03:57 PM
SpaethCo,

So I've been capturing the delta between packet exchanges for the last few hours for your account / connection, I've sorted each response time / delta in ascending order. Please see below.

U +0.000052 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000062 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000062 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000069 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000073 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000075 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000083 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000084 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000084 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000085 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000086 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000086 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000086 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000086 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000087 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000087 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000089 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000089 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000089 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000089 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000090 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000090 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000091 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000091 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000091 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000091 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000092 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000092 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000092 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000092 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000092 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000092 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000092 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000092 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000093 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000093 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000093 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000094 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000094 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000095 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000095 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000095 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000095 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000095 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000095 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000096 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000096 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000096 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000097 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000098 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000099 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000099 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000099 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000099 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000100 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000100 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000100 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000100 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000100 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000100 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000101 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000101 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000102 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000102 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000102 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000104 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000104 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000104 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000104 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000104 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000105 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000107 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000108 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000109 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000109 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000109 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000110 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000111 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000113 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000117 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000120 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000121 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000122 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000122 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000122 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000123 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000124 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000125 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000125 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000127 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000128 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000128 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000131 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000131 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000132 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000133 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000134 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000134 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000136 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000136 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000136 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000138 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000138 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000139 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000139 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000141 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000141 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000142 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000146 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000147 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000147 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000147 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000149 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000149 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000150 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000150 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000151 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000152 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000153 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000155 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000157 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000158 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000159 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000160 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000160 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000163 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000164 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000164 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000167 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000168 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000170 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000171 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000173 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000173 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000173 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000174 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000175 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000176 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000176 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000178 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000179 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000181 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000181 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000183 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000183 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000186 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000192 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000193 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000195 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000198 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000201 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000203 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000204 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000206 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000208 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000209 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000210 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000211 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000218 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000234 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000235 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000240 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000258 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000263 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000267 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000269 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000290 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000298 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000307 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000323 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000333 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000359 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000383 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000390 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000407 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000410 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000413 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000434 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000435 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000435 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000444 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000447 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000447 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000466 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000467 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000468 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000469 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000471 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000476 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000487 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000493 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000494 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000494 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000494 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000495 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000498 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000500 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000502 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000507 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000508 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000508 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000519 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000520 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000522 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000529 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000530 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000532 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000533 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000546 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000564 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000564 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000566 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000570 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000572 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000573 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000578 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000590 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000592 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000594 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000598 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000608 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000613 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000614 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000626 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000647 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000681 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000698 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000716 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000717 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000740 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000753 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000849 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000851 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000874 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000896 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000913 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.000981 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001015 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001023 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001092 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001106 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001127 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001133 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001158 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001160 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001258 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001267 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001300 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001309 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001310 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001342 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001392 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001438 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001455 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001499 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001527 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001532 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001571 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001579 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001703 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001716 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001836 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001850 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001911 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001946 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001953 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.001992 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.002005 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.002118 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.002207 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.002302 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.002397 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.002459 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.002483 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.002484 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.002514 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.002531 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.002540 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.002613 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.002651 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.002656 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.002688 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.002717 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.002759 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.002778 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.002792 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.002916 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.002919 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.002929 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.002970 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.002978 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003002 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003010 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003023 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003039 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003042 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003048 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003054 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003070 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003118 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003151 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003167 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003210 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003220 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003228 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003255 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003273 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003325 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003350 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003360 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003372 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003510 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003530 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003572 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003646 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003654 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003676 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003694 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003768 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003865 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003871 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003871 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003906 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003982 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.003982 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.004011 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.004023 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.004117 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.004136 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.004159 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.004419 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.004460 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.004511 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.004565 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.004597 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.004633 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.004710 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.004719 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.004748 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.004748 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.004758 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.004763 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.004784 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.004877 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.004896 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.005039 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.005043 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.005048 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.005087 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.005131 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.005255 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.005520 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.005522 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.005538 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.005627 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.005696 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.005816 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.005894 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.005909 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.005960 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.005979 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.006055 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.006061 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.006121 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.006344 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.006380 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.006490 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.006599 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.006688 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.006735 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.006842 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.006873 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.007061 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.007082 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.007206 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.007324 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.007677 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.007736 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.007912 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.008494 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.008564 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.008733 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.009323 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.009406 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.009825 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.010276 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.010737 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.010845 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.011251 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.011428 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.011905 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.012261 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.012583 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.012704 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.012755 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.013819 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.013924 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.014485 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.028704 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.029313 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.032724 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.036662 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.036980 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.077777 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.080340 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.141949 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.149192 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.182269 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.220008 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.268069 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.331442 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.411739 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.431680 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.491423 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.517639 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.528667 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.595162 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.623156 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.650850 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.690568 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.701821 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.715816 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.773802 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.802555 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.931967 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +0.963959 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +1.016428 67.228.190.149:5060 -> XX.XX.XX.XXX:5060
U +3.197618 67.228.190.149:5060 -> XX.XX.XX.XXX:5060

Now --- as you can see there are a few packets that are above the 80ms mark. So I will admit there is some delay. However I do not see this as "service effecting" delay. One thing I can suggest is to lengthen your re-registration interval. There really is no need to re-register every 1 minute to our network. This will only cause further congestion.

Please let us know if you are seeing otherwise "service affecting issues". Thank you.

tritch
03-21-2012, 08:47 AM
Brandon, I don't think this issue has been resolved yet.....

Are any of you still experiencing this issue today? I just tried calling my father and it went to his failover number even though it appeared his lines were registered. These registration problems are so intermittent you never know if it's going to work or not. They seem to drop in and out of registration in between re-registration intervals similar to the posted SpaethCo logs.

VOIPoBrandon
03-21-2012, 09:16 AM
Tritch,

The scenario you describe is completely different than SpaethCo's logs. He has a registration interval of 1 minute as well as OPTION ping requests he is sending us in which he is stating that our response to requests are delayed. I tracked each of his requests and as you can see an actual delay in response is few and far in-between and certainly not service impacting.

As for your call to your father --- it could have routed to failover for a number of different reasons, however this typically means that we did not receive a response back from your Father's endpoint / device to our request to initiate the call. So you can see here we are talking about two completely different scenarios.

Also there is not really a such thing as dropping out of registration in-between registration intervals since the actual registration interval is what determines in 99% of the cases the next time of request for registration. So in which case we would still have maintained an AoR (Address of Record) that we could contact the endpoint at given there are no firewalls preventing our request. This is of course unless the SIP device / client is doing some kind of odd rebounding logic in which it thinks its loss connectivity to our network.

tritch
03-21-2012, 10:26 AM
Also there is not really a such thing as dropping out of registration in-between registration intervals since the actual registration interval is what determines in 99% of the cases the next time of request for registration. So in which case we would still have maintained an AoR (Address of Record) that we could contact the endpoint at given there are no firewalls preventing our request. This is of course unless the SIP device / client is doing some kind of odd rebounding logic in which it thinks its loss connectivity to our network.

Thanks. I stand corrected. I probably should have said that in-between registrations it was losing the "ability" to communicate with SIP server even though the lines showed registered. There's no doubt that I was seeing sporadic loss of registrations on his lines in vPanel up until Monday. His problems were identical to what others have posted.

The failover problem this morning was symptomatic of the same registration/connectivity problems that have been affecting most of the BYOD folks over the past week. I just assumed it was the same ongoing issue. His ATA is in the DMZ of the router, so I doubt it was a response or firewall issue with his device.

Is this case considered closed? I'm assuming all the support tickets have been cleared up.

SpaethCo
03-21-2012, 11:48 AM
He has a registration interval of 1 minute as well as OPTION ping requests he is sending us in which he is stating that our response to requests are delayed. I tracked each of his requests and as you can see an actual delay in response is few and far in-between and certainly not service impacting.The expiry interval for registration is actually 120 seconds (asterisk always renews at expiry-15 seconds, so 105 seconds in this case).

In any case, I'm updating the case with packet captures to show the behavior that is concerning. There are periods of time where the server simply stops responding to all SIP requests -- registration, options, invites. I'm sorry, but that is service impacting when call setup traffic is not being processed.

stenger
03-21-2012, 01:00 PM
Tritch,

As of today I am still having issues although not as bad as yesterday. Brandon has been very helpful in trying to get to the bottom of the problem. I agree though that because it is so sporadic it is a bit frustrating to know when a call will work or not work, especially on incoming calls. My guess is that it is not very widespread but still an issue for some of us.

VOIPoBrandon
03-21-2012, 02:08 PM
Hello,

We really do not see any majorly concerning issues and it seems very isolated as to who is experiencing issues.

This is not a capacity / load issue as the load and demand on the current proxy is very low and processing as normally expected.

sip:~# uptime
20:04:34 up 140 days, 21:11, 1 user, load average: 0.08, 0.04, 0.01

However we've setup an additional proxy in an alternate network segment to see if you guys have better connectivity to this server.

You can swap out your proxy from "sip.voipwelcome.com" to "sip2.voipwelcome.com"

Please do let us know how this works out for you, thanks!

tritch
03-21-2012, 08:38 PM
Will do....My father called to tell me that he was still having problems this afternoon with incoming & outgoing calls. Very intermittent. I had him switch over to sip2.voipwelcome.com this evening to see how things go. His patience is starting to wear thin, so if this doesn't fix the issue then he will re-connect the Voipo provided ATA to register with sip-central01.

FYI...I'm BYOD connected to sip-central01 w/ absolutely no connectivity or registration issues at all (using grandfathered SIP credentials). Same ATA (SPA2102), same configuration as my father, just a different ISP.

SpaethCo
03-22-2012, 03:19 PM
Things have been 100% issue-free since I switched to sip2 yesterday around 3pm central.

wingsohot
03-22-2012, 06:25 PM
A bit frustrating? Imagine how us resellers feel. Reseller accounts are all on the BYOD server. Customers complaining non stop. Some even threatening to cancel.
Tritch,

As of today I am still having issues although not as bad as yesterday. Brandon has been very helpful in trying to get to the bottom of the problem. I agree though that because it is so sporadic it is a bit frustrating to know when a call will work or not work, especially on incoming calls. My guess is that it is not very widespread but still an issue for some of us.

tritch
03-22-2012, 07:39 PM
Things have been 100% issue-free since I switched to sip2 yesterday around 3pm central.

Same here....my father reports no issues since switching to sip2.

stenger
03-23-2012, 01:28 PM
No issues any more here after the switch.

Thanks.

GreenLantern
03-25-2012, 08:20 PM
For what it's worth, we've been dealing with a similar issue, using a BYOD IP PBX system.

System has been working near flawlessly for several months, then starting around March 12, we started getting periodic drops in connectivity.

This results in incoming calls going to failover. And outbound calls fail, telling us basically that we do not have a connected trunk.

Changing to SIP2 seems to have solved the issue for several locations, but not our busiest installation.

VOIPoBrandon
03-26-2012, 04:39 PM
For what it's worth, we've been dealing with a similar issue, using a BYOD IP PBX system.

System has been working near flawlessly for several months, then starting around March 12, we started getting periodic drops in connectivity.

This results in incoming calls going to failover. And outbound calls fail, telling us basically that we do not have a connected trunk.

Changing to SIP2 seems to have solved the issue for several locations, but not our busiest installation.

PM me the details and I'll take a look - I am curious if it is possible if you are hitting some kind of channel limiting / alternate issue.

Look forward to hearing back from you, thanks!

GreenLantern
03-27-2012, 02:53 PM
voipo has a ticket open on this for us already.

The problem seems to be related to a similar issue we are now having with several of our accounts.

Some of our voipo accounts are now unable to receive calls. Callers get "the number you have dialed is not in service" messages.

After submitting a ticket, it seems to be partially resolved, so that we can now call some of the problematic accounts from a non-voipo number.

But if we call from a voipo number, we still get the "not in service" message. Or alternately, we get some kind of call failure like a busy signal on IP phones or "all circuits are busy now" on pbx phones.

Hopefully it will be resolved soon.

Bink
03-27-2012, 09:35 PM
However we've setup an additional proxy in an alternate network segment to see if you guys have better connectivity to this server.

You can swap out your proxy from "sip.voipwelcome.com" to "sip2.voipwelcome.com"

Please do let us know how this works out for you, thanks!
Are these the same servers?

$ host sip.voipwelcome.com
sip.voipwelcome.com has address 67.228.182.2
$ host sip2.voipwelcome.com
sip2.voipwelcome.com has address 67.228.182.2

Bink
03-27-2012, 10:30 PM
Are these the same servers?

$ host sip.voipwelcome.com
sip.voipwelcome.com has address 67.228.182.2
$ host sip2.voipwelcome.com
sip2.voipwelcome.com has address 67.228.182.2
On further inspection, it appears sip.voipwelcome.com used to resolve to 67.228.190.149, so I assume issues have been uncovered with the previous network segment and/or proxy and all requests are now being forwarded to the new one.

Bink
03-29-2012, 04:34 PM
Just thought I’d chime in to say since these SIP proxy changes, most of my BYOD calls now connect very quickly—and I tend to have less noticeable delay (from the time I stop speaking till the time my other party starts) in my conversations. Kudos to VOIPo for correcting this ongoing issue—and let’s hope VOIPo’s monitoring and correction of issues like these are more proactive in the future.

SpaethCo
05-21-2012, 11:04 PM
Anyone else starting to see this act up again? I'm noticing my logs showing loss of connectivity, but only for the VOIPo SIP peer:


[May 21 08:33:37] NOTICE[2053] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 30
[May 21 08:33:48] NOTICE[2053] chan_sip.c: Peer 'VOIPo' is now Reachable. (30ms / 500ms)
[May 21 08:35:49] NOTICE[2053] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 30
[May 21 08:35:59] NOTICE[2053] chan_sip.c: Peer 'VOIPo' is now Reachable. (30ms / 500ms)
[May 21 09:08:01] NOTICE[2053] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 30
[May 21 09:08:11] NOTICE[2053] chan_sip.c: Peer 'VOIPo' is now Reachable. (30ms / 500ms)
[May 21 09:53:13] NOTICE[2053] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 30
[May 21 09:53:23] NOTICE[2053] chan_sip.c: Peer 'VOIPo' is now Reachable. (30ms / 500ms)
[May 21 10:10:25] NOTICE[2053] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 30
[May 21 10:10:46] NOTICE[2053] chan_sip.c: Peer 'VOIPo' is now Reachable. (30ms / 500ms)
[May 21 11:52:50] NOTICE[2053] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 30
[May 21 11:53:00] NOTICE[2053] chan_sip.c: Peer 'VOIPo' is now Reachable. (30ms / 500ms)
[May 21 12:32:02] NOTICE[2053] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 31
[May 21 12:32:12] NOTICE[2053] chan_sip.c: Peer 'VOIPo' is now Reachable. (30ms / 500ms)
[May 21 12:42:14] NOTICE[2053] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 30
[May 21 12:42:24] NOTICE[2053] chan_sip.c: Peer 'VOIPo' is now Reachable. (30ms / 500ms)
[May 21 13:39:27] NOTICE[2053] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 30
[May 21 13:39:37] NOTICE[2053] chan_sip.c: Peer 'VOIPo' is now Reachable. (30ms / 500ms)
[May 21 14:00:38] NOTICE[2053] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 30
[May 21 14:00:48] NOTICE[2053] chan_sip.c: Peer 'VOIPo' is now Reachable. (30ms / 500ms)
[May 21 14:41:51] NOTICE[2053] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 30
[May 21 14:42:45] NOTICE[2053] chan_sip.c: Peer 'VOIPo' is now Reachable. (30ms / 500ms)
[May 21 14:56:46] NOTICE[2053] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 30
[May 21 14:56:56] NOTICE[2053] chan_sip.c: Peer 'VOIPo' is now Reachable. (30ms / 500ms)
[May 21 15:13:58] NOTICE[2053] chan_sip.c: Peer 'VOIPo' is now UNREACHABLE! Last qualify: 30
[May 21 15:14:08] NOTICE[2053] chan_sip.c: Peer 'VOIPo' is now Reachable. (30ms / 500ms)