The ICE proxy has 2 operational modes:
- multiplexing mode
In multiplexing mode all incoming connections will be multiplexed over a dedicated port
- dynamic mode
In dynamic mode each connection will be terminated at a dedicated port, which is opened dynamically. Dynamic mode may be used behind NAT environments to allow the server to be running with a NATed IP.
Both modes share the main part of the configuration. To enable multiplexing mode change the multiplexing attribute to true. In this case all configuration withinin the dynamic attribute are rendered invalid. For dynamic mode change the multiplexing flag to false. This enabled the dynamic configuration.
In dynamic mode an external STUN or TURN server may be used to allow the server tp gather it’s external IP ( Scenario NAT environment!) The port range used may be configured also to allow firewall configurations to match.
{
"log" : {
"systemd" : false,
"file" : "stdout",
"level" : "debug"
},
"proxy" : {
"multiplexing" : false,
"ssl" :
{
"certificate" : "resources/certificate/openvocs.test.crt",
"key" : "resources/certificate/openvocs.test.key",
"CA file" : "resources/certificate/openvocs.test.crt"
},
"dynamic" :
{
"port" :
{
"min" : 1025,
"max" : 65535
},
"stun" :
{
"server" :
{
"host" : "87.238.197.166",
"type" : "UDP",
"port" : 3478
}
},
"turn" :
{
"server" :
{
"host" : "127.0.0.1",
"type" : "UDP",
"port" : 12345
},
"user" : "user1",
"password" : "user1"
}
},
"manager" :
{
"host": "127.0.0.1",
"port": 12345,
"type": "TCP"
},
"external" :
{
"host": "192.168.2.112",
"port": 50000,
"type": "UDP"
},
"internal" :
{
"host": "192.168.2.112",
"port": 0,
"type": "UDP"
},
"limits":
{
}
}
}
All configurations must use the SSL attribute filled with the respective data.
The manager socket configuration defines the ov_vocs_mc.service to be used and must be filled accordingly.
The external host is the host used for Multiplexing and Dynamic ICE operations. In multiplexing mode the port configured will be used, in dynamic mode a port from the port range will be used.
Internal host is the internal host configuration of the openvocs core network. The same network like used for the ov_mixer services must be set.