Nortel Meridian Meridian 1 Feature Description And Administration page 226

International isdn primary rate interface
Hide thumbs Also See for Meridian Meridian 1:
Table of Contents

Advertisement

Page 226 of 1814
553-2901-301 Standard 9.00 January 2002
Australia ETSI
If no digits are configured for either of the prefixes, then that part of the
number will not be included in the Calling Party Number. Essentially, this
meant that the CLID could only be built from key 0 of a set. Regardless of
what key was used to make a call, it was the CLID for key 0 that was sent.
Also, only one office code and one location code could have been assigned in
the CLID for a customer.
With the introduction of the ISDN CLID Enhancements feature, PFX1 and
PFX2 are no longer used to construct the CLID. CLID is now table-driven
(when Overlay 15 is loaded, a customer can configure a CLID table), and
virtually any of the information contained in the fields of the CLID table can
now be programmed against any DN or DN key, on a per set basis.
This means that the CLID that is sent from a set is now predicated on what is
in the CLID table, rather than the LDN or PDN. That is, a CLID for any key
is now built by taking the information contained in a particular field in the
CLID table and adding that information to the key's DN. A multi-line set can
now have DN keys that each has their own CLID. Or, the CLID of any one
key on a set could be programmed to use the CLID of any other key on the set.
The construction of CLID is based on the CPFXS prompt in Overlay 16. If
CPFXS = NO, then when constructing the Calling Number, the prefixes are
retrieved from the Route Data Block via the responses to the HNTN and
HLCL prompts. If CPFXS = YES, which is the default response, then CLID
is built depending upon the prefixes HNTN and HLCL retrieved from the
Customer Data Block (Overlay 15) via the entries in the CLID table (refer to
the paragraph above for more details).
Also, the Meridian 1 can now support multiple office codes, location codes
and steering codes in CLID. This means that any telephone set on one
Meridian 1 can send a CLID that will have calls returned to another
Meridian 1. This type of configuration is typically used in cases where a
customer wants calls to be returned to only one central location.
How a CLID table is built
Prompts have been added to Overlay 15 that create a CLID table for a
customer. This table contains up to 4,000 CLID "entries." Each entry contains
unique information pertaining to CLID, as explained in the following
sections.

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Meridian 1Succession cse 1000

Table of Contents