Firstly, thank you for all the support on this forum - we are finding it extremely useful.
Secondly, we are looking in to migrating from Asterisk 1.6 to 1.8 (prompted by 1.6 end of life). I am curious to know to what extent Thirdlane supports 1.8? Further to this, is there a clear and well documented migration path (we have seen a few posts on the forum about this so far - thank you)? Will there be any functionality loss (we have read about parking)? Are there known workarounds we should be cognizant of?
Finally, aside from the end of life issue re 1.6, we had a major error happen on our system last week. When provisioning a customer, Asterisk froze. The Asterisk reload stopped halfway through. Thirdlane saw this and prompted us with the "reload PBX" note on the bottom of the GUI. After some searching, we found only one other individual had somewhat of related issue. Their only suggested fix was to go with 1.8 and did not mention anything deeper. Have you ever come across an Asterisk reload bug in 1.6?
Thanks very much, and your response is appreciated.
Ryley
theres a workaround to parking, its somewhat complex and involves compiling in a patch to the asterisk source tree.
the 'deadlock' issue affects a great deal of 1.6.2 and 1.8 branches. 1.8.5 will be the first potential version to address the issue (hopefully). They have removed a lot of deadlock avoidance code, aparently it was becoming its own enemy.
biggest impact going to 1.8 would be res_fax modules, the libresample code, potential issue with the SIP UPDATE message with older versions of siproxd or programs build around older libosip. You may have to republish some routes, huntlists, ivrs etc if there are syntax complains after a 'reload'.