FAQ

Which Ports are used by SwyxWare (v6.02 - 7.0) (kb3593)

The information in this article applies to:

  • SwyxWare v6.20 Maintenance Pack 1
  • SwyxIt! v6.25 Maintenance Pack 1
  • SwyxWare v7.00
  • SwyxIt! v6.25 Productivity Pack
  • SwyxPhone L680
  • SwyxPhone L660
  • SwyxPhone L640
  • SwyxPhone L620
  • SwyxWare v6.20
  • SwyxIt! v6.20
  • SwyxFax Server v6.20
  • SwyxIt! v6.12
  • SwyxFax Server v6.12
  • SwyxConnect 1724
  • SwyxConnect 1723
  • SwyxConnect 1722
  • SwyxWare v6.12
  • SwyxPhone S315
  • SwyxWare v6.11
  • SwyxFax Server v6.10
  • SwyxWare v6.10
  • SwyxFax Server v6.02
  • SwyxWare v6.02
  • SwyxDECT 800
  • SwyxConnect .
  • SwyxPhone L540
  • SwyxPhone L520s
  • SwyxPhone L440
  • SwyxPhone L400
  • SwyxPhone L420
  • SwyxIt! all versions

[ Question | Answer | Further Informationen ]


Question

Which Ports are used by SwyxWare?


Answer

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

SwyxWare does consist of:

  • Clients:
    • SwyxIt!
    • SwyxPhone L4xx(e,s), L5xx, L6xx 
    • SwyxPhone S315
    • SwyxDECT 800
  • Server:
    • SwyxServer
    • SwyxGate
    • LinkManager
    • ConferenceManager
    • PhoneManager
    • SwyxFax Server
    • MobileExtensionManager (MEM)
    • ConfigDataStore (CDS)

 

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 signaling, 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. With SwyxWare version 6.0x only the servercomponents like SwyxServer, LinkManager and some others made use of it, but from SwyxWare version 6.1x on the SwyxIt!-clients will connect to the ConfigDataStore directly, too. With versions lower than 6.1x the SwyxIt!-clients used Microsoft DCOM to load the configuration.
Taking this into account we can divide the network communication of SwyxWare into 3 major parts:
  1. Loading and saving configuration items
  2. Connect and disconnect of calls via CallControl
  3. Transmission of voice/audio and faxdata
The ConfigDataStore is implemented as a WebService which means, that all clients access the service via a wellknown TCP port. The ConfigDataStore listens at TCP port 9091 and 9092, it never initiates network connections by itself.
Different CallControl protocols are used inside the SwyxWare, like SIP, H.323 and Microsoft DCOM.
Transmission of audio- and faxdata is always done via UDP. The audioframes are encapsulated into RTP (RealTimeProtocol) packets and the faxdata 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 faxdata is send directly between the two connected clients.
Using this method it’s possible to translate between different CallControl protocols. E.g. it’s possible, that a SwyxIt!-User calls by using SIP via the SwyxServer someone inside the PSTN, which means, that the SwyxServer translates the SIP message into H.323 messages to establish the call via the SwyxGate (which uses H.323 for CallControl). Nevertheless the audiodata for this connection will be transmitted directly between the SwyxIt! and the SwyxGate.

The following tables show for all SwyxWare components the used ports and type of transport for CallControl and audio-/faxdata. In case it’s possible to configure them, this will be mentioned. 

 

SwyxServer:

 

Classification
Protocol
Type
Port
Configurable via
Configuration
CDS
TCP
Undetermined
 
CallControl
H.323/RAS multicast
UDP
1718, wellknown
 
CallControl
H.323/RAS unicast
UDP
1719, wellknown
 
CallControl
H.323/H.225
TCP
1720, wellknown
+ undetermined
 
CallControl
MS DCOM
TCP/UDP
Undetermined
 
CallControl
SIP
UDP + TCP
5060, wellknown
 
Audio
RTP
UDP
51000 - 51499
Registry:
RTPFirstPort, RTPLastPort
Master/Standby KeepAlive TCP 65010 Registry: StandbyPort
IntersitePresence (since v7.00) CDS TCP 9093  
 
ConfigDataStore-Service (CDS):

 

Classification
Protocol
Type
Port
Configurable via
Configuration
CDS
TCP

9091, 9092,

9089 (since 6.12.MP1 + 6.20 QF6)

 
 
SwyxGate:

 

