Download Print this page

Nortel Meridian Meridian 1 Feature Description And Administration

International isdn primary rate interface

Hide thumbs Also See for Meridian Meridian 1:

Scripting manual (812 pages)

,

Maintenance manual (504 pages)

,

Upgrade manual (286 pages)

page of 1816

/ 1816
Contents
Table of Contents
Bookmarks

Table of Contents

Advertisement

Quick Links

See also: Maintenance Manual

Meridian 1 and Succession Communication Server for Enterprise 1000

International ISDN Primary Rate Interface

Feature description and administration

Document Number: 553-2901-301

Document Release: Standard 9.00

Date: January 2002

Year Publish FCC TM

Copyright © 1991–2002 Nortel Networks

All Rights Reserved

Printed in Canada

Information is subject to change without notice. Nortel Networks reserves the right to make changes in design

or components as progress in engineering and manufacturing may warrant. This equipment has been tested

and found to comply with the limits for a Class A digital device pursuant to Part 15 of the FCC rules, and the

radio interference regulations of the Industry Canada. These limits are designed to provide reasonable

protection against harmful interference when the equipment is operated in a commercial environment. This

equipment generates, uses and can radiate radio frequency energy, and if not installed and used in accordance

with the instruction manual, may cause harmful interference to radio communications. Operation of this

equipment in a residential area is likely to cause harmful interference in which case users will be required to

correct the interference at their own expense.

SL-1, Meridian 1, and Succession are trademarks of Nortel Networks.

Table of Contents

Advertisement

Chapters

Table of Contents

Need help?

Need help?

Do you have a question about the Meridian Meridian 1 and is the answer not in the manual?

Questions and answers

Summary of Contents for Nortel Meridian Meridian 1

