I manage dozens of different FPBX servers for multiple customers. I have one in particular that seems to have persistent issues with multiple extensions becoming unreachable, then within a minute, becoming reachable again. This particular customer has phones in multiple locations, where their FPBX server is hosted in the cloud. Each of the locations has a different internet provider, one of which is fiber, the rest are cable. It seems every few hours, random endpoints become unreachable, then almost all at the same time become reachable again. It’s not just the phones either, I see entries in the logs for the trunks doing the same thing, at the same times as the phones. But it’s intermittent. Not all extensions do it, and not both of the trunks go. It does seem to be affecting their calls too, as I have been getting reports that calls drop frequently. They have a mix of Polycom and Yealink phones and it does not seem to matter, as endpoints drop from either group and from any of the locations.
This past weekend, I downloaded the latest FPBX image and performed a wipe / reinstall of everything, while also bumping up their asterisk version from 16 to 18.
FreePBX Version: 16.0.21.3
Asterisk: 18.9 (Asterisk 18 Certified LTS)
The only thing consistent from the reload was the backup, so I’m not sure if it’s a config issue with any of those modules that was restored from the backup. I’m not seeing any issues otherwise.
What makes you think it’s the PBX at fault? Just an observation, I’m not going to get into the ins and outs of what you should do next. However….You say each of the locations have a different internet provider, which seems strange in itself for a single business to have so many ISPs — unless they’re all home workers on consumer broadband and not disabling SIP ALG, perhaps? Are their dynamic IP addresses changing frequently? It doesn’t make sense otherwise. What’s the common factor here, assuming FreePBX isn’t the issue for any of your other customers? If you’re sure the PBX is the problem then I have seen similar drops before: Shut off responsive firewall and proactively and reactively whitelist, perhaps just to test temporarily, and see if the drops stop.
The common factor here has to be something in the PBX, I just can’t put my finger on it. Regardless if there were endpoints or not, the trunks are dropping along with them. I have two different trunks established to Twilio, for reference. All of my other servers I manage have the similar trunks setup to the same provider. Each of the locations, now three, have Zyxel firewalls that I have personally configured. So SIP ALG settings are all disabled, and QoS has been enabled for the phones. They all have static IP’s which are already whitelisted in the firewall. I’m not sure what you mean by that’s strange there are different ISP’s at each location. It’s the same business with different offices across the area. They don’t necessarily have access to the exact same service at each one. I was simply pointing out, it can’t possibly be an ISP related issue. Responsive firewall does have just one exception added because they do have a remote worker. Based on this information, would your recommendation still be to disable the responsive firewall? I’ve already got their IP’s whitelisted.
Set up a test endpoint on your own reliable connection and see if it drops. I bet it won’t. I got the impression from your post it was more than 3 locations, my apologies. Perhaps put an endpoint bypassing the firewall and see if it stays up. I have stopped PJSIP trunks dropping in the past by disabling responsive firewall, so perhaps try that. Good luck.
When I look at the logs for asterisk, I do not see anything about it failing or stopping for any reason, especially before the blocks of entries when the endpoints drop and come back. This is the full log that I am looking at, so if there are different logs I should check, please let me know. They do have a constant use during business hours, typically 3 calls at any time minimum. The VM I set up is actually on server hardware I control, housed in a datacenter here in the local area of the customer. The VM itself has 8GB of RAM with 8 Cores of the CPU (Intel Xeon E5-2680). Currently, their load is 2 calls and their load averages are 0.25 0.13 0.14. So as far as I can tell, I don’t think it’s getting stressed by load.
Thanks for the suggestion. I took your advice and completely disabled responsive firewall. I continued monitoring the server and I noticed 11 extensions, out of 52 currently registered, dropped within 3 seconds of each other, then exactly 12 seconds later, they all came back up.
Here is what I see in the logs:
303264[2022-07-18 16:31:17] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 305 is now Unreachable
303265[2022-07-18 16:31:17] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 305/sip:[email protected]:47409;transport=TLS;x-ast-orig-host=192.168.2.112:47409 is now Unreachable. RTT: 0.000 msec
303266[2022-07-18 16:31:17] VERBOSE[131705] res_pjsip/pjsip_configuration.c: Endpoint 347 is now Unreachable
303267[2022-07-18 16:31:17] VERBOSE[131705] res_pjsip/pjsip_options.c: Contact 347/sip:[email protected]:12410;transport=TLS;x-ast-orig-host=192.168.2.58:12410 is now Unreachable. RTT: 0.000 msec
303268[2022-07-18 16:31:17] VERBOSE[135102] res_pjsip/pjsip_configuration.c: Endpoint 324 is now Unreachable
303269[2022-07-18 16:31:17] VERBOSE[135102] res_pjsip/pjsip_options.c: Contact 324/sip:[email protected]:32963;transport=TLS;x-ast-orig-host=192.168.2.83:32963 is now Unreachable. RTT: 0.000 msec
303270[2022-07-18 16:31:18] VERBOSE[135102] res_pjsip/pjsip_configuration.c: Endpoint 327 is now Unreachable
303271[2022-07-18 16:31:18] VERBOSE[135102] res_pjsip/pjsip_options.c: Contact 327/sip:[email protected]:12646;transport=TLS;x-ast-orig-host=192.168.2.93:12646 is now Unreachable. RTT: 0.000 msec
303272[2022-07-18 16:31:18] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint 319 is now Unreachable
303273[2022-07-18 16:31:18] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact 319/sip:[email protected]:35337;transport=TLS;x-ast-orig-host=192.168.2.68:35337 is now Unreachable. RTT: 0.000 msec
303274[2022-07-18 16:31:19] VERBOSE[135102] res_pjsip/pjsip_configuration.c: Endpoint 300 is now Unreachable
303275[2022-07-18 16:31:19] VERBOSE[135102] res_pjsip/pjsip_options.c: Contact 300/sip:[email protected]:62109;transport=TLS;x-ast-orig-host=192.168.2.101:62109 is now Unreachable. RTT: 0.000 msec
303276[2022-07-18 16:31:19] VERBOSE[131705] res_pjsip/pjsip_configuration.c: Endpoint 312 is now Unreachable
303277[2022-07-18 16:31:19] VERBOSE[131705] res_pjsip/pjsip_options.c: Contact 312/sip:[email protected]:49399;transport=TLS;x-ast-orig-host=192.168.2.54:49399 is now Unreachable. RTT: 0.000 msec
303278[2022-07-18 16:31:19] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 348 is now Unreachable
303279[2022-07-18 16:31:19] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 348/sip:[email protected]:12410;transport=TLS;x-ast-orig-host=192.168.2.58:12410 is now Unreachable. RTT: 0.000 msec
303280[2022-07-18 16:31:20] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 345 is now Unreachable
303281[2022-07-18 16:31:20] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 345/sip:[email protected]:39910;transport=TLS;x-ast-orig-host=192.168.2.196:39910 is now Unreachable. RTT: 0.000 msec
303282[2022-07-18 16:31:20] VERBOSE[131705] res_pjsip/pjsip_configuration.c: Endpoint 350 is now Unreachable
303283[2022-07-18 16:31:20] VERBOSE[131705] res_pjsip/pjsip_options.c: Contact 350/sip:[email protected]:43723;transport=TLS;x-ast-orig-host=192.168.2.77:43723 is now Unreachable. RTT: 0.000 msec
303284[2022-07-18 16:31:20] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 304 is now Unreachable
303285[2022-07-18 16:31:20] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 304/sip:[email protected]:35557;transport=TLS;x-ast-orig-host=192.168.2.102:35557 is now Unreachable. RTT: 0.000 msec
303286[2022-07-18 16:31:29] VERBOSE[131705] res_pjsip/pjsip_configuration.c: Endpoint 305 is now Reachable
303287[2022-07-18 16:31:29] VERBOSE[131705] res_pjsip/pjsip_options.c: Contact 305/sip:[email protected]:47409;transport=TLS;x-ast-orig-host=192.168.2.112:47409 is now Reachable. RTT: 6.429 msec
303288[2022-07-18 16:31:29] VERBOSE[131705] res_pjsip/pjsip_configuration.c: Endpoint 347 is now Reachable
303289[2022-07-18 16:31:29] VERBOSE[131705] res_pjsip/pjsip_options.c: Contact 347/sip:[email protected]:12410;transport=TLS;x-ast-orig-host=192.168.2.58:12410 is now Reachable. RTT: 8.513 msec
303290[2022-07-18 16:31:29] VERBOSE[135102] res_pjsip/pjsip_configuration.c: Endpoint 324 is now Reachable
303291[2022-07-18 16:31:29] VERBOSE[135102] res_pjsip/pjsip_options.c: Contact 324/sip:[email protected]:32963;transport=TLS;x-ast-orig-host=192.168.2.83:32963 is now Reachable. RTT: 5.682 msec
303292[2022-07-18 16:31:30] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 327 is now Reachable
303293[2022-07-18 16:31:30] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 327/sip:[email protected]:12646;transport=TLS;x-ast-orig-host=192.168.2.93:12646 is now Reachable. RTT: 16.715 msec
303294[2022-07-18 16:31:30] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 319 is now Reachable
303295[2022-07-18 16:31:30] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 319/sip:[email protected]:35337;transport=TLS;x-ast-orig-host=192.168.2.68:35337 is now Reachable. RTT: 8.085 msec
303296[2022-07-18 16:31:31] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 300 is now Reachable
303297[2022-07-18 16:31:31] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 300/sip:[email protected]:62109;transport=TLS;x-ast-orig-host=192.168.2.101:62109 is now Reachable. RTT: 9.635 msec
303298[2022-07-18 16:31:31] VERBOSE[135102] res_pjsip/pjsip_configuration.c: Endpoint 312 is now Reachable
303299[2022-07-18 16:31:31] VERBOSE[135102] res_pjsip/pjsip_options.c: Contact 312/sip:[email protected]:49399;transport=TLS;x-ast-orig-host=192.168.2.54:49399 is now Reachable. RTT: 7.788 msec
303300[2022-07-18 16:31:31] VERBOSE[131705] res_pjsip/pjsip_configuration.c: Endpoint 348 is now Reachable
303301[2022-07-18 16:31:31] VERBOSE[131705] res_pjsip/pjsip_options.c: Contact 348/sip:[email protected]:12410;transport=TLS;x-ast-orig-host=192.168.2.58:12410 is now Reachable. RTT: 8.504 msec
303302[2022-07-18 16:31:32] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 345 is now Reachable
303303[2022-07-18 16:31:32] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 345/sip:[email protected]:39910;transport=TLS;x-ast-orig-host=192.168.2.196:39910 is now Reachable. RTT: 5.920 msec
303304[2022-07-18 16:31:32] VERBOSE[131705] res_pjsip/pjsip_configuration.c: Endpoint 350 is now Reachable
303305[2022-07-18 16:31:32] VERBOSE[131705] res_pjsip/pjsip_options.c: Contact 350/sip:[email protected]:43723;transport=TLS;x-ast-orig-host=192.168.2.77:43723 is now Reachable. RTT: 6.949 msec
303306[2022-07-18 16:31:32] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint 304 is now Reachable
303307[2022-07-18 16:31:32] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact 304/sip:[email protected]:35557;transport=TLS;x-ast-orig-host=192.168.2.102:35557 is now Reachable. RTT: 6.944 msec
From what I can tell, during this instance, all of these phones it happen to be from one location. But it was only about 20% of their total phones at this facility. But I do not see any errors before or after this block of errors. Just call data like normal.
I have seen this many times. In almost every single case it’s been a NAT issue. If this is a new deploy, are you restoring from a backup system? I ran into this where it pulls the default IP and has to be updated. If not, check ISP and router.
Normally I would agree! But how does that explain the issue happening with the trunks? Sometimes, not everytime, one of the two trunks drops within a batch of the phones dropping at the same time. The only firewalls playing in part with the trunks would be the built in one with FPBX and the carrier. Reviewing the logs overnight, it happened in batches several times again:
324890[2022-07-19 01:10:40] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint 318 is now Unreachable
324891[2022-07-19 01:10:40] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact 318/sip:[email protected]:52223;transport=TLS;x-ast-orig-host=192.168.2.136:52223 is now Unreachable. RTT: 0.000 msec
324892[2022-07-19 01:10:40] VERBOSE[135102] res_pjsip/pjsip_configuration.c: Endpoint 350 is now Unreachable
324893[2022-07-19 01:10:40] VERBOSE[135102] res_pjsip/pjsip_options.c: Contact 350/sip:[email protected]:43723;transport=TLS;x-ast-orig-host=192.168.2.77:43723 is now Unreachable. RTT: 0.000 msec
324894[2022-07-19 01:10:40] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 329 is now Unreachable
324895[2022-07-19 01:10:40] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 329/sip:[email protected]:45114;transport=TLS;x-ast-orig-host=192.168.2.100:45114 is now Unreachable. RTT: 0.000 msec
324896[2022-07-19 01:10:40] VERBOSE[135102] res_pjsip/pjsip_configuration.c: Endpoint 344 is now Unreachable
324897[2022-07-19 01:10:40] VERBOSE[135102] res_pjsip/pjsip_options.c: Contact 344/sip:[email protected]:51583;transport=TLS;x-ast-orig-host=192.168.2.157:51583 is now Unreachable. RTT: 0.000 msec
324898[2022-07-19 01:10:40] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 340 is now Unreachable
324899[2022-07-19 01:10:40] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 340/sip:[email protected]:55742;transport=TLS;x-ast-orig-host=192.168.2.76:55742 is now Unreachable. RTT: 0.000 msec
324900[2022-07-19 01:10:40] VERBOSE[131705] res_pjsip/pjsip_configuration.c: Endpoint 317 is now Unreachable
324901[2022-07-19 01:10:40] VERBOSE[131705] res_pjsip/pjsip_options.c: Contact 317/sip:[email protected]:51824;transport=TLS;x-ast-orig-host=192.168.2.80:51824 is now Unreachable. RTT: 0.000 msec
324902[2022-07-19 01:10:40] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 308 is now Unreachable
324903[2022-07-19 01:10:40] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 308/sip:[email protected]:53667;transport=TLS;x-ast-orig-host=192.168.2.74:53667 is now Unreachable. RTT: 0.000 msec
324904[2022-07-19 01:10:41] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 342 is now Unreachable
324905[2022-07-19 01:10:41] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 342/sip:[email protected]:54312;transport=TLS;x-ast-orig-host=192.168.2.128:54312 is now Unreachable. RTT: 0.000 msec
324906[2022-07-19 01:10:41] VERBOSE[131705] res_pjsip/pjsip_configuration.c: Endpoint 338 is now Unreachable
324907[2022-07-19 01:10:41] VERBOSE[131705] res_pjsip/pjsip_options.c: Contact 338/sip:[email protected]:52158;transport=TLS;x-ast-orig-host=192.168.2.67:52158 is now Unreachable. RTT: 0.000 msec
324908[2022-07-19 01:10:41] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint 315 is now Unreachable
324909[2022-07-19 01:10:41] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact 315/sip:[email protected]:12248;transport=TLS is now Unreachable. RTT: 0.000 msec
324910[2022-07-19 01:10:42] VERBOSE[131705] res_pjsip/pjsip_configuration.c: Endpoint 406 is now Unreachable
324911[2022-07-19 01:10:42] VERBOSE[131705] res_pjsip/pjsip_options.c: Contact 406/sip:[email protected]:12565;transport=TLS;x-ast-orig-host=192.168.0.44:12565 is now Unreachable. RTT: 0.000 msec
324912[2022-07-19 01:10:42] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint 346 is now Unreachable
324913[2022-07-19 01:10:42] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact 346/sip:[email protected]:12719;transport=TLS;x-ast-orig-host=192.168.2.160:12719 is now Unreachable. RTT: 0.000 msec
324914[2022-07-19 01:10:42] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 204 is now Unreachable
324915[2022-07-19 01:10:42] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 204/sip:[email protected]:49229;transport=TLS;x-ast-orig-host=10.0.1.102:49229 is now Unreachable. RTT: 0.000 msec
324916[2022-07-19 01:10:43] VERBOSE[131705] res_pjsip/pjsip_configuration.c: Endpoint 205 is now Unreachable
324917[2022-07-19 01:10:43] VERBOSE[131705] res_pjsip/pjsip_options.c: Contact 205/sip:[email protected]:35565;transport=TLS;x-ast-orig-host=10.0.1.110:35565 is now Unreachable. RTT: 0.000 msec
324918[2022-07-19 01:10:43] VERBOSE[135102] res_pjsip/pjsip_configuration.c: Endpoint 316 is now Unreachable
324919[2022-07-19 01:10:43] VERBOSE[135102] res_pjsip/pjsip_options.c: Contact 316/sip:[email protected]:53888;transport=TLS;x-ast-orig-host=192.168.2.104:53888 is now Unreachable. RTT: 0.000 msec
324920[2022-07-19 01:10:44] VERBOSE[135102] res_pjsip/pjsip_configuration.c: Endpoint 306 is now Unreachable
324921[2022-07-19 01:10:44] VERBOSE[135102] res_pjsip/pjsip_options.c: Contact 306/sip:[email protected]:43674;transport=TLS;x-ast-orig-host=192.168.2.61:43674 is now Unreachable. RTT: 0.000 msec
324922[2022-07-19 01:10:44] VERBOSE[135102] res_pjsip/pjsip_configuration.c: Endpoint 309 is now Unreachable
324923[2022-07-19 01:10:44] VERBOSE[135102] res_pjsip/pjsip_options.c: Contact 309/sip:[email protected]:62034;transport=TLS;x-ast-orig-host=192.168.2.142:62034 is now Unreachable. RTT: 0.000 msec
324924[2022-07-19 01:10:45] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 320 is now Unreachable
324925[2022-07-19 01:10:45] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 320/sip:[email protected]:61627;transport=TLS;x-ast-orig-host=192.168.2.73:61627 is now Unreachable. RTT: 0.000 msec
324926[2022-07-19 01:10:45] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint 343 is now Unreachable
324927[2022-07-19 01:10:45] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact 343/sip:[email protected]:32828;transport=TLS;x-ast-orig-host=192.168.2.87:32828 is now Unreachable. RTT: 0.000 msec
324928[2022-07-19 01:10:45] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint 302 is now Unreachable
324929[2022-07-19 01:10:45] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact 302/sip:[email protected]:59999;transport=TLS;x-ast-orig-host=192.168.2.78:59999 is now Unreachable. RTT: 0.000 msec
324930[2022-07-19 01:10:45] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 332 is now Unreachable
324931[2022-07-19 01:10:45] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 332/sip:[email protected]:59161;transport=TLS;x-ast-orig-host=192.168.1.46:59161 is now Unreachable. RTT: 0.000 msec
324932[2022-07-19 01:10:46] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 202 is now Unreachable
324933[2022-07-19 01:10:46] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 202/sip:[email protected]:53408;transport=TLS;x-ast-orig-host=10.0.1.109:53408 is now Unreachable. RTT: 0.000 msec
324934[2022-07-19 01:10:47] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 404 is now Unreachable
324935[2022-07-19 01:10:47] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 404/sip:[email protected]:58404;transport=TLS;x-ast-orig-host=192.168.0.46:58404 is now Unreachable. RTT: 0.000 msec
324936[2022-07-19 01:10:47] VERBOSE[131705] res_pjsip/pjsip_configuration.c: Endpoint 305 is now Unreachable
324937[2022-07-19 01:10:47] VERBOSE[131705] res_pjsip/pjsip_options.c: Contact 305/sip:[email protected]:47409;transport=TLS;x-ast-orig-host=192.168.2.112:47409 is now Unreachable. RTT: 0.000 msec
324938[2022-07-19 01:10:47] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 347 is now Unreachable
324939[2022-07-19 01:10:47] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 347/sip:[email protected]:12410;transport=TLS;x-ast-orig-host=192.168.2.58:12410 is now Unreachable. RTT: 0.000 msec
324940[2022-07-19 01:10:47] VERBOSE[131705] res_pjsip/pjsip_configuration.c: Endpoint 339 is now Unreachable
324941[2022-07-19 01:10:47] VERBOSE[131705] res_pjsip/pjsip_options.c: Contact 339/sip:[email protected]:11999;transport=TLS is now Unreachable. RTT: 0.000 msec
324942[2022-07-19 01:10:47] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint 324 is now Unreachable
324943[2022-07-19 01:10:47] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact 324/sip:[email protected]:32963;transport=TLS;x-ast-orig-host=192.168.2.83:32963 is now Unreachable. RTT: 0.000 msec
324944[2022-07-19 01:10:47] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 203 is now Unreachable
324945[2022-07-19 01:10:47] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 203/sip:[email protected]:63616;transport=TLS;x-ast-orig-host=10.0.1.103:63616 is now Unreachable. RTT: 0.000 msec
324946[2022-07-19 01:10:47] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint Twilio-US1-Virginia is now Unreachable
324947[2022-07-19 01:10:47] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact Twilio-US1-Virginia/sip:[email protected]:5061 is now Unreachable. RTT: 0.000 msec
324948[2022-07-19 01:10:47] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 401 is now Unreachable
324949[2022-07-19 01:10:47] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 401/sip:[email protected]:47932;transport=TLS;x-ast-orig-host=192.168.0.108:47932 is now Unreachable. RTT: 0.000 msec
324950[2022-07-19 01:10:48] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint 327 is now Unreachable
324951[2022-07-19 01:10:48] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact 327/sip:[email protected]:12646;transport=TLS;x-ast-orig-host=192.168.2.93:12646 is now Unreachable. RTT: 0.000 msec
324952[2022-07-19 01:10:48] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 304 is now Unreachable
324953[2022-07-19 01:10:48] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 304/sip:[email protected]:35557;transport=TLS;x-ast-orig-host=192.168.2.102:35557 is now Unreachable. RTT: 0.000 msec
324954[2022-07-19 01:10:48] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint 319 is now Unreachable
324955[2022-07-19 01:10:48] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact 319/sip:[email protected]:35337;transport=TLS;x-ast-orig-host=192.168.2.68:35337 is now Unreachable. RTT: 0.000 msec
324956[2022-07-19 01:10:48] VERBOSE[131705] res_pjsip/pjsip_configuration.c: Endpoint 200 is now Unreachable
324957[2022-07-19 01:10:48] VERBOSE[131705] res_pjsip/pjsip_options.c: Contact 200/sip:[email protected]:42433;transport=TLS;x-ast-orig-host=10.0.1.104:42433 is now Unreachable. RTT: 0.000 msec
324958[2022-07-19 01:10:49] VERBOSE[135102] res_pjsip/pjsip_configuration.c: Endpoint 300 is now Unreachable
324959[2022-07-19 01:10:49] VERBOSE[135102] res_pjsip/pjsip_options.c: Contact 300/sip:[email protected]:62109;transport=TLS;x-ast-orig-host=192.168.2.101:62109 is now Unreachable. RTT: 0.000 msec
324960[2022-07-19 01:10:49] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 312 is now Unreachable
324961[2022-07-19 01:10:49] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 312/sip:[email protected]:49399;transport=TLS;x-ast-orig-host=192.168.2.54:49399 is now Unreachable. RTT: 0.000 msec
324962[2022-07-19 01:10:49] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint 348 is now Unreachable
324963[2022-07-19 01:10:49] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact 348/sip:[email protected]:12410;transport=TLS;x-ast-orig-host=192.168.2.58:12410 is now Unreachable. RTT: 0.000 msec
324964[2022-07-19 01:10:50] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 310 is now Reachable
324965[2022-07-19 01:10:50] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 310/sip:[email protected]:61872;transport=TLS;x-ast-orig-host=192.168.2.132:61872 is now Reachable. RTT: 6.060 msec
324966[2022-07-19 01:10:50] VERBOSE[131705] res_pjsip/pjsip_configuration.c: Endpoint 201 is now Unreachable
324967[2022-07-19 01:10:50] VERBOSE[131705] res_pjsip/pjsip_options.c: Contact 201/sip:[email protected]:47412;transport=TLS;x-ast-orig-host=10.0.1.105:47412 is now Unreachable. RTT: 0.000 msec
324968[2022-07-19 01:10:50] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 345 is now Reachable
324969[2022-07-19 01:10:50] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 345/sip:[email protected]:39910;transport=TLS;x-ast-orig-host=192.168.2.196:39910 is now Reachable. RTT: 10.914 msec
324970[2022-07-19 01:10:50] VERBOSE[135102] res_pjsip/pjsip_configuration.c: Endpoint 403 is now Reachable
324971[2022-07-19 01:10:50] VERBOSE[135102] res_pjsip/pjsip_options.c: Contact 403/sip:[email protected]:44968;transport=TLS;x-ast-orig-host=192.168.0.45:44968 is now Reachable. RTT: 21.555 msec
324972[2022-07-19 01:10:50] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint 402 is now Reachable
324973[2022-07-19 01:10:50] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact 402/sip:[email protected]:54852;transport=TLS;x-ast-orig-host=192.168.0.47:54852 is now Reachable. RTT: 18.178 msec
324974[2022-07-19 01:10:51] VERBOSE[135102] res_pjsip/pjsip_configuration.c: Endpoint 330 is now Reachable
324975[2022-07-19 01:10:51] VERBOSE[135102] res_pjsip/pjsip_options.c: Contact 330/sip:[email protected]:12322;transport=TLS;x-ast-orig-host=192.168.2.121:12322 is now Reachable. RTT: 14.619 msec
324976[2022-07-19 01:10:51] VERBOSE[135102] res_pjsip/pjsip_configuration.c: Endpoint 307 is now Reachable
324977[2022-07-19 01:10:51] VERBOSE[135102] res_pjsip/pjsip_options.c: Contact 307/sip:[email protected]:42490;transport=TLS;x-ast-orig-host=192.168.2.167:42490 is now Reachable. RTT: 7.003 msec
324978[2022-07-19 01:10:51] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint 331 is now Reachable
324979[2022-07-19 01:10:51] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact 331/sip:[email protected]:12367;transport=TLS;x-ast-orig-host=192.168.2.198:12367 is now Reachable. RTT: 16.545 msec
324980[2022-07-19 01:10:51] VERBOSE[135102] res_pjsip/pjsip_configuration.c: Endpoint 313 is now Reachable
324981[2022-07-19 01:10:51] VERBOSE[135102] res_pjsip/pjsip_options.c: Contact 313/sip:[email protected]:52276;transport=TLS;x-ast-orig-host=192.168.2.111:52276 is now Reachable. RTT: 7.969 msec
324982[2022-07-19 01:10:51] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint 335 is now Reachable
324983[2022-07-19 01:10:51] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact 335/sip:[email protected]:63338;transport=TLS;x-ast-orig-host=192.168.2.109:63338 is now Reachable. RTT: 7.646 msec
324984[2022-07-19 01:10:52] VERBOSE[135102] res_pjsip/pjsip_configuration.c: Endpoint 318 is now Reachable
324985[2022-07-19 01:10:52] VERBOSE[135102] res_pjsip/pjsip_options.c: Contact 318/sip:[email protected]:52223;transport=TLS;x-ast-orig-host=192.168.2.136:52223 is now Reachable. RTT: 7.522 msec
324986[2022-07-19 01:10:52] VERBOSE[135102] res_pjsip/pjsip_configuration.c: Endpoint 350 is now Reachable
324987[2022-07-19 01:10:52] VERBOSE[135102] res_pjsip/pjsip_options.c: Contact 350/sip:[email protected]:43723;transport=TLS;x-ast-orig-host=192.168.2.77:43723 is now Reachable. RTT: 6.594 msec
324988[2022-07-19 01:10:52] VERBOSE[135102] res_pjsip/pjsip_configuration.c: Endpoint 329 is now Reachable
324989[2022-07-19 01:10:52] VERBOSE[135102] res_pjsip/pjsip_options.c: Contact 329/sip:[email protected]:45114;transport=TLS;x-ast-orig-host=192.168.2.100:45114 is now Reachable. RTT: 6.429 msec
324990[2022-07-19 01:10:52] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 344 is now Reachable
324991[2022-07-19 01:10:52] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 344/sip:[email protected]:51583;transport=TLS;x-ast-orig-host=192.168.2.157:51583 is now Reachable. RTT: 5.906 msec
324992[2022-07-19 01:10:52] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint 340 is now Reachable
324993[2022-07-19 01:10:52] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact 340/sip:[email protected]:55742;transport=TLS;x-ast-orig-host=192.168.2.76:55742 is now Reachable. RTT: 7.569 msec
324994[2022-07-19 01:10:52] VERBOSE[131705] res_pjsip/pjsip_configuration.c: Endpoint 317 is now Reachable
324995[2022-07-19 01:10:52] VERBOSE[131705] res_pjsip/pjsip_options.c: Contact 317/sip:[email protected]:51824;transport=TLS;x-ast-orig-host=192.168.2.80:51824 is now Reachable. RTT: 6.842 msec
324996[2022-07-19 01:10:52] VERBOSE[135102] res_pjsip/pjsip_configuration.c: Endpoint 308 is now Reachable
324997[2022-07-19 01:10:52] VERBOSE[135102] res_pjsip/pjsip_options.c: Contact 308/sip:[email protected]:53667;transport=TLS;x-ast-orig-host=192.168.2.74:53667 is now Reachable. RTT: 8.004 msec
324998[2022-07-19 01:10:53] VERBOSE[131705] res_pjsip/pjsip_configuration.c: Endpoint 342 is now Reachable
324999[2022-07-19 01:10:53] VERBOSE[131705] res_pjsip/pjsip_options.c: Contact 342/sip:[email protected]:54312;transport=TLS;x-ast-orig-host=192.168.2.128:54312 is now Reachable. RTT: 6.757 msec
325000[2022-07-19 01:10:53] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint 338 is now Reachable
325001[2022-07-19 01:10:53] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact 338/sip:[email protected]:52158;transport=TLS;x-ast-orig-host=192.168.2.67:52158 is now Reachable. RTT: 7.020 msec
325002[2022-07-19 01:10:53] VERBOSE[131705] res_pjsip/pjsip_configuration.c: Endpoint 315 is now Reachable
325003[2022-07-19 01:10:53] VERBOSE[131705] res_pjsip/pjsip_options.c: Contact 315/sip:[email protected]:12248;transport=TLS is now Reachable. RTT: 23.174 msec
325004[2022-07-19 01:10:54] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint 406 is now Reachable
325005[2022-07-19 01:10:54] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact 406/sip:[email protected]:12565;transport=TLS;x-ast-orig-host=192.168.0.44:12565 is now Reachable. RTT: 30.780 msec
325006[2022-07-19 01:10:54] VERBOSE[135102] res_pjsip/pjsip_configuration.c: Endpoint 346 is now Reachable
325007[2022-07-19 01:10:54] VERBOSE[135102] res_pjsip/pjsip_options.c: Contact 346/sip:[email protected]:12719;transport=TLS;x-ast-orig-host=192.168.2.160:12719 is now Reachable. RTT: 16.948 msec
325008[2022-07-19 01:10:54] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint 204 is now Reachable
325009[2022-07-19 01:10:54] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact 204/sip:[email protected]:49229;transport=TLS;x-ast-orig-host=10.0.1.102:49229 is now Reachable. RTT: 15.373 msec
325010[2022-07-19 01:10:55] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint 205 is now Reachable
325011[2022-07-19 01:10:55] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact 205/sip:[email protected]:35565;transport=TLS;x-ast-orig-host=10.0.1.110:35565 is now Reachable. RTT: 15.600 msec
325012[2022-07-19 01:10:55] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint 316 is now Reachable
325013[2022-07-19 01:10:55] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact 316/sip:[email protected]:53888;transport=TLS;x-ast-orig-host=192.168.2.104:53888 is now Reachable. RTT: 6.082 msec
325014[2022-07-19 01:10:56] VERBOSE[131705] res_pjsip/pjsip_configuration.c: Endpoint 306 is now Reachable
325015[2022-07-19 01:10:56] VERBOSE[131705] res_pjsip/pjsip_options.c: Contact 306/sip:[email protected]:43674;transport=TLS;x-ast-orig-host=192.168.2.61:43674 is now Reachable. RTT: 7.838 msec
325016[2022-07-19 01:10:56] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint 309 is now Reachable
325017[2022-07-19 01:10:56] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact 309/sip:[email protected]:62034;transport=TLS;x-ast-orig-host=192.168.2.142:62034 is now Reachable. RTT: 6.696 msec
325018[2022-07-19 01:10:57] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 320 is now Reachable
325019[2022-07-19 01:10:57] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 320/sip:[email protected]:61627;transport=TLS;x-ast-orig-host=192.168.2.73:61627 is now Reachable. RTT: 7.574 msec
325020[2022-07-19 01:10:57] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint 343 is now Reachable
325021[2022-07-19 01:10:57] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact 343/sip:[email protected]:32828;transport=TLS;x-ast-orig-host=192.168.2.87:32828 is now Reachable. RTT: 6.143 msec
325022[2022-07-19 01:10:57] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 302 is now Reachable
325023[2022-07-19 01:10:57] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 302/sip:[email protected]:59999;transport=TLS;x-ast-orig-host=192.168.2.78:59999 is now Reachable. RTT: 10.974 msec
325024[2022-07-19 01:10:57] VERBOSE[131705] res_pjsip/pjsip_configuration.c: Endpoint 332 is now Reachable
325025[2022-07-19 01:10:57] VERBOSE[131705] res_pjsip/pjsip_options.c: Contact 332/sip:[email protected]:59161;transport=TLS;x-ast-orig-host=192.168.1.46:59161 is now Reachable. RTT: 6.902 msec
325026[2022-07-19 01:10:58] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 202 is now Reachable
325027[2022-07-19 01:10:58] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 202/sip:[email protected]:53408;transport=TLS;x-ast-orig-host=10.0.1.109:53408 is now Reachable. RTT: 17.909 msec
325028[2022-07-19 01:10:59] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 305 is now Reachable
325029[2022-07-19 01:10:59] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 305/sip:[email protected]:47409;transport=TLS;x-ast-orig-host=192.168.2.112:47409 is now Reachable. RTT: 6.345 msec
325030[2022-07-19 01:10:59] VERBOSE[131705] res_pjsip/pjsip_configuration.c: Endpoint 404 is now Reachable
325031[2022-07-19 01:10:59] VERBOSE[131705] res_pjsip/pjsip_options.c: Contact 404/sip:[email protected]:58404;transport=TLS;x-ast-orig-host=192.168.0.46:58404 is now Reachable. RTT: 16.273 msec
325032[2022-07-19 01:10:59] VERBOSE[135102] res_pjsip/pjsip_configuration.c: Endpoint 347 is now Reachable
325033[2022-07-19 01:10:59] VERBOSE[135102] res_pjsip/pjsip_options.c: Contact 347/sip:[email protected]:12410;transport=TLS;x-ast-orig-host=192.168.2.58:12410 is now Reachable. RTT: 8.251 msec
325034[2022-07-19 01:10:59] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 339 is now Reachable
325035[2022-07-19 01:10:59] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 339/sip:[email protected]:11999;transport=TLS is now Reachable. RTT: 61.306 msec
325036[2022-07-19 01:10:59] VERBOSE[135102] res_pjsip/pjsip_configuration.c: Endpoint 324 is now Reachable
325037[2022-07-19 01:10:59] VERBOSE[135102] res_pjsip/pjsip_options.c: Contact 324/sip:[email protected]:32963;transport=TLS;x-ast-orig-host=192.168.2.83:32963 is now Reachable. RTT: 5.857 msec
325038[2022-07-19 01:10:59] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 203 is now Reachable
325039[2022-07-19 01:10:59] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 203/sip:[email protected]:63616;transport=TLS;x-ast-orig-host=10.0.1.103:63616 is now Reachable. RTT: 19.017 msec
325040[2022-07-19 01:11:00] VERBOSE[131705] res_pjsip/pjsip_configuration.c: Endpoint 401 is now Reachable
325041[2022-07-19 01:11:00] VERBOSE[131705] res_pjsip/pjsip_options.c: Contact 401/sip:[email protected]:47932;transport=TLS;x-ast-orig-host=192.168.0.108:47932 is now Reachable. RTT: 16.955 msec
325042[2022-07-19 01:11:00] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint 327 is now Reachable
325043[2022-07-19 01:11:00] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact 327/sip:[email protected]:12646;transport=TLS;x-ast-orig-host=192.168.2.93:12646 is now Reachable. RTT: 15.721 msec
325044[2022-07-19 01:11:00] VERBOSE[135102] res_pjsip/pjsip_configuration.c: Endpoint 304 is now Reachable
325045[2022-07-19 01:11:00] VERBOSE[135102] res_pjsip/pjsip_options.c: Contact 304/sip:[email protected]:35557;transport=TLS;x-ast-orig-host=192.168.2.102:35557 is now Reachable. RTT: 6.855 msec
325046[2022-07-19 01:11:00] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint 319 is now Reachable
325047[2022-07-19 01:11:00] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact 319/sip:[email protected]:35337;transport=TLS;x-ast-orig-host=192.168.2.68:35337 is now Reachable. RTT: 7.802 msec
325048[2022-07-19 01:11:00] VERBOSE[135102] res_pjsip/pjsip_configuration.c: Endpoint 200 is now Reachable
325049[2022-07-19 01:11:00] VERBOSE[135102] res_pjsip/pjsip_options.c: Contact 200/sip:[email protected]:42433;transport=TLS;x-ast-orig-host=10.0.1.104:42433 is now Reachable. RTT: 19.162 msec
325050[2022-07-19 01:11:01] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 300 is now Reachable
325051[2022-07-19 01:11:01] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 300/sip:[email protected]:62109;transport=TLS;x-ast-orig-host=192.168.2.101:62109 is now Reachable. RTT: 8.274 msec
325052[2022-07-19 01:11:01] VERBOSE[131705] res_pjsip/pjsip_configuration.c: Endpoint 312 is now Reachable
325053[2022-07-19 01:11:01] VERBOSE[131705] res_pjsip/pjsip_options.c: Contact 312/sip:[email protected]:49399;transport=TLS;x-ast-orig-host=192.168.2.54:49399 is now Reachable. RTT: 8.514 msec
325054[2022-07-19 01:11:01] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint 348 is now Reachable
325055[2022-07-19 01:11:01] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact 348/sip:[email protected]:12410;transport=TLS;x-ast-orig-host=192.168.2.58:12410 is now Reachable. RTT: 8.946 msec
325056[2022-07-19 01:11:02] VERBOSE[224449] res_pjsip/pjsip_configuration.c: Endpoint 201 is now Reachable
325057[2022-07-19 01:11:02] VERBOSE[224449] res_pjsip/pjsip_options.c: Contact 201/sip:[email protected]:47412;transport=TLS;x-ast-orig-host=10.0.1.105:47412 is now Reachable. RTT: 17.771 msec
325058[2022-07-19 01:11:04] VERBOSE[135102] res_pjsip/pjsip_configuration.c: Endpoint 333 is now Reachable
325059[2022-07-19 01:11:04] VERBOSE[135102] res_pjsip/pjsip_options.c: Contact 333/sip:[email protected]:12199;transport=TLS;x-ast-orig-host=192.168.2.56:12199 is now Reachable. RTT: 20.026 msec
325060[2022-07-19 01:11:04] VERBOSE[131705] res_pjsip/pjsip_configuration.c: Endpoint 337 is now Reachable
325061[2022-07-19 01:11:04] VERBOSE[131705] res_pjsip/pjsip_options.c: Contact 337/sip:[email protected]:52471;transport=TLS;x-ast-orig-host=192.168.2.115:52471 is now Reachable. RTT: 6.772 msec
325062[2022-07-19 01:11:45] VERBOSE[110905] res_pjsip/pjsip_configuration.c: Endpoint Twilio-US1-Virginia is now Reachable
325063[2022-07-19 01:11:45] VERBOSE[110905] res_pjsip/pjsip_options.c: Contact Twilio-US1-Virginia/sip:[email protected]:5061 is now Reachable. RTT: 65.272 msec
Just this block, the issue occurred across all locations, even a couple of remote users are in there. They have Yealinks setup using the built in VPN.
This customer has been setup since the beginning of the year, and everything seemed fine up until the last month or so when they started reporting the dropped calls. But it was so inconsistent, it was hard to troubleshoot. Over this last weekend, I did do a complete wipe and reinstall of their PBX, upgrading their Asterisk version in the process. I did do a restore from a backup, which seemed to restore 99% of everything. There were a couple of things I noticed that were missing, settings not set, so I manually changed them, but the settings in EPM seemed to carry over just fine. Once it was restored, and I rebooted the server for the final time, all of their phones registered back up without issue.
are you hosting the PBX or is it a cloud provider? If it’s cloud, Contact re-write should be set to “yes” and asterisk should show the public IP and not private
There are so many possibilities, firewall, internet connection, misconfiguration, its a tough one.
I think @kierknoby makes a good point, I would try that and see if you’re getting the same result.
I have seen peering issues at times, even when the datacenter the pbx is in, is in the same state, and literally had to move a pbx to another state then it was flawless.
Also, if you don’t manage the firewall directly, you may want to get more info from the IT guys.
I agree, the possibilities are many. The servers I host all of my customers phone servers from, I manage. It is stored in a datacenter with a direct 500Mbps fiber connection. Each of them are VM’s in Hyper-V and each one of them has their own, dedicated IP, directly on the edge. So no firewall of special routing in front of the servers. Since I am not seeing this same behavior with the dozens of other customers servers’, I figured it’s either a weird configuration issue, which I’m not sure what it would be at this point, or maybe something weird with the routing on the ISP side. Earlier, I tried swapping their public IP to a different one in our block, but the same issue happens.
Now I would normally chalk this up to a NAT issue, but the fact that sometimes, not every time, but sometimes, one or both of the trunks drop along with the random endpoints, points me to an issue on the PBX. I have disabled the responsive firewall, lowered keep-alive (even though the defaults usually work just fine, and the session timeouts on the firewalls at each location are set to 60 seconds). The only other thing I can think to try is setting a VPS with a third party and migrating their setup to that. If the problem follows, it has to be something configuration-wise on the server at that point. I just have no more ideas beyond what I tried already.
OK I enabled logging and watched for the occurrence of a block of phones dropping. Didn’t take too long to get that result. I tracked one extension out of the dozens that dropped at the same time and filtered out everything related to that extension between the unregister and register. I have put that in a pastebin here.
What’s immediately concerning is that I switched the server’s public IP to a different one in our block, and there are still references in a couple of those messages to the old IP! Mind you, I completely rebooted the server after the change. But from what I understand from this, the register message is sent and received, then just 11 seconds after that, drops.
This looks like TCP packet loss/retransmission. Asterisk sent an OPTIONS out, it didn’t get a response after 3 seconds so it was marked unreachable and then it sent another OPTIONS. Finally things sorted themselves out, and a 200 OK to the original OPTIONS was received followed by a 200 OK to the second OPTIONS which made it reachable again.
That’s what it seems like for sure. Is there a timeout that needs adjusted maybe? Do resources need adjusted, I figured the hardware available to the FPBX was more than plenty, but I can assign more if that will help. Since this seems to happen for dozens of extensions at once, is it flooding the asterisk server?
My references were more about the client side firewall.
Also, changing your IP from the same provider, probably doesn’t help much since its still the same provider.
I do believe its something on the client side firewall or peer routing creating the delay.
There’s nothing within Asterisk itself for this, I guess besides increasing the qualify_timeout but I don’t know if that would be sufficient enough. Otherwise it’s looking outside of Asterisk, at packet captures, to understand precisely from a packet and TCP layer what exactly is going on.
I was experiencing the same problem for phones connecting remotely to the PBX
The client side routers/firewalls should be in full-cone NAT mode (some routers default to symmetric NAT which causes issues sometimes as the ports aren’t kept open).
I had a pjsip trunk that was constantly becoming unreachable/reachable and the only fix that worked was setting the qualify frequency for the trunk to 0 to disable qualify and that fixed the trunk issues 100%.
However disabling qualify for remote extensions did not fix the issue with the phones becoming reachable/unreachable like you are experiencing as well. I am eager to monitor this thread to see if there is another solution
trunks that use IP authentication, do not need to ‘qualify’ but if using registration, the FireWall will need to be bidirectionally one-to-one for the SIP communication to get to the PBX, further the same will need to be true for any negotiated media (SDP) stream, and that applies to both IP and registration connections
External extensions are almost always ‘dynamic’ so need different treatment and successfully ‘qualify’ing’ them is a good thing to achieve if you want the phone to actually ring.