Dn Discovery - Nortel RLC Installation And Administration Manual

June 2005
If the party on the PBX side hears echo during conversations, adjust the settings,
as follows:
RLC: NLP Enabled - More Aggressive
9150: NLP Enabled - More Aggressive
The NLP does not have to operate aggressively if echo is not present. If echo is
not present but double-talk is present, even with Less Aggressive settings, try
disabling the NLP on the RLC.

DN Discovery

Through DN Discovery, the RLC detects the PBX-configured name and number
assigned to all line keys in its portion of the remote network.
Some of the characteristics of DN Discovery are:
DN Discovery overrides the DN configuration for Local Call keys.
Local SwitchOver and Bridge Ports require DN Discovery.
The Remote Gateway 9150 unit also uses the discovered DNs to determine
when it can switch calls locally.
MADN appearances of the DN Discovery port ring periodically during DN
Discovery.To avoid this, do not start DN Discovery more frequently than
once per half-hour and add a unique SCR key for DN Discovery.
If Make Set Busy is active, DN Discovery fails and results in blank DN
displays on M39xx sets. To avoid this, do not activate Make Set Busy for
the port designated for DN Discovery.
For DN Discovery to work using key 0 on the target port, no special Class
of Service (CLS) is required. If the target key is key 1 or higher, TDD CLS
is required.
The target key must be a Single Call Ringing (SCR) or Multiple Call
Ringing (MCR) key - not an ACD key.
DN Discovery configures the DNs for the local call keys based upon the first
line key DN discovered in the PBX configuration of the RLC port. Therefore,
the first line key DN must be unique on all sets.
RLC Installation and Administration Guide
Configuring the RLC
171