registration only keeps one hour

Have a question or problem with your Fongo application? This forum is the place to get help from both staff and fellow community members.
Fongo recommends Fongo Home Phone for a fully supported Home Phone system for only $4.95/mo
Forum rules
Post Reply
akoei
Quiet One
Posts: 38
Joined: 12/14/2009
SIP Device Name: asterisk
ISP Name: 3web

registration only keeps one hour

Post by akoei »

Hi Support,

My registration can't be kept after one hour: I set register expiry time 3600s, it only keeps one hour, then disconnected, the all following re-registering attempts will be failing. It has been one week I can't figure it out, would you please help?

ADD: from what I am observing, it looks my IP is blocked after 1 hour, I have to change my router's MAC to get a new IP (cable internet), then I can register again (for just 1 hour!). I read some announcement that the register expiry has to be 3600, if too many request in 5 minutes, the IP is going to be temporary blocked.
I am wondering:
1. how many hours for each temporary IP block?
2. I have set the expiry to 3600, what reason cause my IP be blocked?

Thanks

Shawn
Top
User avatar
Liptonbrisk
Technical Support
Posts: 2773
Joined: 04/26/2010
SIP Device Name: Obihai 202/2182, Groundwire
Firmware Version: various
ISP Name: FTTH
Computer OS: Windows 64 bit
Router: Asuswrt-Merlin & others

Re: registration only keeps one hour

Post by Liptonbrisk »

akoei wrote: the all following re-registering attempts will be failing
SIP error code might be helpful for others to look at, including logs.
if too many request in 5 minutes, the IP is going to be temporary blocked
Yes, more than 5 authentication rounds within 5 minutes


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)."
1. how many hours for each temporary IP block?
I have no clue, and I'm not willing to test being temp banned to find out either. If you want an official response, submit a ticket: https://support.fongo.com/hc/en-us/requests/new
Select "My account inquiry" for the issue type.

Keep in mind that you may only register a FPL account on a single device at any given time.


http://support.freephoneline.ca/hc/en-u ... redentials
These registration timers are important.

Registration Interval: 3600 seconds (1 hour)

Registration Expiry: 3600 seconds (1 hour)

Failed Registration Re-Try Interval: 120 seconds

Edit: In the event you're dealing with a corrupted NAT connection (as opposed to an IP ban), read #6 at http://forum.fongo.com/viewtopic.php?f= ... 82&p=74501.
Please do not send me emails; I do not work for nor represent Freephoneline or Fongo. Post questions on the forums so that others may learn from responses or assist you. Thank you. If you have an issue with your account or have a billing issue, submit a ticket here: https://support.fongo.com/hc/en-us/requests/new. Visit http://status.fongo.com/ to check FPL/Fongo service status. Freephoneline setup guides can be found at http://forum.fongo.com/viewforum.php?f=15.
Top
akoei
Quiet One
Posts: 38
Joined: 12/14/2009
SIP Device Name: asterisk
ISP Name: 3web

Re: registration only keeps one hour

Post by akoei »

SIP error code might be helpful for others to look at, including logs.
I understand that, however, the error's on client side is not useful: I am running a home asterisk v1.8, the console just gives generic "Retransmission timeout reached on transmission 192982fb6a46be0a7c31aa553cc9e708@192.168.5.8 for seqno 114 (Critical Request) -- See https://wiki.asterisk.org/wiki/display/ ... nsmissions
Packet timed out after 32007ms with no response"

From my experience, and others around me who also setup FPL on */freepbx, this looks my IP is banned on server side. The issue started to happen one week ago after I switched my ISP from Rogers to Fido, and no matter how I change my public IP (by changing router's MAC), the registration from my asterisk wont be able to keep more than 1 hour.

I really want to know what is happening on server side:
1. Is my IP blocked after one hour?
2. If yes for 1, what cause it?
3. Why this happens just after I change to Fido? Is Fido IP in some sort of "grey" list?
Top
User avatar
Jake
Technical Support
Posts: 2825
Joined: 10/18/2009

Re: registration only keeps one hour

Post by Jake »

I would do as Liptonbrisk suggest and check your timers, especially the retry one.

FPL will block your IP if you try and register/re-register too often.

When you changed from Rogers to Fido did you change the SIP server you were registered to? I know some Rogers customers have to use sip4 and a different port number. It could be that the sip4 server is a little bit nicer when it comes to registration times.

You have probably found that switching between voip. and voip2. servers gets you reconnected again, for about an hour. This is because the IP ban is server specific so by the time you get banned on the first it has cleared on the second allowing you to reconnect.

To answer your questions:-
1. Yes quite probably.
2. The main reasons for your account to be blocked is either an account they found not right (hacked password, incorrect 911 details, etc) or the timer issue.
3. It won't have anything to do with Fido directly, it would be very silly of them to exclude anyone in Canada. There whole business model is built around people having phone numbers and people calling them. They won't care what ISP you are with.
Top
akoei
Quiet One
Posts: 38
Joined: 12/14/2009
SIP Device Name: asterisk
ISP Name: 3web

Re: registration only keeps one hour

Post by akoei »

Thanks for your information, Jack.
I did some tests based on your info, and found actually my IP is not blocked - after one hour, although my asterisk can't register, but softphone has no issue to register; and, if I change from voip to voip2, my asterisk is still not able to register.

I turned on the debug mode and monitored it for an hours, and I see "SIP/2.0 401 Unauthorized" error right after 1 hour! (time stamp around 20:45) Do you know what it is? After this error, then 10 re-transmissions are followed.

Below are full log:

Code: Select all

<--- SIP read from UDP:162.213.111.22:5060 --->

<------------->

<--- SIP read from UDP:162.213.111.22:5060 --->
NOTIFY sip:14164778887@162.213.111.22:5060;transport=UDP SIP/2.0
Record-Route: <sip:14164778887@162.213.111.22;lr=on>
Via: SIP/2.0/UDP 162.213.111.22;branch=z9hG4bKb30f.1fc12697.0
Via: SIP/2.0/UDP 208.65.240.165:5060;branch=z9hG4bK-524287-1---049b501fb399d64e;rport=5060
Via: SIP/2.0/UDP 208.65.240.134:5094;branch=z9hG4bK-h7vmkvd3lagwjsb7;rport=5094
Max-Forwards: 69
Contact: "PortaUM"<sip:PortaUM@208.65.240.134:5094>
To: sip:14164778887@208.65.240.165
From: PortaUM <sip:PortaUM@208.65.240.134:5094>;tag=popb5nycgiwq253z
Call-ID: vuL0gAVjqjyr7lLs6!zExJ082i_1@208.65.240.134
CSeq: 1 NOTIFY
Content-Type: application/simple-message-summary
User-Agent: Sippy
Event: message-summary
Content-Length: 22

Messages-Waiting: no
<------------->
--- (15 headers 1 lines) ---

<--- Transmitting (NAT) to 162.213.111.22:5060 --->
SIP/2.0 489 Bad event
Via: SIP/2.0/UDP 162.213.111.22;branch=z9hG4bKb30f.1fc12697.0;received=162.213.111.22;rport=5060
Via: SIP/2.0/UDP 208.65.240.165:5060;branch=z9hG4bK-524287-1---049b501fb399d64e;rport=5060
Via: SIP/2.0/UDP 208.65.240.134:5094;branch=z9hG4bK-h7vmkvd3lagwjsb7;rport=5094
From: PortaUM <sip:PortaUM@208.65.240.134:5094>;tag=popb5nycgiwq253z
To: sip:14164778887@208.65.240.165;tag=as2c737bf9
Call-ID: vuL0gAVjqjyr7lLs6!zExJ082i_1@208.65.240.134
CSeq: 1 NOTIFY
Server: Linksys/RT31P2-3.1.6(LI)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0


<------------>
Scheduling destruction of SIP dialog 'vuL0gAVjqjyr7lLs6!zExJ082i_1@208.65.240.134' in 32000 ms (Method: NOTIFY)

<--- SIP read from UDP:162.213.111.22:5060 --->

<------------->
Really destroying SIP dialog 'vuL0gAVjqjyr7lLs6!zExJ082i_1@208.65.240.134' Method: NOTIFY
..............................
..............................
..............................
 <--- SIP read from UDP:162.213.111.22:5060 --->
..............................
................................
..................................
<--- SIP read from UDP:162.213.111.22:5060 --->

<------------->
[Apr 19 20:45:51] NOTICE[519]: chan_sip.c:13071 sip_reregister:    -- Re-registration for  akoei@sip.sipsorcery.com
[Apr 19 20:45:51] NOTICE[519]: chan_sip.c:13071 sip_reregister:    -- Re-registration for  14164778887@voip2.freephoneline.ca
REGISTER 11 headers, 0 lines
Reliably Transmitting (NAT) to 162.213.111.22:5060:
REGISTER sip:voip2.freephoneline.ca SIP/2.0
Via: SIP/2.0/UDP 72.141.206.9:5060;branch=z9hG4bK66623a11;rport
Max-Forwards: 70
From: <sip:14164778887@voip2.freephoneline.ca>;tag=as14c0f203
To: <sip:14164778887@voip2.freephoneline.ca>
Call-ID: 5972a742788f5d8619a86f3a5e7a3802@192.168.5.8
CSeq: 104 REGISTER
User-Agent: Linksys/RT31P2-3.1.6(LI)
Authorization: Digest username="14164778887", realm="208.65.240.165", algorithm=MD5, uri="sip:voip2.freephoneline.ca", nonce="1492645565:98d56553f2d0ad9b45b73660aeccff10", response="57a1ab04e7a21ea3c954adefbcdcbcba"
Expires: 3600
Contact: <sip:14164778887@72.141.206.9:5060>
Content-Length: 0


---
[Apr 19 20:45:51] NOTICE[519]: chan_sip.c:13071 sip_reregister:    -- Re-registration for  akoei-111@pbxes.org

<--- SIP read from UDP:162.213.111.22:5060 --->
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 72.141.206.9:5060;branch=z9hG4bK66623a11;rport=5060
To: <sip:14164778887@voip2.freephoneline.ca>;tag=e2c31937
From: <sip:14164778887@voip2.freephoneline.ca>;tag=as14c0f203
Call-ID: 5972a742788f5d8619a86f3a5e7a3802@192.168.5.8
CSeq: 104 REGISTER
WWW-Authenticate: Digest nonce="1492649151:91679e828d9457f0fde2e2039c56abec",algorithm=MD5,realm="208.65.240.165",stale=true
Content-Length: 0
Contact: <sip:14164778887@72.141.206.9:5060>

<------------->
--- (9 headers 0 lines) ---
Responding to challenge, registration to domain/host name voip2.freephoneline.ca
REGISTER 11 headers, 0 lines
Reliably Transmitting (NAT) to 162.213.111.22:5060:
REGISTER sip:voip2.freephoneline.ca SIP/2.0
Via: SIP/2.0/UDP 72.141.206.9:5060;branch=z9hG4bK2e6c3ae2;rport
Max-Forwards: 70
From: <sip:14164778887@voip2.freephoneline.ca>;tag=as61631088
To: <sip:14164778887@voip2.freephoneline.ca>
Call-ID: 5972a742788f5d8619a86f3a5e7a3802@192.168.5.8
CSeq: 105 REGISTER
User-Agent: Linksys/RT31P2-3.1.6(LI)
Authorization: Digest username="14164778887", realm="208.65.240.165", algorithm=MD5, uri="sip:voip2.freephoneline.ca", nonce="1492649151:91679e828d9457f0fde2e2039c56abec", response="ca1bfe05ee24f4a7f7e9a63392e6196a"
Expires: 3600
Contact: <sip:14164778887@72.141.206.9:5060>
Content-Length: 0


---
[Apr 19 20:45:52] NOTICE[519]: chan_sip.c:20755 handle_response_register: Outbound Registration: Expiry for sip.sipsorcery.com is 3600 sec (Scheduling reregistration in 3585 s)
Retransmitting #1 (NAT) to 162.213.111.22:5060:
REGISTER sip:voip2.freephoneline.ca SIP/2.0
Via: SIP/2.0/UDP 72.141.206.9:5060;branch=z9hG4bK2e6c3ae2;rport
Max-Forwards: 70
From: <sip:14164778887@voip2.freephoneline.ca>;tag=as61631088
To: <sip:14164778887@voip2.freephoneline.ca>
Call-ID: 5972a742788f5d8619a86f3a5e7a3802@192.168.5.8
CSeq: 105 REGISTER
User-Agent: Linksys/RT31P2-3.1.6(LI)
Authorization: Digest username="14164778887", realm="208.65.240.165", algorithm=MD5, uri="sip:voip2.freephoneline.ca", nonce="1492649151:91679e828d9457f0fde2e2039c56abec", response="ca1bfe05ee24f4a7f7e9a63392e6196a"
Expires: 3600
Contact: <sip:14164778887@72.141.206.9:5060>
Content-Length: 0


---
Retransmitting #2 (NAT) to 162.213.111.22:5060:
REGISTER sip:voip2.freephoneline.ca SIP/2.0
Via: SIP/2.0/UDP 72.141.206.9:5060;branch=z9hG4bK2e6c3ae2;rport
Max-Forwards: 70
From: <sip:14164778887@voip2.freephoneline.ca>;tag=as61631088
To: <sip:14164778887@voip2.freephoneline.ca>
Call-ID: 5972a742788f5d8619a86f3a5e7a3802@192.168.5.8
CSeq: 105 REGISTER
User-Agent: Linksys/RT31P2-3.1.6(LI)
Authorization: Digest username="14164778887", realm="208.65.240.165", algorithm=MD5, uri="sip:voip2.freephoneline.ca", nonce="1492649151:91679e828d9457f0fde2e2039c56abec", response="ca1bfe05ee24f4a7f7e9a63392e6196a"
Expires: 3600
Contact: <sip:14164778887@72.141.206.9:5060>
Content-Length: 0


---
Retransmitting #3 (NAT) to 162.213.111.22:5060:
REGISTER sip:voip2.freephoneline.ca SIP/2.0
Via: SIP/2.0/UDP 72.141.206.9:5060;branch=z9hG4bK2e6c3ae2;rport
Max-Forwards: 70
From: <sip:14164778887@voip2.freephoneline.ca>;tag=as61631088
To: <sip:14164778887@voip2.freephoneline.ca>
Call-ID: 5972a742788f5d8619a86f3a5e7a3802@192.168.5.8
CSeq: 105 REGISTER
User-Agent: Linksys/RT31P2-3.1.6(LI)
Authorization: Digest username="14164778887", realm="208.65.240.165", algorithm=MD5, uri="sip:voip2.freephoneline.ca", nonce="1492649151:91679e828d9457f0fde2e2039c56abec", response="ca1bfe05ee24f4a7f7e9a63392e6196a"
Expires: 3600
Contact: <sip:14164778887@72.141.206.9:5060>
Content-Length: 0


---
Retransmitting #4 (NAT) to 162.213.111.22:5060:
REGISTER sip:voip2.freephoneline.ca SIP/2.0
Via: SIP/2.0/UDP 72.141.206.9:5060;branch=z9hG4bK2e6c3ae2;rport
Max-Forwards: 70
From: <sip:14164778887@voip2.freephoneline.ca>;tag=as61631088
To: <sip:14164778887@voip2.freephoneline.ca>
Call-ID: 5972a742788f5d8619a86f3a5e7a3802@192.168.5.8
CSeq: 105 REGISTER
User-Agent: Linksys/RT31P2-3.1.6(LI)
Authorization: Digest username="14164778887", realm="208.65.240.165", algorithm=MD5, uri="sip:voip2.freephoneline.ca", nonce="1492649151:91679e828d9457f0fde2e2039c56abec", response="ca1bfe05ee24f4a7f7e9a63392e6196a"
Expires: 3600
Contact: <sip:14164778887@72.141.206.9:5060>
Content-Length: 0


---
Retransmitting #5 (NAT) to 162.213.111.22:5060:
REGISTER sip:voip2.freephoneline.ca SIP/2.0
Via: SIP/2.0/UDP 72.141.206.9:5060;branch=z9hG4bK2e6c3ae2;rport
Max-Forwards: 70
From: <sip:14164778887@voip2.freephoneline.ca>;tag=as61631088
To: <sip:14164778887@voip2.freephoneline.ca>
Call-ID: 5972a742788f5d8619a86f3a5e7a3802@192.168.5.8
CSeq: 105 REGISTER
User-Agent: Linksys/RT31P2-3.1.6(LI)
Authorization: Digest username="14164778887", realm="208.65.240.165", algorithm=MD5, uri="sip:voip2.freephoneline.ca", nonce="1492649151:91679e828d9457f0fde2e2039c56abec", response="ca1bfe05ee24f4a7f7e9a63392e6196a"
Expires: 3600
Contact: <sip:14164778887@72.141.206.9:5060>
Content-Length: 0


---
OpenWrt*CLI> sip show registry
Host                                    dnsmgr Username       Refresh State                Reg.Time                
pbxes.org:5060                          N      akoei-111         3585 Request Sent         Wed, 19 Apr 2017 19:46:06
sip.sipsorcery.com:5060                 N      akoei             3585 Registered           Wed, 19 Apr 2017 20:45:52
voip2.freephoneline.ca:5060             N      14164778887       3585 Auth. Sent           Wed, 19 Apr 2017 19:46:06
3 SIP registrations.
Retransmitting #6 (NAT) to 162.213.111.22:5060:
REGISTER sip:voip2.freephoneline.ca SIP/2.0
Via: SIP/2.0/UDP 72.141.206.9:5060;branch=z9hG4bK2e6c3ae2;rport
Max-Forwards: 70
From: <sip:14164778887@voip2.freephoneline.ca>;tag=as61631088
To: <sip:14164778887@voip2.freephoneline.ca>
Call-ID: 5972a742788f5d8619a86f3a5e7a3802@192.168.5.8
CSeq: 105 REGISTER
User-Agent: Linksys/RT31P2-3.1.6(LI)
Authorization: Digest username="14164778887", realm="208.65.240.165", algorithm=MD5, uri="sip:voip2.freephoneline.ca", nonce="1492649151:91679e828d9457f0fde2e2039c56abec", response="ca1bfe05ee24f4a7f7e9a63392e6196a"
Expires: 3600
Contact: <sip:14164778887@72.141.206.9:5060>
Content-Length: 0


---

<--- SIP read from UDP:162.213.111.22:5060 --->

<------------->
Retransmitting #7 (NAT) to 162.213.111.22:5060:
REGISTER sip:voip2.freephoneline.ca SIP/2.0
Via: SIP/2.0/UDP 72.141.206.9:5060;branch=z9hG4bK2e6c3ae2;rport
Max-Forwards: 70
From: <sip:14164778887@voip2.freephoneline.ca>;tag=as61631088
To: <sip:14164778887@voip2.freephoneline.ca>
Call-ID: 5972a742788f5d8619a86f3a5e7a3802@192.168.5.8
CSeq: 105 REGISTER
User-Agent: Linksys/RT31P2-3.1.6(LI)
Authorization: Digest username="14164778887", realm="208.65.240.165", algorithm=MD5, uri="sip:voip2.freephoneline.ca", nonce="1492649151:91679e828d9457f0fde2e2039c56abec", response="ca1bfe05ee24f4a7f7e9a63392e6196a"
Expires: 3600
Contact: <sip:14164778887@72.141.206.9:5060>
Content-Length: 0


---
Retransmitting #8 (NAT) to 162.213.111.22:5060:
REGISTER sip:voip2.freephoneline.ca SIP/2.0
Via: SIP/2.0/UDP 72.141.206.9:5060;branch=z9hG4bK2e6c3ae2;rport
Max-Forwards: 70
From: <sip:14164778887@voip2.freephoneline.ca>;tag=as61631088
To: <sip:14164778887@voip2.freephoneline.ca>
Call-ID: 5972a742788f5d8619a86f3a5e7a3802@192.168.5.8
CSeq: 105 REGISTER
User-Agent: Linksys/RT31P2-3.1.6(LI)
Authorization: Digest username="14164778887", realm="208.65.240.165", algorithm=MD5, uri="sip:voip2.freephoneline.ca", nonce="1492649151:91679e828d9457f0fde2e2039c56abec", response="ca1bfe05ee24f4a7f7e9a63392e6196a"
Expires: 3600
Contact: <sip:14164778887@72.141.206.9:5060>
Content-Length: 0


---
Retransmitting #9 (NAT) to 162.213.111.22:5060:
REGISTER sip:voip2.freephoneline.ca SIP/2.0
Via: SIP/2.0/UDP 72.141.206.9:5060;branch=z9hG4bK2e6c3ae2;rport
Max-Forwards: 70
From: <sip:14164778887@voip2.freephoneline.ca>;tag=as61631088
To: <sip:14164778887@voip2.freephoneline.ca>
Call-ID: 5972a742788f5d8619a86f3a5e7a3802@192.168.5.8
CSeq: 105 REGISTER
User-Agent: Linksys/RT31P2-3.1.6(LI)
Authorization: Digest username="14164778887", realm="208.65.240.165", algorithm=MD5, uri="sip:voip2.freephoneline.ca", nonce="1492649151:91679e828d9457f0fde2e2039c56abec", response="ca1bfe05ee24f4a7f7e9a63392e6196a"
Expires: 3600
Contact: <sip:14164778887@72.141.206.9:5060>
Content-Length: 0


---
Retransmitting #10 (NAT) to 162.213.111.22:5060:
REGISTER sip:voip2.freephoneline.ca SIP/2.0
Via: SIP/2.0/UDP 72.141.206.9:5060;branch=z9hG4bK2e6c3ae2;rport
Max-Forwards: 70
From: <sip:14164778887@voip2.freephoneline.ca>;tag=as61631088
To: <sip:14164778887@voip2.freephoneline.ca>
Call-ID: 5972a742788f5d8619a86f3a5e7a3802@192.168.5.8
CSeq: 105 REGISTER
User-Agent: Linksys/RT31P2-3.1.6(LI)
Authorization: Digest username="14164778887", realm="208.65.240.165", algorithm=MD5, uri="sip:voip2.freephoneline.ca", nonce="1492649151:91679e828d9457f0fde2e2039c56abec", response="ca1bfe05ee24f4a7f7e9a63392e6196a"
Expires: 3600
Contact: <sip:14164778887@72.141.206.9:5060>
Content-Length: 0
Jake wrote:I would do as Liptonbrisk suggest and check your timers, especially the retry one.

FPL will block your IP if you try and register/re-register too often.

When you changed from Rogers to Fido did you change the SIP server you were registered to? I know some Rogers customers have to use sip4 and a different port number. It could be that the sip4 server is a little bit nicer when it comes to registration times.

You have probably found that switching between voip. and voip2. servers gets you reconnected again, for about an hour. This is because the IP ban is server specific so by the time you get banned on the first it has cleared on the second allowing you to reconnect.
.
Top
akoei
Quiet One
Posts: 38
Joined: 12/14/2009
SIP Device Name: asterisk
ISP Name: 3web

Re: registration only keeps one hour

Post by akoei »

I have figured it out, it is not freephoneline issue at all, it is Fido, my ISP issue: when I tested with my 4G mobile internet, it works. I have seen ppl complains about Fido cable modem firmware, under bridge mode, so I again tested with gateway mode, even though with 2 level NATing, the issue is gone. I will ask Fido update my fireware, thank you Jack and Liptonbrisk
Top
Post Reply

Return to “Community Support”