Page 1 All Rights Reserved Printed in Canada Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components as progress in engineering and manufacturing may warrant. This equipment has been tested and found to comply with the limits for a Class A digital device pursuant to Part 15 of the FCC rules, and the radio interference regulations of the Industry Canada.
Page 3: Revision History
Page 3 of 1814 Revision history January 2002 Standard 9.00. This document is up-issued to include content changes for Meridian 1 Release 25.40 and Succession Communication Server for Enterprise 1000 Release 1.1. April 2000 Standard 8.00. This is a global document and is up-issued for X11 Release 25.0x.
Page 4 Page 4 of 1814 Revision history document has been changed to International ISDN PRI Feature description and administration. December 1995 Issue 3.00 released as Standard for Generic X11 Release 21.1x. July 1995 Issue 2.00 released as Standard for Generic X11 Release 21.0x. July 1994 Issue 1.00 released as Standard for Generic X11 Release 20.00 July 1993...
Page 5: Table Of Contents
Page 5 of 1814 Contents Revision history ......About this document ..... . ISDN product overview .
Page 6 Page 6 of 1814 Contents Basic Call Service ......B-channel Overload Control ....Break-in Features .
Page 7 Contents Page 7 of 1814 Calling Line Identification in CDR ... . CLID on Analog Trunks for Hong Kong (A-CLID) ....... . . Calling Party Privacy .
Page 8 Page 8 of 1814 Contents Emergency Services Access ....Equi-distribution Routing Network Attendant Service ......Error Handling on ISDN Signaling Link Analog E&M TIE Trunks .
Page 9 Contents Page 9 of 1814 ISDN QSIG-BC and QSIG-GF Compliance Update ........ISDN QSIG Call Diversion Notification .
Page 10 Page 10 of 1814 Contents MCDN End to End Transparency ... . 1203 Meridian Hospitality Voice Services ..1233 Meridian Mail Trunk Access Restriction ..1241 Message Waiting Indication Interworking with DMS .
Page 11 Contents Page 11 of 1814 Network Intercom (Hot Type D and Hot Type I Enhancements) ....1361 Network Message Services ....1371 Network Ring Again .
Page 12 Page 12 of 1814 Contents Recorded Announcement for Calls Diverted to External Trunks ......1539 Reference Clock Switching ....1543 Remote Virtual Queuing .
Page 13: About This Document
This document is a global document. Contact your system supplier or your Nortel Networks representative to verify that the hardware and software described is supported in your area. International ISDN PRI Feature description and administration...
Page 14: Standard 9.00 January
Page 14 of 1814 About this document 553-2901-301 Standard 9.00 January 2002...
Page 15: Regional Material Statement
Backup D-channel ........Regional material statement The information presented in this section does not pertain to all market regions. Contact your system supplier or your Nortel Networks representative to verify support of this product in your area. Integrated Services Digital Network Integrated Services Digital Network (ISDN) is a recommended standard for digital communications.
Page 16: Isdn Product Overview
Page 16 of 1814 ISDN product overview ISDN services are categorized into two types of interfaces, Primary Rate and Basic Rate. ISDN Primary Rate Interface (PRI), provides 23B+D (T-1 carriers) or 30B+D (E-1 carriers) digital connectivity between the Meridian 1 or Succession Communication Server for Enterprise 1000 and the following interfaces: •...
Page 17 ISDN product overview Page 17 of 1814 These protocols are based on a model containing seven layers of protocol developed by the International Standards Organization (ISO). This seven-layer model, called the Open Systems Interconnection model, has been adopted by the International Telegraph and Telephony Consultative Committee (CCITT).
Page 18: Isdn Primary Rate Interface
Page 18 of 1814 ISDN product overview • a non-call-associated supplementary service to handle TCAP remote operation • a call-associated supplementary service to handle ROSE remote operation Note: ROSE messaging is supported for call-associated messages; TCAP messaging is supported for non-call-associated messages. ISDN Primary Rate Interface ISDN PRI provides the interface between a customer's equipment and the public and private network, and allows basic call services and network...
Page 19: Isdn Signaling Link Interface
To determine the constraints in your market, consult your local Nortel Networks representative. Also note that the maximum number “n” in nB+D configurations is subject to trunk route limitations.
Page 20 Page 20 of 1814 ISDN product overview The ISL interface is structured as a collection of analogue and/or digital trunks, and can operate under two basic modes of operation: shared and dedicated. Shared mode requires a PRI (either 30B+D, or nB+D) between originating and terminating switches.
Page 21: Backup D-Channel
ISDN product overview Page 21 of 1814 When a D-channel with backup re-establishes • there is no impact. The primary D-channel simply recovers. ISL calls, still using D-channel signaling (in existing software), can bypass the restart procedure. When a D-channel without backup re-establishes •...
Page 22 Page 22 of 1814 ISDN product overview 553-2901-301 Standard 9.00 January 2002...
Page 23: Connection Parameters For 2.0 Mb Pri
Page 23 of 1814 Connection parameters Contents The following are the topics in this section: Connection parameters for 2.0 Mb PRI ......Frame formats .
Page 24: Connection Parameters
Page 24 of 1814 Connection parameters — HDB3 coding, a modified form of Alternate Mark Inversion (AMI), for zero code suppression Note: (Line coding is bipolar for 2Mb/s line transmission.) • Error detection on the 2.0 Mb data stream consists of: —...
Page 25 Connection parameters Page 25 of 1814 • Si bit: The Si bit is always 1 in transmission, and is ignored in reception. • A bit: This bit is used for Remote Alarm Indication (RAI). Table 1 Alternate frame formats Bit number Alternate frame Even frame Odd frame...
Page 26 Page 26 of 1814 Connection parameters Table 2 CRC 4 Multiframe Format table (Part 2 of 2) Sa 4 Sa 5 Sa 6 Sa 7 Sa 8 Sa 4 Sa 5 Sa 6 Sa 7 Sa 8 Sa 4 Sa 5 Sa 6 Sa 7 Sa 8...
Page 27: Line Encoding
Connection parameters Page 27 of 1814 Line encoding Line coding for CEPT is bipolar. A modified form of Alternate Mark Inversion (AMI) is used, and is called High Density Bipolar 3 (HDB3) coding (see below). The general requirements for CEPT code suppression is a maximum of 3 consecutive zero binary bits.
Page 28 Page 28 of 1814 Connection parameters Channel restoration When the PRI stops receiving the remote alarm, the 30 B channels are placed into the idle state and made available for calls. Each time a remote alarm is generated, a counter is incremented. Remote alarm is cleared immediately upon the reception of a cleared message from the card.
Page 29 Connection parameters Page 29 of 1814 Cyclic redundancy check (CRC) The CRC 4 Multiframe Frame format contains a checksum of all the data in the frame. The receiving side uses the checksum to verify that the data is error free. The primary functional difference between BPV and CRC is that BPV indicates physical errors limited to the local span, while CRC indicates errors on an end-to-end span.
Page 30 Page 30 of 1814 Connection parameters MAINTNONEWCALL UNAVAIL SEVERE TOTAL 24HR BPV- xxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxx TOTAL 24HR CRC- xxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxx TOTAL 24HR FAP- xxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxx TOTAL 24HR SLPREP- xxxxxxxxx TOTAL 24HR SLPDEL- xxxxxxxxx TOTAL 24 HOUR G2 AIS - xxxxxxxxx TOTAL 24 HOUR G2 LFAS - xxxxxxxxx TOTAL 24 HOUR G2 LMAS - xxxxxxxxx TOTAL 24 HOUR G2 RAI - xxxxxxxxx TOTAL 24 HOUR G2 LOS - xxxxxxxxx...
Page 31: Channel Parameters
Connection parameters Page 31 of 1814 Frame slip Digital signals must have accurate clock synchronization for data to be interleaved into or extracted from the appropriate timeslot during multiplexing and demultiplexing operations. Frame-slip monitoring detects frame-deletion and repetition errors in clock synchronization. Clock synchronization can track on either a primary or a secondary reference clock, or it can operate in free-run (non-tracking) mode.
Page 32: Connection Parameters For 1.5 Mb Pri
Page 32 of 1814 Connection parameters Outgoing trunk hunting on B-channels should be set for the round-robin searching method, rather than the linear method. This way, when the switch is looking for an outgoing idle trunk, it will look for the next lower available trunk member, rather than the last member that was used.
Page 33: Frame Formats
Connection parameters Page 33 of 1814 — Superframe format — Extended superframe format • Line encoding — B7 coding — B8ZS coding • Error detection — Yellow alarm (remote alarm) — Bit error rate — Frame alignment — Frame slip •...
Page 34 Page 34 of 1814 Connection parameters Superframe format A superframe format, the standard format, consists of 12 DS-1 frames (see Table 3). It is consistent with the channel bank formats D2, D3, and D4. The signaling bit is time-shared to identify both the channel and the signaling frame.
Page 35 Connection parameters Page 35 of 1814 Extended superframe format The Extended superframe format (ESF) consists of 24 frames. The 8 kbps F-bit channel is divided into three separate channels. Framing Pattern Sequence (FPS) Beginning with frame 4 or ESF bit 579, the framing bit of every fourth frame forms FPS 001011, which is used to determine the mainframe, superframe, and robbed bit signaling synchronization.
Page 36 Page 36 of 1814 Connection parameters Table 4 Extended superframe format table (Part 2 of 2) F-Bit Frame Robbed bit Assignments number signaling Bit number 1158 — — 1351 — — 1544 — — 1737 — — 1930 — — 2123 —...
Page 37: Line Encoding
Connection parameters Page 37 of 1814 Line encoding Line coding for DS-1 is bipolar, Alternate Mark Inversion (AMI). The general requirements for DS-1 code suppression are: • a maximum of 15 consecutive zero binary bits • a minimum average of 12.5 percent density of one binary bit over any 192 consecutive bits To meet the maximum and minimum requirements, PRI provides B7 and B8ZS zero code substitution techniques as options.
Page 38: Error Detection
Page 38 of 1814 Connection parameters Error detection This section describes the ISDN error detection. There are four types of error detection: • yellow (remote) alarm • bit error rate • frame alignment • frame slip Yellow alarm (remote alarm) A yellow alarm signal (received by the near end) indicates that the far end (the remote end) is not ready.
Page 39 Connection parameters Page 39 of 1814 Bit error rate Bit error rate monitoring detects errors in transmission. There are two methods of bit error rate monitoring: bipolar violation tracking and cyclic redundancy check (CRC). If the D2, D3, or D4 framing format is selected in LD 17, prompt DLOP, bipolar violation tracking is implemented.
Page 40 Page 40 of 1814 Connection parameters There are three bit error rate thresholds set in LD 73. Setting BIPC to zero enables automatic recovery. BIPV 1–(3)–4 maintenance threshold 1–(2)–4 out-of-service threshold BIPC 0–(2)–128 maximum number of times a DTI/PRI loop can be taken out of service in 24 hours Note: The BIPV values determine the sensitivity of the loop to errors, where BIPV = 1 is the least tolerant to errors, and BIPV = 4 is the most...
Page 41 Connection parameters Page 41 of 1814 Clock synchronization can either track on a primary or secondary reference clock, or operate in free run (nontracking) mode. In LD 73 (prompts PREF and SREF), one PRI can be defined as the primary clock reference. Another can be defined as the secondary clock reference.
Page 42: Data Rate Parameters
Page 42 of 1814 Connection parameters Free run (nontracking) mode PRI hardware detects frame slips in the free run mode. Running the midnight routines prints the number of frame deletions and repetitions and clears the counters. Data rate parameters ISDN uses three types of data rates 56 kbps inverted, 64 kbps clear, and 64 kbps restricted.
Page 43: Interface Protocols
Connection parameters Page 43 of 1814 Set outgoing trunk hunting on B-channels for the round robin searching method, rather than the linear method. Thus, when the system looks for an outgoing idle trunk, it looks for the next lower available trunk member, rather than the last member that was used.
Page 44 Page 44 of 1814 Connection parameters Symmetric The interface protocol between a Meridian 1 or Succession CSE 1000 and another Meridian 1 or Succession CSE 1000 is a symmetric protocol. Call processing uses a master-slave relationship for glare resolution. One PBX must be designated as the network (master), the other as the user (slave) (in LD 17).
Page 45: Meridian 1 Correlation Tables
Page 45 of 1814 Meridian 1 Correlation tables Contents The following are the topics in this section: Meridian 1-to-Meridian 1 correlation tables over 2.0 Mb PRI ..Meridian 1-to-Meridian 1 correlation tables over 1.5 Mb PRI ..Meridian 1-to-Meridian 1 correlation tables .
Page 46 Page 46 of 1814 Meridian 1 Correlation tables Table 5 PRI database correlation (protocol layer 1) — Overlay Prompts to be Matched (Part 2 of 2) BIPV Bit error rate maintenance threshold Bit error rate out-of-service threshold BIPC Bit error rate 24-hour threshold Frame alignment maintenance threshold Frame alignment out-of-service threshold Table 6...
Page 47 Meridian 1 Correlation tables Page 47 of 1814 Table 8 Database correlation — Prompt requiring different responses at each Meridian 1 Description Meridian 1 Meridian 1 USER-USER Overlay:17 Overlay:17 INTERFACE Prompt:SIDE Prompt:SIDE Response:MAS Response:SLAV Meridian 1-to-Meridian 1 correlation tables over 1.5 Mb PRI The correlation tables that follow are used to coordinate the software features between two switches, over 1.5 Mb ISDN PRI.
Page 48 Page 48 of 1814 Meridian 1 Correlation tables The following tables are provided for Meridian 1 to Meridian 1: — Table 9 PRI database correlation (protocol layer 1) — Table 10 DCH database correlation (protocol layer 2) — Table 11 Facility database correlation (protocol layer 3) The following tables are provided for Meridian 1 to DMS-100: —...
Page 49 Meridian 1 Correlation tables Page 49 of 1814 Meridian 1-to-DMS-100 correlation tables Table 12 through Table 14 describe how to coordinate the software features between a Meridian 1 switch and a DMS-100 switch. The tables consist of three columns. The description column lists the software feature to be coordinated.
Page 50 Page 50 of 1814 Meridian 1 Correlation tables Table 9 PRI database correlation (protocol layer 1) for Meridian 1 to Meridian 1 (Part 1 of 2) Description Meridian 1 Meridian 1 CARD TYPE Program: LD 17 Program: LD 17 Prompt: MODE Prompt: MODE...
Page 51 Meridian 1 Correlation tables Page 51 of 1814 Table 9 PRI database correlation (protocol layer 1) for Meridian 1 to Meridian 1 (Part 2 of 2) Description Meridian 1 Meridian 1 DATA LINK (yellow alarm Program: LD 17 Program: LD 17 method) Prompt: YALM...
Page 52 Page 52 of 1814 Meridian 1 Correlation tables Table 10 DCH database correlation (protocol layer 2) for Meridian 1 to Meridian 1 Description Meridian 1 Meridian 1 Associate D-channel with Program: LD 17 Program: LD 17 Prompt and Response: Prompt and Response: ADAN DCH xx ADAN...
Page 53 Meridian 1 Correlation tables Page 53 of 1814 Table 11 Facility database correlation (protocol layer 3) for Meridian 1 to Meridian 1 Description Meridian 1 Meridian 1 B-channel selection Program: LD 16 Program: LD 16 Prompt: SRCH Prompt: SRCH Response: RRB Response: RRB Loss and level preset...
Page 54 Page 54 of 1814 Meridian 1 Correlation tables Table 12 PRI database correlation (protocol layer 1) for Meridian 1 to DMS-100 (Part 1 of 2) Description Meridian 1 DMS-100 Card type Program: LD 17 Table: CARRMTC Prompt: MODE Field: CARD Response: PRI Value: NT6X50AA...
Page 55 Meridian 1 Correlation tables Page 55 of 1814 Table 12 PRI database correlation (protocol layer 1) for Meridian 1 to DMS-100 (Part 2 of 2) Description Meridian 1 DMS-100 Bit error rate 24-hour Program: LD 73 Table: CARRMTC threshold (errored second Prompt: BIPC Field:...
Page 56 Page 56 of 1814 Meridian 1 Correlation tables Table 13 DCH database correlation (protocol layer 2) for Meridian 1 to DMS-100 Description Meridian 1 DMS-100 Associate D-channel with PRI Program: LD 17 Table: TRKSGRP Prompt and Response: Field: DCHNL ADAN DCH xx Value: same as DS1...
Page 57 Meridian 1 Correlation tables Page 57 of 1814 Table 14 Facility database correlation (protocol layer 3) for Meridian 1 to DMS-100 Description Meridian 1 DMS-100 Q.931 Interface identifier Table: IACPSINV (used in CID IE) Field: Value: Q.931 Call Reference Value Table: TRKSGRP Length...
Page 58 Page 58 of 1814 Meridian 1 Correlation tables Each of the tables corresponds to one of three protocol layers. Table 15 PRI database correlation (protocol layer 1) for Meridian 1 to DMS-250 (Part 1 of 2) Description Meridian 1 DMS-250 Card type Program: LD 17...
Page 59 Meridian 1 Correlation tables Page 59 of 1814 Table 15 PRI database correlation (protocol layer 1) for Meridian 1 to DMS-250 (Part 2 of 2) Description Meridian 1 DMS-250 Bit error rate out of service Program: LD 73 Table: CARRMTC threshold Prompt: BIPV...
Page 60 Page 60 of 1814 Meridian 1 Correlation tables Table 16 DCH database correlation (protocol layer 2) for Meridian 1 to DMS-250 Description Meridian 1 DMS-250 Associated D-channel with Program: LD 17 Table: TRKSGRP Prompt and Response: Field: PMTYPE ADAN DCH xx Value: DTCI DCHL...
Page 61 Meridian 1 Correlation tables Page 61 of 1814 Table 17 Facility database correlation (protocol layer 3) for Meridian 1 to DMS-250 Description Meridian 1 DMS-250 Q.931 Interface identifier Table: LTCTSINV (used in CID IE) Field: PSLNKTAB Value: O/DSIPRA/ Default/N/Nil Q.931 Call Reference Value Table: TRKSGRP Length...
Page 62 Page 62 of 1814 Meridian 1 Correlation tables 553-2901-301 Standard 9.00 January 2002...
Page 63 Page 63 of 1814 Data administration Contents The following are the topics in this section: PRI implementation ........Task summary list .
Page 64 Page 64 of 1814 Data administration LD 73 - Set error detection thresholds and clock synchronization control. This configuration is required only when configuring PRI for the first time, and is optional for subsequent configurations. Prompt Response Description Create a PRI data block TYPE Digital data block PREF...
Page 65 Data administration Page 65 of 1814 Prompt Response Description BIPV Bit rate (bipolar violation and CRC) monitoring limits 1–(3)–4 Maintenance threshold 1–(2)–4 Out-of-service threshold SRTK Frame slip tracking monitoring limits 1–(5)–24 Maintenance threshold, the minimum time, in hours, between slips 1–(30)–3600 Out-of-service threshold, the maximum number of slips per hour SRNT...
Page 66: Data Administration
Page 66 of 1814 Data administration Prompt Response Description Free run mode <cr> No primary or secondary reference source assigned X preceding the number deletes existing primary reference source SREF Secondary reference source for clock controller Prompted only if PREF is not free run Free run mode <cr>...
Page 67 Data administration Page 67 of 1814 Prompt Response Description 1–(5)–24 Maintenance threshold, the minimum time, in hours, between slips 1–(30)–3600 Out-of-service threshold, the maximum number of slips per hour SRNT Frame slip free run (nontracking) monitoring limits 1–(15)–1024 Maintenance threshold, the minimum time, in seconds, between 10 consecutive slips 1–(3)–1024 Out-of-service threshold, the minimum time, in seconds, between...
Page 68 Page 68 of 1814 Data administration LD 17 - Configure the Primary D-channel. Prompt Response Description Change existing data. TYPE ADAN Action device and number. - ADAN NEW DCH xx Add a D-channel on logical port 0-63, for large systems (51C, 61C, and 81C).
Page 69 Data administration Page 69 of 1814 Port number of the NTBK51BA, for the small system (Option 11C). - DES aaa...a Designator. DES is used to identify the link and can be up to 16 alphanumeric characters: 0-9, and upper case A-Z. Characters “*”...
Page 70 Page 70 of 1814 Data administration - TIMR (NO) YES Change Protocol Timer values. - LAPD (NO) YES Change Link Access Protocol for D-Channel parameters. LD 17 – Configure a Back-up D-channel. This step is optional, and performed only if a Back-up D-Channel is required.
Page 71 Data administration Page 71 of 1814 Port number of the NTBK51AA, if the NTBK51AA is used for D-Channel handling on large systems (Options 51C, 61C, 81C). Port 0 of the NTBK51AA can only be defined to work with Loop 0 of the NT5D97AA DDP2 card, and Port 1 of the NTBK51AA can only be defined to work with Loop 1 of the NT5D97AA.
Page 72 Page 72 of 1814 Data administration - CTYP MSDL Card type where: TMDI MSDL = NT6D80 Multi-purpose Serial Data Link, or the NTBK51AA Downloadable D-Channel Daughterboard, for large systems (Options 51C, 61C, or 81C). MSDL = The NTBK51BA Downloadable D-Channel Daughterboard for the small system (Option 11C).
Page 73 Data administration Page 73 of 1814 - - DCHL LOOP ID Primary PRI loop number and interface identifier, for the 0-159 (0)-15 D-channel. When INBD package 255 is enabled values for both the PRI loop number (LOOP) and the D-channel interface identifier (ID) must be entered.
Page 74: Mbps Gateway
Page 74 of 1814 Data administration FEAT Feature is digital pad. PDCA (1)-16 Pad category table number. TNLS Print TN list (if REQ = PRT). DFLT (1)-16 Default table (when REQ = NEW). The following prompts define the pad levels. The receiving pad code is r and the transmission pad code is t.
Page 75 Data administration Page 75 of 1814 PRI2 2.0 Mbps PRI/DTI trunk (prompted only if the 1.5/2.0 Mbps Gateway feature is available and equipped and TYPE=PRI). Analog CO trunk Analog TIE trunk LD 16 – Configure a PRI route. Prompt Response Description Add new data.
Page 76 Page 76 of 1814 Data administration - NCNA Network Calling Name allowed. - NCRD Network Call Redirection allowed. ICOG Incoming and Outgoing trunks. SRCH (LIN) RRB Search method for outgoing trunk member. LIN = Linear Hunt search method. RRB = Round Robin search method. ACOD xxx..x One-seven-digit access code for the trunk route.
Page 77 Data administration Page 77 of 1814 CTYP DCHI MSDL The card type on which the I/O device is to be configured. There is no default. You must choose one of the available responses. PTYP Port type at far end: Analog TIE trunk routes: (ATT) Analog TIE trunk Analog satellite Meridian 1 TIE trunk or ESN satellite Meridian 1...
Page 78 Page 78 of 1814 Data administration TYPE TIE trunk data block. l ch Loop and channel for digital trunks, where: l = Previously defined PRI loops. ch = channel 1-30. For large systems (Options 51C, 61C, 81C). c = card. u = unit.
Page 79 Data administration Page 79 of 1814 DTI implementation Task summary list The following is a summary of the tasks in this section: LD 17 – Configure a DTI interface on the Meridian 1 PBX. LD 16 – Configure a DTI route. LD 14 –...
Page 80 Page 80 of 1814 Data administration Designator field for trunk. TKTP TIE trunk type (this is the only type allowed). DTRK Digital trunk route. - DGTP DTI/DTI2 Digital trunk. ISDN Integrated Services Digital Network. ICOG Incoming and Outgoing trunks. SRCH Search method for outgoing trunk member.
Page 81 Data administration Page 81 of 1814 Loop and channel for digital trunks, where: l = Previously defined PRI loops. ch = channel 1-30. For large systems (Options 51C, 61C, 81C). c = card. u = unit. For the small system (Option 11C). DTI/DTI2 Designator field for trunk.
Page 82 Page 82 of 1814 Data administration TYPE DTI/DTI2 Digital Trunk Interface. FEAT Feature is digital pad. PDCA (1)-16 Pad category table number. TNLS Print TN list (if REQ = PRT). DFLT (1)-16 Default table (when REQ = NEW). For the following prompts, x = Rx code (receive) and y = Tx code (transmit). You may assign receive and transmit dB values to the prompts by entering a code which corresponds to a dB value.
Page 83 Data administration Page 83 of 1814 SATT Rx Tx Analog Satellite TIE trunk. Rx = 6 Tx = 0 Rx Tx Analog CO trunk. Rx = 6 Tx = -3 Tx Rx 1.5 Mb PRI trunk. Applicable when Port Type at far end is PRI for the route (PTYP prompt = PRI in LD 16).
Page 84 Page 84 of 1814 Data administration IDLE (S) abcd Idle. IDLE (R) abcd Idle. FALT (S) abcd Fault (DTI out-of-service). FALT (R) abcd Fault (DTI out-of-service). P RRC (S) abcd Register Recall. - TIME 10-(100)-630 Time of RRC (S) in milliseconds. TIME (0)-1920 Persistence Time required before signal is accepted.
Page 85 Data administration Page 85 of 1814 Prompts for Incoming Calls SEZ (R) abcd Seize for voice or data calls from a non-SL-1. E SEZ (R) abcd Seize for voice or data calls from a non-SL-1. - TIME 16-(56)-1000 16-(296)-1000. Minimum and maximum acceptable pulse duration. SEZD (R) abcd Seize for data calls between SL-1s.
Page 86 Page 86 of 1814 Data administration P OPC (R) abcd Operator Calling. - TIME 64-(128)-192 Time of OPCA (R) pulse. - TIME 16-(96)-1000 16-(160)-1000 Minimum and maximum acceptable pulse duration. - REPT (1)-5 Number of OPCA (R) pulses. CONN (S) abcd Connect.
Page 87 Data administration Page 87 of 1814 P ESNW (S) abcd ESN Wink. P CAS (S) abcd Centralized Attendant. CLRF (R) abcd Clear Forward. - SOS abcd Special Operator Signal. P BRLS (S) abcd Backward Release. - TIME 10-(600)-2000 Time of pulse length in 10 ms increments. P FRLS (R) abcd Forward Release.
Page 88 Page 88 of 1814 Data administration Prompts for Outgoing Calls SEZ (S) abcd Seize for voice or data calls to a non-SL-1. E SEZ (S) abcd Seize for voice or data calls to a non-SL-1. - TIME 10-(150)-630 Time of pulse length in 10 ms increments. SEZD (S) abcd Seize for Data calls.
Page 89 Data administration Page 89 of 1814 P OPRC (R) abcd Operator Recall for special services. P BURS (S) abcd Bring Up Receiver for L1 networking. P BURS (R) abcd Bring Up Receiver for L1 networking. - TIME 64-(128)-192 Time for BURS (R) pulse. CLRB (R) abcd Clear Back.
Page 90 Page 90 of 1814 Data administration Time of pulse length in 8 ms increments. C SUPO (S) abcd Complex Supervision to Operator Signal used for KD3 signaling. Note that the input for a must be C. 553-2901-301 Standard 9.00 January 2002...
Page 91: 1.5/2.0 Mbps Gateway
Page 91 of 1814 1.5/2.0 Mbps Gateway Contents The following are the topics in this section: Feature Description ........2.0 Mb hardware introduced into North America .
Page 92 Page 92 of 1814 1.5/2.0 Mbps Gateway Feature Description For digital connectivity, via both Digital Trunk Interface (DTI) and Primary Rate Interface (PRI), North America uses 1.5 Mbps carriers programmed as Pulse Code Modulation Companding u-Law. Internationally, in places like Europe, 2.0 Mbps carriers programmed as Pulse Code Modulation Companding A-Law are used.
Page 93: Mb Hardware Introduced Into North America
1.5/2.0 Mbps Gateway Page 93 of 1814 • ETSI QSIG (European Telecommunications Standard Institute QSIG) • ISIG QSIG (International Standards Organization QSIG) Back-up D-Channel and nB+D are only supported in an MCDN environment (IFC type of SL1). The North America 1.5/2.0 Mbps Gateway feature supports the following interfaces: •...
Page 94 Page 94 of 1814 1.5/2.0 Mbps Gateway For DTI2 on Meridian 1 large systems (Options 51C, 61C, 81C): • NT5D97AA Dual-port DTI2/PRI2 card (in DTI2 mode) For PRI2 on the Meridian 1 small system (Option 11C): • NTBK50AA PRI2 card •...
Page 95: Hardware Installation
For information on how to install the NT5D97AA Dual-port DTI2/PRI2 card, and the NTBK51AA DDCH card on large systems (Options 51C, 61C, and 81C), please refer to Nortel Networks Publication ISDN PRI: Installation (553-2901-201). Also refer to this publication for information on Clocking.
Page 96: Conversion Scenarios
Page 96 of 1814 1.5/2.0 Mbps Gateway • International Primary Rate Access (IPRA) package 202 • International nB+D (INBD) package 255, as an optional package for nB+D applications Note: The following packages are required as prerequisites: • Digit Display (DDSP) package 19 •...
Page 97 1.5/2.0 Mbps Gateway Page 97 of 1814 In this scenario, the conversion from A-Law to u-Law, and u-Law to A-Law, is done at the Meridian 1 programmed as A-Law. It is this Meridian 1 PBX that acts as the 1.5/2.0 Mbps gateway. Scenario 4 - Gateway A-Law Meridian 1 connected to u-Law Meridian/CO over an u-Law 2.0 Mbps connection An International (2.0 Mbps) Meridian 1 PBX, programmed as A-Law, is...
Page 98: Pri2 Implementation
Page 98 of 1814 1.5/2.0 Mbps Gateway LD 17 - Configure the CODEC coding law for the set. LD 97 - Configure the Multifrequency Sender parameters. LD 97 - Configure the system parameters for peripheral equipment. LD 17 - Configure the Primary D-channel. LD 17 –...
Page 99 1.5/2.0 Mbps Gateway Page 99 of 1814 • Configure a PRI2 interface, using LD 17. • Configure a the Pulse Code Modulation Companding Law on the PRI2 D-Channel, using LD 17. Please note the following additional steps when using a Meridian M2317 set on a Meridian switch configured as A-Law: —...
Page 100 Page 100 of 1814 1.5/2.0 Mbps Gateway ISDN Integrated Services Digital Network. - RCNT 0-(5) Redirection Count for ISDN calls. - - PCMC 0-(15)-31 The number of Pulse Code Modulation Conversions allowed, from u-Law to A-Law or A-Law to u-Law, in a network connection.
Page 101 1.5/2.0 Mbps Gateway Page 101 of 1814 Please note the following additional steps when using a Meridian M2317 set on a Meridian switch configured as A-Law: • Configure the CODEC coding law for the set, using LD 17 • Configure the Multifrequency Sender parameters, using LD 97 •...
Page 102 Page 102 of 1814 1.5/2.0 Mbps Gateway TYPE SYSP System parameters for peripheral equipment. INTN International companding law. FDLC P ALL Fast Download parameters to all line cards. Initialize the Meridian 1 switch, to download all parameters to the line cards. This initialization has to be performed only once.
Page 103 1.5/2.0 Mbps Gateway Page 103 of 1814 - DNUM 0-15 Device number for I/O ports. All ports on the MSDL card share the same DNUM. The MSDL card address settings must match the DNUM value. - PORT Port number on the NT6D80 MSDL card, if the MSDL is used for D-Channel handling on large systems (Options 51C, 61C, 81C).
Page 104 Page 104 of 1814 1.5/2.0 Mbps Gateway - PRI2 Secondary PRI2 loops and sequence, for nB+D configuration. 0-159 (0)-15 For large systems (Options 51C, 61C, 81C). 1-9 (0)-15 For small system (Option 11C). Enter 0, the default. - OTBF 0-(32)-127 Output Request Buffers.
Page 105 1.5/2.0 Mbps Gateway Page 105 of 1814 LD 17 – Configure a Back-up D-channel. This step is optional, and performed only if a Back-up D-Channel is required. Please note that Back-up D-Channel is only supported in an MCDN environment (IFC must be set to SL1). Prompt Response Description...
Page 106 Page 106 of 1814 1.5/2.0 Mbps Gateway Port number of the NTBK51AA, if the NTBK51AA is used for D-Channel handling on large systems (Options 51C, 61C, 81C). Port 0 of the NTBK51AA can only be defined to work with Loop 0 of the NT5D97AA DDP2 card, and Port 1 of the NTBK51AA can only be defined to work with Loop 1 of the NT5D97AA.
Page 107 1.5/2.0 Mbps Gateway Page 107 of 1814 - CTYP MSDL Card type where: MSDL = NT6D80 Multi-purpose Serial Data Link, or the NTBK51AA Downloadable D-Channel Daughterboard, for large systems (Options 51C, 61C, or 81C). MSDL = The NTBK51BA Downloadable D-Channel Daughterboard for the small system (Option 11C).
Page 108 Page 108 of 1814 1.5/2.0 Mbps Gateway - - DCHL LOOP ID Primary PRI2 loop number and interface identifier, for 0-159 (0)-15 the D-channel. When INBD package 255 is enabled values for both the PRI loop number (LOOP) and the D-channel interface identifier (ID) must be entered.
Page 109 1.5/2.0 Mbps Gateway Page 109 of 1814 PDCA (1)-16 Pad category table number. TNLS Print TN list (if REQ = PRT). DFLT (1)-16 Default table (when REQ = NEW). For the following prompts, x = Rx code (receive) and y = Tx code (transmit). You may assign receive and transmit dB values to the prompts by entering a code which corresponds to a dB value.
Page 110 Page 110 of 1814 1.5/2.0 Mbps Gateway Rx Tx Analog CO trunk. Rx = 6 Tx = -3 Tx Rx 1.5 Mb PRI trunk. Applicable when Port Type at far end is PRI for the route (PTYP prompt = PRI in LD 16). Rx = 0 Tx = 0 PRI2...
Page 111 1.5/2.0 Mbps Gateway Page 111 of 1814 DTRK Digital trunk route. - DGTP PRI2 2.0 Mb PRI digital trunk. ISDN Integrated Services Digital Network. - MODE ISDN PRI route. - IFC SL-1 interface (Meridian 1 to Meridian 1 connectivity). - - PNI (0)-32700 Private Network identifier.
Page 112: Dti2 Implementation
Page 112 of 1814 1.5/2.0 Mbps Gateway l ch Loop and channel for digital trunks, where: l = Previously defined PRI2 loops. ch = channel 1-30. For large systems (Options 51C, 61C, 81C). c = card. u = unit. For the small system (Option 11C). PRI2 Designator field for trunk.
Page 113 1.5/2.0 Mbps Gateway Page 113 of 1814 • Configure a PRI2 route, using LD 16. • Configure a PR2 trunk, using LD 14. • Define the ABCD (signaling category) table, using LD 73. ABCD tables apply to DTI/DTI2 interfaces only. LD 15 - Configure the Pulse Code Modulation Conversion value on the Meridian 1 PBX.
Page 114 Page 114 of 1814 1.5/2.0 Mbps Gateway LD 16 – Configure a DTI2 route. Prompt Response Description Add new data. TYPE Route Data Block. CUST Customer number, as already defined in LD 15. ROUT Route number. xxx = 0-511 for large systems (Options 51C, 61C, 81C). xxx = 0-127 for the small system (Option 11C).
Page 115 1.5/2.0 Mbps Gateway Page 115 of 1814 LD 14 – Configure DTI2 trunks. Prompt Response Description Add new data. Change existing data. TYPE TIE trunk data block. Loop and channel for digital trunks, where: l = Previously defined PRI2 loops. ch = channel 1-30.
Page 116 Page 116 of 1814 1.5/2.0 Mbps Gateway LD 73 – Define the digital pad tables, per country requirement. Prompt Response Description NEW = Add new data. CHG = Change existing data. OUT = Remove existing data. END = Exit LD 73. PRT = Print specified data.
Page 117 1.5/2.0 Mbps Gateway Page 117 of 1814 Rx Tx 1.5 Mb DTI/PRI Digital COT, FEX, WAT, DID trunks. Rx = 3 Tx = 3 Rx Tx Via Net Loss Analog TIE trunk. Rx = 3 Tx = 0 SATT Rx Tx Analog Satellite TIE trunk.
Page 118 Page 118 of 1814 1.5/2.0 Mbps Gateway LD 73 – Configure an ABCD (signaling category table). ABCD tables apply only to DTI/DTI2 interfaces. This step is optional. Before configuring the ABCD tables, you may refer to the section “Signaling category (ABCD tables) assignment and modification” on page 125, which explains ABCD tables assignment and modification.
Page 119 1.5/2.0 Mbps Gateway Page 119 of 1814 - TIME 10-(100)-630 Time of RRC (S) in milliseconds. TIME (0)-1920 Persistence Time required before signal is accepted. Prompts for Incoming Calls SEZ (R) abcd Seize for voice or data calls from a non-SL-1. E SEZ (R) abcd Seize for voice or data calls from a non-SL-1.
Page 120 Page 120 of 1814 1.5/2.0 Mbps Gateway - P EOSB (S) abcd End of Selection Busy. - - TIME (100)-150 Time for EOSB (S). P OPC (R) abcd Operator Calling. - TIME 64-(128)-192 Time of OPCA (R) pulse. - TIME 16-(96)-1000 16-(160)-1000 Minimum and maximum acceptable pulse duration.
Page 121 1.5/2.0 Mbps Gateway Page 121 of 1814 - TIME xxxx yyyy Minimum and maximum time range for OPRS (R). P NXFR (S) abcd Network Transfer. P ESNW (S) abcd ESN Wink. P CAS (S) abcd Centralized Attendant. CLRF (R) abcd Clear Forward.
Page 122 Page 122 of 1814 1.5/2.0 Mbps Gateway P WNKS (R) abcd Wink Start. - TIME 16-(136)-504 16-(288)-504 Minimum and maximum length of P WNKS (R) pulse. P EOS (R) abcd End of Selection. - TIME (64)-320 64-(256)-320 Length of EOS (R) pulse. CONN (S) abcd Connect.
Page 123 1.5/2.0 Mbps Gateway Page 123 of 1814 P NXFR (R) abcd Network Transfer. P ESNW (R) abcd ESN Wink. P CAS (R) abcd Centralized Attendant Service. CLRF (S) abcd Clear Forward. - TIME (0)-800 Time in milliseconds. - SOS abcd Special Operator Signal.
Page 124 Page 124 of 1814 1.5/2.0 Mbps Gateway Table 23 Default values for Signaling Categories 1 and 16 (Incoming Calls) Incoming Calls SICA 1 SICA 16 Incoming Calls SICA 1 SICA 16 E SEZ (R) 0001 0101 CONN (R) 0001 0101 SEZD (R) UNUSED UNUSED...
Page 125 1.5/2.0 Mbps Gateway Page 125 of 1814 Outgoing Calls SICA 1 SICA 16 P EOS (R) UNUSED UNUSED CONN (S) 0001 0101 E CONN (R) 0101 0101 P OPRC (R) UNUSED UNUSED P BURS (S) UNUSED UNUSED P BURS (R) UNUSED UNUSED C CLRB (R)
Page 126 Page 126 of 1814 1.5/2.0 Mbps Gateway — “C” can only be entered for signals that have “C” in front of them when the signal is prompted; the signals are: “C CLRB (S), C CLRB (R) and C SUPO (S) UNUSED” —...
Page 127 1.5/2.0 Mbps Gateway Page 127 of 1814 How to determine signal direction? The direction of the signal is indicated by a single character in brackets at the end of the signal name: • (R) - Indicates that the signal is to be received by the switch •...
Page 128 Page 128 of 1814 1.5/2.0 Mbps Gateway 553-2901-301 Standard 9.00 January 2002...
Page 129: Trunk Route Member Expansion
Page 129 of 1814 510 Trunk Route Member Expansion Contents The following are the topics in this section: Feature Description ........Operating parameters .
Page 130: Trunk Route Member Expansion
Page 130 of 1814 510 Trunk Route Member Expansion For a Meridian 1 to Meridian 1 connectivity, a user is now able to configure, on one trunk route, one D-Channel with 382 (T1) or 480 (E1) B-Channels, a Backup D-Channel, and a second D-Channel with another 128 (T1) or 30 (E1) B-Channels.
Page 131 510 Trunk Route Member Expansion Page 131 of 1814 Figure 3 510 trunk members expansion configured for a Meridian 1 to Meridian 1 connectivity (E1) Figure 4 510 trunk members expansion configured for a Meridian 1 to DMS connectivity (T1) International ISDN PRI Feature description and administration...
Page 132 Page 132 of 1814 510 Trunk Route Member Expansion Figure 5 510 trunk members expansion configured for a Meridian 1 to DMS connectivity (E1) This feature applies to the following trunk mode configurations: • PRI/PRI2 mode • DTI/DTI2 mode • Shared mode •...
Page 133 510 Trunk Route Member Expansion Page 133 of 1814 • FGDT (Feature Group D) • COT (Central Office) • • DID (Direct Inward Dial) • FEX (Foreign Exchange) • WATS (Wide Area Telecommunications Service) The overlay programs that are affected are: •...
Page 134 Page 134 of 1814 510 Trunk Route Member Expansion Feature interactions Integrated Services Access The ISA minimum (MIN) and maximum (MAX) fields for service routes may be configured in LD 16 at a value from 0-510. NI-2 Call By Call Service Selection The NI-2 Call By Call Service Selection maximum (MAX) field for service routes may be configured in LD 16 at a value from 0-510.
Page 135 510 Trunk Route Member Expansion Page 135 of 1814 LD 27 - Define the trunk type as BRIT, and the route member number on a Digital Subscriber Loop (DSL). For ISA trunks: LD 16 – Define the ISA master route. LD 14 - Define the trunk type as ISA, and the route member number.
Page 136 Page 136 of 1814 510 Trunk Route Member Expansion TKTP Supported trunk type (other than ISA or CBC). Central Office. Direct Inward Dial. Foreign Exchange. Wide Area Telecommunications Service. FGDT Feature Group D. DTRK (NO) YES Define whether or not the trunk route is digital. Enter NO for analog, YES for digital.
Page 137 510 Trunk Route Member Expansion Page 137 of 1814 ICOG Incoming or outgoing trunk type, where aaa can be: ICT = Incoming only. OGT = Outgoing only. IAO = Both incoming and outgoing. LD 14 - Define the trunk type, and the route member number. Prompt Response Description...
Page 138 Page 138 of 1814 510 Trunk Route Member Expansion RTMB 0-511 1-510 Route number and member number, for Options 51C-81C. 0-127 1-510 Route number and member number, for Option 11C. LD 27 - Define the trunk type as BRIT, and the route member number on a Digital Subscriber Loop (DSL).
Page 139 510 Trunk Route Member Expansion Page 139 of 1814 For ISA trunks LD 16 – Define the ISA master route. Prompt Response Description Add a new data. Change existing data. TYPE Route Data Block. CUST Customer number, as already defined in LD 15. xx = 0-99 for Options 51C-81C.
Page 140 Page 140 of 1814 510 Trunk Route Member Expansion LD 14 - Define the trunk type as ISA, and the route member number. Prompt Response Description NEW xxx Add new data. Follow NEW with xxx = 1-510, to create that number of consecutive trunks.
Page 141 510 Trunk Route Member Expansion Page 141 of 1814 LD 16 - Define the maximum and minimum number of channels per ISA service route. Prompt Response Description Add a new data. Change existing data. TYPE Route Data Block. CUST Customer number, as already defined in LD 15. xx = 0-99 for Options 51C-81C.
Page 142 Page 142 of 1814 510 Trunk Route Member Expansion ICOG Incoming or outgoing trunk type, where aaa can be: ICT = Incoming only. OGT = Outgoing only. IAO = Both incoming and outgoing. For NI-2 CBC trunks LD 16 – Define the NI-2 CBC master route. Prompt Response Description...
Page 143 510 Trunk Route Member Expansion Page 143 of 1814 ICOG Incoming or outgoing trunk type, where aaa can be: ICT = Incoming only. OGT = Outgoing only. IAO = Both incoming and outgoing. LD 14 - Define the trunk type as NI-2 CBC, and the route member number. Prompt Response Description...
Page 144 Page 144 of 1814 510 Trunk Route Member Expansion LD 16 - Define the maximum number of channels per NI-2 service route. Prompt Response Description Add a new data. Change existing data. TYPE Route Data Block. CUST Customer number, as already defined in LD 15. xx = 0-99 for Options 51C-81C.
Page 145: Advice Of Charge
Page 145 of 1814 Advice of Charge Contents The following are the topics in this section: Feature Description ........Introduction .
Page 146 Page 146 of 1814 Advice of Charge Feature Description This section describes the Advice of Charge feature as it applies to the interface types supported by ISDN PRI. Introduction Prior to the introduction of the Advice of Charge supplementary service, the cost of calls to Central Offices in most European markets was calculated by counting and recording the periodic pulses provided by the Central Office during a call, and then calculating the cost of each call.
Page 147: Storing Charging Information
Advice of Charge Page 147 of 1814 Storing charging information Charging information is stored using meters, which may be assigned to sets, attendant consoles, trunk routes, and customers as follows: • one meter is assigned to each set, via Metered Assigned (MRA) Class of Service, on a TN basis.
Page 148: Displaying Charging Information
Page 148 of 1814 Advice of Charge Displaying charging information Charging information may be displayed on display-equipped Meridian Modular terminals, M2317, and M3000 sets. This display capability is provided by the Charge Display at End of Call feature. This feature appends the charge information to existing information on the display and retains the information displayed for 10 seconds.
Page 149: Handling Overflow Charging Information
Advice of Charge Page 149 of 1814 Handling overflow charging information The charging information meters can store a maximum of 32,767 Periodic Pulse units. If this total is exceeded, an overflow counter is incremented. Whenever this counter reaches three, a message is output to the background terminal and the counter is reset to zero.
Page 150 Page 150 of 1814 Advice of Charge • The Advice of Charge information is not transported between a Meridian 1 to Meridian 1 connection. Therefore, if a tandem call is made from one Meridian 1 PBX to another Meridian 1 PBX, and then to a Central Office, the originator’s display is not updated with the charge information.
Page 151 Advice of Charge Page 151 of 1814 The attendant activates this feature by requesting the call charge on any outgoing ISDN CO trunk providing AOC by pressing the METER (MTR) key after making the call. When the MTR key is pressed, the METER lamp is lit and all metered outgoing ISDN calls connected to the active console loop are marked as “metered”.
Page 152 Page 152 of 1814 Advice of Charge BRI Trunk Access for Japan AOC information can be received over ISDN BRI trunks using the Japan D70 signaling. Call Forward All Calls, Call Forward Busy, Call Forward No Answer Chargeable calls transferred to a station and redirected to another station via Call Forward are charged against: the “Call Forwarded to Station”, if it answers and the transferring party completes the transfer;...
Page 153 Advice of Charge Page 153 of 1814 Conference Whenever an ISDN CO trunk providing AOC is added into a conference, the charge for the call continues to be assigned to the station user who initiated the conference. If the person who adds the call to the conference disconnects while the conference is ongoing, the DN to be charged is changed to the one that has been in the conference the longest.
Page 154 Page 154 of 1814 Advice of Charge Malicious Call Trace (Enhanced) In Australia, the ISDN version of this feature introduces a disconnect delay to sets with MCT class of service. This delay may be up to 30 seconds. In cases of sets having MCT class of service, the charge information is not delayed, printed in the CDR records, or added to the permanent meter of the set until the delay timer expires or the user releases the call.
Page 155: Advice Of Charge For Central Office Connectivity
Advice of Charge Page 155 of 1814 • Busy Verification • Recording the accumulated call charging information for each call on the CDR record (if CDR is equipped) • Calculating the total charge for each call, based on the assigned unit cost and the accumulated call charging information •...
Page 156 Page 156 of 1814 Advice of Charge Feature packaging The following packages are required for Advice of Charge: • Call Detail Recording (CDR) package 4; • Call Detail Recording Teletype Terminal (CTY) package 5; • Controlled Class of Service (CCOS) package 81; •...
Page 157 Advice of Charge Page 157 of 1814 PARM System parameters. MTRO Periodic Pulse Metering. LD 15 – Allow CDR Charge. Prompt Response Description REQ: Change. TYPE: Periodic Pulse Metering. CUST Customer number. - UCST Unit cost, x = (0)-9999. LD 15 – Allow Charge Display. Prompt Response Description...
Page 158 Page 158 of 1814 Advice of Charge ISDN Configure ISDN data. AXEA ISDN Interface for Australia. Must be configured in LD 17 for the applicable D-channel. Call Detail Recording. CDR on outgoing toll calls. CDR on all answered outgoing calls. ENDC AOC End of Call allowed for international ISDN interfaces.
Page 159 Advice of Charge Page 159 of 1814 LD 12 – Assign a Meter Recall key to the Attendant Console. Prompt Response Description Add new data. Change existing data. TYPE aaaa Type of console, where aaaa = 1250 for M1250 console, 2250 for M2250 console, ATT for QCW3, QCW4 console, or PWR if the TN is used for power or Attendant Supervisory Module ASM.
Page 160 Page 160 of 1814 Advice of Charge • Call Detail Recording (CDR) package 4; • Call Detail Recording Teletype Terminal (CTY) package 5; • Controlled Class of Service (CCOS) package 81; • Background Terminal (BGD) package 99; • Periodic Pulse Metering/Message Registration (MR) package 101; and •...
Page 161 Advice of Charge Page 161 of 1814 - IFC EURO EuroISDN interface. - CNTY Enter country pertaining to EuroISDN interface. Austria Denmark (ETSI) ETS 300-102 basic protocol Finland Germany Italy Norway Portugal Sweden Ireland Holland Switzerland Belgium Spain United Kingdom France Commonwealth of Independent States (Russia and the Ukraine).
Page 162 Page 162 of 1814 Advice of Charge LD 15 – Allow Charge Display. Prompt Response Description REQ: Change. TYPE: Customer features and options. CUST Customer number. CHDA Charge display allowed. LD 16 – Allow AOC on the route. Prompt Response Description Change.
Page 163 Advice of Charge Page 163 of 1814 - - CNTY Enter country pertaining to EuroISDN interface. Austria Denmark (ETSI) ETS 300-102 basic protocol Finland Germany Italy Norway Portugal Sweden Ireland Holland Switzerland Belgium Spain United Kingdom France Commonwealth of Independent States (Russia and the Ukraine).
Page 164: Ins1500 (Japan D70) (End Of Call)
Page 164 of 1814 Advice of Charge LD 10/11 – Assign meters to sets. Prompt Response Description REQ: Add new data. Change existing data. TYPE: aaaa Telephone type where aaaa = 500, 2500, SL1, 2006, 2008, 2009, 2016, 2018, 2112, 2216, 2317, 2616, or 3000. l s c u Terminal Number, for Options 51C, 61C, 81C.
Page 165 Advice of Charge Page 165 of 1814 Prior to the introduction of the AOC feature for Japan D70, the method used to determine which feature was equipped was to check if the International Supplementary Features software package 131 was equipped. If it was, PPM was required.
Page 166 Page 166 of 1814 Advice of Charge Feature implementation Task summary list The following is a summary of the tasks in this section: LD 17 – Select PPM functionality and CDR format. LD 15 – Allow CDR Charge. LD 15 – Allow Charge Display. LD 16 –...
Page 167 Advice of Charge Page 167 of 1814 CUST Customer number. - UCST Unit cost, x = (0)-9999. LD 15 – Allow Charge Display. Prompt Response Description REQ: Change. TYPE: Customer features and options. CUST Customer number. CHDA Charge display allowed. LD 16 –...
Page 168 Page 168 of 1814 Advice of Charge ISDN Interface for Japan. Call Detail Recording. CDR on outgoing toll calls. CDR on all answered outgoing calls. ENDC AOC End of Call allowed for international ISDN interfaces. RUCS Route unit cost value received is treated as charge. RUCF Route unit conversion factor, no conversion required.
Page 169: Numeris (End Of Call)
Advice of Charge Page 169 of 1814 LD 12 – Assign a Meter Recall key to the Attendant Console. Prompt Response Description Add new data. Change existing data. TYPE aaaa Type of console, where aaaa = 1250 for M1250 console, 2250 for M2250 console, ATT for QCW3, QCW4 console, or PWR if the TN is used for power or Attendant Supervisory Module ASM.
Page 170 Page 170 of 1814 Advice of Charge LD 15 – Configure Periodic Pulse Metering. LD 16 – Modify the Trunk Route for AOC. LD 17– Change Configuration Record to allow PPM. Prompt Response Description Change. TYPE Configuration record. PARM Parameters for Interface and transmission mode. MTRO Periodic Pulse Metering.
Page 171 Advice of Charge Page 171 of 1814 LD 15 – Configure the Customer Data Block for AOC Prompt Response Description REQ: Change existing data. TYPE: Features and options. CUST Customer number. xx MTR ICI number, Meter Recall. LD 15 – Configure Periodic Pulse Metering Prompt Response Description...
Page 172: Numeris And Swissnet (During Call)
Page 172 of 1814 Advice of Charge CDR on Outgoing calls. - OTL CDR on Outgoing toll calls. Printing CDR records for no PPM or AOC count. ENDC The AOC information is decoded at the end of the call. RUCF Route Unit Conversion Factor.
Page 173 Advice of Charge Page 173 of 1814 • for a call which has been modified by transfer or conference, the cost of each part of the call is provided in each CDR record associated with each extension, and • a call is redirected, the CDR records show all extensions associated with a particular call together with the call costs associated with each extension.
Page 174 Page 174 of 1814 Advice of Charge LD 10/11 – Assign meters to sets. LD 12 – Assign a Meter Recall key to the Attendant Console. LD 17 – Select PPM functionality and CDR format. Prompt Response Description Change. TYPE Configuration record.
Page 175 Advice of Charge Page 175 of 1814 CHDA Charge display allowed. LD 16 – Allow AOC on the route. Prompt Response Description Change. TYPE Route data block. CUST Customer number. ROUT Route number. ISDN Configure ISDN data. NUME ISDN Interface for Numeris (France). SWIS ISDN Interface for Swis (Switzerland).
Page 176 Page 176 of 1814 Advice of Charge TYPE: aaaa Telephone type where aaaa = 500, SL1, 2006, 2008, 2009, 2016, 2018, 2112, 2216, 2317, 2616, or 3000. l s c u Terminal Number. For Option 11C. Message Registration Allowed. LD 12 – Assign a Meter Recall key to the Attendant Console. Prompt Response Description...
Page 177 Advice of Charge Page 177 of 1814 For PRI connectivity, the following packages are required: • Integrated Service Digital Network (ISDN) package 145; • 2.0 Mb Primary Rate Interface (PRI2) package 154; • ISDN Supplementary Features (ISDNS) package 161; and •...
Page 178 Page 178 of 1814 Advice of Charge LD 15 – Configure the Customer Data Block for AOC. Prompt Response Description REQ: Change existing data. TYPE: ISDN and ESN Networking options. CUST Customer number. ISDN Integrated Services Digital Network allowed for customer. - PFX1 xxxx Prefix 1.
Page 179 Advice of Charge Page 179 of 1814 HMTL (YES) NO Hotel/Motel environment. PCDL PPM output on CDR Link. Additional three words added to tape record. UCST (0) - 9999 Unit Cost for Periodic Pulse Metering. ATCH (NO) YES Attendant display of call Charge. SCDL Schedule for printing Message Registration and PPM data.
Page 180 Page 180 of 1814 Advice of Charge - LAPD Link Access Protocol for D-channel. Change LAPD parameters. - - T203 2-(10)-40 Maximum Time allowed without frames being exchanged in seconds. LD 16 – Change the Trunk Route for AOC. Prompt Response Description Ad new data.
Page 181 Advice of Charge Page 181 of 1814 - - OTL CDR on Outgoing Toll calls. (NO) YES RUCS 0-9999 Route Unit Cost. Feature operation No specific operating procedures are required to use this feature. International ISDN PRI Feature description and administration...
Page 182 Page 182 of 1814 Advice of Charge 553-2901-301 Standard 9.00 January 2002...
Page 183: Analog Semi-Permanent Connections
Page 183 of 1814 Analog Semi-permanent Connections Contents The following are the topics in this section: Feature Description ........Operating parameters .
Page 184: Analog Semi-Permanent Connections
Page 184 of 1814 Analog Semi-permanent Connections If communication is broken after an ASPC call is established between two systems, the incoming trunk is left in the busy state. A message is then printed along with the date, time, manual incoming trunk TN and its corresponding MNDN on the TTY.
Page 185 Analog Semi-permanent Connections Page 185 of 1814 The incoming manual trunk, when seized at the far end, is automatically terminated on the MNDN. The manual outgoing trunk service dials the outgoing route access code to complete an outgoing call after ringing the trunk.
Page 186 Page 186 of 1814 Analog Semi-permanent Connections LD 15 – Configure ASPC reconnection timer. Prompt Response Description REQ: Change existing data. TYPE: Customer features and options. CUST Customer number..BSFE (NO) YES Boss Secretary Filtering Enhancement ASPCT (10)–180 ASPC reconnection Timer (in seconds).
Page 187 Analog Semi-permanent Connections Page 187 of 1814 LD 16 – Configure Incoming Manual Route. Prompt Response Description Change route data. TYPE Route data block. CUST Customer number associated with this route..TKTP a..a Outgoing manual trunk type ..
Page 188 Page 188 of 1814 Analog Semi-permanent Connections MNDN xx...x Manual Directory Number xx...x is the access code of the outgoing manual route or is the DN of the terminating set. Manual Incoming Allowed. SPCA ASPC allowed. SPCD = ASPC denied (default). Feature operation No specific operating procedures are required to use this feature.
Page 189 Page 189 of 1814 Attendant and Network Wide Remote Call Forward Contents The following are the topics in this section: Feature Description ........Operating parameters .
Page 190 Page 190 of 1814 Attendant and Network Wide Remote Call Forward The attendant RCFW functionality is controlled by a flexible Attendant key (RFW). The attendant has the capability to view the current call forward number and determine the call forward status of any station. It is also possible for an attendant to activate or deactivate call forward for a particular station.
Page 191 Attendant and Network Wide Remote Call Forward Page 191 of 1814 Since ISDN BRI sets do not support Flexible Feature Codes (FCCs), Remote Call Forward is not supported on BRI sets. Multiple Appearance DNs The RCFW feature only applies to the primary appearances of Multiple Appearance DNs, and it is recommended that only one appearance of a Multiple Appearance DN be configured as the prime DN.
Page 192 Page 192 of 1814 Attendant and Network Wide Remote Call Forward Preventing Reciprocal Call Forward When Preventing Reciprocal Call Forward Allowed (PVCA) is defined in LD 15, a set within the same customer configuration cannot be call forwarded to a set that is call forwarded back to it. Thus, CFW loops are prevented. This feature applies when the CFW DN is changed by Remote Call Forward.
Page 193 Attendant and Network Wide Remote Call Forward Page 193 of 1814 There is no Attendant RCFW operation which interacts with the DCFW DN of Phantom TNs. Traffic Measurements The peg count, for the attendant RFW key, will be generated on the first RFW key press of the RCFW operation.
Page 194 Page 194 of 1814 Attendant and Network Wide Remote Call Forward Feature implementation Task summary list The following is a summary of the tasks in this section: Set-based Configuration: LD 15 – Set the Station Control Password Length. LD 15 – Configure a Special Prefix Number (SPRE) for the customer. LD 15 –...
Page 195 Attendant and Network Wide Remote Call Forward Page 195 of 1814 LD 15 – Configure a Special Prefix Number (SPRE) for the customer. Prompt Response Description REQ: Change. TYPE: Customer features and options. CUST Customer number. - SPRE xxxx Special Prefix Number. LD 15 –...
Page 196 Page 196 of 1814 Attendant and Network Wide Remote Call Forward LD 10 – Set the Station Control Password and allow Call Forward. Prompt Response Description REQ: Change. TYPE: Telephone type. l s c u Terminal number, for Options 51C, 61C, 81C. For Option 11C.
Page 197 Attendant and Network Wide Remote Call Forward Page 197 of 1814 CFXA Call Forward to External DN allowed. xx CFW 4-(16)-23 Assign Call Forward key (xx) and set the forwarding DN length. LD 16 – Configure the route data block. Prompt Response Description...
Page 198 Page 198 of 1814 Attendant and Network Wide Remote Call Forward FFCT (NO) YES Confirmation tone is (is not) to be given after an FFC. CODE RCFA Remote Call Forward Activate. RCFA xx = RCFA code. CODE RCFD Remote Call Forward Deactivate. RCFD xx = RCFD code.
Page 199 Attendant and Network Wide Remote Call Forward Page 199 of 1814 LD 15 – Configure the Attendant RCFW password. Prompt Response Description REQ: Change. TYPE: Attendant console. CUST Customer number. - IRFR (NO) YES Internal Remote Call Forward Password required. -- IRFP xxxxxxxx Internal RCFW Password (only prompted if the response to...
Page 200 Page 200 of 1814 Attendant and Network Wide Remote Call Forward - PNI 1-327000 Private Network Identifier. - - - HLOC 0-9999999 Home location code (ESN), 1-7 digits. X = delete digits. Feature operation Network Wide Set-based Remote Call Forward From the remote set dial: FFC RCFA code.
Page 201 Attendant and Network Wide Remote Call Forward Page 201 of 1814 If a password is not required, the console display will show the DN of the set to be forwarded followed by the CFW DN stored on that set. The RFW key lamp will display the status of the CFW DN.
Page 202: Attendant And Network Wide Remote Call Forward
Page 202 of 1814 Attendant and Network Wide Remote Call Forward 553-2901-301 Standard 9.00 January 2002...
Page 203: Attendant Blocking Of Directory Number
Page 203 of 1814 Attendant Blocking of Directory Number Contents The following are the topics in this section: Feature Description ........Operating parameters .
Page 204: Attendant Blocking Of Directory Number
Page 204 of 1814 Attendant Blocking of Directory Number When the attendant has completed the external call, the blocked DN can be rung and the call extended. The attendant is guaranteed that the requesting DN is not busy and is available to take the call when the processing has been completed.
Page 205 Attendant Blocking of Directory Number Page 205 of 1814 Feature interactions It is not possible to activate the Attendant Blocking of DN feature for an ACD DN. If an attempt to block an ACD DN is made, the attempt will be canceled and overflow tone will be returned.
Page 206 Page 206 of 1814 Attendant Blocking of Directory Number It will be possible to Break-in on the destination side with an Attendant Blocking of DN call on the source side of the Attendant Console. The same limitations to Break-in will apply as if the source side call is a normal call. Busy Lamp Field/Enhanced Busy Lamp Field When a DN is blocked due to the Attendant Blocking of DN feature, the Busy Lamp Field/Enhanced Busy Lamp Field lamp corresponding to this DN...
Page 207 Attendant Blocking of Directory Number Page 207 of 1814 Call Park It is not possible to park an Attendant Blocking of DN call. If a Call Park call recalls to a blocked DN, the recall will be treated as if the DN is in a ringing state.
Page 208 Page 208 of 1814 Attendant Blocking of Directory Number FFC Boss Secretary Filtering The FFC Boss Secretary Filtering feature will be overridden. If an Attendant Blocking of DN attempt is made for a set that has the Boss Secretary Filtering feature active, the dialed DN will be blocked if idle.
Page 209 Attendant Blocking of Directory Number Page 209 of 1814 ISDN Basic Rate Interface (BRI) Trunk Access It is possible to use the Attendant Blocking of DN feature in an ISDN MCDN based on BRI TIE trunks if Network Attendant Service (NAS) is configured in the network.
Page 210 Page 210 of 1814 Attendant Blocking of Directory Number Ring Again It is possible to activate Ring Again towards a DN that is blocked due to the Attendant Blocking of DN feature. Ringing Change Key When the SACP key (or Signal Source) key is pressed to ring a blocked SCR where the Ring Change feature is activated, an audible ring signal will always be given.
Page 211 Attendant Blocking of Directory Number Page 211 of 1814 Source Included when Attendant Dials The Attendant Blocking of DN feature will follow the current Source Included when Attendant Dialing handling, depending on what is configured. Vacant Number Routing The Attendant Blocking of DN feature will work across an ISDN network if the call is routed due to the Vacant Number Routing feature.
Page 212 Page 212 of 1814 Attendant Blocking of Directory Number xx SACP Semi-automatic Camp-on key. LD 15 – Modify the Customer Data Block. Prompt Response Description REQ: Change. TYPE: Attendant Console options. CUST Customer number. Change Attendant Console options. - SACP (NO) Semi-automatic Camp-on not allowed.
Page 213 Attendant Blocking of Directory Number Page 213 of 1814 If the dialed DN is idle, it is blocked. The DN lamp indicates a ringing state, although the DN will not ring (for PBX telephones, there is no indication that the DN is blocked.) On the Attendant Console, the SACP key lamp remains lit and the Source key lamp begins blinking.
Page 214 Page 214 of 1814 Attendant Blocking of Directory Number 553-2901-301 Standard 9.00 January 2002...
Page 215: Attendant Through Dialing Networkwide
Page 215 of 1814 Attendant Through Dialing Networkwide Contents The following are the topics in this section: Feature Description ........Operating parameters .
Page 216: Attendant Through Dialing Networkwide
Page 216 of 1814 Attendant Through Dialing Networkwide Figure 6 illustrates Attendant Through Dialing Networkwide. Figure 6 Attendant Through Dialing Networkwide Central ISDN or DASS2 any TIE trunk except DPNSS Office 553-7583 When requested, the attendant dials a specific code and extends the call once the Destination (DEST) lamp lights.
Page 217 Attendant Through Dialing Networkwide Page 217 of 1814 Table 25 shows situations when the attendant is allowed to press the Release (RLS) key depending on the type of numbering plan implemented by a customer. Table 25 Numbering Plans and Attendant Release of external trunk Numbering Plan used Destination (DEST) to seize external trunk...
Page 218 Page 218 of 1814 Attendant Through Dialing Networkwide If an attendant dials a Trunk Steering Code or Special Number over an ISDN trunk connected to a Central Office/Public Exchange, the outgoing trunk must support Overlap Signaling. Attendant Through Dialing Networkwide allows a caller to bypass all trunk access restrictions at the set level.
Page 219 Attendant Through Dialing Networkwide Page 219 of 1814 If the Calling Line Identification (CLID) option is activated in the Call Detail Recording, the calling party’s Directory Number (DN) is printed in the Attendant’s node. If End-to-End Signaling is used to establish a link, the ECDR prompt in Overlay 15 can be used to print End-to-End Signaling digits in the CDR record.
Page 220 Page 220 of 1814 Attendant Through Dialing Networkwide Speed Call Speed Call is only supported in the attendant dialing phase. Speed Call is not supported once the caller begins dialing an external number. Once an external call is established, the caller cannot press the SCU (Speed Call User) key. Stored Number Redial Digits dialed by the caller using End-to-End Signaling are not retained by the Stored Number Redial feature.
Page 221 Attendant Through Dialing Networkwide Page 221 of 1814 LD 15 – Allow Attendant Through Dialing Networkwide. Prompt Response Description REQ: Change existing data. TYPE: Attendant Console data block. CUST Customer number. (ATDA) Attendant Through Dialing Allowed (default). ATDD = Attendant Through Dialing Denied. Note: The configuration of Improved End-to-End Signaling in Overlay 15 and Calling Line Identification in Call Detail Recording Record are optional.
Page 222 Page 222 of 1814 Attendant Through Dialing Networkwide LD 17 – Allow Calling Line Identification (CLID) field in Call Detail Recording (CDR) records. Prompt Response Description Change existing data. TYPE PARM System parameters. - FCDR Format for Call Detail Recording (OLD) OLD CDR format (default).
Page 223: Australia Etsi
Page 223 of 1814 Australia ETSI Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 224 Page 224 of 1814 Australia ETSI • Circuit-mode bearer capabilities (speech, 3.1 kHz audio, 64 kbps digital, and adapted 56 kbps to 64 kbps digital) • COT, DID, DOD, and TIE trunk call types • Calling Line Identification (public and private) •...
Page 225 Australia ETSI Page 225 of 1814 MCDN Call Modification (Conference, Transfer) is not supported. Network Call Redirection, Network Call Forward, and Network Call Forward No Answer (MCDN Component) are not supported. Network Attendant Service (NAS) features are not supported across the Australia ETSI interface;...
Page 226 Page 226 of 1814 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.
Page 227 Australia ETSI Page 227 of 1814 For users of an International Numbering Plan, the Meridian 1 now supports multiple Prefix 1 (PFX1) and Prefix 2 (PFX2) contents, and multiple Home Location Codes (HLOCs) and Local Steering Codes (LSCs), on a DN or DN key basis.
Page 228 Page 228 of 1814 Australia ETSI Coordinated Dialing Plan (CDP) A Coordinated Dialing Plan (CDP) can be used to access an Australia ETSI trunk. However, neither the CDP private plan nor the CDP numbering type is supported. They get converted to unknown plan and type, respectively. Virtual Network Services (VNS) It is not possible to configure an Australia ETSI D-channel as a VNS D-channel.
Page 229 Australia ETSI Page 229 of 1814 • International Supplementary Features (SUPP) package 131 • Flexible Features Code (FFC) package 139 • Network Attendant Service (NAS) package 159 • ISDN Supplementary Features (ISDN INTL SUP) package 161 For ISDN Basic Rate Interface Trunking connectivity: •...
Page 230 Page 230 of 1814 Australia ETSI 13 LD 27 - Configure an S/T Interface (SILC) or U-Interface (UILC) line card, for an ISDN BRI trunk. 14 LD 27 - Configure a Digital Subscriber Loop (DSL) for an ISDN BRI trunk. 15 LD 27 - Assign meters to a DSL (this step is required for Advice of Charge).
Page 231 Australia ETSI Page 231 of 1814 - CTYP MSDL Multi-purpose Serial Data Link card or Downloadable D-Channel Daughterboard (Options 51C-81C). Downloadable D-Channel Daughterboard (Option 11C). - GRP Network group number (Options 81C). - DNUM 0-15 Device number for I/O ports (Options 51C-81C). All ports on the MSDL card share the same DNUM.
Page 232: Australia Etsi
Page 232 of 1814 Australia ETSI - RCAP Remote capabilities, prompted to configure the Connected Line ID Presentation supplementary service. Multiple entries are allowed if separated by a space. (COLP) CLID Presentation supported. XCOL To remove COLP. MCID Allow Malicious Call Trace XMCI Remove Malicious Call Trace.
Page 233 Australia ETSI Page 233 of 1814 LD 16 - Configure the ETSI Australian ISDN PRI2 Route Data Block. Prompt Response Description Add new data. Change existing data. TYPE Route Data Block. CUST Customer number. xx = 0-99 (Options 51C-81C). xx = 0-31 (Option 11C). ROUT 0-511 Route number (Options 51C-81C).
Page 234 Page 234 of 1814 Australia ETSI MCTS Enable MCT signaling. - MCTM (0)-30 Malicious Call Trace disconnect delay timer (this timer overrides the T306 timer for calls originating or terminating on sets with MCT Class of Service). - MTND (NO) YES (Do not) apply a Malicious Call Trace disconnect delay for tandem calls.
Page 235 Australia ETSI Page 235 of 1814 LD 17 - Configure Advice of Charge for Australia ETSI. Note: The MR package 101 must be equipped on the Meridian 1. Prompt Response Description Change existing data. TYPE PARM Change system parameters, OCAC (NO) YES (Do not) support the Original Carrier Access Code format.
Page 236 Page 236 of 1814 Australia ETSI LD 10 - Assign meters to analog (500/2500) sets. Prompt Response Description REQ: Add new data. Change existing data. TYPE: Analog set. TN address l s c u Loop, shelf, card, and unit (Options 51C-81C). Card and unit (Option 11C).
Page 237 Australia ETSI Page 237 of 1814 TN address l s c u Loop, shelf, card, and unit (Options 51C-81C). Card and unit (Option 11C). x...x ODAS Station Designator. CUST Customer number, as defined in LD 15. TGAR 0 - (1) - 30 Trunk Group Access Restriction The default of 1 automatically blocks direct access.
Page 238 Page 238 of 1814 Australia ETSI DTRK Digital trunk route. - DGTP PRI2 2.0 Mb PRI digital trunk type. ISDN Integrated Services Digital Network. - MODE ISDN PRI route. - IFC EURO EuroISDN interface. - - CNTY EAUS Australia ETSI. Include AOC information in the CDR ticket.
Page 239: Isdn Bri Configuration
Australia ETSI Page 239 of 1814 RUCF Route unit conversion factor. 0 = No conversion is required. DSPT 0-(10)-60 Charge display timer. ISDN BRI configuration LD 27 - Define a Link Access Procedure on the D-channel (LAPD) protocol group. The protocol configuration procedures define the protocols used by ISDN BRI DSLs to communicate over ISDN.
Page 240 Page 240 of 1814 Australia ETSI Prompt Response Comment - N201 4-(260) Maximum number of contiguous octets or bytes of information. (1)-32 Maximum number of outstanding negative acknowledgment (NAKs) allowed before alarming the system. PGPN <CR> Press <CR> to prevent repetition of all the parameters starting with LAPD.
Page 241 Australia ETSI Page 241 of 1814 Prompt Response Comment - IFC EURO EuroISDN interface. - - CNTY EAUS Australia ETSI. - CNEG (NO) YES (Do not) allow Channel Negotiation. OVLS (NO) YES (Do not) allow Overlap Sending. - OVLT (0)-8 Overlap Timer in seconds.
Page 242 Page 242 of 1814 Australia ETSI Prompt Response Comment - - INC_T306 0-(120)-240 Variable timer, in seconds, for received DISCONNECT message on incoming calls allowing in-band tone to be heard. The network will stop sending after this timer times out. The value is stored in two-second increments, which are rounded up.
Page 243 Australia ETSI Page 243 of 1814 LD 27 - Configure an S/T Interface (SILC) or U-Interface (UILC) line card, for an ISDN BRI trunk. Prompt Response Comment Add new data Change existing data. TYPE CARD SILC or UILC configuration. Card location (Options 51C-81C). lll (superloop) = 0-156 (must be an even number, divisible by 4) s (shelf) = 0-1...
Page 244 Page 244 of 1814 Australia ETSI Prompt Response Comment DSL Terminal Number location (Options 51C-81C). lll (superloop) = 0-156 (must be zero or a number divis ible by 4) s (shelf) = 0-1 cc (card) = 0-15 dsl# dsl# (DSL location) = 0-7 DSL Terminal Number location (Option 11C).
Page 245 Australia ETSI Page 245 of 1814 Prompt Response Comment - - T310 (30)-100 Maximum time in seconds between an incoming CALL PROCEEDING message and the next incoming message. (NO) YES (Do not) change the configuration parameters for B-Channel 1. - MEMB 1-510 Route member number.
Page 246 Page 246 of 1814 Australia ETSI LD 27 - Assign meters to a DSL (this step is required for Advice of Charge). The MR/PPM package 101 must be equipped on the Meridian 1. Prompt Response Comment Add an ISDN protocol group TYPE LAPD Protocol group DSL Terminal Number location (Options 51C-81C).
Page 247 Australia ETSI Page 247 of 1814 Prompt Response Comment DTRK BRI Digital Trunk Route BRIP ISDN BRI packet handler route (NO is entered, since packet data is not required). - DGTP Digital trunk type. ISDN Integrated Services Digital Network. - IFC EURO EuroISDN interface.
Page 248 Page 248 of 1814 Australia ETSI Prompt Response Comment RURC Route unit reference cost. (-Y) Formula is X*10 where X = 0-9999, Y = 0-3. The default value for X is the value that is entered for RUCS. RUCF Route unit conversion factor. 0 = No conversion is required.
Page 249 Page 249 of 1814 Backup D-channel Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 250: Backup D-Channel
Page 250 of 1814 Backup D-channel When Back-up D-channel is configured, one D-channel is active and the other one acts as a backup. Should the active D-channel fail, the auto-recovery software first attempts to recover the primary D-channel. If the recovery is successful, the D-channel goes back in operation.
Page 251 Backup D-channel Page 251 of 1814 Feature implementation Task summary list The following is a summary of the tasks in this section: LD 17 – Change the Configuration Record to define the Backup D-channel. Use the following procedure to define the Backup D-channel Note: Basic PRI or ISL administration must be performed before the backup D-channel is defined.
Page 252 Page 252 of 1814 Backup D-channel Table 26 Recovery to primary D-channel RCVP prompt responses RCVP = YES RCVP = NO primary D-channel up—active primary D-channel up—active backup D-channel up backup D-channel up primary D-channel down primary D-channel down backup D-channel up—active backup D-channel up—active (see below) primary D-channel up—active...
Page 253: Basic Call Service
Page 253 of 1814 Basic Call Service Contents The following are the topics in this section: Feature description ........Call progress signaling .
Page 254: Basic Call Service
Page 254 of 1814 Basic Call Service Call progress signaling ISDN PRI supports 64 Kb/s out-of-band signaling (on the D-channel) to effect: • call setup • call tear down • feature activation • local-busy and reorder tones (overflow tone is supplied locally) Both out-of-band signaling messages and in-band audible tones are provided for ringback.
Page 255 Basic Call Service Page 255 of 1814 Operating parameters There are no operating parameters associated with this feature. Feature interactions There are no feature interactions associated with this feature. Feature packaging This feature requires the following packages: • Integrated Services Digital Network (ISDN) package 145; •...
Page 256 Page 256 of 1814 Basic Call Service 553-2901-301 Standard 9.00 January 2002...
Page 257: B-Channel Overload Control
Feature operation ......... . Regional material statement This feature is only available in North America. Contact your system supplier or your Nortel Networks representative to verify support of this product in your area. Feature description...
Page 258 Page 258 of 1814 B-channel Overload Control Note: An example where this could happen would be where a telemarketing firm advertises a product by giving an 1-800 number. In response to the advertisement, the company receives a burst of incoming calls in a short period of time.
Page 259 B-channel Overload Control Page 259 of 1814 Figure 7 Before the B-channel Overload Control Timer has been applied Meridian 1 Busy destination C e n t r a O f f i c e T I M E Call Initiation No delay before Call Release (User Busy) call release...
Page 260 Page 260 of 1814 B-channel Overload Control Figure 8 After the B-channel Overload Control Timer has been applied Meridian 1 Busy destination C e n t r a l O f f i c e T I M E Call Initiation BCOT delay Start Call Disconnect sequence Call Initiation...
Page 261 B-channel Overload Control Page 261 of 1814 B-channel Overload Control Timer (BCOT) considerations Please consider the following pertaining to the application of the BCOT: • When configuring the BCOT in Overlay 16, the recommended value to be used is 256 milliseconds (most problem scenarios can be solved with this value).
Page 262 Page 262 of 1814 B-channel Overload Control Traffic measurement output For non-ISA and non-NI-2 Call By Call service routes, the TFC002 traffic measurement report has been updated for the BCOC feature as shown by Table 27. Table 27 TFC002 format for a non-ISA and non-NI-2 Call By Call routes System ID TFC002 Route Number...
Page 263: Operating Parameters
B-channel Overload Control Page 263 of 1814 Table 28 TFC002 format for an ISA service route (Part 2 of 2) Total number of activations of BCOC for this route Operating parameters This feature applies only to the following ISDN PRI to North American Central Office connectivities: •...
Page 264 Page 264 of 1814 B-channel Overload Control • incoming calls presented on a Controlled Directory Number (CDN), and being released by Customer Controlled Routing (CCR) due to a “User Busy” cause • incoming calls that are tandemed to a route whose trunk members are all busy Figure 9 Busy set is a on node interfacing directly to a Central Office...
Page 265: Feature Interactions
B-channel Overload Control Page 265 of 1814 Feature interactions Automatic Call Distribution ACD allows a large volume of calls to be made to the same DN (called the ACD DN), and answered by a group of telephones (called ACD agent positions).
Page 266 Page 266 of 1814 B-channel Overload Control Secondary DN Call Blocking Secondary DN Call Blocking blocks new incoming ACD calls to the Secondary DN of an ACD agent, so that the agent can handle a current call without interruption. The calls to the Secondary DN receive busytone. These calls that are to receive busytone will be affected by the B-channel Overload Control feature, in that a delay will be imposed on these calls before the caller receives the busytone.
Page 267 B-channel Overload Control Page 267 of 1814 Remote Virtual Queuing Since Remote Virtual Queuing interworks over a Meridian 1 to DMS interface, the B-channel Overload Control feature imposes a delay on the automatic retry capability of RVQ, which is used when congestion is encountered due to no idle trunks being available.
Page 268: Feature Packaging
Page 268 of 1814 B-channel Overload Control Network Individual Do Not Disturb This feature allows extends the functionality of the Individual Do Not Disturb feature to a network environment. If a DN is in the Do Not Disturb mode, calls may be made from it, but incoming calls to it would receive Intercept treatment.
Page 269: Feature Operation
B-channel Overload Control Page 269 of 1814 - IFC Supported interface types. D100 D100 = DMS-100 D250 D250 = DMS-250 S100 S100 = SL100 ESS4 ESS4 = Lucent 4ESS ESS5 ESS5 = Lucent E5SS NI2 = National ISDN-2 - - BCOT (0)-4000 The value for the B-channel Control timer, in milliseconds.
Page 270 Page 270 of 1814 B-channel Overload Control 553-2901-301 Standard 9.00 January 2002...
Page 271: Break-In Features
Page 271 of 1814 Break-in Features Contents The following are the topics in this section: Feature description ........Break-in busy indication and prevention .
Page 272 Page 272 of 1814 Break-in Features Feature description The Break-in (BKI) feature allows an attendant to interrupt an established call in order to connect an important incoming call to one of the established parties. For a description of the basic Break-in feature, refer to Features and Services (553-3001-306).
Page 273 Break-in Features Page 273 of 1814 Break-in prevention With the Break-In to External Call Denied option (BIXD option), break-in to a party involved in an external call is temporarily denied. This applies to both pre-dial and post-dial break-in operations. Break in with secrecy The Break In With Secrecy (BKIS) feature enhances the operation of the Break In (BKI) feature.
Page 274 Page 274 of 1814 Break-in Features Feature interactions Feature interactions for the Break-In and Network Attendant Service Break-In features also apply to this feature. With the Break-In to Line Lockout Set product improvement, the appropriate busy indication is supported. If the Break-In to Line Lockout Set Denied option (option BLD) was set for the customer, attempts at break-in results in Temporarily Denied—1 status.
Page 275 Break-in Features Page 275 of 1814 The following is a list of treatments for different circumstances: • Existing BKI BIEC disconnects undesired parties when the desired party goes on-hook, except for analog (500/2500 type) sets where overflow is given. Therefore Meridian digital and SL-1 sets and trunks are disconnected.
Page 276 Page 276 of 1814 Break-in Features Display In all cases, when displays are equipped, the information displayed is consistent with current operation (i.e., when connected to only one party, the display shows the number and name, if equipped and configured, of that party, and when connected to more than one party, the display is blank).
Page 277 Break-in Features Page 277 of 1814 LD 15 - Modify Multi-Party Operations data in Customer Data Block if MPO package 141 is equipped. LD 20 – When the Attendant Console data block is printed the BKI key information is output. LD 21 –...
Page 278 Page 278 of 1814 Break-in Features 0-19 BKI Key number assigned to Break-in. LD 15 - Modify Multi-Party Operations data in Customer Data Block if MPO package 141 is equipped. Prompt Response Description REQ: Request: Modify or create data block. TYPE: Multi-Party Operations.
Page 279 Break-in Features Page 279 of 1814 - - RCY2 1-(4)-15 Number of Cycles of Ringing before forwarding to transferring station - - ACNS (NO) ALL EXT Attendant Clearing during Night Service - - RALL (NO) YES Mandatory recall is required prior to dialing control digits - - CDTO 2-(14) Control digit timeout;...
Page 280 Page 280 of 1814 Break-in Features The scenario is as follows: Party A calls the attendant, the attendant calls party B who is talking to party C. The attendant presses the BKI key to intrude into the conversation. At this point, the attendant and both parties B and C are in conversation with intrusion tone provided, while party A is on HOLD (with music if EMUS, package 119, is equipped).
Page 281 Break-in Features Page 281 of 1814 Attendant presses Break-in key again The BKIS feature allows the attendant to press the BKI key again in order to exclude the undesired party C (who continues to hear intrusion tone) and to talk directly to the desired party B without intrusion tone. The BKI indicator, which was active, flashes at 60 impulses per minute (ipm).
Page 282 Page 282 of 1814 Break-in Features Release The attendant presses the RLS key to apply Camp-on. If Camp-on or Call Waiting is available, parties B and C are reconnected and party A is released and either Camp-on or Call Waiting is applied to the wanted party A. The BKI indicator is off.
Page 283 Break-in Features Page 283 of 1814 AOCS set to ATN for party C If AOCS is set to ATN for party C, then party C is routed to the attendant while B is re-rung by the attendant. The BKI indicator goes off and the attendant hears ring back and the DEST indicator winks at 30 ipm.
Page 284 Page 284 of 1814 Break-in Features An external call is on the source and neither Camp-on nor Call Waiting is possible at the wanted station (i.e., Camp-on or Call Waiting not possible or the station already has a call camped on). The desired station is busy with Call Forward active and the attendant initiated a predial Break-in.
Page 285 Break-in Features Page 285 of 1814 While in this state, the following situations can occur: Attendant actions Break-in The attendant may press the flashing BKI key. The original conference is reestablished with intrusion tone. The BKI indicator reverts to active. Exclude Destination The attendant may press the EXCL DEST key to return to the incoming call.
Page 286 Page 286 of 1814 Break-in Features Desired party action At this point, if party B goes on-hook, party B is re-rung by the attendant and the conferees are left in conference without party B and without intrusion tone. The BKI indicator goes off, the attendant hears ringback tone, and the DEST indicator winks at 30 ipm.
Page 287 Break-in Features Page 287 of 1814 Table 29 Summary of possible Break-in situations and indications (Part 2 of 2) 7Ignored b) Predial WINK ringback station is rung 8Invalid post-dial or overflow predial 9Break-in after post-dial or ACTIVE or FLASH no tone with Secrecy predial, active FLASH...
Page 288 Page 288 of 1814 Break-in Features 553-2901-301 Standard 9.00 January 2002...
Page 289: Bri/Pri Basic Call Interworking
Page 289 of 1814 BRI/PRI Basic Call Interworking Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 290 Page 290 of 1814 BRI/PRI Basic Call Interworking The affected IEs are: • Bearer Capability BRI and PRI propagate octet 4ab without modification. • Called party subaddress Meridian 1 decodes and saves the called party subaddress when it is received from PRI, passing it to the terminating BRI. The system also sends the subaddress to PRI when the originating BRI or PRI includes it.
Page 291 BRI/PRI Basic Call Interworking Page 291 of 1814 A call with new Bearer Capability encodings will only terminate to a BRI terminal. If the terminating terminal is not a BRI terminal, the call is blocked. Voice calls are successful between BRI and PRI with no restrictions. Feature interactions The following feature interactions are unique to BRI/PRI basic data call interworking.
Page 292 Page 292 of 1814 BRI/PRI Basic Call Interworking Feature implementation Task summary list The following is a summary of the tasks in this section: LD 17 – Configure far-end BRI support LD 22– Print the configuration record LD 17 – Configure far-end BRI support Prompt Response Description...
Page 293 Page 293 of 1814 BRI Trunks with Night Service Enhancement Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 294: Bri Trunks With Night Service Enhancement
Page 294 of 1814 BRI Trunks with Night Service Enhancement B-channels transmit user voice and data information at high speeds, while D-channels are packet-switched links that carry call set-up, signaling and other user data across the network. One single DSL can carry two simultaneous voice or data conversations, to the same or to different locations.
Page 295 BRI Trunks with Night Service Enhancement Page 295 of 1814 The Auto Terminate DN (ATDN) prompt appears in Overlay 14 when the following conditions apply: • Auto Terminate is enabled (AUTO = YES) in Overlay 16. • The BRI trunk is defined as a DID, CO, or TIE trunk in Overlay 27. Note: In this case, neither the NITE prompt nor the NGRP prompt appears in Overlay 27.
Page 296 Page 296 of 1814 BRI Trunks with Night Service Enhancement Feature interactions For line access, Succession BRI is compliant with CCITT, ANSI, ETSI NET-3 (EuroISDN), INS NET-64 (Japan D70), National ISDN-1, 1TR6, Numeris VN2, and EuroISDN standards. Succession BRI trunks connect to local exchanges that support Numeris VN3, 1TR6, ETSI NET-3 (EuroISDN), INS NET-64 (Japan D70), and Asia-Pacific protocols.
Page 297 BRI Trunks with Night Service Enhancement Page 297 of 1814 LD 27 – Define a Night Service DN when ENS is disabled in Overlay 15. Prompt Response Description Change existing data. TYPE Digital Subscriber Loop Data Block c dsl Digital Subscriber Loop address APPL Application type for this DSL BRIE...
Page 298 Page 298 of 1814 BRI Trunks with Night Service Enhancement Prompt Response Description NITE x...x Night Service Directory Number This DN can have up to four digits, or up to seven digits with Directory Number Expansion (DNXP) package 150. You can enter a Group Hunt Pilot DN at this prompt. The DN that you enter here takes precedence over the NITE and NIT1-NIT4 prompts in LD 15.
Page 299 BRI Trunks with Night Service Enhancement Page 299 of 1814 Prompt Response Description APPL Application type for this DSL BRIE Basic Rate Interface protocol engine BRIE supports the QSIG and EuroISDN interfaces, and requires BRIT package 233. Any changes in the DSL route must match the BRIE loadware application.
Page 300 Page 300 of 1814 BRI Trunks with Night Service Enhancement 553-2901-301 Standard 9.00 January 2002...
Page 301: Diversion
Page 301 of 1814 Business Networking Express/EuroISDN Call Diversion Contents The following are the topics in this section: Regional material statement ....... . . Feature description .
Page 302: Business Networking Express/Euroisdn Call Diversion
Business Networking Express/EuroISDN Call Diversion Regional material statement ISDN BRI trunking is not available in North America. Contact your system supplier or your Nortel Networks representative to verify support of this product in your area. Feature description Business Networking Express (BNE) is a term that refers to a group of EuroISDN network functionalities.
Page 303 Business Networking Express/EuroISDN Call Diversion Page 303 of 1814 Figure 11 Example of a network where BNE is useful EuroISDN Meridian 1 PSTN EuroISDN Meridian 1 EuroISDN Meridian 1 This chapter provides information about the EuroISDN Call Diversion aspect of the BNE package. For information about the other BNE features, refer to the Business Network Express/EuroISDN Name and Private Number Display and Business Network Express/EuroISDN Explicit Call Transfer feature modules in this book.
Page 304 Page 304 of 1814 Business Networking Express/EuroISDN Call Diversion This chapter uses the terms served user or served telephone. These terms refer to the telephone that is diverting calls to another telephone in the network. Figure 12 shows the component parts and terms used in the Call Diversion environment.
Page 305: Redirection Services
Business Networking Express/EuroISDN Call Diversion Page 305 of 1814 Redirection services The CFU service enables the network to redirect all calls, addressed to the ISDN number of a served telephone, to another telephone in the network. The CFU supplementary service does not affect the served user’s ability to originate calls.
Page 306: Class Of Service
Page 306 of 1814 Business Networking Express/EuroISDN Call Diversion Class of Service The Class of Service (CLS) of the served telephone affects the notification that the calling telephone and the final destination telephone receive. Tables 31 and 33 shows a summary of the relationships. Table 31 Relationship between the served user’s CLS and the calling user’s notification...
Page 307 Business Networking Express/EuroISDN Call Diversion Page 307 of 1814 Table 32 Examples of calling user’s display related to the served user’s CLS (Part 2 of 2) 0164665000 0164665000 Yes without diverted-to-number 0164665000 F 0164665000 F Yes with diverted-to-number 00164665000 F 0164666000 F Table 33 Relationship between the served user’s Class of Service and the notification on the final...
Page 308: Multiple Diversions
Page 308 of 1814 Business Networking Express/EuroISDN Call Diversion Multiple Diversions For the purpose of discussion, assume that the following events occur: Originating user A calls B1. B1 has activated CFU, CFB or CFNR to B2. B2 has activated diversion to B3. B3 has activated diversion to the next telephone.
Page 309: Procedures For Interworking With Private Isdns
Business Networking Express/EuroISDN Call Diversion Page 309 of 1814 • any CLS information related to “notify the calling user of diversion” received contains the value “Yes with diverted-to number” • any diverted-to-number information (the presentation indicator of the Redirecting Number IE) received allows the display of the diverted-to-number The last diverted-to-number replaces the previous one.
Page 310 Page 310 of 1814 Business Networking Express/EuroISDN Call Diversion Figure 14 Rerouting takes place in the public network Call Forward Diverted-to-user EuroISDN user PSTN Served Meridian 1 user B Calling user Basic Call The Rerouting request sent by the Meridian 1 contains the following information: •...
Page 311 Business Networking Express/EuroISDN Call Diversion Page 311 of 1814 — “PresentationAllowedNumber” if the served user’s CLS = DNDY — “PresentationRestricted” if the served user’s CLS = DNDN — “NumberNotAvailableDueToInterworking” - if the gateways perform this service • the calling party subaddress, if available •...
Page 312 Page 312 of 1814 Business Networking Express/EuroISDN Call Diversion • the calling user notification information that depends on the served user’s CLS (see Table 31, “Relationship between the served user’s CLS and the calling user’s notification,” on page 306) • the diverted-to user’s number For CFU or CFB, when the diverted-to-telephone starts ringing, an ALERT message that includes Diversion Notification Information DLI3...
Page 313: Call Forward
Business Networking Express/EuroISDN Call Diversion Page 313 of 1814 Figure 16 The calling and served users are in the public network and the diverted-to-user is on the Meridian 1 Served user B Diverted-to-user C Call Forward Basic EuroISDN user PSTN Meridian 1 Calling user A When the Meridian 1 receives a DivertingLegInformation 2 (DLI2) APDU,...
Page 314 Page 314 of 1814 Business Networking Express/EuroISDN Call Diversion Figure 17 The calling and served users are on the Meridian 1 and the diverted-to-user is in the public network Diverted-to user C Call Forward Served user B EuroISDN user PSTN Basic Call Meridian 1...
Page 315 Business Networking Express/EuroISDN Call Diversion Page 315 of 1814 A call from the Meridian 1 is diverted within the public ISDN Figure 18 illustrates an example of interworking. In this illustration, the calling user A, on a Meridian 1, makes a call through a EuroISDN link to the served user B in the public network.
Page 316: Qsig, Mcdn And Dpnss Gateways
Page 316 of 1814 Business Networking Express/EuroISDN Call Diversion The PSTN can send a Notification Indicator IE and Redirection Number IE instead of DLI1 and DLI3. If this happens, the display on the originating telephone is updated when the system receives these IEs, the same way it does when it receives DLI1 and DLI3 messages.
Page 317 Business Networking Express/EuroISDN Call Diversion Page 317 of 1814 Node I Gateways (A/B) The following gateways can exist between the Originating user node and the Served user node (refer to Figure 19): • QSIG/EuroISDN and EuroISDN/QSIG Because the messaging is the same for both protocols, the DLI1 and DLI3 APDUs are sent in the same message format as they were received •...
Page 318 Page 318 of 1814 Business Networking Express/EuroISDN Call Diversion • EuroISDN/DPNSS The diversion information (if available) received at the gateway on the DPNSS link is contained in the NAM message (for CFU and CFB) or the EEM message (for CFNR). Since DPNSS does not support Presentation Indication, all diversion information received on the DPNSS link is mapped into DLI1 information and sent on the EuroISDN link within a FACILITY...
Page 319 Business Networking Express/EuroISDN Call Diversion Page 319 of 1814 • EuroISDN/MCDN The call establishment message (SETUP) is not impacted by the gateway and is sent with the Diversion information. DLI1 and DLI3 are both sent in a FACILITY message. The FACILITY message sending is triggered by the reception of the NOTIFY message on MCDN.
Page 320 Page 320 of 1814 Business Networking Express/EuroISDN Call Diversion • MCDN/EuroISDN The call establishment message is mapped with the relevant information (DLI2 diversion information is included in the SETUP message on the EuroISDN link). Once the gateway receives the DLI3 diversion information, it propagates the redirection information by sending a NOTIFY message on the MCDN link.
Page 321: Message Mapping For Rerouting Method
Business Networking Express/EuroISDN Call Diversion Page 321 of 1814 • EuroISDN/DPNSS The call establishment message is mapped with the relevant information (Diversion information is included in the ISRM message on the DPNSS link). As soon as a NAM is received on the DPNSS link, it is mapped into an ALERTING message with DLI3 Diversion information (presentation always allowed).
Page 322 Page 322 of 1814 Business Networking Express/EuroISDN Call Diversion Rerouting request received at the originating node When a valid rerouting request is received on either a QSIG, MCDN or DPNSS interface, and the generation of a new call on the EuroISDN is necessary (due to the rerouting), a DLI2 APDU is included within the SETUP message sent on EuroISDN.
Page 323 Business Networking Express/EuroISDN Call Diversion Page 323 of 1814 If the diverted-to user is located within the private network, the request is processed by the gateway node. Figure 22 Call rerouting request processed at the gateway node. Served Originating user user First Call Private...
Page 324: Operating Parameters
Page 324 of 1814 Business Networking Express/EuroISDN Call Diversion Operating parameters Table 34 summarizes the correspondence between the ETSI reason for diversion supported by this feature, and the Meridian 1 equivalent features. Table 34 Correspondence between the ETSI reason for diversion names and the Meridian 1 features ETSI reason for Meridian 1 features...
Page 325 Business Networking Express/EuroISDN Call Diversion Page 325 of 1814 The BNE/EuroISDN Call Diversion feature has the following limitations: • The served user does not receive an indication when a call is diverted. • The calling user is notified each time a redirection occurs, if information is provided by the network.
Page 326 Page 326 of 1814 Business Networking Express/EuroISDN Call Diversion — Yes without diverted-to-number — Yes with diverted-to-number (when available). Due to the limitation of the number of digits that a digital telephone can display, only the diverted-to number displays, when available, on the calling telephone.
Page 327 Business Networking Express/EuroISDN Call Diversion Page 327 of 1814 • The served user can release their number to the diverted-to-user. There are two possible values: No, Yes. Due to the limitation of the number of digits that a digital telephone can display, only the calling number displays on the diverted-to-telephone, independent of the served user’s Class of Service.
Page 328: Feature Interactions
Page 328 of 1814 Business Networking Express/EuroISDN Call Diversion If a call from the public ISDN is diverted within the Meridian 1 and a reject component is received from the CO, the Meridian 1 accepts this information and continues to establish the call. If a diverted call is presented from a public ISDN to the Meridian 1 and a reject component is received from the CO, the Meridian 1 accepts this information and continues to establish the call.
Page 329 Business Networking Express/EuroISDN Call Diversion Page 329 of 1814 Call Forward Option The active Class of Service is always the served user’s Class of Service. The EuroISDN Call Diversion feature is not affected by the OPT configuration (CFO/CFF) in the served user’s Customer Data Block. Call Waiting Redirection The Call Waiting Redirection (CWTR) feature allows unanswered calls in the Call Waiting state to be redirected using Call Forward No Answer (CFNA).
Page 330: Networking Feature Interactions
Page 330 of 1814 Business Networking Express/EuroISDN Call Diversion This feature is not supported by EuroISDN Call Diversion. A Meridian 1 user can neither originate nor receive a call by using the FFC for CFHO through EuroISDN. Access restrictions / trunk group access restrictions EuroISDN Call Diversion is not performed if the served user is not able to access the route to the diverted-to-node.
Page 331: Feature Packaging
Business Networking Express/EuroISDN Call Diversion Page 331 of 1814 Meridian Mail A call diverted to Meridian Mail through EuroISDN can access Meridian Mail functionalities (such as message reception and mailbox interrogation) in the same way as a simple call to the mailbox. Feature packaging The following software packages are required for this feature to operate on EuroISDN BRI Trunks:...
Page 332: Feature Implementation
Page 332 of 1814 Business Networking Express/EuroISDN Call Diversion Feature implementation Task summary list The following is a summary of the tasks in this section: LD 10 – Configure Analog (500/2500 type) set for EuroISDN Call Diversion notification. LD 11 – Configure digital telephone for EuroISDN Call Diversion notification.
Page 333 Business Networking Express/EuroISDN Call Diversion Page 333 of 1814 Class of Service. DN01 Call Diversion: No notification to the calling user. DN02 Call Diversion: Notification without diverted-to-number to the originating user. (DN03) Call Diversion: Notification with diverted-to-number to the originating user. DNDN Call Diversion: no served user’s number notification to the diverted-to-user.
Page 334 Page 334 of 1814 Business Networking Express/EuroISDN Call Diversion x..x Call Forward No Answer DN (for internal calls if Call Forward by Call Type is active). DN01 Call Diversion: No notification to the calling user. DN02 Call Diversion: Notification without diverted-to-number to the originating user.
Page 335 Business Networking Express/EuroISDN Call Diversion Page 335 of 1814 x..x External Flexible Call Forward No Answer DN. HUNT x..x Hunt DN. x..x External Hunt DN. LD 27 – Configure BRI telephone for EuroISDN Call Diversion notification. Prompt Response Description Change. TYPE Terminal Service Profile.
Page 336 Page 336 of 1814 Business Networking Express/EuroISDN Call Diversion SSRV_ ETSI Supplementary Service. Prompted if PRID = 2 (ETSI) ETSI in the DSL. VCFW Voice Call Forward. VCFW is valid if CT = VCE or if CT = VCE and DTA. DCFW Data Call Forward.
Page 337: Feature Operation
Business Networking Express/EuroISDN Call Diversion Page 337 of 1814 CNTY aaaa All countries that are supported by the E403 interface: ETSI, AUS, DEN, FIN, GER, ITA, NOR, POR, SWE, DUT, EIR, SWI, ESP, UK, BEL, FRA, CIS. RCAP DV3I EuroISDN Call Diversion. LD 17 –...
Page 338 Page 338 of 1814 Business Networking Express/EuroISDN Call Diversion 553-2901-301 Standard 9.00 January 2002...
Page 339: Regional Material Statement
Feature operation ......... . Regional material statement ISDN BRI trunking is not available in North America. Contact your system supplier or your Nortel Networks representative to verify support of this product in your area. International ISDN PRI Feature description and administration...
Page 340: Business Networking Express/Euroisdn Explicit Call Transfer
Page 340 of 1814 Business Networking Express/EuroISDN Explicit Call Transfer Feature description Business Networking Express Business Networking Express (BNE) is a Virtual Private Network (VPN) solution for connecting several Meridian 1 systems through a EuroISDN interface. The BNE solution is a mix of EuroISDN public services and select Meridian 1 proprietary features.
Page 341: Bne/Euroisdn Explicit Call Transfer
Business Networking Express/EuroISDN Explicit Call Transfer Page 341 of 1814 BNE/EuroISDN Explicit Call Transfer While Call Transfer functionality exists on EuroISDN with the X11 software feature “Call Transfer”, this feature extends the functionality of the private network: • to notify the public network that a transfer has occurred within the private network •...
Page 342 Page 342 of 1814 Business Networking Express/EuroISDN Explicit Call Transfer Figure 24 Served User A is the only one in the Meridian 1 private network (or stand alone Meridian 1 EuroISDN EuroISDN Meridian 1 Meridian 1 PSTN EuroISDN Meridian 1 Figure 25 Served user A is the only one in the Meridian 1 private network.
Page 343 Business Networking Express/EuroISDN Explicit Call Transfer Page 343 of 1814 Figure 26 User A and user B or C are in the Meridian 1 private network B or C Meridian 1 EuroISDN EuroISDN PSTN Meridian 1 B or C Figure 27 User A and user B or C are in the Meridian 1 private network.
Page 344 Page 344 of 1814 Business Networking Express/EuroISDN Explicit Call Transfer Figure 28 User A and user B or C are in the Meridian 1 private network. The Meridian 1 acts as a gateway node and a served node. B or C EuroISDN MCDN EuroISDN...
Page 345: Call Transfer Through The Pstn
Business Networking Express/EuroISDN Explicit Call Transfer Page 345 of 1814 Figure 30 Remote user B or C is in the Meridian 1 private network. The Meridian 1 acts as a gateway. Meridian 1 MCDN EuroISDN Private Network QSIG EuroISDN PSTN DPNSS Meridian 1 EuroISDN...
Page 346 Page 346 of 1814 Business Networking Express/EuroISDN Explicit Call Transfer With an Unsupervised transfer, the transfer (by join) is first completed on the Meridian 1, and notifications are sent to the PSTN. The Meridian 1 waits until both calls are in an established call state. When both calls are established, and all the conditions are met, the Meridian 1 invokes Explicit Call Transfer in the PSTN.
Page 347: Call Transfer Notification Display
Business Networking Express/EuroISDN Explicit Call Transfer Page 347 of 1814 Call Transfer Notification Display If the network provides the information, the originating caller is notified, on the display of the telephone, when a transfer occurs. This means that: • if a previous Call Transfer notification was provided, it is replaced by the last received notification.
Page 348 Page 348 of 1814 Business Networking Express/EuroISDN Explicit Call Transfer Figure 31 User B calls user A. User A transfers call to user C. Served User DN 0466312020 A transfers call to C Originating User Served Transferred-to User DN 0141037474 Meridian 1 DN 0164767620 EuroISDN...
Page 349 Business Networking Express/EuroISDN Explicit Call Transfer Page 349 of 1814 Figure 33 User A presses Call Transfer key and calls user C A presses Call Transfer key and calls C User A User C 0141037474 0164767620 Called user’s DN Calling user’s DN Figure 34 User A presses Call Transfer key a second time to transfer the call to user C A presses Call Transfer key a second time to transfer call...
Page 350 Page 350 of 1814 Business Networking Express/EuroISDN Explicit Call Transfer • CNDA – Calling Name Display Allowed • CNDD – Calling Name Display Denied. Note: The reason is displayed on a telephone only when the CNDA Class of Service is configured. Transferred and Transferred-to users’...
Page 351 Business Networking Express/EuroISDN Explicit Call Transfer Page 351 of 1814 Table 37 on page 351 identifies the originating user’s notification according to the originating and transferred-to users’ configuration options. Table 37 Originating and Transferred-to users’ notification in a Meridian 1 environment (Part 1 of 2) Originating user’s dis- Transferred-to user’s display Originating user...
Page 352: Operating Parameters
Page 352 of 1814 Business Networking Express/EuroISDN Explicit Call Transfer Table 37 Originating and Transferred-to users’ notification in a Meridian 1 environment (Part 2 of 2) Originating user’s dis- Transferred-to user’s display Originating user Transferred-to play after receipt of after receipt of originating telephone B user Transferred-to user’s...
Page 353: Feature Interactions
Business Networking Express/EuroISDN Explicit Call Transfer Page 353 of 1814 — MSDL card (NT6D80AA) on Options 51C, 61C, and 81C — Clock Controller (QPC775E) for large systems • ISDN Basic Rate Interface • SILC card (NT6D70BA) for layer 1 interface •...
Page 354: Networking Feature Interactions
Page 354 of 1814 Business Networking Express/EuroISDN Explicit Call Transfer Networking feature interactions BNE/EuroISDN Name and Private Number display BNE Name and Private number information can not be carried out in EuroISDN Explicit Call Transfer Notifications. If an incoming EuroISDN call with the BNE name information and the private CLID is being forwarded through EuroISDN, after Call Transfer occurs, the BNE information name and number are replaced on the display and the notification numbers provided...
Page 355: Feature Implementation
Business Networking Express/EuroISDN Explicit Call Transfer Page 355 of 1814 • Basic Rate Interface (BRI) 216 • Multipurpose Serial Data Link (MSDL) package 222 • ISDN BRI Trunk Access (BRIT) 233 • EuroISDN (EURO) package 261 • Business Networking Express (BNE) package 367 Feature implementation Task summary list The following is a summary of the tasks in this section:...
Page 356 Page 356 of 1814 Business Networking Express/EuroISDN Explicit Call Transfer LD 11 – Configure a Meridian 1 proprietary telephone for EuroISDN Call Transfer. Prompt Response Description REQ: Change. TYPE: aaaa Telephone type l s c u Terminal Number. For Option 11C. Class of Service.
Page 357 Business Networking Express/EuroISDN Explicit Call Transfer Page 357 of 1814 LD 17 – Configure EuroISDN Call Transfer on PRI2. Prompt Response Description Change. TYPE ADAN ADAN Data Block. ADAN Action Device and Number. NEW aaa x Add I/O device. Where: aaa = type, x = port CHG aaa x Change I/O device.
Page 358: Feature Operation
Page 358 of 1814 Business Networking Express/EuroISDN Explicit Call Transfer Interface type for D-channel. E403 EuroISDN interface for ETS 300 403. EURO EuroISDN interface. CNTY xxxx Country. Note: Countries that support the E403 interface. RCAP Remote Capabilities. Add Call Transfer notification. ECTO Add Call Transfer notification and invocation.
Page 359: Regional Material Statement
Features and Services (553-3001-306) Regional material statement ISDN BRI trunking is not available in North America. Contact your system supplier or your Nortel Networks representative to verify support of this product in your area. International ISDN PRI Feature description and administration...
Page 360: Business Networking Express/Name And Private Number Display
Page 360 of 1814 Business Networking Express/Name and Private Number Display Feature description Business Networking Express (BNE) is a term that refers to a group of different EuroISDN network functionalities. The BNE capabilities provide Meridian 1 systems that are connected on a EuroISDN public network with the following functionalities: •...
Page 361 Business Networking Express/Name and Private Number Display Page 361 of 1814 Figure 35 Example of a network where BNE is useful Meridian 1 EuroISDN northern telecom Headquarter Offices PUBLIC NETWORK EuroISDN EuroISDN Meridian 1 Meridian 1 distant small distant site small northern site...
Page 362: Name Display On Euroisdn
Page 362 of 1814 Business Networking Express/Name and Private Number Display Consistent with MCDN and QSIG networking, the letter H is displayed in front of the private number. You can implement restrictions on displaying the name and number of the calling, called, or connected party.
Page 363 Business Networking Express/Name and Private Number Display Page 363 of 1814 CNIP does not deliver the calling user’s name to the called user if: • the Calling Party Name is not available. This occurs when a name is not configured in the CPND data block for the calling party DN, or in the case of interworking.
Page 364 Page 364 of 1814 Business Networking Express/Name and Private Number Display 2. Connected Name Identification Presentation (CONP) This is a service offered to the calling user. CONP provides the calling user with the alerted/connected user’s name. CONP service also delivers: •...
Page 365 Business Networking Express/Name and Private Number Display Page 365 of 1814 Note: The alerted name carried in the NOTIFY message (RCAP = ND2) is not provided to the originator because UUS1 doesn’t define any message to tandem this information. The connected (or alerting) user’s name delivered by the BNE feature is sent to the MCDN network.
Page 366: Private Calling Number On Euroisdn
Page 366 of 1814 Business Networking Express/Name and Private Number Display CNIR — EuroISDN/QSIG Gateway When a user invokes the CNIR service, the calling, alerting, and connected names are marked as “presentation is restricted”, and this indication is passed to the other network. CNIR —...
Page 367 Business Networking Express/Name and Private Number Display Page 367 of 1814 The following two services are supported: 1. Calling Line Identification Presentation (CLIP) CLIP provides the called party with the identification of the calling party in a form that allows the called party to return the call, if desired, using the VPN network built on the public EuroISDN connections.
Page 368 Page 368 of 1814 Business Networking Express/Name and Private Number Display ‘H’ is not displayed in the private number on the DPNSS side, according to the existing DPNSS gateway. 2. Calling Line Identification Restriction (CLIR) This service enables the calling party to prevent presentation of the calling number on the called user’s telephone.
Page 369: Private Connected Number On Euroisdn
Business Networking Express/Name and Private Number Display Page 369 of 1814 CLIR — EuroISDN/QSIG Gateway When the CLIR service is invoked, the calling number is marked as “presentation is restricted”, and this indication is passed to the other network. CLIR — EuroISDN/MCDN Gateway When the CLIR service is invoked, the calling number is marked as “presentation is restricted”, and this indication is passed to the other network.
Page 370 Page 370 of 1814 Business Networking Express/Name and Private Number Display • the DN digits of the connected telephone prefixed by an LSC (CDP) or HLOC (UDP), if configured • presentation flag to allow or deny the display on the calling user’s telephone Two different services are supported: 1.
Page 371 Business Networking Express/Name and Private Number Display Page 371 of 1814 COLP — EuroISDN/DPNSS Gateway The connected number, delivered by the BNE feature, is sent to the DPNSS network. The connected number, provided by the DPNSS network, is sent over EuroISDN to the originator of the call. ‘H’...
Page 372 Page 372 of 1814 Business Networking Express/Name and Private Number Display • attendant: COLR is not provided • BRI telephones: Table 39 summarizes the possibilities: Table 39 Reception of COLP on BRI telephones presentation of the COLP IE transmitted to the calling BRI COLP TRANS Connected Number IE...
Page 373: Operating Parameters
Business Networking Express/Name and Private Number Display Page 373 of 1814 Operating parameters The hardware requirements for BRI Trunk (BRIT) access are: • NT6D73AA MISP • NT6D70BA SILC • NT6D71AA UILC The hardware requirements for PRI2 are: • 2.0 Mb NT8D72 PRI card with either one of the following cards for handling the D-channel: —...
Page 374: Feature Interactions
Page 374 of 1814 Business Networking Express/Name and Private Number Display Basic Rate Interface (BRI) telephones cannot have names displayed but they can send a name to a called telephone. If the called telephone is busy, BNE/Name and Private Number Display does not operate.
Page 375 Business Networking Express/Name and Private Number Display Page 375 of 1814 The CNIR supplementary service takes precedence over the CONP supplementary service. COLR and COLP The COLR supplementary service takes precedence over the COLP supplementary service. CLIR and COLR The same Class of Service controls the CLIR and COLR services. If a user has presentation restricted configured, the number is sent to the other party with the presentation flag set to restricted for incoming and outgoing calls.
Page 376 Page 376 of 1814 Business Networking Express/Name and Private Number Display Figure 37 Local Call Transfer Meridian 1 EuroISDN EuroISDN Meridian 1 Public network northern telecom northern telecom Set C Set B transfers to C Set A calls B Transfer on ringing (internal) Figure 37 illustrates a local transfer of an incoming EuroISDN call that has BNE Name information and a private CLID.
Page 377 Business Networking Express/Name and Private Number Display Page 377 of 1814 Figure 38 External Call Transfer Meridian 1 Meridian 1 EuroISDN EuroISDN Public network northern northern telecom telecom Set B transfers to C Set C Set A calls B Transfer on ringing (external) Figure 38 illustrates the transfer of a local call over the EuroISDN network to telephone C.
Page 378 Page 378 of 1814 Business Networking Express/Name and Private Number Display Figure 39 Local Conference Meridian 1 Meridian 1 EuroISDN EuroISDN Public network northern northern telecom telecom Station A calls B Set B Set C Conferences with C Figure 39 illustrates an incoming EuroISDN call that has BNE Name information and a private CLID which is conferenced locally.
Page 379 Business Networking Express/Name and Private Number Display Page 379 of 1814 Figure 40 Local Call Forward Meridian 1 EuroISDN EuroISDN Meridian 1 Public network northern telecom northern telecom Set C Set A calls B Set B forwards to C Call Forward All Calls (internal) Figure 40 illustrates an incoming EuroISDN call that has BNE Name information and a private CLID which forwards all calls to a local telephone.
Page 380 Page 380 of 1814 Business Networking Express/Name and Private Number Display Figure 41 External Call Forward Meridian 1 EuroISDN EuroISDN Meridian 1 Public network northern telecom northern telecom Set C Set B forwards to C Set A calls B Call Forward All Calls (external) A local call can forward over a EuroISDN network, as shown in Figure 41.
Page 381 Business Networking Express/Name and Private Number Display Page 381 of 1814 Hunting/Group Hunt Figure 42 illustrates a local Hunting situation. Figure 42 Local Hunting Meridian 1 EuroISDN EuroISDN Meridian 1 Public network northern telecom northern telecom Set C Set B busy, Set A calls B call hunts to C Figure 42 illustrates an incoming EuroISDN call with BNE Name...
Page 382 Page 382 of 1814 Business Networking Express/Name and Private Number Display Figure 43 AOC and Charge Display Meridian 1 EuroISDN Meridian 1 EuroISDN Public network northern telecom northern telecom Set B Set A calls B An outgoing EuroISDN call, carrying BNE signaling, as shown in Figure 43, is charged by the Central Office.
Page 383: Networking Feature Interactions
Business Networking Express/Name and Private Number Display Page 383 of 1814 Networking feature interactions Call Diversion (diversion notification sent): Call Forward All Calls (Call Forward Unconditional) Figure 44 illustrates an incoming EuroISDN call that has BNE Name information and a private CLID forwarding all calls to telephone C over the EuroISDN network.
Page 384: Feature Packaging
Page 384 of 1814 Business Networking Express/Name and Private Number Display Figure 45 Call Transfer across a network Meridian 1 EuroISDN Meridian 1 EuroISDN Public network northern telecom northern telecom EuroISDN Meridian 1 Set C Set A calls B northern telecom Set B transfers call to Set C Explicit Call Transfer (Call Transfer notification sent)
Page 385 Business Networking Express/Name and Private Number Display Page 385 of 1814 • Basic Rate Interface (BRI) package 216 • Basic Rate Trunk Application (BRIT) package 233 • EuroISDN (EURO) package 261 • Business Networking Express (BNE) package 367 • and at least one of the following three packages: —...
Page 386: Feature Implementation
Page 386 of 1814 Business Networking Express/Name and Private Number Display The following software packages are required for Business Networking Express Private CLID and COLP: • Digit Display (DDSP) package 19 • Flexible Feature Code (FFC) package 139 • Calling Party Privacy (CPP) package 301 Feature implementation Task summary list The following is a summary of the tasks in this section:...
Page 387 Business Networking Express/Name and Private Number Display Page 387 of 1814 LD 95 – Create a new name string. Prompt Response Description New. TYPE NAME Create a new name string. CUST Customer group number. xxxx DN linked with the name string. LD 10 –...
Page 388 Page 388 of 1814 Business Networking Express/Name and Private Number Display LD 11 – Allow or deny name and digit display on Meridian 1 proprietary telephone. Prompt Response Description REQ: New. Change. TYPE: xxxx Telephone type, where xxxx = SL-1, 2006, 2008, 2009, 2016, 2018, 2112, 2216, 2317, 2616, 3000, 3901, 3902, 3903, 3904, 3905.
Page 389 Business Networking Express/Name and Private Number Display Page 389 of 1814 LD 27 – Configure the BRI Digital Subscriber Loop. Prompt Response Description New. TYPE Terminal Service Profile. l s c dsl DSL address. c dsl For Option 11C. xxxx DN associated with the TSP.
Page 390 Page 390 of 1814 Business Networking Express/Name and Private Number Display LD 16 – Configure D-channel for User-to-User service 1 (BRI). Prompt Response Description Change. TYPE Route Data Block. Interface type. EURO EuroISDN interface - complies with ETS 300 102 ETSI standard.
Page 391: Feature Operation
Business Networking Express/Name and Private Number Display Page 391 of 1814 LD 86 – Configure Route List Index for BNE feature. Prompt Response Description Add a Route List Index. Change an existing Route List Index. CUST Customer group number. FEAT Route List Data Block.
Page 392 Page 392 of 1814 Business Networking Express/Name and Private Number Display 553-2901-301 Standard 9.00 January 2002...
Page 393: Call Charge Keeping
Page 393 of 1814 Call Charge Keeping Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 394 Page 394 of 1814 Call Charge Keeping Call charging under 1TR6 supports: • recording of accumulated call charging information for each call in the CDR (if equipped) • calculation of total charge for each call based on assigned unit cost, and the accumulated call charging information received over the network.
Page 395: Call Connection Restriction
Page 395 of 1814 Call Connection Restriction Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 396 Page 396 of 1814 Call Connection Restriction • PSTNs can be limited. If so specified, only a single PSTN is permitted in a call connection; or, an unlimited number of PSTNs can be allowed. • µ/A-Law conversions are limited, to prevent potential transmission problems.
Page 397 Call Connection Restriction Page 397 of 1814 Feature implementation Task summary list The following is a summary of the tasks in this section: LD 15 – Configure the Customer Data Block to allow Call Connection Restriction. LD 15 – Configure the Customer Data Block to allow Call Connection Restriction. Prompt Response Description...
Page 398 Page 398 of 1814 Call Connection Restriction 553-2901-301 Standard 9.00 January 2002...
Page 399 Page 399 of 1814 Call Detail Recording Enhancement Contents The following are the topics in this section: Feature description ........Call Detail Recording .
Page 400: Call Detail Recording Enhancement
Page 400 of 1814 Call Detail Recording Enhancement Feature description Call Detail Recording Call Detail Recording (CDR) records information about selected calls for accounting purposes. For each call, CDR identifies the calling and called parties and notes the time and duration of the call. A record describing the complete call is output by the Meridian 1 system when the call is terminated.
Page 401: Operating Parameters
Call Detail Recording Enhancement Page 401 of 1814 • Generates CDR “X” records for stand-alone multiple call transfers on outgoing non-PPM CO trunks, and • Generates CDR “X” records for network multiple transfers on outgoing PPM and non-PPM CO trunks. A new CDR field is introduced (BLID – Billing Line Identification) indicating the remote responsible party for the particular call duration specified in the Call Duration field in cases of network multiple call transfers.
Page 402 Page 402 of 1814 Call Detail Recording Enhancement CDR Enhancement – Conference Interaction In the second scenario, A calls an outgoing CO trunk; A transfers to B; B conferences C; C conferences D; B disconnects; and C disconnects. D transfers to F. All Sets are in the same node. An “S”...
Page 403: Call Forward All Calls/No Answer
Call Detail Recording Enhancement Page 403 of 1814 Call Forward Call Forward All Calls The following table explains the interaction between Call Forward All Calls and the CDR Enhancement feature. CDR Enhancement – Call Forward All Calls Interaction In the first scenario, A calls an outgoing CO trunk, and transfers to B. B call forwards (all calls) to C, and call forwards (all calls) to D.
Page 404 Page 404 of 1814 Call Detail Recording Enhancement CDR Enhancement – Call Forward No Answer Interaction In the second scenario, A calls an outgoing CO trunk, and unguarded transfers to B. B call forwards (no answer) to C and C call forwards (no answer) to D.
Page 405 Call Detail Recording Enhancement Page 405 of 1814 Attendant Recall The following table explains the interaction between Attendant Recall and the CDR Enhancement feature. CDR Enhancement – Attendant Recall Interactions In the first scenario, the attendant calls an outgoing CO trunk, and extends the call to A.
Page 406 Page 406 of 1814 Call Detail Recording Enhancement Network PPM and Non-PPM During network call transfer, if the outgoing CDR X trunk is transferred through ISDN directly to Meridian Mail, the CDR record is generated against the Meridian Mail virtual agent DN. During network call transfer, if the outgoing CDR X trunk is transferred though ISDN to a remote DN which is Call Forwarded (All Calls) to Meridian Mail, the CDR record is generated against the Meridian Mail virtual agent...
Page 407 Call Detail Recording Enhancement Page 407 of 1814 CDR Enhancement – Call Park Interaction In the third scenario, A calls an outgoing CO trunk, and presses the Call Park key twice. B dials Special Service Prefix (SPRE) + Parked Call Access code (72) + the identification number assigned to the parked call to access the parked call later.
Page 408 Page 408 of 1814 Call Detail Recording Enhancement Automatic Call Distribution For ACD Call Transfer, ACD Conference and Network ACD, CDR records are generated as if these feature are functioning in a non-ACD environment. For the Agent Observe subfeature, CDR records are generated as for a conference on non-ACD calls.
Page 409 Call Detail Recording Enhancement Page 409 of 1814 Break-in to Enquiry Calls The following table explains the interaction between Break-in to Enquiry Calls and the CDR Enhancement feature. CDR Enhancement – Break-in to Enquiry Calls Interaction In this scenario, A makes an outgoing CO call, and transfers to B. B transfers to C, and is talking to C without completing the transfer.
Page 410: Feature Packaging
Page 410 of 1814 Call Detail Recording Enhancement Multi-party Operations “Recovery of Misoperation on Call Transfer” interacts with the CDR Enhancement feature. The following table explains the interaction between this feature and the CDR Enhancement feature. CDR Enhancement – Multi-party Operations Interaction In this scenario, A calls an outgoing CO and transfers to B.
Page 411: Feature Implementation
Call Detail Recording Enhancement Page 411 of 1814 CDR for the attendant is included as part of Call Detail Recording (CDR) package 4 and is applicable to outgoing trunks. Network PPM CDRX is included as part of Periodic Pulse Metering/Message Registration (MR) package 101.
Page 412: Feature Operation
Page 412 of 1814 Call Detail Recording Enhancement TKTP Central Office Trunk data block. Direct Inward Dialing trunk data block. Wide Area Telephone Service trunk data block. Foreign Exchange trunk data block. CDR provided. - INC (NO) YES CDR records generated for incoming calls. - OAL CDR records generated for outgoing calls.
Page 413 Page 413 of 1814 Call Forward All Calls/No Answer Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 414 Page 414 of 1814 Call Forward All Calls/No Answer — M2008 — M2616 — M2216 Operating parameters There are no operating parameters associated with this feature. Feature interactions There are no feature interactions associated with this feature. Feature packaging This feature requires the following packages: •...
Page 415 Page 415 of 1814 Call Forward, Break-In and Hunt Internal or External Network Wide Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 416: Call Forward, Break-In And Hunt Internal Or External Network Wide
Page 416 of 1814 Call Forward, Break-In and Hunt Internal or External Network Wide If neither the CLID, NAS, QSIG or DPNSS information is present, the following occurs. The route class mark defined in the route data block will be used to collect information necessary to determine whether a call should be given internal or external treatment.
Page 417 Call Forward, Break-In and Hunt Internal or External Network Wide Page 417 of 1814 When Trunk Y calls Set A and Set A does not answer, the Call Forward by Call Type feature is activated from Set A’s node. The calling CLID initially received is NPI public or unknown.
Page 418 Page 418 of 1814 Call Forward, Break-In and Hunt Internal or External Network Wide Internal Call Forward considers the transferred party and not the transferring party (both attendant and set) when the transferring party is on the treating node. Information transported across the network by NAS, DPNSS or QSIG from a network side transferred call is not considered.
Page 419 Call Forward, Break-In and Hunt Internal or External Network Wide Page 419 of 1814 Feature packaging Depending on the capabilities of this feature, the following packages are required: • Call Forward, Break-In and Hunt Internal or External Network Wide is included in base X11 system software;...
Page 420 Page 420 of 1814 Call Forward, Break-In and Hunt Internal or External Network Wide LD 16 – Modify Route Data Block to Define Internal/External Calls. Prompt Response Description Change. TYPE Route data block. CUST Customer number. ROUT Route number. RCLS (EXT) INT Route Class marked as External or Internal.
Page 421: Feature Description
Page 421 of 1814 Call Forward/Hunt Override Via Flexible Feature Code Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 422: Operating Parameters
Page 422 of 1814 Call Forward/Hunt Override Via Flexible Feature Code Call Forward/Hunt Override Via FFC works in network environments with Meridian 1 nodes and Meridian Customer Defined Network (MCDN) links. Operating parameters The Call Forward/Hunt Override FFC can only be used in predial mode from a set (i.e., it has to be dialed before dialing the DN that has Call Forward All Calls, Intercept Call Forward, Call Forward No Answer, Hunt, or Make Set Busy active).
Page 423: Call Forward/Hunt Override Via Flexible
Call Forward/Hunt Override Via Flexible Feature Code Page 423 of 1814 ACD DNs are not overridden by Call Forward/Hunt Override Via FFC. Any attempt will be canceled and access denied treatment will be returned. Individual DNs on an ACD set are overridden by Call Forward/Hunt Override Via FFC with the same limitations as for other sets.
Page 424 Page 424 of 1814 Call Forward/Hunt Override Via Flexible Feature Code Call Waiting Call Waiting can be used even if the Call Forward/Hunt Override Via FFC feature has been activated. When a busy set with Call Waiting configured is encountered, it will terminate on Call Waiting. Call Waiting Redirection There is no interaction with the Call Waiting treatment component of the Call Waiting Redirection feature.
Page 425 Call Forward/Hunt Override Via Flexible Feature Code Page 425 of 1814 Group Call It is not possible to use the Call Forward/Hunt Override FFC as a Group Call Group Hunt Primary Line Directory Numbers (PLDNs) are not overridden by the Call Forward/Hunt Override Via FFC feature.
Page 426 Page 426 of 1814 Call Forward/Hunt Override Via Flexible Feature Code Primary Line Directory Number (PLDN) It is not possible to store the Call Forward/Hunt Override FFC as a PLDN. Phantom TN This feature is not overridden by the Call Forward/Hunt Override FFC. If a Call Forward/Hunt Override FFC is used against a Phantom TN, the call will be canceled and overflow will be given.
Page 427: Feature Code
Call Forward/Hunt Override Via Flexible Feature Code Page 427 of 1814 Feature packaging For stand-alone environments, the following package is required: • Flexible Feature Codes (FFC) software package 139. For network environments, the following software package must also be provided: •...
Page 428 Page 428 of 1814 Call Forward/Hunt Override Via Flexible Feature Code LD 10 – Set Class of Service for the Forward/Hunt Override Via FFC. Prompt Response Description REQ: NEW, CHG New, or change. TYPE: Type of telephone set. (CFHD) CFHA Call Forward/Hunt Override Via FFC is (denied) or allowed.
Page 429: Feature Operation
Call Forward/Hunt Override Via Flexible Feature Code Page 429 of 1814 CFHO*FFC* CFHO is assigned to key B. CFHO*FFC* CFHO is assigned to key C. CFHO*FFC* CFHO is assigned to key D. Feature operation There are no operating procedures specified for this feature. The user gets the same functionality in a Meridian Customer Defined Network (MCDN) as in standalone environments.
Page 430 Page 430 of 1814 Call Forward/Hunt Override Via Flexible Feature Code 553-2901-301 Standard 9.00 January 2002...
Page 431: Call Page Network Wide
Page 431 of 1814 Call Page Network Wide Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 432: Call Page Network Wide
Page 432 of 1814 Call Page Network Wide PAGENET Controlled allows limited access to external users meeting the following criteria: • the Attendant Console or set is programmed with PAGENET allowed in the Class of Service; • the point-to-point D-channel is configured with remote capability (e.g RCAP=NAC).
Page 433 Call Page Network Wide Page 433 of 1814 Attendant Call Extension If an attendant’s source (SRC) or destination (DEST) Key is connected to an external PAGENET uncontrolled trunk, Attendant Call Extension is not blocked. However, if an attendant’s SRC or DEST Key is connected to an external PAGENET controlled route, Attendant Call Extension is blocked.
Page 434 Page 434 of 1814 Call Page Network Wide LD 10 – Assign Class of Service to Analog (500/2500 type) telephones. LD 11 – Assign Class of Service to Meridian 1 Proprietary Telephones. LD 27 – Assign Class of Service to ISDN BRI sets. LD 17 –...
Page 435 Call Page Network Wide Page 435 of 1814 DGTP Digital Trunk type. RCAP Remote capability where: NAC = Class of Service data. XNAC = removes Class of Service as a remote capability (default). LD 14 – Paging Trunk Configuration. Prompt Response Description New.
Page 436 Page 436 of 1814 Call Page Network Wide TYPE: xxxx Telephone type, where xxxx = SL1, 2006, 2008, 2009, 2016, 2018, 2112, 2216, 2317, 2616, or 3000. PGNA Call Page Network Wide Allowed. (PGND) = Call Page Network Wide Denied (default). LD 27 –...
Page 437 Call Page Network Wide Page 437 of 1814 Feature operation Internal Paging Call No specific operating procedures are required to use this feature. External Paging Call When a user makes an external Paging call via dial access, one of the following dialing plans must be used: Route Access Code (ACOD) that connects user to Paging node and Paging route ACOD;...
Page 438 Page 438 of 1814 Call Page Network Wide 553-2901-301 Standard 9.00 January 2002...
Page 439: Call Park Network Wide
Page 439 of 1814 Call Park Network Wide Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 440 Page 440 of 1814 Call Park Network Wide Network Call Park enables an attendant or a station set to park a call on System DN or DN within a Meridian Customer Defined Network (MCDN). This networking capability requires users at parking, parked at, tandem and accessing nodes be equipped with Network Attendant Services (NAS).
Page 441 Call Park Network Wide Page 441 of 1814 Call Park Expansion The Primary Call Park Block must be defined for the customer. Network Call Park Network Call Park is supported if the network has all nodes connected by MCDN ISDN links with NAS signaling configured. All the current limitations of the NAS feature apply to CPRKNET.
Page 442 Page 442 of 1814 Call Park Network Wide Basic Alternate Route Selection Network Alternate Route Selection An Electronic Switched Network (ESN) number can be assigned as the System Park or Station Set DN to a Network Call Park call. A parked call on a System Park DN can be retrieved by a caller outside the parked node via BARS/NARS dialing.
Page 443 Call Park Network Wide Page 443 of 1814 Feature implementation Task summary list The following is a summary of the tasks in this section: LD 15 – Enable Call Park Network Wide. LD 17 – Set the remote capability at both ends of the ISDN link to Call Park.
Page 444 Page 444 of 1814 Call Park Network Wide - NASA Allow Network Attendant Service. LD 50 – Add/Change Customer Call Park Data. Prompt Response Description New, change, or print. TYPE Call Park data block. CUST Customer number. BLOC Call Park data block number. Primary Call Park (block 1) must be defined for Call Park operation.
Page 445 Call Park Network Wide Page 445 of 1814 For Option 11C. Call Transfer Allowed. XFD = Call Transfer Denied. LD 11 – Add/Change Call Park Key on Meridian 1 proprietary telephones. Prompt Response Description REQ: New, or change. TYPE: xxxx Telephone type where: aaaa = SL1, 2006, 2008, 2009, 2016, 2018, 2112, 2216, 2317, 2616 or 3000.
Page 446 Page 446 of 1814 Call Park Network Wide Feature operation Call Park Expansion Attendant Console with Park Key Attendant Console via Dial Access Meridian 1 Proprietary Set with Display and Park Key Press PRK key, or dial SPRE + 71 or Call Park FFC. An available System Park DN is displayed.
Page 447 Call Park Network Wide Page 447 of 1814 Press the CONF or TRN key to complete call park. —————————— End of Procedure —————————— Meridian 1 Proprietary without Display Analog (500/2500) type telephones The Call Park operation on these types of telephones is not affected. Network Call Park The existing Call Park operation is modified to accommodate the Network Call Park capabilities of the CPRKNET feature.
Page 448 Page 448 of 1814 Call Park Network Wide Attendant Parking an Extended Call Press the PRK key. Extended party is released and ringback or busy tone is removed. SPRE + 71 + ESN number of the extended call are displayed. •...
Page 449 Call Park Network Wide Page 449 of 1814 Meridian 1 Proprietary Set without Display with PRK key Meridian 1 Proprietary Set without Display via Dial Access Analog (500/2500 type) set Press the PRK, CONF, TRN or perform switchhook flash depending on type of set and key assignment.
Page 450 Page 450 of 1814 Call Park Network Wide External Call Park Access External Call Park Access allows a parked call on a System Park DN to be retrieved by an external user via an incoming DID or TIE trunk. This capability requires that the node where the call is parked (parked at node) is equipped with the CPRKNET feature and the Primary Call Park Block is defined.
Page 451: Call Pickup Network Wide
Page 451 of 1814 Call Pickup Network Wide Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 452 Page 452 of 1814 Call Pickup Network Wide • Directed Call Pickup by DN • Display Call Pickup With the exception of Display Call Pickup, user operation of the above features remains unchanged. To display Call Pickup, press the Display key, followed by the Call Pickup key.
Page 453 Call Pickup Network Wide Page 453 of 1814 Operating parameters Call Pickup Network Wide is not supported over a Virtual Network Services (VNS) or QSIG link. A Speed Call List must be configured with the PINX DNs of the remote switch.
Page 454 Page 454 of 1814 Call Pickup Network Wide A call to an non ACD DN on an ACD set can be picked up as a normal call. A call transferred by an ACD agent can be picked up as a call transferred by a normal set.
Page 455 Call Pickup Network Wide Page 455 of 1814 Call Transfer Network Call Transfer A call may be picked up before or after the transferring party has completed the transfer. For pickup before transfer completion, the transferring party is displayed updated information by the Call Pickup Network Wide feature when the call is picked up.
Page 456 Page 456 of 1814 Call Pickup Network Wide Display of Calling Party Denied The Class of Service DDGA/DDGD for digit display and NAMA/NAMD for name display are respected when the requesting party’s display and the originating party’s display are updated after the ringing call has been picked up successfully.
Page 457 Call Pickup Network Wide Page 457 of 1814 Network Attendant Service/ISDN Call Connection Limitations ISDN Call Connection Limitations (ICCL) apply to Call Pickup Network Wide calls. If the call being redirected by the Call Pickup Network Wide feature is blocked due to one of the ICCL limitations (e.g., Tandem Threshold, Call Redirection Threshold, Number of MU/A Law Conversions, Disconnect Supervision), the originating call will re-ring the originally called party and overflow tone is given to the requesting party.
Page 458 Page 458 of 1814 Call Pickup Network Wide Virtual Network Services The Call Pickup Network Wide feature will not work in conjunction with the Virtual Network Services feature. Feature packaging The Call Pickup Network Wide feature is included in Integrated Services Digital Network (ISDN) package 145.
Page 459 Call Pickup Network Wide Page 459 of 1814 LD 15 – Define the special prefix code (SPRE) to be able to activate the Call Pickup features by dialing SPRE + xx. LD 16 – Configure the PNI on the route. This PNI must correspond to the one configured in LD 15 on the target (remote) node.
Page 460 Page 460 of 1814 Call Pickup Network Wide The configuring of different pickup keys is optional, since the Call Pickup and Directed Call Pickup features can be activated by dialing the SPRE + xx or by dialing a Flexible Feature Code. The Digit Display key is needed for the Display Call Pickup feature.
Page 461 Call Pickup Network Wide Page 461 of 1814 xx DPU Key number, DN Pickup. xx DSP Key number, Digit Display. LD 15 – Define the customer’s Private Integrated Network Identifier (PNI) and Private Integrated Services Network Exchange (PINX) DN. Prompt Response Description REQ:...
Page 462 Page 462 of 1814 Call Pickup Network Wide CODE mmmm Specific FFC type. - PUDN PUDN Pickup DN code. xxxx Enter the Flexible Feature Code. - PUGR PUGR Pickup Group code. xxxx Enter the Flexible Feature Code. - PURN PURN Pickup Ringing Number code.
Page 463 Call Pickup Network Wide Page 463 of 1814 SIZE 1-1000 Maximum number of DNs allowed in Speed Call list. Note: The size cannot be greater than the value entered against the STOR prompt below. STOR 000-999 xxxx Speed Call List entry number and digits (PINX DN) stored against it.
Page 464 Page 464 of 1814 Call Pickup Network Wide - RLS Release ID of the switch at the far end of the D-channel. LD 15 – Define the special prefix code (SPRE) to be able to activate the Call Pickup features by dialing SPRE + xx.
Page 465 Call Pickup Network Wide Page 465 of 1814 Feature operation Display Call Pickup This feature is only supported on Meridian Digital Telephones (with the exception of the M2317, and M3000). Press the DSP key. • The DSP key is lit. Press the RNP key.
Page 466 Page 466 of 1814 Call Pickup Network Wide Where 2 = The DN of the originating party if it is local or available from CLID. If no CLID is available for a remote, originating party, either the route access code and the route member number are displayed if the ringing set is local, or dashes (“----”) are displayed if the ringing set is remote.
Page 467 Call Pickup Network Wide Page 467 of 1814 Directed Call Pickup by Group Number (Group Pickup) To answer a call in another Call Pickup group from a Meridian Digital Telephone: Lift the handset, or press a DN key. • The DN key is lit. Press the GPU key or dial SPRE + 94 or dial PUGR FFC.
Page 468 Page 468 of 1814 Call Pickup Network Wide Dial the extension number. • Once the group number is dialed completely, the DPU key is flashing to indicate that a search or scan is in progress. You are connected to the call. •...
Page 469: Calling Line Identification (Clid)
Information display on telephone sets and terminals The ISDN features listed in this section can be used on all Nortel Networks sets. However, not all sets or terminals provide information displays. Displayphone. The Meridian 1 Displayphone allows the full display of CLID information.
Page 470: Standard 9.00 January
Page 470 of 1814 Calling Line Identification (CLID) Other sets and terminals. The following devices (if equipped with a digit display) can receive and display a CLID name: • Attendant Consoles • Meridian 1 sets with digit display • Digital sets (M2317) •...
Page 471 Calling Line Identification (CLID) Page 471 of 1814 Figure 47 Digit display format for Calling Line Identification trunk route access code trunk route member number Non-ISDN or CLID not available: area code (not shown for local calls) central office prefix user's extension ISDN call to/from 1111...
Page 472: Calling Line Identification (Clid)
Page 472 of 1814 Calling Line Identification (CLID) CLID on outgoing calls The calling party number that is sent out with the call SETUP message on the D-channel is based on: • the numbering plan (private or public); • the customer option configured in the Customer Data Block (LD 15), either Prime Directory Number (PDN) or Listed Directory Number (LDN);...
Page 473 Calling Line Identification (CLID) Page 473 of 1814 Feature interactions There are no feature interactions associated with this feature. Feature packaging This feature is included in base Meridian 1 System Software. Feature implementation There are no specific implementation procedures for this feature. Feature operation No specific operating procedures are required to use this feature.
Page 474 Page 474 of 1814 Calling Line Identification (CLID) 553-2901-301 Standard 9.00 January 2002...
Page 475: Contents
Page 475 of 1814 Calling Line Identification in CDR Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 476 Page 476 of 1814 Calling Line Identification in CDR • outgoing answered toll calls, and • all incoming calls. For detailed descriptions of the Call Detail feature, please refer to Call Detail Recording: Description and Formats (553-2631-100). The Calling Line ID in CDR feature is an enhancement to the CDR feature. The description which follows applies to a stand-alone as well as an ISDN PRI environment.
Page 477 Calling Line Identification in CDR Page 477 of 1814 In the TTY output, the CLID information is printed on the second line, as shown in Table 3. The field is always 16 characters: the actual CLID digits, followed by X's to total 16. Table 40 CLID number in the TTY output DN499...
Page 478 Page 478 of 1814 Calling Line Identification in CDR In the following example DN 2222 on PBX A is calling DN 5222 on PBX C where PBX B is used as a tandem PBX. PBX B's CDR captures the actual extension (X2222) of the caller.
Page 479 Calling Line Identification in CDR Page 479 of 1814 Feature packaging This feature requires the Calling line Identification in Call Detail Recording (CCDR) package 118. The following packages are also required: • Call Detail Recording (CDR) package 4; • Call Detail Recording on Teletype Terminal (CTY) package 5; •...
Page 480 Page 480 of 1814 Calling Line Identification in CDR LD 15 – Change the Customer Data Block to configure CLID. Prompt Response Description REQ: Add or change a customer. TYPE: Networking Data. CUST Customer number. ISDN Change ISDN options. - PNI 1-32700 Private Network Identifier.
Page 481 Calling Line Identification in CDR Page 481 of 1814 LD 17 – Allow CDR to be printed on the TTY terminal. Prompt Response Description Change. TYPE ADAN All input/output devices. ADAN CHG TTY XX Change I/O device where xx = port. USER Use the TTY for CDR records.
Page 482 Page 482 of 1814 Calling Line Identification in CDR 553-2901-301 Standard 9.00 January 2002...
Page 483: Clid On Analog Trunks For Hong Kong
X11 Release: Page 483 of 1814 CLID on Analog Trunks for Hong Kong (A-CLID) Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 484 Page 484 of 1814 CLID on Analog Trunks for Hong Kong (A-CLID) The A-CLID information is treated similar to ISDN CLID for delivery to other modules and applications in the system, including the display on digital telephones and consoles at the local node and other network nodes (if any). You can enable or disable A-CLID on an individual trunk port basis.
Page 485: Calling Party Privacy
Page 485 of 1814 Calling Party Privacy Contents The following are the topics in this section: Feature description ........Calling Party Privacy Enhancement .
Page 486 Page 486 of 1814 Calling Party Privacy Depending on the trunk route configuration, public network numbers which tandem over the Meridian 1 Meridian Customer Defined Network (MCDN), prior to exiting to the PSTN, Privacy Indicator will be passed along if dialed by the originator.
Page 487 Calling Party Privacy Page 487 of 1814 When the Privacy Indicator Ignore (PII) prompt is set to YES in Overlay 16, the Calling Line Identification (CLID) Presentation Indicator and the Calling Party Name Display (CPND) Indicator (if it exists) are changed from restricted/denied to allowed.
Page 488 Page 488 of 1814 Calling Party Privacy A non-ISDN trunk route will not be able to provision the CPP feature if Outpulsing of Asterisk and Octothorpe (OPAO) package 104 is equipped on the switch. During SYSLOAD, the CPP database will be removed from the non-ISDN trunk routes if the OPAO package is equipped.
Page 489 Calling Party Privacy Page 489 of 1814 A common number defined for the Special Prefix (SPRE) code in the database is “1”. Thus, “1167” will not be accepted as an FFC for CPP due to the conflict with existing DNs. The technician should either change the SPRE code, or define a new FFC for CPP to be used by a rotary telephone.
Page 490 Page 490 of 1814 Calling Party Privacy Call Detail Recording The current Call Detail Recording (CDR) records which include the Calling Party Number will continue to do so even if the caller has requested CPP. The FFC for CPP dialed by the user will be included in the dialed digits field when generating a CDR record.
Page 491 Calling Party Privacy Page 491 of 1814 Call Pickup Network Wide If an incoming trunk call with the Privacy Indicator is picked up by a remote set (requesting party), the display of the calling Party Number and Name are not displayed on the requesting set. Call Party Name Display (CPND) In current operations, if the International Supplementary Features (SUPP) package 131 is not equipped in the system, an incoming ISDN call with the...
Page 492 Page 492 of 1814 Calling Party Privacy Conference The CPP feature will pass the Privacy Indicator to the terminating set to inhibit the display of the Calling Party Name and Number if the Conference feature is used for the purpose of performing a transfer. Calling Party Name Display Denied For outgoing calls, if the CPP package is equipped, the CPP feature will take precedence over the Calling Party Name Display Denied feature for...
Page 493 Calling Party Privacy Page 493 of 1814 Feature Group D If an incoming Feature Group D (FGD) call terminates at a Meridian 1 switch locally, the received 10-digit Automatic Number Identification (ANI) will be displayed on the terminating set if the Show ANI Digits on Terminal Displays (SHAN) field is set to “YES”...
Page 494 Page 494 of 1814 Calling Party Privacy ISDN QSIG Name Display Calling Party Privacy (CPP) takes precedence over the ISDN QSIG Name Display feature. Last Number Redial The Last Number Redial (LNR) feature will store the CPP code in the LNR data space if the CPP code was included in the last number dialed by the user.
Page 495 Calling Party Privacy Page 495 of 1814 Network Message Services An incoming trunk call with the Privacy Indicator will not display the Calling Party Name and Number on the Message Center operator’s terminal. Network Ring Again A call placed by means of the Network Ring Again feature will respect the CPP requested when the call was originally dialed.
Page 496 Page 496 of 1814 Calling Party Privacy Stored Number Redial During Stored Number Redial (SNR) programming, a user can store the CPP code followed by the normal dialing sequence in the SNR data space. Outgoing calls originated by the SNR feature will send the Privacy Indicator to the far end.
Page 497 Calling Party Privacy Page 497 of 1814 LD 57 – Define the FFC for CPP feature. FFC package 139 is required for loading LD 57. Prompt Response Description Add, or change. TYPE Flexible Feature Code. CUST Customer number. FFCT (NO) YES Flexible Feature Confirmation Tone.
Page 498 Page 498 of 1814 Calling Party Privacy TKTP Central Office Trunk data block. Direct Inward Dialing trunk data block. Foreign Exchange trunk data block. Wide Area Telephone Service trunk data block. DTRK Digital trunk route. DGTP Digital trunk type. ISDN ISDN PRI option.
Page 499 Calling Party Privacy Page 499 of 1814 - DPPI (1167) nnnn Privacy Indicator for a dial pulse trunk. DPPI is prompted only if CPP is set to “YES” and the trunk route is non-ISDN. If CPP is changed from NO to YES, the default is 1167. Any arbitrary digit sequence (0-9) up to four digits can be specified.
Page 500 Page 500 of 1814 Calling Party Privacy Feature operation Any outgoing call initiated from a set with Calling Party per-line blocking (CLBA) Class of Service will request Calling Party Privacy. If the originating party has CLBD Class of Service, the Calling Party Privacy feature can only be activated on a per-call basis;...
Page 501: Calling Party Privacy Override
Feature operation ......... . Regional material statement The information presented in this section does not pertain to all market regions. Contact your system supplier or your Nortel Networks representative to verify support of this product in your area. Feature description Calling Party Privacy Override (CPPO) enhances the functionality of the Calling Party Privacy (CPP) feature.
Page 502 Page 502 of 1814 Calling Party Privacy Override The Calling Party Privacy (CPP) feature enables the Meridian 1 system to permanently block the Calling Party Number and Name from being displayed on the terminating set across the Public Switched Telephone Network (PSTN).
Page 503: Outgoing Calls
Calling Party Privacy Override Page 503 of 1814 The following example illustrates Calling Party Privacy Override functionality: Set A, a Meridian 1 proprietary set with Class of Service set to CLBA, goes off-hook. Set A dials the Calling Party Privacy Override Flexible Feature Code, defined in Overlay 57.
Page 504: Tandem Calls
Page 504 of 1814 Calling Party Privacy Override When an incoming call is on a non-ISDN route, the Meridian 1 does not receive the Privacy Override Indicator. Tandem Calls Incoming ISDN calls ISDN to ISDN tandem For an incoming call tandeming through the Meridian 1, any incoming Privacy Override Indicator is only repeated to the outgoing trunk route that also has CPPO provisioned.
Page 505: Operating Parameters
Calling Party Privacy Override Page 505 of 1814 Non-ISDN to ISDN tandem Even though a Privacy Override Indicator is not provided for an incoming non-ISDN trunk call, if the outgoing route has TCPP set to NO, the Presentation Indicator field in the Calling Party IE is set to “Presentation Allowed”.
Page 506 Page 506 of 1814 Calling Party Privacy Override When a user dials the Flexible Feature Code defined for the CPPO feature and if CPPO is not provisioned on the outgoing trunk route, the call proceeds without carrying the Privacy Override Indicator. The CPPO feature does not affect whether or not the Calling Party Number and Name information is displayed for internal calls within the Meridian 1 system, even if the originator requests CPPO.
Page 507: Feature Interactions
Calling Party Privacy Override Page 507 of 1814 Feature interactions Attendant Consoles A CPPO call can be originated from any Meridian 1 Attendant Console. Attendant Consoles request CPPO by preceding the normal dialing sequence with the Flexible Feature Code for CPPO. Attendant Consoles can also initiate a CPPO call using the Autoline key.
Page 508 Page 508 of 1814 Calling Party Privacy Override Automatic Call Distribution Calls placed by means of Enhanced Automatic Call Distribution (ACD) Routing, Enhanced Interflow, Enhanced Night Call Forward, Enhanced Network Routing, and Network ACD recognize the originator’s CPPO request. Automatic Call Distribution MAX If the CPP package is equipped, ACD MAX reports include the Calling Line Identification (CLID) for incoming ISDN calls that have the CLID Presentation Indicator set to “Allowed”.
Page 509 Calling Party Privacy Override Page 509 of 1814 When an incoming ISDN trunk call with the Privacy Override Indicator is forwarded into the public or private networks, the Privacy Override Indicator is tandemed to the far end to allow the display of the Calling Party Number and Name, provided that the outgoing trunk route on the tandem node has CPPO provisioned.
Page 510 Page 510 of 1814 Calling Party Privacy Override Call Transfer As per existing operation, if an incoming non-ISDN call is transferred or an incoming ISDN call is transferred to a non-ISDN trunk, the Connect Party Number and Name information is not passed to the terminating node. The CPPO feature does not change this operation.
Page 511 Calling Party Privacy Override Page 511 of 1814 Calling Party Privacy and Call Forward Set A, requesting CPPO, calls Set B. Set B Call Forwards All Calls to Set C. The CPP Flexible Feature Code is part of the forwarding DN. Set A’s number and name is displayed on Set C as the Calling Party Number and Name;...
Page 512 Page 512 of 1814 Calling Party Privacy Override Display of Calling Party Denied When the CPP package is equipped, the CPPO feature takes precedence over the Display of Calling Party Denied (DPD) feature for allowing the Calling Party Number and Name to be displayed. For example, when an outgoing ISDN call is marked as a CPPO call, then the outgoing SETUP message includes the Calling Party Number IE with the Presentation Indicator set to “Presentation Allowed”...
Page 513 Calling Party Privacy Override Page 513 of 1814 Last Number Redial The Last Number Redial (LNR) feature stores the CPPO Flexible Feature Code in the LNR database if the CPPO Flexible Feature Code was included in the last number dialed by the user. The outgoing redialed calls also send the Privacy Override Indicator to the far end.
Page 514 A call placed by means of the Network Ring Again feature recognizes the CPPO request from when the call was originally dialed. Nortel Networks Symposium Call Center As per existing operation, an incoming CPPO call routed to Nortel Networks Symposium Call Center contains the CLID. 553-2901-301 Standard 9.00 January 2002...
Page 515 Calling Party Privacy Override Page 515 of 1814 Private Line Service The Private Line Service feature outpulses the Privacy Override Indicator only if it is dialed by the originator. The asterisk (*) is outpulsed to the far end only if it is an Outpulse Asterisk and Octothorpe (OPAO) call. Otherwise, the asterisk (*) signals a three-second pause.
Page 516: Feature Packaging
Page 516 of 1814 Calling Party Privacy Override During an active call on a Meridian 1 proprietary set, the Stored Number Redial feature stores the CPPO Flexible Feature Code in the SNR database if the CPPO Flexible Feature Code is included in the number dialed by the originator.
Page 517: Feature Implementation
Calling Party Privacy Override Page 517 of 1814 Feature implementation Task summary list The following is a summary of the tasks in this section: LD 16 – Configure Privacy Override Indicators for a Non-ISDN route. LD 16 – Set the TCPP flag in RDB to tandem non-ISDN calls on an ISDN trunk route.
Page 518 Page 518 of 1814 Calling Party Privacy Override - TCPP CPP/CPPO flag treatment for an incoming non-ISDN trunk call tandemed to this trunk route. (NO) Outgoing call will carry the Privacy Override Indicator (default). Outgoing call will carry the Privacy Indicator. - DTPI (*67) nnnn Digitone Trunk Privacy Indicator...
Page 519 Calling Party Privacy Override Page 519 of 1814 LD 57 – Define the Flexible Feature Code for the Calling Party Privacy Override feature. Prompt Response Description Change existing data. TYPE Flexible Feature Code. CUST Customer number as defined in LD 15. FFCT (NO) Flexible Feature Confirmation Tone denied.
Page 520: Feature Operation
Page 520 of 1814 Calling Party Privacy Override LD 10/11 – Activate Calling Party Number and Name per-line blocking. Prompt Response Description REQ: Add new data. Change existing data. TYPE: aaaa Type of set. l s c u Terminal Number. l = loop, s = shelf, c = card, u= unit for options 51C, 61C, and 81C.
Page 521: Channel Negotiation
Page 521 of 1814 Channel Negotiation Contents The following are the topics in this section: Feature description ........Outgoing calls .
Page 522 Page 522 of 1814 Channel Negotiation Channel Negotiation allows call setup to continue even where a chosen bearer channel is unacceptable to the receiving switch. When this occurs, a search for an alternative channel acceptable to both ends of the call can take place. On an incoming or an outgoing call, the SETUP message sent by the Central Office or the Meridian 1 respectively contains the number of the requested B-channel.
Page 523 Channel Negotiation Page 523 of 1814 Operating parameters Channel negotiation cannot take place over ISDN PRI connections between Meridian 1 nodes. Feature interactions There are no feature interactions associated with this feature. Feature packaging This feature is included in base X11 System Software. Feature implementation There are no specific implementation procedures for this feature.
Page 524 Page 524 of 1814 Channel Negotiation 553-2901-301 Standard 9.00 January 2002...
Page 525: D-Channel Expansion
Page 525 of 1814 D-Channel Expansion Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 526 Page 526 of 1814 D-Channel Expansion Table 41 shows a summary of the physical I/O addresses permitted in a system. Table 41 Maximum physical I/O addresses in an Option 81C system Card Type Application DCH Only MSDL (NT6D80) 0-15 per system 0-15 per system 0-15 per group DDCH (NTBK51AA)
Page 527 D-Channel Expansion Page 527 of 1814 If an MSDL card uses a physical I/O address, and a non-DCH application is configured one of it's ports, then: • this I/O address is available for use by DDCH cards, or MSDL cards running DCH applications only, in another network group.
Page 528 Page 528 of 1814 D-Channel Expansion Note: You cannot configure a duplicate physical I/O address within the same network group, regardless of the applications. Table 42 Use of the same physical I/O address in a multi-group System MSDL MSDL Non-MSDL (DCH only) (non-DCH) DNUM x...
Page 529 D-Channel Expansion Page 529 of 1814 For example, a system has an MSDL, non-DCH (any single port not configured as a DCH), configured as DNUM 4 in GROUP 0. The system also has an MSDL (DCH only) configured as DNUM 5 in GROUP 0. To configure DCHI (Non-MSDL) DNUM 5 in GROUP 1 is not valid.
Page 530 Page 530 of 1814 D-Channel Expansion Feature implementation Task summary list The following is a summary of the tasks in this section: LD 17 – Define D-channels with D-channel Expansion feature. LD 17 – Define D-channels with D-channel Expansion feature. Prompt Response Description...
Page 531 D-Channel Expansion Page 531 of 1814 Example of D-channel configuration in Overlay 17 Table 43 shows an example of how you can configure D-channels in Overlay 17. In this example, you can define a TTY device using I/O address 0 (device number) in group 0. You can also define an MSDL card using I/O address 0, but it must be in a different network group.
Page 532 Page 532 of 1814 D-Channel Expansion Table 43 Example of D-channel configuration in Overlay 17 (Part 2 of 2) Network group 2. DNUM Device number 0..Note: The MSDL cards must run DCH applications only. Feature operation No specific operating procedures are required to use this feature. 553-2901-301 Standard 9.00 January 2002...
Page 533: Data Packet Network Access
Page 533 of 1814 Data Packet Network access Contents The following are the topics in this section: Feature description ........Data Packet Network Access X.25 .
Page 534 Page 534 of 1814 Data Packet Network access The HSDU and HSDM go through T-Link protocol exchange. The DN of a Packet Assembler/Disassembler (PAD) output port is associated with the HSDM. The Meridian 1 user accesses the Data Packet Network by dialing the DN of the PAD. Figure 49 Meridian 1 PRI to DMS-100 Data Packet Network Meridian 1...
Page 535 Data Packet Network access Page 535 of 1814 Data Packet Network Access X.25 PRI trunks may be configured to access a Public Data Packet Network (DPN - X25) via the DMS-100 ISDN node, provided that this service is made available by the serving Central Office. On a per call basis, any B-channel can be used to access the packet network.
Page 536 Page 536 of 1814 Data Packet Network access 553-2901-301 Standard 9.00 January 2002...
Page 537: Did-To-Network Calling
Page 537 of 1814 DID-to-network Calling Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 538 Page 538 of 1814 DID-to-network Calling A DID call which must be routed across the network will receive a treatment similar to that given to a call terminating within the local node. The DID call will receive intercept treatment, if the dialed DN is fully restricted or has DID-restricted Class of Service.
Page 539: Digit Key Signaling At Console
Page 539 of 1814 Digit Key Signaling at Console Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 540 Page 540 of 1814 Digit Key Signaling at Console The digits are sent to Meridian Mail by way of ISDN/AP KEY messages (and not by way of End to End signaling). Dialed digits are not saved by the Meridian 1 and are not displayed at the Attendant Console. While connected to Meridian Mail, other attendant functions continue to operate as before.
Page 541 Digit Key Signaling at Console Page 541 of 1814 Feature packaging The following packages are both required for Digit Key Signaling at Console: • ISDN package 145; and • Digit Key Signaling (DKS) package 180. Feature implementation There are no specific implementation procedures for this feature. Feature operation No specific operating procedures are required to use this feature.
Page 542 Page 542 of 1814 Digit Key Signaling at Console 553-2901-301 Standard 9.00 January 2002...
Page 543: Digital Trunk Interface And Primary Rate Interface Time Slot Reuse
Page 543 of 1814 Digital Trunk Interface and Primary Rate Interface Time Slot Reuse Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 544 Page 544 of 1814 Digital Trunk Interface and Primary Rate Interface Time Slot Reuse A count is kept of the number of times that a time slot has been reused. The time slot is not idled until all reservations have been canceled. This feature applies to the following loop types on single-group switches: •...
Page 545 Page 545 of 1814 Display of Access Prefix on CLID Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 546 Page 546 of 1814 Display of Access Prefix on CLID The Display of Access Prefix on CLID feature supports the following Integrated Services Digital Networks (ISDN) interfaces: • Meridian Customer Defined Network (MCDN) • Q-reference Signaling Point (QSIG) Operating parameters If CLID is not available, the trunk access code and the prefix number are displayed according to the existing feature operation.
Page 547 Display of Access Prefix on CLID Page 547 of 1814 LD 11 - Enable the Display of Access Prefix on CLID feature for digital sets. Prompt Response Description REQ: Add new data. Change existing data. TYPE: aaaa Type of Meridian 1 proprietary set. Terminal Number.
Page 548: Display Of Access Prefix On Clid
Page 548 of 1814 Display of Access Prefix on CLID LD 12 - Enable the Display of Access Prefix on CLID for attendant consoles. Prompt Response Description Add new data. Change existing data. TYPE aaaa Attendant type. Where aaaa = 1250 or 2250. Terminal Number.
Page 549 Display of Access Prefix on CLID Page 549 of 1814 -NPI aaaa Numbering Plan Identification. Valid entries for aaaa include: UNKN - Unknown. E164 - Numbering Plan based on E164. PRIV - Private. E163 - Numbering Plan based on E163. TELX - Telex.
Page 550 Page 550 of 1814 Display of Access Prefix on CLID LD 16 - Enable the Display of Access Prefix on CLID feature. Prompt Response Description Add new data. Change existing data. TYPE Route Data Block. CUST Customer Number as defined in LD 15. ROUT Route number.
Page 551: Display Of Calling Party Denied
Page 551 of 1814 Display of Calling Party Denied Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 552 Page 552 of 1814 Display of Calling Party Denied Display of Digits Denied (DDGD) Class of Service restricts digits from being displayed on another set when involved in a call. However, on the calling party’s set, the dialed digits are always displayed regardless of the Class of Service assigned to the called party’s set.
Page 553 Display of Calling Party Denied Page 553 of 1814 Figure 50 illustrates the functionality of Display of Calling Party Denied (DPD) on a nodal basis when both the calling and called parties have enabled DPD Class of Service options. The calling party has configured a Digit Display Denied (DDGD) and Name Display Denied (NAMD) Class of Service.
Page 554 Page 554 of 1814 Display of Calling Party Denied As illustrated in Figure 51, for calls placed over a MCDN ISDN network, Display Digits Denied (DDGD) Class of Service on the calling party’s set prevents the Calling Line Identification (CLID) from being displayed on the called party’s set.
Page 555 Display of Calling Party Denied Page 555 of 1814 Operating parameters Display of Calling Party Denied (DPD) is only supported on internal calls, Meridian Customer Defined Network (MCDN) ISDN networks and the interface to the public network. This feature does not support calls over DASS/DPNSS1 trunks. Display of Calling Party Denied is not supported on ISDN BRI sets.
Page 556 Page 556 of 1814 Display of Calling Party Denied If the terminating set has Dialed Name Display Allowed (DNDA), the display on the terminating set reflects the number of the calling party and the name and number of the forwarding set. In both cases, the terminating set’s display is in accordance with the DPD Class of Service options of the calling and forwarding sets.
Page 557 Display of Calling Party Denied Page 557 of 1814 Call Pickup When a call is picked up from another set, the terminating set’s display is in accordance with the Class of Service of the dialed and calling sets. The calling party’s display includes the dialed DN, the terminating DN and the name of the terminated set.
Page 558 Page 558 of 1814 Display of Calling Party Denied For network conference calls, display is provided. This is in accordance with the DPD Class of Service options of the individual sets. Dial Intercom Display information on sets that are involved in a Dial Intercom Group (DIG) call is based on the individual Class of Service of each set.
Page 559 Display of Calling Party Denied Page 559 of 1814 Multi Party Operations - Call Join When three parties are joined using the Call Join capabilities of the Multi Party Operations feature, display information is not provided on any of the conferee’s sets. When setting up a conference call, by conferencing one set at a time, the display on the conferee’s set is in accordance with the individual set’s Class of Service.
Page 560 Page 560 of 1814 Display of Calling Party Denied Note: The NAS package is required to display a calling party’s name and DN on the attendant console, when using the Display of Calling Party Denied feature within an ISDN PRI private network. With NAS configured and Calling Party Name Display equipped, the attendant console will display the calling party’s name and DN, regardless of the Display of Calling Party Denied Class of Service of the calling party’s...
Page 561 Display of Calling Party Denied Page 561 of 1814 LD 11 – Deny Digit Display and Name Display for Meridian 1 proprietary sets. Prompt Response Description REQ: CHG. Change. TYPE: xxxx Telephone type, where: xxxx = SL1, 2006, 2008, 2009, 2016, 2018, 2112, 2216, 2317, 2616 or 3000.
Page 562 Page 562 of 1814 Display of Calling Party Denied 553-2901-301 Standard 9.00 January 2002...
Page 563: Dpnss1/Dass2 To Q.931 Gateway
Feature operation ......... . Regional material statement The information presented in this section does not pertain to all market regions. Contact your system supplier or your Nortel Networks representative to verify support of this product in your area. Feature description This feature allows a Meridian 1 node to act as a gateway between DPNSS1, DASS2 and Q.931 (ISDN PRI) protocols.
Page 564 Page 564 of 1814 DPNSS1/DASS2 to Q.931 Gateway • coordinated dialing plan • network ring again, between DPNSS1 and Q.931 protocols Operating parameters The feature has the following limitation: • PSTN incoming trunks are not to be allowed access to PSTN outgoing trunks Feature interactions There are no feature interactions associated with this feature.
Page 565: Regional Material Statement
Regional material statement The information presented in this section does not pertain to all market regions. Contact your system supplier or your Nortel Networks representative to verify support of this product in your area. International ISDN PRI Feature description and administration...
Page 566: Dpnss1 Route Optimisation/Mcdn Trunk Anti-Tromboning Interworking
Page 566 of 1814 DPNSS1 Route Optimisation/MCDN Trunk Anti-Tromboning Interworking Feature description The Digital Private Networking Signalling System No.1 (DPNSS1) Route Optimisation (RO)/Meridian Customer Defined Networking (MCDN) Trunk Anti-Tromboning (TAT) Interworking feature provides RO and TAT interworking at DPNSS1/MCDN gateway nodes. Note: For detailed information on the DPNSS1 Route Optimisation feature, please refer to the DPNSS1: Product Overview Guide (553-3921-100) and the DPNSS1: Features and Services Guide...
Page 567 DPNSS1 Route Optimisation/MCDN Trunk Anti-Tromboning Interworking Page 567 of 1814 Figure 52 DPNSS1/MCDN scenario with Network Call Transfer, before RO/TAT optimisation Node 1 Meridi Station A an 1 DPNSS1 Station A calls Station B PRI channel 1 Station B Meridi Meridi used for first call an 1...
Page 568 Page 568 of 1814 DPNSS1 Route Optimisation/MCDN Trunk Anti-Tromboning Interworking Figure 53 DPNSS1/MCDN RO/TAT Interworking scenario, after TAT has been applied Node 1 Meridi Station A an 1 DPNSS1 Station B Meridi Meridi an 1 an 1 DPNSS1 tromboned trunks removed DPNSS1 Station C...
Page 569 DPNSS1 Route Optimisation/MCDN Trunk Anti-Tromboning Interworking Page 569 of 1814 Upon the completion of TAT on Node 3, a call transfer operation is simulated, and a new RO operation is initiated to remove any potential triangulation of routes. Figure 54 DPNSS1/MCDN RO/TAT Interworking scenario, after RO has been applied Node 1 Meridi...
Page 570 Page 570 of 1814 DPNSS1 Route Optimisation/MCDN Trunk Anti-Tromboning Interworking Referring to Figure 55, Station A, located at Node 1 on the MCDN side of the MCDN/DPNSS1 gateway, calls Station B located at Node 3 on the DPNSS1 side of the MCDN/DPNSS1 gateway. Station B transfers the call (using the Three Party Service feature) to Station C, also located at Node 1 on the MCDN side of the gateway.
Page 571 DPNSS1 Route Optimisation/MCDN Trunk Anti-Tromboning Interworking Page 571 of 1814 Once Three Party Service messaging has taken place, Node 2 initiates RO. The initial DPNSS1 routes are cleared. Node 2 becomes a MCDN/MCDN transit node, and the two tromboning PRI routes between Node 2 and Node 1 remain, as shown in Figure 56.
Page 572 Page 572 of 1814 DPNSS1 Route Optimisation/MCDN Trunk Anti-Tromboning Interworking Figure 57 MCDN/DPNSS1 RO/TAT Interworking scenario, after TAT has been applied Node 1 Node 2 Node 3 Meridi Meridi Meridi an 1 an 1 an 1 tromboned Station A routes Station B are dropped Station C...
Page 573 DPNSS1 Route Optimisation/MCDN Trunk Anti-Tromboning Interworking Page 573 of 1814 RO/TAT interworking within multiple MCDN/DPNSS1 gateways A RO/TAT Interworking is supported within a multiple gateway scenario, as illustrated by the following example. Referring to Figure 58, Station A on the originating node call Station B across the multiple gateway scenario over PRI and DPNSS1 trunks, as shown below.
Page 574: Operating Parameters
Page 574 of 1814 DPNSS1 Route Optimisation/MCDN Trunk Anti-Tromboning Interworking Abnormal RO/TAT interworking scenarios The following are possible scenarios whereby the RO/TAT Interworking feature may function abnormally. RO fails or is not configured, and TAT is configured. In the case of a DPNSS1/MCDN gateway, TAT optimises the PRI trunks on the MCDN side, but the DPNSS1 trunks are not optimised on the DPNSS1 side.
Page 575: Feature Interactions
DPNSS1 Route Optimisation/MCDN Trunk Anti-Tromboning Interworking Page 575 of 1814 RO/TAT Interworking functionality is not applied if the originating party of the first call or the terminating party of the second call is on a conference call. RO/TAT Interworking functionality is not applied if the originating party of the first call is an attendant.
Page 576: Feature Packaging
Page 576 of 1814 DPNSS1 Route Optimisation/MCDN Trunk Anti-Tromboning Interworking Network Call Redirection If Network Call Redirection is not configured in an DPNSS1/MCDN gateway, the displays are updated normally, since the RO/TAT Interworking feature is not affected. If Network Call Redirection is not configured in an MCDN/DPNSS1 gateway, the displays are not updated on the bridged sets on the MCDN side.
Page 577: Feature Implementation
DPNSS1 Route Optimisation/MCDN Trunk Anti-Tromboning Interworking Page 577 of 1814 Feature implementation No new steps are required to configure the DPNSS1 Route Optimisation/MCDN Trunk Anti-Tromboning Interworking feature. However, the following basic configuration must be done: • Configure MCDN Trunk Anti-Tromboning at the far-end switch, in LD 17 (TAT is configured on a D-Channel basis, and not on a route basis).
Page 578 Page 578 of 1814 DPNSS1 Route Optimisation/MCDN Trunk Anti-Tromboning Interworking 553-2901-301 Standard 9.00 January 2002...
Page 579: E.164/Esn Numbering Plan Expansion
Regional material statement The information presented in this section does not pertain to all market regions. Contact your system supplier or your Nortel Networks representative to verify support of this product in your area. International ISDN PRI Feature description and administration...
Page 580: Feature Description
Page 580 of 1814 E.164/ESN Numbering Plan Expansion Feature description The E.164/ESN Numbering Plan Expansion feature provides the capabilities to meet the International Telegraph and Telephone Consultative Committee (CCITT) recommendation E.164 for Integrated Services Digital Network (ISDN) and Public Switching Telephone Network (PSTN) dialing. Generally, the following enhancements are offered by this feature: •...
Page 581: Summary Of Expanded Esn Functionalities
E.164/ESN Numbering Plan Expansion Page 581 of 1814 Summary of expanded ESN functionalities Table 45 summarizes the changes made to the ESN functionality. Please note that the components that are not affected are not listed. Table 45 Summary of ESN changes (Part 1 of 2) Component Expanded Maximum number of digits for a Special Numbering...
Page 582 Page 582 of 1814 E.164/ESN Numbering Plan Expansion Table 45 Summary of ESN changes (Part 2 of 2) Total number of digits for screening under Free Special Number Screening (FSNS). Maximum number of possible Supplemental Digit 9 (‘ALOW’ is Restriction and Recognition (SDRR) entry types. added).
Page 583: Summary Of Meridian 1 Base Features Enhancements
E.164/ESN Numbering Plan Expansion Page 583 of 1814 Summary of Meridian 1 base features enhancements Table 46 summarizes the changes made to the base Meridian 1 features functionality. Please note that the components that are not affected are not listed. Table 46 Summary of Meridian 1 base features changes Component...
Page 584: Summary Of Automatic Call Distribution (Acd) Enhancements
Page 584 of 1814 E.164/ESN Numbering Plan Expansion Summary of Automatic Call Distribution (ACD) enhancements Table 47 summarizes the changes made to the ACD functionality. Please note that the components that are not affected are not listed. Table 47 Summary of Meridian 1 ACD changes Component Expanded Maximum number of digits for the ACD Night...
Page 585: Summary Of Isdn Features Enhancements
E.164/ESN Numbering Plan Expansion Page 585 of 1814 Summary of ISDN features enhancements Table 49 summarizes the changes made to the ISDN functionality. Please note that the components that are not affected are not listed. Table 49 Summary of ISDN changes Component Expanded For ISDN BRI basic call service line access (BRIL),...
Page 586 Page 586 of 1814 E.164/ESN Numbering Plan Expansion The 31-digit expansion, pertaining to the Call Forward All Calls DN, does not apply to Meridian M2317 and M3000 sets, since their firmware limits entering a CFAC DN from the set to a maximum of 23 and 28 digits, respectively.
Page 587: Feature Interactions
E.164/ESN Numbering Plan Expansion Page 587 of 1814 Calling Party Privacy (CPP) allows a caller to block his or her name from appearing on the called party display. The call is marked as a CPP call by entering a CPP FFC, up to seven digits long. This means that up to seven additional digits may have to be stored for automatic dialing.
Page 588 Page 588 of 1814 E.164/ESN Numbering Plan Expansion For ESN expansions: • Basic Alternate Route Selection (BARS) package 57; • Network Alternate Route Selection (NARS) package 58; and • Flexible Numbering Plan (FNP) package 160. For ISDN expansions: • Digit Display (DDSP) package 19; •...
Page 589: Feature Implementation
E.164/ESN Numbering Plan Expansion Page 589 of 1814 • 500 Telephone Features (SS5) package 73; • Controlled Class of Service (CCOS) package 81; • Background Terminal (BGD) package 99; • Flexible Feature Codes (FFC) package 139; and • Phantom Terminal Numbers (PHTN) package 254. Feature implementation Task summary list The following is a summary of the tasks in this section:...
Page 590 Page 590 of 1814 E.164/ESN Numbering Plan Expansion LD 87 – For a Free Special Number Screening Index, configure the expansion pertaining to the maximum number of Special Numbers to be screened. 10 LD 87 – For a Trunk Steering Code, configure the expansion pertaining to the maximum number of Flexible Numbers.
Page 591 E.164/ESN Numbering Plan Expansion Page 591 of 1814 DCFW ll xxx...x Enter the maximum number of digits in the Default Call Forward DN for a Phantom DN. ll = 4,8,12,16,20,24,28,31 (entries are rounded up to the next valid length.) xx...x = the Default Call Forward All Calls DN. ICF (4)-31 Enter the maximum number of digits in the Internal Call Forward DN for a Phantom DN.
Page 592 Page 592 of 1814 E.164/ESN Numbering Plan Expansion nn CFW ll xxx...x Enter the maximum number of digits that may be stored for the Call Forward All Calls DN. nn = Key number ll = (4)-31 (for M2317 and M3000 sets, the accepted range is (4)-23) xx...x = the Call Forward All Calls DN (this is an optional entry.)
Page 593 E.164/ESN Numbering Plan Expansion Page 593 of 1814 TYPE: Redirection data. CUST Customer number. - CCFWDN xxx...x Enter the Customer Call Forward DN, up to 23 digits (this entry is made for a new CCFWDN, or if the length of an existing CCFWDN has been expanded.) Enter X for no entry.
Page 594 Page 594 of 1814 E.164/ESN Numbering Plan Expansion LD 86 – For the ESN data block, configure the expansion pertaining to the maximum number of Supplemental Digit Restriction and Recognition blocks, and the maximum number of Digit Manipulation tables. Prompt Response Description Add new data, or change existing data.
Page 595 E.164/ESN Numbering Plan Expansion Page 595 of 1814 Enter the Digit Manipulation table. 1-999 1-999 = for Flexible Numbering Plan 1-255 1-255 = for BARS/NARS 1-31 1-31 = for Coordinated Dialing Plan. The maximum number of Digit Manipulation tables is defined using prompt MXDM, in the ESN data block.
Page 596 Page 596 of 1814 E.164/ESN Numbering Plan Expansion OVLL (0)-24 Enter the minimum Overlap Digit Length, pertaining to Overlap Sending. If 0 (the default) is entered, then the Flexible Digit Number Length (FLEN) determines whether Overlap Sending takes place. LD 87 – For a Free Special Number Screening Index, configure the expansion pertaining to the maximum number of Special Numbers to be screened.
Page 597 E.164/ESN Numbering Plan Expansion Page 597 of 1814 LD 90 – For Network Translation tables, configure the expansion pertaining to the maximum number of Special Numbers digits, the maximum number of digits for Flexible Numbers, the maximum number of Supplemental Digit Restriction and Recognition digits per entry, and the addition of “allow”...
Page 598: Feature Operation
Page 598 of 1814 E.164/ESN Numbering Plan Expansion The maximum number of digits entered in response to the DENY, LDID, LDDD, DID, DDD and ALOW prompts, which follow, must be less than 10, or 7-m (8-m for 1+ dialing) for Central Office translation data (NXX), 10-m (11-m for 1= dialing) for Numbering Plan Area Code translation data (NPA), or 19-m for Special Numbers Translation data...
Page 599: Feature Description
Page 599 of 1814 Electronic Lock Network Wide/Electronic Lock on Private Lines Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 600: Electronic Lock Network Wide/Electronic Lock On Private Lines
Page 600 of 1814 Electronic Lock Network Wide/Electronic Lock on Private Lines In a Meridian Customer Defined Network (MCDN) environment, Electronic Lock Network Wide can be used to change the Class of Service of a set in a remote location. Electronic Lock Network Wide is activated or deactivated from any node by dialing the Electronic Lock Flexible Feature Code (FFC), the password, and the DN of the set to be changed.
Page 601: Feature Interactions
Electronic Lock Network Wide/Electronic Lock on Private Lines Page 601 of 1814 The Electronic Lock feature must be equipped on both originating and remote nodes. The FFC used is defined on the node from which Network Electronic Lock is being activated. To activate or deactivate Network Electronic Lock from any remote node, the user has to use the FFC Electronic Lock Activate (ELKA) or Electronic Lock Deactivate (ELKD) code defined on that remote node.
Page 602 Page 602 of 1814 Electronic Lock Network Wide/Electronic Lock on Private Lines Direct Inward System Access (DISA) The Electronic Lock feature cannot be activated or deactivated when accessing the node through DISA. Digital Private Network Signaling System (DPNSS1) Digital Access Signaling System (DASS2) Analog Private Network Signaling System (APNSS) Electronic Lock Network Wide is not supported on DPNSS1, DASS2, or APNSS trunks.
Page 603: Feature Packaging
Electronic Lock Network Wide/Electronic Lock on Private Lines Page 603 of 1814 Virtual Network Services (VNS) Electronic Lock may function in a VNS environment. Feature packaging Electronic Lock Network Wide/Electronic Lock on Private Lines is packaged under Flexible Feature Codes (FFC) package 139, and it has the following dependencies: •...
Page 604 Page 604 of 1814 Electronic Lock Network Wide/Electronic Lock on Private Lines 10 LD 10 – Set the Station Control Password and Controlled Class of Service Allowed for each analog (500/2500 type) telephone. 11 LD 11 – Set the Station Control Password and Controlled Class of Service Allowed for each Meridian 1 proprietary telephone.
Page 605 Electronic Lock Network Wide/Electronic Lock on Private Lines Page 605 of 1814 - - PWD2 xxxx PWD2 password for confirmation - FFCS (NO) YES Change Flexible Feature Code end-of-dialing indicator - - STRL String Length of end-of-dial indicator - - STRG String to indicate end-of-dialing - ADLD (0)-20...
Page 606 Page 606 of 1814 Electronic Lock Network Wide/Electronic Lock on Private Lines l s c u Terminal number. For Option 11C. SCPW xxxxxxxx Station Control Password (1 to 8 digits, as defined in LD 15). CCSA Controlled Class of Service Allowed. LD 57 –...
Page 607 Electronic Lock Network Wide/Electronic Lock on Private Lines Page 607 of 1814 NCOS 0-99 Network Class of Service group number. – FRL (0)-7 Facility Restriction level. Electronic Lock on Private Lines Use the following overlays to implement Electronic Lock Network on Private Lines.
Page 608 Page 608 of 1814 Electronic Lock Network Wide/Electronic Lock on Private Lines - SCPL Station Control Password Length. - SBUP (YES) NO Enable use of station control passwords for set based administration user level access - - PWD2 xxxx PWD2 password for confirmation - FFCS (NO) YES Change Flexible Feature Code end-of-dialing indicator...
Page 609 Electronic Lock Network Wide/Electronic Lock on Private Lines Page 609 of 1814 TYPE: Telephone type. CUST 0-99 Customer number. l s c u Terminal number. For Option 11C. SCPW xxxxxxxx Station Control Password (1 to 8 digits, as defined in LD 15). CCSA Controlled Class of Service Allowed.
Page 610: Feature Operation
Page 610 of 1814 Electronic Lock Network Wide/Electronic Lock on Private Lines Feature operation Electronic Lock Network Wide In this example, an MCDN ISDN network is set up connecting Node 1 to Node 2. Set A is the Controlling set. Set B is the set to be locked and unlocked by Set A.
Page 611: Electronic Lock On Private Lines
Electronic Lock Network Wide/Electronic Lock on Private Lines Page 611 of 1814 To lock set B (in Node 2) from set A (in Node 1), the user goes off-hook and dials the Electronic Lock Activate (ELKA) FFC defined in the Customer Data Block of Node 1, followed by the Station Password (SCPW) defined for set B, and the digits that set A would normally dial to ring set B (e.g., 41 + 9999 + 6-343-3000).
Page 612 Page 612 of 1814 Electronic Lock Network Wide/Electronic Lock on Private Lines 553-2901-301 Standard 9.00 January 2002...
Page 613 Page 613 of 1814 Electronic Switched Network Compatibility on ISDN Contents list The following are the topics in this section: Feature description ........Operating parameters .
Page 614 Page 614 of 1814 Electronic Switched Network Compatibility on ISDN ISDN enhances Electronic Switched Network (ESN), by allowing ESN capabilities such as Network Class of Service, Network Alternate Route Selection, ESN queuing, and Network Authorization Codes across a Meridian 1 ISDN network. ISDN provides a series of messages containing imbedded information;...
Page 615 Electronic Switched Network Compatibility on ISDN Page 615 of 1814 Table 50 ESN features available with ISDN (Part 2 of 2) ESN features Available on ISDN? Network Alternate Route Selection —NARS Access Codes —Uniform Dialing Plan —Time of Day Routing —Network Routing Control —Satellite Link Control —Digit Screening...
Page 616 Page 616 of 1814 Electronic Switched Network Compatibility on ISDN Operating parameters There are no operating parameters associated with this feature Feature interactions There are no feature interactions associated with this feature. Feature packaging This feature is included in base Meridian 1 System Software. Feature implementation There are no specific implementation procedures for this feature.
Page 617 Page 617 of 1814 Electronic Switched Network interworking Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 618: Electronic Switched Network Interworking
Page 618 of 1814 Electronic Switched Network interworking • access queuing • receive Expensive Route Warning Tone (ERWT) • access network speed call When NCOS information, which includes Traveling Class of Service (TCOS) information, is sent to a DMS-100, the DMS switch can provide access to AT&Ts Electronic Tandem Network (ETN).
Page 619 Electronic Switched Network interworking Page 619 of 1814 ESN access code configuration with package 148 For Meridian 1 configurations that utilize ISDN networking features, ESN access code insertion must be performed on the receiving Meridian 1. The originating Meridian 1 must not use digit manipulation to insert and send the ESN access code to the terminating Meridian 1.
Page 620 Page 620 of 1814 Electronic Switched Network interworking Note: When a trunk access code is used to dial on an ISDN route, the caller dials all digits without waiting for subsequent dial tones. Table 51 Default Call Types Dial method Default call type Comment Direct dial...
Page 621 Electronic Switched Network interworking Page 621 of 1814 Prompt Response Description Location Code Coordinated Dialing Plan Special number UKWN Unknown call type ESN access code insertion Procedure 2 and Procedure 3 describe how to automatically insert the needed NARS/BARS access code to the incoming digit stream. This is required for ISDN networking features such as Network Ring Again (NRAG) and Network Message Services (NMS).
Page 622 Page 622 of 1814 Electronic Switched Network interworking LD 15 – Map the NARS/BARS access code to the incoming call types. Prompt Response Description Add or change data. TYPE Networking data. Access code 2. Enter call types (type of number) that use access code 2.
Page 623 Electronic Switched Network interworking Page 623 of 1814 Figure 61 Private Network Hopoff DMS-100, or Meridian 1 or Meridian 1 Meridian SL-100 Private Network Private network — POTS capability only ISDN PRI capability 553-1536 Private Network Overflow This service allows overflow from a private network onto public network facilities (see Figure 62).
Page 624 Page 624 of 1814 Electronic Switched Network interworking Figure 62 Private Network Overflow DMS-100, or Meridian SL-100 n+1 private Private network calls Network Meridian SL-1 DMS-100 n private trunks Meridian SL-1 553-1500 Feature operation No specific operating procedures are required to use this feature. 553-2901-301 Standard 9.00 January 2002...
Page 625: Emergency Services Access
Page 625 of 1814 Emergency Services Access Emergency Services Access (ESA) feature places a customer in compliance with new federal legislation that requires the Private 911 type of functionality provided by ESA. Please note, however, that the ESA feature is also generally useful for users who are not subject to legislation, and is broad enough to be used in different countries.
Page 626 Page 626 of 1814 Emergency Services Access 553-2901-301 Standard 9.00 January 2002...
Page 627: Equi-Distribution Routing Network Attendant Service
Page 627 of 1814 Equi-distribution Routing Network Attendant Service Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 628 Page 628 of 1814 Equi-distribution Routing Network Attendant Service The load level is a value defined as the customer-defined efficiency factor, multiplied by the number of calls waiting for an attendant, divided by the number of attendants in service. The efficiency factor is a value between 0-8064.
Page 629 Equi-distribution Routing Network Attendant Service Page 629 of 1814 • Integrated Services Digital Network Signaling (ISDN) package 145, or ISDN Signaling Link (ISL) package 147; and • Network Attendant Service (NAS) package 159. Feature implementation Task summary list The following is a summary of the tasks in this section: LD 15 –...
Page 630 Page 630 of 1814 Equi-distribution Routing Network Attendant Service ALST Alternatives List.Attendant alternatives for NAS routing (up to 4 alternatives may be defined for each schedule period). (N) Y Drop Back busy option. YES = Drop Back Busy allowed, NO = Drop Back Busy denied.
Page 631: Analog E&M Tie Trunks
Page 631 of 1814 Error Handling on ISDN Signaling Link Analog E&M TIE Trunks Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 632: Error Handling On Isdn Signaling Link Analog E&M Tie Trunks
Page 632 of 1814 Error Handling on ISDN Signaling Link Analog E&M TIE Trunks Once the external equipment removes the error condition, a message is printed and a restart message is sent on the D-channel to indicate that the unit is usable.
Page 633 Error Handling on ISDN Signaling Link Analog E&M TIE Trunks Page 633 of 1814 Feature implementation Task summary list The following is a summary of the tasks in this section: LD 16 – Configure ISL on Analog Trunks.2 LD 16 – Configure ISL on Analog Trunks. Prompt Response Description...
Page 634 Page 634 of 1814 Error Handling on ISDN Signaling Link Analog E&M TIE Trunks These overlay changes ensure that error states on both sides of the link are not affected by enabling/disabling the unit. Error Applied to Unit • An error condition can be generated by the external equipment when a unit is idle, during call setup or when a call is established.
Page 635 Error Handling on ISDN Signaling Link Analog E&M TIE Trunks Page 635 of 1814 Error State When the unit is an error state then it is not available for incoming or outgoing calls. The error state is maintained until it is cleared by external equipment. Outgoing Calls Normal call processing selects the next available channel for outgoing calls.
Page 636 Page 636 of 1814 Error Handling on ISDN Signaling Link Analog E&M TIE Trunks 553-2901-301 Standard 9.00 January 2002...
Page 637: Feature Description
Page 637 of 1814 EuroISDN 7kHz/Videotelephony Teleservices Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 638: Euroisdn 7Khz/Videotelephony Teleservices
Page 638 of 1814 EuroISDN 7kHz/Videotelephony Teleservices The Videotelephony teleservice is a real-time, audiovisual teleservice in which voice and moving pictures are interchanged by means of one or two 64 kbit/s circuit-mode connections. The 7 kHz/Videotelephony teleservices are supported over EuroISDN PRI2 and Basic Rate Trunk interfaces, and on ETSI Basic Rate Interface sets.
Page 639: Operating Parameters
EuroISDN 7kHz/Videotelephony Teleservices Page 639 of 1814 7 kHz or videotelephony teleservice request with fall-back not allowed If fall-back is not allowed, the call may be either established with the requested teleservice, or rejected. If the call request reaches a non EuroISDN link, or if the requested set is a non-ETSI BRI set, the call is rejected.
Page 640: Feature Interactions
Page 640 of 1814 EuroISDN 7kHz/Videotelephony Teleservices Feature interactions Call Forward All Calls Fall-back may be applied, if Call Forward All Calls has been activated. If fall-back is not allowed, the call is treated as per normal operation. If fall-back has already occurred, a call request for the alternate (3.1 kHz) teleservice is sent to the forwarded-to set or trunk.
Page 641 EuroISDN 7kHz/Videotelephony Teleservices Page 641 of 1814 Advice On Charge If a second connection is established for a videotelephony teleservice, the charge information is received separately for the two connections, since there is no way to identify that the two connections relate to the same videotelephony call.
Page 642: Feature Packaging
Page 642 of 1814 EuroISDN 7kHz/Videotelephony Teleservices Meridian Link For a call request for the 7 kHz or videotelephony teleservice terminating on a Meridian link application, fall-back occurs if allowed, or else the call is rejected. Meridian Mail For a call request for the 7 kHz or videotelephony teleservice terminating on Meridian Mail, fall-back occurs if allowed, or else the call is rejected.
Page 643: Feature Implementation
EuroISDN 7kHz/Videotelephony Teleservices Page 643 of 1814 Feature implementation Task summary list The following is a summary of the tasks in this section: LD 17 - Configure D-Channel for the ETS 300 403 interface. LD 16 - Configure the 7 kHz/Videotelephony teleservices for a PRI2 EuroISDN E403 route.
Page 644 Page 644 of 1814 EuroISDN 7kHz/Videotelephony Teleservices LD 16 - Configure the 7 kHz/Videotelephony teleservices for a PRI2 EuroISDN E403 route. Note: The EuroISDN route using the 7 kHz/Videotelephony teleservices must be configured as using the interface type of ETS 300 403 (IFC = E403), even if the link to the Central Office is still be based on ETS 300 102 implementation.
Page 645 EuroISDN 7kHz/Videotelephony Teleservices Page 645 of 1814 Austria. Denmark. Finland. Germany. Italy. Norway. Portugal. Sweden. Ireland. Holland. Switzerland. Belgium. Spain. United Kingdom. France. Commonwealth of Independent States (Russia and the Ukraine). - DSEL Data selection. 7VOD The route supports voice and data calls, and the telephony 7 kHz/Videotelephony teleservices.
Page 646: Isdn Basic Rate Interface Implementation
Page 646 of 1814 EuroISDN 7kHz/Videotelephony Teleservices RTMB 0-511 1-510 Route number and member number, for Options 51C-81C. 0-127 1-510 For Option 11C. ISDN Basic Rate Interface implementation LD 16 - Configure the 7 kHz/Videotelephony teleservices for an ISDN BRI EuroISDN E403 route, in the Route Data Block.
Page 647 EuroISDN 7kHz/Videotelephony Teleservices Page 647 of 1814 - - CNTY Enter country pertaining to the E403 interface. If either ETSI or NET are entered, the interface is fully compliant with ETS 300 403. The entered value must match the entry in LD 17. ETSI ETS 300 403 for the user side.
Page 648 Page 648 of 1814 EuroISDN 7kHz/Videotelephony Teleservices LD 27 - Configure the ETSI ISDN BRI sets, on the Digital Subscriber Loop (DSL), for voice and data. Prompt Response Comment Add new data Change existing data. TYPE Digital Subscriber Loop data block. l s c dsl# DSL Terminal Number location lll (superloop) = 0-156 (must be zero or a number divis ible...
Page 649 EuroISDN 7kHz/Videotelephony Teleservices Page 649 of 1814 LD 27 - Configure the Terminal Service Profile (TSP) for voice and data, and the 7 kHz/Videotelephony teleservices on the ETSI ISDN BRI sets. Prompt Response Comment Add new data Change existing data. TYPE Terminal Service Profile data block.
Page 650: Maintenance And Diagnostics Guidelines
Page 650 of 1814 EuroISDN 7kHz/Videotelephony Teleservices Maintenance and diagnostics guidelines Call Trace (LD 80) LD 80 is used to gather information pertaining to a call. If the call originated or terminated over a ISDN trunk, the following information is printed, in addition to the basic call information: •...
Page 651: No Correlation Between Two Connections For The Same Call
EuroISDN 7kHz/Videotelephony Teleservices Page 651 of 1814 Bearer capability print format when fall-back is allowed If fall-back is allowed, there are two bearer capability IE contained in the received SETUP message. There are two print formats for the bearer capability. When the used teleservice has not yet been selected, both values are printed in the order that they are received.
Page 652 Page 652 of 1814 EuroISDN 7kHz/Videotelephony Teleservices 553-2901-301 Standard 9.00 January 2002...
Page 653: Regional Material Statement
Feature operation ......... . Regional material statement ISDN BRI trunking is not available in North America. Contact your system supplier or your Nortel Networks representative to verify support of this product in your area. Feature description...
Page 654 Page 654 of 1814 EuroISDN Continuation In addition, the following functionalities are provided by the EuroISDN Continuation feature: • Intercept treatment upon reception of an invalid or incomplete called party number; • Interception to an attendant for EuroISDN voice calls terminating on a data device;...
Page 655: Operating Parameters
EuroISDN Continuation Page 655 of 1814 This development also provides a subset of the ETSI Generic functional protocol for the support of supplementary services. Implementation relies on the Generic Functional (GF) Transport platform in the ISDN QSIG GF Transport feature. The ETSI GF subset provides two types of supplementary service control entities as follows: •...
Page 656: Feature Interactions
Page 656 of 1814 EuroISDN Continuation For Connected Line Identification Presentation (COLP) supplementary service, sending or restricting connected line identification is not supported on ISDN BRI sets on a per call basis. Feature interactions Auto terminate Call This feature is not supported. Call Back Queuing and Off-hook Queuing This feature is not supported with Overlap Signaling.
Page 657 EuroISDN Continuation Page 657 of 1814 ISDN Calling Line Identification Enhancements The EuroISDN Continuation feature allows Home National Numbers and Home Local Numbers to be configured on a route. When an ISDN call is made from a set to a EuroISDN interface, the Calling Line Identification (CLID) constructed by EuroISDN, based on the outgoing route, takes precedence over the CLID constructed for the calling station set.
Page 658 Page 658 of 1814 EuroISDN Continuation Tandem Interworking When tandem interworking occurs, the EuroISDN trunk terminates on an ISDN link terminating on an analog trunk. When the tandem SETUP message is sent, the CALL PROCEEDING message is sent to the PSTN to indicate that no further called party information is required.
Page 659: Feature Packaging
EuroISDN Continuation Page 659 of 1814 Table 52 Networking features supported by more than one ISDN interface Calling Line ID Connected Number Transit Counter Special Dial Tone after Dialed Numbers Special dial tones after dialed numbers are not supported for incoming calls. Transfer of Unanswered Call The EuroISDN Continuation feature supports the transfer of a call from a set dialing an external number, before the external set answers, to both local and...
Page 660 Page 660 of 1814 EuroISDN Continuation For Primary Rate Interface (PRI), the following software packages are required: • Digit Display (DDSP) package 19; • Integrated Services Digital Network (ISDN) package 145; • 2.0 Mbit Primary Rate Interface (PRI2) package 154; •...
Page 661: Feature Implementation
EuroISDN Continuation Page 661 of 1814 For the Coordinated Dialing Plan (CDP), package 59 and the following packages are required: • Integrated Services Digital Network (ISDN) package 145; • 2.0 Mbit Primary Rate Interface (PRI2) package 154; • Flexible Numbering Plan (FNP) package 160; •...
Page 662 Page 662 of 1814 EuroISDN Continuation TYPE: Telephone type. FAXA Fax Class of Service allowed for set or modem. ISDN call is generated with 3.1 KHz bearer capability. FAXD = Fax Class of Service denied. LD 17 – Create a new D-channel. Prompt Response Description...
Page 663 EuroISDN Continuation Page 663 of 1814 - - CNTY Austria. Denmark. (ETSI) ETS 300-102 basic protocol. Finland. Germany. Italy. Norway. Portugal. Sweden. Ireland. Holland. Switzerland. Belgium. Spain. United Kingdom. - - DCHL 0-159 PRI loop number. - RCAP COLP Enter COLP to support Connected Line Identification Presentation as a remote capability.
Page 664 Page 664 of 1814 EuroISDN Continuation CUST Customer number. ROUT Route number. TKTP Trunk type, where: DID = Direct Inward Dialing. DTRK Digital trunk route. - DGTP Digital trunk type for route. PRI2 2.0 Mb Primary Rate Access. ISDN Basic Rate Access. - IFC EURO Interface type for route, where:...
Page 665 EuroISDN Continuation Page 665 of 1814 CLID OPT0 Prefix = 0, for North American dialing plan. This is the default value for ESIG and ISIG interfaces. OPT1 Prefix = 1, for international PFXs in CLID, any numbering type supported. This is the default value for all EuroISDN interfaces.
Page 666: Euroisdn Continuation
Page 666 of 1814 EuroISDN Continuation - - HNTN 0-9999 Home National Number. This number is similar to the PFX1 number prompted in LD 15. It is added to this overlay so that this prefix can be configured on a route basis as required in some countries (e.g., Italy).
Page 667: Feature Operation
EuroISDN Continuation Page 667 of 1814 LD 14 – Configure new DID trunks. Prompt Response Description NEW xx Add a new data block to the system. Follow NEW with a value of 1-255 to create that number of consecutive trunks. TYPE Direct Inward Dialing data block.
Page 668 Page 668 of 1814 EuroISDN Continuation 553-2901-301 Standard 9.00 January 2002...
Page 669: Regional Material Statement
Feature operation ......... . Regional material statement ISDN BRI trunking is not available in North America. Contact your system supplier or your Nortel Networks representative to verify support of this product in your area. International ISDN PRI Feature description and administration...
Page 670: Feature Description
Page 670 of 1814 EuroISDN Continuation Phase III Feature description The EuroISDN feature provides ISDN PRI and ISDN BRI connectivity between the Meridian 1 and Public Exchanges that comply with the European Telecom Standards Institute (ETSI) specification ETS 300 102 for the Layer 3.
Page 671: Optional Sending Of Last Forwarding Dn As Clid
EuroISDN Continuation Phase III Page 671 of 1814 Optional sending of last forwarding DN as CLID In a call redirection scenario (Call Forward All Calls, Call Forward No Answer, Hunt, and the ACD redirections, Night Call Forward and Interflow) occurring at a gateway node, the (optional) capability, on a per system basis, of sending the last forwarding DN as Calling Line Identification (CLID) information.
Page 672 Page 672 of 1814 EuroISDN Continuation Phase III Figure 63 Incoming EuroISDN call redirected back to the Public Network/PBX Station A Station A calls Station B Gateway Standard ISDN connectivity Private DID or CO Exchange C e n t r a l O f f i c e Station B is redirected to Station C...
Page 673 EuroISDN Continuation Phase III Page 673 of 1814 Figure 64 MCDN/QSIG call redirected to the Public Network/PBX Originating Gateway Standard ISDN Private connectivity Exchange DID or CO MCDN/QSIG C e n t r a l O f f i c e Station B is redirected Station A calls to Station C...
Page 674 Page 674 of 1814 EuroISDN Continuation Phase III Figure 65 Internal call (stand-alone case) redirected to the Public Network/PBX Station A Station A calls Station B Gateway Standard ISDN Private connectivity Exchange DID or CO Station B C e n t r a l O f f i c e Station B is Station C...
Page 675: Trunk Route Optimization - Before Answer On Euroisdn Trunks
EuroISDN Continuation Phase III Page 675 of 1814 Figure 66 MCDN call redirected to the Public Network/PBX from a non-gateway node Station C Station A Station A calls Station C Station B is redirected to Satation D Standard ISDN connectivity Originating DID or CO MCDN...
Page 676 Page 676 of 1814 EuroISDN Continuation Phase III Figure 67 EuroISDN calling scenario before Trunk Optimization is applied Station A Station B Station A calls Station B MCDN EuroISDN link MCDN C e n tr a l O f f ic e MCDN Gateway Transit...
Page 677: Numbering Plan Identification And Type Of Number In Cdr Tickets For Euroisdn Calls
EuroISDN Continuation Phase III Page 677 of 1814 Figure 68 EuroISDN calling scenario after Trunk Optimization has been applied As soon as redirection occurs, the redundant Station A Station B MCDN trunks between the Transit node and Terminating node are dropped, leaving Station A and Private Station C connected...
Page 678: Operating Parameters
Page 678 of 1814 EuroISDN Continuation Phase III The NPI and TON fields are left blank if the calls are internal, are over outgoing ISDN trunks, are over incoming non-ISDN trunks, or if the FCDR prompt is set to OLD or the CLID prompt is set to NO (note that the FCDR prompt takes precedence over the CLID prompt, that is, if FCDR is set to OLD and the CLID prompt is set to YES, the fields are left blank.) The NPI and TON are both printed on the third line of the CDR ticket, at...
Page 679: Feature Interactions
EuroISDN Continuation Phase III Page 679 of 1814 Feature interactions Call Completion Supplementary Service Call Completion interacts with Call Transfer Over EuroISDN SN3. Call Completion Free Notification can only be presented to the Call Completion originating station and cannot be transferred to any other station. However, once the Call Completion call is established, it behaves as a normal call with respect to Call Transfer.
Page 680 Page 680 of 1814 EuroISDN Continuation Phase III Intercept Treatment on Invalid or Partial Dialing The Partial Dial Timing (PRDL), Vacant Number Routing (VNR), and Intercept features handle dialing irregularities on the Meridian 1. The Intercept feature allows calls with dialing irregularities to be routed to an attendant or to a Recorded Announcement, or to receive overflow or busy tone.
Page 681 EuroISDN Continuation Phase III Page 681 of 1814 The following three alternatives can be configured in Overlay 16 by responding to the PROG prompt to stop the network T310 timer: A PROGRESS message is sent to the network after the CALL PROCEEDING message.
Page 682 Page 682 of 1814 EuroISDN Continuation Phase III Networking Features Some networking features currently exist on more than one ISDN interface implemented on the Meridian 1. These features are listed in Table 53. Any networking feature that does not appear in the table is only supported on one ISDN interface and is rejected by the gateway when the service is requested.
Page 683: Feature Packaging
EuroISDN Continuation Phase III Page 683 of 1814 The transfer of an unanswered EuroISDN call interacts with the CDR feature. When the originating party completes the call transfer after the transferred-to set answers, a CDR Start (S) is generated when the transferred-to set answers. When one side releases the call, a CDR End (E) ticket is generated.
Page 684 Page 684 of 1814 EuroISDN Continuation Phase III • Basic Rate Interface (BRI) package 216 • Integrated Services Digital Network Basic Rate Interface Trunk Access (BRIT) package 233 Overlap Signaling is included in (OVLP) package 184. For the Uniform Dialing Plan (UDP), the following packages are also required: •...
Page 685: Feature Implementation
EuroISDN Continuation Phase III Page 685 of 1814 • Call Detail Recording on Teletype Terminal (CDR_TTY) package 5 • Calling Line Identification in Call Detail Recording (CLID_CDR_PKG) package 118 • New Format for Call Detail Recording (CDR_NEW) package 234 Feature implementation Task summary list The following is a summary of the tasks in this section: LD 15 –...
Page 686 Page 686 of 1814 EuroISDN Continuation Phase III OCLI (NO) NO = No manipulation is done on outgoing CLID for calls forwarded over EuroISDN links. EXT = The last forwarding DN is sent as CLID information for incoming calls over a standard ISDN (EuroISDN, APAC, NI-2) DID or CO link to a gateway Meridian 1 node, and redirected back over the standard ISDN (EuroISDN, APAC, NI-2) DID or CO link.
Page 687 EuroISDN Continuation Phase III Page 687 of 1814 - - CNTY Enter country pertaining to EuroISDN interface. Austria Denmark (ETSI) ETS 300-102 basic protocol Finland Germany Italy Norway Portugal Sweden Ireland Holland Switzerland Belgium Spain United Kingdom France Commonwealth of Independent States (Russia and the Ukraine).
Page 688 Page 688 of 1814 EuroISDN Continuation Phase III LD 16 – Configure new DID routes (the same responses to the IFC and CNTY prompts, as were used in LD 17, must be entered). Prompt Response Description Add new data. Change or delete existing data. TYPE Route Data Block.
Page 689 EuroISDN Continuation Phase III Page 689 of 1814 - - CNTY Enter country pertaining to EuroISDN and Asia Pacific interface type. Austria Denmark (ETSI) ETS 300-102 basic protocol Finland Germany Italy Norway Portugal Sweden Ireland Holland Switzerland Belgium Spain United Kingdom France Commonwealth of Independent States (Russia and the Ukraine).
Page 690 Page 690 of 1814 EuroISDN Continuation Phase III - CLID OPT0 Prefix = 0, for North American dialing plan. This is the default value for ESIG and ISIG interfaces. OPT1 Prefix = 1, for international PFXs in CLID, any numbering type supported.
Page 691 EuroISDN Continuation Phase III Page 691 of 1814 - CPFXS (YES) NO Customer-defined Prefixes option. This prompt is added as one of the sub-prompts of ISDN = YES. It is added at the end of the ISDN sub-prompts. If CPFXS = YES, when constructing the Calling or Connected Line Identification, the prefixes are retrieved from the Customer Data Block via the PFX1 and PFX2 prompts in LD 15, as is currently done.
Page 692: Feature Operation
Page 692 of 1814 EuroISDN Continuation Phase III LD 17 – Configure the Numbering Plan Identification (NPI) and Type of Number (TON) fields to be included in the CDR tickets, in addition to the CLID, for EuroISDN calls (this is automatically done by entering YES in response to the CLID prompt).
Page 693 Page 693 of 1814 EuroISDN ETS 300 403 Compliance Update Contents The following are the topics in this section: Feature description ........Existing EuroISDN functionalities supported by the EuroISDN ETS 300 403 Compliance Update feature .
Page 694: Euroisdn Ets 300 403 Compliance Update
Page 694 of 1814 EuroISDN ETS 300 403 Compliance Update The EuroISDN continuation feature expanded the scope of the original EuroISDN feature to provide application support for Belgium, Spain, Switzerland (ISDN PRI connectivity added to the ISDN BRI connectivity), and the United Kingdom. EuroISDN Continuation Phase III, added France, Russia and the Ukraine to the list of countries having country-specific Application Documents comply with ETS 300 102 for EuroISDN.
Page 695: Ets 300 403 Compliance Update Feature
EuroISDN ETS 300 403 Compliance Update Page 695 of 1814 With the EuroISDN ETS 300 403 Compliance Update feature, all of the functionalities provided by the previous offerings of the EuroISDN features are supported, along with the following enhancements: • Support for signalling procedures for bearer capability and High Layer Capability selections by, providing repeatable Bearer capability, High layer compatibility Information Elements (IEs) in the SETUP message.
Page 696 Page 696 of 1814 EuroISDN ETS 300 403 Compliance Update Note: The ETSI GF does not by itself control any supplementary service but rather provides a generic transport platform that will support ETSI compliance supplementary services. The ETSI Generic Functional protocol is implemented for all ETSI interfaces.
Page 697 EuroISDN ETS 300 403 Compliance Update Page 697 of 1814 Any feature that is not listed in this table is not supported at gateways with EuroISDN connectivity. A “YES”/ “NO” indicates that the gateway is/is not supported. A “NS” indicates the service is not supported on the specified interface.
Page 698 Page 698 of 1814 EuroISDN ETS 300 403 Compliance Update • Capability of Transferring outgoing EuroISDN calls after completion of dialling (applies only for Italy). • Calling Line Identification and Connected Line Identification transparency to/from EuroISDN to/from a BRI set. •...
Page 699: Operating Parameters
EuroISDN ETS 300 403 Compliance Update Page 699 of 1814 • Capability of immediately releasing rejected BRI data calls without providing tone provision to the BRI terminal. • Capability, on a per configuration basis, of sending last forwarding DN as a CLID information, for the following types of calls: —...
Page 700 Page 700 of 1814 EuroISDN ETS 300 403 Compliance Update Operating parameters pertaining to Call Control Procedures: • If more than one Channel Identification IE is received in a SETUP message, only the first one is used by the Meridian 1. If it is not available, the call is processed as per the channel negotiation configuration.
Page 701 EuroISDN ETS 300 403 Compliance Update Page 701 of 1814 Operating parameters pertaining to ETSI GF: • ETSI GF gateways to and from other signalling systems, such as DPNSS1, QSIG, and MCDN, are not supported. • The following ETSI GF procedures are not implemented: —...
Page 702: Feature Interactions
Page 702 of 1814 EuroISDN ETS 300 403 Compliance Update • The Facility Information Element (FIE) is a repeatable IE, and its length is application dependent. However, due to system capacity considerations, such as call register usage and real time usage, there are two types of limitations enforced by the ETSI GF transport platform (actually by the ISDN GF transport platform provided by the ISDN QSIG GF development):...
Page 703 EuroISDN ETS 300 403 Compliance Update Page 703 of 1814 Intercept Treatment on Invalid or Partial Dialing There are three features that are involved in the treatment of calls with dialling irregularities. These are the Partial Dial Timing (PRDL), the Vacant Number Routing (VNR), and the Intercept features.
Page 704 Page 704 of 1814 EuroISDN ETS 300 403 Compliance Update — an incomplete number with a Sending complete IE has been received. • If the number received is not completed and not yet invalid, one of the following timer is started: —...
Page 705 EuroISDN ETS 300 403 Compliance Update Page 705 of 1814 The transfer of an unanswered EuroISDN outgoing call interacts with the CDR feature. When the originating party completes the transfer, a CDR ticket type “S” (Start) is generated as soon as the transferred party answers. If one side releases the call, a second CDR ticket E is generated corresponding to the end of the communication.
Page 706 Page 706 of 1814 EuroISDN ETS 300 403 Compliance Update Call Completion Supplementary Service Call Completion interacts with Call Transfer over EuroISDN. This interaction is similar to the current Network Ring Again/Network Ring Again on No Answer, and Call Back When Free/Call back When Not in Use implementations.
Page 707 EuroISDN ETS 300 403 Compliance Update Page 707 of 1814 Optional Sending of Forwarding CLID The Meridian 1 is able, on a per configuration basis, to send the last forwarding DN as CLID information for different scenarios of forwarded calls when the redirection occurs on a gateway node. The functionality is activated for the following redirections: Call Forward All Calls, Call Forward No Answer, Hunt and the two ACD redirections, Night Call Forward and Interflow.
Page 708 Page 708 of 1814 EuroISDN ETS 300 403 Compliance Update Note: Note: An incoming DID/Central Office call, routed through a private ISDN network and then redirected back to the PSTN via the DID/Central Office link, is considered as an internal call. Hence, OCLI prompt has to be set to ALL for the outgoing CLID to be manipulated.
Page 709 EuroISDN ETS 300 403 Compliance Update Page 709 of 1814 Both fields only appear if the system configuration parameter CLID is set to YES, if the system configuration parameter FCDR is set to NEW and if there is an incoming ISDN trunk involved in the call. This means that both NPI and TON information are taken from the incoming trunk.
Page 710: Euroisdn Malicious Call Identification
Page 710 of 1814 EuroISDN ETS 300 403 Compliance Update A EuroISDN link can be used as a B-Channel for the VNS feature. Commonwealth of Independent States Phase II, MF Shuttle The gateway between EuroISDN and the CIS MF Shuttle is supported. Interworking with KD3 No interworking with KD3 is supported.
Page 711: Feature Packaging
EuroISDN ETS 300 403 Compliance Update Page 711 of 1814 Note: It is recommended that the MCTM timer be configured to a lower value than the T306 timer to avoid any timeout of the T306 timer on the network side. EuroISDN 7 kHz/Videotelephony teleservices Telephony 7 kHz and videotelephony teleservices are supported on ISDN BRI Line and EuroISDN interfaces.
Page 712: Feature Implementation
Page 712 of 1814 EuroISDN ETS 300 403 Compliance Update • Network Alternate Route Selection (NARS) package 58 or • Basic Alternate Route Selection (BARS) package 57 • Network Class of Service (NCOS) package 32 • Basic Routing (BRTE) package 14 For EuroISDN to interwork with MFC, MFE, DID, and DASS2/DPNSS1 gateways, the following additional packages are required: •...
Page 713 EuroISDN ETS 300 403 Compliance Update Page 713 of 1814 - PRI2 0-159 PRI2 loop number. 17 - Configure a D-Channel for the ETS 300 403 interface. Prompt Response Description REQ: Change existing data. TYPE ADAN Action Device and Number. - ADAN NEW DCH xx Add a D-Channel on port 0-63...
Page 714 Page 714 of 1814 EuroISDN ETS 300 403 Compliance Update Austria. Denmark. Finland. Germany. Italy. Norway. Portugal. Sweden. Ireland. Holland. Switzerland. Belgium. Spain. United Kingdom. France. Commonwealth of Independent States (Russia and the Ukraine). - RLS Software Release of the far-end switch. - RCAP aaaa Remote capabilities.
Page 715 EuroISDN ETS 300 403 Compliance Update Page 715 of 1814 - - OUT_T306 0-(30) Variable timer, in seconds, for received DISCONNECT message on outgoing calls allowing in-band tone to be heard. The network will stop sending after this timer times out. The value is stored in two-second increments, which are rounded up.
Page 716 Page 716 of 1814 EuroISDN ETS 300 403 Compliance Update - IFC E403 EuroISDN Interface conforming to the ETS 300 403, or the extended ETS 300 102 version for country-specific interfaces. Refer to the Note on page 694. - - CNTY Enter country pertaining to the E403 interface.
Page 717 EuroISDN ETS 300 403 Compliance Update Page 717 of 1814 - CLID OPT0 Prefix = 0, for North American dialing plan. This is the default value for ESIG and ISIG interfaces. OPT1 Prefix = 1, for international PFXs in CLID, any numbering type supported.
Page 718 Page 718 of 1814 EuroISDN ETS 300 403 Compliance Update - CPFXS (YES) NO Customer-defined Prefixes option. This prompt is added as one of the sub-prompts of ISDN = YES. It is added at the end of the ISDN sub-prompts. If CPFXS = YES, when constructing the Calling or Connected Line Identification, the prefixes are retrieved from the Customer Data Block via the PFX1 and PFX2...
Page 719: Feature Operation
EuroISDN ETS 300 403 Compliance Update Page 719 of 1814 LD 14 - Configure the PRI2 trunks for the E403 interface. Prompt Response Description Add new data. Change existing data. TYPE TIE trunk data block. Central Office Trunk data block. Direct Inward Dialing trunk data block.
Page 720 Page 720 of 1814 EuroISDN ETS 300 403 Compliance Update 553-2901-301 Standard 9.00 January 2002...
Page 721: Regional Material Statement
Trace Number (TRC) key lamp status ..... . . Regional material statement ISDN BRI trunking is not available in North America. Contact your system supplier or your Nortel Networks representative to verify support of this product in your area. Feature description...
Page 722: Euroisdn Malicious Call Identification
Page 722 of 1814 EuroISDN Malicious Call Identification This request is initiated by the activation of the Malicious Call Trace feature (MCT) from analog (500/2500) type sets using a SPRE code and a two-digit Flexible Feature MCT access code or from Meridian 1 proprietary sets and attendant consoles using the TRC feature key.
Page 723 EuroISDN Malicious Call Identification Page 723 of 1814 Figure 70 illustrates a situation where EuroISDN MCID is initiated after the active phase of a malicious call. Figure 70 EuroISDN MCID invoked after the active phase of a malicious call mct ticket incoming malicious call printed mct key...
Page 724: Malicious Call Trace Record Output
Page 724 of 1814 EuroISDN Malicious Call Identification When the MCID request is initiated via activation of the Malicious Call Trace feature, a MCID request message is sent to the Central Office from the called party node. The Central Office processes the MCID request and returns a message to indicate the successful operation.
Page 725: Operating Parameters
EuroISDN Malicious Call Identification Page 725 of 1814 Operating parameters Malicious Call Trace (MCT) feature is only activated against one call at one time from either a set or an attendant. If a set activates MCT against a call, then the traced call is put on hold and a second call is activated. A trace against the second call cannot be completed until the first call is disconnected.
Page 726: Feature Interactions
Page 726 of 1814 EuroISDN Malicious Call Identification Feature interactions Call Detail Recording If a DISCONNECT message is received from an incoming EuroISDN call and the Malicious Call Trace time is started, then this timer delays the output of the Call Detail Recording (CDR) record. This will not occur if the called party’s set goes on-hook.
Page 727: Feature Implementation
EuroISDN Malicious Call Identification Page 727 of 1814 Basic Rate Interface (BRI) connectivity requires: • Basic Rate Interface (BRI) package 216 • ISDN Basic Rate Interface Trunk Access (BRIT) package 233 Feature implementation Task summary list The following is a summary of the tasks in this section: LD 17 - Configure remote D-channel capability for EuroISDN interface for PRI and BRI.
Page 728 Page 728 of 1814 EuroISDN Malicious Call Identification LD 16 - Configure remote capability for EuroISDN interface for PRI. Prompt Response Description Change existing data. TYPE Route Data Block. DTRK Digital Trunk Route. - IFC EURO EuroISDN interface. RCAP MCID Add Malicious Call Identification as a new remote capability.
Page 729 EuroISDN Malicious Call Identification Page 729 of 1814 LD 15 - Modify system and software parameters. Prompt Response Description REQ: Change existing data. TYPE: Customer Features and options. MCTA Malicious Call Trace signal is allowed for attendants. MCTD = Malicious Call Trace is denied (default) MCDC Malicious Call DN/CLID printing allowed.
Page 730 Page 730 of 1814 EuroISDN Malicious Call Identification LD 11 - Configure Meridian 1 proprietary sets. Prompt Response Description REQ: Change existing data. TYPE: xxxx Telephone type, where: xxxx = SL1, 2006, 2008, 2009, 2016, 2018, 2112, 2216, 2317, 2616, 3000 l s c u Terminal Number.
Page 731 EuroISDN Malicious Call Identification Page 731 of 1814 LD 57 - Configure Flexible Feature Codes for Analog (500/2500 type) sets. Prompt Response Description Add new data. Change existing data TYPE Flexible Feature Code data block. CUST Customer number. CODE MTRC Malicious Call Trace code - MTRC xxxx...
Page 732: Feature Operation
Page 732 of 1814 EuroISDN Malicious Call Identification Feature operation There are no operating procedures specified for this feature. However, the Malicious Call Identification feature is activated by one of the following methods, depending on the station: • From an analog (500/2500) type set, a switch-hook flash is performed, and then a SPRE code and two-digit Flexible Feature MCT access code are dialed.
Page 733 EuroISDN Malicious Call Identification Page 733 of 1814 Lamp Dark This lamp state indicates an idle TRC key or failure of the call identification request to the CO. In an MCDN tandem scenario, the lamp goes from winking to dark if a Facility message received from the node nearest the CO indicates that the MCID request was unsuccessful.
Page 734 Page 734 of 1814 EuroISDN Malicious Call Identification 553-2901-301 Standard 9.00 January 2002...
Page 735: Euroisdn Trunk - Network Side
Feature operation ......... . Regional material statement ISDN BRI trunking is not available in North America. Contact your system supplier or your Nortel Networks representative to verify support of this product in your area. Feature description EuroISDN Trunk - Network Side refers to the behaviour of EuroISDN as a network interface (generally referred to as “network side”), where the...
Page 736 Page 736 of 1814 EuroISDN Trunk - Network Side ETSI EuroISDN network side compliance to go along with the ETSI EuroISDN user side compliance. The ETSI EuroISDN network side interface (EuroISDN Trunk - Network Side) provides the capability to connect the ETSI EuroISDN user side interface of a Common Peripheral Equipment (CPE) to the Meridian 1.
Page 737 EuroISDN Trunk - Network Side Page 737 of 1814 — User-to-User Signaling 1 (UUS1) information exchange transparency, which allows a calling and a called party to exchange small amounts of data over an ISDN PRI or ISDN BRI trunk’s D-Channel. This data is contained in the USER_USER Information Element (IE) within the call control messages.
Page 738 Page 738 of 1814 EuroISDN Trunk - Network Side Operating parameters The User-to-User transparency capability is only supported between EuroISDN trunks. The following specific hardware is required on Meridian 1 Options 51C, 61C, and 81C. For ISDN PRI access: • The NT8D72BA PRI2 card or the NTCK43 dual-port PRI2 card;...
Page 739 EuroISDN Trunk - Network Side Page 739 of 1814 Feature interactions Basic Call Gateways The gateways that are supported for the EuroISDN Trunk - Network Side connectivity are the same as the ones supported for the EuroISDN connectivities. Table 55 lists these gateways and the associated support for basic call functionality.
Page 740 Page 740 of 1814 EuroISDN Trunk - Network Side Table 55 Basic Call Gateways (Part 2 of 2) Gateway Basic Call Support MCDN Basic Voice Call Data Call (64K unrestricted) Calling Line ID transmission Basic Voice Call Calling Line ID transmission Note: For MFE, MFC, and CIS using DTI2, data calls are possible.
Page 741 EuroISDN Trunk - Network Side Page 741 of 1814 Connected Line Identification Presentation (COLP)/Connected Line Identification Restriction (COLR) The EuroISDN Trunk - Network Side connectivity can generate, tandem or receive a Connected Line Identification with presentation allowed (COLP) or restricted (COLR). A Connected Line Identification that is generated or tandemed is constructed in the same manner as the EuroISDN user mode connectivity.
Page 742 Page 742 of 1814 EuroISDN Trunk - Network Side Integrated Services Access (ISA) ISA is not supported on a EuroISDN Trunk - Network Side connectivity. ISA is currently implemented for the North American ISDN interfaces. ISA allows a B-channel to be configured as a universal trunk. For example, the same B-channel trunk can be used once as a Central Office trunk and the next time as a Direct Inward Dial trunk.
Page 743 EuroISDN Trunk - Network Side Page 743 of 1814 Network Call Redirection (Call Forward, Call Forward No Answer, Hunt) and Network Call Modification (Conference, Transfer) It is possible to have a set Call Forward, Call Forward No Answer or Hunt to an external number over a EuroISDN Trunk - Network Side connectivity ISDN PRI or ISDN BRI trunk.
Page 744 Page 744 of 1814 EuroISDN Trunk - Network Side Virtual Network Services Virtual Network Services is supported on a EuroISDN Trunk - Network Side connectivity, meaning that a EuroISDN Trunk - Network Side trunk can be used as a VNS bearer trunk. Feature packaging To support the network side EuroISDN Trunk - Network Side connectivity, EuroISDN Trunk - Network Side feature (MASTER), package 309, is...
Page 745 EuroISDN Trunk - Network Side Page 745 of 1814 For ISDN BRI access: LD 16 – For an ISDN or DPNSS1/DASS2 trunk, configure the route for the Bearer Capability-Based Routing call type. For ISDN PRI access: LD 17 – For the network side EuroISDN Trunk - Network Side connectivity, configure the D-Channel for the network side EuroISDN ETSI protocol.
Page 746 Page 746 of 1814 EuroISDN Trunk - Network Side CUST Customer number. ROUT Route number. DTRK Digital trunk. - IFC EURO Interface type. Enter EURO for EuroISDN. - - CNTY Country pertaining to EuroISDN interface. Enter NET for network side. LD 16 –...
Page 747 EuroISDN Trunk - Network Side Page 747 of 1814 - DSEL Data Selection. (VOD) Route is for both voice and data Route is voice only Route is data only 3VCE Route is voice and 3.1 KHz 3DTA Route is data and 3.1 KHz Transparent Data Network Feature operation No specific operating procedures are required to use this feature.
Page 748 Page 748 of 1814 EuroISDN Trunk - Network Side 553-2901-301 Standard 9.00 January 2002...
Page 749: Idle Extension Notification
Page 749 of 1814 Idle Extension Notification Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 750 Page 750 of 1814 Idle Extension Notification • The attendant can use Idle Extension Notification for extensions with ordinary HOT/MCN/MCR/SCN/ SCR DNs. It does not work for ACD DNs or PLDNs. • Only one Idle Extension Notification at a time can be requested for an extension.
Page 751 Idle Extension Notification Page 751 of 1814 • The Idle Extension Notification feature is not valid for the 2616 set. • If in an ISDN network environment there are nodes with the Idle Extension Notification feature active and nodes without the feature active, the feature will not work across the network.
Page 752 Page 752 of 1814 Idle Extension Notification If the SACP lamp is lit during the pre-dial Break-In sequence, the only available possibilities are: to press the Release key to request for Idle Extension Notification; to press the SACP key again to remove the request; or to press the Release SRC key to Release the source without requesting Idle Extension Notification.
Page 753 Idle Extension Notification Page 753 of 1814 It is not possible to request for Idle Extension Notification towards an extension that has the Do-Not-Disturb feature activated. The Idle Extension Notification feature is not supported on DPNSS networks. It is not possible to request for Idle Extension Notification towards an extension that is Second Degree Busy.
Page 754 Page 754 of 1814 Idle Extension Notification Feature packaging The following packages are required for Idle Extension Notification: • Attendant Break-in/Trunk Offer (BKI) package 127 • International Supplementary Features (SUPP) package 131 • Integrated Services Digital Network (ISDN) package 145 •...
Page 755 Idle Extension Notification Page 755 of 1814 xx SACP Key number, Semi-automatic Camp-on/Idle Extension Notification. LD 15 – Configure a new Incoming Call Indicator (ICI) key for customer data. Prompt Response Description REQ: New, or change. TYPE: Attendant Console options. CUST Customer number.
Page 756 Page 756 of 1814 Idle Extension Notification 553-2901-301 Standard 9.00 January 2002...
Page 757: Calling Line Identification
Page 757 of 1814 Incoming Trunk Programmable Calling Line Identification Contents The following are the topics in this section: Feature description ........Operating parameters .
Page 758: Incoming Trunk Programmable Calling Line Identification
Page 758 of 1814 Incoming Trunk Programmable Calling Line Identification Operating parameters This feature is not supported on the following outgoing interface types: • SL-1 interfaces, and • DPNSS1 interfaces. M911 trunks do not support the billing number. If the route defined is both incoming and outgoing, the billing number will only be used for incoming calls to support outgoing Integrated Services Digital Network (ISDN) routes.
Page 759 Incoming Trunk Programmable Calling Line Identification Page 759 of 1814 Feature packaging The following package is required for Incoming Trunk Programmable Calling Line Identification: • Integrated Services Digital Network (ISDN) package 145. For ISDN and networking, the following packages are required: •...
Page 760 Page 760 of 1814 Incoming Trunk Programmable Calling Line Identification LD 16 – Configure the outgoing route. Prompt Response Description Change. TYPE Route data block. ISDN ISDN route must be YES. xxxx Select the appropriate interface type for route (cannot be SL1 or IDA).
Page 761: Integrated Services Access
Feature operation ......... . Regional material statement This feature is only available in North America. Contact your system supplier or your Nortel Networks representative to verify support of this product in your area. Feature description Integrated Services Access (ISA) is an ISDN PRI feature offered by Meridian 1 for connecting to switches such as DMS-100 and DMS-250.
Page 762 Basic PRI configuration must be performed before Integrated Services Access (ISA) is defined (see “ISDN product overview”). ISA routes and trunks must be defined to access Nortel Network’s ISA functionality or AT&T’s Call-by-Call Service. You cannot configure trunks for the service route that also accesses the ISA master route.
Page 763 The NSF information dictates which service route the Meridian 1 will use to terminate an incoming call. Nortel Networks connectivity to DMS provides Public, Private, INWATS, OUTWATS, TIE, and FX call types. When specifying COT or DID, the default is the Public call type. The call types determine the NSF values.
Page 764 Integrated Services Access Page 764 of 1814 The values for the COT/DID service route (COTR), the WATS service route (WATR), and the TIE service route (TIER) are for incoming call termination only. Predefined NARS, BARS, or CDP allows multiple outgoing routes. The COTR can be a route number for a central office DID/DOD route.
Page 765 Integrated Services Access Page 765 of 1814 The sum of all Min values for the service route cannot exceed the number of B-channels defined for the ISA master route. When the NSF prompt is YES and the Max value is reached in a service route, the All Trunks Busy (ATB) counter is incremented.
Page 766 Integrated Services Access Page 766 of 1814 Meridian 1 to DMS-100 WATS: • Only one INWATS route can be defined. • All INWATS calls terminate to the attendant console. • OUTWATS services are not limited to a single outgoing route. COT or DID: •...
Page 767 Integrated Services Access Page 767 of 1814 TIE: • Multiple routes can be defined. • They are routed according to the Service Identifier (SID) value. Note: In LD 16, if NSF = NO, then only one TIE route can be defined. •...
Page 768 Integrated Services Access Page 768 of 1814 Enhancements ISA has ben enhanced to provide the following: • Private, INWATS, FX, and TIE call types received from an ISA master route terminate to an individual set with or without Incoming Digit Conversion (IDC) for the DMS and AT&T interfaces.
Page 769 B-channels in LD 16 for all the bands of the WATB service. • For AT&T interfaces, only nine possible services can be used per ISA master route. With Nortel Networks DMS products, there are 512 possibilities, one for each SID value. International ISDN PRI Feature description and administration...
Page 770 Integrated Services Access Page 770 of 1814 Tables 56 and 57 illustrate the Min/Max function, assuming 23 ISA B-channels. Table 56 Example of Min/Max function for Meridian 1 to DMS Meridian 1 to DMS interface Call Type (WATR = 30, COTR = 10, NSF = YES) Public (rout 10, tkty DID, icog IAO) Private...
Page 771 Integrated Services Access Page 771 of 1814 Table 57 Example of Min/Max function for Meridian 1 to ESS Service Meridian 1 to ESS interface ACCunet (rout 10, tkty DID, icog IAO) (rout 20, tkty TIE, icog IAO) IWAT (rout 30, tkty WAT, icog ICT) WATB (rout 40, tkty WAT, sprm 9, icog OGT) WATM...
Page 772 Integrated Services Access Page 772 of 1814 • Incoming Digit Conversion (IDC) Part or all of the digits received in the DID route are converted and terminated at the existing internal DN in the Meridian 1. With this enhancement, IDC applies to the incoming WATS route over the ISDN interface.
Page 773 LD 16 – Configure ISA service routes. Basic PRI configuration must be performed before Integrated Services Access (ISA) is defined. ISA routes and trunks must be defined to access Nortel Network’s ISA functionality or AT&T’s Call-by-Call Service. LD 16 – Create an ISA master route. Prompt...
Page 774 Integrated Services Access Page 774 of 1814 LD 16 – Create an ISA master route. Prompt Response Description (NO) YES Network Service Facility (for TKTP = ISA and non-AT&T IFC; AT&T always has NSF) COTR DID/central office route number Prompted if IFC = D100, SL1, S100, or D250. Enter CO or DID route.
Page 775 Integrated Services Access Page 775 of 1814 LD 14 – Configure ISA trunks. Prompt Response Description RTMB 0-511 1-510 Route number and member number, for Options 0-127 1-510 51C-81C. Route number and member number, for Option 11C. TGAR (0)–31 Trunk Group Access Restriction Class of service options LD 16 –...
Page 776 Integrated Services Access Page 776 of 1814 LD 16 – Configure ISA service routes. Prompt Response Description ISAR Yes, (No) ISA service route - RTN Select route number of any configured ISA master route Prompted only when ISAR = YES. - FACY YES (NO) Facility for the call type (only applies if the far-end will be...
Page 777 Integrated Services Access Page 777 of 1814 To test ISA, follow steps 1 through 8. Select a PRI to be tested. Access LD 60. Use STAT command on all pertinent B-channels. Set all the Min/Max values in all service routes to 1. Make a test call on a trunk route that accesses the PRI being tested.
Page 778 Integrated Services Access Page 778 of 1814 International ISDN PRI Feature description and administration...
Page 779: Integrated Trunk Access
Feature operation ......... . Regional material statement This feature is only available in North America. Contact your system supplier or your Nortel Networks representative to verify support of this product in your area. Feature description...
Page 780 Page 780 of 1814 Integrated Trunk Access This feature removes some trunks from PRI exclusive use, to share between PRI and traditional A&B signaling. ITA supports the following configurations: • Meridian 1 to Meridian 1 • Meridian 1 to SL-100 •...
Page 781: Feature Description
Page 781 of 1814 ISDN Calling Line Identification Enhancements Contents The following are the topics in this section: Feature description ........How a CLID table is built .
Page 782: How A Clid Table Is Built
Page 782 of 1814 ISDN Calling Line Identification Enhancements The contents of these data fields were used to generate the CLID for a call. The CLID could only be built from key 0 of a set. This meant that regardless of what key was used to make a call, it was the CLID for key 0 that was sent.
Page 783 ISDN Calling Line Identification Enhancements Page 783 of 1814 North American Numbering Plan For users of a North American Numbering Plan, the Meridian 1 can now support multiple Home Central Office Codes (HNXXs), Home Numbering Plan Area (HNPA) codes, Home Location Codes (HLOCs) and Local Steering Codes (LSCs), on a DN or DN key basis.
Page 784: How Clid Entries Are Assigned To A Set
Page 784 of 1814 ISDN Calling Line Identification Enhancements Another new capability, which applies to both the North American Numbering Plan and the International Numbering Plan, pertains to how the HLCL is constructed. A new prompt, DIDN (which signifies “use DN as a DID number”) in LD 15, allows the HLCL to be built either using the digits in the HLCL plus the digits of the active key (if DIDN is set to “YES”...
Page 785: Examples Of Clid Generation
ISDN Calling Line Identification Enhancements Page 785 of 1814 Examples of CLID generation The examples that follow show CLID generation using different combinations of CLID entries for DN keys, for Private ESN UDP/CDP calls and for Public Local and Public National calls. Most of the examples use a North American Numbering Plan, since the construction of CLID entries in a CLID is the same for both a North American Numbering Plan and an International Numbering Plan.
Page 786 Page 786 of 1814 ISDN Calling Line Identification Enhancements Example 1 - Set has DID number on DN key 0 In this example, the calls are made on DN key 0, which has a DID number. Key 0 is configured against CLID table entry 0, and key 1 is configured against CLID table entry 1.
Page 787 ISDN Calling Line Identification Enhancements Page 787 of 1814 For a private ESN CDP call made from Key 0 (DN 2130) on the set, the CLID would be built as follows: — LSC from CLID entry 0 (5) plus the DN of the active key (2130). —...
Page 788 Page 788 of 1814 ISDN Calling Line Identification Enhancements HOLD Key 1 7567 Key 0 7566 553-7656.EPS For a private ESN UDP call made from Key 0 (DN 7566) on the set, the CLID would be built as follows: — HLOC from CLID entry 0 (578) plus the DN of the active key (7566).
Page 789 ISDN Calling Line Identification Enhancements Page 789 of 1814 Example 3 - Set does not have a DID number on DN key 1 (DIDN set to NO) In this example, the calls are made on DN key 1, which does not have a DID number.
Page 790 Page 790 of 1814 ISDN Calling Line Identification Enhancements HOLD Key 1 2540 Key 0 2130 553-7655.EPS For a private ESN UDP call made from Key 1 (DN 2540) on the set, the CLID would be built as follows: — HLOC from CLID entry 1 (646) plus the DN of the active key (2540).
Page 791 ISDN Calling Line Identification Enhancements Page 791 of 1814 Example 4 - Set does not have a DID number on DN key 1 (DIDN set to NO), International Numbering Plan. In this example, the calls are made on DN key 1, which does not have a DID number.
Page 792 Page 792 of 1814 ISDN Calling Line Identification Enhancements For a private ESN UDP call made from Key 1 (DN 2366) on the set, the CLID would be built as follows: — HLOC from CLID entry 1 (581) plus the DN of the active key (2366).
Page 793 ISDN Calling Line Identification Enhancements Page 793 of 1814 This means that the CLID assigned for key 1 is constructed based on a search starting from key 0. When a CLID entry is found, which has DIDN set to YES (that would be key 0), the HLCL for that key is used in the CLID for key 1.
Page 794 Page 794 of 1814 ISDN Calling Line Identification Enhancements For a private ESN UDP call made from Key 1 (DN 2540) on the set, the CLID would be built as follows: — HLOC from CLID entry 2 (655) plus the DN of the active key (2540).
Page 795 ISDN Calling Line Identification Enhancements Page 795 of 1814 Key 0 is configured against table entry 1. Since table entry 1 has DIDN set to NO, the search next takes place on key 1, which is configured against table entry 2. Since table entry 2 does not have DIDN set to YES either, the search fails to find a CLID entry which has DIDN set to YES.
Page 796 Page 796 of 1814 ISDN Calling Line Identification Enhancements — That is, the CLID that is sent would be 655 2540. For a private ESN CDP call made from Key 1 (DN 2540) on the set, the CLID would be built as follows: —...
Page 797 ISDN Calling Line Identification Enhancements Page 797 of 1814 Key 0 is configured against CLID table entry 0, and key 1 uses the CLID assigned to key 0. Table 64 Set with DN KEY prompt of “D” on key 1. CLID entry HNTN HLCL...
Page 798 Page 798 of 1814 ISDN Calling Line Identification Enhancements For a private ESN UDP call made from Key 1 (DN 2540) on the set, the CLID would be built as follows: — HLOC from CLID entry 0 (646) plus the DN for key 0 (2130) - since the Key option has been set to ‘D’, a search is done from key 0 to find a DN key.
Page 799 ISDN Calling Line Identification Enhancements Page 799 of 1814 Key 0 is configured against CLID table entry 0, and key 1 uses the CLID assigned to key 0. Table 65 Set with DN KEY prompt of “D” on key 1. CLID entry HNTN HLCL...
Page 800 Page 800 of 1814 ISDN Calling Line Identification Enhancements — Therefore, the CLID that is sent would be 578 7566. For a private ESN CDP call made from Key 1 (DN 7567) on the set, the CLID would be built as follows: —...
Page 801 ISDN Calling Line Identification Enhancements Page 801 of 1814 Key 1 is configured against CLID table entry 0, and key 0 uses the CLID assigned to key 1. Table 66 Set with DN KEY prompt of “D” on key 0. CLID entry HNTN HLCL...
Page 802: Operating Parameters
Page 802 of 1814 ISDN Calling Line Identification Enhancements — Therefore, the CLID that is sent would be 646 2540. For a private ESN CDP call made from Key 0 (DN 2130) on the set, the CLID would be built as follows: —...
Page 803: Feature Interactions
ISDN Calling Line Identification Enhancements Page 803 of 1814 There is no cross-validation of the CLID entry associated with a set against the CLID entry entered in LD 15. If a CLID entry is deleted from the CLID table and the CLID entry remains assigned to a DN key, the active DN is sent as CLID.
Page 804 Page 804 of 1814 ISDN Calling Line Identification Enhancements If an ACD agent has an active call on Key 0 and if a call transfer or conference is initiated by the ACD agent, the CLID entry associated with the ACD DN Key 0 is used as the CLID (for remote calls only.) There is no CLID entry for an analog (500/2500 type) ACD DN.
Page 805 ISDN Calling Line Identification Enhancements Page 805 of 1814 EuroISDN Continuation for UK/Spain/Belgium/SN3 The EuroISDN Continuation feature allows Home National Numbers and Home Local Numbers to be configured on a route. When an ISDN call is made from a set to a EuroISDN interface, the CLID constructed by EuroISDN, based on the outgoing route, takes precedence over the CLID constructed for the calling station set.
Page 806: Feature Packaging
Page 806 of 1814 ISDN Calling Line Identification Enhancements In general, with the enhancement of sending the DN associated with an active key to make a call to Meridian Mail, the secondary key’s DN is included in the Meridian Mail User’s definition (for either a local or remote user.) Network Ring Again The Network Ring Again feature remains operational when a user uses a multiple appearance DN on a key other than Key 0 to activate Network Ring...
Page 807 ISDN Calling Line Identification Enhancements Page 807 of 1814 LD 15 – Construct the CLID entry for a customer. Prompt Response Description REQ: Add new data, or change or delete existing data. TYPE: Networking data (if REQ = CHG only.) CUST Customer number.
Page 808 Page 808 of 1814 ISDN Calling Line Identification Enhancements - - ENTRY aaaa aaaa = CLID entry to be configured. Xaaaa Xaaaa = CLID entry to be deleted. Xaaaa Xbbbb Xaaaa Xbbbb = CLID entries to be deleted. <CR> aaaa and bbbb must be a value between 0 and (SIZE-1). The ENTRY prompt is repeated until <CR>...
Page 809 ISDN Calling Line Identification Enhancements Page 809 of 1814 It is advised that after the CLID table has been built in LD 15, a printout be generated, using LD 21, to verify the table entries defined in LD 15. LD 21 – Print the CLID table for a customer. Prompt Response Description...
Page 810 Page 810 of 1814 ISDN Calling Line Identification Enhancements LD 10 – Define the CLID entry for analog (500/2500 type) sets. Prompt Response Description REQ: Add new data, or change existing data. TYPE: 500 set. l s c u Terminal Number. For Option 11C.
Page 811 ISDN Calling Line Identification Enhancements Page 811 of 1814 Telephone function key assignments. xx = key number. xx MCN yyyy MCN = Multiple Call Non-ringing key. (0)-N/D MCR = Multiple Call Ringing key. xx MCR yyyy PVN = Private Line Non-Ringing key (0)-N/D PVR = Private Line Ringing key xx PVN yyyy...
Page 812: Feature Operation
Page 812 of 1814 ISDN Calling Line Identification Enhancements xx ACD aaaa ACD key, where: 0-N/D bbbb xx = key number. aaaa = ACD DN or Message Center DN. 0-N = CLID entry, with N = CLID SIZE-1 (SIZE defined in LD 15).
Page 813 ISDN Calling Line Identification Enhancements Page 813 of 1814 International ISDN PRI Feature description and administration...
Page 814: Isdn Calling Line Identification Enhancements
Page 814 of 1814 ISDN Calling Line Identification Enhancements 553-2901-301 Standard 9.00 January 2002...
Page 815: Isdn Pri Central Office Connectivity
Page 815 of 1814 ISDN PRI Central Office Connectivity Contents The following are the topics in this section: Regional material statement ....... . . Feature description .
Page 816 Page 816 of 1814 ISDN PRI Central Office Connectivity Feature implementation ........Task summary list .
Page 817 ISDN PRI Central Office Connectivity Page 817 of 1814 Feature operation ........SYS-12 (Norway) .
Page 818: Regional Material Statement
Networking Features and Services (553-2901-301) Regional material statement The information presented in this section does not pertain to all market regions. Contact your system supplier or your Nortel Networks representative to verify support of this product in your area. Feature description...
Page 819: Asia Pacific Isdn Pri Central Office Connectivity
ISDN PRI Central Office Connectivity Page 819 of 1814 • Japan D70 (non-Asia Pacific ISDN Connectivity) • NEAX-61 (New Zealand) (non-Asia Pacific ISDN Connectivity) • Numeris VN3 (France) • SwissNet (Switzerland) • SYS-12 (Norway) • 1TR6 (Germany) These connectivities are described in the sections which follow. Asia Pacific ISDN PRI Central Office Connectivity Description The Asia Pacific ISDN PRI Central Office Connectivity provides ISDN...
Page 820 Page 820 of 1814 ISDN PRI Central Office Connectivity • Advice of Charge, for Japan (considered a basic service) • Malicious Call Trace, for Australia • Advice of Charge (AOC) at End of Call, for Australia • Incoming Trunk Programmable CLID for analog trunks, for Australia. This feature is available for use in a private or alternative carrier network, as required in Australia.
Page 821: Operating Parameters
ISDN PRI Central Office Connectivity Page 821 of 1814 • Taiwan R1 Modified Signaling • private networks (e.g., Meridian Customer Defined Network, and QSIG) • other digital signaling systems (e.g., Digital Private Network Signaling System #1 (DPNSS1), and Digital Access Signaling System #2 (DASS2), and 1.5/2.0 Mb DTI) •...
Page 822 Page 822 of 1814 ISDN PRI Central Office Connectivity For all of the Asia Pacific interfaces, User-to-User Signalling and Multiple Subscriber Number, Calling Party Name Display, and Call Diversion are not supported. For all of the Asia Pacific interfaces, the SUSPEND, SUSPEND ACKNOWLEDGE, SUSPEND REJECT, RESUME, RESUME ACKNOWLEDGE, RESUME REJECT call rearrangement messages are not supported.
Page 823: Hardware Requirements
ISDN PRI Central Office Connectivity Page 823 of 1814 • Virtual Network Services (VNS) The Malaysia interface does not support RESTART and RESTART ACKNOWLEDGE messages for BRIT. Hardware requirements For Options 51C-81C, the following hardware is required: For Japan, Taiwan, and Hong Kong interfaces: •...
Page 824: Feature Interactions
Page 824 of 1814 ISDN PRI Central Office Connectivity For Option 11C, the following hardware is required: For Japan, Taiwan, and Hong Kong interfaces: • For Primary Rate Access, the 1.5 NTAK09AA (DTI/PRI) circuit card is required along with the NTBK51BA Downloadable D-Channel (DCHI) card.
Page 825 ISDN PRI Central Office Connectivity Page 825 of 1814 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.
Page 826 Page 826 of 1814 ISDN PRI Central Office Connectivity • a 1 - 12 digit local code for a home local number (HLCL), or a one-12 digit Listed Directory Number for a switchboard • a 1 - 7 digit Home Location Code (HLOC) •...
Page 827 ISDN PRI Central Office Connectivity Page 827 of 1814 Connected Line Identification Presentation and Restriction (COLP and COLR) are applicable only for Indonesia, India, Taiwan, and Philippines. The Connected Line Identification Restriction (COLR) supplementary service takes precedence over the COLP supplementary service. The COLP service can take precedence over COLR service if the calling user has an override category.
Page 828 Page 828 of 1814 ISDN PRI Central Office Connectivity DPNSS Gateway The Asia Pacific interface interacts with the DPNSS gateway in a manner consistent with other PSTN interfaces. The Information Elements (IEs) supported on the Asia Pacific interface, which have equivalents in DPNSS interwork are translated on an IE by IE basis.
Page 829: Feature Packaging
ISDN PRI Central Office Connectivity Page 829 of 1814 Trunk Optimization Trunk Optimization is not supported across the Asia Pacific interface, but interworks transparently. In other words, trunk optimization will not be observed at the Asia Pacific ISDN. The call will appear to be static, not undergoing any modifications.
Page 830: Feature Implementation
Page 830 of 1814 ISDN PRI Central Office Connectivity • Meridian 1 Extended Peripheral Equipment (XPE) package 203 • Multi-Purpose Serial Data Link (MSDL) package 222, which requires the Integrated Services Digital Network (ISDN) package 145 • New Format CDR (FCDR) package 234 For Basic Rate Interface trunk access the following packages are required instead of the PRI-related packages: •...
Page 831 ISDN PRI Central Office Connectivity Page 831 of 1814 LD 17 – Configure nB+D for Hong Kong, Japan, New Zealand, and Malaysia. LD 17 – Configure the Bearer Capability for the Asia Pacific connectivity D-Channel. LD 16 – Configure Asia Pacific ISDN PRI Route Data Block. LD 14 –...
Page 832 Page 832 of 1814 ISDN PRI Central Office Connectivity - ENTRY aaaa aaaa = CLID entry to be configured. Xaaaa Xaaaa = CLID entry to be deleted. Xaaaa Xbbbb Xaaaa Xbbbb = CLID entries to be deleted. aaaa and bbbb must be a value between 0 and (SIZE-1). The ENTRY prompt is repeated until <CR>...
Page 833 ISDN PRI Central Office Connectivity Page 833 of 1814 LD 17 – Configure the Asia Pacific D-channel. Prompt Response Description Change existing data. TYPE Configuration data block. - ADAN NEW DCH xx Add a D-channel on logical port 0-63 (51C-81C). NEW DCH xx Add a D-channel on logical port 0-15 (Option 11C).
Page 834 Page 834 of 1814 ISDN PRI Central Office Connectivity - - CNTY Country associated with the APAC interface. AUST Australia. CHNA China. HKNG Hong Kong. INDI India. INDO Indonesia. JAPN Japan. MSIA Malaysia. PHLP Philippines. SING Singapore. TAIW Taiwan. TCNZ New Zealand.
Page 835 ISDN PRI Central Office Connectivity Page 835 of 1814 - RCAP Remote capabilities, to configure the Connected Line ID Presentation supplementary service. (XCOL) To remove COLP. COLP CLID Presentation supported. This prompt appears if CNTY = Indonesia, India, Taiwan, and the Philippines. - OVLR Allow Overlap Receiving.
Page 836 Page 836 of 1814 ISDN PRI Central Office Connectivity - - INC_T306 0-(2)-240 Variable timer for received DISCONNECT message on incoming calls allowing in-band tone to be heard when the network sends in-band tone. T306 is the duration of the network timer in seconds. The network will stop sending after T306 times out, so the maximum time will be T306.
Page 837 ISDN PRI Central Office Connectivity Page 837 of 1814 LD 17 – Configure a Back-up D-Channel for Hong Kong. Prompt Response Description Change existing data. TYPE ADAN Action device and number. - ADAN NEW BDCH xx Add a Back-up D-Channel on logical port 0-63, for Options 51C-81C NEW BDCH xx Add a Back-up D-Channel D-Channel on logical port...
Page 838 Page 838 of 1814 ISDN PRI Central Office Connectivity Port number of the NTBK51AA, if the NTBK51AA is used for D-Channel handling on large systems (Options 51C, 61C, 81C). Port 0 of the NTBK51AA can only be defined to work with Loop 0 of the NT5D97AA DDP2 card, and Port 1 of the NTBK51AA can only be defined to work with Loop 1 of the NT5D97AA.
Page 839 ISDN PRI Central Office Connectivity Page 839 of 1814 PRI/PRI2 loop number for D-channel (Option 11C). LD 17 – Configure nB+D for Hong Kong, Japan, New Zealand, and Malaysia. Note: The International nB+D (INBD) package 255 must be enabled to configure nB+D.
Page 840 Page 840 of 1814 ISDN PRI Central Office Connectivity Port number of the NTBK51AA, if the NTBK51AA is used for D-Channel handling on large systems (Options 51C-81C). Port 0 of the NTBK51AA can only be defined to work with Loop 0 of the NT5D97AA DDP2 card, and Port 1 of the NTBK51AA can only be defined to work with Loop 1 of the NT5D97AA.
Page 841 ISDN PRI Central Office Connectivity Page 841 of 1814 - PRI LOOP ID Secondary PRI loop number and interface identifier 0-159 (0)-15 (Options 51C-81C). Prompted if INBD package 255 is enabled. The values entered must be different than those entered for the loop number and interface identifier at the DCHL prompt.
Page 842 Page 842 of 1814 ISDN PRI Central Office Connectivity LD 16 – Configure Asia Pacific ISDN PRI Route Data Block. Prompt Response Description Add new data. Change existing data. TYPE Route Data Block. CUST Customer number, as defined in LD 15. ROUT 0-511 Route number, for Options 51C-81C.
Page 843 ISDN PRI Central Office Connectivity Page 843 of 1814 - - CNTY Country associated with the APAC interface. AUST Australia. CHNA China. HKNG Hong Kong. INDI India. INDO Indonesia. JAPN Japan. MSIA Malaysia. PHLP Philippines. SING Singapore. TAIW Taiwan. TCNZ New Zealand.
Page 844 Page 844 of 1814 ISDN PRI Central Office Connectivity ICOG Incoming and/or Outgoing trunk. The trunk is Incoming and Outgoing. The trunk is Incoming only. The trunk is Outgoing only. ACOD x...x The Access Code for the trunk route. The ACOD must not conflict with the existing numbering plan.
Page 845 ISDN PRI Central Office Connectivity Page 845 of 1814 LD 14 – Configure Asia Pacific ISDN PRI trunks. Prompt Response Description Add new data. Change existing data. TYPE TIE trunk data block. Central Office Trunk data block. Direct Inward Dialing trunk data block. Note: Must match TKTP defined in LD 16.
Page 846: Feature Operation
Page 846 of 1814 ISDN PRI Central Office Connectivity LD 73 – Define the frame format and grade of service timers for a PRI/PRI2 loop. Prompt Response Description Change existing data. TYPE PRI loop. PRI2 PRI2 loop. FEAT LPTI Set the timers for PRI2 loop. LOOP PRI/PRI2 loop number.
Page 847: Operating Parameters
ISDN PRI Central Office Connectivity Page 847 of 1814 This feature uses the existing EuroISDN software packages to provide the basic ISDN capabilities and supplementary services listed below (EURO is configured as the interface in the overlay programs when configuring PRI2 and BRI).
Page 848 Page 848 of 1814 ISDN PRI Central Office Connectivity Overlap Receiving is not supported. Basic Alternate Route Selection (BARS) is not supported. Network Alternate Route Selection (NARS) is. In a Meridian Customer Defined Network (MCDN), receiving Calling Party Name Display (CPND) and sending a CPND are not supported MCDN Call Redirection (Call Forward, Call Forward No Answer, Hunt) is not supported.
Page 849: Feature Interactions
ISDN PRI Central Office Connectivity Page 849 of 1814 Feature interactions Calling Line Identification Enhancements Prior to the CLID Enhancements feature, the Customer Data Block (Overlay15) contained the prompts PFX1 and PFX2 (for Prefix 1 and Prefix 2) that were used to construct the CLID. The combination of PFX1, PFX2 and the originating DN were used to construct a correct number for the called party to dial in order to reach the calling party.
Page 850 Page 850 of 1814 ISDN PRI Central Office Connectivity 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.
Page 851: Feature Packaging
ISDN PRI Central Office Connectivity Page 851 of 1814 Connected Line Identification Presentation and Restriction (COLP and COLR) The Connected Line Identification Restriction (COLR) supplementary service takes precedence over the COLP supplementary service. The COLP service can take precedence over COLR service if the calling user has an override category.
Page 852: Feature Implementation
Page 852 of 1814 ISDN PRI Central Office Connectivity For the Advice of Charge capability: • Controlled Class of Service (CCOS) package 81 • Background Terminal (BGD) package 99 • Periodic Pulse Metering/Message Registration (MR) package 101 • International Supplementary Features (SUPP) package 131 For the Malicious Call Trace capability: •...
Page 853 ISDN PRI Central Office Connectivity Page 853 of 1814 LD 11 – Assign meters to Meridian proprietary sets. LD 16 – Allow Advice of Charge on the route configured for Australia ETSI. LD 17 – Configure a PRI2 loop for the ETSI Australian ISDN connectivity. Prompt Response Description...
Page 854 Page 854 of 1814 ISDN PRI Central Office Connectivity - PORT Port number on the MSDL card (Options 81C). For Option 11C. - DES aaa...a Designator. DES is used to identify the link and can be up to 16 alphanumeric characters: 0-9, and upper case A-Z. Characters “*”...
Page 855 ISDN PRI Central Office Connectivity Page 855 of 1814 - - INC_T306 0-(2)-30 Variable timer, in seconds, for received DISCONNECT message on incoming calls allowing in-band tone to be heard. The network will stop sending after this timer times out. The value is stored in two-second increments, which are rounded up.
Page 856 Page 856 of 1814 ISDN PRI Central Office Connectivity ISDN Integrated Services Digital Network. - MODE ISDN PRI route. - IFC EURO EuroISDN interface. - - CNTY EAUS Australia ETSI. MCTS Enable MCT signaling. - MCTM (0)-30 Malicious Call Trace disconnect delay timer (this timer overrides the T306 timer for calls originating or terminating on sets with MCT Class of Service).
Page 857 ISDN PRI Central Office Connectivity Page 857 of 1814 LD 14 – Configure the Australia ETSI ISDN PRI2 trunks. Prompt Response Description Add new data. Change existing data. TYPE TIE trunk data block. Central Office Trunk data block. Direct Inward Dialing trunk data block. Note: Must match TKTP defined in LD 16.
Page 858 Page 858 of 1814 ISDN PRI Central Office Connectivity LD 17 – Configure Advice of Charge for Australia ETSI. Note: The MR/PPM package 101 must be equipped on the Meridian 1. Prompt Response Description CHG = Change existing data. TYPE PARM Change system parameters, OCAC...
Page 859 ISDN PRI Central Office Connectivity Page 859 of 1814 TN address l s c u Loop, shelf, card, and unit (Options 51C-81C). Card and unit (Option 11C). LD 11 – Assign meters to Meridian proprietary sets. Prompt Response Description REQ: Add new data.
Page 860 Page 860 of 1814 ISDN PRI Central Office Connectivity DTRK Digital trunk route. - DGTP PRI2 2.0 Mb PRI digital trunk type. ISDN Integrated Services Digital Network. - MODE ISDN PRI route. - IFC EURO EuroISDN interface. - - CNTY EAUS Australia ETSI.
Page 861: Feature Operation
ISDN PRI Central Office Connectivity Page 861 of 1814 RUCF Route unit conversion factor. 0 = No conversion is required. DSPT 0-(10)-60 Charge display timer. Feature operation No specific operating procedures are required to use this feature. AXE-10 (Australia), non-Asia Pacific connectivity Description This feature allows ISDN PRI connectivity between the Meridian 1 and the AXE-10 for Australia, using switched-circuit mode connections.
Page 862: Feature Interactions
Page 862 of 1814 ISDN PRI Central Office Connectivity The supplementary service control messages not relating to a call are not supported. The Meridian 1 does not send the High Layer Compatibility Information Element in the SETUP message to the AXE-10, nor does it send the Restart Request and Restart Global Call States.
Page 863: Feature Operation
ISDN PRI Central Office Connectivity Page 863 of 1814 LD 17 – Define system support for the AXE-10 Australia connectivity. Prompt Response Description Change existing data block. TYPE Configuration record. - ADAN CHG DCH x Change a D-channel on logical port 0-63 (all other machine types).
Page 864: Axe-10 (Sweden), Non-Asia Pacific Connectivity
Page 864 of 1814 ISDN PRI Central Office Connectivity AXE-10 (Sweden), non-Asia Pacific connectivity Description This feature allows ISDN PRI connectivity between the Meridian 1 and the Ericsson AXE-10 for Sweden, using switched-circuit mode connections. The design in based on the international 30B + D PRI configuration. Basic ISDN PRI connectivity between the Meridian 1 and the AXE-10 will support: •...
Page 865: Feature Interactions
ISDN PRI Central Office Connectivity Page 865 of 1814 Feature interactions There are no feature interactions specified for this feature. Feature packaging To support all of the call services, the following packages must be equipped: • Digit Display (DDSP) package 19; •...
Page 866: Feature Operation
Page 866 of 1814 ISDN PRI Central Office Connectivity - IFC AXES Ericsson AXE-10 for Sweden. - CNEG (1) 2 The required channel negotiation option, either exclusive (the default) or preferred. LD 16 – Configure the routes for the AXE-10 Sweden connectivity. Prompt Response Description...
Page 867: New Zealand Supplementary Isdn Services
ISDN PRI Central Office Connectivity Page 867 of 1814 • Channel Negotiation • nB+D, up to 120 B-channels/four interfaces • Public Switched Telephone Network (PSTN) three-party conferencing • Flexible Numbering Plan, and • Malicious Call Trace. Note that Electronic Switched Network (ESN) cannot be supported across the interface for private network applications.
Page 868 Page 868 of 1814 ISDN PRI Central Office Connectivity Figure 71 PBX and PSTN supported conference Conference Conference Card Card Single COT COTs PSTN Conference Card This operation is a stand-alone feature as the network wide trunk hook flash is not supported. Note also that from the New Zealand NEAX-61 side, MCT and PSTN conferencing are mutually exclusive features.
Page 869: Operating Parameters
ISDN PRI Central Office Connectivity Page 869 of 1814 Operating parameters The following hardware is used to implement the interface: • For Options 51C through 81C and SL-1 systems, the layer one function is provided by the circuit pack NT8D72 (2.0 Mb PRI card for non Option 11 systems).
Page 870 Page 870 of 1814 ISDN PRI Central Office Connectivity A set on the Meridian 1 can Hunt or CFNA to an external number over an NEAX-61 Primary Rate Interface (this operates exactly the same as over any other Central Office trunk). It is possible to transfer or conference a call on the Meridian 1 to an external number over an NEAX-61 Primary Rate Interface (this operates exactly the same as over any Central Office trunk).
Page 871 ISDN PRI Central Office Connectivity Page 871 of 1814 Calling Party Name Display This feature is offered within the MCDN. Names can be assigned to various items, including route access codes. An incoming call across this route will have the name stored against the route displayed. This will continue, however, CPND received from the NEAX-61 is not currently supported, and sending CPND to the NEAX-61 is also not supported at this time.
Page 872 Page 872 of 1814 ISDN PRI Central Office Connectivity Basic Automatic Route Selection (BARS) This feature has no interactions with the NEAX-61 with the exceptions of: the NPA and NXX cannot be used on this interface, as the public network cannot accept them;...
Page 873: Feature Packaging
ISDN PRI Central Office Connectivity Page 873 of 1814 Virtual Network Services (VNS) VNS uses a dedicated, MCDN level of service DCH to control a number of temporary B-channels, seized and used on demand. The ISDN signaling requests a connection (SETUP), and a returned FACILITY has a DN that is to be recognized as a VNS virtual DN on the terminating switch.
Page 874: Feature Implementation
Page 874 of 1814 ISDN PRI Central Office Connectivity If the user subscribes to the following services on the PSTN, the ISDN International Supplementary (ISDNS) package 161 is required. The packages as listed below for each feature are also required: •...
Page 875 ISDN PRI Central Office Connectivity Page 875 of 1814 - GRP Network group number for the Option 81C. CDNO 1-10 Card number on the Option 11. - DES aaaaaa Alphanumeric designator. - DPNS (NO) YES Digital Private Network Signaling. - USR D-channel mode.This D-channel is used for Primary Rate only.
Page 876 Page 876 of 1814 ISDN PRI Central Office Connectivity - - INC_T306 0,(2),...,T306 Variable timer for received DISCONNECT message on incoming calls, allowing in-band tone to be heard when (T306 is the sent by the network. The network will stop sending duration of the tone after T306 expires, so the maximum time will be T306 Network...
Page 877: Feature Operation
ISDN PRI Central Office Connectivity Page 877 of 1814 CTYP UKWN, INTL, Only these call types are supported for TCNZ interface TIE NPA, NXX routes. (YES) NO Outpulsed digits in CDR. CDRX YES NO X records produced on call transfer. INC 1-32 Number of printed digits;...
Page 878: Operating Parameters
Page 878 of 1814 ISDN PRI Central Office Connectivity • COT, DID, DOD, TIE trunks call types • 64 kbps clear bearer capability • Channel Negotiation • Call Restriction • Flexible Numbering Plan • Advice of Charge at end of call, and during call Operating parameters The only connection that is supported is the switched circuit mode connection.
Page 879: Feature Interactions
ISDN PRI Central Office Connectivity Page 879 of 1814 An RAI signal must be sent if an ERR condition of 10 lasts more than four to five seconds. The RAI transmission must cease after an ERR condition of 10 lasts for more than four to five seconds.
Page 880 Page 880 of 1814 ISDN PRI Central Office Connectivity LD 17 – Define system support for NUMERIS. Prompt Response Description Change existing data block. TYPE Configuration record. - ADAN CHG DCH x Change a D-channel on logical port 0-63 (all other machine types).
Page 881: Feature Operation
ISDN PRI Central Office Connectivity Page 881 of 1814 LD 73 – Define the alarm handler in the firmware, disable or enable the grade of service processing in the software, and define the number of seconds before the firmware sends an ERR message.
Page 882: Operating Parameters
Page 882 of 1814 ISDN PRI Central Office Connectivity • COT, DID, DOD, TIE call types • 64 kbps clear bearer capability • Channel Negotiation • Flexible Numbering Plan • Overlap Sending • Advice of Charge during call Operating parameters The only connection that is supported is the switched circuit mode connection.
Page 883: Feature Packaging
ISDN PRI Central Office Connectivity Page 883 of 1814 Call Detail Recording (CDR) For calls made over an ISDN PRI to SwissNet interface equipped with the Advice of Charge at End of Call feature, all Start and Transfer records will show “OVF99”...
Page 884: Feature Operation
Page 884 of 1814 ISDN PRI Central Office Connectivity LD 17 – Define the ISDN PRI to SwissNet connectivity. Prompt Response Description Change. TYPE Configuration Record. - ADAN CHG DCH x Change a D-channel on logical port 0-63 (all other machine types).
Page 885: Norway)
ISDN PRI Central Office Connectivity Page 885 of 1814 SYS-12 (Norway) Description This feature allows ISDN PRI connectivity between the Meridian 1 and the Norwegian SYS-12, using switched-circuit mode connections. The ISDN PRI connectivity between the Meridian 1 and the SYS-12 supports: •...
Page 886: Feature Implementation
Page 886 of 1814 ISDN PRI Central Office Connectivity Feature implementation Task summary list The following is a summary of the tasks in this section: LD 17 – Define the ISDN PRI to SYS-12 connectivity. LD 16 – Define the ISDN PRI to SYS-12 connectivity. The following procedures assume that a D-channel has been configured.
Page 887: Feature Operation
ISDN PRI Central Office Connectivity Page 887 of 1814 Feature operation There are no operating procedures specified for this feature. 1TR6 (Germany) Description This feature will allow the interconnection of the Meridian 1 with the 1TR6 protocol. Basic connectivity between the Meridian 1 and the 1TR6 DCH supports: •...
Page 888: Feature Implementation
Page 888 of 1814 ISDN PRI Central Office Connectivity • 2.0 Mb Primary Rate Access (PRI2) package 154; • ISDN Supplementary Features (ISDNS) package 161; and • International Primary Rate Access (IPRA) package 202. Feature implementation Task summary list The following is a summary of the tasks in this section: LD 17 –...
Page 889: Feature Operation
ISDN PRI Central Office Connectivity Page 889 of 1814 LD 16 – Define the ISDN PRI to 1TR6 connectivity. Prompt Response Description New, or change. TYPE Route Data Block. CUST Customer number. ROUT Route number. 1TR6 Interface type for 1TR6 connectivity. Feature operation There are no operating procedures specified for this feature.
Page 890 Page 890 of 1814 ISDN PRI Central Office Connectivity • Connected Line Identification Restriction are provided for the above countries where Application Documents are available. • Channel negotiation • Advice of Charge (at call set-up, during call, and end of call) is supported in some countries •...
Page 891 ISDN PRI Central Office Connectivity Page 891 of 1814 • The addition and display of national or international prefix in front of the received Calling/Connected Line Identification on incoming/outgoing EuroISDN calls; • Flexible national and local prefixes in addition to the Calling/Connected Line Identification on incoming/outgoing calls based on the route configuration;...
Page 892 Page 892 of 1814 ISDN PRI Central Office Connectivity In addition to providing all of the functionalities provided by the original introduction of EuroISDN and the EuroISDN Continuation, EuroISDN Continuation Phase III introduces the following new functionalities for all EuroISDN interfaces: •...
Page 893: Operating Parameters
ISDN PRI Central Office Connectivity Page 893 of 1814 With the EuroISDN ETS 300 403 Compliance Update feature, all of the functionalities provided by the previous offerings of the EuroISDN features are supported, along with the following enhancements: • Support for signalling procedures for bearer capability and High Layer Capability selections by, providing repeatable Bearer capability, High layer compatibility Information Elements (IEs) in the SETUP message.
Page 894 Page 894 of 1814 ISDN PRI Central Office Connectivity The Call Back Queuing and Off-hook Queuing feature and the Flexible Hotline feature are not supported with Overlap Signaling. End-to-End Signaling is supported on all outgoing EuroISDN routes as soon as the CALL PROCEEDING message with a Progress Indicator is received. Special dial tones after dialed numbers are not supported for incoming calls.
Page 895 ISDN PRI Central Office Connectivity Page 895 of 1814 • Transit network selection is not supported. This IE is normally used by the user to identify a selected transit network in the SET-UP message. As no European country specifies the coding to use this IE, this service is not supported by the Meridian 1.
Page 896 Page 896 of 1814 ISDN PRI Central Office Connectivity — generic status request procedure. — support of the Extended facility information element. • DN address translation requires the association with a customer number. For an ETSI basic call establishment, the customer number association is found through the B-Channel identified in the channel ID IE.
Page 897: Feature Interactions
ISDN PRI Central Office Connectivity Page 897 of 1814 Operating parameters pertaining to ETS 300 403: • The operating parameters pertaining to ETS 300 102 are applicable to ETS 300 403, except for the user-to-user compatibility checking, which is partially supported in some cases. For instance, as in the case of the EuroISDN 7 kHz/Videotelephony teleservices.
Page 898 Page 898 of 1814 ISDN PRI Central Office Connectivity Incoming Trunk Programmable CLID The Optional Sending of Last Forwarding DN as CLID functionality interacts with the Incoming Trunk Programmable CLID feature. This feature provides the capability of assigning a billing number to incoming trunks. If the redirection does not occur at the gateway node, the incoming redirecting number information is used as the outgoing CLID on the standard ISDN connectivity DID or CO trunk, even though the Incoming Trunk...
Page 899 ISDN PRI Central Office Connectivity Page 899 of 1814 For the PRDL feature, when applied to EuroISDN trunks, the EOD timer used as the PRDL timer must be at least two seconds shorter than the ISDN interdigit timer (T302 = 15 seconds) used for the VNR and Intercept treatments.
Page 900 Page 900 of 1814 ISDN PRI Central Office Connectivity The destination non-ISDN trunk may be busy instead of ringing; therefore, it is not effective to provide an ALERTING message, since the PSTN provides the caller with ringback. However, the PSTN will be running a T310 timer. Expiry of this timer causes call clearing, and a message must be provided.
Page 901 ISDN PRI Central Office Connectivity Page 901 of 1814 When interworking with an analog trunk without answer supervised signaling, the Meridian 1 should be configured to send a CONNECT message rather than an ALERT message. An ALERT or CONNECT message stops the receipt of digits, which implies that all digits have been received.
Page 902: Feature Packaging
Page 902 of 1814 ISDN PRI Central Office Connectivity The transfer of an unanswered EuroISDN call interacts with the CDR feature. When the originating party completes the call transfer after the transferred-to set answers, a CDR Start (S) is generated when the transferred-to set answers. When one side releases the call, a CDR End (E) ticket is generated.
Page 903: Feature Implementation
ISDN PRI Central Office Connectivity Page 903 of 1814 • Integrated Services Digital Network Basic Rate Interface Trunk Access (BRIT) package 233 For the Uniform Dialing Plan (UDP), the following packages are also required: • Basic Routing (BRTE) package 14 •...
Page 904 Page 904 of 1814 ISDN PRI Central Office Connectivity LD 16 – Configure new DID routes (the same responses to the IFC and CNTY prompts, as were used in LD 17, must be entered). LD 17 – Configure the Numbering Plan Identification (NPI) and Type of Number (TON) fields to be included in the CDR tickets, in addition to the CLID, for EuroISDN calls (this is automatically done by entering YES in response to the CLID prompt).
Page 905 ISDN PRI Central Office Connectivity Page 905 of 1814 OCLI (NO) NO = No manipulation is done on outgoing CLID for calls forwarded over EuroISDN links. EXT = The last forwarding DN is sent as CLID information for incoming calls over a standard ISDN (EuroISDN, APAC, NI-2) DID or CO link to a gateway Meridian 1 node, and redirected back over the standard ISDN (EuroISDN, APAC, NI-2) DID or CO link.
Page 906 Page 906 of 1814 ISDN PRI Central Office Connectivity - IFC DCH interface type. EURO EURO = EuroISDN E403 E403 = EuroISDN Interface conforming to the ETS 300 403, or the extended ETS 300 102 version for country-specific interfaces. Refer to the Note on page 892 - - CNTY Enter country pertaining to EuroISDN interface.
Page 907 ISDN PRI Central Office Connectivity Page 907 of 1814 - - CNEG (1) 2 Channel Negotiation option. (1) = Channel is indicated and no alternative is acceptable. This is the default value for all EuroISDN Interfaces except FRA. 2 = Channel is indicated and any alternative is acceptable.
Page 908 Page 908 of 1814 ISDN PRI Central Office Connectivity - IFC DCH interface type. EURO EURO = EuroISDN E403 E403 = EuroISDN Interface conforming to the ETS 300 403, or the extended ETS 300 102 version for country-specific interfaces. Refer to the Note on page 892 - - CNTY Enter country pertaining to EuroISDN interface.
Page 909 ISDN PRI Central Office Connectivity Page 909 of 1814 - CLID OPT0 Prefix = 0, for North American dialing plan. This is the default value for ESIG and ISIG interfaces. OPT1 Prefix = 1, for international PFXs in CLID, any numbering type supported.
Page 910 Page 910 of 1814 ISDN PRI Central Office Connectivity - CPFXS (YES) NO Customer-defined Prefixes option. This prompt is added as one of the sub-prompts of ISDN = YES. It is added at the end of the ISDN sub-prompts. If CPFXS = YES, when constructing the Calling or Connected Line Identification, the prefixes are retrieved from the Customer Data Block via the PFX1 and PFX2 prompts in LD 15, as is currently done.
Page 911: Feature Operation
ISDN PRI Central Office Connectivity Page 911 of 1814 LD 17 – Configure the Numbering Plan Identification (NPI) and Type of Number (TON) fields to be included in the CDR tickets, in addition to the CLID, for EuroISDN calls (this is automatically done by entering YES in response to the CLID prompt).
Page 912: Operating Parameters
Page 912 of 1814 ISDN PRI Central Office Connectivity • nB+D, up to 120 B-channels/four interfaces • Public Switched Telephone Network (PSTN) three-party conferencing • Flexible Numbering Plan • Malicious Call Trace Operating parameters For the ISDN layer 1 interface, the circuit pack QPC720 (Digital Trunk Interface) is used for the Meridian 1 to D70 connectivity.
Page 913: Feature Implementation
ISDN PRI Central Office Connectivity Page 913 of 1814 • Multi-purpose Serial Data Link (MSDL) package 222 for use of the MSDL card in place of the DCH card. Feature implementation Task summary list The following is a summary of the tasks in this section: LD 17 –...
Page 914: Feature Operation
Page 914 of 1814 ISDN PRI Central Office Connectivity Interface type for Japan D70 connectivity. Feature operation There are no operating procedures specified for this feature. 553-2901-301 Standard 9.00 January 2002...
Page 915: Isdn Qsig
Feature operation ......... . Regional material statement ISDN BRI trunking is not available in North America. Contact your system supplier or your Nortel Networks representative to verify support of this product in your area. International ISDN PRI Feature description and administration...
Page 916 Page 916 of 1814 ISDN QSIG Feature description The European Computer Manufacturer’s Association (ECMA) has defined an ISDN protocol that specifies the Layer 3 signaling requirement for support of circuit switched call control at the “Q” reference point between Private Telecommunications Network Exchanges (PTNXs) connected within a Private Telecommunications Network (PTN).
Page 917 ISDN QSIG Page 917 of 1814 QSIG development underscores Nortel Network's commitment to global standards. QSIG will provide a greater interworking of voice, image, video, and data services in multi-vendor environments. Users will also be able to combine ISDN PRI with ISDN BRI to deliver enhanced services via end-to-end ISDN networks.
Page 918 Page 918 of 1814 ISDN QSIG Trunk Route Optimization Trunk Route Optimization (TRO) is supported within the Meridian 1 network only. When a redirecting node sends a message to the originating node and the TRO request is accepted, the new call can go through the QSIG interface as a normal basic call.
Page 919 ISDN QSIG Page 919 of 1814 A QSIG link can be used as a B-channel for the VNS feature over a private network. All VNS services are then supported as normal; the QSIG link is only used as a speech bearer. Feature packaging A new QSIG Interface (QSIG) package 263 must be provisioned to activate this feature.
Page 920 Page 920 of 1814 ISDN QSIG LD 17 – Assign the configuration record. Prompt Response Description Change. TYPE Configuration Record. ISIG Interface ID for ISO QSIG. ESIG Interface ID for ETSI QSIG. TIMR (NO) YES NO = skip timer prompt. YES = change timer value.
Page 921 ISDN QSIG Page 921 of 1814 Data relating to the software downloading for the MSDL card will remain in the overlay. Hence, this overlay must be modified to accept the parameters required for downloading the PRI application data files. The parameters basically specify conditional or forced downloading. Prompt Response Description...
Page 922 Page 922 of 1814 ISDN QSIG 553-2901-301 Standard 9.00 January 2002...
Page 923: Isdn Qsig Alternate Routing
Feature operation ......... . Regional material statement The information presented in this section does not pertain to all market regions. Contact your system supplier or your Nortel Networks representative to verify support of this product in your area. Feature description The ISDN QSIG Alternate Routing feature provides a solution to calls encountering congestion due to high traffic situations within a QSIG network.
Page 924 Page 924 of 1814 ISDN QSIG Alternate Routing This feature uses the routing capability of Network Alternate Route Selection (NARS) to re-route a congested call. For each QSIG call translated at a Meridian 1 node, NARS selects one route from up to 512 routes to complete the call.
Page 925: Transit Node Operation
ISDN QSIG Alternate Routing Page 925 of 1814 Transit node operation Consider the following calling scenario for a transit node operation (refer to Figure 72). An attempt is being made to establish a call over a QSIG link, from originating node A to terminating node C, via transit node B. All the trunks pertaining to the call attempt at node C are busy.
Page 926 Page 926 of 1814 ISDN QSIG Alternate Routing Figure 72 Transit node operation Node A Node B Node C QSIG QSIG call clearing message call is routed to next call is established using available alternate route alternate route Node D Private Exchange C e n t r a l...
Page 927: Originating Node Operation
ISDN QSIG Alternate Routing Page 927 of 1814 If SBOC = NRR, no alternate routing is performed. The call receives network blocking treatment, depending on the congestion cause value and the type of treatment defined by prompt NBLK in LD 15. Originating node operation Consider the following calling scenario for an originating node operation (refer to Figure 73).
Page 928 Page 928 of 1814 ISDN QSIG Alternate Routing Figure 73 Originating node operation Node A Node B QSIG call clearing message call is routed to next call is established using Node C available alternate route alternate route Private Exchange C e n t r a l O f f i c e 553_8381 An attempt to find a free alternate is made until all of the alternate routes, as...
Page 929: Operating Parameters
ISDN QSIG Alternate Routing Page 929 of 1814 Operating parameters There are two forms of QSIG Call Transfer - QSIG Call Transfer by the “rerouting” method, and QSIG Call Transfer by the “join” method. QSIG Alternate Routing and the QSIG Call Transfer by the “re-routing” method are mutually exclusive.
Page 930: Feature Interactions
Page 930 of 1814 ISDN QSIG Alternate Routing Feature interactions Drop Back Busy and Off-Hook Queuing QSIG Alternate Routing takes precedence over ISDN Drop Back Busy, if both are configured on an MCDN-to-QSIG gateway node. Intercept treatment If QSIG Alternate Routing fails to find an alternate route for a call encountering congestion at a transit node, intercept treatment is not applied at the transit node.
Page 931: Feature Packaging
ISDN QSIG Alternate Routing Page 931 of 1814 Feature packaging The following packages are required for the QSIG Alternate Routing feature: • Basic Routing (BRTE) package 14 • Network Class of Service (NCOS) package 32 One of the following: • Basic Alternate Route Selection (BARS) package 57 •...
Page 932 Page 932 of 1814 ISDN QSIG Alternate Routing ROUT 0 - 511 Route Number for Options 51C-81C. 0-127 Route Number for Option 11C. SBOC Step Back On Congestion option. (NRR) No re-routing. Re-route if congestion is encountered at the originating node;...
Page 933: Feature Operation
ISDN QSIG Alternate Routing Page 933 of 1814 IDBB ISDN Drop Back Busy options. (DBD) Deny Drop Back Busy. Allow Drop Back Busy on, if all route sets are busy. Allow Drop Back Busy, if all Initial route sets are busy. Feature operation No operating procedures are required to use this feature.
Page 934 Page 934 of 1814 ISDN QSIG Alternate Routing 553-2901-301 Standard 9.00 January 2002...
Page 935: Isdn Qsig Basic Call
Feature operation ......... . Regional material statement ISDN BRI trunking is not available in North America. Contact your system supplier or your Nortel Networks representative to verify support of this product in your area. Feature description...
Page 936: Standard 9.00 January
Page 936 of 1814 ISDN QSIG Basic Call This protocol has been adopted by the European Telecommunications Standards Institute (ETSI) and the International Standards Institute (ISO). Most of the major European PTNX manufacturers will be supporting ISDN connectivity based on this standard. This applies to both ISDN PRI and ISDN BRIT (trunk application.) QSIG is oriented toward signaling and services that occur between two “peer-to-peer”...
Page 937 ISDN QSIG Basic Call Page 937 of 1814 Meridian 1 accepts up to three Progress Information Elements (IE) in one message on the QSIG interface. The maximum length of an ISDN message is limited to 260 bytes. Only circuit mode connection is supported. nB+D is not supported for QSIG.
Page 938 Page 938 of 1814 ISDN QSIG Basic Call Network Calling Party Name Display Network Calling Party Name Display (NCPND) is supported within the Meridian Customer Defined Network only. When QSIG is involved in the call setup, the existing NCPND operation on unsupported interfaces applies on QSIG.
Page 939 ISDN QSIG Basic Call Page 939 of 1814 • 2.0 Mb Primary Rate Access (PRI2) package 154; • Overlap Signaling (OVLP) package 184; • International Primary Rate Access (IPRA) package 202; • ISDN QSIG Basic Call (QSIG) is package 263. Feature implementation Task summary list The following is a summary of the tasks in this section:...
Page 940 Page 940 of 1814 ISDN QSIG Basic Call LD 16 – Define the Route Data Block. Prompt Response Description New, or change. TYPE Route Data Block. DTRK Digital Trunk Route. DGTP 1.5 Mb PRI. PRI2 2.0 Mb PRI. Basic Rate Interface. ISIG New DCH interface identification as entered in LD 17.
Page 941: Contents
Feature operation ......... . Regional material statement ISDN BRI trunking is not available in North America. Contact your system supplier or your Nortel Networks representative to verify support of this product in your area. Feature description Two European QSIG interfaces are available.
Page 942: Isdn Qsig-Bc And Qsig-Gf Compliance Update
Page 942 of 1814 ISDN QSIG-BC and QSIG-GF Compliance Update The ISDN QSIG-BC and QSIG-GF Compliance Update feature is compliant with the following European standards documents for QSIG: • ETS 300-172, fourth edition (1997) • ETS 300-239, second edition Initially, support for the ISDN QSIG interface and the basic call capability was introduced.
Page 943: Qsig Gf Compliance Update
ISDN QSIG-BC and QSIG-GF Compliance Update Page 943 of 1814 Transit counter The transit counter IE is defined as a codeset 4 IE instead of codeset 5. The transit counter functionality is considered to be a supplementary service. Restart procedure When a RESTART message with a restart IE coded “Channel indicated”...
Page 944 Page 944 of 1814 ISDN QSIG-BC and QSIG-GF Compliance Update Figure 74 Facility IE layout Octet Facility Information Element Identifier Length of Information Element Contents spare Protocol Profile NetworkFacilityExtension NetworkProtocolProfile InterpretationAPDU Service APDU 4... Protocol profile coding Figure 70 illustrates three different examples of coding in the Protocol Profile.
Page 945: Operating Parameters
ISDN QSIG-BC and QSIG-GF Compliance Update Page 945 of 1814 On transmission, the Meridian 1 codes the Protocol Profile as “Networking Extension.” On reception, the Meridian 1 supports Protocol Profile coded as “ROSE” or “Networking Extension.” Network Protocol Profile coding The Network Protocol Profile is used to specify the Service APDU coding type.
Page 946: Feature Interactions
Page 946 of 1814 ISDN QSIG-BC and QSIG-GF Compliance Update There are two choices of PRI2 hardware for Option 51C, Option 61C, and Option 81C systems: • PRI2 card (NT8D72) and MSDL card (NT6D80) • Dual port DTI/PRI2 card (NTCK43) and either the Downloadable D-channel Daughterboard card (NTBK51) or the MSDL card (NT6D80) These systems require the QPC775 (Release E) or the QPC471 Clock Controller card.
Page 947: Feature Implementation
ISDN QSIG-BC and QSIG-GF Compliance Update Page 947 of 1814 The following software packages are required for ISL QSIG: • ISDN Signaling (ISDN) package 145 • ISDN Signaling Link (ISL) package 147 • Multi-Purpose Serial Data Link (MSDL) package 222 •...
Page 948: Feature Operation
Page 948 of 1814 ISDN QSIG-BC and QSIG-GF Compliance Update - IFC ESGF ETSI QSIG interface with GF platform. ISGF ISO QSIG interface with GF platform. LD 16 – Configure the updated interface type for the trunk route. Prompt Response Description Change existing data.
Page 949: Regional Material Statement
Feature operation ......... . Regional material statement ISDN BRI trunking is not available in North America. Contact your system supplier or your Nortel Networks representative to verify support of this product in your area. Feature description...
Page 950 Page 950 of 1814 ISDN QSIG Call Diversion Notification • Call Forwarding No Reply (CFNR) - the called set does not answer after a given number of rings • Call Forwarding Unconditional (CFU) - the called set is forwarded as soon as the set is reached With this feature, notification can be provided to the calling party and the forwarded-to (diverted) party that call diversion has occurred.
Page 951 ISDN QSIG Call Diversion Notification Page 951 of 1814 Figure 75 shows an example of a Call Diversion environment. Figure 75 Call Diversion Environment •Call Forwarding Unconditional •Call Forwarding Busy •Call Forwarding No Reply QSIG QSIG QSIG QSIG QSIG Meridian 1 QSIG QSIG QSIG...
Page 952: Calling Party's Notification
Page 952 of 1814 ISDN QSIG Call Diversion Notification Calling Party’s Notification The calling party that originates the call receives notification of call diversion depending on the configuration of the called party’s set. As shown in Table 71, the called party configures one of the three possible Classes of Service.
Page 953: Called Party's Notification
ISDN QSIG Call Diversion Notification Page 953 of 1814 Called Party’s Notification The forwarded-to (diverted) party receives notification of call diversion depending on the configuration of the called party’s set. As shown in Table 72, the called party configures one of the two possible Classes of Service.
Page 954: Operating Parameters
Page 954 of 1814 ISDN QSIG Call Diversion Notification On the forwarded-to (diverted) party’s set, the Dialed Name Display Allowed/Denied (DNDA/DNDD) Class of Service allows the forwarded-to (diverted) party to choose the name displayed after call diversion. If the forwarded-to (diverted) party configures a Dialed Name Display Allowed (DNDA) Class of Service their display shows one of the following: •...
Page 955: Feature Interactions
ISDN QSIG Call Diversion Notification Page 955 of 1814 The maximum allowable size of QSIG name information is 50 characters. With the Call Party Name Display feature, only 27 characters string length is supported. Accordingly, names processed by the Meridian 1 may be truncated.
Page 956: Feature Implementation
Page 956 of 1814 ISDN QSIG Call Diversion Notification • International Primary Rate Access (IPRA) package 202 • Multipurpose Serial Data Link (MSDL) package 222 ISDN Basic Rate Interface Trunk Access (BRIT) QSIG Interface requires: • Basic Rate Interface (BRI) package 216 •...
Page 957 ISDN QSIG Call Diversion Notification Page 957 of 1814 Remote Capability Meanings Table 73 indicates the remote capabilities meanings for both D-channel and BRI routes. When using Table 73 consider the following: • Only nodes subject to be Originating, Served, Diverted or Rerouting nodes with respect to QSIG Call Diversion Notification need to have diversion remote capability configured.
Page 958 Page 958 of 1814 ISDN QSIG Call Diversion Notification Only one remote capability allows the QSIG Diversion configuration on a D-channel/BRI route. This remote capability gathers the three following possibilities for the D-channel/BRI route: coding of operations is sent to the remote switch, which can be coded as either as Object Identifier or as Integer Value.
Page 959 ISDN QSIG Call Diversion Notification Page 959 of 1814 Table 73 Remote Capability Meanings DV2O Sent coded as Object Processed when received Identifier Not Sent DV2I Sent coded as Integer Value DV3O Sent coded as Object Processed when received Identifier Sent DV3I Sent coded as...
Page 960 Page 960 of 1814 ISDN QSIG Call Diversion Notification RCAP QSIG SS Call Diversion Notification remote capability. Configure sending of QSIG Diversion Notification Information, treatment of Rerouting request and coding of operations. If coded as Object Identifier, the remote capability ends with ‘O”, whereas for Integer Value, the remote capability ends with ‘I’.
Page 961 ISDN QSIG Call Diversion Notification Page 961 of 1814 RCAP QSIG SS Call Diversion Notification remote capability. Configure sending of QSIG Diversion Notification Information, treatment of Rerouting request and coding of operations. If coded as Object Identifier, the remote capability ends with ‘O”, whereas for Integer Value, the remote capability ends with ‘I’.
Page 962 Page 962 of 1814 ISDN QSIG Call Diversion Notification - -CPND_LANG Calling Party Name Display Language where: (ROM) = Roman. KAT = Katakana. - - NAME Calling Party Name Display Name where: aaaa First name bbbb Last name. QSIG Call Diversion Notification options for calling party.
Page 963 ISDN QSIG Call Diversion Notification Page 963 of 1814 l s c u Terminal Number. For Option 11C. x...x Flexible Call Forward No Answer DN for an Internal Directory Number. QSIG Call Diversion Notification options for calling party. (DNO3) Notification with diverted-to party’s number and name. DNO1 No notification.
Page 964 Page 964 of 1814 ISDN QSIG Call Diversion Notification - -CPND_LANG Calling Party Name Display Language where: (ROM) = Roman. KAT = Katakana. - - NAME Calling Party Name Display Name where: aaaa First name bbbb Last name. LD 27 – Configure Basic Rate Interface telephones Prompt Response Description...
Page 965 ISDN QSIG Call Diversion Notification Page 965 of 1814 FEAT xxxx QSIG Call Diversion Notification for forwarded-to (diverted) party where xxxx: DNDN = no notification of called party’s number and name notification (DNDY) = notification with called party’s number and name when available (default).
Page 966: Feature Operation
Page 966 of 1814 ISDN QSIG Call Diversion Notification x..x Directory Number. - NAME a..a Calling Party Name Display in ASCII characters. LD 11 – Configure the name that is to be displayed on the Forwarded-to (diverted) Party’s set Prompt Response Description REQ:...
Page 967: Regional Material Statement
Feature operation ......... . Regional material statement ISDN BRI trunking is not available in North America. Contact your system supplier or your Nortel Networks representative to verify support of this product in your area. International ISDN PRI Feature description and administration...
Page 968: Isdn Qsig Call Diversion Notification Enhancements
Page 968 of 1814 ISDN QSIG Call Diversion Notification Enhancements Feature description The ISDN QSIG Call Diversion Notification feature allows the Meridian 1 to provide notification to the originating calling party and forwarded-to (diverted) party when a call is forwarded over an ISDN QSIG private network.
Page 969: Operating Parameters
ISDN QSIG Call Diversion Notification Enhancements Page 969 of 1814 The notification of the originating set and the diverted-to set now depends on the type of signaling protocol that is in play (QSIG, DPNSS1, or MCDN), at what stage of the call establishment that the diversion takes place, and the user’s subscription option.
Page 970 Page 970 of 1814 ISDN QSIG Call Diversion Notification Enhancements Originating user’s notification rules Diversion Reason Notification rules: • This reason is displayed or not on the originating user’s set (as soon as Diversion Notification information is received from the served node) according to the served user’s Subscription option (see Table 74 on page 971).
Page 971 ISDN QSIG Call Diversion Notification Enhancements Page 971 of 1814 When both originating and diverted-to users are on the same Meridian 1 node, and diversion is performed by the Rerouting method, then the served user’s subscription options are effective for the originating user notification only before the diverted-to user answers, but no name is provided.
Page 972 Page 972 of 1814 ISDN QSIG Call Diversion Notification Enhancements Diverted-to user’s notification rules Diversion Reason Notification rules: • The reason is displayed on the diverted-to user’s set (as soon as Diversion Notification Information is received from the served node). Served Number Notification rules: •...
Page 973 ISDN QSIG Call Diversion Notification Enhancements Page 973 of 1814 Table 75 sums up the diverted-to user’s Notification rules, according to the served user’s Subscription options and the diverted-to user’s class of service DNDA/DNDD. Note that, in the case presented in the example, the Originating user name is Abby, with a DN of 4000.
Page 974 Page 974 of 1814 ISDN QSIG Call Diversion Notification Enhancements Multiple diversions Originating and Diverted-to user’s Notifications are detailed for the following scenario: “Station A calls Station B. Station B has activated CFU, CFB or CFNR to Station C. Station C has activated diversion to Station D, which itself has activated diversion to Station E.
Page 975 ISDN QSIG Call Diversion Notification Enhancements Page 975 of 1814 Diverted-to user’s notification rules Diversion Reason Notification rules: • The same rules apply as per the single diversion case (refer to page 970). Served Number Notification rules: • Either the originally-called number (as soon as a Diversion Notification information message is received from the last served node) is displayed or not on the diverted-to user’s set, according to the first served user’s Subscription option.
Page 976 Page 976 of 1814 ISDN QSIG Call Diversion Notification Enhancements Note that, in the case presented in the example, the Originating user name is Abby, with a DN of 4000. The first Served user name is Bobby, with a DN of 5001.
Page 977: Feature Interactions
ISDN QSIG Call Diversion Notification Enhancements Page 977 of 1814 Table 76 Diverted-to user’s notification versus served user’s Subscription option and diverted-to user class of service for multiple diversions (Part 2 of 2) H4000 H5001 F H4000 H5001 F Abby Bobby H4000 H---- F H4000 H---- F...
Page 978 Page 978 of 1814 ISDN QSIG Call Diversion Notification Enhancements Call waiting redirection The Call Waiting Redirection (CWTR) feature allows unanswered calls given Call Waiting treatment to receive call redirection via Call Forward No Answer (CFNA) for the active set. An unanswered call receiving Call Waiting treatment is redirected to the active set’s CFNA DN after the expiration of the customer data block defined CFNA timer selected for that set.
Page 979 ISDN QSIG Call Diversion Notification Enhancements Page 979 of 1814 Call Forward/Hunt Override This feature is not supported on QSIG Diversion. A Meridian 1 user can neither originate nor receive a call over a QSIG link via Call Forward/Hunt Override. At gateways between QSIG and MCDN, this information is lost. Access restrictions/trunk group access restrictions Access restrictions are checked on the served node.
Page 980 Page 980 of 1814 ISDN QSIG Call Diversion Notification Enhancements Meridian Link Present Call Indication A Present Call Indication message contents an IE called “Call Type”, which contains Diversion information about the incoming call. In case of a QSIG Diverted incoming call, this field is updated. Unsolicited Status Message When a set stops ringing because Call Forward No Reply has been applied to a QSIG call, an Unsolicited Status Message is sent to Meridian Link.
Page 981 ISDN QSIG Call Diversion Notification Enhancements Page 981 of 1814 QSIG Name Display Supplementary Services Calling Name After a QSIG Diversion takes place, and Call Diversion Notification information is received at the diverted-to node, the calling name is displayed on the diverted-to user’s set only if this set has a DNDD class of service. If the diverted-to user’s set has a DNDA class of service, another name or nothing is displayed.
Page 982 Page 982 of 1814 ISDN QSIG Call Diversion Notification Enhancements QSIG Alternate Routing When a QSIG Alternate Routing is performed, the Facility IE sent with the setup message are not re-sent. Therefore, the diverted-to user does not receive the DLI2 information and is not notified that a diversion occurred. Preventing Reciprocal Call Forward Configuring the Preventing Reciprocal Call Forward Allowed (PVCA) option in LD 15 prevents Call Forward looping.
Page 983 ISDN QSIG Call Diversion Notification Enhancements Page 983 of 1814 This feature is supported by QSIG, which transports the equivalent information. Note that this feature is an available solution for avoiding infinite diversion loops, since Preventing Reciprocal Call Forward is not supported network-wide.
Page 984: Feature Packaging
Page 984 of 1814 ISDN QSIG Call Diversion Notification Enhancements MCDN Trunk Route Optimization is blocked on MCDN calls due to the Rerouting method used by QSIG Diversion on No Reply, as far as the original call being kept by the originating PINX to eventually be restored for further treatment.
Page 985: Feature Implementation
ISDN QSIG Call Diversion Notification Enhancements Page 985 of 1814 • Multi-purpose Serial Data Link (MSDL) package 222 • Q-reference Signaling Point Interface (QSIG) package 263 • QSIG Generic Functional Protocol Transport (QSIG-GF) package 305 • Q-reference Signaling Point Interface Supplementary Services (QSIG-SS) package 316 For ISDN Basic Rate Interface Trunking (BRIT), the following additional packages are required:...
Page 986 Page 986 of 1814 ISDN QSIG Call Diversion Notification Enhancements LD 95 – Configure the QSIF Call Diversion Notification mnemonics, for Call Forward All Calls, Call Forward No Answer, and Call Forward Busy, in the Call Party Name Display data block. LD 95 –...
Page 987 ISDN QSIG Call Diversion Notification Enhancements Page 987 of 1814 Only one remote capability allows the QSIG Diversion configuration on a D-Channel/BRI route. This remote capability gathers the three following possibilities for the D-Channel/BRI route: coding of operations is sent to the remote switch, which can be coded as either as Object Identifier or as Integer Value.
Page 988 Page 988 of 1814 ISDN QSIG Call Diversion Notification Enhancements Table 77 Remote Capability Meanings (Part 2 of 2) DV2O Sent coded as Object Processed when received Identifier Not Sent DV2I Sent coded as Integer Value DV3O Sent coded as Object Processed when received Identifier Sent...
Page 989: Isdn Pri Implementation
ISDN QSIG Call Diversion Notification Enhancements Page 989 of 1814 ISDN PRI implementation LD 17 – Configure or remove remote capabilities D-Channel for QSIG Call Diversion Notification. Prompt Response Description Change existing data. TYPE ADAN Action Device and Number. - ADAN NEW DCH xx Add a D-Channel on port 0-63 (Options 51C-81C).
Page 990 Page 990 of 1814 ISDN QSIG Call Diversion Notification Enhancements RCAP QSIG SS Call Diversion Notification remote capability. Configure sending of QSIG Diversion Notification Information, treatment of Rerouting request and coding of operations. If coded as Object Identifier, the remote capability ends with ‘O”, whereas for Integer Value, the remote capability ends with ‘I’.
Page 991 ISDN QSIG Call Diversion Notification Enhancements Page 991 of 1814 - CPND Calling Party Name Display where aaa can be: NEW = Add data block. CHG = Change existing data block. OUT = Remove existing data block. Calling Party Name Display Language where: -CPND_LA (ROM) = Roman.
Page 992 Page 992 of 1814 ISDN QSIG Call Diversion Notification Enhancements x...x Flexible Call Forward No Answer DN for an Internal Directory Number. QSIG Call Diversion Notification options for calling party. Notification with diverted-to party’s number and name. (DNO3) No notification. DNO1 Notification without diverted-to party’s number and name.
Page 993 ISDN QSIG Call Diversion Notification Enhancements Page 993 of 1814 CUST Customer number, as defined in LD 15. xx = 0-99 for Options 51C-81C. xx = 0-31 for Option 11C. RESN Display Redirection reason allowed. (NO) = Display Redirection reason denied (default). - CFWD aaaa Mnemonic for Call Forward All Call display.
Page 994: Isdn Brit Implementation
Page 994 of 1814 ISDN QSIG Call Diversion Notification Enhancements TYPE: xxxx Telephone type, where: xxxx = SL1, 2006, 2008, 2009, 2016, 2018, 2112, 2216, 2317, 2616 or 3000. l s c u Terminal Number, for Options 51C-81C. l = loop, s = shelf, c = card, u = unit. Terminal Number for Option 11C.
Page 995 ISDN QSIG Call Diversion Notification Enhancements Page 995 of 1814 TKTP Trunk type. DTRK Digital Trunk Route. BRIP ISDN BRI packet handler route (NO is entered, since packet data is not required). - DGTP Digital trunk type. ISDN Integrated Services Digital Network. - IFC QSIG interface type where xxxx is: ESGF...
Page 996 Page 996 of 1814 ISDN QSIG Call Diversion Notification Enhancements LD 27 – Configure the Terminal Service Profile (TSP), to implement the QSIG Call Diversion options on BRI sets. Prompt Response Description Add new data. Change existing data. TYPE Terminal Service Profile. DSL Terminal Number location, for Options 51C-81C: lll (superloop) = 0-156 (must be zero or a number divisible by 4)
Page 997: Feature Operation
ISDN QSIG Call Diversion Notification Enhancements Page 997 of 1814 Feature operation No specific operating procedures are required to use this feature. International ISDN PRI Feature description and administration...
Page 998 Page 998 of 1814 ISDN QSIG Call Diversion Notification Enhancements 553-2901-301 Standard 9.00 January 2002...
Page 999: Isdn Qsig Call Transfer Notification
Feature operation ......... . 1014 Regional material statement ISDN BRI trunking is not available in North America. Contact your system supplier or your Nortel Networks representative to verify support of this product in your area. International ISDN PRI Feature description and administration...
Page 1000: Feature Description
Page 1000 of 1814 ISDN QSIG Call Transfer Notification Feature description The QSIG Call Transfer Notification feature supports the Call Transfer Notification capability over QSIG private networks, and over mixed QSIG/MCDN and QSIG/DPNSS1 networks. This applies to 2.0 Mbps Primary Rate Interface (PRI2), and ISDN Basic Rate Trunking (BRIT) applications.
Page 1001 ISDN QSIG Call Transfer Notification Page 1001 of 1814 Note: The underlined Class of Service values are in effect. Table 78 Originating set and transferred-to set display possibilities (Part 1 of 2) Originating set Originating set Transferred-to set Transferred-to set Class of Service display Class of Service...

This manual is also suitable for:

Meridian 1 Succession cse 1000