We've got Conductor + Several TP servers. While Conductor works great for Ad-Hoc or dial-in conferences, "Automatic Connect" and dial-outs from conductor, and general TMS based conferences seem to be lacking. For this reason we are still using TP Server in locally managed mode, even though it means missing some of the newer features (IX/ multistream etc).
Specifically, a few of the issues we have:
When Conductor dials out (e.g. from a scheuled "Automatic Connect" conference), the callback alias is just the Conductor's IP address, rather than a valid URI. This is a deal-breaker as users often miss the first call and use the missed call to enter the meeting (we don't use auto-answer sue to security).
When scheduling meetings from TMS, the email template doesn't support the "Numeric ID" variable, it only supports the "SIP URI" variable. This limits our ability to edit and use the dial-in number as we need to - there's all sorts of scenarios where we want to present just the number as opposed to a SIP URI/link in an email.
Are there any plans to address these issues? We'd really like to migrate to Conductor but right now we can't afford to lose these features.
