[WXC/VFX] [solved] PAP2T can't connect to login server

Forums › One New Zealand (including Vodafone, WxC, Farmside) › [WXC/VFX] [solved] PAP2T can't connect to login server - dyndns problem??

sultanoswing

814 posts

Ultimate Geek

#57064 2-Feb-2010 10:22

I've done some searching here and elsewhere and wonder if dyndns could be interfering with my VFx.

The Problem:
Every 12-24 hours I lose my VFx phone connection. Checking the PAP2T web interface, shows:

Registration State: Can't connect to login server

I have to reboot my router and then PAP2T to re-establish the connection, which works, but then it goes down again several hours later.

Network Setup:
Draytek 110 modem into a linksys WRT54GS router running dd-wrt Ver. 2.4-sp2 vpn
WAN connection through router using PPPoE (via modem's PPPoA > PPPoE passthrough feature)
PAP2T connected to router
Because I've set up an openvpn server on the router I'm also running a dyndns service on the router.

Things I've tried so far:
PAP2T into the DMZ
PAP2T and WRT54GS under DHCP and static IP setups
I didn't get this problem with Tomato 1.25vpn (but the vpn server didn't work properly)

I haven't tried disabling dyndns yet, but thought I'd ask here first. I'll also do some more searching around the dd-wrt forums too. I suppose I could pony up $10/month for a static IP from Xnet to access the VPN, but my cheapness is preventing me just yet.

Any immediate thoughts / suggestions?

[UPDATE] network configuration updated

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#295333 2-Feb-2010 10:59

Probably not, as generally the setup isn'nt using dns for your registration details IP only, most likely something is either blocking the messages coming back or there is a SIP nat issue.

That message is telling you that it is not seeing any SIP messages coming back from the network, now will almost bet the house that they are being sent back but not being received by the unit, we have seen issues with the pap2t and routers when they change public IP's and the natting info is then not passed / updated for SIP natted devices but usually with chaeper dlink / dynalinks , Draytek are a very good brand and havn't every heard of an issue with them.

Drop me a pm next tiome it happens and I will take a look and see if I notice anything out of the ordinary.

A quick way to possibly check this is to quickly drop your dsl connection (just unplug it for a second or 2) then see what happens on the PAP2T , check the Line Status LED within 3 minutes the device will try to reregister so if this si the issue it should occur within this time period.

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

https://www.facebook.com/wxccommunications

Mighty Ape

Shop Mighty Ape for electronics, games, computers books and more (affiliate link).

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#295339 2-Feb-2010 11:28

Found your account details and had a quick look as I see you had the issue this morning.

Looks to be as I thought with the challange we send back to you isn't getting back as the challenge is never responded to and the unit just keeps sending the original register message and because the unit is saying can't cotact login server it's teling us that it is not seeing the SIP replies, however they are being sent in this case to the Public IP and yur router should send it to 192.168.1.4, the issue does appear to be a nat problem with that router, Public IP could Fix it , could try it for a month and see if it makes a difference ?

Via: SIP/2.0/UDP 192.168.1.4:5060;received=118.90.xxx.xxx

Session ID : 0x08C3869E08F85CA9

REGISTER sip:as.wxcnz.net SIP/2.0
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK-571e73d8
From: 0784xxxx4 <sip:784xxxx4@as.wxcnz.net>;tag=9ed901dba6519a9o0
To: 0784xxxx4 <sip:784xxxx4@as.wxcnz.net>
Call-ID: 64ab0c76-3b0da11a@192.168.1.4
CSeq: 31254 REGISTER
Max-Forwards: 70
Contact: 0784xxxx4 <sip:784xxxx4@192.168.1.4:5060>;expires=180
User-Agent: Linksys/PAP2T-5.1.6(LS)
Content-Length: 0
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER
Supported: 100rel, x-sipura, replaces

----------------------------------------
Timestamp     : 08:35:27.467 2010-02-02
Direction     : TX
Remote IP/Port: 118.90.xxx.xxx/5060
Local IP/Port : 58.28.xxx.xxx/5060
Transport     : UDP
----------------------------------------
SIP/2.0 401 Unauthorized
From: "0784xxxx4" <sip:784xxxx4@as.wxcnz.net>;tag=9ed901dba6519a9o0
To: "0784xxxx4" <sip:784xxxx4@as.wxcnz.net>
Call-ID: 64ab0c76-3b0da11a@192.168.1.4
CSeq: 31254 REGISTER
Via: SIP/2.0/UDP 192.168.1.4:5060;received=118.90.xxx.xxx;branch=z9hG4bK-571e73d8;rport=5060
WWW-Authenticate: DIGEST realm="xport.co.nz", nonce="BroadWorksXg55nulmvT6pholmBW", algorithm=MD5, qop="auth"
Content-Length: 0

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

