Furthermore, having previously read extensively into this, from what I understand the two main problems with Webex are intermittent latency issues, and that it only allows a limited number of seats at the table for a call.
Harvest solves both those problems, especially seats at the table allowing virtually unlimited remote participants anywhere in the world without loss of latency on voice, video or data.
Is it stating the obvious to say this is the reason why Cisco Webex are collaborating with Harvest to solve these problems? And if they can, and indeed have solved these problems then the extent of any commercial agreement may well be much bigger and further reaching in scope than first envisaged. Starting with a scaleable, dedicated API for end-user on-demand use.
As per the planned proof-of-concept development roadmap, phase 2 of the Webex integration continued through the December quarter to create a scalable dedicated API for end user on-demand use.
Connections are now possible between the Nodestream and Webex ecosystems, and connections can be initiated from any Nodestream enabled hardware encoder. The interface requires minimal input from a user standpoint and the results are in line with expectation.
Pilot commercial opportunities are being identified and trials are expected to commence in Q1 2022.
Furthermore, having previously read extensively into this, from...
Add to My Watchlist
What is My Watchlist?
