Processor Channel Assignment

Last Updated : Oct 29, 2012 |

Assigns each local processor channel to an interface link channel, and defines the information associated with each processor channel on an Ethernet link.

Note:

You cannot remove a service from this screen if that service has overrides defined on the Survivable Processor screen.

Example command: change communication-interface processor-channels

Appl

Specifies the server application type or adjunct connection used on this channel.

Valid Entry

Usage

audix

Voice Messaging.

ccr

Contact Center Reporting, now known as Avaya IQ.

dcs

Distributed Communication System.

fp-mwi

ISDN Feature Plus Message Waiting Indication. This channel passes message waiting light information for subscribers on the messaging system, from a messaging adjunct on a main switch for a telephone on a satellite switch. The terminating location (far end) of this channel must be a Communication Manager system compatible with ISDN Feature Plus proprietary protocol.

gateway

Supports an X.25 connected AUDIX connected to an ISDN DCS network.

gateway-tcp

Supports a TCP-connected voice messaging system connected to an ISDN DCS network.

mis

Management Information System, otherwise known as the Call Management System.

qsig-mwi

QSIG Message Waiting Indication. Used with a QSIG-based interface to a messaging system, this channel passes message waiting light information for subscribers on the messaging system.

Destination Node

Identifies the server or adjunct at the far end of this link. The destination node can be an adjunct name, server name, far end IP address, or node name for services local to the Avaya server. For ppp connections, match the Destination Node Name administered for the ppp data module.

Destination Port

Valid Entry

Usage

5000 to 64500

The number of the destination port.

0

Any port can be used.

Enable

Enables or disables this processor channel on the main server.

Gtwy to

A number that identifies the processor channel to which the specified processor channel is serving as a gateway.

Interface Channel

The channel number or the TCP/IP listen port channel to carry this processor (virtual) channel.

Valid Entry

Usage

5000 to 64500

For ethernet or ppp. For TCP/IP, interface channel numbers are in the range 5000 to 64500. The value 5001 is recommended for CMS, and 5003 is recommended for DCS.

0

Any port can be used.

Interface Link

Valid Entry

Usage

1 to 254

The physical link carrying this processor (virtual) channel.

pv4 or pv6

Communication Manager’s Processor Ethernet interface used for adjunct connectivity.

blank

Not administered.

Mach ID

Valid Entry

Usage

1 to 63 for MWI

1 to 63 for DCS

1 to 99 for voice messaging

blank

The destination server ID defined on the dial plan of the destination server.

Mode

Valid Entry

Usage

c(lient)

s(erver)

blank

Indicates whether the IP session is passive (client) or active (server).

This field must be blank if the interface link is procr-intf. This field cannot be blank if the type of interface link is ethernet or ppp.

Proc Chan

The number assigned to each processor channel.

Session - Local/Remote

Valid Entry

Usage

1 to 384

blank

The Local and Remote Session numbers. For each connection, the Local Session number on the Avaya server must equal the Remote Session number on the remote server and vice versa. It is allowed, and sometimes convenient, to use the same number for the Local and Remote Session numbers for two or more connections. Local and Remote Session numbers must be consistent between endpoints.
Related information
Mach ID