No incomming audio on outbound call

[bblenke]

I did not change anything on my network.
Now when I make an outgoing call to another phone I do not here the call being made, but the receiving phone rings. When call is picked up they can hear me but I can't hear them.

Does this make sense?

Please help.

[bblenke]

also:

I have done the following:

- power cycled everything
- DMZ'd my pap2t
- port forward on 13000...
- tried sip client on android phone

- fongo app works.

[bblenke]

tried 2 different network opperators bell and rogers... both have same issue with android sip client.

must be an issue between freephoneline and fongo...

[epsilon3]

It happened to me yesterday as well! EXACTLY the same issue. I have a Talkswitch PBX. The router is Tenda N60

What I did to solve the problem: I had to reprogram the router and re-open/re-map the ports 5060-6061 (UDP) and 10000 -20000 (UDP) and to re-enable the UPnP. ALL WORINGK AGAIN NOW.

I posted this on another threads as well ... see if it works for you

[nanyte]

Same thing happened to me. I opened the ports as epsilon suggested and it is working now. They must have did something different though that now required me to open the ports all of a sudden.

[mchotard]

I have the same problem since the maintenance of Feb 12th. I made a linksys reset, but did not change anything on my network.
When outgoing call to another phone, I do not hear the call being made, but the receiving phone rings.
When call is picked up they can hear me but I can't hear them.

I have a linksys SPA2012, Freephoneline account.

Thank's for help

[boatguy]

Thank goodness someone else is having this problem too. I have had one ATA (HT-286) working for months on FPL. Never opened a port or did any forwarding. Added a second ATA (HT-701) on the 11th and both worked flawlessly without doing any port forwarding or opening any ports. Then on the 12th BOOM. Spent the entire day fighting this problem with one, both or soft phone. I tried the port forwarding and it sort of worked for one device. Please let this just be a network issue or let some Handy Tone genius and Cisco smart guy drop by to help me. I waited until this month because I wanted to prove to my wife it was stable for a home phone. UUURRRGGGHHHH.


John

[dibsmft]

Did you power cycle the modem/router/ATA and if not do so and see if that helps.

[bblenke]

Still not working.

sip app on android with mobile data, so I don't really have control here. But it worked before, and I have a fongo app that is working fine, both wifi and mobile data...

[techsupport]

What kind of changes have been made on the server that now I have to expose my internal network to make calls?

This used to work until 2 days ago for TWO YEARS. Now only way to make it work is to allow WAN -> LAN exposing internal network to all sorts of attacks from abroad. I tested same setup with 4 other providers and none of them requires me to open any WAN -> LAN settings.

[tde]

I am having the same issue as well for the last couple of days. I tried power cycling my modem/router/ATA but no luck. Have anyone been able to resolve this since yesterday? And has anyone received any response from Fongo support? My support ticket received just an automated response.

[boatguy]

I figure I can hide this for about 2 weeks, then I am going to have to find another service and port my numbers again. I wish you would share those "4 other services" with use so perhaps I could just jump ship early. 2 days and no response.

[h00ch]

I've also been using the service since last year without major issues, now since the morning of Feb 12th, I've not been able to make outbound calls. I hear a dialtone, the number dials, but I hear no ringing and I cannot hear anything when the person picks up, but they can hear me. PLEASE FPL, undo what you have done!

[Funkytown]

have you tried this http://forum.fongo.com/viewtopic.php?f=6&t=7926

[h00ch]

Yes, makes no difference to me

[triron]

I fisrt posted this in the fongo home phone section before I noticed that there is a freephone section. I started to notice this same problem yesterday Feb 12,2013 incoming calls to my freephone phone work fine, it is just outgoing calls from my freephone phone they can hear me but I can't hear them. I am also experiencing the exact same problem on my smartphone using acrobits softphone sip software with either wifi or 3g data using my freephone sip configuration. Everything has been working fine for months since I first got the sip configuration file from freephone until yesterday. This problem is from the updates fongo did on Feb.11 - 12th. I am using a linksys ata for my freephone phone and an iPhone for acrobits softphone. Fongo please look into this as a lot of people are having this issue. I have reset router and ATA numerous times and already have all ports forwarded that have been suggested, still this is not working as it was just a few days ago.

