No incomming audio on outbound call

[h00ch]

Spoke too soon. The problem is back for me just a few minutes ago.

[tanny]

well sure, as I am sure that ALL of us have receieved the email "Fongo Notification - Time for an Upgrade" -way back on Feb.12, 2013.

OK, BUT The point is
1./ "OUTBOUND" is NOT working properly, if at all, since that upgrade.\
2./ I have called succesffuly about half of the phone numbers of freinds', from Ontario throughout Quebec.
But Again, it only works interrmittemtly on and off.

On the contrary, I was fine for months before this, and had no problems calling ANYWHERE !

If this had ANYTHING to do with having to make all these port changes? to our VOIP SPA's,... then why did "outbound" even work at all although HORRIBLY,
and more important, if all these fancy "port-changes" atre required at our end, then why didn't we ALL NOT get a "follow-up" email from "Freephonelin.ca / FOMGO" ,
on EXACTLY what to do, at this point. ???

It's not like we haven't PAID for this VOIP service / Phone Number already ?
I mean, be it FT"P", HTT"P", ... TC"P"/I"P",... get my point ? this VOI"P" shound just work. If my Internet works,..., then yes Freephonline VOIP should work as well.

So now what, no outbound ?, .., and for how long ?

...really not happy here anymore.

Soooo, please FIX this freephoneline / fongo.
arggghhhh!

[tanny]

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!

Yes, THIS is similar to my predicament as well. I've been with freephoneline.ca, with almost NO problems, for about a year now, until this HORRID (FAIL) Upgrade.

[triron]

Everything back working again Thank you Fongo.

[dalexop]

Hi Folks,

Yes, RTP port forwarding led me to a solution.

I have a SPA3102 and it stopped working in the same way around the 12th as well.

I opened the port range from 16385 to 16440.
( Note that the maz range on the 3102 is 16385 to 16482 )
So I added more and more ports to the range until it started working on a live call.

I am not too fusssed about the rationale for changing the server side, but I do think that Fongo needs a way to go as far as customer communications.
This is unnacceptable.

[Jake]

Hi Folks,

Yes, RTP port forwarding led me to a solution.

I have a SPA3102 and it stopped working in the same way around the 12th as well.

I opened the port range from 16385 to 16440.
( Note that the maz range on the 3102 is 16385 to 16482 )
So I added more and more ports to the range until it started working on a live call.

I am not too fusssed about the rationale for changing the server side, but I do think that Fongo needs a way to go as far as customer communications.
This is unnacceptable.

I believe the ATA and server will sort out RTP ports to use between that range in a random fashion. My only concern with what you have done is if it decides to use ports between 16441 and 16482 (which the ATA assumes it can use). It might mean you get no audio again. I would probably either open the same range in the router, or change the upper range in the ATA to 16440, this way the ATA will only try and use the same port range that is forwarded in the router.