Avaya Communication Manager Administrator's Manual page 1007

Directory Number
These 10-digit fields contain the directory numbers assigned to the interface, which it views as being
allocated to 2 separate endpoints.
Valid entries
Any string of 1
to 10 digits
Endpt ID
A 2-digit field containing the Endpoint Identifier expected by the far end. Avaya Communication
Manager blocks you from changing this field unless the port is busied out or unadministered.
Valid entries
00 to 62
Endpt Init
Indicates whether the far end supports endpoint initialization. Avaya Communication Manager blocks
you from changing this field unless the port is busied out or unadministered.
Valid entries
y
n
Interworking Message
This field determines what message Communication Manager sends when an incoming ISDN trunk call
interworks (is routed over a non-ISDN trunk group).
Valid entries
PROGress
ALERTing
Administrator's Guide for Avaya Communication Manager
November 2003
Usage
These fields must be administered in pairs. That is, if you enter a
value in one field, you must enter a value in the other.
Usage
Leading zeroes considered significant and not ignored.
Usage
If set to y, the SPID field must not be blank. Avaya
Communication Manager blocks you from changing this field and
the SPID field unless that port is busied out or unadministered.
If set to n, the SPID and Endpt ID fields must be blank.
Usage
Normally select this value. PROGress asks the public network to
cut through the B-channel and let the caller hear tones such as
ringback or busy tone provided over the non-ISDN trunk.
ALERTing causes the public network in many countries to play
ringback tone to the caller. Select this value only if the DS1 is
connected to the public network, and it is determined that callers
hear silence (rather than ringback or busy tone) when a call
incoming over the DS1 interworks to a non-ISDN trunk.
Screen Reference
ISDN-BRI Trunk Circuit Pack
1007