I’m going to be very honest with you all. When you go and open a ticket up about PJSIP issues on the FreePBX issue tracker that are about issues which have no logs, no debug of any sort (the auto responder basically begs you to add logs and debugging) AND the issue is about something that FreePBX has almost no control over it’s very hard for the development team to replicate. Of note we use PJSIP internally and also externally and we haven’t seen any of the issue you mentioned in your ticket which only further adds to use not being able to replicate.
I see that maybe there is a lot of finger pointing between Digium and Sangoma here but when a reload happens write merely write out configuration files and then tell Asterisk to reload. There is no other fancy logic we would be able to control here with phones not being able to register.
Your best bet would be going to either our Commercial Support or Digium’s commercial support. Either would work for you.
You see the only practical thing we could do from that ticket is working on your system directly. Because again it’s not reproducible. We are not allowed to do this on open source tickets. This is because if we go in and muck around with your system and break something Sangoma is now liable for damages. When you go through our commercial ticket system you agree to terms of service.
What I don’t like doing is assigning a ticket like this out to anyone, as it consumes resources (I already reloaded the system a few times and my phones stay registered each time). It consumes resources because it doesn’t do anything but sit in our tracker and collect dust.
Therefore I closed this ticket. Really there is nothing more we can do. As the ticketing system states, “tickets are for reproducible issues”. We try to reproduce every ticket we run across. If we can’t reproduce it we have to close the ticket. Especially if it’s something that has a ton of variables. The ticket itself was named “PJSIP - all extensions “Unavailable” after some “Apply Config” reloads”