Busy signal

[ap236]

When someone tries to call me (or when I try to call myself from my cell phone) a busy signal is coming through despite the fact I'm not using that line.

[FONGO_steve]

Hm,
Has this happened before?

Firewalls all turned off? Internet security software all disabled?

If both of the above are true, then you may need to port forward in your router to let the VOIP traffic through

[ap236]

It was working fine for a while after I hooked up the ATA I got today. I'll try the port forwarding when I get home.

[ap236]

How do you forward ports?

[ap236]

I think I figured it out thanks to Google. Seemed to work when I called myself from my cell.

[ap236]

Last night I thought I had successfully forwarded ports 6060 and 6061, but this morning the busy signal came back. so I've added ports 5060 and 5061 hoping this will help.

[ap236]

I'm still getting the busy signal. I should add that I'm behind two routers, not just one due to the length of the place where I live.

[Red89GT]

I'm behind two routers

I bet thats your problem. You need to disable one of the routers from acting as a DCHP server and make it operate as a hub instead.

[bridonca]

You are on Rogers and behind 2 routers? I am shocked you get any connection at all!

Enough of the monkeyshines from me, what do you have for routers? I want to see if you are able to turn one of them into an access point so as to make for much less confusing routing for the VOIP gear. What is the modem model also?

[ap236]

One is a D-Link DI-624 (this is the one hooked up to the modem), the other is a Trendnet TEW-432BR. This is the one I have the ATA hooked up to.

[bridonca]

I only recently gave help on converting a TEW-432BRP router into a access point, which is what you also need to do, so I will be doing a little cut and paste.

You will need to convert the TEW-432BRP from a router to an access point, so that the D-Link DI-624 will be the only router. As an access point, the TEW-432BRP and it's wifi will be controlled by the D-Link DI-624. The SIP ATA, other computers, and wifi devices connected to the TEW-432BRP will also be directly routed by the D-Link DI-624.

Here is a a document on how to configure the TEW-432BRP as an access point. It is not hard.
http://www.trendnet.com/kb/kbp_viewques ... &catId=524

Make sure the TEW-432BRP ip address is set to 192.168.0.111 instead of the default 192.168.10.1 This will allow you to be able to access the TEW-432BRP access point while still connected to the D-Link DI-624.

Plug the D-Link DI-624 ethernet cable in one of the TEW-432BRP lan ports instead of the wan port it is in now.

You can now access the D-Link DI-624 at 192.168.0.1 if the default settings are still intact. If you still need to forward ports, you can do it on the D-Link DI-624. More likely than not, you will not have to do anything though.

[ap236]

Thank you birdonca, I have done this and so far it seems to work. My fingers are crossed.

[ap236]

So I got the busy signal again, and went onto the D-Link router to forward ports 5060, and 5061.

[ap236]

Still no dice.

[psycon]

try setting your ATA as a DMZ host on your router.
try disabling your firewall on your router all together.
try using 208.65.240.142 instead of voip.freephoneline.ca when configuring your account (maybe your ATA has issues resolving hostnames, see if you can manually input your ISP's DNS servers)

if that does not work

try using a softphone on your pc, and disconnect your ATA
(I suggest QuteCom, easy to set up and use, and can have the g729 codec)

if the call is coming through fine to your softphone, then you know the problem is your ATA.

go to goole and see if people are having issues with that ATA and other providers.

[bridonca]

That D-Link DI-624 is a bit of a stinker! You need to be able to reliably pass ports to the right device, and the D-Link DI-624 is not making things easier.

You are going to have to disable DCHP on the SIP ATA, and manually input an IP like 192.168.0.55 with a netmask of 255.255.255.0 The gateway IP will be 192.168.0.1 You do that, and when the D-Link DI-624 routes a port to 192.168.0.55, it should reliably pass that port to your newly set up SIP ATA.

You only need a SIP port like 5062 and an RTP port like 12000 forwarded to your SIP ATA. Make sure the SIP ATA is set up to accepts those ports.

What do you have for an ATA?

[ap236]

I got the Linksys PAP2T. If I were to replace the d-link router, what would you suggest?

[ap236]

What if I switch them, and have the D-Link as the access point, with the trendnet router doing the routing?

[bridonca]

I am sure any new router would have better options than the DI-624, it is kind of hard to get a clunker nowadays. I am partial to routers that can do DD-WRT, an open source router firmware, but that is probably overkill for most people.

I should not slam your DI-624 that badly, it does work. It is just that it is bit of a bear to configure, Once you do the workarounds, it will be fine. If you do a lot of configuring though, you might want to shop for another router.

The pap2 is a pretty good ATA. You do not need that many RTP ports. Limit the range to about 3, to make it easier when you are doing forward entries on the DI-624. Whatever sip port you have set on the PAP2, make sure you have it forwarded from your DI-624

[ap236]

I'm not sure I can do all that is needed for the DI router. Which routers are DD-WRT compatible?

I think I'll try switching the Trendnet and D-Link routers, perhaps that'll solve the problem on its own. I bought it back in 2006.

[bridonca]

That is a big duh on my part! Apparently the DI-624 can also be turned into an access point. Doh! http://bitworking.org/news/Configuring_ ... cess_point As an access point, the DI-624 does not have to be particularly smart so it would make for a perfect access point!


Just make sure you undo the settings I told you to make on the Trendnet before you switch.

[ap236]

I'm having the problem that I can't log in to my trendnet router to change it back from being an access point.

[Jake]

I'm having the problem that I can't log in to my trendnet router to change it back from being an access point.

I'm going to bet there is a reset button on the back of the router. I don't know that router, but all the ones I have worked with had one somewhere. Try holding it in for 20 seconds or so and see if all the lights go out then back on again indicating it has done a master reset. The other thing to try would be to down power it, and hold it in and power it up again. Hold the button in for 20 seconds again for good measure as you power it up. After which you will probably find that the router is back to square one where you can set it up to how you want it.

[bridonca]

A reset in the back would fix the problem would put all the settings on the trendnet to default, but I got you to change the login ip to 192.168.0.111 so you could access the dlink and the trendnet at the same time, when the trendnet was configured as a access point. If you did not yank things apart, you can access your trendnet at 192.168.0.111

[ap236]

I'll do the re-set button. I hadn't changed the IP Address, not a big issue to re-set.