{"id":2866,"date":"2017-06-08T16:43:40","date_gmt":"2017-06-08T14:43:40","guid":{"rendered":"https:\/\/www.boc.de\/watchguard-info-portal\/?p=2866"},"modified":"2017-08-12T23:18:55","modified_gmt":"2017-08-12T21:18:55","slug":"anbindung-polycom-group-500-an-bluejeans-video-conferencing-cloud","status":"publish","type":"post","link":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/2017\/06\/anbindung-polycom-group-500-an-bluejeans-video-conferencing-cloud\/","title":{"rendered":"Anbindung Polycom Group 500 an BlueJeans Video Conferencing Cloud"},"content":{"rendered":"<p>Um ein Video Konferenz Terminal vom Typ Polycom Group 500 an <strong>BlueJeans<\/strong> anzubinden (eine Cloudl\u00f6sung f\u00fcr Group Video Conferences), sind netterweise nur outgoing Ports in der WatchGuard Firewall freizuschalten. Das BlueJeans System ist so gestrickt, dass sich alle Clients \u00fcber eine ausgehende Verbindung zu dem BlueJeans Cloud-Server verbinden und ihren Video-Stream von dort geliefert bekommen.<\/p>\n<p>Die Dokumentation von BlueJeans in deren Support-Bereich ist eine wahre Freude f\u00fcr Firewall-Administratoren:<\/p>\n<h4>Verwendete Ziel-Adressen:<\/h4>\n<ul>\n<li>199.48.152.0\/22<\/li>\n<li>31.171.208.0\/21<\/li>\n<li>103.20.59.0\/24<\/li>\n<li>103.255.54.0\/24<\/li>\n<li>8.10.12.0\/24<\/li>\n<li>165.254.117.0\/24<\/li>\n<\/ul>\n<h4>Je nach Protokoll werden folgende Ports verwendet:<\/h4>\n<p><strong>BlueJeans Desktop App &amp; Mobile App, BlueJeans Huddle and Chrome WebRTC:<\/strong><\/p>\n<ul>\n<li>Outbound TCP Port 443, 5061 or 5000 &#8211; Call Setup Signaling<\/li>\n<li><span style=\"font-size: inherit;\">Media Outbound UDP Ports 5000-5999 &#8211; RTP Media<\/span><\/li>\n<\/ul>\n<p><strong>H.323 based Room System:<\/strong><\/p>\n<ul>\n<li>Outbound TCP Port 1720 &#8211; H.225 Signaling for H.323<\/li>\n<li>Outbound TCP Ports 5000-5999 &#8211; H.245 Call Control for H.323<\/li>\n<li>Outbound UDP Ports 5000-5999 &#8211; RTP Media<\/li>\n<\/ul>\n<p><strong>SIP based Room System:<\/strong><\/p>\n<ul>\n<li>Outbound TCP Port 5060 &#8211; SIP Signaling<\/li>\n<li>Outbound TCP Port 5061 &#8211; SIPS (TLS) Signaling<\/li>\n<li>Outbound UDP Ports 5000-5999 &#8211; RTP Media<\/li>\n<\/ul>\n<p><strong>Microsoft Lync\/ Skype For Business client:<\/strong><\/p>\n<ul>\n<li>Outbound &amp; Inbound TCP Port 5061 &#8211; Lync Federation and SIP\/TLS connection.<\/li>\n<li>Outbound &amp; Inbound UDP Ports 50000-59999 &#8211; RTP Media<\/li>\n<li>Outbound &amp; Inbound TCP Ports 50000-59999 &#8211; RTP Media<\/li>\n<\/ul>\n<h4>Fazit:<\/h4>\n<p><strong>Dies ist eine sehr freundliche L\u00f6sung im Hinblick auf die notwendigen Freigaben in der Firewall.<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Um ein Video Konferenz Terminal vom Typ Polycom Group 500 an BlueJeans anzubinden (eine Cloudl\u00f6sung f\u00fcr Group Video Conferences), sind netterweise nur outgoing Ports in der WatchGuard Firewall freizuschalten. Das BlueJeans System ist so gestrickt, dass sich alle Clients \u00fcber eine ausgehende Verbindung zu dem BlueJeans Cloud-Server verbinden und ihren Video-Stream von dort geliefert bekommen. Die Dokumentation von BlueJeans in deren Support-Bereich ist eine wahre &hellip; <a href=\"https:\/\/wordpress.boc.de\/watchguard-info-portal\/2017\/06\/anbindung-polycom-group-500-an-bluejeans-video-conferencing-cloud\/\" class=\"more-link\">Weiterlesen <span class=\"screen-reader-text\">Anbindung Polycom Group 500 an BlueJeans Video Conferencing Cloud<\/span> <span class=\"meta-nav\">&raquo;<\/span><\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-2866","post","type-post","status-publish","format-standard","hentry","category-watchguard-technischer-blog"],"_links":{"self":[{"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/posts\/2866"}],"collection":[{"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/comments?post=2866"}],"version-history":[{"count":3,"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/posts\/2866\/revisions"}],"predecessor-version":[{"id":3175,"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/posts\/2866\/revisions\/3175"}],"wp:attachment":[{"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/media?parent=2866"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/categories?post=2866"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wordpress.boc.de\/watchguard-info-portal\/wp-json\/wp\/v2\/tags?post=2866"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}