c00lman wrote:
our ISP is with Shaw and modem is (XB6) in bridge mode.
our router is a FortiGate 60D
Were incoming calls working at any point when you had both the XB6 and FortiGate 60D?
Is this problem happening with incoming calls from all carriers (ex. Telus, Rogers, Bell) or just one carrier? Is it happening with all numbers?
Note that only one registration per FPL account is allowed at any time. An ATA is one registration. A SIP app is another.
When there are multiple devices/softphones/lines using the same account, only the most recent registration is valid. The previous device will lose registration (despite whatever Freephoneline's web portal indicates; remember registration interval is 1hr with FPL, and that status is updated hourly at the next registration interval), and, consequently, incoming calls will not work on it. This is especially important to consider if someone else is using your SIP credentials (username and password) that are found after logging in at
https://www.freephoneline.ca/showSipSettings or if you're trying to register your FPL account with a smartphone SIP app or with another device. Registration is required for incoming calls. It is not required for outgoing calls. Another concern is that multiple registration attempts can lead to temporary IP bans. The more devices being used with the exact same FPL account can make the temporary ban happen more quickly. Each time you reboot or restart your ATA or SIP app, it's attempting to register with Freephoneline again. Multiple registration attempts within a short period can result in temporary IP ban. Each time you reboot your ATA it's attempting to register with FPL's proxy server.
Please follow the steps, step by step, down the list:
1. Login to your PAP2 (ensure you select "Advanced view" and "admin").
2. In your PAP2, Navigate to Line 1 (or whatever Line you're using for FPL)-->SIP settings, and change SIP Port to a random number between 30000 and 60000. Do this for security reasons. Also, this step may help to temporarily address a corrupted NAT association that's developed between a router and ATA.
If you're using both Lines, change both SIP Port for each line to a random number between 30000 and 60000. But do not use the exact same SIP Port number for both Lines.
3. In your PAP2T, Navigate to the SIP tab-->NAT Support Parameters, and make sure that the following settings are enabled:
a)Handle VIA received-->yes
b)Handle VIA rport-->yes
c)Substitute VIA Addr-->yes
This helps to ensure RTP (the streaming audio packets sent by FPL's server) packets are sent to your public WAN IP address as opposed to your LAN IP address (nowhere/outer space).
4. NAT Keep Alive Intvl should be 20
5. Navigate to Line used for FPL-->NAT settings
a) NAT Mapping enabled --> yes
b) NAT Keep alive enabled --> yes
c) NAT Keep Alive Msg: $NOTIFY
d) NAT Keep Alive Dest: $PROXY
6. Navigate to Voice-->SIP-->SIP Timer Values (sec)
a. Reg Retry Intvl should be 120 seconds
https://support.freephoneline.ca/hc/en- ... redentials
This step is not related to your problem, but old guides didn't include this setting.
7. You stated you tried voip4.freephoneline.ca:6060
Let's keep using it for testing purposes
Double check to ensure Register Expires is 3600 seconds (it likely is).
8. After changing and savings settings, reboot your devices. Proper device reboot order is always modem (wait for it to be fully up and running first before rebooting your)-->router (wait for it to be fulling up and running first before rebooting your)-->ATA
9. Log into the ATA. Navigate to Info tab-->Line (FPL) status-->Registration State.
What does it indicate?
Hopefully, the line is registered.
10. Test with an incoming call. Hopefully it works.
11. If the incoming call fails, connect the ATA directly to XB6 in bridge mode. Reboot XB6 (wait for it to be up and running fully). Then reboot ATA. Test again. If that works, the problem involves FortiGate 60D, which I am unfortunately not familiar with. Keep in mind the ATA will be unprotected by the XB6 (due to it being in bridge mode). I would just do this briefly for testing and not keep the ATA permanently connected to the XB6 while it's in bridge mode.