[WXC/VFX] WAG160N and PAP2T - VOIP line disconnects after ADSL line drops

Forums › One NZ (including Farmside) › [WXC/VFX] WAG160N and PAP2T - VOIP line disconnects after ADSL line drops

YB

5 posts

Wannabe Geek

#29739 17-Jan-2009 11:04

Hi guys,

I need a help. I bought a Linksys WAG160N and a PAP2T as my VOIP solution. They work fine but when my ADSL line drops, my VOIP line 1 disconnects and never comes back up automatically. The only way to bring it back up is to 1) manually change the IP address of the ATA device or 2) restart the router.

I tried many things but none solved my problem: upgraded firmware on both devices, configured port forwarding and port triggering on the router (5060), configured the ATA for DHCP and static IP address. I just can't get it to reconnect automatically. What makes it really bad is that every night my monitored alarm disconnects my ADSL.

I have been reading on this forum similar issues (one case with a Dynalink Router, I think Phil from WorldXChange was advising somebody).

Linksys support can only advise me to get a replacement for those, which I don't think is going to solve the problem.

Please, please! Can somebody help me?

Thank you very much,

YB

sbiddle

30853 posts

Uber Geek
+1 received by user: 9996

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#190158 17-Jan-2009 12:38

Does your internet connection come back up OK?

YB

5 posts

Wannabe Geek

#190161 17-Jan-2009 12:56

Hi Steve,

Yes, the Internet connection comes back up ok. My wired and wireless devices instantly reconnect to the Internet but not the ATA.

I have been doing some new tests - I got an old Dlink ADSL router 504G I had stored in the attic, powered it on and connected my computer and ATA. Then I simulated the ADSL line drop (disconnected the phone line from the back of the router). I waited for line1 in the ATA to drop off and then I reconnected the phone line in the Dlink router. It worked like magic, 30 seconds later the ATA line 1 was available again and the registration status was showing the device back online.

With these results, I can only imagine there is a problem with the WAG160N firmware. Called Linksys again, they want me to RMA the router. No matter how many times I say "I think it is a software issue" they keep asking me to go back to the store and get a replacement (BTW, the firmware its running is 1.00.10)

I am thinking in replacing the router - but by another model or even another brand...

Cheers,

Yehudi

sbiddle

30853 posts

Uber Geek
+1 received by user: 9996

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#190165 17-Jan-2009 13:05

Try giving the ATA a static IP and then putting this IP on a DMZ and see if that resolves it.

YB

5 posts

Wannabe Geek

#190176 17-Jan-2009 13:48

Good idea. I tried, but it doesn't work. I am so frustrated with this router... I bought both devices Linksys thinking, "they have to work well together, they are made by the same manufacturer". What a mistake.

old3eyes

9158 posts

Uber Geek
+1 received by user: 1364

Subscriber

#190224 17-Jan-2009 19:28

Have a look thru this site..

http://forums.linksys.com/linksys/board?board.id=VoIP_Adapters

Regards,

Old3eyes

YB

5 posts

Wannabe Geek

#190343 18-Jan-2009 11:59

Hi there,

Thanks for the url. I found people with similar issues on the Linksys forums. The most similar so far was this one: http://forums.linksysbycisco.com/linksys/board/message?board.id=VoIP_Adapters&message.id=5177&query.id=151004#M5177

The guy was experiencing the same issue but with a Netgear router. The solution was to upgrade the router's firmware and add the PAP2T on the router's DMZ.

My PAP2T is currently configured with a static address and its address on the DMZ list. Not sure if the WAG160N's DMZ functionality really works...

Cheers,

Yehudi

Samsung

Shop now on Samsung phones, tablets, TVs and more (affiliate link).

YB

5 posts

Wannabe Geek

#191431 23-Jan-2009 05:04

Folks, just an update about this issue. Following Linksys' advice, I replaced the router (via RMA) and got a brand new one. Surprise surprise - have got the same problem. Therefore, this is definetely not a hardware issue but a firmware issue. I will speak with Linksys support again, let's see what they've got to say....

Cheers,

Yehudi