I’m having problems registering to my sip provider!
I’ve had problems with this before, but it’s been working fine for a few months.
Today it just stooped working. I don’t understand why! If I reinstall the FreePBX or if I put in a new router it works fore awhile.
It’s the same problem I’ve had earlier!
I have a NAT router with a firewall.
I’ve forwarded port 5060 and 10.000-20.000 to the FreePBX.
And opend port 5060 and 10.000-20.000 to the FreePBX.
I also turnd off SIP ALG and SIP Transformations in the router.
Is ther any other setings I have to do in the router, or do you have any other suggestions?
[2016-01-23 18:59:43] NOTICE[1807]: chan_sip.c:15180 sip_reg_timeout: – Regi
stration for ‘[email protected]’ timed out, trying again (Attempt #584)
[2016-01-23 18:59:43] NOTICE[1807]: chan_sip.c:15180 sip_reg_timeout: – Regi
stration for ‘[email protected]’ timed out, trying again (Attempt #584)
Is your PBX set to use Dynamic IP, if so how are you setting the IP from your ISP to your FreePBX?
You are missing tons of information you need to provide, the above being one of them. Telling us it stops working is not very helpful. What stops working? Does a reboot make it work again?
Who is your ISP, do you have a static IP or leased?
I apologize for the light information!
I’m not sure what info you need.
The PBX is set to a Dynamic ip, but it is bound from the router.
Never any problem accessing the pbx “web-interface”.
My internet provider have me om dynamic IP, I use DDNS. I’ve had the same IP more than one month and still do.
I have two sip providers,
affinity telecom and Voicetech.
Both providers are Swedish
I can register to both providers with a soft phone!
I don’t have any problem registering phones or making calls between them,
with in the lan or from outside the firewall.
It doesn’t help to restart the PBX.
I’ve also restarted the router, it didn’t help
What type of router are you using? Many of them try to do SIP connection tracking whic is different than ALG NAT and this can sometimes stop working correctly for many reasons.
Yes, of course. The router can run out of memory, the connection tracking table can fill up due to bugs in firmware preventing connections. Regardless of what the actual issue is, it seems like the most likely issue is your NAT gateway/router since it works again if you swap it out. You aren’t seeing 404 unauthorized or registration rejected, so the request is not traversing you router properly. If it were the other conditions, we would look elsewhere.
That’s probably outside the scope of this forum, and this is 90% opinion and for every admin that suggests and has success with a certain device, there are 10 that will trash it. Personally though I use full linux and iptables whenever possible, but ddwrt or openwrt routers can work for small installs in a pinch or for testing. The websites of those respective project keep a database of compatible models. Larger enterprise networks might use cisco, juniper, or any number or high end router/firewall vendors.
