emailit wrote: I don't know what Fongo does when asked to do a "forced registration", but it seems to have resolved my 1 way audio issue on incoming calls that I have been experiencing from day one.
"Forced registration" doesn't actually force registration. Rather, I suspect FPL is forcing its switch to proxy audio for the user's account.
There's a related thread at
http://forum.fongo.com/viewtopic.php?f= ... =25#p68860.
Read Mango's posts.
I read the interesting Obi200/202 pdf you suggested. The only timeout value I coud find in my router was "NAT UDP Timeout" which is currently set to 10 minutes.
10 minutes seems crazy high to me. Are you sure that's not seconds?
I'm not sure if this value is the "UDP Unreplied Timeout", the "UDP Assured Timeout", or something else.
Sorry, I'm not sure either.
Thanks to Mango, many of us now understand that in order for ATAs to remain registered and working properly with a VoIP SIP provider like Freephoneline,
in particular after power failures, the following conditions must be met:
UDP Unreplied Timeout (in your router) < NAT Keep-alive Interval (in your ATA; for Obihai ATAs this is X_KeepAliveExpires) < UDP Assured Timeout (in
your router) < SIP Registration Failure Retry Wait Time (or RegisterRetryInterval in Obihai ATAs)
“<“ means less than.
UDP Unreplied Timeout (in your router) < 20 (in your ATA) < UDP Assured Timeout (in your router) < 120 (in your ATA)
These values here (20 and 120) are in seconds.
Grandstream GT-502 has a default Keep Alive interval of 20s. And then the SIP Registration Failure Retry Wait time should be set to 120s for FPL in your ATA.
It is safe to increase your SIP Registration Failure Retry Wait Time, but it's not a good idea to lower it. More than 5 registration attempts in a 5 minute period will result in a temporary IP ban from FPL's server.
SIP Registration Failure Retry Wait Time set at 120 means that when registration with FPL fails, your ATA will attempt to register again in 2 minutes. So you can increase that value in order to satisfy the above equation/conditions if need be.
Having a 10 (600s) minute unreplied UDP timeout in your router would be insane.
A lot of routers default to 30s, which is still too high for VoIP since a lot of ATAs use a Keep-alive default value around 20s or slightly lower.
However, I'm not sure what the 10 minute value applies to, sorry.
The other thing to keep in mind is that the equation (or conditions) also apply to the other services you're using, so if your UDP timeouts work with Nettalk and Tektalk, then you might not want to fiddle with those UDP timeout settings.
If I try to call FPL again, the call goes thru and both parties can hear each other.
Seems like the NAT hole is taking awhile to open for some reason. Unfortunately since I don't have the router you're using, I don't know what else to suggest.