Installation guide

Remote Connection to the SignalPath Device 1-17
SP201-SA™ Customization and Maintenance Guide
Figure 1-4. Full Path for Remote Access to a SignalPath Device
1.6.2.1 Connection between the SignalPath and the Local Terminal
The local terminal (e.g., a PC) must have a direct connection to the
SignalPath device. Connect the local terminal’s COM1 port to the RJ45
Supervisory port on the front of the SP201-SA chassis.
Start a terminal-emulation program (e.g., HyperTerminal). Use the
following settings for communication between the local terminal and the
SignalPath device:
1.6.2.2 Connection between the Local Terminal and the Remote Terminal
In the connection between the terminals, the SignalPath’s local terminal is a
host or a client (depending on the application), and the remote terminal is a
client. The unit connected to the SignalPath device must be on line and
available when a remote connection is desired. (In the following procedures,
the local terminal is called the host and the remote terminal is called the
client.)
There are several connection protocols for remote access. However, most
connections travel across an IP network. Encore Networks, Inc.,
recommends using TCP/IP for the connection between the local and remote
terminals.
Note: The connection can take place between terminals using the same or
different operating systems. Some remote-access products are available in
each of the operating systems Unix, Macintosh, and Windows. The
examples given are for a workstation (terminal) using the Windows
operating system.
•9600 bps •No parity •No flow control
• 8 data bits • 1 stop bit