Kofax Communication Server 9.1 User Manual
Page 107
Environment Guide
Version 3.00.04
© Copyright Kofax, Inc. All information is subject to change without notice.
107
FoIP/VoIP
Component
1720/tcp
IPPBX or
gateway
H.323 FoIP/VoIP
Component
N
N/A
H.323 with
FoIP/VoIP
Component
IPPBX or gateway
1024-
65535/tcp
N
N
H.323/H.245 call setup (particular port from
this range agreed during H.225 signaling
exchange and the calling H.323 endpoint
establishes connection to this port)
IPPBX or
gateway
H.323 with
FoIP/VoIP
Component
N
N/A
H.323 with
FoIP/VoIP
Component
IPPhone or
Gateway
10000-
10999/tcp
N
Y
Voice media data, particular port number from
this range is agreed through H.245 call control
IPPhone or
Gateway
H.323 with
FoIP/VoIP
Component
N
N/A
SIP with
FoIP/VoIP
Component
IPPBX or gateway
5060/udp
KCS 9.0
(FoIPv3
only)
Y
SIP call signaling
IPPBX or
gateway
SIP with
FoIP/VoIP
Component
KCS 9.0
(FoIPv3
only)
N/A
SIP with
FoIP/VoIP
Component
IPPhone or
Gateway
10000-
10999/udp
KCS 9.0
(FoIPv3
only)
Y
Voice media data
IPPhone or
Gateway
SIP with
FoIP/VoIP
Component
KCS 9.0
(FoIPv3
only)
N/A
Internet
Browser
TC/Web/
IIS Server
80/tcp or
443/tcp
KCS 9.0
Y
Client Internet browser connection with
TC/Web
TC/Report
TC/Probe
KCS
Monitoring API
MS-SQL
1434/udp
1433/tcp
Random
high TCP
ports
N
Y
Through UDP connection to the SQL Server
browser service the current port number of the
particular named-SQL server instance is being
fetched (the default SQL server instance
listens on the 1433/tcp)
See also
TC/SPI-MX
Exchange server
2003/2007
135/tcp
Random
high TCP
N
Y
At first a connection to MS-RPC endpoint
mapper is established (port 135), which tells to
the client which ports to use to connect to
particular Exchange service (typically high