Avaya 1000 Manual page 3

Avaya Communication Server 1000 Port Utilization – Issue 4.04
Avaya Port Matrix for Communication Server 1000
Applicable Releases
Version 1.00 of this document is applicable to the Communication Server 1000 Release 5.5 and the MGC Loadware
MGCCAMxx.
Version 2.XX of this document is applicable to the Communication Server 1000 Release 6.0 and at a minimum the MGC
loadware MGCCAP02. The method to present the information is modified from the previous version and reflects the
introduction new component. Additions from the previous document are either reflected in the Comments column of the
various tables or as a generic statement for the entire table.
Version 3.XX of this document is applicable to the Communication Server 1000 Release 7.0 and at a minimum the MGC
loadware MGCCBD01. Additions from the previous document are either reflected in the Comments column of the various
tables or as a generic statement for the entire table.
Version 4.XX of this document is applicable to the Communication Server 1000 Release 7.5/7.6 and at a minimum the MGC
loadware MGCCCD01. Additions from the previous document are either reflected in the Comments column of the various
tables or as a generic statement for the entire table.
Defining TCP/IP Ports
What are ports and how are they used?
TCP and UDP use ports (defined at http://www.iana.org/assignments/port-numbers) to route traffic arriving at a particular IP
device to the correct upper layer application. These ports are logical descriptors (numbers) that help devices multiplex and de-
multiplex information streams. Consider your desktop PC. Multiple applications may be simultaneously receiving information.
In this example, email may use destination TCP port 25, a browser may use destination TCP port 80 and a telnet session may
use destination TCP port 23. These logical ports allow the PC to de-multiplex a single incoming serial data packet stream into
three mini-streams inside the PC. Furthermore, each of the mini-streams is directed to the correct high-level application
because the port numbers identify which application each data mini-stream belongs. Every IP device has incoming (Ingress)
and outgoing (Egress) data streams.
Ports are used in TCP and UDP to name the ends of logical connections which carry data flows. TCP and UDP streams have
an IP address and port number for both source and destination IP devices. The pairing of an IP address and a port number is
called a socket (discussed later). Therefore, each data stream is uniquely identified with two sockets. Source and destination
sockets must be known by the source before a data stream can be sent to the destination. Some destination ports are "open"
to receive data streams and are called "listening" ports. Listening ports actively wait for a source (client) to make contact to a
destination (server) using a specific port that has a known protocol associate with that port number. HTTPS, as an example,
is assigned port number 443. When a destination IP device is contacted by a source device using port 443, the destination
uses the HTTPS protocol for that data stream conversation.
Port Type Ranges
Port numbers are divided into three ranges: Well Known Ports, Registered Ports, and Dynamic Ports (sometimes called
Private Ports).
Well Known Ports are those numbered from 0 through 1023.
Registered Ports are those numbered from 1024 through 49151
Dynamic Ports are those numbered from 49152 through 65535
The Well Known and Registered ports are assigned by IANA (Internet Assigned Numbers Authority) and are found here:
http://www.iana.org/assignments/port-numbers.
Avaya – Proprietary.
3
Use pursuant to the terms of your signed agreement or Avaya policy.