[WXC/VFX] Moved Asterisk box and I've stuffed something up, not getting incoming calls

Forums › One New Zealand (including Vodafone, WxC, Farmside) › [WXC/VFX] Moved Asterisk box and I've stuffed something up, not getting incoming calls

aw

286 posts

Ultimate Geek

#77444 16-Feb-2011 16:09

I need a little help here with something I've stuffed up.

I had an Asterisk box running on a home server and it's time to migrate machines (old to new) and distros (openSUSE to CentOS).

I compiled a fresh Asterisk+FreePBX install on the new box, copied over the config from the old box (I'd moved MySQL and other services earlier).

I've solved all issues migrating bar one.

I can't receive incoming calls. My personal line goes straight to voicemail and my home office line is being forwarded to my cellphone (as they both should when the * box is down).

Thing is, it's up.

Outgoing calls are 100% fine.
SIP from my mobile over VoIP and over 3G also remains fine when I make calls between extensions, local and remote.

Wireshark seems to show successful SIP registrations with WxC (coming back with 200 OK), but when I place a call from py PSTN line, with Wireshark's filter set to "net 58.28.0.0/16 and udp", no activity is shown at all relating to the incoming call.

It seems that my * box is registering, but not quite properly, and I can't quite figure out what I've screwed up.

The only change I know I've made is changing all references to as.wxcnz.net to pan.wxnz.net. I tried changing these back on one of the lines and re-added the appropriate entry in /etc/hosts but when I did that registration packets seemed to go unanswered. I've changed it back again to pan.wxnz.net.

Port forwarding on the Dynalink router is on for TCP 5060 and UDP 5060, 8000-8500 and 20000-20500. SIP ALG is OFF. Previous experimentation showed that it works both ON and OFF as the * box is the only thing that talks SIP between my home net and the internet, all other SIP traffic is local.
rtp.conf has the RTP port range set at 20000-20500 for remote extensions (my cellphone).

sip_general_custom.conf has nat=yes, externip=(my static IP) and localnet=(my local IP range).

Anything obvious I'm missing?

1 | 2

3594 posts

Uber Geek

Trusted

WorldxChange

#440323 16-Feb-2011 16:27

Your sending us a 410 Gone message ..... Invite is going to you and your responding with a 410

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

https://www.facebook.com/wxccommunications

aw

286 posts

Ultimate Geek

#440331 16-Feb-2011 16:43

Thanks Maverick for the fast reply!

Bizarre. If I comment out the NAT settings in rtp.conf it all comes right. That's the opposite of the behaviour I'd expect.

Of course I need that on for my remote extensions.

I've now added localnet=58.28.20.150/255.255.255.255 into my rtp.conf. A couple of test calls shows it seems to be working like that, but by my understanding that should have broken it, not fixed it!

Any SIP gurus know why that'd be?

aw

286 posts

Ultimate Geek

#440394 16-Feb-2011 18:54

Spoke too soon, that didn't fix it. Now no matter what I try, one line always works (the WxC native one), and the other always fails (the ported Woosh 940 number, not that that's relevant, it'll just help Maverick tell which numbers I'm talking about).

I'll keep at it this evening unless it drives me too crazy. I've disabled the working line so I can focus on the not-working one.

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#440400 16-Feb-2011 19:00

aw: Thanks Maverick for the fast reply!

Bizarre. If I comment out the NAT settings in rtp.conf it all comes right. That's the opposite of the behaviour I'd expect.

Of course I need that on for my remote extensions.

I've now added localnet=58.28.20.150/255.255.255.255 into my rtp.conf. A couple of test calls shows it seems to be working like that, but by my understanding that should have broken it, not fixed it!

Any SIP gurus know why that'd be?

You mean SIP.conf?

aw

286 posts

Ultimate Geek

#440402 16-Feb-2011 19:08

Yeah, sip.conf - specifically sip_general_custom.conf as this is a FreePBX install. I have no idea why I said rtp.conf.

aw

286 posts

Ultimate Geek

#440405 16-Feb-2011 19:17

I wonder if the whole thing is being mucked up by a corrupt registration or something with all the restarts I've been doing? I've gone through profile settings for both lines, and besides the number and auth info, they're both configured exactly alike. I'm starting to think that if it were at my end, both, or neither of my lines should be working now, not just one.

Even tried routing it through my backup connection (2D USB modem on a gateway), same result.

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#440407 16-Feb-2011 19:23

It's always a good idea to register with as.wxnz.net and load this in your hosts file anyway. This can minimise the effects of the well known Asterisk DNS failing where internal calls are not possible if the internet goes down.

Wise

Send money globally for less with Wise - one free transfer up to NZ$900 (affiliate link).

aw

286 posts

Ultimate Geek

#440408 16-Feb-2011 19:23

Maverick, you still at work? I just spotted that test call :)

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#440409 16-Feb-2011 19:24

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

https://www.facebook.com/wxccommunications

aw

286 posts

Ultimate Geek

#440410 16-Feb-2011 19:26

Haha I almost answered that second one in time too. I guess that means it's working - cheers :)

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#440411 16-Feb-2011 19:28

Your all good now, a corrupted cached registration was the issue

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

https://www.facebook.com/wxccommunications

aw

286 posts

Ultimate Geek

#440414 16-Feb-2011 19:30

Yeah all those changes and restarts I did earlier in the day probably mucked it up. Thanks so much for the fix!

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#440447 16-Feb-2011 20:27

aw: Maverick, you still at work? I just spotted that test call :)

That man never sleeps!

DonGould

3892 posts

Uber Geek

#440459 16-Feb-2011 20:57

maverick: Your all good now, a corrupted cached registration was the issue

This might be a dumb question... but is that something the user end can detect and fix?

Promote New Zealand - Get yourself a .kiwi.nz domain name!!!

Check out mine - i.am.a.can.do.kiwi.nz - don@i.am.a.can.do.kiwi.nz

aw

286 posts

Ultimate Geek

#440467 16-Feb-2011 21:28

It wasa combination of reading this thread, the fact that one line was working while the other wasn't, and the knowledge that I'd restarted Asterisk dozens of times troubleshooting the original issue that alerted me to the possibility that it might be a bad reg.

I guess a dodgy internet connection could also set something like that off, but the average end user wouldn't be migrating an Asterisk PBX then restarting it every minute for most of the day!!

(I also had issues with the NZ voice recordings, permissions and all sorts of other stuff that had me restarting it dozens of times, followed by the (I think) NAT issue that started this thread, before then hitting this problem with just one of the two trunk lines, so that's a lot of restarts)

But I guess that fault should self-correct when the bad registration expires. By the way Phil, just curious, how long would that have been if it had not been manually reset?

1 | 2