[WXC/VFX] Inbound calls not working

Forums › One NZ (including Farmside) › [WXC/VFX] Inbound calls not working

BigGuy

227 posts

Master Geek
+1 received by user: 26

#148857 3-Jul-2014 00:05

Hi,
My inbound calls have stopped working (OpenVFX).
It's been happening for about a month now, but I've been very lazy and have just gotten around to looking at the issue.

One thing I've noticed is that I frequently get the message "[2014-07-02 23:52:04] NOTICE[2999]: chan_sip.c:15135 sip_reg_timeout: -- Registration for 'xxxxxxxx@pan.wxnz.net' timed out, trying again (Attempt #51)"

Out bound calls are perfectly fine BTW.

There haven't been any changes to the environment (other than a SonicWall firmware update I did a while ago).

I can ping pan.wxnz.net (182.154.16.150) fine.

Other information:
CLI> sip show channels
Peer User/ANR Call ID Format Hold Last Message Expiry Peer
182.154.16.150 xxxxxxxx 483333333333335 (nothing) No <guest>

CLI> sip show peers
Name/username Host Dyn Forcerport Comedia ACL Port Status Description
VFX/abcdefghijklmnopqr 182.154.16.150 Yes Yes 5060 OK (21 ms)

I'm on an Orcon connection (for what it's worth).

Any ideas anyone?

Cheers

This is a filtered page: currently showing replies marked as answers. Click here to see full discussion.

Cameronn

334 posts

Ultimate Geek
+1 received by user: 3

Trusted

WorldxChange

#1079085 3-Jul-2014 08:34

Could potentially be a firewall issue, can you make an inbound call straight after an outbound?

I'll see if we can have a look at your registrations attempts and see if I can spot anything odd.

PM me your details - account number or phone number would be suitable.

sbiddle

30853 posts

Uber Geek
+1 received by user: 9996

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#1079089 3-Jul-2014 08:45

Do you have firewall rules restricting your SIP traffic and if so did you update these when WxC changed their IP addresses?

BigGuy

227 posts

Master Geek
+1 received by user: 26

#1079259 3-Jul-2014 11:23

So it turned out to be a couple of things.
1/ external rule had not been updated.
2/ external NAT entry had not been updated.

Thanks for the pointers guys. I started looking at it late last night and couldn't see the forest for the trees!