Classification
Protocol
Type
Port
Configurable via
Configuration
CDS
TCP
Undetermined
 
CallControl
H.323/RAS
UDP
2001
 
CallControl
H.323/H.225
TCP
2000 + undetermined
 
Audio/Fax
RTP + T.38
UDP
52000 - 52499
 
 
LinkManager:

 

Classification
Protocol
Type
Port
Configurable via
Configuration
CDS
TCP
Undetermined
 
CallControl
(local EP)
H.323/RAS
UDP
65000
Registry:
TcpPortOfLocalH323Endpoint
CallControl
(local EP)
H.323/H.225
TCP
65000
Registry:
TcpPortOfLocalH323Endpoint
CallControl
(remote EP)
H.323/RAS
UDP
65001
Registry:
TcpPortOfRemoteH323Endpoint
CallControl
(remote EP)
H.323/H.225
TCP
65001
Registry:
TcpPortOfRemoteH323Endpoint
CallControl
SIP
UDP + TCP
65002
Registry:
TcpPortOfRemoteSipEndpoint
Audio/Fax
RTP + T.38
UDP
55000 – 56000
Registry:
LowerBoundMediaPortUdp,
UpperBoundMediaPortUdp
 
ConferenceManager:

 

Classification
Protocol
Type
Port
Configurable via
Configuration
MS DCOM
UDP + TCP
Undetermined
 
Audio
RTP
UDP
56000 – 57000
Registry:
LowerBoundMediaPortUdp,
UpperBoundMediaPortUdp
 
PhoneManager:

 

Classification
Protocol
Type
Port
Configurable via
Configuration
MS DCOM
UDP + TCP
Undetermined
 
CallControl
CorNet TC
TCP
4061
 
CallControl
H.323
TCP
1721
 
Configuration
DLS
TCP
18443
 
 
SwyxFaxServer:

 

Classification
Protocol
Type
Port
Configurable via
Configuration
MS DCOM
UDP + TCP
Undetermined
 
CallControl
H.323/RAS ( < v7.00)
SIP (>= v7.00)
UDP
61000
 since v7.00:
LowerBoundSipPort - UpperBoundSipPort
CallControl
H.323/H.225 ( < v7.00)
SIP (>= v7.00)
TCP
61000
 since v7.00: LowerBoundSipPort - UpperBoundSipPort
Fax
T.38
UDP
2000 - 8000
 
CDS CDS TCP 9090 (since v7.00)  
 
MobileExtensionManager (MEM):

 

Classification
Protocol
Type
Port
Configurable via
Configuration
CDS
TCP
Undetermined
 
CallControl
SIP
UDP + TCP
5070 – 5170
Registry:
SipListenerPort
Audio
RTP
UDP
50000 – 50999
Registry:
PortrangeBegin,
PortrangeEnd
 
SwyxIt!:

 

Classification
Protocol
Type
Port
Configurable via
Configuration
CDS
TCP
Undetermined
 
CallControl
SIP
UDP + TCP
5070 – 5170
Registry:
SIPListenerPort
Audio
RTP
UDP
50000 – 50999
Registry:
PortrangeBegin,
PortrangeEnd
 
SwyxPhone L4xx(e, s); L5xx; L6xx:

 

Classification
Protocol
Type
Port
Configurable via
CallControl
CorNet
TCP
4060, 4061
 
CallControl
H.323/H.225
TCP
1720
 
Configuration
HTTP
TCP
8085
 
Audio
RTP
UDP
5000-5020 (usually 5012/13)
 
ServerCheck
(old L420 only)
 ping  ICMP    
 
SwyxPhone S315:

 

Classification
Protocol
Type
Port
Configurable via
CallControl
SIP
UDP + TCP
5060
WebInterface
Audio
RTP
UDP
5000 – 5009, 5060
WebInterface
 
SwyxDect 800:

 

Classification
Protocol
Type
Port
Configurable via
CallControl
H.323/RAS
UDP
2048 – 65535
 
CallControl
H.323/H.225
TCP
2048 – 65535
 
Audio
RTP
UDP
16384 – 32767
WebInterface
 
SwyxConnect:

 

Classification
Protocol
Type
Port
Configurable via
CallControl
SIP
UDP + TCP
5060
 
Audio/Fax/General
RTP + T.38
UDP
32768 – 49151
 
General
 
TCP
3072 – 19455
 
Masquerading
 
UDP + TCP
53248 – 57343
 
 

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.