flybluesky wrote:thanks
. use it for years, everything was good,.ISP & Router are same
Unfortunately, it doesn't really matter if everything worked well for you for years. NAT associations in routers can become corrupt without you doing anything.
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.
A problem can occur when the Keep-Alive interval is greater than UDP Assured Timeout (often 180 by default in
consumer routers): the NAT hole will close due to the ATA not communicating frequently enough with the SIP server.
In turn, incoming calls may, intermittently, not reach the ATA. Again, X_Keepalives expires is supposed to be 20 with
FPL.
Getting access to both UDP Unreplied Timeout and UDP Assured Timeout settings in consumer routers may be
difficult, if not impossible. Asuswrt-Merlin, third party firmware for Asus routers, does offer easy access to these two
settings, which are found under General–>Tools-->Other settings. In part, for this reason, I tend to use Asus routers
that work with Asuswrt-Merlin. However, my understanding is that third party Tomato firmware has these two settings
as well. So if your router supports Tomato firmware, that may be another option.
The keep alive interval for FPL is 20. The SIP Registration Failure Retry Wait Time is 120. I use 10 for UDP
Unreplied Timeout and 117 for UDP Assured Timeout.
Typically, it's best to have your own router for VoIP.
out call is good. each time after setting retest, both side have ring tone when try incoming call, but receive side hear nothing. and one more problem : after a few minters , try incoming call again , both side no ring tone
This sounds like a corrupted NAT association/UPnP issue or SIP ALG related problem to me.
Test by using a regular landline or cellphone service (not VoIP) when making calls to or receiving calls from someone else.
If the other side is using a VoIP service, the problem could be on that user's end.
try more times resetting as you said
1) What does the registration status in your ATA indicate for Freephoneline?
Navigate to Status-->System Status-->SP(FPL) Service Status-->Status
What does the registration status state?
Registration isn't required for outgoing calls. It is required for incoming calls.
It's important to note that only one registration per FPL account is allowed at any given time.
If multiple devices are registered (or attempting registrations) with the same FPL account, only the most recently registered device will ring for incoming calls.
The others will not. Obviously, if your FPL SIP credentials are being used on another device or by someone else (even by a hacker) that can present problems.
With respect to registration being required to receive incoming calls, more than 5 registration attempts within 5 minutes can result in a temporary IP ban from the FPL proxy server being used.
From
https://community.freepbx.org/t/trunk-s ... ca/22479/8"As May 2013, our servers will rate limit REGISTER requests to a maximum of 10 requests per 5 minutes. Each authentication round usually consumes 2 requests (digest auth), so it is a fair number given our guidelines. Also, it does not affect INVITES (which are also authenticated)...
This rate limit is applied per IP address as our service is tailored to residential Canadian users (ADSL/Cable)."
2) Your X_keepalive related settings are wrong.
X_KeepAliveExpires should be 20
X_KeepAliveMsgType should be notify
3) In your Obihai ATA or at Obitalk.com, Navigate to Voice Services-->SP(FPL) Service-->X_UserAgentPort
Pick a new random number between 30000 and 60000, and don't post it this time
4) Try voip4.freephoneline.ca:6060 for the proxyserver just to see if there's some bug in your router despite SIP ALG being disabled in it.
I strongly suggest you configure FPL again from scratch (if you're using Obitalk.com, I would delete your FPL profile) using the PDF guide:
viewtopic.php?f=15&t=18805#p73839