Busy signal

[ap236]

I followed the instructions after re-setting the trendnet router, and even after forwarding the ports it didn't work.

[bridonca]

What do you have for a modem? With your luck, it is probably also a router!

I took a look at the manual for the TEW-432BRP. Tough not the best, it seems OK when it comes to forwarding ports.

I would like you to get the dlink completely out of the way for the time being, and connect the TEW-432BRP's wan port to the modem, and then connect the pap2 to the TEW-432BRP's lan port. Make sure the TEW-432BRP is reset to it's default settings. If it does not work, your modem might also be a router, and if that is the case, I can work with that. Let me know.

[ap236]

I don't know the exact make, but it's a Rogers modem. So far as I'm aware it isn't a router, but I'll check into it. It's difficult for me to plug the ATA directly into the trendnet router, but I'll see if I can test on it. The trendnet and d-link routers are in different rooms.

[ap236]

The modem is a SA Webstar, manufactured 12/06.

[ap236]

So I hooked the ATA directly up to the trendnet router (which is now directly after the modem), and it worked. I'm waiting 5 minutes to repeat the test, to see if the issue is solved or not.

[ap236]

That test failed too.

[bridonca]

Yup, the WebSTAR is a router! You gotta laugh!

See if you can access the WebSTAR at 192.168.100.1. If you can, you have to again turn the TEW-432BRP from a router to an access point.

This time, set the TEW-432BRP ip address to 192.168.100.111 instead of the default 192.168.10.1 so as to allow access to the TEW-432BRP access point while still connected to the Webstar.

Plug the WebSTAR ethernet cable into one of the TEW-432BRP lan ports instead of the TEW-432BRP wan port it is in now.

From the TEW-432BRP, you should be able to now access the WebSTAR at 192.168.100.1 if the default settings are still intact. You should also be able to access the TEW-432BRP at 192.168.100.111

Connect the PAP2 to one of the lan ports of the TEW-432BRP. If you still need to forward ports, you can do it from the WebSTAR. More likely than not, you will not have to configure anything.

You will also have to make the Dlink into an access point also if you choose to use it. When configured as such, the Webstar will be the only router as far as the devices connected are concerned.

[Red89GT]

So I hooked the ATA directly up to the trendnet router (which is now directly after the modem), and it worked. I'm waiting 5 minutes to repeat the test, to see if the issue is solved or not.

in the trendnet router make sure you have the right port forwarded to the ata. In the pap2 under Line 1 (assuming you use line 1 for FPL) you will see a SIP port listed. Make sure it matches what you have forwarded in your router. or just forward all of theses ports (13000-13001,5060,5061,6060,6061,16384-16482)

I had similar issues with my ata working for one call then not working anymore. also unplug power to everything ( modem, router and ata)

[ap236]

I turned the trendnet back into an access point, but I couldn't even get on the net. I did log on to the modem, but nothing on it indicates that it is a router also. I'll power-cycle everything.

[ap236]

I power-cycled both routers, the ATA and the modem, no dice.

[ap236]

There's no way to forward ports or do anything when logged in to the Webstar.

[bridonca]

If you have the pap2 directly connected to the webstar, does it work properly?

[ap236]

I hadn't tested that, though if it doesn't work does that mean the modem needs replacing?

[bridonca]

It is possible, but I would suspect the pap2 is misconfigured in some way if the pap2 still does not work when directly connected to the modem.

[ap236]

Images removed. New post with updated images will be made.

[Red89GT]

please retake the pics showing the "advanced" settings and logged on as admin

[ap236]

[images removed]

[Red89GT]

I would hazard a guess saying you have your ATA configured correctly. The only difference I noticed between your settings and mine is that under provisioning I have my set to "no" and you have yours set as "yes"

[ap236]

I would hazard a guess saying you have your ATA configured correctly. The only difference I noticed between your settings and mine is that under provisioning I have my set to "no" and you have yours set as "yes"

It was set that way when I got it.

[Jake]

Are you able to call out, or is that not working either?

Looking at your other posts it looks like you first mentioned that it was working OK, but now you get a busy signal when someone tries to call in.

What happens when you down power the ATA for 5 minutes or so, then power it back up again? does it work? both calling in and out?

If you find it does work when down powered for a while, but only for a short time, I had the exact same problem. The way I fixed it was to change the registration time from 3600 (as I see yours is set now) down to 60. If you try changing it, then make sure you down power the unit for a while, as I found my didn't take until I did.

[ap236]

It worked fine when directly plugged into the modem. And it works for about 5 mins or so after I make a change to my router.

[bridonca]

I am going to assume the trendnet is back to it's default settings, where it can be accessed at 192.168.10.1. I am also assuming the trendnet's wan port is directly connected to the modem. The pap2, for the time being, should be connected to the lan port of the trendnet.

Your problem is that the trendnet router has to be be able to know exactly where the pap2 is, If you can figure out how to set up the trendnet so as to always be able to make the PAP2 use the same ip all the time, 192.168.10.99 being an example, that is the best way to go. Otherwise you have to disable dchp on the pap2 and set up a static IP on the pap2 like 192.168.10.99 with a netmask of 255.255,255.0 and a gateway ip of 192.168.10.1 When done right, if you input 192.168.10.99 you should always be able to access the pap2 router.

In the PAP2, on the rtp port parameters leave the RTP port min as is at 16384, but the rtp port max as 16836

With the trendnet, forward ports 16384, 16385, 16386 and 5060 to 192.168.10.99. You do that, and your problems should go away.

[ap236]

Would replacing the router with a new router solve the problem, and if so, which router would be best?

At this point I'm ready to buy a new router to save headaches.

[Jake]

Would replacing the router with a new router solve the problem, and if so, which router would be best?

At this point I'm ready to buy a new router to save headaches.

The fact that it works at some point behind your router could mean it is not your router at all, or at least not entirely.

Changing the registration time to 60 has helped quite a few people with the same problem as you, it could be worth trying and saving yourself the cost of a router.

You didn't mention if you are still able to make outgoing calls when you get the busy signal when calling in. If you can still dial out, this is the exact same problem as others have had, and was fixed with changing that registration number. Maybe it also has something to do with the router but this seems to fix it.

[ap236]

I can make calls out, no issue. I'll try to change the registration time.

I presume registration time = registration expires?