# OV 2.20 Pro edition: is it possible to deploy the coturn server on a port other than 3478?

**URL:** https://openvidu.discourse.group/t/ov-2-20-pro-edition-is-it-possible-to-deploy-the-coturn-server-on-a-port-other-than-3478/3710
**Category:** Issues with deployment
**Tags:** v2
**Created:** [January 16, 2022, 5:40am UTC](https://openvidu.discourse.group/t/ov-2-20-pro-edition-is-it-possible-to-deploy-the-coturn-server-on-a-port-other-than-3478/3710 "2022-01-16T05:40:04Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![mhowald](https://avatars.discourse-cdn.com/v4/letter/m/439d5e/32.png) [@mhowald](https://openvidu.discourse.group/u/mhowald)
#### Post date: [January 16, 2022, 5:40am UTC](https://openvidu.discourse.group/t/ov-2-20-pro-edition-is-it-possible-to-deploy-the-coturn-server-on-a-port-other-than-3478/3710/1 "2022-01-16T05:40:04Z")

</div>

Is it possible to specify a port other than 3478 for the coturn server to listen on?

I notice that `docker-compose.yml` specifies a COTURN\_PORT configuration variable in the source code:

> <https://github.com/OpenVidu/openvidu/blob/1965a6b44f3cf328c76e5fed4f714a0d5d9377b9/openvidu-server/deployments/pro/docker-compose/openvidu-server-pro/docker-compose.yml#L45>

But this line is not present in `/opt/openvidu/docker-compose.yml` on a fresh deployment of OV 2.20 Pro to AWS. Manually adding it back and restarting openvidu does not appear to have any effect.

I have also tried changing the listening port here:

> <https://github.com/OpenVidu/openvidu/blob/1965a6b44f3cf328c76e5fed4f714a0d5d9377b9/openvidu-server/deployments/pro/docker-compose/openvidu-server-pro/docker-compose.yml#L79>

However, even after making both configuration changes above, logging `openvidu.iceServers` from a client outputs:

`urls: ['turn:<my AWS IP>:3478']` rather than the expected `:80`.

Is there any way of deploying the coturn server to an alternate port? My reason for doing this is to circumvent particularly restrictive corporate firewalls on some client machines, which may block _outgoing_ connections on high ports.

Thanks!

---

<div class="post-metadata">

### Author: ![cruizba](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/cruizba/32/18_2.png) [@cruizba](https://openvidu.discourse.group/u/cruizba)
#### Post date: [January 17, 2022, 8:03pm UTC](https://openvidu.discourse.group/t/ov-2-20-pro-edition-is-it-possible-to-deploy-the-coturn-server-on-a-port-other-than-3478/3710/2 "2022-01-17T20:03:57Z")

</div>

We’ve recently added that option for the next release which would be available on the next weeks, for the next release you will only need to change COTURN\_PORT

For know I’m afraid that’s not possible by default.

But you can deploy an external Coturn if you want following the guide of this repo: [GitHub - OpenVidu/openvidu-external-coturn](https://github.com/OpenVidu/openvidu-external-coturn)

---

<div class="post-metadata">

### Author: ![mhowald](https://avatars.discourse-cdn.com/v4/letter/m/439d5e/32.png) [@mhowald](https://openvidu.discourse.group/u/mhowald)
#### Post date: [January 17, 2022, 8:22pm UTC](https://openvidu.discourse.group/t/ov-2-20-pro-edition-is-it-possible-to-deploy-the-coturn-server-on-a-port-other-than-3478/3710/3 "2022-01-17T20:22:31Z")

</div>

Thank you! This is very helpful. I’ll keep an eye out for the next release, and in the meantime look into deploying an external TURN server.