Add private-port flag for ICE endpoints #406
Description
Feature Request
Description of Problem:
During WhatsApp integration had some issue because WA media's servers are using a shared port for multiple calls, like SMB does. That causes issues to contextualize packets as there are no unique ip-port pair for at least one side.
We do have the possibility to allocate a conference in their own port and all participants of that conference/mixer will share the same port. Although that works, it is not acceptable for Symphony use case since it would require Symphony customers to whitelist a much wider range of UDP ports.
Then the solution is have a new boolean on endpoint allocation that allow to choose private or share port by endpoint basis. That will allow us to configure a private port for WA leg while keep the Symphony's client on the shared media port.
Potential Solutions:
Solution will be adding a new flag on endpoint allocation in the "transport" json object. The name will be private-port and it will be false by default. This is only has an effect on ICE endpoints once the non ICE endpoints use always a private port.
Not providing this flag or set it as false for ICE endpoints. It will allocate the endpoint on the same port of the conference/mixer (if global-port was set to false when conference was created), or in the SMB shared port when conference/mixer when global-port is set to true (default value). When the new endpoint configuration private-port is set to true for ICE endpoints, it will always allocate a private port exclusively for this endpoint, regardless the value of global-port on the conference level.