{"id":14181,"date":"2019-09-09T09:00:02","date_gmt":"2019-09-09T09:00:02","guid":{"rendered":"https:\/\/blog.tmcnet.com\/blog\/rich-tehrani\/?p=14181"},"modified":"2022-10-14T18:27:50","modified_gmt":"2022-10-14T22:27:50","slug":"highfive-video-collaboration-platform-connects-across-any-sip-enabled-meeting-platform","status":"publish","type":"post","link":"https:\/\/blog.tmcnet.com\/blog\/rich-tehrani\/fow\/highfive-video-collaboration-platform-connects-across-any-sip-enabled-meeting-platform.html","title":{"rendered":"Highfive Video Collaboration Platform Connects Across Any SIP-Enabled Meeting Platform"},"content":{"rendered":"\n

Dealing with numerous collaboration and conferencing platforms can be a productivity drain as well as a security risk. Often companies do not allow downloads, making it a challenge for communications between companies which use different platforms.<\/p>\n\n\n\n

WebRTC has made this less problematic but has not eliminated the issue. <\/p>\n\n\n\n

To solve this problem, the Highfive Meeting Connector overcomes vendor-to-vendor incompatibility, allowing users to easily meet and collaborate. <\/p>\n\n\n\n

This new tool allows any Highfive user to connect directly with third-party video conferencing platforms, including BlueJeans, Webex, Zoom and other SIP-enabled platforms. Meeting Connector removes barriers to connectivity such as toggling between meeting platforms or connecting with outside organizations that use other meeting platforms, which can burden workers and inhibits collaboration. <\/p>\n\n\n\n

Meeting\nConnector was built using proprietary technology from Highfive and functions\nthat leveraged vendor APIs, WebRTC and SIP interoperability. It is designed to\nenable teams to use hardware and software they\u2019ve already deployed and then\nconnect with parties using other meeting services. Unlike today\u2019s existing\nintegrations, such as purpose-built applications that connect two technologies\nlike a Poly system or Zoom, Highfive Meeting Connector requires no special\nconfiguration and serves as a bridge between SIP-enabled meeting systems.<\/p>\n\n\n\n

\u201cWhile the video collaboration industry has come a long way in the last decade, we still tend to cling to legacy technologies and proprietary services. But is this what\u2019s best for better collaboration to get work done?\u201d commented Joe Manuele, CEO at Highfive. \u201ciPhone users can easily text with Android users, so why shouldn\u2019t Highfive connect with another meeting vendor? Our ability to connect transcends the time, energy and frustration drain workers experience when there are barriers to connecting and collaborating with others.\u201d<\/p>\n\n\n\n

In our ongoing mission to make video conferencing ubiquitous, Highfive continues to make timely investments in smart, easy-to-use technology, giving end users a seamless experience from the desktop to their Highfive meeting room. <\/p>Concluded Manuele. <\/cite><\/blockquote>\n\n\n\n

We are pretty excited about this new solution which allows various video collaboration systems to interoperate. It is similar to what Mio has done with messaging<\/a>.<\/p>\n\n\n\n

This is great news for the Future of Work<\/a> – which encompasses advanced collaboration tools and enhanced productivity.<\/p>\n\n\n\n

Where do organizations go to learn more? The world\u2019s only\u00a0Future of Work Expo<\/a>\u00a0(collocated with the\u00a0ITEXPO\u00a0<\/a>#TechSuperShow) of course. Feb 12-14, 2020 in Fort Lauderdale, Florida. <\/p>\n\n\n\n

\"\"<\/figure>\n","protected":false},"excerpt":{"rendered":"

Dealing with numerous collaboration and conferencing platforms can be a productivity drain as well as a security risk. Often companies do not allow downloads, making it a challenge for communications between companies which use different platforms. WebRTC has made this less problematic but has not eliminated the issue. To solve this problem, the Highfive Meeting<\/p>\n","protected":false},"author":44,"featured_media":14182,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[155],"tags":[1263,2339,1900,1899,2338,14,2057,4,868],"post_mailing_queue_ids":[],"_links":{"self":[{"href":"https:\/\/blog.tmcnet.com\/blog\/rich-tehrani\/wp-json\/wp\/v2\/posts\/14181"}],"collection":[{"href":"https:\/\/blog.tmcnet.com\/blog\/rich-tehrani\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.tmcnet.com\/blog\/rich-tehrani\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.tmcnet.com\/blog\/rich-tehrani\/wp-json\/wp\/v2\/users\/44"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.tmcnet.com\/blog\/rich-tehrani\/wp-json\/wp\/v2\/comments?post=14181"}],"version-history":[{"count":1,"href":"https:\/\/blog.tmcnet.com\/blog\/rich-tehrani\/wp-json\/wp\/v2\/posts\/14181\/revisions"}],"predecessor-version":[{"id":14183,"href":"https:\/\/blog.tmcnet.com\/blog\/rich-tehrani\/wp-json\/wp\/v2\/posts\/14181\/revisions\/14183"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.tmcnet.com\/blog\/rich-tehrani\/wp-json\/wp\/v2\/media\/14182"}],"wp:attachment":[{"href":"https:\/\/blog.tmcnet.com\/blog\/rich-tehrani\/wp-json\/wp\/v2\/media?parent=14181"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.tmcnet.com\/blog\/rich-tehrani\/wp-json\/wp\/v2\/categories?post=14181"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.tmcnet.com\/blog\/rich-tehrani\/wp-json\/wp\/v2\/tags?post=14181"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}