ACCESS Product Manual
115
A
PPEndIx
B
I
nformAtIon
for
It m
AnAgErS
The purpose of this appendix is to describe all open ports and services
available on the Comrex ACCESS. If a service is not mentioned here, it is
disabled by default.
The Comrex ACCESS is a device designed to move real-time, wideband
audio over IP networks. The main network interface is 10/100 10baseT
Ethernet.
The device contains an optimized version of the 2.6 Linux kernel. The IP
parameters are set using a GUI that requires attachment of a keyboard and
VGA monitor to the device.
Alternately, during the first five minutes of power up, the IP parameters
may be set by a PC on the local LAN using a proprietary broadcast UDP
protocol. Comrex provides the Device Manager application to perform this
function on the local PC. After five minutes of operation, this function is
disabled.
Firmware updates to the device are installed using the
Device Manager
utility software. This update process is password protected and done via
XML over TCP port 8080. In addition to the password protection, the
update data itself must have a valid cryptographic signature from Comrex,
or else it is rejected. In order for the unit to be remotely updated, TCP port
8080 must be forwarded to the device. Alternately, updates can be initiated
from any local PC using the
Device Manager
application.
In its most commonly used mode, the ACCESS codec delivers an RTP/
UDP stream from source port 9000 to destination port 9000 by default. By
default it listens for incoming RTP/UDP streams on port 9000. To use the
default mode, only UDP 9000 needs to be forwarded to the device.
Alternately, the device can be configured to deliver a similar TCP-based
stream on TCP port 9000. By default, the device listens for incoming TCP
streams on TCP 9000. This function may be disabled. The source port of
TCP streams is ephemeral, and, if an incoming stream is detected, one will
be returned to the ephemeral port.
The device also supports transmitting and receiving UDP multicast streams,
using UDP port 9002 unless another port is specified by the user. This is
not enabled by default, and a configuration must be explicitly created and
connected on both ends for this function. Multicast streams are inherently
unidirectional, and the configured port must be forwarded to the device
on the receiving end. The multicast TTL value defaults to 1 (for in-network
multicasting), but may be changed to any valid TTL by the user.