Freephoneline registration timers are important!
Posted: 02/16/2023
If you don't follow these rules or configure your SIP application or device properly, your FPL account may be blocked. Account/registration blocking enforcement for low registration interval timers is relatively new.
Visit https://support.freephoneline.ca/hc/en- ... redentials
Registration Interval: 3600 seconds (1 hour)
Registration Expiry: 3600 seconds (1 hour)
Failed Registration Re-Try Interval: 120 seconds
(NAT) Keep Alive Interval: 20 seconds
Frequent registrations (via UDP transport, in this case) do create system load. Use a 20 second keep-alive interval to retain NAT associations; don't rely on frequent registrations to do it.
--
By the way, Freephoneline uses a 15 minute session timer at the moment. Your outbound calls may drop at the 15 minute mark of the call if you don't register FPL with the device or app you're using. This isn't related to the registration timers listed above, but the point is you may need to be registered in order for calls to continue past 15 minutes. Incoming calls require registration, regardless. Outgoing calls don't (but may drop after 15 minutes if you're not registered). When a SIP app, ATA, or IP phone is not registered with your Freephoneline account, placing a call on hold and resuming the call before the 15 minute interval is reached will allow the call to continue past 15 minutes.
Similarly, using *67 in Linksys ATAs/Cisco ATAs with FPL has been reported to drop calls after 15 minutes.
So, trying to block outbound caller ID (at the time of writing) should be avoided with those devices.
In your Linksys/Cisco ATA, navigate to Voice tab-->Line tab (whichever you use for FPL)-->Supplementary Service Subscription-->Block CID Serv:
a) change to no
b) Click "submit"
Do this to avoid 15 minute call disconnections with Freephoneline.
Visit https://support.freephoneline.ca/hc/en- ... redentials
Registration Interval: 3600 seconds (1 hour)
Registration Expiry: 3600 seconds (1 hour)
Failed Registration Re-Try Interval: 120 seconds
(NAT) Keep Alive Interval: 20 seconds
Frequent registrations (via UDP transport, in this case) do create system load. Use a 20 second keep-alive interval to retain NAT associations; don't rely on frequent registrations to do it.
--
By the way, Freephoneline uses a 15 minute session timer at the moment. Your outbound calls may drop at the 15 minute mark of the call if you don't register FPL with the device or app you're using. This isn't related to the registration timers listed above, but the point is you may need to be registered in order for calls to continue past 15 minutes. Incoming calls require registration, regardless. Outgoing calls don't (but may drop after 15 minutes if you're not registered). When a SIP app, ATA, or IP phone is not registered with your Freephoneline account, placing a call on hold and resuming the call before the 15 minute interval is reached will allow the call to continue past 15 minutes.
Similarly, using *67 in Linksys ATAs/Cisco ATAs with FPL has been reported to drop calls after 15 minutes.
So, trying to block outbound caller ID (at the time of writing) should be avoided with those devices.
In your Linksys/Cisco ATA, navigate to Voice tab-->Line tab (whichever you use for FPL)-->Supplementary Service Subscription-->Block CID Serv:
a) change to no
b) Click "submit"
Do this to avoid 15 minute call disconnections with Freephoneline.