04.11.2014 Views

Definity ECS Admin for Network Connectivity.pdf - TextFiles.com

Definity ECS Admin for Network Connectivity.pdf - TextFiles.com

Definity ECS Admin for Network Connectivity.pdf - TextFiles.com

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Configuration 4: R8csi R8si Gateway<br />

R8csi<br />

3 C-LAN <strong>Admin</strong>istration<br />

Field<br />

Destination<br />

Node<br />

Destination<br />

Port<br />

Session -<br />

Local<br />

Session -<br />

Remote<br />

Mach ID<br />

Conditions/Comments<br />

Name of the far-end node <strong>for</strong> this channel. This must be a name<br />

entered on the Node Names screen. For ppp connections, it must<br />

match the Destination Node Name entered on the ppp Data<br />

Module screen.<br />

A value of 0 allows any available interface channel on the<br />

destination node to be used <strong>for</strong> this connection. The Interface<br />

Channel number <strong>for</strong> this connection on the Switch-3 Processor<br />

Channel screen must also be set to 0.<br />

The Local and Remote Session numbers can be any value<br />

between 1 and 256 (si model) or 384 (r model), but they must be<br />

consistent between endpoints. For each connection, the Local<br />

Session number on this switch must equal the Remote Session<br />

number on the remote switch and vice versa.<br />

It is allowed, and sometimes convenient, to use the same number<br />

<strong>for</strong> the Local and Remote Session numbers. It is allowed, but not<br />

re<strong>com</strong>mended, to use the same Session numbers <strong>for</strong> two or more<br />

connections.<br />

Destination switch ID identified on the dial plan of the<br />

destination switch.<br />

Processor Channel 14: (Gateway between Switch 2 and Switch 3)<br />

Enable Set to y.<br />

Appl. Set to gateway <strong>for</strong> conversion between ISDN and TCP/IP.<br />

Mode Node-1 is the “server” <strong>for</strong> this session. Set node-3 to “client”<br />

(c).<br />

Interface Link This must match the link number assigned on the node- 1 data<br />

module screen.<br />

Interface Chan For TCP/IP, interface channel numbers are in the range 5000 –<br />

64500.<br />

The re<strong>com</strong>mended values are: 5001 <strong>for</strong> CMS, 5002 <strong>for</strong> Intuity<br />

AUDIX, and 5003 <strong>for</strong> DCS connections that are not gateways.<br />

These three values should be reused <strong>for</strong> multiple instances of<br />

these applications; <strong>for</strong> example, if there are two Intuity<br />

AUDIX’s, use 5002 <strong>for</strong> both; or if there are four DEFINITY<br />

<strong>ECS</strong>’s, use 5003 <strong>for</strong> all four. The <strong>com</strong>bination of Link, Interface<br />

Channel, and Mach ID must be unique.<br />

The re<strong>com</strong>mended values <strong>for</strong> gateway switches is 6001–6099.<br />

The interface channel number must be unique <strong>for</strong> each gateway.<br />

This number must match the Destination Port number on the<br />

node-3 Processor Channel screen.<br />

2 of 3<br />

130<br />

<strong>Admin</strong>istration <strong>for</strong> <strong>Network</strong> <strong>Connectivity</strong><br />

CID: 77730 555-233-504 — Issue 1 — April 2000

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!