Connectivity Issues with sip.voipwelcome.com

[stenger]

No issues any more here after the switch.

Thanks.

[GreenLantern]

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]

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]

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]

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]

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]

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]

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)