kenmirrors/freeswitch
1
0
Fork 0
mirror of https://github.com/signalwire/freeswitch.git synced 2025-05-30 02:20:11 +00:00
Code Issues Projects Releases Wiki Activity

misc readme updates (#2235)

Browse Source 
* Update README.md regarding the archived freeswitch-users mailing list

* update docker/README.md to suggest --network host
This commit is contained in:
tmancill 2023-09-09 09:26:04 -07:00 committed by GitHub
parent bb9afcb388
commit dc3c0f00f3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 12 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -67,8 +67,8 @@ This is the place to get answers faster and chat with other users in real time.
Slack Community: Slack Community:
* https://signalwire.community/ * https://signalwire.community/
Mailing list: Mailing list (ARCHIVED):
* http://lists.freeswitch.org/mailman/listinfo/freeswitch-users * http://lists.freeswitch.org/pipermail/freeswitch-users/
**Thank you for using FreeSWITCH!** **Thank you for using FreeSWITCH!**

18
docker/README.md
View File

@ -2,7 +2,7 @@
These are the official Docker files for master branch and the current release packages. These are the official Docker files for master branch and the current release packages.
## Volumes ## Volumes
These containers are setup so that you can mount your freeswitch configuration form a host or data volume container. These containers are set up so that you can mount your freeswitch configuration from a host or data volume container.
To mount freeswitch Configuration To mount freeswitch Configuration
``` ```
@ -16,17 +16,19 @@ To mount tmp directory for storing recordings, etc
The container also has a healthcheck where it does a fs_cli status check to make sure the freeswitch service is still running. The container also has a healthcheck where it does a fs_cli status check to make sure the freeswitch service is still running.
# Ports ## Ports
The container exposes the following ports: The container should be run with host networking using `docker run --network host ...`.
- 5060/tcp 5060/udp 5080/tcp 5080/udp as SIP Signaling ports. If you prefer to (or for some reason must) publish individual ports via `--publish/-p`, refer to this [issue](https://github.com/moby/moby/issues/11185) and this [potential workaround](https://hub.docker.com/r/bettervoice/freeswitch-container/) regarding using docker with large port ranges.
- 5066/tcp 7443/tcp as WebSocket Signaling ports.
- 8021/tcp as Event Socket port.
- 64535-65535/udp as media ports.
- 16384-32768/udp
The following ports will be used, depending upon your specific configuration:
- 5060/tcp, 5060/udp, 5080/tcp, 5080/udp - SIP signaling
- 5061/tcp, 5081/tcp - SIPS signaling
- 5066/tcp, 7443/tcp - WebSocket signaling
- 8021/tcp - the Event Socket
- 16384-32768/udp, 64535-65535/udp - media
If you wish to help improve these please submit a pull request at: If you wish to help improve these please submit a pull request at: