Avaya 1000 Manual page 4

Port ranges for dynamic ports can vary based on platforms and applications used. Refer to the port listing tables below for the
CS1000 R5.5 dynamic ports used.
Well Known Ports
For the purpose of providing services to unknown clients, a service listen port is defined. This port is used by the server
process as its listen port. Common services often use listen ports in the well known port range. A well known port is
normally active meaning that it is "listening" for any traffic destined for a specific application. For example, well known port 23
on a server is actively waiting for a data source to contact the server IP address using this port number to establish a Telnet
session. Well known port 25 is waiting for an email session, etc. These ports are tied to a well understood application and
range from 0 to 1023.
In UNIX and Linux operating systems, only root may open or close a well-known port. Well Known Ports are also commonly
referred to as "privileged ports".
Registered Ports
Unlike well known ports, these ports are not restricted to the root user. Less common services register ports in this range.
Avaya uses ports in this range for call control. Some, but not all, ports used by Avaya in this range include: 1719/1720 for
H.323, 5060/5061 for SIP, 2944 for H.248 and others. The registered port range is 1024 – 49151. Even though a port is
registered with an application name, industry often uses these ports for different applications. Conflicts can occur in an
enterprise when a port with one meaning is used by two servers with different meanings.
Dynamic Ports
Dynamic ports, sometimes called "private ports", are available to use for any general purpose. This means there are no
meanings associated with these ports (similar to RFC 1918 IP Address Usage). These are the safest ports to use because no
application types are linked to these ports. The
Dynamic ports are also known as "Ephemeral ports". Ephemeral ports are short lived ports that are dynamically assigned.
Typically ephemeral ports are assigned on the client side of a TCP or UDP interaction. With FTP and RPC, ephemeral ports
are also assigned on the server side as part of the protocol.
The most effective method to manage ephemeral ports in a firewall is through the use of connection tracking. These features
examine the application protocol (e.g. FTP, RPC) to open the required firewall ports temporarily. Connection tracking for TCP,
FTP and RPC is commonly available. UDP connection tracking is available in some firewalls.
When connection tracking is not used in firewalls for TCP, RPC or FTP protocols it is necessary to open all the ports in the
ephemeral port ranges.
Port ranges for dynamic ports can vary based on platforms and applications used. Refer to the port listing tables below for the
CS1000 R7.6 dynamic ports used.
Sockets
A socket is the pairing of an IP address with a port number. An example would be 192.168.5.17:3009, where 3009 is the
socket number associated with the IP address. A data flow, or conversation, requires two sockets – one at the source device
and one at the destination device. The data flow then has two sockets with a total of four logical elements. Each data flow
must be unique. If one of the four elements is unique, the data flow is unique. The following three data flows are uniquely
identified by socket number and/or IP address.
Data Flow 1:
Data Flow 2:
Data Flow 3:
Use pursuant to the terms of your signed agreement or Avaya policy.
Avaya Communication Server 1000 Port Utilization – Issue 4.04
IANA
172.16.16.14:1234
172.16.16.14.1235
172.16.16.14:1234
Avaya – Proprietary.
suggests 49152 to 65535 as "dynamic and/or private ports".
- 10.1.2.3:2345
- 10.1.2.3:2345
- 10.1.2.4:2345
4