FreePBX 15.0.17.34 / Current Asterisk Version: 16.17.0 / all modules up to date
Apologies if my description is a bit vague tho’ I will attempt to describe the issue as well as I can. Also I’m not sure that this forum is the right place for this problem, but I’ll start here.
The FreePBX server is located in Vancouver BC and there are a number of Cisco Linksys SPA 922 IP phones deployed as remote extensions across Canada, including Ladysmith on Vancouver Island BC, Kelowna BC, Edmonton AB, and as well as one at a cottage in a wilderness location about 3 hours north of Toronto ON. I chose the Cisco 922 because they’re cheap to buy, easy to configure as a remote phone (factory reset and modify a couple of parameters), not terribly complicated for end users to operate, and light enough so they’re cheap to ship. (In addition to the 922s, the FreePBX server has a number of phones of various makes and models–Yealink, Aastra, Cisco, Sangoma, etc.–deployed in the city of Vancouver as remote extensions but they are not at issue here).
All of the 922s are in use and working well except for the 922 at a cottage in Ontario, so I am only concerned with the latter. Unfortunately, except for the logs on the FreePBX server, I don’t have much visibility into the 922 as somebody is physically only at the cottage for a few hours on occasional weekends.
Here’s the issue. A few weeks ago I had someone at the cottage plug in the phone to the AC adapter, plug in an Ethernet cable into the “router” and into the phone, and send me the public IP address of the “router” (as I said, simple for users to set up). I have a pfSense firewall configured with rules to allow access to specific IP addresses (i.e., the public IPs of remote phones) and their specific SIP and RTP port ranges. It all works very well, except for the cottage 922.
Initially, as far as I can recall, the cottage 922 worked just fine. I made a few test calls to and from the 922, and checked that the 922 could make local calls here in Vancouver, and all seemed well. I have a FOP2 server, and I could see that the cottage 922 was available, so I pretty much forgot about it.
However, I started noticing some random “chattering” (unreachable/reachable) in the logs, as follows (IP, port, and extension anonymized):
[2021-05-30 09:13:42] VERBOSE[6253] res_pjsip/pjsip_configuration.c: Endpoint 1004 is now Reachable
[2021-05-30 09:13:42] VERBOSE[6253] res_pjsip/pjsip_options.c: Contact 1004/sip:[email protected]:5062;x-ast-orig-host=192.168.0.159:5061 is now Reachable. RTT: 1221.096 msec
[2021-05-30 09:14:44] VERBOSE[31685] res_pjsip/pjsip_configuration.c: Endpoint 1004 is now Unreachable
[2021-05-30 09:14:44] VERBOSE[31685] res_pjsip/pjsip_options.c: Contact 1004/sip:[email protected]:5062;x-ast-orig-host=192.168.0.159:5061 is now Unreachable. RTT: 0.000 msec
[2021-05-30 12:20:41] VERBOSE[28683] res_pjsip/pjsip_configuration.c: Endpoint 1004 is now Reachable
[2021-05-30 12:20:41] VERBOSE[28683] res_pjsip/pjsip_options.c: Contact 1004/sip:[email protected]:5062;x-ast-orig-host=192.168.0.159:5061 is now Reachable. RTT: 136.431 msec
[2021-05-30 12:21:44] VERBOSE[31756] res_pjsip/pjsip_configuration.c: Endpoint 1004 is now Unreachable
[2021-05-30 12:21:44] VERBOSE[31756] res_pjsip/pjsip_options.c: Contact 1004/sip:[email protected]:5062;x-ast-orig-host=192.168.0.159:5061 is now Unreachable. RTT: 0.000 msec
[2021-05-30 13:07:42] VERBOSE[5904] res_pjsip/pjsip_configuration.c: Endpoint 1004 is now Reachable
[2021-05-30 13:07:42] VERBOSE[5904] res_pjsip/pjsip_options.c: Contact 1004/sip:[email protected]:5062;x-ast-orig-host=192.168.0.159:5061 is now Reachable. RTT: 438.286 msec
[2021-05-30 13:08:44] VERBOSE[6253] res_pjsip/pjsip_configuration.c: Endpoint 1004 is now Unreachable
[2021-05-30 13:08:44] VERBOSE[6253] res_pjsip/pjsip_options.c: Contact 1004/sip:[email protected]:5062;x-ast-orig-host=192.168.0.159:5061 is now Unreachable. RTT: 0.000 msec
[2021-05-30 13:54:43] VERBOSE[31685] res_pjsip/pjsip_configuration.c: Endpoint 1004 is now Reachable
[2021-05-30 13:54:43] VERBOSE[31685] res_pjsip/pjsip_options.c: Contact 1004/sip:[email protected]:5062;x-ast-orig-host=192.168.0.159:5061 is now Reachable. RTT: 1432.722 msec
[2021-05-30 13:55:44] VERBOSE[28683] res_pjsip/pjsip_configuration.c: Endpoint 1004 is now Unreachable
[2021-05-30 13:55:44] VERBOSE[28683] res_pjsip/pjsip_options.c: Contact 1004/sip:[email protected]:5062;x-ast-orig-host=192.168.0.159:5061 is now Unreachable. RTT: 0.000 msec
[2021-05-30 14:41:42] VERBOSE[5904] res_pjsip/pjsip_configuration.c: Endpoint 1004 is now Reachable
[2021-05-30 14:41:42] VERBOSE[5904] res_pjsip/pjsip_options.c: Contact 1004/sip:[email protected]:5062;x-ast-orig-host=192.168.0.159:5061 is now Reachable. RTT: 1273.873 msec
[2021-05-30 14:42:44] VERBOSE[31685] res_pjsip/pjsip_configuration.c: Endpoint 1004 is now Unreachable
[2021-05-30 14:42:44] VERBOSE[31685] res_pjsip/pjsip_options.c: Contact 1004/sip:[email protected]:5062;x-ast-orig-host=192.168.0.159:5061 is now Unreachable. RTT: 0.000 msec
[2021-05-30 17:48:41] VERBOSE[11409] res_pjsip/pjsip_configuration.c: Endpoint 1004 is now Reachable
[2021-05-30 17:48:41] VERBOSE[11409] res_pjsip/pjsip_options.c: Contact 1004/sip:[email protected]:5062;x-ast-orig-host=192.168.0.159:5061 is now Reachable. RTT: 193.525 msec
[2021-05-30 17:49:44] VERBOSE[11409] res_pjsip/pjsip_configuration.c: Endpoint 1004 is now Unreachable
[2021-05-30 17:49:44] VERBOSE[11409] res_pjsip/pjsip_options.c: Contact 1004/sip:[email protected]:5062;x-ast-orig-host=192.168.0.159:5061 is now Unreachable. RTT: 0.000 msec
[2021-05-30 18:35:43] VERBOSE[6253] res_pjsip/pjsip_configuration.c: Endpoint 1004 is now Reachable
[2021-05-30 18:35:43] VERBOSE[6253] res_pjsip/pjsip_options.c: Contact 1004/sip:[email protected]:5062;x-ast-orig-host=192.168.0.159:5061 is now Reachable. RTT: 1553.815 msec
[2021-05-30 18:36:44] VERBOSE[31685] res_pjsip/pjsip_configuration.c: Endpoint 1004 is now Unreachable
[2021-05-30 18:36:44] VERBOSE[31685] res_pjsip/pjsip_options.c: Contact 1004/sip:[email protected]:5062;x-ast-orig-host=192.168.0.159:5061 is now Unreachable. RTT: 0.000 msec
The remote extension is mostly down, but as can be seen, it does come up for a minute or so every hour or two. I’ve actually been able to make a call to that extension in the brief interval that it’s up, tho’ nobody has answered the phone. [Also today, I saw that the public IP had changed from 11.22.33.117 to 11.22.33.2 but I was able to modify the rules in pfSense to accommodate this.]
I did check with someone at the cottage who told me that the “router” that’s being used is a Bell Turbo Hub, which is apparently something that Bell (i.e., the ISP) uses to provide remote locations such as those in Ontario cottage country with reasonably fast internet access. I believe the Bell Turbo Hub is just a hot spot which provides access from the nearest cell tower.
If anyone has suggestions on how I can further this issue it would be appreciated.