When the SOA-Clients receive the createPeerconnection Message they need additional informations for the WebRTC connection (right now this is just the list of STUN and TURN Servers)
To hard code them into the client doesn't seem right, so maybe we should add them to the createPeerconnection Message.
Keep in mind, that the CreatePeerconnection Message should be a general function that also works with other types of connections.
When the SOA-Clients receive the createPeerconnection Message they need additional informations for the WebRTC connection (right now this is just the list of STUN and TURN Servers)
To hard code them into the client doesn't seem right, so maybe we should add them to the createPeerconnection Message. Keep in mind, that the CreatePeerconnection Message should be a general function that also works with other types of connections.