Switch administration for ISDN
Following are a group of guidelines to direct the configuration of ISDN on a network switch connected to an Avaya IR system already configured for ISDN. These are general guidelines and do not pertain to any particular network switch.
Configuration of ISDN where trunks are attached to an NMS card and each trunk contains its own D-channel
In this case, there is no NFAS (non-facility associated signaling) involved:
- Trunk interface identifiers or NAI (network access identifier) values are assigned the value of the trunk (for example: trunk 0 has NAI or interface identifier of 0, trunk 1 has NAI or interface identifier of 1, and so on).
- The network switch should be configured so that level 3 packets between the Avaya IR system and the network switch which contain a Channel Identification IE have the Interface Identifier Present field set to Interface Implicitly Identified.
- Should the switch not allow implicit interface identification, the Interface Identifier field of the Channel Identification IE should be set to the number of the trunk over which the packet travels. From the network switch, this may be �fixing the interface number� to a specific value.
Configuration of ISDN where trunks are attached to an NMS card and one trunk contains the D-channel
In this case, there is NFAS:
- The NFAS group number must be set and matched up on both the network switch and the Avaya IR system.
- The first trunk to the Avaya IR system must contain the D-channel. The second trunk to the Avaya IR system should be included in the NFAS group and contain only B-channels.
- An NFAS group cannot span multiple NMS cards, so verify that the network switch is set up accordingly.
- The first trunk's NAI value is 0, and the second trunk's NAI is 1. The network switch must match these values.
