*** Please also note the currently valid Security hints for the configuration of a SwyxWare system ***
Regarding SwyxWare the central units inside the network are the SwyxServer and the ConfigDataStore. The main task of the SwyxServer is the call control, means delivery of calls to the correct destination. Additionally, it takes care about status signalling, scripting and a lot of other things.
The main purpose of the ConfigDataStore is to store all configuration items of SwyxWare, but it’s also used to store phonebooks, caller lists etc.
Taking this into account we can divide the network communication of SwyxWare into 3 major parts:
- Loading and saving configuration items
- Connect and disconnect of calls via CallControl
- Transmission of voice/audio and fax data
The ConfigDataStore is implemented as a WebService which means, that all clients access the service via a well-known TCP port. The ConfigDataStore listens at TCP port 9094, it never initiates network connections by itself. With SwyxWare SDC port 9095 is used additionally.
Since SwyxWare 2011 only SIP is used as CallControl protocol.
Transmission of audio- and fax data is always done via UDP. The audio frames are encapsulated into RTP (Realtime Protocol) packets and the fax data is transmitted via the T.38 protocol. Both protocols (RTP and T.38) are using UDP for transmission.
Please keep in mind, that the CallControl is always done via the SwyxServer itself, but the audio- and fax data is send directly between the two connected clients.
The attached file show for all SwyxWare components the used ports and type of transport for CallControl and audio-/fax data. In case it’s possible to configure them, this will be mentioned.
For Yealink T4xs - Device the official Ports from Yealink are used: