[WXC/VFX] VFX on Asterisk - one line working, one not

Forums › Vodafone New Zealand › [WXC/VFX] VFX on Asterisk - one line working, one not

aw

273 posts

Ultimate Geek
+1 received by user: 7

Subscriber

Topic # 82186 23-Apr-2011 13:10

Hi Maverick and all,

Last week I noticed one of our lines wasn't accepting calls (the one starting with 950). Outgoing calls on both lines are fine (both on Asterisk).

I started playing around with settings in Asterisk and my firewall (ALG, NAT and so on) but have not managed to find nor fix the issue. I must stress that I started going through everything *after* the fault, however the server this was on did suffer from a full disc a few days earlier, although that was freed up and the server then restarted. I don't know if the two issues are coincidental or not. We may not have noticed the issue for a couple of days, or it may not have happened for a couple of days.

We have two trunk lines. The (ported) one starting with 940 works fine. The other one starting with 950 can place but not receive calls, they go instantly to the voice portal.

"sip show registry" shows both trunks as registered.

endeavour*CLI> sip show registry
Host                            Username       Refresh State                Reg.Time
pan.wxnz.net:5060               9940XXXX           285 Registered           Sat, 23 Apr 2011 13:07:57
pan.wxnz.net:5060               9950XXXX           285 Registered           Sat, 23 Apr 2011 13:07:57

Any ideas as to what to check next? A few months ago the same problem was caused by a corrupt SIP registration, but this time I waited several days for that to clear before doing anything.

Cheers,

Andrew

maverick

3594 posts

Uber Geek
+1 received by user: 79

Trusted

WorldxChange

Reply # 461780 23-Apr-2011 13:49

Your on the same port probably, make sure one line is on 5060 the other on 5061, pan is fine on 5060 but make both your lines 950xxxx and 940xxxx are on different ports

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

https://www.facebook.com/wxccommunications

aw

273 posts

Ultimate Geek
+1 received by user: 7

Subscriber

Reply # 461814 23-Apr-2011 16:27

Hi Phil,

I tried 5061 (as in register string being "9950XXXX:abcdef12345:uvwxyz67890@pan.wxnz.net:5061/9950XXXX") but I got no response from pan (state stays as "Request Sent". Am I doing that right? Tired mapping 5061->5061 and alternately 5061->5060 at the firewall.

Since trying that I changed the 950 number back to using port 5060 and it is again showing "Registered".

For troubleshooting purposes I've disabled the 940 trunk so the 950 is now the only one registering, but the 950 still goes direct to WxC voicemail. I did this two minutes before hitting "send", will check if it's still the case in 5 mins when the 940 reg times out.

edit: oh and having both on 5060 used to work up until this week...

maverick

3594 posts

Uber Geek
+1 received by user: 79

Trusted

WorldxChange

Reply # 461839 23-Apr-2011 18:47

You will have some sort of natting happening which is most likely your issue here, generally having the same internal port for both numbers causes problems as the nat rules , sip alg don't handle it very well, trying 5061 at the VFX will never work this is not a SIP port, only 5060 and 8060

you need to have this

You                  VFX (pan.wxnz,net)
950xxxx 5060       5060
940xxxx 5061       5060

Send me the numbers and I will take a look for you but you will probably need to set one of your numbers up on 5061 local port at your end.

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

https://www.facebook.com/wxccommunications

aw

273 posts

Ultimate Geek
+1 received by user: 7

Subscriber

Reply # 461862 23-Apr-2011 19:58

Thanks, Phil, PM sent.

Since sending the PM I've disabled the 940xxxx trunk again to try to get the 950xxxx number going, once that's up I'll re-enable the 940.

Andrew

maverick

3594 posts

Uber Geek
+1 received by user: 79

Trusted

WorldxChange

Reply # 461975 24-Apr-2011 16:06

Hi Andrew,

Sorry been out today so have just picked this up,

you are replying from a PAP2 with a SIP 410 gone message , this is why you are going directly to Voice Message your PAP2 is telling us the number is not there so so we send it to VM as this is what you have set up for Call Forward unreachable.... so I would take a look at the PAP2 in this case and see if it is registered and what it is registered , your outbound is fine it's your inbound which has somehow screwed up locally but start with your PAP2 would be my suggestion as this is the device which is replying.

Timestamp : 15:54:26.466 2011-04-24
Direction : TX
Remote IP/Port: 58.xxx.xxx.33/5060
Local IP/Port : 58.28.xxx.xxx(vx2)/5060
Transport : UDP
----------------------------------------
INVITE sip:995xxxx5@58.xxx.xxx.33;transport=udp SIP/2.0
From: "Phillip Moore" <sip:09950xxxx>;tag=3201400a-13c4-4db39ef2-34cf7a4d-7ee31d17
To: "Andrew Walters" <sip:9950xxx5@as.wxcnz.net;rinstance=4db39e53618b6825>
Call-ID: BW1554263842404111714346583
CSeq: 1 INVITE
Via: SIP/2.0/UDP 58.xxx.xxx.xxx:5060;branch=z9hG4bK-4a338-4db39ef2-34cf7a4d-105a9504
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE
Accept: multipart/mixed,application/media_control+xml,application/sdp
Max-Forwards: 9
Contact: <sip:0995xxxx:5060;maddr=58.xxx.xxx.xxx;transport=udp>
Content-Type: application/sdp
Content-Length: 314

v=0
o=BroadWorks 20559953 1 IN IP4 xxx.xxx.xxx.xxx
s=-
c=IN IP4 xxx.xxx.xxx.xxx
t=0 0
m=audio 35696 RTP/AVP 9 8 0 18 101
a=rtpmap:9 G722/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729a/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=bsoft:1 image udptl t38
a=sendrecv

----------------------------------------

----------------------------------------
Timestamp : 15:54:26.511 2011-04-24
Direction : RX
Remote IP/Port: 58.xxx.xxx.33/5060
Local IP/Port : 58.xxx.xxx.xxx(vx2)/5060
Transport : UDP
----------------------------------------
SIP/2.0 410 Gone
To: "Andrew Walters" <sip:9950xxx5;rinstance=4db39e53618b6825>;tag=ebdbfae57c486d62i0
From: "Phillip Moore" <sip:09950xxxx>;tag=3201400a-13c4-4db39ef2-34cf7a4d-7ee31d17
Call-ID: BW1554263842404111714346583
CSeq: 1 INVITE
Via: SIP/2.0/UDP xxx.xxx.xxx:5060;branch=z9hG4bK-4a338-4db39ef2-34cf7a4d-105a9504
Server: Linksys/PAP2T-5.1.6(LS)
Content-Length: 0

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

https://www.facebook.com/wxccommunications

aw

273 posts

Ultimate Geek
+1 received by user: 7

Subscriber

Reply # 462720 26-Apr-2011 20:01

Thanks Phil,

I'm now overseas for a while so I'm limited in what I can do remotely to stop that.

The PAP2T box is WxC provisioned and used to be for that 950 number. Line 2 is unlocked and is set up as an extension on Asterisk. I didn't reset the PAP2 because it didn't seem to be a problem.

I've blocked all UDP traffic from it at the firewalll, hopefully that'll be enough til I can factory reset it when I'm back.

Thanks,

Andrew

aw

273 posts

Ultimate Geek
+1 received by user: 7

Subscriber

Reply # 462724 26-Apr-2011 20:04

Can't edit posts on GZ mobile, clarification of above post:

I didn't reset the PAP when we shifted the 950 number from it to Asterisk a year ago as I assumed line 1 details had been cleared at the time that line was moved from it to Asterisk.

maverick

3594 posts

Uber Geek
+1 received by user: 79

Trusted

WorldxChange

Reply # 462854 27-Apr-2011 08:21

Argh okay, so something was forwarding off to that device so that explains the response, I also see now that there appears to be an issue with your SIP natting as it looks like you do not see the challenge for your registers as you don't send the auth details after we send the unauthorized,this normally indiactes a sip natting issue,

No rush since your overseas I will be here when you get back

Timestamp     : 08:00:28.292 2011-04-27
Direction     : TX
Remote IP/Port: 58.xxx.xxx.33/5060
Local IP/Port : 58.xxx.xxx.150(vx2)/5060
Transport     : UDP
----------------------------------------
SIP/2.0 401 Unauthorized
From: <sip:9950xxx5@pan.wxnz.net>;tag=as39c746c4
To: <sip:9950xxx5@pan.wxnz.net>
Call-ID: 7a033d623a4db3817e6b0ebc2437e291@192.168.1.63
CSeq: 2311 REGISTER
Via: SIP/2.0/UDP 58.xxx.xxx.33:5060;branch=z9hG4bK700d0e98
WWW-Authenticate: DIGEST realm="xport.co.nz", nonce="xxxxxxxxxxxxxxxxxxxxxxxxxx", algorithm=MD5, qop="auth"
Content-Length: 0

----------------------------------------

----------------------------------------
Timestamp     : 08:00:29.287 2011-04-27
Direction     : RX
Remote IP/Port: 58.xxx.xxx.33/1024
Local IP/Port : 58.xxx.xxx.150(vx2)/5060
Transport     : UDP
----------------------------------------
REGISTER sip:pan.wxnz.net SIP/2.0
Via: SIP/2.0/UDP 58.xxx.xxx.33:5060;branch=z9hG4bK700d0e98
From: <sip:9950xxx5@pan.wxnz.net>;tag=as39c746c4
To: <sip:9950xxx5@pan.wxnz.net>
Call-ID: 7a033d623a4db3817e6b0ebc2437e291@192.168.1.63
CSeq: 2311 REGISTER
User-Agent: FPBX-2.6.0(1.4.39.1)
Max-Forwards: 70
Expires: 120
Contact: <sip:9950xxx5@58.xxx.xxx.33>
Event: registration
Content-Length: 0

----------------------------------------

----------------------------------------
Timestamp     : 08:00:29.288 2011-04-27
Direction     : TX
Remote IP/Port: 58.xxx.xxx.33/5060
Local IP/Port : 58.xxx.xxx.150(vx2)/5060
Transport     : UDP
----------------------------------------
SIP/2.0 401 Unauthorized
From: <sip:9950xxx5@pan.wxnz.net>;tag=as39c746c4
To: <sip:9950xxx5@pan.wxnz.net>
Call-ID: 7a033d623a4db3817e6b0ebc2437e291@192.168.1.63
CSeq: 2311 REGISTER
Via: SIP/2.0/UDP 58.xxx.xxx.33:5060;branch=z9hG4bK700d0e98
WWW-Authenticate: DIGEST realm="xport.co.nz", nonce="xxxxxxxxxxxxxxxxxxxxxxxxxx", algorithm=MD5, qop="auth"
Content-Length: 0

----------------------------------------

----------------------------------------
Timestamp     : 08:00:30.287 2011-04-27
Direction     : RX
Remote IP/Port: 58.xxx.xxx.33/1024
Local IP/Port : 58.xxx.xxx.150(vx2)/5060
Transport     : UDP
----------------------------------------
REGISTER sip:pan.wxnz.net SIP/2.0
Via: SIP/2.0/UDP 58.xxx.xxx.33:5060;branch=z9hG4bK700d0e98
From: <sip:9950xxx5@pan.wxnz.net>;tag=as39c746c4
To: <sip:9950xxx5@pan.wxnz.net>
Call-ID: 7a033d623a4db3817e6b0ebc2437e291@192.168.1.63
CSeq: 2311 REGISTER
User-Agent: FPBX-2.6.0(1.4.39.1)
Max-Forwards: 70
Expires: 120
Contact: <sip:9950xxx5@58.xxx.xxx.33>
Event: registration
Content-Length: 0

----------------------------------------

----------------------------------------
Timestamp     : 08:00:30.289 2011-04-27
Direction     : TX
Remote IP/Port: 58.xxx.xxx.33/5060
Local IP/Port : 58.xxx.xxx.150(vx2)/5060
Transport     : UDP
----------------------------------------
SIP/2.0 401 Unauthorized
From: <sip:9950xxx5@pan.wxnz.net>;tag=as39c746c4
To: <sip:9950xxx5@pan.wxnz.net>
Call-ID: 7a033d623a4db3817e6b0ebc2437e291@192.168.1.63
CSeq: 2311 REGISTER
Via: SIP/2.0/UDP 58.xxx.xxx.33:5060;branch=z9hG4bK700d0e98
WWW-Authenticate: DIGEST realm="xport.co.nz", nonce="xxxxxxxxxxxxxxxxxxxxxxxxxx", algorithm=MD5, qop="auth"
Content-Length: 0

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

https://www.facebook.com/wxccommunications

aw

273 posts

Ultimate Geek
+1 received by user: 7

Subscriber

Reply # 463796 29-Apr-2011 18:11

Switching the firewall ALG back on seems to have fixed that although I haven't tested an incoming call yet as I haven't had a chance to have my phone register remotely for a decent length of time.

Will see if I can test today.

I don't get why port forwarding UDP 5060 doesn't seem to work without the ALG on, something to figure out when I'm back.

Thanks for all your help!

aw

273 posts

Ultimate Geek
+1 received by user: 7

Subscriber

Reply # 472439 22-May-2011 16:30

Arrived home, factory reset the PAP2 to get rid of the (very old) VFX provisioning, set it up exclusively as a client of the local PABX, and tested both trunks look OK for incoming calls.

Looks like the PAP was the cause. Why it would start after working fine for a year I don't know, but it looks to be fixed now.

Thanks for the pointer to the PAP from the headers you saw, without that I may have never figured out the PAP was the problem.

edit: Likely the PAP2 was also confusing my router's SIP ALG.