Nortel Meridian 1 Administration And Maintenance
  1. Manuals
  2. Brands
  3. Nortel Manuals
  4. Telephone
  5. Meridian Meridian 1
  6. Administration and maintenance

Nortel Meridian 1 Administration And Maintenance

Hide thumbs Also See for Meridian 1:
1
2
3
4
Table Of Contents
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
Table of Contents

Advertisement

Quick Links

Download this manual
Meridian 1
Option 11C
ISDN BRI Administration and Maintenance
Document Number: 553-3011-311
Document Release: Standard 7.0
Date: May 1999
Year Publish FCC TM
© 1993, 1999
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 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 the user will be required to correct the
interference at their own expense.
Meridian 1 is a trademark of Nortel Networks.
Option 11C
ISDN BRI Administration and Maintenance

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Related Manuals for Nortel Meridian 1

Summary of Contents for Nortel 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 Industry Canada.
  • Page 3 Revision history April 1999 Issue7.0 released as Standard for Generic X11 Release 24.2x. October 1997 Issue 6.00 released as Standard for Generic X11 Release 23. July 1996 Issue 5.00 released as Standard for Generic X11 Release 22. December 1995 Issue 4.00 released as Standard for Generic X11 Release 21B. July 1995 Issue 3.00 released as Standard for Generic X11 Release 21A.
  • Page 4 553-3011-311 Standard 7.0 May 1999...

  • Page 5: Table Of Contents

    Contents About this guide ......Chapter 1 — ISDN Basic Rate Interface ..Introduction .
  • Page 6 NI-1 BRI Compliance Enhancements ..... . . Set-based ISDN BRI features on Meridian 1 ISDN BRI terminals ..........
  • Page 7 Contents Hierarchical synchronization ....... . Stratum Levels ......... Guidelines .
  • Page 8 Contents Programming procedures for line application and packet data transmission Chapter 6 — ISDN BRI trunk implementation . . . 241 Introduction ..........ISDN BRI trunk access .
  • Page 9 Contents Removing the test setup ........Chapter 8 — Service changes and maintenance .
  • Page 10 Contents Error monitor messages (ERRxxxx) ......Network link messages (LNKxxx) ......Network and peripheral replacement messages (NPRxxx) .
  • Page 11 Contents Inspecting the NTBK50 circuit card ......Setting the switches on the NTBK50 ..... . . Mounting the daughterboards on the NTBK50 .
  • Page 12 viii Contents 553-3011-311 Standard 7.0 May 1999...

  • Page 13: About This Guide

    Page ix About this guide This guide provides information for the ISDN Basic Rate Interface feature for the Option 11C system. The information includes: — An overview of ISDN Basic Rate Interface — Feature descriptions — Feature packaging and prerequisites —...
  • Page 14 Page x About this guide 553-3011-311 Standard 7.0 May 1999...

  • Page 15: Chapter 1 - Isdn Basic Rate Interface

    Note: This document is intended to support the Meridian 1 Option 11 (sometimes referred to simply as the Option 11) system. (When only the term “Meridian 1" is referenced, it is meant to include all members of the Meridian 1 family (Meridian 1 Option 11 through Option 81C).

  • Page 16: Isdn Basic Rate Interface

    Page 2 of 492 Chapter 1 — ISDN Basic Rate Interface Option 11 provides the following ISDN accesses: — Primary Rate Interface (PRI) • 1.5 Mb T1 (23B+D) • 2.0 Mb E1 (30B+D) — Basic Rate Interface (BRI) • A single digital access connection This document focuses on Basic Rate Interface for the Option 11.
  • Page 17 Page 3 of 492 Chapter 1 — ISDN Basic Rate Interface Packet Data transmission - The Option 11 supports both B-channel and D-channel packet data transmission through an external DPN-100 packet handler. ISDN BRI allows simultaneous voice, circuit-switched data, and packet data transmission over a single DSL.

  • Page 18: Isdn Bri Protocol

    Page 4 of 492 Chapter 1 — ISDN Basic Rate Interface Figure 1 ISDN BRI standard maximum configuration ISDN BRI protocol ISDN standards have adopted the Open System Interconnect (OSI) protocol model to control ISDN functions. The OSI model defines seven layers required to perform all ISDN functions from establishing an end-to-end physical connection between two terminals to making a decision about the type of application that is to be activated.
  • Page 19 Page 5 of 492 Chapter 1 — ISDN Basic Rate Interface — Data link layer (layer 2) that provides point-to-point signaling used to establish a communication link between a terminal and its supporting BRI interface card. It also performs error checking and error recovery. —...

  • Page 20: Isdn Bri Line Access

    Page 6 of 492 Chapter 1 — ISDN Basic Rate Interface ISDN BRI line access ISDN BRI line access provides 2B+D ISDN service to terminating equipment such as ISDN telephone sets and data terminals. ISDN BRI line connections are configured on a per DSL basis, that is, DSL line connections may be configured on any given DSL for any SILC or UILC.
  • Page 21 Page 7 of 492 Chapter 1 — ISDN Basic Rate Interface Figure 3 ISDN Basic Rate Interface S/T interface configured as a line Terminal 4 Terminal 3 Terminal 1 Option 11 S/T Interface SILC Terminal 2 553-7551.EPS The S/T interface permits 4-wire multi-point connection of up to eight physical voice and data terminals on one DSL.
  • Page 22 Page 8 of 492 Chapter 1 — ISDN Basic Rate Interface The length of an S/T interface DSL depends on the specific terminal configuration and the DSL wire gauge, however, it should not exceed 1 km (3280 ft). Refer to Chapter 5 for more information. Terminal Adapters (TAs), as shown in Figure 3, are used to adapt non-BRI terminals to ISDN BRI line interface standards.
  • Page 23 Page 9 of 492 Chapter 1 — ISDN Basic Rate Interface Figure 4 ISDN Basic Rate Interface U interface configured as a line U Interface Option 11 UILC Server S/T Interface Terminal Adapter 553-7552.EPS 1TR6 terminal connectivity 1TR6 is the ISDN protocol used in Germany and in any country that supports this German protocol.
  • Page 24 Page 10 of 492 Chapter 1 — ISDN Basic Rate Interface Figure 5 shows a 1TR6 ISDN BRI terminal connected to a 1TR6 protocol adapter, which is used to access the Option 11. For specific 1TR6 configuration guidelines refer to Chapter 5 (for line applications) and Chapter 6 (for trunk applications).

  • Page 25: Isdn Bri Packet Data Transmission

    Page 11 of 492 Chapter 1 — ISDN Basic Rate Interface ISDN BRI Packet Data Transmission Packet switching differs from circuit switching in that the content of the call is switched rather than the call itself. The message that is being transmitted is broken down into packets that are then sent to their destination through the fastest route.
  • Page 26 Page 12 of 492 Chapter 1 — ISDN Basic Rate Interface Figure 6 Packet handling flow diagram Internal to Option 11 External to Option 11 Dedicated timeslots for Dedicated timeslot for B-channel packet data D-channel packet data Network Bus Packet Handler DPN -100 Packet Data...

  • Page 27: Isdn Bri Trunk Access

    Page 13 of 492 Chapter 1 — ISDN Basic Rate Interface ISDN BRI trunk access ISDN BRI trunk connections are configured on a per DSL basis, that is, DSL trunk connections may be configured on any given DSL for any SILC or UILC.
  • Page 28 Dependent on support from country through local exchange specific local exchanges (See Figure 8) ISDN BRI TIE trunk through NT1 Supported between any two Meridian 1 (See Figure 9) systems (see Note) ISDN BRI TIE trunk direct Supported between any two Meridian 1...

  • Page 29: Isdn Bri Local Exchange/Did Connectivity

    Page 15 of 492 Chapter 1 — ISDN Basic Rate Interface ISDN BRI Local Exchange/DID connectivity ISDN BRI Local Exchange connectivity is supported for 1TR6, Numeris, D70, EuroISDN, and Asia-Pacific protocols. This connection is accomplished through the SILC line card. Figure 7 illustrates the ISDN BRI Local Exchange connectivity.

  • Page 30: 1Tr6 Local Exchange Connectivity

    Page 16 of 492 Chapter 1 — ISDN Basic Rate Interface The ISDN BRI DSL is connected to a Network Termination (NT1) device, which is physically located on the same premises as the Option 11. The NT1 device connects to the Local Exchange that supports Numeris or 1TR6 protocol through a U interface.

  • Page 31: Numeris Vn2 Local Exchange Connectivity

    Numeris protocol. The NT6D70BA SILC card provides the layer 1 interface, the MISP provides the layer 2 and layer 3 pre-processing interface, and the Meridian 1 software handles the layer 3 interface. The ISDN BRI/Numeris local exchange connectivity provides the following basic call and supplementary services: —...

  • Page 32: Japan D70 (Ins Net-64) Local Exchange Connectivity (Non-Asia Pacific Protocol)

    D70 protocol (D70 is the ISDN Japan protocol). The SILC card provides the layer 1 interface, the MISP provides the layer 2 and layer 3 pre-processing interface, and the Meridian 1 software handles the layer 3 interface. The ISDN BRI/Japan D70 local exchange connectivity provides the following basic call and supplementary services: —...

  • Page 33: Euroisdn Connectivity

    ETS 300 102 to be supported. The SILC card provides the layer 1 interface, the MISP provides the layer 2 functions and the layer 3 protocol control functions, and the Meridian 1 software handles the layer 3 interface.

  • Page 34: Asia-Pacifc Connectivity

    Page 20 of 492 Chapter 1 — ISDN Basic Rate Interface Asia-Pacifc connectivity This Asia Pacific Connectivity provides interface between the Meridian 1 and Public Exchange/Central Offices in the following markets: — Australia — China — Hong Kong — Indonesia —...
  • Page 35 Page 21 of 492 Chapter 1 — ISDN Basic Rate Interface — PRI Route Back-up with BRI routes, and — Sub-addressing The following supplementary services are supported for the Australia connectivity only: — Malicious Call Trace — Advice of Charge (AOC) at End of Call —...

  • Page 36: Isdn Bri Trunk Connectivity

    Page 22 of 492 Chapter 1 — ISDN Basic Rate Interface ISDN BRI trunk connectivity ISDN BRI TIE trunk connectivity ISDN BRI TIE trunk connectivity may have three implementations. In the first configuration (refer to Figure 8), a Meridian Customer Defined Networking (MCDN) TIE trunk connection may be implemented by connecting two Option 11s to the ISDN BRI leased line through the local exchange through two SILC cards.
  • Page 37 SILC, derive clock reference from the BRI TIE trunk connection or from other PRI/DTI/BRI connections if available. The Meridian 1 equipped with the UILC interface may be allowed to operate in free-run mode or derive the clock source from other PRI/DTI/BRI...
  • Page 38 Meridian 1s derive clock reference from the BRI TIE trunk connection or from any other PRI/DTI/BRI connections if available. The other Meridian 1 may be allowed to operate in free-run mode or derive the clock source from any PRI/DTI/BRI connections if available.

  • Page 39: Qsig Isdn Bri Trunk Connectivity

    Page 25 of 492 Chapter 1 — ISDN Basic Rate Interface QSIG ISDN BRI trunk connectivity 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 40 Page 26 of 492 Chapter 1 — ISDN Basic Rate Interface Figure 11 QSIG ISDN BRI trunk connectivity Public Public Network Network ETSI ISDN BRI/PRI Third party (public access) ISDN BRI QSIG QSIG ISDN BRI/PRI ISDN BRI/PRI Option 11 Option 11 ISDN BRI ISDN BRI terminal equipment...

  • Page 41: Chapter 2 - Feature Descriptions

    BRI. The chapter is divided into the following sections: — A description and implemntation procedures for ISDN BRI specific features, including set-based ISDN BRI features on Meridian 1 ISDN BRI terminals (the M5317TDX and the M5209TDcp) — Generic X11 features: •...

  • Page 42: Isdn Bri Specific Features

    Page 28 of 492 Chapter 2 — Feature descriptions ISDN BRI specific features The following unique ISDN BRI features are described below. Where applicable, implementation procedures are provided. — Calling Line Identification Presentation/Calling Line Identification Restriction — ISDN BRI National ISDN-1 Conference —...

  • Page 43: Calling Line Identification Presentation And Restriction

    Page 29 of 492 Chapter 2 — Feature descriptions Calling Line Identification Presentation and Restriction This feature allows or restricts the display of a Calling Line ID on the called party terminal. Calling Line ID Presentation (CLIP) controls the called party terminal’s choice to display the calling line identification for incoming calls.

  • Page 44: National Isdn-1 Conference

    An ISDN BRI terminal can also be conferenced into a call by a non-ISDN BRI terminal. Meridian 1 ISDN BRI supports two versions of Conference: A03, a 3-party Conference and A06, a 6-party Conference. See ISDN Basic Rate Interface administration (5533901300) for configuration details.
  • Page 45 Page 31 of 492 Chapter 2 — Feature descriptions Add a conferee The ISDN BRI user can add a conferee with Consultation Hold, add a held call to an active conference, or add an active call to a held conference providing: —...
  • Page 46 Page 32 of 492 Chapter 2 — Feature descriptions Programming procedures for ISDN BRI National ISDN-1 Conference The following steps should be used to configure ISDN BRI National ISDN-1 Conference: Configure National ISDN-1 protocol for a DSL using LD 27. Configure Conference in the TSP using LD 27.
  • Page 47 Page 33 of 492 Chapter 2 — Feature descriptions LD 27 – Configuring Conference in the TSP. Prompt Response Description NEW/CHG New, or change. TYPE Terminal Service Profile. c dsl# DSL address. FEATID aaa mmm nnn Feature ID (must be unique for a TSP), where: Xmmm aaa = feature;...

  • Page 48: Isdn Bri Circuit-Switched Data Calls

    ISDN BRI to ISDN BRI circuit-switched data calls Circuit-switched data calls between two ISDN BRI terminals are supported for all bearer capability encodings. The Meridian 1 screens for the validity of its bearer capability codepoints only; it does not screen for protocol compatibility between two ISDN BRI devices.
  • Page 49 Page 35 of 492 Chapter 2 — Feature descriptions The following describe the bearer capability encodings used by ISDN BRI terminals that support TLINK protocol. Only calls originating from ISDN BRI with these bearer capability encodings are allowed to terminate to a MCA: —...
  • Page 50 ISDN BRI devices using other bearer capability encodings can communicate with another ISDN BRI device across ISDN PRI under these conditions: — the ISDN PRI interface is Meridian 1, Japan D70, or ESS#4/ESS#5; — the remote capability for ISDN BRI interworking is turned on (in LD17) for all ISDN PRI interfaces involved in the call.
  • Page 51 DTE type MCU, because the MCU supports TLINK protocol. ISDN BRI devices cannot communicate with other Meridian 1 DTE type data modules that connect to modems because they use the DM-DM protocol. ISDN BRI terminals may access analog lines through modem trunk...

  • Page 52: Isdn Bri Special Call Forward Busy

    Page 38 of 492 Chapter 2 — Feature descriptions ISDN BRI Special Call Forward Busy This feature is activated for a call terminated at a DSL. The call is forwarded to the attendant when a call encounters the following busy conditions. The calling party receives a busy tone in all other cases.

  • Page 53: Isdn Bri Etsi Call Forwarding Unconditional

    Forwarding Unconditional (CFU) supplementary service allows an incoming call to an ISDN) BRI terminal to be forwarded to a predetermined destination, within or outside the Meridian 1 system. The call is forwarded regardless of whether the user is busy or idle.
  • Page 54 Chapter 2 — Feature descriptions ETSI public ISDN partial rerouting will not be supported. According to ETSI standards, when the Meridian 1 receives a local exchange call and the call is forwarded within or outside of the system, the Meridian 1 should send a message to the local exchange to make the call directly to the forwarded-to user.
  • Page 55 Chapter 2 — Feature descriptions Call Forward All Calls The Meridian 1 Call Forward All Calls feature allows only calls to the Prime DN or a single appearance DN to be forwarded. For an ISDN BRI set, calls are forwarded based on this basic service. Since ETSI CFU supplementary...
  • Page 56 ISDN BRI: — Basic Rate Interface (BRI) package 216 — Basic Rate Interface Line Application (BRIL) package 235, and — Meridian 1 Extended Peripheral Equipment (XPE) package 203. Programming procedures for ISDN BRI ETSI Call Forwaring Unconditional...
  • Page 57 DSL address (as already entered in step 1). USID 0-15 User Service Identifier. 0 = default TSP. MPHC This TSP is not configured for Meridian 1 Packet Handler. SPID aaaaaaaaa Service Profile Identifier (up to nine characters; eight SPIDs per TSP).

  • Page 58: Isdn Bri Etsi Conference

    ETSI specifies. ETSI specifies that when a conference controller disconnects, all conferees will be disconnected; however, this subfeature follows the current Meridian 1 Conference feature in that when a conference controller disconnects the conference continues for the remaining parties).
  • Page 59 Page 45 of 492 Chapter 2 — Feature descriptions The Meridian 1 only sends notification messages to conferees or the conference controller when conference operations are requested and performed if they are ISDN BRI users. If a user is on another node across ISDN or non-ISDN trunks, the Notify message will not be sent.
  • Page 60 Page 46 of 492 Chapter 2 — Feature descriptions Programming procedures for ISDN BRI ETSI Conference The following steps should be used to configure ISDN BRI ETSI Conference: Configure ETSI protocol for a DSL using LD 27 Configure Conference in the TSP using LD 27. LD 27 —...

  • Page 61: Isdn Bri National Isdn-1 Call Forward All Calls

    Operating parameters This feature is based on the Meridian 1 Call Forward All Calls feature; therefore, it is subject to the same limitation as the Meridian 1 Call Forward All Calls feature. ISDN BRI terminals must support the Feature Key Management protocol.
  • Page 62 Feature interactions Call Forward All Calls Meridian 1 Call Forward All Calls only allows calls to a prime DN or single appearance DN to be forwarded. For the BRI interface, the terminology of prime DN and single appearance DN does not apply. When Call Forward has...
  • Page 63 Page 49 of 492 Chapter 2 — Feature descriptions Remote Call Forward Remote Call Forward allows a user to program Call Forwarding from a remote set. Call Forwarding remotely to an ISDN BRI terminal is supported. However, using Remote Call Forward from an ISDN BRI terminal is not supported.
  • Page 64 ISDN BRI: — Basic Rate Interface (BRI) package 216 — Basic Rate Interface Line Application (BRIL) package 235, and — Meridian 1 Extended Peripheral Equipment (XPE) package 203. Programming procedures for ISDN BRI National ISDN-1 Call Forward All Calls...
  • Page 65 Page 51 of 492 Chapter 2 — Feature descriptions LD 27 — Configuring Call Forward All Calls in the TSP Prompt Response Comment Change data. TYPE Terminal Service Profile c dsl# DSL address (as already entered in step 1). nnnnnnn Directory Number associated with the TSP(up to seven digits).

  • Page 66: Isdn Basic Rate Interface Connected Line Presentation/Restriction

    Presentation/Restriction ISDN Basic Rate Interface Connected Line Presentation/Restriction is a supplementary service that enables the Meridian 1 to either allow or restrict the presentation of a connected party’s ISDN number and sub-address on the display of an ISDN BRI terminal. The presentation of a ISDN number and sub-address to the calling party occurs when the connected party’s ISDN BRI...
  • Page 67 Page 53 of 492 Chapter 2 — Feature descriptions ISDN BRI COLP/COLR coding is based on ETSI protocol. COLP/COLR from or to the public network is available to all countries, using the EuroISDN DSS1 protocol on the BRI interface. The construction of the ISDN BRI connected number follows the same rules that apply to Calling Line Identification when sending an extension number over the same interface.
  • Page 68 Page 54 of 492 Chapter 2 — Feature descriptions ISDN Calling Line Identification Enhancement The ISDN Calling Line Identification Enhancement allows the choice of National and Local prefixes. This is applicable to connected numbers received from a ISDN BRI terminal and sent over a ISDN trunk. EuroISDN Continuation The EuroISDN Continuation capability adds National and Local prefixes to the connected number being sent.
  • Page 69 When Connected Line Restriction (COLR) has been enabled on the connected party’s ISDN BRI terminal, the Meridian 1 system transmits the connected party’s information element, based on the Terminal Service Profile (TSP) configuration of the calling user (TRANS prompt in LD 27).
  • Page 70 - COLP (NO), YES YES = Connected, number is passed from Meridian 1 to ISDN BRI terminal. NO = Connected, number is not passed from Meridian 1 to ISDN BRI terminal. - TRANS (NO), YES YES = Connected, number is transmitted to the ISDN BRI terminal as received with no modification.
  • Page 71 Page 57 of 492 Chapter 2 — Feature descriptions LD 27 – Configuring Connected Line Presentation/Restriction for a DSL. Prompt Response Description Create new data block. TYPE Digital Subscriber Loop. c dsl# Digital Subscriber Loop address. USID User Service Identifier. PRID Protocol Identification.

  • Page 72: Ni-1 Bri Compliance Enhancements

    Service Profile Identification (SPID) has been expanded from 9 to 20 characters (although the NI-1 standard only requires that the SPID range be from 9-20, the Meridian 1 implementation supports 1-20). The SPID is configured in Overlay 27 (by administering the Terminal Service Profiles) for the network side, and programmed on NI-1 compatible ISDN BRI terminals for the user side (both entries for the SPID must be the same).
  • Page 73 Page 59 of 492 Chapter 2 — Feature descriptions LD 27 – Administer the Terminal Service Profiles (TSPs) on a Digital Subscriber Loop (DSL). Prompt Response Description Add a TSP. Change a TSP. TYPE Administer the TSP on a DSL. c dsl# DSL location.
  • Page 74 Page 60 of 492 Chapter 2 — Feature descriptions Configure the NI-1 protocol for a DSL. LD 27 – Refer to the note above pertaining to selecting the NI-1 protocol on the ISDN BRI terminals. Prompt Response Description Add a TSP. Change a TSP.

  • Page 75: Set-Based Isdn Bri Features On Meridian 1 Isdn Bri Terminals

    Page 61 of 492 Chapter 2 — Feature descriptions Set-based ISDN BRI features on Meridian 1 ISDN BRI terminals The following features are supported on M5317TDX terminals: — AutoDial Keys (up to 9 keys each with 20 digit numbers) — Inspect Key —...

  • Page 76: Generic X11 Features

    Page 62 of 492 Chapter 2 — Feature descriptions Generic X11 features ISDN BRI Lines — Generic X11 This section begins with a quick reference table (Table 2) of features with a column that indicates how this feature is supported by ISDN BRI lines. Reference to the notes at the end of the table provide some detail about the support of the feature.
  • Page 77 Page 63 of 492 Chapter 2 — Feature descriptions Note 1: ISDN BRI Terminal can ONLY initiate calls to the user equipped with this feature. Note 2: ISDN BRI Terminal CAN NOT invoke this feature, however, the non-ISDN BRI calling party (calling an ISDN BRI user) will have access to this feature.
  • Page 78 Page 64 of 492 Chapter 2 — Feature descriptions Table 2 Generic X11 features on ISDN BRI lines Features and services Supported Comments — A— Access Restrictions** See details later in this chapter Access to Paging** See details later in this chapter Access to Recorded Telephone See details later in this...
  • Page 79 Page 65 of 492 Chapter 2 — Feature descriptions Table 2 Generic X11 features on ISDN BRI lines Features and services Supported Comments Attendant consoles Attendant End-to-End Signaling** See details later in this chapter Attendant Incoming Call Indicators Attendant Interpositional Transfer Attendant Lockout Attendant Overflow Position** See Note 1 and details...
  • Page 80 Page 66 of 492 Chapter 2 — Feature descriptions Table 2 Generic X11 features on ISDN BRI lines Features and services Supported Comments Automatic Call Distribution** See Note 1 and details later in this chapter. Automatic Hold Automatic Line Selection See Note 3 Automatic Number Identification See Note 4...
  • Page 81 Page 67 of 492 Chapter 2 — Feature descriptions Table 2 Generic X11 features on ISDN BRI lines Features and services Supported Comments Basic Call, North American ISDN PRI See details later in this Connectivity** chapter Bearer Capability in CDR Boss/Secretary Filtering Enhancement Bridging Busy Lamp Field Array...
  • Page 82 Page 68 of 492 Chapter 2 — Feature descriptions Table 2 Generic X11 features on ISDN BRI lines Features and services Supported Comments Call Forward External Deny Call Forward and Hunt by Call Type** See details later in this chapter Call Forward No Answer** See details later in this chapter...
  • Page 83 Page 69 of 492 Chapter 2 — Feature descriptions Table 2 Generic X11 features on ISDN BRI lines Features and services Supported Comments Call Park** See details later in this chapter Call Park Network Wide Call Park on Unsupervised Trunks Call Party Name Display** See details later in this chapter...
  • Page 84 Page 70 of 492 Chapter 2 — Feature descriptions Table 2 Generic X11 features on ISDN BRI lines Features and services Supported Comments Calling Party Number Calling Party Privacy Override Charge Account and Calling Party No See Note 1 Calls Waiting Indication (Attendant) CAMA Trunks Camp-on Capacity Expansion...
  • Page 85 Page 71 of 492 Chapter 2 — Feature descriptions Table 2 Generic X11 features on ISDN BRI lines Features and services Supported Comments Controlled Class Of Service Controlled Class of Service, Enhanced Coordinated Dialing Plan Coordinated Call-Back Queuing Coordinated Call-Back Queuing - Main —...
  • Page 86 Page 72 of 492 Chapter 2 — Feature descriptions Table 2 Generic X11 features on ISDN BRI lines Features and services Supported Comments Directory Number Directory Number Expansion** See details later in this chapter Display of Access Prefix on CLID Distinctive/New Distinctive Ringing Distinctive Ringing by DN Distinctive Ringing for Dial Intercom...
  • Page 87 Page 73 of 492 Chapter 2 — Feature descriptions Table 2 Generic X11 features on ISDN BRI lines Features and services Supported Comments Electronic Lock Network Wide/Electronic Lock on Private Lines Equal Access Compliance ESN Queuing Exclusive Hold — F — Fast Tone Digit Switch FCC Compliance for DID Answer Supervision...
  • Page 88 Page 74 of 492 Chapter 2 — Feature descriptions Table 2 Generic X11 features on ISDN BRI lines Features and services Supported Comments — G — Global CDR Record Group Call Group Hunt** See details later in this chapter Guest Entry of Automatic Wake Up —...
  • Page 89 Page 75 of 492 Chapter 2 — Feature descriptions Table 2 Generic X11 features on ISDN BRI lines Features and services Supported Comments In-Band ANI Incoming DID Digit Conversion** See Note 7 and details later in this chapter Incremental Software Management** See details later in this chapter Incoming Call Indicators...
  • Page 90 Page 76 of 492 Chapter 2 — Feature descriptions Table 2 Generic X11 features on ISDN BRI lines Features and services Supported Comments ISDN BRI Connected Line Presentation/Restriction ISDN BRI to ISDN BRI Circuit Switched Data Call ISDN BRI Circuit-Switched Data Call over PRI ISDN BRI Circuit- Switched Data Call for Tandem...
  • Page 91 Page 77 of 492 Chapter 2 — Feature descriptions Table 2 Generic X11 features on ISDN BRI lines Features and services Supported Comments ISDN QSIG/ETSI Generic Functional Transport Enhancement ISDN QSIG-BC and QSIG_GF Compliance Update ISDN QSIG Channel ID Coding ISDN QSIG Name Display** See details later in this chapter...
  • Page 92 Manual Line Service Manual Signaling (Buzz) Manual Trunk Service MCDN Alternate Routing MCDN End to End Transparency Meridian 1 Attendant Console Enhancement Meridian Communications Adapter See details later in this (MCA) Data Module** chapter Meridian Companion Enhanced...
  • Page 93 Page 79 of 492 Chapter 2 — Feature descriptions Table 2 Generic X11 features on ISDN BRI lines Features and services Supported Comments Message Waiting (Meridian Mail)** See Note 3 and details later in this chapter Modem Trunk Hunting MSDL Idle Code Selection MSDL Port Overload Counter MSDL Status Enquiry Message Throttle Multiple Appearance Directory Number...
  • Page 94 Page 80 of 492 Chapter 2 — Feature descriptions Table 2 Generic X11 features on ISDN BRI lines Features and services Supported Comments Network Alternate Route Selection** See details later in this chapter Network Attendant Service** See details later in this chapter Network Authorization Codes Network Call Transfer**...
  • Page 95 Page 81 of 492 Chapter 2 — Feature descriptions Table 2 Generic X11 features on ISDN BRI lines Features and services Supported Comments Night Key for DID Digit Manipulation Night Service/TAFAS** See Note 1 and details later in this chapter Night Service by Time of Day See Note 6 No Hold Conference...
  • Page 96 Page 82 of 492 Chapter 2 — Feature descriptions Table 2 Generic X11 features on ISDN BRI lines Features and services Supported Comments Packet Switched Data Service Paging Permanent Hold Position Busy Preference Trunk Usage Pretranslation** See details later in this chapter Pretranslation and System Speed Call Enhancement...
  • Page 97 Page 83 of 492 Chapter 2 — Feature descriptions Table 2 Generic X11 features on ISDN BRI lines Features and services Supported Comments — R — Recall (Attendant)** See Note 2 and see details later in this chapter Recall After Parking Recall to Same Attendant** See details later in this chapter...
  • Page 98 Page 84 of 492 Chapter 2 — Feature descriptions Table 2 Generic X11 features on ISDN BRI lines Features and services Supported Comments Schedule Access Restriction Secrecy (Attendant) Secretarial Filtering Selectable Conferee Display and Disconnect Short Buzz for digital sets Signal source and destination Single Appearance DN Six Party Conference for 2500 Sets...
  • Page 99 Page 85 of 492 Chapter 2 — Feature descriptions Table 2 Generic X11 features on ISDN BRI lines Features and services Supported Comments Station-to-Station-Calling Station-to-Station Call Waiting Stored Number Redial See Note 3 Supervisory Attendant Console System Capacity Expansion Switched 56 Kbps Service** See details later in this chapter —...
  • Page 100 Page 86 of 492 Chapter 2 — Feature descriptions Table 2 Generic X11 features on ISDN BRI lines Features and services Supported Comments Trunk Verification from a Station SPRE codes are not supported — U — Uninterrupted Line Connections Uniform Dialing plan —...

  • Page 101: Features Supported By Isdn Bri As A Line

    Page 87 of 492 Chapter 2 — Feature descriptions Features supported by ISDN BRI as a Line The following descriptions provide additional information for the features tagged with "**" in Table 2. Access Restrictions Access restriction for an ISDN BRI terminal is based on assigned class of service, trunk group access restriction, and area and exchange codes dialed by the terminal.
  • Page 102 Page 88 of 492 Chapter 2 — Feature descriptions Call forward no answer and second level call forward no answer are activated if FNA and SFA are selected for a DN when configuring the TSP using Service Change ISDN BRI Program LD 27. If a call is not answered after a predetermined timer expires, the initial call setup is released from the DSL and call forward no answer routes the call to an alternate DN.
  • Page 103 DSL are not enabled or fail to handle the call. ISDN BRI call waiting is subject to call forward no answer as defined in the Meridian 1. Departmental LDN This feature allows specified terminals to share the same numbering plan and to access the attendant console or consoles dedicated to a departmental LDN.
  • Page 104 Page 90 of 492 Chapter 2 — Feature descriptions A call terminating at an ISDN BRI DN can be redirected to Meridian Mail or Network Message Services-Meridian Mail (NMS-MM) through call forward no answer. A call originating from an ISDN BRI terminal to a non-ISDN BRI terminal can also be redirected to Meridian Mail or NMS-MM through call redirection on the non-ISDN BRI terminal.
  • Page 105 Page 91 of 492 Chapter 2 — Feature descriptions Departmental listed directory number groupings are supported for ISDN BRI and are configured for a DSL using Service Change ISDN BRI Program LD 27. This allows assignment of a DSL to one of the four listed directory number groups.

  • Page 106: Features Partially Supported By Isdn Bri As A Line

    Page 92 of 492 Chapter 2 — Feature descriptions Features partially supported by ISDN BRI as a line The following descriptions provide additional information for the features tagged with:**: in Table 2. Attendant Alternative Answering An ISDN BRI DN cannot be assigned as an attendant alternative answering DN.
  • Page 107 Page 93 of 492 Chapter 2 — Feature descriptions Automatic Call Distribution An ISDN BRI terminal cannot be an ACD agent terminal, however, an ISDN BRI terminal can place a call to an ACD agent. Call Forward All Calls An ISDN BRI terminal does not support call forward all calls. Calls originating from an ISDN BRI terminal can be forwarded if call forwarding is activated by a non-ISDN BRI terminal.
  • Page 108 Page 94 of 492 Chapter 2 — Feature descriptions Calling Line Identification Calling line identification is sent across ISDN PRI to and/or from ISDN BRI terminals. Trunk access code is displayed at the called ISDN BRI terminal instead of the calling line identification if it has calling party number restricted.
  • Page 109 Page 95 of 492 Chapter 2 — Feature descriptions For voice messages, an ISDN BRI terminal that can generate end-to-end signaling can access other options available. Calls terminated on an ISDN BRI terminal may be redirected to IMS/IVMS through call forward no answer or hunting, but the ISDN BRI DN will not have a mailbox defined and a caller may not leave a message for an ISDN BRI ISDN BRI Network Ring Again The Network Ring Again feature cannot be activated from nor offered to an...
  • Page 110 Page 96 of 492 Chapter 2 — Feature descriptions Multi-Party Operations Call Join The Call Join feature allows a controlling party to conference-in or transfer an active party to a held party. The controlling party can then hang up. The controlling party’s terminal must be equipped with a Conference 3/6 key, and at least one secondary DN or Call Waiting key.
  • Page 111 Network Attendant Service Network Attendant Service (NAS) provides the capability of stand alone attendant service, full or part time, across a Meridian 1 network. NAS provides the following attendant features network wide: — attendant routing, which allows calls to an attendant to be routed to any other destination within the network;...
  • Page 112 Page 98 of 492 Chapter 2 — Feature descriptions — attendant control, which gives the attendant control of the call, including control of disconnecting the call and the ability to exclude the source or destination; — ring held party, which allows the attendant console to receive ringing if a terminal that originated a call to the attendant disconnects while attendant control is configured;...
  • Page 113 Page 99 of 492 Chapter 2 — Feature descriptions Priority Override Priority Override is partially supported on ISDN BRI terminals, as explained below: — Priority Override to an ISDN BRI terminal is not possible, because Priority Override require Warning Tone Allowed Class of Service (ISDN BRI terminals are defaulted to WTD COS);...

  • Page 114: Isdn Bri Trunk Access Features: Generic X11

    ISDN BRI Trunk Access features: Generic X11 ISDN PRI features interaction with ISDN BRI All Meridian 1 networking features and services supported by ISDN PRI are also supported by ISDN BRI. The following exceptions apply: ISDN PRI features not supported The following ISDN PRI specific features are not supported by ISDN BRI: —...
  • Page 115 Page 101 of 492 Chapter 2 — Feature descriptions — Trunk Optimization (SL-1 to SL-1 only) — Virtual Network Services - VNS takes advantage of ISDN signaling through a private D-channel using the Public Exchange voice connections instead of TIE trunk connections. It is not possible to configure a D-channel of an ISDN BRI Trunk Access as a VNS D-channel.

  • Page 116: Generic X11 International Features - Lines And Trunks

    Page 102 of 492 Chapter 2 — Feature descriptions Generic X11 International features — lines and trunks Generic X11 International features interaction This section defines the Generic X11 International feature support and interaction with ISDN BRI. Table 3 indicates to what extent the Generic X11 International features are supported by ISDN BRI.
  • Page 117 Page 103 of 492 Chapter 2 — Feature descriptions Table 3 Generic X11 International features on ISDN BRI Features and services Supported Comments —A— ACD Answering Time in Night Service ACD Call Priority ACD Call Waiting Threshold ACD Calls on Hold ACD Enhancements —...
  • Page 118 Page 104 of 492 Chapter 2 — Feature descriptions Table 3 Generic X11 International features on ISDN BRI Features and services Supported Comments Alternative Loss Plan Analog Semi-permanent Connection Asia Pacific CO trunks only Connectivity Attendant and Network See details later in this Wide Remote Call chapter Forward**...
  • Page 119 Page 105 of 492 Chapter 2 — Feature descriptions Table 3 Generic X11 International features on ISDN BRI Features and services Supported Comments — B — Bar Reciprocal Call Forward Bearer Capability in CDR Boss/Secretary Filtering Enhancement Break-in Features — Break-in to inquiry calls —...
  • Page 120 Page 106 of 492 Chapter 2 — Feature descriptions Table 3 Generic X11 International features on ISDN BRI Features and services Supported Comments Call Forward, Break-In and Hunt Internal or External Network Wide Call Forward/Hunt See details later in this Override via FFC** chapter Call Forward to Trunk...
  • Page 121 Page 107 of 492 Chapter 2 — Feature descriptions Table 3 Generic X11 International features on ISDN BRI Features and services Supported Comments CIS Multifrequency Shuttle CIS Toll Dial Tone Detection — D — Default Loss Plan Dial Tone Detection DID to Network Calling Digital Private Networking Signaling...
  • Page 122 Page 108 of 492 Chapter 2 — Feature descriptions Table 3 Generic X11 International features on ISDN BRI Features and services Supported Comments End of Selection End of Selection Busy End-to-End Signaling Display Enhancement Enhanced Charge Display Enhanced Malicious Call Trace Enhanced Secrecy EuroISDN**...
  • Page 123 Page 109 of 492 Chapter 2 — Feature descriptions Table 3 Generic X11 International features on ISDN BRI Features and services Supported Comments FCC Compliance for Equal Access FCC Compliance for Equal Access - CAC Expansion First-Second Degree Busy Indication Flexible Attendant Call Waiting Threshold Flexible Busy Tone...
  • Page 124 Page 110 of 492 Chapter 2 — Feature descriptions Table 3 Generic X11 International features on ISDN BRI Features and services Supported Comments Hold Features — Automatic Hold — Held Call Clearing Hunting by Call Type Hunting and Speed Call See details later in this Features** chapter...
  • Page 125 Page 111 of 492 Chapter 2 — Feature descriptions Table 3 Generic X11 International features on ISDN BRI Features and services Supported Comments Interchangeable NPA IPE Completion IPE Loss Plan for China ISDN BRI Trunk Access for Japan ISDN CLID Enhancements ISDN QSIG Alternate Routing...
  • Page 126 Page 112 of 492 Chapter 2 — Feature descriptions Table 3 Generic X11 International features on ISDN BRI Features and services Supported Comments ISDN QSIG Path trunks only Replacement ISDN QSIG Supplementary Services - Name Display Enhancement ISDN Semi Permanent Connection for Australia Italian Phase 2 Features for DTI2...
  • Page 127 Generic X11 International features on ISDN BRI Features and services Supported Comments Malicious Call Trace on Manual Service Recall to Attendant Meridian 1 to New See details later in this Zealand NEAX-61 ISDN chapter PRI connectivity** Meridian Hospitality Voice Services...
  • Page 128 Page 114 of 492 Chapter 2 — Feature descriptions Table 3 Generic X11 International features on ISDN BRI Features and services Supported Comments — N — NACD Source Table Viewer N Digit DNIS Network Anti-tromboning Network Application Protocol Link Enhancement Network Call Pick-up and TAFAS Network Drop Back Busy...
  • Page 129 Page 115 of 492 Chapter 2 — Feature descriptions Table 3 Generic X11 International features on ISDN BRI Features and services Supported Comments — O — On Hold on Loudspeaker Option 11 Downloadable D-channel Overlap Signaling — P — Partial Dial Timing Periodic Camp-on Tone Periodic Clearing Periodic Pulse...
  • Page 130 Page 116 of 492 Chapter 2 — Feature descriptions Table 3 Generic X11 International features on ISDN BRI Features and services Supported Comments Recorded See details later in this Announcement for Calls chapter Diverted to External Trunks** Restricted DID Class of Service Ring Again on No Answer...
  • Page 131 Page 117 of 492 Chapter 2 — Feature descriptions Table 3 Generic X11 International features on ISDN BRI Features and services Supported Comments Series Call Seizure Acknowledgment Selectable Directory Number Size Single Digit Access to Hotel Services Slow Answer Recall Modification Source Included When Attendant Dials...
  • Page 132 Page 118 of 492 Chapter 2 — Feature descriptions Table 3 Generic X11 International features on ISDN BRI Features and services Supported Comments — T — Taiwan R1 Modified sets only Signaling Telelink Mobility Switch Telset Call Timer Enhancement Tone to Last Party Transfer Tone Trunk Direct Inward Dialing Digitone Receiver...
  • Page 133 Page 119 of 492 Chapter 2 — Feature descriptions Table 3 Generic X11 International features on ISDN BRI Features and services Supported Comments Virtual Network Services in the UK with DASS2/DPNSS1 Bearers Virtual Network Services in the UK with Virtual DN Expansion Voice Call Override The following lists the Generic X11 International features that are tagged in...

  • Page 134: Generic X11 International Features Partially Supported

    Attendant and Network Wide Remote Call Forward Prior to Release 20, the Remote Call Forward (RCFW) feature allowed a user to administer call forward from a remote set within the Meridian 1 or from outside the Meridian 1 through the Direct Inward System Access (DISA) number.
  • Page 135 Code (FFC) feature. Call Forward/Hunt Override Via FFC works in network environments with Meridian 1 nodes and Meridian Customer Defined Network (MCDN) links. This feature is supported over ISDN BRI trunks in an MCDN environment, if NAS is equipped. It is not supported on ISDN BRI sets.
  • Page 136 The call is released if the calling party goes on hook once more. CDPC allows an operator, involved in an operator-assisted call from a Meridian 1, to automatically recall a station without having to re-dial it. TOBI allows a toll operator to break in to an established call.
  • Page 137 Toll Operator Call Back. This capability is supported transparently for ISDN BRI. The Malicious Call Trace enhancement allows a Meridian 1 to have Called Party Control on incoming calls when the Malicious Call Trace (MCT) feature is activated from a station, or when the Multifrequency Compelled (MFC) Idle Call Trace (IDCT) signal is sent.
  • Page 138 Page 124 of 492 Chapter 2 — Feature descriptions The tones and announcement feature allows a howler tone to be given to indicate that a 500/2500 terminal is off-hook. This capability is not applicable to ISDN BRI terminals. This feature also provides new intercept treatments upon the reception of some MFC signals.
  • Page 139 Flexible timers is not supported on ISDN BRI terminals. Calling Party DN allows the Meridian 1 to send to the Toll Office the calling-party customer DN and, if applicable, the calling-party DID DN for all outgoing calls. This capability is supported when the calling party is an ISDN BRI terminal.
  • Page 140 BRI terminal display is not updated. Intercept Computer Interface This feature allows the Meridian 1 to use an intercept (attendant assistance service) computer for storing and retrieving call messages. Calls to an absent tenant's DN using this feature are routed to a designated Intercept Position (ICP) DN.
  • Page 141 Page 127 of 492 Chapter 2 — Feature descriptions — From the ICP terminal; — Automatically when a TN is disabled or enabled by a maintenance overlay program. The Intercept Computer Interface is partially supported on ISDN BRI terminals, as explained below: —...
  • Page 142 MF sender and receiver card. Each forward signal sent to the Central Office is acknowledged by a backward signal. This feature also allows the Meridian 1 to request Calling Number Identification (CNI) information, to be shown on the originating terminal’s display.
  • Page 143 ISDN BRI terminals; however, some restrictions may apply to data calls. Advice of Charge for NUMERIS connectivity This feature provides the total cost for a call made from a Meridian 1 switch to the ISDN access designed for France (NUMERIS). The Meridian 1 to NUMERIS PSTN connectivity is implemented using ISDN packages PRI2 and IPRI.
  • Page 144 Page 130 of 492 Chapter 2 — Feature descriptions Message Registration (MR) and Periodic Pulse Metering (PPM) are both packaged under software package 101. Prior to the introduction of this feature, the method used to differentiate which feature was equipped was to check if the International Supplementary Features software package was equipped.
  • Page 145 Meridian 1 to New Zealand NEAX-61 ISDN PRI Connectivity This feature provides an ISDN Primary Rate Interface (PRI) between a Meridian 1 (SL-1) and New Zealand NEAX-61. The design in based on the international 30B + D PRI configuration. The NEAX-61 interface will support calls from ISDN BRI sets within the MCDN.
  • Page 146 This feature, based on the Message Registration feature, allows meters to be assigned to terminals, attendant consoles, trunk routes, and customers. This permits Meridian 1 customers to maintain accurate records of Central Office and DOD calls, for billing or administrative purposes. The Call Detail Recording (CDR) feature has been enhanced to record the PPM metering information.
  • Page 147 Page 133 of 492 Chapter 2 — Feature descriptions Meter recalls to the attendant and background terminal messaging uses the originating ISDN BRI CLID. Meter charge transfers associated with the activation of Hunt or Call Forward No Answer from an ISDN BRI terminal are not supported; the calling party is charged for the entire call.
  • Page 148 Page 134 of 492 Chapter 2 — Feature descriptions Digit Display to Same Attendant This improvement enables the attendant’s display to be updated with paged name to display paged name instead of answering name on the paging party when answered, and to make network Radio Paging show the same display information as in the standalone operation.

  • Page 149: Chapter 3 - Feature Packaging And Prerequisites

    Page 135 of 492 Chapter 3 — Feature packaging and prerequisites Introduction The Option 11C uses a series of software cartridges, each providing a number of features. Depending on your particular market, the features offered on any of the cartridges may vary. This following is a description of the ISDN BRI related feature packages and their prerequisites.

  • Page 150: Isdn Basic Rate Interface (Bri) Packages

    Page 136 of 492 Chapter 3 — Feature packaging and prerequisites Table 4 Application and package requirements Application Package Line Trunk Packet data 75 — PBXI (Note 1) Ð 145 — ISDN Ð 154 — PRI2 (Note 2) Ð (Note 2) 203 —...

  • Page 151: Isdn Bri Trunk Applications (Brit) Package

    Page 137 of 492 Chapter 3 — Feature packaging and prerequisites ISDN BRI Trunk applications (BRIT) package Option package 233 This package allows ISDN BRI Trunk Access application to be activated. Prerequisites ISDN BRI — Option package 216 This is the base package for ISDN BRI. ISDN BRI Line applications (BRIL) package Option package 235 This package allows the ISDN BRI Line application to be activated.
  • Page 152 Page 138 of 492 Chapter 3 — Feature packaging and prerequisites 553-3011-311 Standard 7.0 May 1999...

  • Page 153: Chapter 4 - Network Clocking

    This chapter describes digital network clocking as it applies to systems equipped with the ISDN BRI feature. Note: The Option 11 is a member of the Meridian 1 family of systems. References to Meridian 1 or Meridian 1 SL-1 in this chapter include the Option 11 system unless stated otherwise.

  • Page 154: Synchronization Methods

    Mesochronous mode by configuring the Clock Controller circuit cards to lock onto an external reference source. The above statement is true unless the Meridian 1 is used as a master in an independent/private network. An independent network has no digital links to a higher Node Category.
  • Page 155 Page 141 of 492 Chapter 4 — Network clocking Figure 12 Hierarchical Synchronization Primary Reference Source Stratum 1 nodes (clock derived directly from or controlled by Cesium clock) Stratum 2 nodes (i.e. Toll Offices) Stratum 3 nodes (i.e. Digital Central or End offices) Stratum 4 nodes (i.e.

  • Page 156: Stratum Levels

    Page 142 of 492 Chapter 4 — Network clocking Stratum Levels In a digital network, nodes are synchronized using a priority master/slave method. Digital nodes are ranked in Stratum levels 1 to 4. Each node is synchronized to the highest ranking node in its neighborhood with which it has a direct link.
  • Page 157 Page 143 of 492 Chapter 4 — Network clocking — When connecting two PBXs together (no CO connections), the most reliable PBX should be the Master. Reliability here refers to Dual CPU/Dual Clock, battery back-up or stratum level of the clock controller. —...
  • Page 158 Page 144 of 492 Chapter 4 — Network clocking In Example 2, there is no digital connection to the local exchange. For TIE lines between PBXs facilitated by a local exchange, clocking is derived from the PBX, not the local exchange. When a second Digital loop is available, it can be used as a Secondary Clock source in case the Primary Source fails.
  • Page 159 PBXs are connected as slaves. When a second Digital loop from the Meridian 1 which forms the hub of this network becomes available, it can be used as a Secondary Clock Source in case the Primary Source fails.
  • Page 160 Page 146 of 492 Chapter 4 — Network clocking In Example 4, a digital connection to the local exchange may exist (i.e. Loops X and Y). When a second Digital loop from the local exchange or Master M-1 becomes available, it can be used as a Secondary Clock Source in case the Primary Source fails.
  • Page 161 Page 147 of 492 Chapter 4 — Network clocking In Example 5, digital connections to the local exchange do exist. When a second Digital loop from the local exchange becomes available, it can be used as a Secondary Clock Source in case the Primary Source fails. Slaves can track on each other as a secondary source since the chances of both links to the local exchanges going down at the same time are minimal (very unlikely).
  • Page 162 PBX connected to it will track off the local exchange and will in turn be used as a clock source to other nodes. When a second Digital loop from the Master Meridian 1/SL-1 becomes available, it can be used as a Secondary Clock Source in case the Primary Source fails.
  • Page 163 Page 149 of 492 Chapter 4 — Network clocking In Example 7, the direct connection to the local exchange (without a MUX) should be used as a primary clock reference since there is the least amount of hardware involved. The MUX must pass the clock and not generate its own clock;...

  • Page 164: Option 11 Clock Controllers

    Page 150 of 492 Chapter 4 — Network clocking Option 11 clock controllers Digital trunking requires synchronized clocking so that a shift in one clock source will result in an equivalent shift of the same size and direction in all parts of the network.

  • Page 165: Free-Run (Non-Tracking)

    Page 151 of 492 Chapter 4 — Network clocking There are two stages to clock controller tracking: — tracking a reference, and — locked onto a reference. When tracking a reference, the clock controller uses an algorithm to match its frequency to the frequency of the incoming clock.
  • Page 166 Page 152 of 492 Chapter 4 — Network clocking 553-3011-311 Standard 7.0 May 1999...

  • Page 167: Chapter 5 - Isdn Bri Line And Packet Data Implementation

    Page 153 of 492 Chapter 5 — ISDN BRI line and packet data implementation Introduction This chapter describes Integrated Services Digital Network (ISDN) Basic Rate Interface (BRI) line and packet data implementation. Hardware requirements, installation procedures and software programming procedures for the Option 11 system are described.

  • Page 168: Isdn Bri Line Configuration Guidelines

    Page 154 of 492 Chapter 5 — ISDN BRI line and packet data implementation ISDN BRI line configuration guidelines The following recommendations should be considered when connecting terminals to DSLs: — The total number of physical terminations on an S/T DSL may not exceed eight.

  • Page 169: Dsl Configuration

    Page 155 of 492 Chapter 5 — ISDN BRI line and packet data implementation DSL configuration Digital subscriber loops connect the Option 11 to ISDN BRI terminals. A DSL consists of a cable connecting the ISDN BRI port to the cross-connect terminal.

  • Page 170: Line Powering Options

    Page 156 of 492 Chapter 5 — ISDN BRI line and packet data implementation — connect a maximum of two ISDN BRI terminals requiring B-channel transmission or one terminal using both circuit-switched voice and data to each DSL for a non-blocking configuration —...
  • Page 171 Page 157 of 492 Chapter 5 — ISDN BRI line and packet data implementation Figure 13 S/T digital subscriber loop wiring example for ISDN BRI lines Option 11 Stub RJ-45 Cross-connect Wall Jack terminal S/T DSL Non-reversing Modular Cord Maximum 10 m (33 ft) Non-reversing SILC Port Office Wiring...
  • Page 172 Page 158 of 492 Chapter 5 — ISDN BRI line and packet data implementation Cable characteristics Table 5 lists the parameters of the various cable types used in determining the S/T DSL configuration limits. The cables listed are those used for telephony wiring applications, and the characteristics listed are for Northern Telecom cable at 96 kHz and 20°...
  • Page 173 Page 159 of 492 Chapter 5 — ISDN BRI line and packet data implementation Point-to-point SILC DSL This configuration is shown in Figure 14. It represents the simplest type of bus configuration. The Point-to-Point bus provides the longest DSL length. Recommended rules: —...
  • Page 174 Page 160 of 492 Chapter 5 — ISDN BRI line and packet data implementation Table 6 Cable types and point-to-point SILC DSL lengths Maximum Gauge DSL length Cable type ft (m) Outside PIC 3640 (1110) Outside PIC 2590 (790) Outside PIC 1770 (540) Outside PULP 3280 (1000)
  • Page 175 — Use a 100 ¾ terminating resistor (A0378866) at the end of the DSL. — Terminate both ends of the DSL if the NT is not located at the end of the DSL. In this case the distance between the Meridian 1 and the DSL should not exceed 30 ft (9 m).
  • Page 176 Page 162 of 492 Chapter 5 — ISDN BRI line and packet data implementation Figure 15 Short passive SILC DSL Option 11 Modular Cable Terminating Cross-connect 10m (35 ft) maximum Resistor terminal AO378866 RJ-45 jacks S/T interface DSL length 553-7570.EPS 553-3011-311 Standard 7.0 May 1999...
  • Page 177 Page 163 of 492 Chapter 5 — ISDN BRI line and packet data implementation Table 7 Cable types and short passive SILC DSL lengths Maximum DSL Gauge length Cable type ft (m) Outside PIC 560 (170) Outside PIC 540 (165) Outside PIC 510 (155) Outside PULP...
  • Page 178 Page 164 of 492 Chapter 5 — ISDN BRI line and packet data implementation Extended passive SILC DSL This bus configuration is shown in Figure 16. The extended passive bus is designed to allow up to four terminals to be located a long distance from the SILC.
  • Page 179 Page 165 of 492 Chapter 5 — ISDN BRI line and packet data implementation Figure 16 Extended passive SILC DSL Option 11 Terminating Cross-connect Cross-connect Resistor terminal terminal RJ-45 AO378866 jacks Modular Cable 10m (35 ft) maximum Total terminal separation S/T interface DSL length 553-7571.EPS Option 11C...
  • Page 180 Page 166 of 492 Chapter 5 — ISDN BRI line and packet data implementation Table 8 Cable types and extended passive SILC DSL lengths Maximum DSL Total terminal Gauge length separation Cable type ft (m) ft (m) Outside PIC 2300 (700) 130 (40) Outside PIC 1640 (500)
  • Page 181 Page 167 of 492 Chapter 5 — ISDN BRI line and packet data implementation Branched passive SILC DSL This bus configuration is shown in Figure 17. The branched passive bus configuration uses the existing building wiring where the DSL is terminated in a telephone wiring closet.
  • Page 182 Page 168 of 492 Chapter 5 — ISDN BRI line and packet data implementation Figure 17 Branched passive SILC DSL Modular Cable 10m (35 ft) maximum RJ-45 jack Option 11 Terminating Cross-connect Resistor Branch 1 terminals AO378866 Total branch length Branch 2 RJ-45 jack...
  • Page 183 Page 169 of 492 Chapter 5 — ISDN BRI line and packet data implementation Table 9 shows the recommended maximum length of cable and branches at the end of the DSL. Calculate the length of the DSL, and the sum of the branches.

  • Page 184: Uilc Dsl Configuration

    Page 170 of 492 Chapter 5 — ISDN BRI line and packet data implementation UILC DSL configuration The UILC supports only point-to-point transmission. The maximum DSL length should not exceed 5 km (16,404 ft). Figure 18 shows a typical U interface DSL with an NT1 terminating the DSL and providing an S/T interface to an ISDN BRI terminal.
  • Page 185 Page 171 of 492 Chapter 5 — ISDN BRI line and packet data implementation The maximum length of the U DSL is determined by maximum loop loss. The maximum loss is 46 dB at 40 kH. However, to meet bit error rate performance of 10 or better in all cases, a maximum limit of 40 dB cable loss is recommended.
  • Page 186 Page 172 of 492 Chapter 5 — ISDN BRI line and packet data implementation Table 11 U DSL cable calculations Loss Gauge dB/km Length Loss Insulation type Item (dB/kft) km (kft) 3.3 (1.0) PULP 3.6 (1.1) 4.6 (1.4) 4.9 (1.5) 5.9 (1.8) PULP 6.3 (1.9)
  • Page 187 Page 173 of 492 Chapter 5 — ISDN BRI line and packet data implementation Figure 19 shows a DSL extension where the U interface is used to extend the loop by 5 km to an NT1 and from the NT1 it shows an S/T interface connecting two ISDN BRI terminals.

  • Page 188: Isdn Bri Terminals

    Page 174 of 492 Chapter 5 — ISDN BRI line and packet data implementation ISDN BRI terminals ISDN BRI terminals deemed compatible with the Option 11 system should comply with ANSI, ETSI NET-3, INS NET-64 or Numeris standards for ISDN BRI terminals. 1TR6 terminals are also supported through a 1TR6 to ETSI NET-3 converter box.

  • Page 189: Terminal Addressing And Service Profile Assignment

    Page 175 of 492 Chapter 5 — ISDN BRI line and packet data implementation Terminal addressing and service profile assignment ISDN BRI terminal addressing and Terminal Service Profile (TSP) assignment differs from the conventional approach where a Terminal Number (TN) identifies a terminal and its address and the protected line blocks in the database contain service related data for that terminal.
  • Page 190 Page 176 of 492 Chapter 5 — ISDN BRI line and packet data implementation Figure 21 shows the relationships of the physical and logical address components to the OSI model. Figure 21 Physical and logical address 5-components Terminal logical address Layer 1 = TSP (terminal service profile) (Network)
  • Page 191 Page 177 of 492 Chapter 5 — ISDN BRI line and packet data implementation Assigning the Terminal Endpoint Identifier (TEI) A TEI is associated with establishing the data link (layer 2) connection between a terminal and the network. The TEI is a terminal logical address that is used by the MISP to address a terminal during the exchange of layer 2 information messages with that terminal.
  • Page 192 Page 178 of 492 Chapter 5 — ISDN BRI line and packet data implementation Figure 22 Multiple logical terminals on one physical termination Digital Subscriber Loop (DSL) Terminating Resistor AO378866 Physical Termination Voice Circuit Switched Logical Logical Terminal Data Terminal Terminal Terminal number 2...
  • Page 193 Page 179 of 492 Chapter 5 — ISDN BRI line and packet data implementation Types of ISDN BRI terminals ISDN BRI terminals are divided into four categories based on layer 3 and layer 2 initialization procedures: — initializing terminal with dynamic end-point identification —...
  • Page 194 Page 180 of 492 Chapter 5 — ISDN BRI line and packet data implementation Before layer 3 terminal initialization can start, the terminal must have its SPID entered at the terminal. The TEI may be dynamic (the MISP automatically assigns an unassigned TEI) or static (the TEI in manually entered on the terminal key pad) Layer 3 initialization starts when the terminal transmits its SPID to the MISP using an information message.
  • Page 195 Page 181 of 492 Chapter 5 — ISDN BRI line and packet data implementation Figure 23 Terminal initialization and service profile assignment examples Service Profile A MISP SPID=2000 (USID=3) Automatically (TEI=82) Assigned Service Profile A Parameters Initializing terminal with dynamic TEI assignment TSP B assigned to: SPID=2000 USID...

  • Page 196: Packet Data Configuration

    Page 182 of 492 Chapter 5 — ISDN BRI line and packet data implementation Packet Data Configuration Refer to Figure 24 for a diagram of packet handling flow. D-channel packet data transmission D-channel packet data from each DSL is multiplexed by the line card (SILC or UILC) into two sets of four D-channels and placed onto two 64 kbps connections for transmission to the MISP.
  • Page 197 Page 183 of 492 Chapter 5 — ISDN BRI line and packet data implementation B-channel packet data transmission The B-channel packet data from each DSL is sent over the dedicated time slots to the PRI. A dedicated PRI B-channel handles the B-channel packet data between the PRI and the DPN-100 external packet handler.

  • Page 198: Hardware Requirements

    Page 184 of 492 Chapter 5 — ISDN BRI line and packet data implementation Figure 24 Packet handling flow diagram Internal to Meridian 1 External to the Meridian 1 Dedicated timeslots for Dedicated timeslot for B-channel packet data D-channel packet data...
  • Page 199 Note: This item is required for packet data implementation only. — ISDN BRI terminals — M5317TDX Meridian 1 set equipped with voice and data transmission options and a hands-free feature; supports B-channel and D-channel packet data. — M5000TD-1 ISDN Terminal Adapter provides a connection to an analog telephone and supports circuit-switched or packet data;...

  • Page 200: Ntbk22 Multi-Purpose Isdn Signaling Processor

    Page 186 of 492 Chapter 5 — ISDN BRI line and packet data implementation NTBK22 Multi-Purpose ISDN Signaling Processor (MISP) card The MISP card (NTBK22) is an Option 11 specific card (Options 21 through 71 use the NT6D73AA). It performs Data Link (Layer 2) and Network (Layer 3) processing associated with the OSI protocol.
  • Page 201 — execute instructions received from the MISP to configure and control the S/T interfaces. — provide channel mapping between ISDN BRI format (2B+D) and Meridian 1 system bus format. — multiplexes 4 D-channels onto one connection. — perform activation and deactivation of DSLs.
  • Page 202 Page 188 of 492 Chapter 5 — ISDN BRI line and packet data implementation SILCs required for non-blocking conditions Use the equations below to calculate the number of SILCs required to provide interfaces for the S/T type ISDN BRI terminals for non-blocking traffic conditions.

  • Page 203: Nt6D71 U Interface Line Card (Uilc)

    2B1Q line coding on the DSL. The Option 11 UILC card (NT6D71) is the same circuit card that is used by the rest of the Meridian 1 product line. It supports the OSI physical layer (layer 1) protocol. The UILC supports ANSI 2B1Q line encoding.
  • Page 204 Page 190 of 492 Chapter 5 — ISDN BRI line and packet data implementation To calculate the number of NT1s for non-blocking operation take the larger resulting number from the two equations below: S/T B-channel terminals ÷ 2 = NT1's Note: A physical terminal that can use two B-channels simultaneously such as circuit-switched voice and data, should be counted as two terminals for the purpose of this calculation.

  • Page 205: Ntak09/Ntak10/Ntbk50 Pri Card

    Page 191 of 492 Chapter 5 — ISDN BRI line and packet data implementation NTAK09/NTAK10/NTBK50 PRI card Note 1: This item is required for packet data implementation only. Note 2: Vintage NTBK50AA is required for Downloadable D-channel applications. When setting the timers for EuroISDN PRI2 loops in Overlay 73, the following settings are required: If the Option 11 is connected to a local exchange that supports CRC-4 multiframing, enter CRC-4 in response to the MFF prompt, enter yes in...

  • Page 206: Network Termination 1 (Nt1)

    Page 192 of 492 Chapter 5 — ISDN BRI line and packet data implementation Network Termination 1 (NT1) Stand-alone NT1 unit The stand-alone NT1 product, which is typically installed at the user's work area, consists of the following units: — the NT1 unit (NTBX80) —...

  • Page 207: Isdn Bri Terminals

    Page 193 of 492 Chapter 5 — ISDN BRI line and packet data implementation Cables Two cables are provided with the NT1 power supply unit: — a 178 mm (7 in.) cable (A0346581) for connecting between the power supply and the NT1 unit. —...

  • Page 208: Installing Isdn Bri Hardware

    Page 194 of 492 Chapter 5 — ISDN BRI line and packet data implementation Installing ISDN BRI Hardware Installation procedures The following lists the procedures that should be followed in the order shown to install ISDN BRI equipment for line and packet data implementation. The Option 11 should already be installed and operating before performing these procedures.

  • Page 209: Selecting The Card Slots

    Page 195 of 492 Chapter 5 — ISDN BRI line and packet data implementation Selecting the card slots Refer to Table 12 for ISDN BRI circuit card assignments in the main and expansion Option 11 cabinets. Note: Refer to the Option 11 Installation guide (553-3011-210) for instructions about adding a cabinet, if one is required.
  • Page 210 Page 196 of 492 Chapter 5 — ISDN BRI line and packet data implementation Figure 25 Shelf assignments, main cabinet IPE, SDI/DCH or Meridian Mail (12-port Meridian Mail also requires card slot 9) IPE, TDS/DTR, SDI/DCH, DTI/PRI, MISP (Note: On EMC systems, active CCs must be in slots 1-3) SYST CORE NTAK04 ac / dc...
  • Page 211 Page 197 of 492 Chapter 5 — ISDN BRI line and packet data implementation Figure 26 Shelf assignments, expansion cabinet IPE, Auxillary processors NTAK04 ac / dc or NTAK05 Power Supply 11 12 13 15 16 17 18 19 20 Pwr Sup IPE, Auxillary processors NTAK04...

  • Page 212: Installing The Misps

    Page 198 of 492 Chapter 5 — ISDN BRI line and packet data implementation Installing the MISPs The following procedure describes how to install MISPs into the Option 11 main cabinet. Refer to the Card slot allocation plan for the card slots assigned to MISP.

  • Page 213: Installing Silcs And Uilcs

    Page 199 of 492 Chapter 5 — ISDN BRI line and packet data implementation Installing SILCs and UILCs The following procedure describes how to install SILCs and UILCs into the Option 11 cabinets. Refer to the Card slot allocation plan for the card slot assignments.
  • Page 214 Page 200 of 492 Chapter 5 — ISDN BRI line and packet data implementation Figure 27 Silc line power options Jumper plug location NT6D70 SILC DSL Port 0 DSL Port 1 Faceplate DSL Port 2 DSL Port 3 J2 (not used) Backplane Storage for connector...
  • Page 215 Page 201 of 492 Chapter 5 — ISDN BRI line and packet data implementation BRTN Jumper plugs 553-7580.EPS Reverse power on the Tx and Rx leads. This option is used only in Japan and provides power (-48 or -40 V) on the Rx lead and battery return (BRTN) on the Tx lead to power the terminal.

  • Page 216: Installing Pri Hardware

    Page 202 of 492 Chapter 5 — ISDN BRI line and packet data implementation No power on the Tx and Rx leads. This option is used when the terminal is powered locally with an adapter provided with the terminal. It is also used when a SILC DSL is used for trunking. See Chapter 6 for trunking information.

  • Page 217: Connecting Isdn Bri Terminals

    Page 203 of 492 Chapter 5 — ISDN BRI line and packet data implementation Connecting ISDN BRI terminals To complete the installation of ISDN BRI equipment, the ISDN BRI terminals must be connected to the Option 11. This consists of: —...
  • Page 218 Page 204 of 492 Chapter 5 — ISDN BRI line and packet data implementation Figure 28 Connecting ISDN BRI terminals to the Option 11 Main cross-connect terminal Interemediate cross-connect terminal NE-A25B Cable SILC DSL (Office Wiring) To connector panel Modular Cable Terminating Wall Outlets Resistor...
  • Page 219 Page 205 of 492 Chapter 5 — ISDN BRI line and packet data implementation Connecting Option 11 cables to the cross-connect terminal The following procedure describes how to connect the cables from the Option 11 cabinet to the cross-connect terminal. Each card slot equipped with a SILC or UILC requires one NE-A25B 25-pair connector cable.
  • Page 220 Page 206 of 492 Chapter 5 — ISDN BRI line and packet data implementation Figure 29 Cable connectors in the main cabinet INTER J1 J2 J4 J5 J6 J7 J8 J9 J10 Grooves to route cables Retaining Connector retaining bar bar release (remove to install cables) NE-A25B cable...
  • Page 221 Page 207 of 492 Chapter 5 — ISDN BRI line and packet data implementation Figure 31 - Cable connectors in the second expansion cabinet INTER J21 J22 J24 J25J26J27J28 J29 J30 Grooves to route cables Retaining Connector retaining bar bar release (remove to install cables) NE-A25B cable to cross-connect terminal...
  • Page 222 Page 208 of 492 Chapter 5 — ISDN BRI line and packet data implementation Figure 32 SILC port designation label at the cross-connect terminal Tx-Tx+Rx+Rx- Tx-Tx+Rx+Rx- Tx-Tx+Rx+Rx- Tx-Tx+Rx+Rx- Tx-Tx+Rx+Rx- Tx-Tx+Rx+Rx- Tx-Tx+Rx+Rx- 553-7812.EPS Note: The pair designated Tx- Tx+ is the transmit pair. The pair designated Rx- Rx+ is the receive pair.
  • Page 223 Page 209 of 492 Chapter 5 — ISDN BRI line and packet data implementation To cross-connect SILC and/or UILC ports to the building wiring: Identify the card type (SILC or UILC) at the cross-connect terminal. Identify the transmit and receive connections for the SILC and the TIP and RING connections for the UILC from the label of the distribution strip.
  • Page 224 Page 210 of 492 Chapter 5 — ISDN BRI line and packet data implementation Table 13 SILC and UILC port assignments connectors at cross-connect terminal SILC UILC Connector Pin Card Port Port Number and Ports Signals Signals Wire Color Code 0 Tx- W-BL 0 Tx+...
  • Page 225 Page 211 of 492 Chapter 5 — ISDN BRI line and packet data implementation Figure 34 Cross-connecting a SILC port to the office wiring Cross connect terminal T- T+ R+ R- T- T+ R+ R- T- T+ R+ R- T- T+ R+ R- T- T+ R+ R- P or t 0 P or t 0 Port 1...
  • Page 226 Page 212 of 492 Chapter 5 — ISDN BRI line and packet data implementation Figure 35 Cross-connecting a UILC port to the office wiring Cross connect terminal Port 1 Port 1 Port 2 Port 3 Port 4 Cross connect wires or cable for DS1 10 11 12 13 14 15 16 17 18 19 20 DSL 2...
  • Page 227 Note: All terminals should comply with one of the following protocols: ETSI NET-3, INS NET-64, NUMERIS or ANSI standards for ISDN BRI terminals and be deemed compatible with Meridian 1. Contact your Northern Telecom representative for the latest list of compatible terminals.
  • Page 228 Page 214 of 492 Chapter 5 — ISDN BRI line and packet data implementation Table 14 S/T interface connector specification RJ45 Jack SILC Number Pin Signal Name Signal Name Power Source 3 No connection Power Source 3 No connection Tx + Rx + Rx + Tx +...
  • Page 229 Page 215 of 492 Chapter 5 — ISDN BRI line and packet data implementation Table 15 U interface connector specification RJ45 Jack UILC Number Pin Signal Name Signal Name Not used No connection Not used No connection Not used No connection Tip or Ring Tip or Ring Tip or Ring...
  • Page 230 Page 216 of 492 Chapter 5 — ISDN BRI line and packet data implementation Figure 36 Connecting the ISDN BRI terminal to the S/T interface Optional Power Adapter RJ-45 type RJ-45 type plug wall outlet DSL wiring WHT/ORG BLU/WHT WHT/BLU ORG/WHT GRN/WHT WHT/GRN...
  • Page 231 Page 217 of 492 Chapter 5 — ISDN BRI line and packet data implementation Figure 37 Connecting the ISDN network terminator to the U interface RJ-45 type wall outlet RJ - 45 type plug RJ - 45 type plug Modular cable maximum length 10 m U interface Office Wiring...
  • Page 232 Page 218 of 492 Chapter 5 — ISDN BRI line and packet data implementation Initializing a Northern Telecom M5317TDX terminal The following is an example of the steps to follow to initialize an M5317TDX terminal. Table 16 is a list of error codes that may appear during terminal initialization and their meaning.
  • Page 233 Page 219 of 492 Chapter 5 — ISDN BRI line and packet data implementation 18 Press YES for Enter datafill. 19 Press YES to delete existing datafill. 20 Press KEY# then enter on the keypad the key number you would like to program.
  • Page 234 Page 220 of 492 Chapter 5 — ISDN BRI line and packet data implementation Table 16 M5317TDX terminal error codes Error Code Number Description >>10<< S/T-loop sync loss and/or Frame sync loss >>11<< L1 transmit timer expired >>21<< Voice TEI removed by network >>22<<...

  • Page 235: Programming Procedures For Line Application And Packet Data Transmission

    Page 221 of 492 Chapter 5 — ISDN BRI line and packet data implementation Programming procedures for line application and packet data transmission You must configure the following components in the order listed below to configure ISDN BRI lines and/or packet data. Items required for packet data implementation only are noted.
  • Page 236 Page 222 of 492 Chapter 5 — ISDN BRI line and packet data implementation This step is optional since if no pad values are set the default values will be used. Define the pad settings if required. The digital pad provides gain or attenuation values to condition the level of the digitized transmission signal according to the network loss plan.
  • Page 237 Page 223 of 492 Chapter 5 — ISDN BRI line and packet data implementation Prompt Response Comment VIA NET LOSS 2Mb DTI digital TOLL office trunks Analog local exchange or WATS trunks Analog FEX trunks Analog DID trunks SATT Analog satellite TIE trunks Analog TOLL office trunks PRI2 2Mb PRI trunk...
  • Page 238 Page 224 of 492 Chapter 5 — ISDN BRI line and packet data implementation The following table shows pads codes and their values. Positive dB represents loss and negative dB represents gain. Pad codes and values code value +1.0 +2.0 +3.0 +4.0 +5.0...
  • Page 239 Page 225 of 492 Chapter 5 — ISDN BRI line and packet data implementation Configuring the LAPD protocol group A protocol group is added by using LD 27 and specifying its protocol group number. You also change its LAPD parameters or accept the default values. LAPD is a transmission protocol that specifies the transmission timers, the maximum number of retransmissions, the size of the data frame, and the number of negative acknowledgments before the system issues an alarm.
  • Page 240 Page 226 of 492 Chapter 5 — ISDN BRI line and packet data implementation Configuring a MISP A MISP is added to the system by specifying its card slot number using LD 27. You must also determine if the MISP will handle packet data and specify the PRI loop and channel numbers that will be used to transmit packet data to and from the packet handler.
  • Page 241 Page 227 of 492 Chapter 5 — ISDN BRI line and packet data implementation Configuring a SILC or UILC A new SILC or UILC is added by specifying its location, card type, and the MISP card slot that this card uses to transmit and receive signaling and D-channel packet data.
  • Page 242 Page 228 of 492 Chapter 5 — ISDN BRI line and packet data implementation Prompt Response Comment x...x Designator you assign to a DSL (example, BUILD2) The values for this prompt are: x...x=1 to 6 alphanumeric DSL designator CUST 0-31 Customer number CTYP SILC,UILC...
  • Page 243 Page 229 of 492 Chapter 5 — ISDN BRI line and packet data implementation Prompt Response Comment lll ch lll (0-159) = PRI2 loop number which is connected to the external packet handler or the Packet Switched Data Network. ch (1-30) = the PRI2 channel on which the dedicated B-channel dedicated connection from the DSL B-channel is terminated.
  • Page 244 Page 230 of 492 Chapter 5 — ISDN BRI line and packet data implementation Prompt Response Comment 0, 1, 2, 3 Departmental listed directory number (NO) The values for this prompt are: 0, 1, 2, 3=Departmental listed directory number specified in Customer Data Block Program LD 15 NO=No departmental listed directory number associated with the DSL...
  • Page 245 Page 231 of 492 Chapter 5 — ISDN BRI line and packet data implementation Prompt Response Comment PRID Defines the protocol to be used on the DSL Selection of the protocol ID is terminal dependent The values for this prompt are: 1=ANSI 2=ETSI NET-3 3=DMS...
  • Page 246 Page 232 of 492 Chapter 5 — ISDN BRI line and packet data implementation Prompt Response Comment Class of service access restrictions. The values for this prompt are: (ICDD) Internal Call Detail Recording Denied ICDA Internal Call Detail Recording Allowed (MRD) Message Restriction Denied Message Restriction Allowed...
  • Page 247 Page 233 of 492 Chapter 5 — ISDN BRI line and packet data implementation Configuring a TSP A TSP is added to a DSL by specifying the DSL location and its transmission characteristics as well as the class of service features for the terminals connected to the DSL.
  • Page 248 Page 234 of 492 Chapter 5 — ISDN BRI line and packet data implementation Prompt Response Comment SPID aaa...a <cr> Service profile ID Xaaa...a aaa...a = any combination of 1-20 alphanumeric characters. <cr> = Stops this prompt from being displayed again. A maximum of 8 valid SPIDs per TSP are allowed.
  • Page 249 Meridian 1 to the Terminal Adapter TRANS (NO) YES CLID and Connected Number Information Element (IE) are (not) passed from the Meridian 1 to the Terminal Adapter (S ), if presentation is restricted. Option 11C ISDN BRI Administration and Maintenance...
  • Page 250 Page 236 of 492 Chapter 5 — ISDN BRI line and packet data implementation Prompt Response Comment FEAT HTA/(HTD) Class of service features FNA/(FND) HTA = Hunt allowed (always assign if terminal has CWT SFA/(SFD) capability) CFTA/(CFTD) HTD = Hunt denied MWA/(MWD) FNA = Ca ll forward no answer allowed FBA/(FBD)
  • Page 251 Page 237 of 492 Chapter 5 — ISDN BRI line and packet data implementation Prompt Response Comment xxxx (0)-N xxxx = DN to be associated with the TSP. <cr> (0)-N = CLID entry, with N = CLID SIZE-1 (SIZE defined in LD 15).
  • Page 252 Page 238 of 492 Chapter 5 — ISDN BRI line and packet data implementation Configuring ISDN PRI trunk assignments for packet data Note: This step is required for packet data implementation only. The following describes how to configure ISDN PRI trunk assignments for packet data using LD 15, LD 17, LD 16 and LD 14 respectively.
  • Page 253 Page 239 of 492 Chapter 5 — ISDN BRI line and packet data implementation LD 17 — Prompt formats for defining configuration data block Prompt Response Comment CHG to define data TYPE Configuration data block. CEQU CE parameter change DLOP 1.5 Mb PRI PRI2 2.0 Mb PRI...
  • Page 254 Page 240 of 492 Chapter 5 — ISDN BRI line and packet data implementation Prompt Response Comment CNTL <cr> Changes to control timers LD 14 — Configuring the trunk data Prompt Response Comment Enter new trunk data TYPE Trunk type cc uu Card and unit CUST...

  • Page 255: Chapter 6 - Isdn Bri Trunk Implementation

    Page 241 of 492 Chapter 6 — ISDN BRI trunk implementation Note: ISDN BRI trunk access is not supported in North America. Introduction This chapter describes the implementation of the Integrated Services Digital Network (ISDN) Basic Rate Interface (BRI) trunk service, the associated equipment, installation procedures and software programming procedures for the Option 11 system.

  • Page 256: Isdn Bri Trunk Access

    ETSI NET-3 (EuroISDN), INS NET-64 (Japan D70), or Asia-Pacific protocols; refer to Figure Figure 39. — directly between two Meridian 1 PBXs; refer to Figure 40 and Figure 41. ISDN BRI QSIG connectivity is achieved through an MISP card and either S/T or U interfaces, using the SILC and UILC line cards respectively.

  • Page 257: Isdn Bri Local Exchange/Co/Didconnectivity

    Page 243 of 492 Chapter 6 — ISDN BRI trunk implementation ISDN BRI local exchange connectivity /CO/DID ISDN BRI Local Exchange connectivity is supported in markets equipped with local exchanges that conform to Numeris VN3, 1TR6, ETSI NET-3 (EuroISDN), INS NET-64 (Japan D70), or Asia-Pacific protocols. This connection is accomplished through the SILC line card, with the designated DSL configured in the Terminal Equipment (TE) Mode.
  • Page 258 Page 244 of 492 Chapter 6 — ISDN BRI trunk implementation The ISDN BRI DSL is connected to a Network Termination (NT1) device which is physically located on the same premises as the Option 11. The NT1 device connects to a local exchange that supports Numeris or 1TR6 protocol through a U interface.
  • Page 259 Page 245 of 492 Chapter 6 — ISDN BRI trunk implementation 1TR6 local exchange connectivity 1TR6 local exchange connectivity provides 2B+D connectivity to a local exchange that supports 1TR6 protocol via an S/T interface. The ISDN BRI 1TR6 local exchange connectivity provides the following basic call and supplementary services: Note: Support for any feature is dependent upon the terminal equipment being used.
  • Page 260 Page 246 of 492 Chapter 6 — ISDN BRI trunk implementation Numeris VN3 local exchange connectivity The Numeris local exchange connectivity provides 2B+D connectivity through an S/T interface to a local exchange that supports Numeris VN3 protocol. The ISDN BRI/Numeris VN3 local exchange connectivity provides the following basic call and supplementary services: —...
  • Page 261 Page 247 of 492 Chapter 6 — ISDN BRI trunk implementation Japan D70 (INS NET-64) local exchange connectivity The Japan D70 (INS NET-64) local exchange connectivity provides 2B+D connectivity through an S/T interface to a local exchange that supports the D70 protocol (D70 is the Japanese version of the INS NET-64 protocol).The ISDN BRI/Japan D70 local exchange connectivity provides the following basic call and supplementary services:...
  • Page 262 Independent State (Russia and the Ukraine), Denmark, Finland, Germany, Holland, Ireland, Italy, Norway, Portugal, Spain, Sweden, Switzerland, and the United Kingdom. The Meridian 1 on the EuroISDN connectivity provides the following call services, for the complying countries: — Basic call service —...
  • Page 263 Page 249 of 492 Chapter 6 — ISDN BRI trunk implementation Asia-Pacifc connectivity This Asia Pacific Connectivity provides interface between the Meridian 1 and Public Exchange/Central Offices in the following markets: This Asia Pacific Connectivity provides interface between the Meridian 1 and Public Exchange/Central Offices in the following markets: —...
  • Page 264 Page 250 of 492 Chapter 6 — ISDN BRI trunk implementation Note: in cases where several ISDN BRI trunks (and hence several DSLs) are configured on a route, if Channel Negotiation fails to yield an acceptable channel on any of these DSLs, it is not possible to use another channel on another DSL.

  • Page 265: Isdn Bri Mcdn Tie Trunk Connectivity

    Page 251 of 492 Chapter 6 — ISDN BRI trunk implementation ISDN BRI MCDN Tie trunk connectivity ISDN BRI TIE trunk connectivity may have three implementations. In the first configuration (refer to Figure 39), a Meridian Customer Defined Networking (MCDN) TIE trunk connection may be implemented by connecting two Meridian 1s to the BRI leased line through the local exchange by way of two SILC cards.
  • Page 266 (that supports 2B1Q line encoding). The S/T end is connected to the Meridian 1 Option 11 equipped with an SILC DSL interface in Terminal Equipment (TE) mode; the other end is connected to the other Meridian 1 equipped with a UILC DSL interface in the Network Termination (NT) mode.
  • Page 267 SILC, derive clock reference from the BRI TIE trunk connection or from other PRI/DTI/BRI connections if available. The Meridian 1 equipped with the UILC interface may be allowed to operate in free-run mode or derive the clock source from other PRI/DTI/BRI connections if available.
  • Page 268 Meridian 1s derive clock reference from the BRI TIE trunk connection or from any other PRI/DTI/BRI connections if available. The other Meridian 1 may be allowed to operate in free-run mode or derive the clock source from any other PRI/DTI/BRI connections if available.

  • Page 269: Isdn Bri Qsig Connectivity

    Page 255 of 492 Chapter 6 — ISDN BRI trunk implementation Non ISDN BRI device Non ISDN BRI Non ISDN BRI such as 2500 or digital Line Card Line Card type telephone ISDN/BRI ISDN/BRI terminal terminal SILC SILC Note 3 Note 3 Note 4 Clock...
  • Page 270 Page 256 of 492 Chapter 6 — ISDN BRI trunk implementation QSIG is oriented towards signaling and services that occur between peer-to-peer connectivity, that is, between two PBXs, between two Centrex, or between a PBX and a Centrex; the signaling for services would be exchanged across a “Q”...
  • Page 271 Page 257 of 492 Chapter 6 — ISDN BRI trunk implementation Figure 42 ISDN BRI TIE trunk connectivity Public Public Network Network ETSI ISDN BRI/PRI Third party (public access) ISDN BRI QSIG QSIG ISDN BRI/PRI ISDN BRI/PRI Option 11 Option 11 ISDN BRI ISDN BRI terminal equipment...

  • Page 272: Hardware Requirements

    Page 258 of 492 Chapter 6 — ISDN BRI trunk implementation Hardware Requirements Hardware requirements for ISDN BRI trunk applications are as follows: — MISP circuit card NTBK22 — Multi-Purpose ISDN Signaling Processor (Required for TIE and Local exchange connectivity) —...

  • Page 273: Ntbk22 Multi-Purpose Isdn Signaling Processor

    Page 259 of 492 Chapter 6 — ISDN BRI trunk implementation NTBK22 Multi-Purpose ISDN Signaling Processor (MISP) card The MISP card (NTBK22) is an Option 11 specific card. It performs Data Link (Layer 2) and Network (Layer 3) processing associated with the OSI protocol.

  • Page 274: Nt6D70Aa/Nt6D70Ba S/T Interface Line Card (Silc)

    -40 V International) are the same circuit cards that are used by the rest of the Meridian 1 product line. SILC circuit cards support the OSI physical layer (layer 1) protocol. The SILC is a globally accepted standard interface. The SILC card is required for MCDN TIE connectivity and Local exchange connectivity.

  • Page 275: Nt6D71 U Interface Line Card (Uilc)

    UILC card (NT6D71) is the same circuit card that is used by the rest of the Meridian 1 product line. UILC circuit cards support the OSI physical layer (layer 1) protocol. The UILC supports 2B1Q encoding. The UILC card is required for TIE trunk connectivity SILC to UILC as shown in Figure 40.

  • Page 276: Cables

    Page 262 of 492 Chapter 6 — ISDN BRI trunk implementation The stand-alone NT1 unit is a two-part molded housing 210 mm (8.27 in.) by 108 mm (4.25 in.), its depth tapering from about 50 mm (2 in.) to about 32 mm (1.25 in).

  • Page 277: Installing Bri Hardware

    Page 263 of 492 Chapter 6 — ISDN BRI trunk implementation Installing BRI hardware Installation procedures The following lists the procedures that should be followed in the order shown to install ISDN BRI equipment for a trunking configuration. The Option 11 should already be installed and operating before performing these procedures.
  • Page 278 Page 264 of 492 Chapter 6 — ISDN BRI trunk implementation Table 17 ISDN BRI card location ISDN BRI Circuit Card Main Cabinet Expansion Cabinet MISP Slots 1 through 9 — SILC not used as a clock Slots 1 through 9 Slots 11 through 30 reference SILC used as a clock...
  • Page 279 Page 265 of 492 Chapter 6 — ISDN BRI trunk implementation Figure 43 Shelf assignments, main cabinet IPE, SDI/DCH or Meridian Mail (12-port Meridian Mail also requires card slot 9) IPE, TDS/DTR, SDI/DCH, DTI/PRI, MISP (Note: On EMC systems, active CCs must be in slots 1-3) SYST CORE NTAK04 ac / dc...
  • Page 280 Page 266 of 492 Chapter 6 — ISDN BRI trunk implementation NTAK20BB—Stratum 4) may reside on the MISP circuit card. 553-3011-311 Standard 7.0 May 1999...
  • Page 281 Page 267 of 492 Chapter 6 — ISDN BRI trunk implementation Figure 44 Shelf assignments, expansion cabinet IPE, Auxillary processors NTAK04 ac / dc or NTAK05 Power Supply Pwr Sup 11 12 13 15 16 17 18 19 20 IPE, Auxillary processors NTAK04 ac / dc or NTAK05...

  • Page 282: Installing The Clock Controller On The Misp

    Page 268 of 492 Chapter 6 — ISDN BRI trunk implementation Installing the clock controller on the MISP The line cards associated with BRI DSLs used as references must be installed in the Main Cabinet. Clock controller installation guidelines — If the primary reference clock source is to come from a PRI or DTI, then the clock controller (CC) must reside as a daughter board on the DTI/PRI card.
  • Page 283 Page 269 of 492 Chapter 6 — ISDN BRI trunk implementation Note: Observe the LED on the faceplate of the MISP while performing the next step. Insert the MISP into the selected card slot and lock it in place. The LED should light, flash three times then remain lit to indicate that the MISP is operating correctly but is not configured and enabled.

  • Page 284: Installing Silcs And Uilcs

    Page 270 of 492 Chapter 6 — ISDN BRI trunk implementation Installing SILCs and UILCs The following procedure describes how to install SILCs and UILCs into the Option 11 cabinets. Refer to the Card slot allocation plan for the card slot assignments.
  • Page 285 Page 271 of 492 Chapter 6 — ISDN BRI trunk implementation Jumper plug location NT6D70 SILC DSL Port 0 DSL Port 1 Faceplate DSL Port 2 DSL Port 3 J2 (not used) Backplane Storage for connector unused DSL Port 4 jumper plugs DSL Port 5 DSL Port 6...

  • Page 286: Connecting Option 11 Cables To The Cross-Connect Terminal

    Page 272 of 492 Chapter 6 — ISDN BRI trunk implementation Connecting Option 11 cables to the cross-connect terminal The following procedure describes how to connect the cables from the Option 11 cabinet to the cross-connect terminal. Each card slot equipped with an SILC or UILC requires one NE-A25B 25-pair connector cable.
  • Page 287 Page 273 of 492 Chapter 6 — ISDN BRI trunk implementation Figure 45 Cable connectors in the main cabinet INTER J1 J2 J4 J5 J6 J7 J8 J9 J10 Grooves to route cables Retaining Connector retaining bar bar release (remove to install cables) NE-A25B cable to cross-connect terminal 553-7809.EPS...
  • Page 288 Page 274 of 492 Chapter 6 — ISDN BRI trunk implementation Figure 46 Cable connectors in the first expansion cabinet INTER J11 J12 J14 J15J16J17J18 J19 J20 Grooves to route cables Retaining Connector retaining bar bar release (remove to install cables) NE-A25B cable to cross-connect terminal 553-7810.EPS...
  • Page 289 Page 275 of 492 Chapter 6 — ISDN BRI trunk implementation Figure 47- Cable connectors in the second expansion cabinet INTER J21 J22 J24 J25J26J27J28 J29 J30 Grooves to route cables Retaining Connector retaining bar bar release (remove to install cables) NE-A25B cable to cross-connect terminal 553-7811.EPS...

  • Page 290: Cross-Connecting Dsls At The Cross-Connect Terminal

    Page 276 of 492 Chapter 6 — ISDN BRI trunk implementation Figure 48 SILC port designation label at the cross-connect terminal Tx-Tx+Rx+ Tx-Tx+Rx+ Tx-Tx+Rx+ Tx-Tx+Rx+ Tx-Tx+Rx+ Tx-Tx+Rx+ Tx-Tx+Rx+ Rx-0 Note: The pair designated Tx- Tx+ is the transmit pair. The pair designated Rx- Rx+ is the receive pair.
  • Page 291 Page 277 of 492 Chapter 6 — ISDN BRI trunk implementation Identify the trunk wiring facilities connected at the cross-connect terminal. Cross-connect the pins from the SILC or UILC to the trunk wiring facilities. Repeat this procedure for each DSL. Option 11C ISDN BRI Administration and Maintenance...
  • Page 292 Page 278 of 492 Chapter 6 — ISDN BRI trunk implementation Table 18 SILC and UILC port assignments connectors at cross-connect terminal SILC UILC Connector Pin Card Port Port Number and Ports Signals Signals Wire Color Code 0 Tx- W-BL 0 Tx+ BL-W 0 Rx-...
  • Page 293 Page 279 of 492 Chapter 6 — ISDN BRI trunk implementation For the Option 11 DSL in TE mode, the Tx and Rx pairs must be reversed as shown in Figure 52. Maintain the same polarity on the Tip and Ring pins as for line application.
  • Page 294 Page 280 of 492 Chapter 6 — ISDN BRI trunk implementation Figure 51 Cross-connecting a UILC port Cross connect terminal Port 0 Port 1 Port 0 Port 1 Port 2 Port 3 Port 4 Port 2 Port 3 Cross connect wires or Port 4 cable for DSL 1 Port 5...
  • Page 295 Page 281 of 492 Chapter 6 — ISDN BRI trunk implementation Figure 52 Connecting the ISDN network terminator to the U interface and to the S/T interface (in TE mode) Cross connect terminal Cross connect terminal Port 0 Tx+ Rx+ Tx+ Rx+ Tx+ Rx+ Port 0...

  • Page 296: Isdn Bri Trunk Software Programming

    Page 282 of 492 Chapter 6 — ISDN BRI trunk implementation ISDN BRI trunk software programming Various items must be configured in software to implement the ISDN BRI trunk feature. You must configure the following components in the order listed below to configure ISDN BRI trunks: Configure ISDN customer, using overlay 15.
  • Page 297 Page 283 of 492 Chapter 6 — ISDN BRI trunk implementation Configuring customer data Define an ISDN customer using the Customer Data Block (overlay 15). LD 15 — Prompt formats for defining an ISDN customer Prompt Response Comment NEW/CHG NEW for new customer or CHG for an existing customer TYPE Customer data block.
  • Page 298 Page 284 of 492 Chapter 6 — ISDN BRI trunk implementation Configure trunk pad tables, using overlay 73 (Optional step) Define the pad settings if required. This step is optional because if no pad values are configured the default values are used. The digital pad provides gain or attenuation values to condition the level of the digitized transmission signal according to the network loss plan.
  • Page 299 Page 285 of 492 Chapter 6 — ISDN BRI trunk implementation LD 73 —Configuring pad tables (continued) Prompt Response Comment The following prompts define the pad levels. The receiving pad code is r and the transmission pad code is t . These entries have the range 0-26.
  • Page 300 Page 286 of 492 Chapter 6 — ISDN BRI trunk implementation The following table shows pads codes and their values. Positive dB represents loss and negative dB represents gain. Pad codes and values code value (dB) 0.0 +1.0 +2.0 +3.0 +4.0 +5.0 +6.0...
  • Page 301 Page 287 of 492 Chapter 6 — ISDN BRI trunk implementation Configuring the LAPD protocol group A protocol group is added by using LD 27 and specifying its protocol group number. You also change its LAPD parameters or accept the default values. LAPD is a transmission protocol that specifies the transmission timers, the maximum number of retransmissions, the size of the data frame, and the number of negative acknowledgments before the system issues an alarm.
  • Page 302 Page 288 of 492 Chapter 6 — ISDN BRI trunk implementation Configuring ISDN BRI trunk route data block parameters Route data block parameters for the ISDN BRI Trunk access capability are configured using LD 16. LD 16 — Configuring ISDN BRI trunk route data block parameters Prompt Response Comment...
  • Page 303 Page 289 of 492 Chapter 6 — ISDN BRI trunk implementation Prompt Response Comment DCH interface type. (SL1) SL1 = Meridian SL-1 EURO EURO = EuroISDN D100 D100 = Meridian DMS-100 D250 D250 = Meridian DMS-250 ESS4 ESS4 = AT&T ESS#4 ESS5 ESS5 = AT&T ESS#5 S100...
  • Page 304 Page 290 of 492 Chapter 6 — ISDN BRI trunk implementation Prompt Response Comment CNTY (cnt’d.) Enter the country pertaining to the Asia Pacific interface. AUST Australian interface. CHNA China interface. HKNG Hong Kong interface. INDO Indonesia interface. JAPN Japan interface. MSIA Malaysia interface.
  • Page 305 Page 291 of 492 Chapter 6 — ISDN BRI trunk implementation Prompt Response Comment HNTN 0-9999 This prompt applies to APAC only if CPFXS = NO. 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.
  • Page 306 Page 292 of 492 Chapter 6 — ISDN BRI trunk implementation Prompt Response Comment MCTS Enable Malicious Call Trace signaling for AUST or TCNZ. - MCTM (0)-30 Malicious Call Trace request timer is defined in seconds. This is the disconnection delay which is used. It overrides T306 for calls to/from Malicious Call Trace capable sets (Australia only).
  • Page 307 Page 293 of 492 Chapter 6 — ISDN BRI trunk implementation Prompt Response Comment RCAP Remote D-Channel capabilities. Enter X followed by the option to remove the configured capability. This prompt is repeated until <cr> is entered. NCT = Network Call Trace RVQ, RVQ = Remote Virtual Queueing ND1 = Network Name Display 1...
  • Page 308 Page 294 of 492 Chapter 6 — ISDN BRI trunk implementation Table 19 Remote Capability Meanings for ISDN BRI routes Remote Meaning for Meaning for Meaning for Rerouting request capability Operation Coding Notification Informations None of the Not applicable Not sent Not processed when received following (nothing sent)
  • Page 309 Page 295 of 492 Chapter 6 — ISDN BRI trunk implementation Only one remote capability allows the QSIG Diversion configuration on an ISDN BRI route. This remote capability gathers the three following possibilities for the route: — coding of operations sent to the remote switch, which can be coded as either as Object Identifier or as Integer Value.
  • Page 310 Page 296 of 492 Chapter 6 — ISDN BRI trunk implementation Configuring an MISP An MISP is added to the system by specifying its card slot number using LD 27. LD 27 — Configuring an MISP Prompt Response Comment Add an ISDN BRI MISP TYPE MISP MISP...
  • Page 311 Page 297 of 492 Chapter 6 — ISDN BRI trunk implementation Configuring an SILC or UILC A new SILC or UILC is added by specifying its location, card type, and the MISP card slot that this card uses to transmit and receive signals. Note: You have an option of skipping this step and specifying the card type when you configure the DSL.
  • Page 312 Page 298 of 492 Chapter 6 — ISDN BRI trunk implementation Configuring a trunk DSL A DSL is added by specifying its port location and its DSL characteristics. A DSL port location specifies an SILC or UILC port that is connected to a DSL. LD 27 —...
  • Page 313 Page 299 of 492 Chapter 6 — ISDN BRI trunk implementation Prompt Response Comment MODE TE/NT The mode for the trunk DSL. TE is entered for Terminal Equipment, NT is used for Network Termination. See the Trunk configuration figures earlier in this chapter to determine the Mode to be set based on the configuration you are implementing.
  • Page 314 Page 300 of 492 Chapter 6 — ISDN BRI trunk implementation Prompt Response Comment ROUT 0-511 Route number for the trunk DSL. The specified route must match the ISDN BRI trunk type specified at the TKTP prompt. If the DSL is in the NET mode (MODE = NT in LD 27), the entered route must be NET side (SIDE = NET in LD 16).
  • Page 315 Page 301 of 492 Chapter 6 — ISDN BRI trunk implementation Prompt Response Comment YES/(NO) Configure B Channel 2. If REQ = NEW, and the default of NO is entered to this prompt, all parameters entered for B1 will be applied to B2, except the route member number will be an unused value.
  • Page 316 Page 302 of 492 Chapter 6 — ISDN BRI trunk implementation Configuring trunk clock reference source In the case where an ISDN BRI trunk is providing a reference clock source to the system clock controller, the Digital Data Block (overlay 73) must be modified as follows.
  • Page 317 Page 303 of 492 Chapter 6 — ISDN BRI trunk implementation Note: The items in the following table are only defined for systems that require 2 Mb DTI/PRI functionality. LD 73 — Configuring trunk clock reference source for 2.0 Mb PRI/DTI Prompt Response Comment...
  • Page 318 Page 304 of 492 Chapter 6 — ISDN BRI trunk implementation 553-3011-311 Standard 7.0 May 1999...

  • Page 319: Chapter 7 - Acceptance Testing

    Page 305 of 492 Chapter 7 — Acceptance testing Verifying ISDN BRI operation After ISDN BRI equipment has been installed and configured, you can visually inspect ISDN BRI cards to make sure that they are operating correctly by observing their LEDs: —...
  • Page 320 Page 306 of 492 Chapter 7 — Acceptance testing Refer to the ISDN BRI line and packet data implementation chapter of this guide for ISDN BRI terminal installation instructions: To perform acceptance testing using the configuration shown in Figure 53: —...
  • Page 321 Page 307 of 492 Chapter 7 — Acceptance testing Figure 53 ISDN BRI acceptance testing setup TDS/DTR MISP CPU Bus DS30X Bus UILC SILC SILC S/T Interface S/T Interface U Interface S/T Interface 553-7865.EPS Option 11C ISDN BRI Administration and Maintenance...
  • Page 322 Page 308 of 492 Chapter 7 — Acceptance testing Setting up ISDN BRI trunking - Local Exchange connectivity The ISDN BRI Local Exchange DSL is connected to a Network Termination (NT1) device, which is physically located on the same premises as the Option 11.

  • Page 323: Testing Isdn Bri Functions

    Page 309 of 492 Chapter 7 — Acceptance testing Testing ISDN BRI functions The following describes some ISDN BRI tests used to verify the operation of ISDN BRI features. The tests include basic call connections, voice and data transmission, and verification of features using ISDN BRI terminals. The tests are divided into: —...
  • Page 324 Page 310 of 492 Chapter 7 — Acceptance testing Call hold (not applicable to 1TR6) Call hold is used to place an active call on hold in order to answer an incoming call or place an outgoing call. After releasing an incoming or an outgoing call, you can retrieve the call on hold.
  • Page 325 Page 311 of 492 Chapter 7 — Acceptance testing ISDN BRI Call waiting Call waiting informs a ISDN BRI terminal user engaged in an active call that a call is waiting to be answered. A call setup message is sent to a DSL when both B-channels are busy and an incoming call is in progress.
  • Page 326 Page 312 of 492 Chapter 7 — Acceptance testing Call forward no answer Call forward no answer and second level forward no answer forwards an unanswered call to a call forward no answer DN after a predetermined number of rings. This feature is enabled at the TSP level when defining the BRI DN.
  • Page 327 Page 313 of 492 Chapter 7 — Acceptance testing Verify that the call was forwarded to the attendant by answering the call at the attendant console. The attendant console will display the call originating identification number and the notification of call redirection. Hang up at the call-originating ISDN BRI terminal to release the call connection.
  • Page 328 Page 314 of 492 Chapter 7 — Acceptance testing — The calling party ISDN BRI terminal must have the presentation (PRES) key enabled, which corresponds to PRES parameter set to YES, to allow the calling line identification number to be sent to the called terminal. It the PRES key on the terminal is disabled, which corresponds to PRES parameter set to NO, the calling line identification will not be sent to the called party terminal.
  • Page 329 Page 315 of 492 Chapter 7 — Acceptance testing Hunting Hunting allows calls that encounter a busy condition at the original call destination to be automatically routed to a different destination in a hunt chain. Hunting continues along a predetermined sequence of DNs in a hunting group until an idle ISDN BRI or non-ISDN terminal DN is found to answer the call or until the maximum number of hunt steps is exhausted.
  • Page 330 Page 316 of 492 Chapter 7 — Acceptance testing Specify the HUNT parameter DNs when configuring the DSL by using Service Change BRI Program LD 27. These hunt parameter DNs specify the members of a hunting chain. Refer to the ISDN BRI line and packet data implementation chapter of this guide in DSL configuration procedures.

  • Page 331: Circuit-Switched Data Calls

    Page 317 of 492 Chapter 7 — Acceptance testing Circuit-switched data calls A circuit-switched data call can be established between two data terminals over a B-channel. The call is set up the same way as a voice call. You can dial a call using the ISDN BRI terminal key pad or keyboard depending on the type of ISDN BRI terminal used.

  • Page 332: Packet Data Transmission

    Page 318 of 492 Chapter 7 — Acceptance testing You may wish to repeat this test on several terminals including both intelligent and dumb terminals. Packet data transmission A packet data call can be established between two data terminals over a B-channel or a D-channel.
  • Page 333 Page 319 of 492 Chapter 7 — Acceptance testing To perform a B-channel packet data transmission test: From a ISDN BRI B-channel packet data terminal, dial another local or a remote ISDN BRI packet data terminal and establish an active call connection. After the call originating ISDN BRI terminal receives an acknowledgment message that the receiving ISDN BRI terminal is ready, the call originating ISDN BRI terminal can start transmitting...

  • Page 334: Testing Isdn Bri Trunk Connectivity

    Page 320 of 492 Chapter 7 — Acceptance testing Testing ISDN BRI trunk connectivity Perform the following procedure to test an ISDN BRI trunk DSL. Set up the ISDN trunk test configuration to be used, as described previously in this chapter. Place a call across the ISDN BRI trunk.

  • Page 335: Chapter 8 - Service Changes And Maintenance

    Page 321 of 492 Chapter 8 — Service changes and maintenance Introduction This chapter describes how to administer the Option 11 ISDN BRI feature and how to identify and clear faults related to it. It includes ISDN BRI equipment replacement procedures. Before proceeding you should have a basic knowledge of the Option 11 ISDN BRI feature (described in this guide) to be able to administer it.
  • Page 336 Page 322 of 492 Chapter 8 — Service changes and maintenance Table 20 Maintenance commands Command Description Program DIS CC x Disable system clock controller (0 or 1) LD 60 DISC BRIL c Disables the ISDN BRI line application on MISP LD 32 DISC BRIT c Disables the ISDN BRI trunk application on the...
  • Page 337 Page 323 of 492 Chapter 8 — Service changes and maintenance Table 20 Maintenance commands Command Description Program ENLC BRIL c Enables the ISDN BRI line application on MISP c LD 32 ENLC c Enables the card in slot c LD 32 ENTS c dsl# Set the ISDN BRI trunk on card c dsl# in test...
  • Page 338 Page 324 of 492 Chapter 8 — Service changes and maintenance Table 20 Maintenance commands Command Description Program PERR c Print the error log for the MISP or ISDN BRI LD 32 card c PLOG c dsl# Print the protocol log for the ISDN BRI trunk on LD 32 card c dsl# PMES c dsl#...
  • Page 339 Page 325 of 492 Chapter 8 — Service changes and maintenance Table 20 Maintenance commands Command Description Program TEIT c dsl# Performs TEI test on card c dsl# LD 30 TRCK aaa Set clock controller tracking to primary, secondary or free run XCON0 Performs loopback test from the MISP to an LD 45...

  • Page 340: Misp And Silc/Uilc Message Monitoring Commands

    Page 326 of 492 Chapter 8 — Service changes and maintenance MISP and SILC/UILC message monitoring commands Link Diagnostic Overlay Program 48 (LD 48) is used to monitor and print messages sent and received by the MISP, SILC, and UILC cards. These commands are used to monitor ISDN BRI activity during normal system operation and to facilitate system maintenance.

  • Page 341: Changing, Removing And Printing An Lapd Protocol Group

    Page 327 of 492 Chapter 8 — Service changes and maintenance Changing, removing and printing an LAPD protocol group The following table gives the prompts and responses used to change, remove and print LAPD protocol groups. LD 27— Changing a protocol group Prompt Response Comment...
  • Page 342 Page 328 of 492 Chapter 8 — Service changes and maintenance Removing an LAPD protocol group You can remove a previously configured LAPD protocol group that is not currently assigned to a DSL. If a protocol group is assigned to a DSL, you must delete the DSL before removing the protocol group.

  • Page 343: Changing, Removing And Printing An Misp

    Page 329 of 492 Chapter 8 — Service changes and maintenance Changing, removing and printing an MISP Changing an MISP You can change voice and data handling status of an MISP. You can remove packet data handling from an MISP or change the PRI card slot and channel assigned for packet data transmission.
  • Page 344 Page 330 of 492 Chapter 8 — Service changes and maintenance Prompt Response Comment 1-23 PRI 1.5 Mb (1-23) or PRI 2 Mb (1-30) channel number 1-30 This channel carries B -channel packet data. To change this parameter, first disable the MISP. This prompt appears only if you selected DCH or BDCH for the PH prompt.

  • Page 345: Changing, Removing And Printing An Silc Or Uilc

    Page 331 of 492 Chapter 8 — Service changes and maintenance Changing, removing and printing an SILC or UILC Changing an SILC or UILC You can change a card type and the MISP card slot number with which the SILC or UILC is associated. Before changing the SILC or UILC, you must disable the card by executing the DISC c command in Diagnostic Program LD 32.

  • Page 346: Changing Or Removing A Dsl

    Page 332 of 492 Chapter 8 — Service changes and maintenance LD 27 — Removing an SILC or UILC Prompt Response Comment Remove an SILC or UILC line card TYPE CARD SILC or UILC line card 1-20 Card slot location The values for this prompt are1-20 Remove any DSLs that are configured for this line card before removing the line card.
  • Page 347 Page 333 of 492 Chapter 8 — Service changes and maintenance LD 27 — Changing a line DSL Prompt Response Comment Change a DSL TYPE cc dsl# DSL location The values for this prompt are: cc (card)=1-20 dsl# (DSL number)=0-7 x...x,<cr>...
  • Page 348 Page 334 of 492 Chapter 8 — Service changes and maintenance Prompt Response Comment B1CT VCE DTA PMD B-channel 1 call type XVCE XDTA The values for this prompt are: XPMD VCE=Adds circuit switched voice. DTA=Adds circuit switched data PMD=Adds packet mode data (B-channel packet data must have been specified in the MISP configuration procedures ).
  • Page 349 Page 335 of 492 Chapter 8 — Service changes and maintenance Prompt Response Comment LTEI n1 n2 m <cr> Note: A response to this prompt is only required for packet data implementation. The Logical Terminal Endpoint Identifier(LTEI) is used to address D-channel packet data terminals. LTEI consists of two components: n1 and n2 = Logical Terminal Identifier (LTID) m = Static Terminal Identifier (TEI)
  • Page 350 Page 336 of 492 Chapter 8 — Service changes and maintenance Prompt Response Comment n...n Flexible external call CFNA directory number Xn...n Enter a directory number from 4 to 13 digits long. Enter Xn...n to delete the parameter. HUNT n...n Hunt directory number Xn...n Enter a directory number from 4 to 13 digits long.
  • Page 351 Page 337 of 492 Chapter 8 — Service changes and maintenance LD 27 — Changing a line DSL (continued) Prompt Response Comment TGAR 0-31 Trunk group access restriction NCOS 0-99 Network class of service (UNR) TLD SRE Class of service access restrictions FRE CUN CTD The values for this prompt are: FR1 FR2...
  • Page 352 Page 338 of 492 Chapter 8 — Service changes and maintenance LD 27 — Changing a trunk DSL Prompt Response Comment Changing a DSL TYPE c dsl# DSL location The values for this prompt are: cc (card)=1-20 dsl# (DSL number)=0-7 APPL BRIT,BRIE, ISDN BRI trunk application...
  • Page 353 Page 339 of 492 Chapter 8 — Service changes and maintenance Prompt Response Comment CLOK YES/(NO) Whether this trunk DSL is provisioned for clock source. The SILC must be residing in slot 1-10 in the main cabinet. This prompt appears if the following conditions are met: - the card type is SILC - the DSL# is 0 or 1 - the trunk DSL has been defined as TE mode...
  • Page 354 Page 340 of 492 Chapter 8 — Service changes and maintenance Prompt Response Comment Class of Service options. Possible inputs are as follows: (UNR)=Unrestricted TLD=Toll denied SRE=Semi-restricted FRE=Fully restricted CUN=Conditionally unrestricted CTD=Conditionally toll denied FR1=Fully restricted class 1 FR2=Fully restricted class 2 (APN)=ACD priority not required APY=ACD priority required MRA = Message Registration Allowed (assigning...
  • Page 355 Page 341 of 492 Chapter 8 — Service changes and maintenance Prompt Response Comment Class of Service options. If TKTP is no longer TIE, CLS will be set to UNR. APN/APY will remain the same as before. Possible inputs are as follows: (UNR)=Unrestricted TLD=Toll denied SRE=Semi-restricted...
  • Page 356 Page 342 of 492 Chapter 8 — Service changes and maintenance LD 27 — Printing a DSL Prompt Response Comment Print an ISDN BRI component TYPE cc dsl#, DSL information The values for this prompt are: <cr> cc dsl#=Prints information for the specified dsl# on card cc=Prints information for all DSLs on the specified card <cr>=Prints the data for all DSLs in the system DATE...

  • Page 357: Changing, Removing And Printing A Tsp

    Page 343 of 492 Chapter 8 — Service changes and maintenance LD 27 — Removing a DSL Prompt Response Comment Remove an ISDN BRI component TYPE cc dsl# DSL location The values for this prompt are: cc (card)=1-20 dsl# (DSL location)=0-7 Changing, removing and printing a TSP Changing a TSP You can change the characteristics of a TSP on a DSL by specifying the DSL...
  • Page 358 Page 344 of 492 Chapter 8 — Service changes and maintenance LD 27 — Changing a TSP Prompt Response Comment Change TSP TYPE cc dsl# DSL location The values for this prompt are: cc (card)=1-20 dsl# (DSL location)=0-7 The DSL must have been configured using the DSL configuration procedures.
  • Page 359 Page 345 of 492 Chapter 8 — Service changes and maintenance Prompt Response Comment n...n,Xn...n, Directory number to be associated with TSP <cr> The values for this prompt are: n...n=Adds a 4 to 7-digit directory number Xn...n=Removes a 4 to 7 digit directory number <cr>=Stops this prompt from being displayed again This prompt is repeated until <cr>...
  • Page 360 Page 346 of 492 Chapter 8 — Service changes and maintenance Prompt Response Comment FEAT HTA (HTD) FNA Class of service features (FND) SFA The values for this prompt are: (SFD) CFTA HTA=Hunt allowed (always assign if terminal does have (CFTD) MWA CWT capability) (MWD) FBA...
  • Page 361 Page 347 of 492 Chapter 8 — Service changes and maintenance Removing a TSP You can remove a TSP from a DSL by specifying the DSL location and the user service identifier or you can remove all TSPs from a DSL by entering ALL for the USID prompt.
  • Page 362 Page 348 of 492 Chapter 8 — Service changes and maintenance Printing a TSP You can print the configuration information for a TSP based on characteristics such as user service identifier, service profile ID, and directory number. LD 27 — Printing a TSP Prompt Response Comment...

  • Page 363: Isolating And Correcting Faults

    Page 349 of 492 Chapter 8 — Service changes and maintenance Isolating and correcting faults Newly installed ISDN BRI equipment Problems that occur during the installation of an entire system with ISDN BRI equipment are usually caused by: — Improperly installed cards —...
  • Page 364 Page 350 of 492 Chapter 8 — Service changes and maintenance Table 22 ISDN BRI equipment problems Symptoms Diagnosis Solution Go to Procedure 8-1 of MISP fault Red LED on the MISP is The MISP is faulty, has permanently lit. not been configured, or is isolation and correction in this chapter disabled.
  • Page 365 Page 351 of 492 Chapter 8 — Service changes and maintenance Symptoms Diagnosis Solution Calls cannot be placed or The DSLs incorrectly Go to Procedure 8-7 of S ILC or UILC received on some DSLs configured, not fault isolation and correction in this on a particular line card.

  • Page 366: Misp Fault Isolation And Correction

    Page 352 of 492 Chapter 8 — Service changes and maintenance MISP fault isolation and correction The MISP provides a communication interface between the CPU and the peripheral devices. It processes the signaling information received on the D-channels from the DSLs. These D-channels may also carry packet data that the MISP separates from signaling information and forwards to the packet handler.
  • Page 367 Page 353 of 492 Chapter 8 — Service changes and maintenance If mm is greater than 0, it indicates disabled connections. The disabled connections may indicate faulty line cards. Go to Procedure 8-6. If the response is c:MISP LOOP DISABLED RESPONDING MISP c MAN DSBL the MISP card slot is disabled but the MISP is responding.
  • Page 368 Page 354 of 492 Chapter 8 — Service changes and maintenance FATAL ERROR - when the MISP has a serious problem SHARED RAM TEST FAILED - when the card has a memory problem OVERLOAD - when the card is faulty and it experiences an overload RESET THRESHOLD - when the card is faulty and reaches the specified threshold STUCK INTERRUPT - when the MISP has hardware failure and the...
  • Page 369 Page 355 of 492 Chapter 8 — Service changes and maintenance If the response is: c:MISP LOOP APPLICATION NOT CONFIGURED the application is not configured for the specified MISP. If the response is: c:MISP LOOP DISABLED NOT RESPONDING the application status is not displayed because the MISP running the application is disabled or faulty and is not responding.
  • Page 370 Page 356 of 492 Chapter 8 — Service changes and maintenance Procedure 8-2: Performing the MISP self-test If the MISP status indicates that the MISP is faulty, you should conduct the self-test to verify that this MISP is actually faulty before replacing it. To start the self-test, follow the steps below: Log-in on the maintenance terminal and load overlay program 32 (LD 32).
  • Page 371 Page 357 of 492 Chapter 8 — Service changes and maintenance You can perform two types of MISP loopback tests. These are: — MISP loopback at a DSL interface as described in Procedure 8-3 — MISP loopback at the SILC or UILC DS30X bus interface as described in Procedure 8-4 Procedure 8-3: MISP loopback at a DSL interface The loopback at a DSL interface checks the continuity of the D-channel...
  • Page 372 Page 358 of 492 Chapter 8 — Service changes and maintenance To start the loopback test: Log-in on the maintenance terminal and load overlay program 45 (LD 45). Select test condition: Enter XCON 0 and press the Enter key if you wish to perform only one loopback test.
  • Page 373 Page 359 of 492 Chapter 8 — Service changes and maintenance Check the test results. The result is automatically displayed if you specified XCON 0 test conditions, otherwise you must specify XSTA or XSTP with the test TAG number to check the status. XSTA gets the status of the manual continuity test and XSTP stops the manual continuity test.
  • Page 374 Page 360 of 492 Chapter 8 — Service changes and maintenance Figure 55 MISP loopback at the SILC or UILC peripheral bus interface Pattern Generator MISP Pattern Detector UILC U Interface SILC S/T Interface D-channel 553-7867.EPS Before you can start loopback testing at the SILC or UILC, you must disable the card you want to test.
  • Page 375 Page 361 of 492 Chapter 8 — Service changes and maintenance Select test conditions Enter XCON 0 and press the Enter key, if you wish to get only one loopback test. Enter one test period shown in XCON H 0-182, M 0-59, S 0-60 and press the Enter key to select continuous loopback testing for a selected time span where H 0-182 is 0 to 182 hours, M 0-59 is 0 to 59 minutes, and S 0-60 is 0 to 50 seconds.
  • Page 376 Page 362 of 492 Chapter 8 — Service changes and maintenance If the loopback continuity test passes and the MISP loopback test failed, the problem may be in the line card. If the loopback continuity test fails, the problem may be between the MISP and the line cards.
  • Page 377 Page 363 of 492 Chapter 8 — Service changes and maintenance The following steps are used to perform the remote loopback test for a ISDN BRI trunk DSL provisioned as a MCDN Tie configuration. Performing the ISDN BRI trunk remote loopback test Log in on the maintenance terminal and load overlay 32 (type in LD 32).

  • Page 378: Silc Fault Isolation Or Uilc Fault Isolation And Correction

    Page 364 of 492 Chapter 8 — Service changes and maintenance Take the far-end ISDN BRI trunk DSL out of remote loopback mode by entering the DSRB c dsl# command, and pressing the ENTER key. The the far-end and near-end ISDN BRI trunk DSLs are placed in the test mode.
  • Page 379 Page 365 of 492 Chapter 8 — Service changes and maintenance To obtain the card status: Log-in on the maintenance terminal and load overlay program 32 (LD 32). Type STAT c and press the Enter key, where c is the card slot number.
  • Page 380 Page 366 of 492 Chapter 8 — Service changes and maintenance Example: SW DSLL2L1D— CHANNELCLK 00 = UNIT 00 = IDLELINEESTAUP 01 = UNIT 01 = IDLETRNKESTAUP ESTASREF (TE) 02 = UNIT 02 = IDLELINEESTADOWN 03 = UNIT 03 = UNEQ 04 = UNIT 04 = UNEQ 05 = UNIT 05 = UNEQ 06 = UNIT 06 = DSBLTRNKDSBLUNEQRLS(NT)
  • Page 381 Page 367 of 492 Chapter 8 — Service changes and maintenance Table 24 DSL Layer 2 status in the MISP MISP _state Description Comments NTAN DSL is not assigned to an DSL is not properly configured. Refer to the Administration section MISP.
  • Page 382 Page 368 of 492 Chapter 8 — Service changes and maintenance Table 25 DSL Layer 1 status in the line card LC_ state Description Comments UNEQ Not equipped. DSL is not configured. Refer to the DSL configuration procedures to DSL is disabled. configure the DSL.
  • Page 383 Page 369 of 492 Chapter 8 — Service changes and maintenance Procedure 8-7: Checking the DSL status If the card status shows that some of the DSLs on the card are undefined, unequipped, disabled, or unable to send a message to the MISP, you can check the individual DSLs to obtain more specific data on its state by following the steps below: To check the status:...
  • Page 384 Page 370 of 492 Chapter 8 — Service changes and maintenance Procedure 8-8: Performing the SILC or UILC self-test If the card or DSL status indicates that the SILC or UILC is faulty, you should conduct a self-test to verify that the SILC or UILC is actually faulty before you replace it.

  • Page 385: Replacing Isdn Bri Cards

    Page 371 of 492 Chapter 8 — Service changes and maintenance Replacing ISDN BRI cards The following procedures describe how to remove and replace defective cards, verify the operation of ISDN BRI equipment, and package and ship the defective cards to an authorized repair center. Removing and replacing the MISP The MISP can be removed and inserted without turning off the power.

  • Page 386: Removing And Replacing The Silc Or Uilc

    Page 372 of 492 Chapter 8 — Service changes and maintenance At the > prompt in LD 32, type ENLC c and press the Enter key to enable the MISP. If the Dis LED on the MISP extinguishes, the MISP is functioning correctly and is ready to process calls.

  • Page 387: Verifying Operation

    Page 373 of 492 Chapter 8 — Service changes and maintenance At the > prompt in LD 32 program, type ENLC c and press the Enter key to enable the card. If the red LED on the card extinguishes, it is functioning correctly and is ready to process calls.

  • Page 388: Testing And Troubleshooting Isdn Bri Terminals

    Isolating switch problems Run the LD32 diagnostic program for the Meridian 1 switch. Check for error and location codes in the diagnostic output. If the codes indicate a faulty component, replace it. Refer to the “Replacing ISDN BRI cards”...
  • Page 389 Page 375 of 492 Chapter 8 — Service changes and maintenance Clearing error codes Perform the following steps if the telephone displays error codes after initialization. After each step, check the display. If an error code persists, go to the next step. If the static X.25 TEIs in the telephone and the network do not match, datafill the telephone TEIs manually.

  • Page 390: Verifying A New M5209T Terminal Installation

    Page 376 of 492 Chapter 8 — Service changes and maintenance Verifying a new M5209T terminal installation Procedures are provided for the following tests: • Running a self-test • Running a panel test • Making a test voice call • Making a test data call (applies to the M5209TDp and M5209TDcp models only) •...
  • Page 391 Page 377 of 492 Chapter 8 — Service changes and maintenance Running a panel test Press the Hold and Rls keys simultaneously until the following main menu is displayed: MAIN MENU CONFIG Press . The following prompt is displayed: ENTER PASSWORD Dial 4736 (ISDN) and press #.
  • Page 392 Page 378 of 492 Chapter 8 — Service changes and maintenance Press each feature/line key. As you press each key, a diamond appears on the associated feature/line indicator. When you press the last indicator, a diamond does not appear. Instead, the following message is displayed: CONFIGURATION MENU EXIT Note any problems that you encountered during the test, and refer to...

  • Page 393: Troubleshooting The M5209T

    Page 379 of 492 Chapter 8 — Service changes and maintenance Press to select the desired display language. Press The following message is displayed: MAIN MENU EXIT Troubleshooting the M5209T Trouble conditions may be reported by the telephone user (customer report), by way of automatic routine tests, or during installation procedures.
  • Page 394 Page 380 of 492 Chapter 8 — Service changes and maintenance The NT1 is functioning properly. Whether the NT1 is a stand-alone or rack-mount model, both types are functioning properly when the LED status indicators appear as summarized below: Status Indicator LED light Power U-sync...

  • Page 395: Isdn Bri Messages

    Page 381 of 492 Chapter 8 — Service changes and maintenance Problems with the set components Problems with the set components may include: • the keys are not responding, or responding improperly; • the feature key indicators are not functional •...

  • Page 396: Basic Rate Interface Messages (Brixxx)

    Page 382 of 492 Chapter 8 — Service changes and maintenance Basic Rate Interface messages (BRIxxx) The following messages are printed on demand by using SETM MISP <card#> MNT command in Link Diagnostic Program LD 48. By using RSET MISP <card#> MNT command in Link Diagnostic Program LD 48, you stop printing these messages.
  • Page 397 Page 383 of 492 Chapter 8 — Service changes and maintenance BRI102 MISP sent DSL update message. This message consists of one word that indicates the DSL status followed by the time when the status was printed. The possible status conditions are: No error Invalid DSL address Forced disconnect has timed out...
  • Page 398 Page 384 of 492 Chapter 8 — Service changes and maintenance BRI104 MISP sent DSL status message. The first number after the address displays the new DSL status message, the second number displays the reason for the change of status, and the third number displays the time when the status was printed.
  • Page 399 Page 385 of 492 Chapter 8 — Service changes and maintenance BRI105 MISP sent DSL B-channel status message. BRI107 MISP received line card audit message. BRI108 MISP received DSL audit message. BRI109 MISP received line card status audit message. BRI110 MISP received line card B-channel status audit message.
  • Page 400 Page 386 of 492 Chapter 8 — Service changes and maintenance DSL 0 transceiver failure DSL 1 transceiver failure DSL 2 transceiver failure DSL 3 transceiver failure DSL 4 transceiver failure DSL 5 transceiver failure DSL 6 transceiver failure DSL 7 transceiver failure BRI201 DSL reports layer 1 status.
  • Page 401 Page 387 of 492 Chapter 8 — Service changes and maintenance For UILCs in terminal equipment (TE) mode, the possible status conditions can be: U interface transceiver failure Physical (layer 1) is activated successfully Deactivation was requested from far end Physical (layer 1) is loosing synchronization Physical (layer 1) is in the process of being activated Physical (layer 1) failed to get established...
  • Page 402 Page 388 of 492 Chapter 8 — Service changes and maintenance B1, B2 0 B-channel disabled B-channel enabled Framing 0 Multi-framing disabled Multi-framing enabled Activation0 Waiting to be activated Automatically activated BRI203 Line card report for query message available. BRI204 Line card responds to terminal equipment query message.
  • Page 403 Page 389 of 492 Chapter 8 — Service changes and maintenance BRI314 Downloading Layer 3 tables to the MISP failed. Default tables in the MISP will be used. The following messages are printed automatically as they occur. BRI800 The MISP being enabled or disabled is not present in network shelf. BRI801 Dedicated connection between the MISP and the line card cannot be established.
  • Page 404 Page 390 of 492 Chapter 8 — Service changes and maintenance BRI811 Data corrupted. BRI812 Resources not available to process the task; try again later. BRI813 Another task waiting to be processed; wait at least 30 seconds and try again. BRI814 Command is illegal.
  • Page 405 Page 391 of 492 Chapter 8 — Service changes and maintenance BRI824 MISP cannot perform the enable/disable tasks. BRI825 Message cannot be sent to remove application from the MISP's EPROM. BRI826 Socket IDs have not been assigned to this application. Task is aborted. BRI827 Message to enable or disable has timed out;...
  • Page 406 Application loadware has been removed from the MISP. BRI848 Application is not identified with a socket ID, no communication with the MISP. BRI849 Task aborted. Meridian 1 cannot access the application information block on the MISP. 553-3011-311 Standard 7.0 May 1999...
  • Page 407 DSL and then recreate it using ISDN BRI Service Change Program LD 27. BRI851 DSL parameter cannot be downloaded because Meridian 1 could not send message to the MISP. BRI852 DSL parameter cannot be downloaded because no call register is available.
  • Page 408 Page 394 of 492 Chapter 8 — Service changes and maintenance BRI862 No path available to setup a D-channel dedicated connection. BRI863 Cannot send a message to the MISP to update the HDLC. BRI864 Cannot send a message to the MISP to update the HDLC. BRI865 Software BUG.

  • Page 409: Basic Rate Interface Trunk Messages (Brit)

    Page 395 of 492 Chapter 8 — Service changes and maintenance BRI875 Unable to establish or remove a dedicated B-channel or B D-channel connection because the channel is in maintenance busy state. BRI876 Specified B D-channel is busy. BRI877 D-channel dedicated connection cannot be established because there is no available path between the MISP and the ISDN PRI.

  • Page 410: Background Signaling Diagnostic Messages (Bsdxxx)

    Page 396 of 492 Chapter 8 — Service changes and maintenance Background signaling diagnostic messages (BSDxxx) BSD800 Command is being executed. BSD801 Call register not available. Wait and try the command again. If the problem persists, increase the number of call registers using Configuration Record Program LD 17.
  • Page 411 Page 397 of 492 Chapter 8 — Service changes and maintenance BSD816 Tags not available. Stop a test by executing XSTP command and try again. BSD817 Generate message could not be sent. The system is temporarily out of message registers. Wait and try again. BSD818 Detect message could not be sent.
  • Page 412 Page 398 of 492 Chapter 8 — Service changes and maintenance BSD829 Loopback cannot be performed on a non-ISDN BRI line card. BSD830 Loopback can only be performed between an MISP and one of the ISDN BRI line cards assigned to it. BSD831 MISP does not respond;...

  • Page 413: Software Error Monitor Messages (Bugxxxx)

    Page 399 of 492 Chapter 8 — Service changes and maintenance Software error monitor messages (BUGxxxx) BUG5438 DSLs already configured have reached the limit. BUG5439 Logical terminal IDs already specified have reached the limit. BUG5441 D-channel dedicated connections could not be established. BUG5442 Messages could not be sent to the line card.
  • Page 414 Page 400 of 492 Chapter 8 — Service changes and maintenance BUG5453 ISDN BRI call cannot be connected because of incompatibility of the B-channel with the incoming call type. BUG5454 Message CR cannot be found for incoming PRI call destined for an ISDN BRI terminal.

  • Page 415: Equipment Data Dump Messages (Eddxxx)

    ISDN BRI call is in wrong state; call attempt is aborted. ERR5158 ISDN BRI call reference invalid. ERR5159 ISDN BRI B-channel status out of sync between Meridian 1 and the MISP; call attempt is aborted. ERR5160 ISDN BRI calls exceeded the limit for the DSL.

  • Page 416: Network Link Messages (Lnkxxx)

    Page 402 of 492 Chapter 8 — Service changes and maintenance ERR5164 ISDN BRI B-channel is in maintenance busy state. ERR5165 Message received from invalid card slot. ERR5166 Message received from wrong ISDN BRI line card. ERR5167 Message received from ISDN BRI line card is invalid. ERR5168 Output buffer not available to send scan and signal distributor (SSD) message.

  • Page 417: Network And Peripheral Replacement Messages (Nprxxx)

    Page 403 of 492 Chapter 8 — Service changes and maintenance Network and peripheral replacement messages (NPRxxx) NPR509 DSL configuration download failed. NPR510 DSL is already enabled. NPR511 Shelf contains at least one ISDN BRI card, wait about 45 seconds to enable the loop.
  • Page 418 Page 404 of 492 Chapter 8 — Service changes and maintenance NPR555 Express output queue is full. NPR556 MISP output buffer is not available. NPR561 Input valid only for the MISP card NPR562 Message cannot be sent to the line card. NPR570 Application information blocks cannot be read from the MISP.

  • Page 419: Network And Signal Diagnostic Messages (Nwsxxx)

    Page 405 of 492 Chapter 8 — Service changes and maintenance Network and signal diagnostic messages (NWSxxx) NWS620 Express output queue full, CPU can not send the message to the MISP. NWS621 MISP output buffer not available. NWS622 Message cannot be sent to the MISP because of invalid message or conditions.

  • Page 420: Service Change Messages (Schxxxx)

    Page 406 of 492 Chapter 8 — Service changes and maintenance NWS636 MISP self test cannot be activated. NWS637 Self test passed. NWS638 Unit is not equipped. NWS639 TEI test could not be performed. NWS640 MISP does not respond. NWS641 Command cannot be performed on the MISP;...
  • Page 421 Page 407 of 492 Chapter 8 — Service changes and maintenance SCH5372 I/O polling table is full. SCH5373 MSDL/MISP index cannot be obtained because the table is full. SCH5374 Warning: B-channel is not configured for packet data transmission. SCH5375 Specified PRI channel is busy. Enter an idle PRI channel number. SCH5376 Number of DSLs exceeded the defined system limit.
  • Page 422 Page 408 of 492 Chapter 8 — Service changes and maintenance SCH5388 Remove all DSLs on the line card to change the card type. SCH5389 DSL number is out of range. Enter a number from 0 to 7. SCH5390 DSL data block has not been created. Configure the DSL. SCH5391 DSL data block has already been created.
  • Page 423 Page 409 of 492 Chapter 8 — Service changes and maintenance SCH5403 ISDN BRI DN is not allowed. SCH5404 MISP not allowed. SCH5405 A non-ISDN BRI terminal can not be configured for the specified ISDN BRI line card. SCH5406 This DSL cannot be configured because a D-channel is used for packet handler.
  • Page 424 Page 410 of 492 Chapter 8 — Service changes and maintenance SCH5418 Define at least one SPID. SCH5419 SPID has not been configured. SCH5420 Input has exceeded the maximum allowed SPIDs per TSP. Specify a maximum or 8 SPIDs for each TSP. SCH5421 DN input must be specified.
  • Page 425 Page 411 of 492 Chapter 8 — Service changes and maintenance SCH5433 DN is already defined for a different DSL. SCH5434 USID does not exist. Specify an available USID. SCH5435 SPID has been defined in the TSP. SCH5436 SPID value is to long. Enter correct SPID value not to exceed 9 characters. SCH5437 TSP has not been defined for the specified SPID.
  • Page 426 Page 412 of 492 Chapter 8 — Service changes and maintenance SCH5448 l Disconnect dedicated D-channel connection command for the specified MISP l has failed. Check MISP status. SCH5449 l Send DSL or line card status command for the specified MISP l has failed. Check MISP status.
  • Page 427 Page 413 of 492 Chapter 8 — Service changes and maintenance SCH5852 Cannot remove BRIL application without disabling the application. Disable the application using LD 32. SCH5853 Cannot remove BRIL application without first removing all associated DSLs. SCH5854 The specified route is not an ISDN BRI route. SCH5855 ISDN BRI trunk package is not equipped on this system.
  • Page 428 Page 414 of 492 Chapter 8 — Service changes and maintenance SCH5863 The new MISP for this card does not have BRIT configured but there is a BRIT DSL on this card. Enter a MISP with a BRIT application. SCH5864 BRIL package is not equipped on this system.
  • Page 429 Page 415 of 492 Chapter 8 — Service changes and maintenance SCH5905 The appropriate DSL in this slot (DSL#0 for PREF or DSL#1 for SREF) is not configured. Use LD 27 to configure the appropriate trunk clock source. SCH5906 Either the appropriate DSL in this slot (DSL#0 for PREF or DSL#1 for SREF) is not configured, or the slot must be a DTI, JDMI or PRI slot.
  • Page 430 Page 416 of 492 Chapter 8 — Service changes and maintenance SCH5931 The slot number is not a valid DTI2/PRI2 /MISP slot. Configure the DTI2/PRI2 slot using LD 17 or configure the MISP using LD 27. SCH5932 This MISP is referenced as a clock controller in the Digital Data Block. This reference must be removed using LD 73 before the MISP can be removed.
  • Page 431 Page 417 of 492 Chapter 8 — Service changes and maintenance SCH6426 The Call Forward External allow/deny is only allowed for ETSI and NI-1 protocol. SCH6427 Invalid supplementary feature. SCH6428 Cannot subscribe Call Forward Unconditional for this call type because the DN does not subscribe to this call type.

  • Page 432: System Loader Messages (Sysxxxx)

    Page 418 of 492 Chapter 8 — Service changes and maintenance System loader messages (SYSxxxx) SYS4206 Data can only be loaded when PRI2, DTI2, BRIT or BRIL package is selected. SYS4413 DSL can not be loaded. The number of DSLs exceeds the limit. SYS4414 Protected storage cannot be allocated.
  • Page 433 Page 419 of 492 Chapter 8 — Service changes and maintenance SYS4595 BRIT application will not be configured on any MISP because the BRIT package is not equipped. SYS4600 The DTI package is restricted and either the BRIT package is restricted or the DTI2 package is equipped or the PRI2 package is equipped.
  • Page 434 Page 420 of 492 Chapter 8 — Service changes and maintenance 553-3011-311 Standard 7.0 May 1999...

  • Page 435: Chapter 9 - Isdn Bri Traffic Reports

    Page 421 of 492 Chapter 9 — ISDN BRI traffic reports Introduction This chapter describes the traffic reports that can be generated for ISDN BRI equipment. It describes and shows examples of each report. Traffic report types Option 11 generates and stores traffic statistics about ISDN BRI equipment. These statistics can be displayed on the administration terminal or printed on the administration printer.

  • Page 436: Understanding Option 11 Traffic Reports

    Page 422 of 492 Chapter 9 — ISDN BRI traffic reports Understanding Option 11 traffic reports The Option 11 system is designed internally as a non-blocking system. It is always configured in a non-blocking concentration, having an internal superloop for every four IPE card slots. Traffic measurements for IPE cards (XDLC, XUT, DTR) are provided in groups of four line cards corresponding to the internal superloops as follows: Table 26...

  • Page 437: Network Traffic Report

    Page 423 of 492 Chapter 9 — ISDN BRI traffic reports Traffic measurements for network level cards configured in LD 17 (such as DTI, PRI, DTI2, PRI2, TDS) are assigned internally to a set of loops separate from the superloops assigned to the IPE cards. They are as follows: Table 27 SUPER CARD SLOT...
  • Page 438 Page 424 of 492 Chapter 9 — ISDN BRI traffic reports Number of call attempts that failed to match the channel call type Traffic load on the card Number of call attempts over the card Total number of call attempts that failed to match for all terminals on the card Total traffic load on the card Total number of calls handled by all the terminals on the card...
  • Page 439 Page 425 of 492 Chapter 9 — ISDN BRI traffic reports 0222 TFS001 TERM 00000 0000000 00000 00000 0000002 00001 TERM 00000 0000000 00000 00000 0000000 00000 TERM 00000 0000000 00000 00000 0000011 00001 TERM 00000 0000000 00000 00000 0000002 00006 TERM 00000...

  • Page 440: Misp/Dsl Traffic Report

    Page 426 of 492 Chapter 9 — ISDN BRI traffic reports MISP/DSL traffic report The MISP/DSL traffic report shows the call processing activities of all DSLs associated with each MISP in the system. It contains the following columns of information for each MISP in the system: Number of attempted calls, which include all the successfully completed calls and the attempted calls that have not been completed Number of successfully completed calls for the reported period...

  • Page 441: Misp D-Channel Management Messages Report

    Page 427 of 492 Chapter 9 — ISDN BRI traffic reports MISP D-channel management messages report The MISP D-channel management messages report contains the traffic management activity for each DSL based on the exchange of signaling messages between the MISP and the terminals over the D-channels. It is used by the maintenance technician to see if there are any communication problems between the MISP and the terminals.

  • Page 442: Misp Messages Report

    Page 428 of 492 Chapter 9 — ISDN BRI traffic reports MISP messages report The MISP messages report shows the total number of call processing, maintenance, and management messages sent through each MISP in the system. The totals are grouped according to the size of the message. It is used by the maintenance technician to determine if these messages are within the specified lengths.

  • Page 443: Misp Messages For Brit Application

    Page 429 of 492 Chapter 9 — ISDN BRI traffic reports MISP messages for BRIT application The MISP messages for BRIT application report shows the total number of maintenance, administration and protocol messages received and transmitted as well as protocol errors and D-channel failures. The report contains the following columns of information for each MISP in the system: Total number of maintenance messages transmitted Total number of maintenance messages received...

  • Page 444: Generating Traffic Reports

    Page 430 of 492 Chapter 9 — ISDN BRI traffic reports Generating traffic reports The following describes how to print traffic reports to verify that the traffic generated during voice and data transmission testing has been stored by the system and can be printed on demand. To print the last traffic report generated during acceptance testing, use the following command in LD 2: INVC (CUSTOMER) (OPTIONS)
  • Page 445 Page 431 of 492 Chapter 9 — ISDN BRI traffic reports To verify ISDN BRI traffic generated during acceptance testing, select the network traffic report and the MISP traffic report as follows: INVC (CUSTOMER) 1 11 The system printer should print these two reports, which you should check to make sure that the traffic generated during the test is reflected in the reports.
  • Page 446 Page 432 of 492 Chapter 9 — ISDN BRI traffic reports 553-3011-311 Standard 7.0 May 1999...

  • Page 447: Appendix A - 2Mb Pri Implementation

    Page 433 of 492 Appendix A — 2Mb PRI implementation Overview This Appendix provides the information required to install 2Mb PRI on a Meridian 1 Option 11 system: — hardware installation — software programming instructions Option 11C ISDN BRI Administration and Maintenance...

  • Page 448: Hardware Requirements

    Appendix A — 2Mb PRI implementation Hardware requirements Circuit cards To implement 2.0 Mb PRI on the Meridian 1 Option 11, an NTAK79 or an NTBK50 PRI card plus associated daughterboards is required. Table 28 2.0 Mb PRI hardware requirements...

  • Page 449: Hardware Description

    Page 435 of 492 Appendix A — 2Mb PRI implementation Hardware description 2.0 Mb PRI cards Two PRI cards are available on the Option 11 system: — NTAK79 2.0 Mb PRI card — NTBK51 2.0 Mb PRI card The difference between the two PRI cards is the ability of the NTBK50, when equipped with the NTBK51 D-channel daughterboard, to download software onto the card.

  • Page 450: Ntak20 Clock Controller (Cc) Daughterboard

    NTAK93 D-Channel Handler Interface (DCHI) daughterboard The NTAK93 DCHI daughterboard interfaces with the Meridian 1 Option 11 Central Processing Unit (CPU) and mounts on the NTBK50 PRI card for PRI (but not ISL) applications. The equivalent circuit is contained on-board the NTAK79 2.0 Mb PRI card.

  • Page 451: Ntbk51 Downloadable D-Channel Daughterboard

    11 Central Processing Unit (CPU) and mounts on the NTBK50 2.0 Mb PRI circuit card for PRI D-Channel applications. The DDCH is equivalent to the MSDL card used on the larger Meridian 1 systems, but it only supports D-channel applications (no SDI or ESDI).

  • Page 452: Setting The Switches On The Ntak79

    Page 438 of 492 Appendix A — 2Mb PRI implementation Setting the switches on the NTAK79 The NTAK79 incorporates four on-board dip switches. The tables that follow provide information on the various settings and related functions of these switches. Note: The ON position for all the switches is towards the bottom of the card.
  • Page 453 Page 439 of 492 Appendix A — 2Mb PRI implementation Set the switches found on the circuit card as per the requirements of your specific installation: Switch SW1—DCHI Configuration This switch enables/disables the on-board DCHI and sets the operating mode of the DCHI.

  • Page 454: Inserting The Ntak79 Into The Main Cabinet

    Page 440 of 492 Appendix A — 2Mb PRI implementation Switch SW4—Carrier Shield Grounding This switch allows for the selective grounding of the Tx and/or Rx pairs of the carrier cable. Closing the switch (down position) applies Frame Ground (FGND) to the coaxial carrier cable shield, creating a 75¾ unbalanced configuration.
  • Page 455 Page 441 of 492 Appendix A — 2Mb PRI implementation NTAK79 Cabling NTBKO5AA 120Ω Twisted Pair OPTION 11 To 2.048 2 Mb PRI Mpbs Carrier Cross Connect 2Mb DTI NTBKO5CA 75Ω Coax Pair 553-7870.EPS NTBK05DA pinouts The pinouts for the NTBK05DA cable are as follows: From: 50 pin MDF 9 pin...

  • Page 456: Installing Pri Hardware: Ntbk50 Pri Card

    Each of these steps is described in the pages that follow. The PRI hardware installation procedure is the same regardless of the type of system at the far end (i.e. another Meridian 1, AXE-10, SYS-12, etc.). Inspecting the NTBK50 circuit card —...

  • Page 457: Setting The Switches On The Ntbk50

    Page 443 of 492 Appendix A — 2Mb PRI implementation Setting the switches on the NTBK50 The NTBK50 incorporates four on-board dip switches. The following tables provided information on the various settings and related functions of these switches. Note: The ON position for all the switches is towards the bottom of the card.
  • Page 458 Page 444 of 492 Appendix A — 2Mb PRI implementation Set the switches found on the circuit card as per the requirements of your specific installation: Switch SW1—DCHI Configuration (NTAK93 only) This switch enables/disables the DCHI and sets the operating mode of the DCHI.

  • Page 459: Mounting The Daughterboards On The Ntbk50

    Page 445 of 492 Appendix A — 2Mb PRI implementation Mounting the daughterboards on the NTBK50 Use the following procedure to mount and remove the NTAK20 CC and the NTBK51 DDCH or NTAK93 DCHI daughterboards onto the NTBK50 PRI. Install the NTAK93 or NTBK51 daughterboard before the NTAK20 daughterboard.
  • Page 460 Page 446 of 492 Appendix A — 2Mb PRI implementation Figure 57 Daughterboard installation Stiffeners NTAK20 Clock Controller Connector Sockets LEDs Bantam Jacks NTAK93 or NTBK51 D-Channel Interface 553-7872 Standoffs 553-7872.EPS 553-3011-311 Standard 7.0 May 1999...

  • Page 461: Inserting The Ntbk50 Into The Main Cabinet

    Page 447 of 492 Appendix A — 2Mb PRI implementation Removing the daughterboards from the NTBK50 Use these guidelines to remove the NTAK20 and NTBK51 or NTAK93 from the NTBK50 PRI card. Because of the physical layout of the mother and daughterboards, the NTAK20 should be removed before the NTAK93 or NTBK51.
  • Page 462 Page 448 of 492 Appendix A — 2Mb PRI implementation Figure 58 2 Mb PRI Cabling NTBKO5AA 120Ω Twisted Pair OPTION 11 To 2.048 Mpbs Carrier NTBK50 Cross Connect NTBKO5CA 75Ω Coax Pair 553-7873.EPS NTBK05DA pinouts The pinouts for the NTBK05DA cable are as follows: From: 50 pin MDF 9 pin...

  • Page 463: Pri Software Programming

    Page 449 of 492 Appendix A — 2Mb PRI implementation NTBK05CA pinouts The pinouts for the NTBK05CA cable are as follows: From: Transmit coax Receive coax 50 pin MDF 50 pin MDF connector connector connector connector pin 23 Inner conductor — —...

  • Page 464: Procedure Summary

    Page 450 of 492 Appendix A — 2Mb PRI implementation — A primary D-Channel can not act as the backup D-Channel of another primary D-Channel. — A primary D-Channel with a backup D-Channel can not be taken out. The craftsperson must first take out the backup D-Channel. —...
  • Page 465 Back-up DCHI port number, if required DPNS Default is no D-channel is for ISDN PRI only. Note: 2.0 Mb only supports PRI or SHA user mode. Interface type is Meridian 1 - Meridian 1 Option 11C ISDN BRI Administration and Maintenance...
  • Page 466 Page 452 of 492 Appendix A — 2Mb PRI implementation Prompt Response Description DCHL (1-9) PRI card number which will be carrying the D-channel. Must match entry made for the “CDNO” associated with the “DCHI” prompt above PRI2 <CR> Additional PRI Loops controlled by this DCHI. Remember one DCHI can control up to 16 PRI loops going to the same destination.
  • Page 467 Network Ring Again, Network ACD..Note that if set to zero (0), NRAG and NACD will not work. HNPA telephone area code for this Meridian 1. Sent as part of setup message as calling line (PFX1) identification. Option 11C...
  • Page 468 Appendix A — 2Mb PRI implementation Prompt Response Description HNXX telephone local exchange code for this Meridian 1. Sent as part of setup message as (PFX2) calling line identification. HLOC home location code (NARS) 1-9999 one to four digit Local Steering Code established in the Coordinated Dialing Plan (CDP).
  • Page 469 Page 455 of 492 Appendix A — 2Mb PRI implementation Prompt Response Description INAC Insert Access Code. Permits the NARS AC1 or AC2 access code to be re-inserted automatically on an incoming ESN call. This prompt only appears on a TIE route and must be set to “YES”...
  • Page 470 Page 456 of 492 Appendix A — 2Mb PRI implementation Prompt Response Description TYPE PRI2 2 Mb PRI FEAT SYTI System timers CLKN Card slot number of the PRI circuit card which will have the active clock controller. PREF Primary reference source for clock controller. Enter the PRI card number of the PRI card which will have an active clock controller.
  • Page 471 Page 457 of 492 Appendix A — 2Mb PRI implementation Define PRI parameters and thresholds. Use Overlay 73. Prompt Response Description TYPE PRI2 2 Mb PRI FEAT LPTI LOOP X is the slot number of the 2 Mb PRI card. AFF, (CRC) The Framing Mode.
  • Page 472 Page 458 of 492 Appendix A — 2Mb PRI implementation Prompt Response Description T2 mt dt ct ot Group 2 error thresholds. This is the maximum amount of time that can occur before software checks the associated thresholds of 120 to 32,640 msec and rounds it to the closest multiple of 128 msec.
  • Page 473 Page 459 of 492 Appendix A — 2Mb PRI implementation Use Overlay 73 to change trunk pad category values Prompt Response Description TYPE PRI2 2 Mb PRI FEAT PADS PDCA PAD table-0 is default and is hard coded The following prompts define the pad levels. The receiving pad code is r and the transmission pad code is t .
  • Page 474 Page 460 of 492 Appendix A — 2Mb PRI implementation Prompt Response Description analog CO trunk (prompted only if the 1.5/2 Mb Gateway feature is equipped and TYPE=PRI2) Author’s Note—p7/dave/gateway analog TIE trunk (prompted only if the 1.5/2 Mb Gateway feature is equipped and TYPE=PRI2) Author’s Note—p7/dave/gateway The following are the pads available to 2 Mb PRI.

  • Page 475: Pri Software Programming: Option 11 To Central Office (Isa)

    Outgoing Calls: Since ISDN requires some form of ESN (CDP or/and NARS), then the Route List Tables (ESN LD 86) include the Service route(s). Therefore. the Meridian 1 software performs the digit translation and sends the call out on an ISA route associated with the service route selected. This feature is transparent.

  • Page 476: Limitations

    Page 462 of 492 Appendix A — 2Mb PRI implementation Limitations The caller is prevented from dialing the access code of an ISA route directly. It is also possible to step to a standard trunk route (NON-ISA) when all ISA channels are busy.

  • Page 477: Dependencies

    Page 463 of 492 Appendix A — 2Mb PRI implementation Dependencies Basic PRI configuration must be performed before Integrated Services Access (ISA) is defined (Steps 1, 2, 3, 4 and 8 under programming the PRI-ISA which follows). An ISA route and associated ISA trunks are then defined, followed by service routes.
  • Page 478 Route number as we know it (LD 16) as programmed in the Meridian 1 does not mean anything to the CO Note that what we call SID on the Meridian 1, is referred to by the DMS table as “FACNUM.”...

  • Page 479: Configuring Option 11 To Central Office (Isa)

    Page 465 of 492 Appendix A — 2Mb PRI implementation NSF=YES This is the preferred method which provides control over the allocation of ISA “B” channels for the various Service Routes. When the NSF prompt is YES, then a route for COTR and WATR should be assigned. The COTR can be a route number for an incoming CO or incoming DID route same as above.

  • Page 480: Procedure Summary

    Page 466 of 492 Appendix A — 2Mb PRI implementation Procedure summary Step Overlay Action LD 17 (CFN) Add a PRI loop. LD 17 (CFN) Add a DCHI/DDCH card. LD 15 (CDB) Define a PRI customer. LD 16 (RDB) Define a PRI service route. LD 14 (TDB) Define service channels (B channels) and PRI trunks.
  • Page 481 Page 467 of 492 Appendix A — 2Mb PRI implementation Prompt Response Description CTYP DCHI/MSDL DCHI for existing D-Channel configuration. (NTAK93 D-channel) MSDL for Downloadable D-Channel configuration (NTBK51 D-channel). The MSDL base and D-Channel application software will be downloadable into the DDCH card.
  • Page 482 Page 468 of 492 Appendix A — 2Mb PRI implementation Prompt Response Description DCHL PRI card number which will be carrying the D-channel. Must match entry made for the “CDNO” associated with the “DCHI” prompt above PRI2 <CR> Additional PRI Loops controlled by this DCHI. Remember one DCHI can control up to 16 PRI loops going to the same destination.
  • Page 483 Meridian 1. Sent as part of setup message as calling line identification. HNXX telephone local exchange code for this Meridian 1. Sent as part of setup message as calling line identification. HLOC home location code (NARS) 1-9999...
  • Page 484 Page 470 of 492 Appendix A — 2Mb PRI implementation Prompt Response Description INTL International Special Number Location Code Configure the ISA route. Use Overlay 16 Prompt Response Description NEW, TYPE route data block TKTP create an ISA trunk route DTRK digital trunk route DGPT...
  • Page 485 Page 471 of 492 Appendix A — 2Mb PRI implementation Prompt Response Description TIER 0-511 incoming or combination TIE route num- ber--prompted if NSF is NO. WATR 0-511 incoming or combination WATS route num- ber--prompted if NSF is YES. Configure the ISA trunks. Use Overlay 14 Prompt Response Description...
  • Page 486 Page 472 of 492 Appendix A — 2Mb PRI implementation Prompt Response Description SRVC IWAT In-Wats Service (AT&T ESS5) (continued) WATM Maximum Subscribed (AT&T ESS5) WATB WATS parameterized band (AT&T ESS5) SRPM 0-(9) WATS parameterized band. Prompted only if SRVC=WATB. MODE route used for PRI only 1-32700...
  • Page 487 Page 473 of 492 Appendix A — 2Mb PRI implementation Prompt Response Description 1-254 maximum number of channels on the ISA route to be used by this service route (service dependent). See text preceding the programming for details. Coordinate with the far end.
  • Page 488 Page 474 of 492 Appendix A — 2Mb PRI implementation Prompt Response Description n1 n2 Cyclic redundancy check error count 1-(201)-255 for n1, 1-(97)-255 for n2. n1 is multiplied by 4 to obtain the actual count, giving an actual count range of 4-1020. FBER n1 n2 Frame alignment problem error count...
  • Page 489 Page 475 of 492 Appendix A — 2Mb PRI implementation Prompt Response Description PERS Persistence Timer for Group II problems. Enter 0 - 256 msec in increments of 2 msec. Default is 50 (=100ms). OOSC Out of Service Counter. Range for nnn of 0-255 with a default of 5. Change trunk pad category values.
  • Page 490 Page 476 of 492 Appendix A — 2Mb PRI implementation Prompt Response Description digital COT, FEX, WAT, and DID trunks VIA NET LOSS 2 Mb PRI2 digital TOLL office trunks Analog CO or WATS trunks Analog FEX trunks Analog DID trunks SATT analog satellite TIE SATT...
  • Page 491 Page 477 of 492 Appendix A — 2Mb PRI implementation The following are the pads available to 2 Mb PRI: code value +1.0 +2.0 +3.0 +4.0 +5.0 +6.0 +7.0 (dB) code value +8.0 +9.0 +10.0 +11.0 +12.0 +13.0 +14.0 -1 (dB) code value...
  • Page 492 Page 478 of 492 Appendix A — 2Mb PRI implementation 553-3011-311 Standard 7.0 May 1999...

  • Page 493: List Of Terms And Abbreviations

    Page 479 of 492 List of terms and abbreviations The following is a list of terms and abbreviations used throughout this guide. 1TR6 The ISDN protocol used in Germany and in any country that supports German protocol Automatic Call Distribution Applications Module Link ANSI American National Standards Institute...
  • Page 494 Page 480 of 492 List of terms and abbreviations B2CT B-channel 2 Call Type Backup D-channel 64 kbps channel carrying D channel packet data Bearer Capability -channel 64 kbps channel carrying D channel packet data Basic Rate Access Basic Rate Interface. A standard format for ISDN access and transmission of both voice and data communications between individual user stations and the supporting PBX switch.
  • Page 495 Page 481 of 492 List of terms and abbreviations CFTD Call Forward by Call Type Denied PRI Channel Number CLID Calling Line Identification CLIP Calling Line Identification Presentation CLIR Calling Line Identification Restriction Class of Service Central Office (local exchange) Local exchange Trunk Central Processing Unit Conditionally Toll Denied...
  • Page 496 Page 482 of 492 List of terms and abbreviations D-Channel DSL Designator DFDN Default Directory Number Direct Inward Dial Digital Multiplex Switching Directory Number Digital Subscriber Loop. Any one of eight physical BRI ports which are supported by a BRI line card (either a UILC or SILC). Each DSL supports two B-channels and one D-channel.
  • Page 497 Page 483 of 492 List of terms and abbreviations ENET Enhanced Network Electronic Switching Network ETSI European Telecommunications Standards Institutes ETSI NET-3 ISDN Protocol in European countries Call Forward Busy Allowed Call Forward Busy Denied Flexible CFNA Directory Number FEAT Class of Service Features Call Forward No Answer Allowed Call Forward No Answer Denied...
  • Page 498 Page 484 of 492 List of terms and abbreviations Fully Restricted HBTA Hunting By Call Type Allowed NBTD Hunting By Call Type Denied HDLC High Level Data Link Control Hunt Allowed Hunt Denied HUNT Hunt Directory Number Information Element Input/Output INS NET-64 Protocol used in Japan Intelligent Peripheral Equipment...
  • Page 499 Page 485 of 492 List of terms and abbreviations ISDN Integrated Services Digital Network. A digital data communications network providing for the universal access and transmission of data, voice, image, facsimile and other communication formats either separately or simultaneously. Incremental Software Management Integrated Voice and Data Kbps Kilobits per second...
  • Page 500 Page 486 of 492 List of terms and abbreviations Logical Terminal Number M5000TD-1 UTA The M5000TD-1 Universal Terminal Adapter (NTBX94AA) is a Northern Telecom ISDN BRI device that connects non-ISDN BRI terminals to an ISDN BRI S/T bus, and supports simultaneous Voice and Data communications using non-ISDN BRI voice and data terminals.
  • Page 501 Page 487 of 492 List of terms and abbreviations Main Processor Unit Message Registration Allowed Message Registration Denied Maintenance Signaling Channel MSDL Multi-Purpose Serial Data Link MTEI Maximum Number of Terminal Endpoint Identifiers MTSP Maximum Number of TSPs Defined for a DSL Multiplexed Message Waiting Allowed Message Waiting Denied...
  • Page 502 Page 488 of 492 List of terms and abbreviations Network Terminator 2, or Meridian 1 NTAS NT1 Adaptive Sampling NTFS NT1 Fixed Sampling NUMERIS The ISDN protocol used in France and in any country that supports French protocol. Open System Interconnect...
  • Page 503 Page 489 of 492 List of terms and abbreviations PRES Presents/Restricts Calling Party Number Display 1,5 Mbps Primary Rate Interface PRI2 2.0 Mbps Primary Rate Interface PRID Protocol ID PSDL Peripheral Software Downloading PSTN Public Switched Telephone Network PULP Paper-Pulp Insulated cable PSWV Peripheral Software Version Restricted DID...
  • Page 504 SILC The SILC is an S/T Interface Line Card that processes S/T signals between the BRI terminal devices (such as BRI telephones) and the Meridian 1. A Terminal Adapter designed to interface with Option 11 ISDN BRI and 1TR6 terminals...
  • Page 505 Page 491 of 492 List of terms and abbreviations Terminal Endpoint Identifier is a terminal logical address assigned and used by the MISP to address a terminal during the exchange of layer 2 information. Each logical terminal is associated with one unique TEI. Up to 20 TEIs can be assigned on a single DSL.
  • Page 506 Page 492 of 492 List of terms and abbreviations UILC The UILC is a U Interface Line Card that processes U-loop signals between an NT1 adapter and the Meridian 1. Unrestricted USID User Service Identifier is an identification number that uniquely identifies a TSP assigned to one or more terminals on a DSL.
  • Page 507 Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at their own expense. Meridian 1 is a trademark of Nortel Networks. Publication number: 553-3011-311 Document release: Standard 7.0 Date: May 1999...

This manual is also suitable for:

Option 11c

Table of Contents