No Inbound Audio in Incoming Calls

[annie]

My FPL had been working fine for a few weeks, but I suddenly had no inbound audio in incoming calls since yesterday. The outbound audio in the incoming calls works fine. All outbound calls work fine with two-way audio. There was no configuration change in ATA or router since then. I also rebooted modem, router and ATA. I didn't configure any port forwarding because it just worked previously. Is this related to firewall, router port forwarding, or something else?

Help is greatly appreciated.

[Winston]

My FPL had been working fine for a few weeks, but I suddenly had no inbound audio in incoming calls since yesterday. The outbound audio in the incoming calls works fine. All outbound calls work fine with two-way audio. There was no configuration change in ATA or router since then. I also rebooted modem, router and ATA. I didn't configure any port forwarding because it just worked previously. Is this related to firewall, router port forwarding, or something else?

Help is greatly appreciated.

Hello Annie, could you please tell us what model of ATA are you using? According to what you describe, I would suggest you to open ports 5060-5061,10000 and 20000 in the UDP ports, make sure your firewall is allowing the traffic and also checking the calls logs is a good idea too.

[bridonca]

You need to port forward. I am guessing your ISP changed your ip. which it does from time to time, and your router never clued in. You need to pay decent money for a router that can do NAT perfectly. Everyone else has to forward ports!

[annie]

I am using Linksys PAP2T. My router is DI-524.
I checked the call logs, and they all showed as successful calls - in a sense they are because the call was established and hung up properly. I'll give it a try for port forwarding. Just need a bit clarification here: Is it UDP ports 10000 and 20000, (not 10000-20000)? Or should it be 13000-13001?
I don't think changing IP has anything to do with it cuz my router crashes a few times here and there, but reboot will fix the problem, VoIP will re-register, etc. I am still confused. Why did it work without port forwarding the first place and why now it is broken?

[Winston]

I am using Linksys PAP2T. My router is DI-524.
I checked the call logs, and they all showed as successful calls - in a sense they are because the call was established and hung up properly. I'll give it a try for port forwarding. Is it UDP ports 10000 and 20000, (not 10000-20000)? Or should it be 13000-13001 as I read in another thread?
I don't think changing IP has anything to do with it cuz my router crashes a few times here and there, but reboot will fix the problem, VoIP will re-register, etc. I am still confused. Why did it work without port forwarding the first place and why now it is broken?

10000-20000 in the UDP should be, this will range all the numbers (13000,13001,etc) also remember the 5060-5061 as well.

Do not worry about the IP let it the way it is and let us know the results

[annie]

10000-20000 in the UDP should be, this will range all the numbers (13000,13001,etc) also remember the 5060-5061 as well.

You know that DI-524 is a crappy router and I can only enter one port at a time not a port range. What is the bare minimum ports I have to open up? Considering all the calls are happening, I think 5060 and 5061 are processed correctly without port forwarding. Thus, I think it is only the call initiated from outside firewall, the RTP traffic was blocked. Which is the port for that?

[Winston]

Honestly I do not know much about your Router, but allow me to provide you an excellent URL that will help you to configure the Router, just go to www.portforward,com, look for your modem's maker and will show you how to open properly the ports.

[FONGO_steve]

10000-20000 in the UDP should be, this will range all the numbers (13000,13001,etc) also remember the 5060-5061 as well.

You know that DI-524 is a crappy router and I can only enter one port at a time not a port range. What is the bare minimum ports I have to open up? Considering all the calls are happening, I think 5060 and 5061 are processed correctly without port forwarding. Thus, I think it is only the call initiated from outside firewall, the RTP traffic was blocked. Which is the port for that?

the PAP2 uses an RTP range, thus us advising of the 10000-20000 to "catch-all"
If you access the PAP2 config you should be able to shorten this range to maybe a handful of ports that you can then setup to forward in the router.

[bridonca]

Annie: You are right, that router is a stinker!

More likely than not, you will get away with porting just one RTP port, something like port 12000. maybe add 12001 12002 12003 ... for comfort, but I believe one will do. That is all I needed on my pap2. I never liked using the default port 5060 with freephoneline because I also use other VOIP providers that do not offer the same port flexibility freephoneline has on the same router. I use port 6060 for freephoneline's sip port, though ports 5060-6060 work well also.

[annie]

Hi folks, I am so excited to tell you that my problem is solved, with help from all of you. Firstly, I verified that my router indeed dropped the UDP traffic. Then I tried to configure my firewall to allow * to ata with port range. It worked. I wasn't exactly comfortable to open so many ports, then the last two posts gave me very good hint. I changed the random ports my ata gave to me and limited to a few. Finally, I added the ports in my router virtual server config.

A big thanks for you all. Now with all that experience, I can contribute to help others too. May need your help again since I want to install a second line in the near future.

[Winston]

Glad to hear it is up and running