Name Display for DNIS displays both the DNIS number and name for IDC DNIS calls terminating on telephones equipped with a display.
An option (DNAM) is provided at the route level for IDC routes to allow the display of the IDC name. This supersedes the display of the route name.
All telephones with display and class of service Automatic Digit Display (ADD) and Called Party Name Display Allowed (CNDA) support Name Display for DNIS.
These telephones include: M 2 3 1 7
M 3 0 0 0
Meridian Modular Terminals (M2008, M2616, M2216 ACD-1 and M2216 ACD-2)
Attendant consoles (Ml250 and M2250)
Name Display for DNIS requires the following packages: CPND (package 95)
DNIS (package 98)
IDC (package which requires NFCR (package 49) and NCOS (package 32)
Prompts in the CPND data block and in the Route data block (LD16) allow a name to be defined for an IDC number belonging to a particular conversion table. For a description of all the prompts and responses, refer to
inputloutput guide (553-3001-400).
Feature interactions
With release 18 and later, DNIS Across Call Modifications preserves the DNIS information across certain call modifications and enhances DNIS operation and functionality. Refer to the DNIS Across Call Modifications section. Some of the following feature interactions may not apply with release 18 and later releases.
When the following functions are activated, the DNIS on the telephone display screen disappears, and redisplays when the function is deactivated.
Call on Hold Call Consultation
Calling Party Number key Charge key
The feature interactions for Name Display for DNIS are the same as those for the except for the differences defined below.
ACD Interflow For ACD Interflow conditions, the DNIS number and name
appears on the display when the IFDN is internal.
ACD Night Call Forward During night service conditions, the DNIS number
and name is displayed.
ACD Overflow If the DNIS call overflows to the target agent, the DNIS name
is displayed with the source DN.
Conference Calls If the conference key is used during the DNIS call, the
display is cleared during the conference operation. When the call is restored to the original two-party call, the new display does not show the DNIS number and name. Instead, the display shows the name associated with the route.
Application Module Link (AML) DNIS Name Display provides the ACD
DN, DNIS number, and position ID in the message for the Meridian link. The DNIS name is not provided.
Network ACD (NACD) DNIS Name Display is provided for ACD agents
within the same switch and for network ACD.
Calling Line Identification (CLID) If a DNIS call comes from an ISDN
network, the DNIS name replaces the CLID name. Additionally, the DNIS number and name are displayed on an attendant console after the CLID.
Operating parameters
Name Display for DNIS does not apply to auto-terminated calls.
An IDC name can only be associated with an IDC number explicitly specified for IDC translation in LD49. Partial conversions apply according to the guidelines below.
partial IDC conversion to a full DN, only one IDC name can be defined for the entire range of represented by the partial IDC number (for example to 5006)
partial conversion to partial DN when the DN is a valid ACD DN
For instance, if 33 to 5006 is specified, only one ID name can be associated with 33; 3300 to 3399 cannot be individually given a name unless explicitly specified as an IDC conversion. The IDC does not support the asterisk (*) or telephone as valid digits to translate.
With DNIS Name enabled (DNAM = YES), the DNIS name overrides all other names, including:
Calling Party Name or Redirected Party Name Route name
Calling Line Identification (CLID) name
Routing by
number (Advanced)
Routing by DNIS number enhances call distribution within an ACD system. This enhancement allows calls to be routed to a specific ACD DN, based on
the DNIS number, instead of auto-terminating as described in the DNIS section.
With Incoming Digit Conversion (IDC) as shown in Figure 6, a set of DID numbers can be matched to existing internal numbering plans. Incoming Digit Conversion (IDC) also allows the conversion of several different DID numbers to a single ACD DN. Complete or partial DNIS numbers can be defined in the IDC translation table using LD49. Refer to Xl input/output
guide (553-3001-400) for a complete list of prompts and responses.
When the digits received are not in the IDC translation table but are valid for an ACD the digits are passed without changes to the system. The IDC conversion is used only when needed. Invalid calls are routed to the attendant. Figure shows how incoming DNIS numbers are handled by the Meridian system.
Figure
Incoming Digit Conversion
Central Office (CO) Meridian
Feature interactions
The feature interactions for routing by DNIS are the same as those for the except for the differences defined below:
Digit insertion Digit insertion for DNIS routes is not allowed.
New Flexible Code Restrictions When enabling IDC in you must
respond Yes to both NFCR and IDCA. When not using New Flexible Code Restrictions (NFCR), respond No to the NFCR prompt.
Outpulsing the asterisk and octothorpe Calls with an asterisk (*) or
octothorpe in the DNIS route are sent to the attendant.
Operating parameters
Feature assumptions and feature requirements for routing by DNIS are the same as those for the DNIS, except as listed below.
In addition to the packaging requirements for Routing by DNIS requires Incoming Digit Conversion (IDC) (package 113).