This page describes basic testing and diagnostics of FreeSWITCH™ on macOS. It is part of the FreeSWITCH™ macOS documentation.
---
Before testing FreeSWITCH™ verify that the installation was completed normally. If using macFI open the installation log folder on the desktop then open the "make" log and scroll to the bottom. If there are errors they must be resolved. If you performed a manual installation each step should have been checked before proceeding to the next step.
Regardless of how FreeSWITCH™ was installed it can be started from the command line or from macFI by selecting the "Test FreeSWITCH" option.
Start FreeSWITCH™ in a Terminal window using these commands:
cd /usr/local/freeswitch/bin ./freeswitch |
There are many startup messages ending with some text boxes containing the names of the developers.
After all startup messages are displayed a command prompt appears, messages may continue as the prompt remains. Try a few FreeSWITCH™ commands:
version status sofia status |
If the commands return responses FreeSWITCH™ is working and you can continue with the next step.
Test using a physical SIP phone or soft phone such as Bria Desktop or Bria for iPhone, or search the macOS App Store for "SIP" for a free download of Telephone. Then follow these steps:
To establish a connection between phones, a second phone must be setup as follows:
User IDs 1000-1019 with password 1234 are pre-configured so up to 20 phones can be tested. To experience the potential of FreeSWITCH™ perform some functions found in Test Calls.
Issue the following command in the FreeSWITCH™ Terminal window:
shutdown |
If there is a problem you may need to provide diagnostic information to the developers. For instance, to see if your phones are registered during testing using the following command:
sofia status profile internal reg |
There is a limited Troubleshooting Freeswitch and Troubleshooting Debugging information page available on the wiki. However, if you report a problem you will be asked for traces and log options. It will help to have them in advance if possible so you should become familiar with some of the following debugging commands:
reloadxml log 7 console loglevel debug sofia loglevel all 9 sofia profile profname(external..) siptrace on/off sofia status [profilename} sofia global siptrace on sofia reload sofia profile <name> restart nat_map status nat_map reinit fsctl debug_level 1 fsctl send_sighup # <- To force the freeswitch.log file to segment. |
You may be asked for traces of the actual network data on the lan connection. The most common tools for this purpose are:
Wireshark - Great network tool to examine TCP and SIP data. Download the macOS version here. Note: You should install the Wireshark application in the Applications folder and you must run Wireshark as root so it must be run from Terminal, see line below. A "Wireshark folder" was also created to hold other Wireshark supplied items.
sudo /Applications/Wireshark.app/Contents/MacOS/Wireshark |
All of these tools are supplied with macOS.
Find source paths to running processes - Open Terminal and type the command:
PS -hax |
Detailed resource usage dynamically updated - Open Terminal and type the command (-u sorts by processor utilization):
top top -u |
To terminate press control+z.