[h00ch]

I should also mention I am using a SPA112 ATA with the latest firmware

[Hyrules]

I had the same problem yesterday with a call. I couldn't hear the other person but they could hear me.

[Melchizedek]

I called my cellphone this morning and it worked, but I haven't made further tests.

[h00ch]

I called my cellphone this morning and it worked, but I haven't made further tests.

and you could hear the phone ringing on your land line phone? I just tried it and it isn't fixed yet for me.

[Melchizedek]

Yes, everything was working as it should, but then again that was only one test. The same test had worked yesterday morning too, but in the end, outgoing calls remained down all day.

[belgiumrom]

Hi there guys, just for people who have/use the Linksys SPA 2102 behind a firewall, here are the settings needed to make this work.
I just want to mention that before Feb12/2013 these port openings and forwarding were not necesssary...
Open in your firewall and forward to the address of your voip ATA static IP the UDP port range 5060-5061.
Verify in the administration console of your voip ATA device what are the ports used for RTP (in my case it was from 16384-16480 but me being a security freak I changed and allowed just 16384 and 16385).
Open in your firewall and forward to the address of your voip ATA static IP the UDP port range 16384-16385.

I just want to emphasize that opening UDP ports randomly like I've seen in this forum (port 10000, 20000, 5004, 13000, 13001, etc) won't help as it HAS to be the RTP ports that YOUR SPECIFIC ATA DEVICE use.

Hope this will help someone to get his phone service back...

[techsupport]

We are into opening inbound connections now? That sounds similar to manufacturer telling me I could fly airplane with broken wings by duct taping it on. Doesn't sound too secure does it?

As previously said, I don't see why Fongo is only one out of all the providers I tried - VOIP.ms, Call With Us, CheapVoipInc, Anveo - to require such insecure setup. It has been working for many years and what is up with sudden change for the worse?

[belgiumrom]

We are into opening inbound connections now? That sounds similar to manufacturer telling me I could fly airplane with broken wings by duct taping it on. Doesn't sound too secure does it?

As previously said, I don't see why Fongo is only one out of all the providers I tried - VOIP.ms, Call With Us, CheapVoipInc, Anveo - to require such insecure setup. It has been working for many years and what is up with sudden change for the worse?

I believe the main reason for this happening is that VOIP providers are more and more often hacked for the purpose of making free outbound calls nowadays.
I also believe that the latest upgrade/maintenance is pointed at this issue as well hence the service working fine b4 but not after without opening ports.
For a hacking aware internet user, this is a serious issue be it corporate or private/personal use...
Don't get me wrong but if someone wants to hack into something it will happen no matter what, given a few conditions necessary (http://www.blackhat.com/presentations/b ... Endler.pdf).
Now, from my point of view, I somewhat agree with these security measures given the fact that I am myself an IT guy. But these issues should not have repercussions on the average user as they can be implemented directly from the provider, hence FPL.
..and again from my point of view, having the SPA2102 (or any other similar device) acting as a SIP router and as a point of entry firewall is very wrong by simply concept.
This is why I use this device as a sole purpose of routing VOIP calls and nothing else and of course behind of a firewall with only 4 ports open/redirected instead of a range of some hundreds or thousands of ports.
I try to minimize the damage in case of a hack to only VOIP service instead of total disaster (all of internal network data/services).

[boatguy]

I got it. Between belgiumrom and funkytown I pieced together the solution, the correct ports, and changed them up for 2 different ATA devices. Both lines work now. Remember to turn off random sip and/or random ftp. Thanks all....I learned something.