[WXC/VFX] Problems receiving calls on my VFX line

Forums › One NZ (including Farmside) › [WXC/VFX] Problems receiving calls on my VFX line

tieke

687 posts

Ultimate Geek
+1 received by user: 256

ID Verified

#191328 1-Feb-2016 10:55

Just wondering if anyone else is experiencing this - despite having a dial tone and being able to ring out on my standard SPA2102 VFX line, most of the calls to it are failing. Calls to my number just don't connect, not even to voicemail. I think I had a problem like this several years ago, but port forwarding fixed that (TCP/UDP Ports 8060 – 8065, 5060 – 5065 and UDP Ports 35384 – 37384 directed straight to the SPA2102).

I was alerted to it by someone who ended up calling my cellphone after two calls failed, and I've only been able to connect one out of ten test calls.

I've tried calling technical support, but have just been listening to their "Sultans of Swing" on-hold mix for well over half an hour now, so it might be a more wide-spread thing or there might be a shortage of techs. (Live chat also isn't being responded to).

(What makes it more of a problem is that due to a completely unrelated problem I'm also currently unable to receive calls or txts from Vodafone mobiles to my 2degrees number, so for instance my wife is now completely unable to contact me - once I give up on waiting for WXC tech support to answer the phone I will try 2degrees again :)

sbiddle

30853 posts

Uber Geek
+1 received by user: 9996

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#1482659 1-Feb-2016 10:57

You should never under any circumstances have port forwards to an SPA. The mere fact you had to do this points to a poor router or something like a SIP ALG enabled that was causing issues, and this would be the first thing I'd be looking at now.

tieke

687 posts

Ultimate Geek
+1 received by user: 256

ID Verified

#1482660 1-Feb-2016 11:00

I think it was with a previous router and I just set up the current one the same way - are you saying that this isn't needed? (Although I'm not sure how it would hurt?)

phantomdb

585 posts

Ultimate Geek
+1 received by user: 103

Lifetime subscriber

#1482662 1-Feb-2016 11:04

i had a similar issue on a pfsence box the firewall was cleaning up the ports to fast and breaking the incoming links.

[ SIGNATURE HERE ]

maverick

3594 posts

Uber Geek
+1 received by user: 80

Trusted

WorldxChange

#1482666 1-Feb-2016 11:11

Is the issue still happening ?

Yes I am a employee of WxC (My Profile) ... but I do have my own opinions as well

https://www.facebook.com/wxccommunications

tieke

687 posts

Ultimate Geek
+1 received by user: 256

ID Verified

#1482669 1-Feb-2016 11:13

I did find a SIP helper setting which I have now disabled, so hopefully that helps - just strange that I haven't changed any settings since I installed the router and this has only just started today. Just checked on when I set up the port forwarding, and wxc provided the info in 2012, so the previous issue was definitely on a different router (looks like I've had the current WRT320N for just over a year now.)

cisconz

cisconz
1348 posts

Uber Geek
+1 received by user: 179

ID Verified

Trusted

Lifetime subscriber

#1482673 1-Feb-2016 11:18

I had some DVX that were off for most of the morning, back on about 11 ish.

Hmmmm

Geekzone

Want to support Geekzone and browse the site without the ads? Subscribe to Geekzone now (monthly, annual and lifetime options).

tieke

687 posts

Ultimate Geek
+1 received by user: 256

ID Verified

#1482679 1-Feb-2016 11:22

maverick:

Is the issue still happening ?

Two of my test calls have just worked, so hopefully the problem's gone away - not entirely sure of course, as it was a bit intermittent to start with. Not sure if it was the SIP change as I hadn't been testing for the last hour while I was on hold, so couldn't test after an earlier device reboot etc.

Is it OK to continue having the port forwards on the router?

(On another topic, I think WXC should consider diverting hold calls after half an hour or so, or at least increasing the number of on-hold tunes to more than the current three - I don't need to hear Sultan's of Swing again for a while.)

tieke

687 posts

Ultimate Geek
+1 received by user: 256

ID Verified

#1482681 1-Feb-2016 11:25

cisconz:

I had some DVX that were off for most of the morning, back on about 11 ish.

It would be good to know if it was an issue on WXC's end - I could stop mucking around with my router if it's not the cause of the problem.

RunningMan

9184 posts

Uber Geek
+1 received by user: 4834

#1482714 1-Feb-2016 11:59

tieke:

[snip], but port forwarding fixed that (TCP/UDP Ports 8060 – 8065, 5060 – 5065 and UDP Ports 35384 – 37384 directed straight to the SPA2102).

Make sure you get rid of those port forwards, and sort out whatever the SIP ALG or similar issue is at router level instead. Forwarding these ports should not normally be needed, and can leave the ATA exposed to VoIP hacking and then big phone bills.....

If this is auto provisioned from WXC/VNGS then they know what they're doing and it will be as secure as it can be, but if you have configured this yourself with OpenVFX, I wouldn't be so sure.

tieke

687 posts

Ultimate Geek
+1 received by user: 256

ID Verified

#1482725 1-Feb-2016 12:30

Fair enough - routes have been deleted. It was auto-provisioned, and I think the incoming address for the routes might have been set to 58.28.20.150, so shouldn't have been vulnerable. The previous problem was on a different router though, so the routes probably weren't needed on this one anyway.

cisconz

cisconz
1348 posts

Uber Geek
+1 received by user: 179

ID Verified

Trusted

Lifetime subscriber

#1482997 1-Feb-2016 17:37

tieke:

Fair enough - routes have been deleted. It was auto-provisioned, and I think the incoming address for the routes might have been set to 58.28.20.150, so shouldn't have been vulnerable. The previous problem was on a different router though, so the routes probably weren't needed on this one anyway.

That is the old ip - new one is 182.154.16.150

Hmmmm