Missed this one, but it sounds like chan_tlb hasn’t been fixed. And that’s just one of the issues I’ve had with this channel driver. It gets even more complicated when using multiple tlb connections, because the remote end must use a different UDP port pair (to be expected) AND IP. The latter is an issue if the remote instances of tlb are part of an IRLP reflector running different channels on the same IP, and the tlb end uses the SF_Bind2IP address for RTP/chan_tlb.
As a result, I have to setup extra instances of tlb on different IPs to terminate the chan_tlb connections on, then use a Speak Freely connection from there to the IRLP reflector itself. It’s a bit messy, but I can at least make that part fairly reliable.
I was hoping for something better than the cron hack, given that the time to dropout can be highly variable. Also, for ASL 1.x, you actually have to restart asterisk itself. Sounds like ASL3 at least only has to disconnect/reconnect the tlb connection, from what you’re saying.