In a past blog post I talked about how you can’t reload transports without enabling explicit support, but alluded to changes coming in the future. I’m happy to say that changes are now afoot and you can experience them in future Asterisk releases (16.18.0 and 18.4.0)!
A change has now been merged which allows partial transport reload support. You might ask, what does this mean?
This change allows the reloading of Asterisk specific information about a transport: specifically local_net, external_signaling_address, and external_media_address. This can be useful if your system has a dynamic IP address and you want to change it without restarting Asterisk or if you’ve added another local network.
Stay tuned for even more potential transport reload changes in the future!