BeroNet Telephony Appliance-v2

From berofix - professional SIP gateway
Jump to: navigation, search
(VNC - Console/Monitor for the VMs)
(VNC - Console/Monitor for the VMs)
Line 105: Line 105:
 
=== VNC - Console/Monitor for the VMs ===
 
=== VNC - Console/Monitor for the VMs ===
  
By default each Virtual Machine starts a VNC Server on the Ports between '''5900 - 5905'''. Any VNC tool can connect to this port, e.g. tightvnc for linux and windows:  
+
By default each Virtual Machine starts a VNC Server on the Ports between '''5900 - 5905'''. Any VNC tool can connect to this port, e.g. tightvnc for linux and windows: '''[http://www.tightvnc.com/download.php TightVNC]'''
+
[http://www.tightvnc.com/download.php TightVNC]
+
 
   
 
   
 
The Dashboard provides a built-In WebtRTC based WebVNC Client from Kanaka: [http://kanaka.github.io/noVNC/ noVNC Client]. As the VNC Server of the VM is not a WebRTC Server, a WebRTC Proxy is used to connect the VM VNC Server and the noVNC Client. We're using again Kanakas Socket Proxy: [https://github.com/kanaka/websockify websockify] for that.
 
The Dashboard provides a built-In WebtRTC based WebVNC Client from Kanaka: [http://kanaka.github.io/noVNC/ noVNC Client]. As the VNC Server of the VM is not a WebRTC Server, a WebRTC Proxy is used to connect the VM VNC Server and the noVNC Client. We're using again Kanakas Socket Proxy: [https://github.com/kanaka/websockify websockify] for that.

Revision as of 11:13, 13 March 2016

Personal tools