Filter
Top Products
Configuration 5A: R8csi <—ppp—> R8r (one C-LAN)
<—ethernet—> R8si
169
Administration for Network Connectivity
555-233-504 — Issue 1 — April 2000 CID: 77730
3 C-LAN Administration
> Submit the screen
End
Session - Local The Local and Remote Session numbers can be any value
between 1 and 256 (si model) or 384 (r model), but they must be
consistent between endpoints. For each connection, the Local
Session number on this switch must equal the Remote Session
number on the remote switch and vice versa.
It is allowed, and sometimes convenient, to use the same
number for the Local and Remote Session numbers. It is
allowed, but not recommended, to use the same Session
numbers for two or more connections.
Session -
Remote
Mach ID Destination switch ID identified on the dial plan of the
destination switch.
For Processor Channel 32: (connection to Switch 2 through Switch 1)
Enable Set to y.
Appl. Set to dcs for DCS signaling.
Mode Node-3 is the “server.” Set node-2 to “client” (c).
Interface Link This must match the link number assigned on the node-3 data
module screen.
Interface Chan This must match the Destination Port number on the Switch-1
Processor Channels screen.
Destination
Node
Name of the far-end node for this channel. This must be a name
entered on the Node Names screen.
Destination
Port
or TCP/IP, interface channel numbers are in the range 5000 –
64500.
The recommended values are: 5001 for CMS, 5002 for Intuity
AUDIX, and 5003 for DCS connections that are not gateways.
These three values should be reused for multiple instances of
these applications. The combination of Link, Interface Channel,
and Mach ID must be unique.
This number must match the Destination Port number on the
Switch-2 Processor Channel screen.
Session - Local
For each connection, the Local Session number on this switch
must equal the Remote Session number on the remote switch
and vice versa.
Session -
Remote
Mach ID Destination switch ID identified on the dial plan of the
destination switch.
Field Conditions/Comments
2 of 2