Docs: addition to document systemd startup and fs_cli usage. #285
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This addition documents how to start FreeSWITCH using systemd after installation and how to connect to the FreeSWITCH CLI. The reason is that the service does not start automatically, accessing the event socket requires explicitly starting the service.
Description
Type of Change
Related Issues
Testing
Checklist
Additional Notes
While installing on Debian 12 (bookworm) on multiple servers, I came across the issue of
fs_cli -rRSfailing to connect the socket, then I figured that it is because Freeswitch doesn't actually start automatically.Hence, I am adding this small fix to the documentation to make it explicit.