----------------------------------------
Timestamp     : 08:35:27.961 2010-02-02
Direction     : RX
Remote IP/Port: 118.90.xxx.xxx/5060
Local IP/Port : 58.28.xxx.xxx/5060
Transport     : UDP
----------------------------------------
REGISTER sip:as.wxcnz.net SIP/2.0
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK-571e73d8
From: 0784xxxx4 <sip:784xxxx4@as.wxcnz.net>;tag=9ed901dba6519a9o0
To: 0784xxxx4 <sip:784xxxx4@as.wxcnz.net>
Call-ID: 64ab0c76-3b0da11a@192.168.1.4
CSeq: 31254 REGISTER
Max-Forwards: 70
Contact: 0784xxxx4 <sip:784xxxx4@192.168.1.4:5060>;expires=180
User-Agent: Linksys/PAP2T-5.1.6(LS)
Content-Length: 0
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER
Supported: 100rel, x-sipura, replaces

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

----------------------------------------
Timestamp     : 08:35:27.962 2010-02-02
Direction     : TX
Remote IP/Port: 118.90.xxx.xxx/5060
Local IP/Port : 58.28.xxx.xxx/5060
Transport     : UDP
----------------------------------------
SIP/2.0 401 Unauthorized
From: "0784xxxx4" <sip:784xxxx4@as.wxcnz.net>;tag=9ed901dba6519a9o0
To: "0784xxxx4" <sip:784xxxx4@as.wxcnz.net>
Call-ID: 64ab0c76-3b0da11a@192.168.1.4
CSeq: 31254 REGISTER
Via: SIP/2.0/UDP 192.168.1.4:5060;received=118.90.xxx.xxx;branch=z9hG4bK-571e73d8;rport=5060
WWW-Authenticate: DIGEST realm="xport.co.nz", nonce="BroadWorksXg55nulmvT6pholmBW", algorithm=MD5, qop="auth"
Content-Length: 0

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

----------------------------------------
Timestamp     : 08:35:28.961 2010-02-02
Direction     : RX
Remote IP/Port: 118.90.xxx.xxx/5060
Local IP/Port : 58.28.xxx.xxx/5060
Transport     : UDP
----------------------------------------
REGISTER sip:as.wxcnz.net SIP/2.0
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK-571e73d8
From: 0784xxxx4 <sip:784xxxx4@as.wxcnz.net>;tag=9ed901dba6519a9o0
To: 0784xxxx4 <sip:784xxxx4@as.wxcnz.net>
Call-ID: 64ab0c76-3b0da11a@192.168.1.4
CSeq: 31254 REGISTER
Max-Forwards: 70
Contact: 0784xxxx4 <sip:784xxxx4@192.168.1.4:5060>;expires=180
User-Agent: Linksys/PAP2T-5.1.6(LS)
Content-Length: 0
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER
Supported: 100rel, x-sipura, replaces

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

----------------------------------------
Timestamp     : 08:35:28.963 2010-02-02
Direction     : TX
Remote IP/Port: 118.90.xxx.xxx/5060
Local IP/Port : 58.28.xxx.xxx/5060
Transport     : UDP
----------------------------------------
SIP/2.0 401 Unauthorized
From: "0784xxxx4" <sip:784xxxx4@as.wxcnz.net>;tag=9ed901dba6519a9o0
To: "0784xxxx4" <sip:784xxxx4@as.wxcnz.net>
Call-ID: 64ab0c76-3b0da11a@192.168.1.4
CSeq: 31254 REGISTER
Via: SIP/2.0/UDP 192.168.1.4:5060;received=118.90.xxx.xxx;branch=z9hG4bK-571e73d8;rport=5060
WWW-Authenticate: DIGEST realm="xport.co.nz", nonce="BroadWorksXg55nulmvT6pholmBW", algorithm=MD5, qop="auth"
Content-Length: 0

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

----------------------------------------
Timestamp     : 08:35:30.961 2010-02-02
Direction     : RX
Remote IP/Port: 118.90.xxx.xxx/5060
Local IP/Port : 58.28.xxx.xxx/5060
Transport     : UDP
----------------------------------------
REGISTER sip:as.wxcnz.net SIP/2.0
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK-571e73d8
From: 0784xxxx4 <sip:784xxxx4@as.wxcnz.net>;tag=9ed901dba6519a9o0
To: 0784xxxx4 <sip:784xxxx4@as.wxcnz.net>
Call-ID: 64ab0c76-3b0da11a@192.168.1.4
CSeq: 31254 REGISTER
Max-Forwards: 70
Contact: 0784xxxx4 <sip:784xxxx4@192.168.1.4:5060>;expires=180
User-Agent: Linksys/PAP2T-5.1.6(LS)
Content-Length: 0
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER
Supported: 100rel, x-sipura, replaces

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

----------------------------------------
Timestamp     : 08:35:30.962 2010-02-02
Direction     : TX
Remote IP/Port: 118.90.xxx.xxx/5060
Local IP/Port : 58.28.xxx.xxx/5060
Transport     : UDP
----------------------------------------
SIP/2.0 401 Unauthorized
From: "0784xxxx4" <sip:784xxxx4@as.wxcnz.net>;tag=9ed901dba6519a9o0
To: "0784xxxx4" <sip:784xxxx4@as.wxcnz.net>
Call-ID: 64ab0c76-3b0da11a@192.168.1.4
CSeq: 31254 REGISTER
Via: SIP/2.0/UDP 192.168.1.4:5060;received=118.90.xxx.xxx;branch=z9hG4bK-571e73d8;rport=5060
WWW-Authenticate: DIGEST realm="xport.co.nz", nonce="BroadWorksXg55nulmvT6pholmBW", 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

sultanoswing

814 posts

Ultimate Geek

#295342 2-Feb-2010 11:31

Cheers maverick.

The PAP2T is logged in an connected again. dyndns enabled. DHCP server on router enabled, but with static MAC IP (192.168.1.4) for the PAP2T which has its DCHP disabled. Primary and secondary DNS are filled in anyway (58.28.5.2, 58.28.6.2) on the PAP2T.

Unplugged the DSL line (i.e. LAN cable from router) from the PAP2T for ten seconds until the LED's went out. Replugged and it synced straight away. Now - will it STAY synced, is the question!

If it continues to be a problem & I can't find another solution, I may have to try a static IP.

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#295345 2-Feb-2010 11:38

Actually can you unplug the DSL not the ethernet side and see how that goes, just long enough for your dsl connection on the router to drop then replug it, the theory is that it's the change of public IP on the router not getting SIP natted back to your PAP2T which is the problem.

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

https://www.facebook.com/wxccommunications

sultanoswing

814 posts

Ultimate Geek

#295474 2-Feb-2010 17:33

I've flashed to a different version of dd-wrt (mega 2.4 sp2 build 13064) and so far, so good for the last few hours. No uPnP, port forwarding or DMZ set up and phone is dialing out and receiving as expected. VPN server and dyndns are also both running.

/me holds breath....

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#295476 2-Feb-2010 17:36

me waits

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

https://www.facebook.com/wxccommunications

sultanoswing

814 posts

Ultimate Geek

#295694 3-Feb-2010 12:59

Well, it's been more than 24 hours since last disconnection, so I'm assuming all has been solved by changing router firmware and / or hard-resetting the router prior to setting everything back up.

Thanks again for your advice, maverick. You saved the call centre some time :)

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#295697 3-Feb-2010 13:03

No problem

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

https://www.facebook.com/wxccommunications

remarks

33 posts

Geek

#300550 20-Feb-2010 17:51

sultanoswing: I've done some searching here and elsewhere and wonder if dyndns could be interfering with my VFx.

The Problem:
Every 12-24 hours I lose my VFx phone connection. Checking the PAP2T web interface, shows:

Registration State: Can't connect to login server

I have to reboot my router and then PAP2T to re-establish the connection, which works, but then it goes down again several hours later.

I've had this problem on and off for coming up 3 years now. I've always had a Linksys WRT54GL or WRT54G2. I've tried many different firmware and network configurations. I also have a dynamic IP address.

I've set up VFX for 5 other households and the instructions I give them are to switch everything off then on to get it back up and running.

This issue seems to pop up on this forum now and then and it usually always seems to be with people running Linksys routers.

sultanoswing

814 posts

Ultimate Geek

#300554 20-Feb-2010 18:03

Well my current, 100% working setup is:

Linksys WRT54GS v.2 with dd-wrt 2.4 'mega' sp2 build 13064 with the following setup:
Static lease assinged to the PAP2T (192.168.1.4) through the router
SPI router firewall enabled
Router DHCP server enabled
uPNP disabled
No forwarded ports, port ranges or triggering are set
DMZ not enabled

PAPT2 settings (under 'System'):
DCHP no
Static IP (192.168.1.4)
Gateway 192.168.1.1 (router's address)
Netmask 255.255.255.0 (same as LAN)
Hostname 'PAP2T'
Primary and secondary DNS's are Xnet's: 58.28.5.2 and 58.28.6.2

Hope these may help you!

remarks

33 posts

Geek

#300562 20-Feb-2010 18:21

Thanks for the reply.

My VFX stays up for around a week sometimes with my current configuration - but then sometimes it may go down twice in a day.

It would be my thinking that having the SPI firewall enabled would actually make it more likely to stop (maybe my understanding of SPI is wrong). Most forums I have read about this issue have said 'disable SPI'.

I have always had a static IP address for the PAP2T - not sure if setting a static lease in the router as well would make any difference.

I have uPNP disabled and have tried with and without forwarded ports as well as DMZ on and off.

A more systematic process of elimination would be required but it would take such a long time to test all the different scenarios ;)

I'll keep playing and post any updates...