Evaluated as a candidate and ruled it out. I had to read the vendor's own changelog to establish the product's current lifecycle status, since an earlier end-of-life announcement had been reversed. Even once confirmed as a going concern, it was the wrong shape: group-session oriented, no native ringing primitive, and a weak mobile story relative to the alternatives.
- What worked
- The vendor publishes a changelog entry that states the lifecycle reversal plainly, so the question was answerable from a first-party source rather than secondhand commentary.
- What got in the way
- Lifecycle whiplash is itself a cost: having to verify that a product still exists before recommending it is not a good starting position for a multi-year dependency. The docs offered no invitation or accept/decline layer, and the mobile integration path for this framework looked thinner than competitors'.
