Move STUN/TURN to IANA-assigned ports - 3478 and 5349 (TLS)

[Yetangitu]

See #5714 (comment)

This change moves STUN/TURN to the IANA-assigned ports, 3478 and 5349 (TLS)

[jitsi-jenkins]

Hi, thanks for your contribution!
If you haven't already done so, could you please make sure you sign our CLA (https://jitsi.org/icla for individuals and https://jitsi.org/ccla for corporations)? We would unfortunately be unable to merge your patch unless we have that piece :(.

[damencho]

Can you grep through the whole repo for 4446, there are more places you are missing, like
https://github.com/jitsi/jitsi-meet/blob/master/doc/debian/jitsi-meet/jitsi-meet.conf#L10

[damencho]

Thank you

[Yetangitu]

Can you grep through the whole repo for 4446, there are more places you are missing, like
https://github.com/jitsi/jitsi-meet/blob/master/doc/debian/jitsi-meet/jitsi-meet.conf#L10

4446 does not occur anywhere in the repo but 4445 does, in that example you cited and one other file:

$ git grep 4445
debian/jitsi-meet-turnserver.postinst:                echo "turnserver is listening on tcp 4445 as other nginx sites use port 443"
debian/jitsi-meet-turnserver.postinst:                sed -i 's/"443"/"4445"/g' $PROSODY_HOST_CONFIG
doc/debian/jitsi-meet/jitsi-meet.conf:        server 127.0.0.1:4445;

I changed these to 5349 in the PR, assuming that it is the TLS-encrypted version of STUN/TURN which is to be used. If not it should be 3478 - in fact that port can be used both for unencrypted as well as encrypted traffic, at least with Coturn (from man turnserver):

       -p, --listening-port
              TURN listener port for UDP and TCP listeners (Default: 3478).  Note: actually, TLS & DTLS sessions can connect  to  the  "plain"  TCP  &  UDP
              port(s), too - if allowed by configuration.