FAQ

Which Ports are used by SwyxWare (<= v6.01) (kb2308)

The information in this article applies to:

  • SwyxPhone L440
  • SwyxPhone L400
  • SwyxPhone L420
  • SwyxFax til v6.01, SwyxWare til v6.01

[ Question | Answer | Further Informationen ]


Question

Which Ports are used by SwyxWare and how do I have to configure my Firewall?


Answer

Information about the used ports of other SwyxWare version can be found here:

SwyxWare does consist of:

  • Clients:
    • SwyxIt!
    • SwyxPhone L400
    • SwyxPhone L420, L420e, L420s
    • SwyxPhone L440
    • SwyxPhone L100
  • Server:
    • SwyxServer
    • SwyxGate
    • LinkManager
    • ConferenceManager
    • PhoneManager
    • ITSPManager
    • SwyxFax Server

 

Connections can be devided into 2 phases: callcontrol (connection establishment/destruction) and the data phase (transmission of audio- of faxpackets).

The audio data will always be transmitted via UDP. Faxdata may be transmitted via UDP or TCP, by default UDP is used up to the current version of SwyxWare (4.10). For all these data transmissions the following source- and destinationports are used:

 

Product Portrange
SwyxIt! 50000-50099
SwyxPhone L400 5010/11
SwyxPhone L420 5006/7
SwyxPhone L420e,s 5010/11
SwyxPhone L440 5010/11
SwyxPhone L100 4103-4119
SwyxServer 51000-51499
SwyxGate 51500-51999
LinkManager 55000-56000
ConferenceManager 56000-57000
PhoneManager no data ports
ITSPManager no data ports
SwyxFax Server 2000-8000,61000

Callcontrol is done with the help of the following protocols:

  • H.323 -> TCP + UDP
  • SIP -> TCP + UDP
  • Microsoft DCOM -> not deterministic
  • CorNet -> TCP
  • ITSP -> TCP

H.323 is a kind of umbrella standard and consists of the protocols RAS (UDP), H.225 and H.245 (both TCP).
Registration of clients is done via RAS and H.225/H.245 is used for callcontrol (e.g. establishment of calls and opening of audio channels etc.).
Some of these protocols use well known ports for the initial connections. The following table shows which ports are used:

 

Protocol Type Destinationport Sourceport
H.323 - RAS UDP 1718 (multicast) + 1719 (unicast) indeterminate
H.323 — H.225 TCP 1720 1 indeterminate
H.323 — H.245 TCP indeterminate (negotiated via H.225) indeterminate
SIP UDP or TCP 5060 2 indeterminate
Microsoft DCOM 3 UDP or TCP indeterminate indeterminate
CorNet TCP 4060
4061
indeterminate
ITSP TCP 4102 indeterminate

1 Technically it's impossible for different applications to listen at the same port. In case of installation of SwyxServer and LinkManager respectively Gateway on the same machine port 65000 and 65001 is used by the LinkManager and port 2000 is used by the Gateway.
2 For the same reason as mentioned above, the LinkManager listens on port 65002 for SIP message, because the SwyxServer claimed port 5060 for SIP.
3 More details are available here:

http://msdn.microsoft.com/library/en-us/dndcom/html/msdn_dcomfirewall.asp
http://support.microsoft.com/support/kb/articles/Q248/8/09.ASP
http://support.microsoft.com/support/kb/articles/Q300/0/83.ASP

 

The next table shows the used call control protocols and the necessary ports for each product:

 

Protocol Port Comment Configurable via
SwyxServer:
UDP 1718 H.323/RAS multicast (WellKnown) -
UDP 1719 H.323/RAS unicast (WellKnown) -
UDP 51000-51499 RTP Audio-/Faxdata Registry (RTPFirstPort, RTPLastPort)
TCP 1720 H.323/H.225 CallSignalling (WellKnown) Registry (H323CallSignalingPort)
UDP + TCP 5060 SIP CallSignalling (WellKnown) Registry (SIPListenerPort)
SwyxGate:
UDP 2001 H.323/RAS unicast SwyxWare Administration
UDP 51500-51999 RTP Audio-/Faxdata SwyxWare Administration
TCP 2000 H.323/H.225 CallSignaling SwyxWare Administration
LinkManager:
UDP + TCP 55000-56000 RTP Audio-/Faxdata Registry (LowerBoundMediaPortUdp/Tcp, UpperBoundMediaPortUdp/Tcp)
TCP 65000 H.323 CallSignalling (local endpoint) Registry (TcpPortOfLocalH323Endpoint)
TCP 65001 H.323 CallSignalling (remote endpoint) Registry (TcpPortOfRemoteH323Endpoint)
UDP + TCP 65002 SIP (remote endpoint) Registry (TcpPortOfRemoteSipEndpoint)
ConferenceManager:
UDP 56000-57000 RTP Audiodata Registry (LowerBoundMediaPortUdp, UpperBoundMediaPortUdp)
PhoneManager:
TCP 4061 CorNet TC -
ITSPManager:
TCP 4102 ITSP Port -
SwyxIt!:
UDP 50000-50099 RTP Audiodata Registry (PortrangeBegin, PortrangeEnd)
SwyxPhone L100:
UDP 4103-4119 RTP Audiodata -
SwyxPhone L400/L420/L440:
UDP 5010/11 5006/7 RTP Audiodata -
TCP 1720 H.323/H.225 CallSignaling (WellKnown) -
SwyxFax Server:
TCP 61000 H323 registration on SwyxServer -
UDP+TCP 2000-8000 H323 connection for fax sessions -

Basically audio and fax data will always be transmitted directly between caller and callee, if both are located in the same site. This is different from the call control messages, which are always exchanged via the SwyxServer. Some clients don't communicate directly with the SwyxServer (as SwyxIt! does), but use in case of L420 phones the Phonemanager and in case of L100 phones the ITSPmanager for call control.
In configurations with more than 1 site there will always be at least one LinkManager. This LinkManager transfers all call control messages between the two SwyxServers (one server for each site) via H.323. Additionally this LinkManager transfers the audio and fax data between two parties calling from one site to the other. If necessary, the LinkManager will transcode the audio data.
This means, if SwyxIt! A from site Aachen establishes a call with SwyxIt! B from site Bochum the following will be done:

  1. SwyxIt! A will contact via DCOM the local SwyxServer of site Aachen.
  2. The SwyxServer of site Aachen will contact the SwyxServer of site Bochum via the LinkManager using H.323.
  3. The SwyxServer of site Bochum will contact the SwyxIt! B via DCOM as the called party.
  4. In case SwyxIt! B does pick up the call the LinkManager will transfer the audio data between SwyxIt! A and SwyxIt! B. The SwyxServers are not used at all for transmitting the audio data.

Please take a look at the following, additional articles:


Further Informationen



Comment

Comment on this article



If we have any follow-up questions, where can we contact you?

E-Mail Address (optional)


Note

This feedback form can't be used for support requests. Those requests must be directed to your Swyx reseller or distributor.