NetWare Connect for ISDN 2 - AVM · and efficiency. NetWare Connect for ISDN is a software product that inte-grates ISDN in a Novell network. In purchasing NetWare Connect for ISDN

NetW

are® Connect

™ for ISDN Installation and A

dministration G

uide

Installation andAdministration Guide

I S D N

P R O D U C T

C O N N E C T I V I T Y

Manufactured and supported by

A Novell® authorized OEM

AVM Computersysteme

ISD

N C

ON

NE

CT

IVIT

Y P

RO

DU

CT

NetWare® Connect™ for ISDN

¸

¸

¸

¸

Novell-Rot Black

This manual is printed on chlorine-free paper and is therefore completely recyclable.

07.9

9/50

0/R

&P

2 Netware Connec

nwci2.1.book Seite 2 Donnerstag, 13. Januar 2000 11:36 11

Netware Connect for ISDNThis manual and the software it describes are protected by copyright. The manual andsoftware as presented are the object of a license agreement and may be used only in ac-cordance with the license conditions. The licensee bears all risk in regard to hazards andimpairments of quality which may arise in connection with the use of this product.

This manual and the software it describes may not be transmitted, reproduced or alteredin whole or in part, in any form, by any means, nor may they be translated into any othernatural or computer language. The creation of a backup copy for personal use is except-ed. The information hereby made available to the licensee may be communicated tothird parties only with the written permission of AVM Berlin.

This software and documentation have been produced with all due care and checked forcorrectness in accordance with the best available technology. AVM Berlin disclaims all li-ability and warranties, whether express or implied, relating to this product’s quality, per-formance or suitability for any given purpose which deviates from the performance spec-ifications contained in the product description.

AVM will not be liable for damages arising directly or indirectly from the use of the manu-al or related software, nor for incidental or consequential damages, except in case of in-tent or gross negligence. AVM expressly disclaims all liability for loss of or damage tohardware, software or data as a result of direct or indirect errors or destruction and forany costs, including ISDN connection charges, related to the software and manual sup-plied and due to incorrect installations not performed by AVM itself.

The information in this manual and the software it describes are subject to change with-out notice for the purpose of technical improvement.

© Copyright 2000 AVM Berlin. All rights reserved.

Netware Connect for ISDN Support Fax: + 49/(0)30/3 99 76-2 66AVM in the Internet: http://www.avm.de

Trademark notice: FRITZ! and AVM are registered trademarks of AVM Vertriebs KG. Novelland NetWare are registered trademarks of Novell, Inc.. Windows is a registered trademarkof Microsoft Corporation. All other trademarks are trademarks or registered trademarks ofthe respective owners.

AVM Audiovisuelles Marketingund Computersysteme GmbHAlt-Moabit 95

AVM Computersysteme VertriebsGmbH & Co.KGAlt-Moabit 95

10559 Berlin 10559 Berlin

t for ISDN

http://www.avm.de

http://www.avm.de


Contents

1 Introduction 71.1 What Does NetWare Connect for ISDN Provide?. . . . . . . . . . . . . . . . . . . 8

LAN-based Access to ISDN: CAPI Connect Service (CCS) . . . . . . . . . 8Dial-in Access to the LAN: Remote Node Servicefor ISDN (RNSI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.2 For Further Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11The AVM Data Call Center (ADC) . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.3 Package Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.4 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2 Installation in NetWare 5 or NetWare With NIAS 4.1 132.1 Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.3 Automatic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.4 Removing NetWare Connect for ISDN . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3 Installation in NetWare Without NIAS and WithNIAS Version 4.0 or Earlier 21

3.1 Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.3 Automatic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.4 Removing NetWare Connect for ISDN . . . . . . . . . . . . . . . . . . . . . . . . . . 27

4 Configuration 294.1 CAPI Connect Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Activating CCS on the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Installing NDC on the Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Operating NDC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32NDC Automation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Removing NDC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34First Test Connection with NDC and CCS . . . . . . . . . . . . . . . . . . . . . 34

Netware Connect for ISDN – Contents 3


4.2 Remote Node Service for ISDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Number Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Network Protocol Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Charge Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

4.3 ISDN-Controller Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Setting up an ISDN-Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46General ISDN-Controller Parameters . . . . . . . . . . . . . . . . . . . . . . . 47Special Instructions for Configuring PCI Controllers . . . . . . . . . . . 48

4.4 Port and Security Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

5 Operation 495.1 Stopping NetWare Connect for ISDN . . . . . . . . . . . . . . . . . . . . . . . . . . 495.2 Starting NetWare Connect for ISDN . . . . . . . . . . . . . . . . . . . . . . . . . . . 495.3 Monitoring the Remote Node Service for ISDN . . . . . . . . . . . . . . . . . . 505.4 Monitoring the CAPI Connect Service. . . . . . . . . . . . . . . . . . . . . . . . . . 505.5 Monitoring the ISDN Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .515.6 Connection and Accounting Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

6 Information for Administrators 536.1 NDS and NetWare Connect for ISDN. . . . . . . . . . . . . . . . . . . . . . . . . . . .53

NDS Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53Snap-In for NetWare Administrator (NWAdmin). . . . . . . . . . . . . . . .53

6.2 Internal Mechanisms and Further Configurationand Operating Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

6.3 Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Testing the ISDN Line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Support: NWCIINFO.NLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56System and Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

4 Netware Connect for ISDN – Contents


Typographical ConventionsThe following typographical conventions and symbols are used in this man-ual to make it more readable and to emphasize important information:

HighlightingThe following table presents a short overview of the highlighting conven-tions used in this manual.

SymbolsThe following symbols used in the manual always appear with gray, itali-cized text:

Highlighting Function Example

quotation marks keys, buttons, program icons, settings pages, menus, commands

“Start / Programs” or “Enter”

capital letters paths and files within float-ing text

DOCS\ALICE.PDF orCAPIPORT.HLP

pointedbrackets

variables <CD-ROM drive>

typewriter characters entries made using the key-board

a:\setup

gray and italics information, tips and warnings; always appear with the correspondingsymbols

... Controllers must be re-moved one at a time ...

This symbol indicates useful tips and supplementary information.

The exclamation point designates sections which contain important infor-mation.

Indicates especially important instructions that absolutely must be ob-served to ensure correct functioning.

Netware Connect for ISDN – Typographical Conventions 5

6 Netware Connec


t for ISDN – Typographical Conventions

Introduction


1 Introduction

The interconnection of computers and telecommunication networks plays amajor part in networking technology. In the computer network, the NetWareoperating system provides a robust platform for telecom integration. Amongthe telecommunications networks in use today, ISDN (Integrated ServicesDigital Network) stands out with key features: high speed, excellent qualityand efficiency. NetWare Connect for ISDN is a software product that inte-grates ISDN in a Novell network.

In purchasing NetWare Connect for ISDN you have acquired a product devel-oped by AVM in close cooperation with Novell. NetWare Connect for ISDNdraws on AVM’s years of experience as Novell’s only OEM partner in thisfield.

NetWare Connect for ISDN expands your NetWare server to include two new,ISDN-specific services: the CAPI Connect Service (CCS) and the Remote NodeService for ISDN (RNSI).

The CAPI Connect Service makes the ISDN-Controllers in the server availablefor use by all workstations in your network, allowing users to transfer files,send faxes or use on-line services from any LAN workstation.

The Remote Node Service provides remote computers with fast, economicalaccess to the LAN. This allows telecommuters or field representatives towork with LAN resources such as e-mail service, databases or applicationsoftware.

A complete description of both services is found in the “NetWare Connect forISDN 2.0 Installation and Administration Guide”, which is enclosed with Net-Ware Connect for ISDN 2.1. The present documentation for NetWare Connectfor ISDN 2.1 contains references to the corresponding chapters in the Instal-lation and Administration Guide. Since these two documents complementeach other, you should keep them both in a safe place.

NetWare Connect for ISDN 2.1 contains specially adapted versions of Net-Ware Connect for ISDN for different NetWare operating systems. The instal-lation routine verifies the operating system environment of your NetWareServer and installs the appropriate version of NetWare Connect for ISDN foryour NetWare environment. On NetWare 5 servers and on NetWare serverswith NIAS 4.1, NetWare Connect for ISDN NIAS Edition 2.1 is installed. On allother NetWare servers, NetWare Connect for ISDN 2.0 is installed to ensurecompatibility with older NetWare versions.

Netware Connect for ISDN – 1 Introduction 7

What Does NetWare Connect for ISDN Provide?


8 Netware Connec

The CCS and RNSI services have identical capabilities in NetWare Connectfor ISDN 2.1 and NetWare Connect for ISDN 2.0. The differences between thetwo versions lie in their specific installation and operation procedures. Fur-ther information is found in the appropriate sections of this manual.

1.1 What Does NetWare Connect for ISDN Provide?
The server-based software product NetWare Connect for ISDN integrates theadvantages of ISDN in recognized NetWare technology. This powerful com-munications platform provides users in the LAN and outside it with fast ac-cess to information and resources in the network—with ISDN reliability andspeed.
Installed on the NetWare server with one or more AVM ISDN-Controllers, Net-Ware Connect for ISDN provides a service that can be used by every worksta-tion in the LAN to access ISDN. Sending and receiving faxes, transferringfiles, dialing in to on-line services, Internet access and other ISDN-based ap-plications—all users in the LAN can take advantage of these possibilities us-ing the ISDN-Controllers in the server. Outside the LAN, remote users canconnect to all LAN resources through NetWare Connect for ISDN, including e-mail, databases or application software.

The overall result is optimum utilization of the company’s ISDN resources,together with centralized management of the accompanying security mecha-nisms and access rights.

LAN-based Access to ISDN: CAPI Connect Service (CCS)
The CAPI Connect Service (CCS) runs on the NetWare server as a NetWareConnect for ISDN service, making the server’s ISDN interfaces availablethroughout the network.
The Network Distributed CAPI (NDC) is started on the workstations and re-quests the CAPI Connect Service. If CCS accepts the request, NDC is loadedand a CAPI interface is then available on the workstation. The CAPI interfaceis the prerequisite that allows the workstation to use a multitude of CAPI ap-plications, such as AVM FRITZ! or on-line services’ access software.

t for ISDN – 1 Introduction

LAN-based Access to ISDN: CAPI Connect Service (CCS)


The following illustrations show two sample applications of the ISDN accessthrough the CAPI Connect Service.

Example: Outgoing Connections from the LAN

* The AVM ISDN-Controllers T1 and T1-B do not support the fax protocol T.30. In this case, the client must perform the conversion of analog fax signals.

Example: Incoming Connections to the LAN

Further information and examples of the general capabilities of CCS andNDC can be found in the “NetWare Connect for ISDN 2.0 Installation and Ad-ministration Guide” in the section “NDC on the LAN Clients and CCS on theNetWare Connect for ISDN Server”, pp. 22–24.

NetWareConnectfor ISDN server

ISDN

CAPI

ISDN-Controller

NDC

NDC

NDC

FRITZ!dataAVM

FRITZ!faxAVM

On-line service access software

FRITZ!dataAVM

Telefax

CCSRNSI

AVM ISDN-Controller B1, T1 or T1-B *

On-line service

Remote control

...


CAPI

ISDN-Controller

CCSRNSI

NDC

CAPI

pc ANYWHERESymantec

ISDN-Controller

...

pc ANYWHERESymantec

IDtransAVM

NDC

FRITZ!dataAVM

File transfer

ISDN

AVM ISDN-Controller B1, T1 or T1-B


Dial-in Access to the LAN: Remote Node Service for ISDN (RNSI)


Dial-in Access to the LAN: Remote Node Service for ISDN (RNSI)

10 Netware Connec

In order for remote computers to access the LAN’s resources, the RemoteNode Services for ISDN (RNSI) must be installed and activated on the Net-Ware server. RNSI allows remote computers outside the local-area networkto dial in over ISDN or over GSM. The remote workstations can use Net-WAYS/ISDN or a PPP client to dial in to the NetWare server’s RNSI serviceand access LAN resources using the network protocol IPX/SPX and/orTCP/IP.

The following diagram illustrates dial-in LAN access from remote worksta-tions.

Dial-in LAN Access from Remote Workstations over ISDN or GSM

Further information and examples of the general capabilities of RNSI can befound in the “NetWare Connect for ISDN 2.0 Installation and AdministrationGuide” in the section “NetWAYS or PPP over ISDN-compatible Product on theRemote Clients; RNSI on the NetWare Connect for ISDN Server”, pp. 28–33.

The remote workstations have access toall resources and services in the LAN: filesystems, data bases, hosts, gateways... . ISDN

AVM ISDN-Controller A1

........

..

....................................

IPX, TCP/IP

NetWAYS/ISDN


.............

......NetWarefor SAA

CCS

RNSI

AVM ISDN-Controller M1

IPX, TCP/IP

NetWAYS/ISDN....

..

GSMcellular

Sales representativeson the way

Employees in asmall branch

AVM ISDN-Controller B1, T1 or T1-B

1.2 For Further Information
AVM provides numerous sources of further information to support you inyour day-to-day work with NetWare Connect for ISDN. Information about newproducts and updates is also available in the Internet and from the AVM Da-ta Call Center (ADC).

Manuals


Manuals
This manual is intended to facilitate a quick start in NetWare Connect for IS-DN. Please see the reference manual mentioned below for more information.
Further details on RNSI, CCS and NDC are found in the accompanying refer-ence manual, the “NetWare Connect for ISDN 2.0 Installation and Adminis-tration Guide”.

The AVM Data Call Center (ADC)
The AVM Data Call Center (ADC) provides access to the latest information, aswell as free updates and extensions, for AVM products.
The ADC is accessible in the following ways:

� By ISDN file transfer:

You can dial the ADC using the file transfer program Connect orConnect32, included with all AVM ISDN-Controllers, or with AVM’sFRITZ!data. The file transfer server’s ISDN number is (IDtrans protocol):

+49-30-399 84 300

� Over the Internet:

AVM’s home page can be found at:

http://www.avm.de/

1.3 Package Contents
NetWare Connect for ISDN contains:
� 1 “NetWare Connect for ISDN 2.1” CD-ROM with CD key

� 1 license disk for the given number of ISDN ports, for NetWare versionswithout NIAS 4.1

The CD key is found on the back of the CD case. Keep both the CD keyand the license disk in a safe place. Both are absolutely necessary forthe NetWare Connect for ISDN installation.

� 1 “NetWare Connect for ISDN 2.1” manual

� 1 “NetWare Connect for ISDN 2.0 Installation and AdministrationGuide”

� 1 single user license for NetWAYS/ISDN 4.0, Windows 95/98 or Win-dows NT, including manual.

If any of these components is missing, please contact your dealer.


System Requirements


1.4 System Requirements

12 Netware Connec

The server equipment must fulfill the following requirements:

� The NetWare version must be one of the following:

� The system RAM must be at least:

� At least 26 MB of available hard disk space

� A CD-ROM drive or an additional 10 MB of hard disk space for a copy ofthe NetWare Connect for ISDN installation files

� Appropriate SET commands in STARTUP.NFC:

set minimum packet receive buffers = 200set maximum packet receive buffers = 500

� Update your NetWare version in accordance with Novell’s recommend-ed minimum patch list. Current patches can be found on Novell’s Website at:

http://novell.com/misc/patlst.htm#nw

There are a number of ways to install NetWare Connect for ISDN. For detailedinformation, please see the section “NetWare Connect for ISDN InstallationSetup” in the “NetWare Connect for ISDN 2.0 Installation and AdministrationGuide”, p. 54. The following procedure describes the installation form theoriginal “NetWare Connect for ISDN 2.1” CD-ROM supplied.

NetWare 5 NetWare for Small Businesses 4.2

NetWare 4.2 Intranetware 4.11

NetWare 4.11 NetWare 4.1


32 MB for:

NetWare 5 NetWare for Small Businesses 4.2

24 MB for:

NetWare 4.2 Intranetware 4.11


8 MB for:


Please note that none of the ISDN-Controllers to be used by NetWare Con-nect for ISDN must be used by a NetWare driver nor by any other applicationduring installation and operation of NetWare Connect for ISDN. If necessary,unload the existing drivers using the command load capi20 -d.


Installation in NetWare 5 or NetWare With NIAS 4.1


2 Installation in NetWare 5 or NetWare With NIAS 4.1

Before you install NetWare Connect for ISDN 2.1, find out which NetWareversion is installed on your NetWare server.

NetWare Connect for ISDN 2.1 contains specially adapted versions of Net-Ware Connect for ISDN for different NetWare operating systems. The installa-tion routine verifies the operating system environment of your NetWare serv-er and installs the appropriate version of NetWare Connect for ISDN for yourNetWare environment. On NetWare 5 servers and on NetWare servers withNIAS 4.1, NetWare Connect for ISDN NIAS Edition 2.1 will be installed.

This chapter describes the initial installation and automatic configuration ofNetWare Connect for ISDN 2.1 in NetWare 5 and NetWare with NIAS 4.1.

Please note that the following instructions refer to the first installation ofNetWare Connect for ISDN NIAS Edition 2.1 on a NetWare server. The re-in-stallation procedure after the software has been installed and removed isslightly different.

2.1 Before You Begin
To prepare for the installation, perform the following steps:
� In Novell NetWare 5, the NIAS 4.1 (Novell Internet Access Server) pro-gram must be installed before you begin. NIAS 4.1 is enclosed withNovell NetWare 5.

If NIAS 4.1 is not shown in the list of products installed on your server,you must install it before you install NetWare Connect for ISDN 2.1.

� After Novell NetWare has been installed, you must down the server andrestart it at least once before you proceed to install NetWare Connectfor ISDN.

� Before you begin the installation of NetWare Connect for ISDN, youmust unload the driver AIO.NLM.

� Please note that none of the ISDN-Controllers to be used by NetWareConnect for ISDN must be used by a NetWare driver nor by any other ap-plication during installation and operation of NetWare Connect forISDN. If necessary, unload the existing drivers using the commandload capi20 -d.

Netware Connect for ISDN – 2 Installation in NetWare 5 or NetWare With NIAS 4.1 13

Installation


2.2 Installation

14 Netware Connec

To install NetWare Connect for ISDN NIAS Edition 2.1, proceed as follows:

1. If you are working with NetWare 5, enter the following command at thesystem console:

nwconfig

For other NetWare versions with NIAS 4.1, enter the following commandat the system console:

load install

This loads the Novell NetWare server’s software installation program.The menu “Configuration Options” or “Installation Options” appears.

2. In this menu, select the item “Product Options”. The menu “Other In-stallation Actions” appears.

3. Select the item “View/Configure/Remove installed products”. Press“Enter”. A list of all the products installed appears.

Make sure that the product “NIAS 4.1 Novell Internet Access Server” ispresent in this list.

If the program NIAS 4.1 is not installed on your NetWare server, installit now before you install NetWare Connect for ISDN 2.1.

4. To continue with the installation, press the “Ins” key.

An input box appears prompting you to enter the path to theinstallation files. The default path shown is the floppy disk drive A:\.

Press “F3” and enter the path to the NetWare Connect for ISDN installa-tion files. The exact path to specify depends on how your CD-ROM driveis addressed.

If you have mounted the CD-ROM in NetWare, then enter the path as fol-lows:

nwci:\nwci2\disk1

If you access your CD-ROM drive as a DOS device, enter the path usinga DOS-style drive letter:

<CD-ROM drive>:\nwci2\disk1

In this case, NetWare warns you that accessing the CD-ROM through aDOS driver might cause a driver conflict. Select “Continue CD-ROM ac-cess”.

t for ISDN – 2 Installation in NetWare 5 or NetWare With NIAS 4.1

Installation


5. In the next window, choose “Install on This Server” and confirm onceagain by pressing “Enter”. The installation files are now copied.

Be patient: it may take a few seconds before the next dialog appears.

6. In the “NDS Login” dialog, enter your Administrator login name andpassword to log in to the Directory Services. Select the option “PerformLogin and Continue” and confirm these entries by pressing “Enter”.

7. In the next dialog, use the “Enter” key to select the NDS context inwhich you want to create the NetWare Connect for ISDN object. Thenbegin creating the object by pressing the “Ins” key.

Do not close this dialog by pressing the “Esc” key. This would cancelthe creation of the NWCI object.

The NWCI object is required for configuration using the Snap-In for Net-Ware Administrator. For further information on this Snap-In, please seethe section “NWCI Snap-In for NetWare Administrator (NWAdmin)” inthis manual.

8. NetWare Connect for ISDN’s configuration menu NWCICON is now load-ed:

The CD key and the configuration parameters for the ISDN-Controller(s)are entered under this menu.

9. Select the item “CD key” and enter the key found on the back of theNetWare Connect for ISDN 2.1 CD case.

10. Select “Configure ISDN-Controllers”.

One ISDN-Controller is already shown in the list with default configura-tion parameters.

NetWare Connect for ISDN Configuration Options

Configure ISDN-Controllers

Configure Global Parameters

CD-Key: [ - - - ]

Exit

List of ISDN-Controllers to load

NWCI1: AVM_B1, 150, 5, DSS1


Installation

16 Netware Connec


11. To adjust the configuration parameters for your ISDN-Controller, selectthe ISDN-Controller entry in the list and press “Enter”. The followingISDN-Controller configuration dialog appears:

12. Press “Enter”. Select the I/O address of your ISDN-Controller.

Configuration of ISDN-Controller NWCI1

I/O Base Address: 150

Interrupt Request Level: 5

ISDN D Channel Protocol: DSS1

Connected to a PBX: Disabled

Outside Line Access: 0

... Number Length: 4

Make sure no other driver (such as CAPI20.NLM) or application is ac-tive for this Controller!

13. If you are using an ISA ISDN-Controller, press “Enter” and choose anavailable interrupt level.

14. Press “Enter” to change the D channel protocol.

15. If your ISDN line is a PBX extension, press “Enter” and select “En-abled”.

16. Enter the outside dialing prefix required by your PBX.

17. Enter the minimum number of digits of a number for which the outsidedialing prefix should be added automatically.

18. To configure another ISDN-Controller, press the “Ins” key in the “List ofISDN-Controllers to load”, and repeat steps 11–17.

19. Close the ISDN-Controller configuration dialog by pressing “Esc” andproceed to configure the “Global Parameters”.


24h Maximum Physical Connection Time

per NWCI Port: Disabled

24h Maximum Charge Units: Disabled

ISDN Line Management Daily Log:

sys:etc/nwciline.*

ISDN Accounting Daily Log: sys:etc/nwciacct.*

International Dialing Prefix:


Automatic Configuration


20. For the “International Dialing Prefix”, enter the prefix dialed before thecountry code when making an international call. In most Europeancountries, this is “00”.

Close this configuration dialog by pressing “Esc”.

For detailed information on the other parameters, please see Chapter 8in the “NetWare Connect for ISDN 2.0 Installation and AdministrationGuide”.

21. Close the ISDN-Controller configuration by selecting “Exit” and then“Yes”. The following message is displayed:

Acknowledge it by pressing “Esc”.

22. Close the “Currently Installed Products” list by pressing “Esc”, then re-open it by pressing “Enter”.

NetWare Connect for ISDN 2.1 now appears in the list of installed prod-ucts as the entry “NWCI v2.1.02 NetWare Connect for ISDN NIAS Edi-tion”.

Close the NetWare server’s installation program and switch to the systemconsole.

The NetWare Communication Service Installationhas been completed.

<Press Esc to continue>

2.3 Automatic Configuration
1. At the system console, start the automatic configuration by entering:
load nwccon

2. First, set the “Connect Rights Level”. To do so, enter the name andpassword of the Administrator (Admin) or a user with equivalent rights.Confirm by pressing “Enter”.

“Connect Rights Level” refers to a container in the NDS. All users in thiscontainer and its subcontainers can access NetWare Connect for ISDNwithout additional configuration or granting user rights. By default thisis the server’s root. This means that all users entered in the NDS haveaccess to NetWare Connect for ISDN.

For detailed information on granting user rights, see the document TID1005092, available from Novell’s Web site athttp://www.novell.com.



18 Netware Connec


3. The message “Welcome to NIAS Remote Access” is displayed and theprompt “Do you want instructions?” appears. Select “No” and confirmby pressing “Enter” twice.

4. In the next dialog, “Do you have any synchronous adapters?”, select“No” if you are using only AVM ISDN-Controllers. The following messageappears: “There are no AIO ports defined. NIAS Remote Access will helpyou load the appropriate AIO driver(s).”

5. Press “Enter” again and select the AVM ISDN-Controller in the “AIODriver” list.

6. Acknowledge the message “The requested driver was loaded success-fully” by pressing “Enter”.

7. Next you are asked, “Do you need more AIO drivers?” Choose “No”.

8. To the question “Keep current modem settings,” answer “Yes”.

The next dialog prompts you: “Now select the services you want toload”. Among the services listed, CCS and RNSI are those provided byNetWare Connect for ISDN.

9. Select “CCS” and press “Enter” to activate the CAPI Connect Service.This allows every workstation in the LAN to use CAPI applications.

10. Answer “Yes” to the question “Do you want to start this service now?”

11. Then select “RNSI” and press “Enter” to configure and start the RemoteNode Service for ISDN. This service allows remote workstations(equipped with NetWAYS/ISDN or PPP over ISDN) to dial in and accessresources in the LAN. The configuration menu for RNSI appears.

12. Configure the RNSI service. At least enter an IPX address that has notyet been assigned in the “General Parameters”, and the number of yourISDN line in “Parameters for ISDN-Controller NWCI1”.

Configuration of RNSI

General Parameters

Parameters for ISDN-Controller NWCI1

Call Acceptance Database

PPP CLI List

Static RNSI Clients

Exit


Removing NetWare Connect for ISDN


A complete description of the RNSI configuration is found in this manu-al in Chapter 4, “Configuration”, Section 4.2, and in the “NetWare Con-nect for ISDN 2.0 Installation and Administration Guide”, Chapter 5,“Configuring RNSI”.

13. Close the configuration with “Exit” and confirm once again by selecting“Yes”.


Exit the configuration program and switch to the system console.

This completes the installation and configuration of NetWare Connect forISDN NIAS Edition 2.1. The software is now active.

2.4 Removing NetWare Connect for ISDN
The Novell NetWare server’s installation menu is also used to removeNetWare Connect for ISDN NIAS Edition 2.1 from the server. In the de-instal-lation process, all the components installed and configuration parametersentered during the NetWare Connect for ISDN NIAS Edition 2.1 installationprocedure are deleted.
To remove NetWare Connect for ISDN NIAS Edition 2.1, proceed as follows:

1. If NetWare Connect for ISDN NIAS Edition 2.1 is active, enter the follow-ing command at the system console:

nwcstop

2. Next, unload the driver AIO.NLM by entering the following command atthe system console:

unload aio

3. If you are working with a NetWare 5 server, start the installation menuby entering the following command at the system console:

nwconfig

For all other NetWare versions with NIAS 4.1, enter the following com-mand at the system console:

load install

The Novell NetWare server’s installation program is loaded and themenu “Installation Options” or “Configuration Options” appears.

4. Select the item “Product Options” in this menu. The menu “Other In-stallation Actions” appears.



20 Netware Connec


5. Select the item “View/Configure/Remove Installed Products”. Press“Enter”. A list of all currently installed products appears.

6. Select the entry “NWCI v2.1.02 NetWare Connect for ISDN NIAS Edition”and press the “Del” key.

7. You are prompted to confirm that you want to remove NetWare Connectfor ISDN NIAS Edition 2.1. Select “Yes”.

8. Enter the Administrator name and password. Select the entry “PerformLogin and Continue” and confirm the entries by pressing “Enter”.

NetWare Connect for ISDN NIAS Edition 2.1 is now removed from yourserver.

9. Acknowledge the message that NetWare Connect for ISDN 2.1 was suc-cessfully removed by pressing “Esc”.

Close the Novell NetWare server’s Installation program and switch to the sys-tem console.

This completes the removal of NetWare Connect for ISDN NIAS Edition 2.1.


Installation in NetWare Without NIAS and With NIAS Version 4.0 or Earlier


3 Installation in NetWare Without NIAS and With NIAS Version 4.0 or Earlier

Netware Conne

Before you install NetWare Connect for ISDN 2.1, find out which NetWareversion is installed on your NetWare server.

NetWare Connect for ISDN 2.1 contains specially adapted versions of Net-Ware Connect for ISDN for different NetWare operating systems. The installa-tion routine verifies the operating system environment of your NetWare serv-er and installs the appropriate version of NetWare Connect for ISDN for yourNetWare environment. On NetWare servers without NIAS or with NIAS ver-sion 4.0 or earlier, NetWare Connect for ISDN 2.0 will be installed to ensurecompatibility with older NetWare versions.

This chapter describes the first installation and automatic configuration ofNetWare Connect for ISDN 2.0 on a NetWare server without NIAS4.1.

Please note that the following instructions refer to the first installation ofNetWare Connect for ISDN 2.0 on a NetWare server. The procedure for re-installing the software after it has been installed and removed is slightly dif-ferent.

3.1 Before You Begin
To prepare for the installation, perform the following steps:
� After Novell NetWare has been installed, you must down the server andrestart it at least once before you proceed to install NetWare Connectfor ISDN.

� Before you begin the installation of NetWare Connect for ISDN, youmust unload the driver AIO.NLM.

� Please note that none of the ISDN-Controllers to be used by NetWareConnect for ISDN must be used by a NetWare driver nor by any other ap-plication during installation and operation of NetWare Connect forISDN. If necessary, then unload the CAPI20.NLM driver.

ct for ISDN – 3 Installation in NetWare Without NIAS and With NIAS Version 4.0 or Earlier 21

Installation


3.2 Installation

22 Netware Connec

To install NetWare Connect for ISDN, proceed as follows:

1. Enter the following command at the system console:

load install

This loads the Novell NetWare server’s software installation program.The menu “Installation Options” appears.

2. In this menu, select the item “Product Options”.

3. Depending on the NetWare version installed, the menu “Other Installa-tion Actions“ may appear. If so, then select the item “View/Config-ure/Remove Installed Products” and press “Enter”.

A list of all products installed appears.

4. Press the “Ins” key to install a new program. An input box appearsprompting you to enter the path to the installation files. The defaultpath shown is the floppy disk drive, A:\.

Depending on the NetWare version installed, either you can now enterthe path to the installation files directly, or you are prompted to pressF3 to enter a different path. The exact path to specify depends on howyour CD-ROM drive is addressed.

If you have mounted the CD-ROM drive in NetWare, then enter the pathas follows:

nwci:\nwci2\disk1

If you access your CD-ROM as a DOS device, enter the path using aDOS-style drive letter:

<CD-ROM drive>:\nwci2\disk1

Depending on the NetWare version installed, NetWare may display awarning that accessing the CD-ROM through a DOS driver could cause adriver conflict. Select “Continue CD-ROM access”.

5. Depending on the NetWare version installed, you may be prompted inthe next dialog to enter a valid administrator name and password to login to NetWare Directory Services.

Enter the administrator login name and password and confirm theseentries by pressing “Enter”.

6. In the next dialog, “Install displayed product”, confirm that you want toinstall NetWare Connect for ISDN 2.0 by selecting “Install on this Serv-er”. The installation files are now copied to the server.

t for ISDN – 3 Installation in NetWare Without NIAS and With NIAS Version 4.0 or Earlier

Installation

Netware Conne


7. At the end of the installation procedure, you are prompted to insert thelicense disk. Insert the license floppy disk included in the NetWare Con-nect for ISDN 2.1 package into the server’s floppy disk drive, and press“Enter”.

8. Acknowledge the message “The License Information was Installed Suc-cessfully” by pressing “Enter”.

9. Depending on the NetWare version installed, you may have to enter theadministrator name and password again in the “NDS Login” dialog. Se-lect the option “Perform Login and Continue” and confirm these entriesby pressing “Enter”.

10. In the next dialog, use the “Enter” key to select the NDS context inwhich you want to create the NetWare Connect for ISDN object. Thenbegin creating the object by pressing the “Ins” key.

Do not close this dialog by pressing the “Del” key. This would abort thecreation of the NWCI object.

The NWCI object is required for configuration using the Snap-In for Net-Ware Administrator. For further information on this Snap-In, please seethe section “NWCI Snap-In for the NetWare Administrator (NWAdmin)”in this manual.

11. NetWare Connect for ISDN’s configuration menu appears:

The configuration parameters for the ISDN-Controller(s) are entered un-der this menu.

12. Select “Configure ISDN-Controllers”.

One ISDN-Controller is already shown in the list with default configura-tion parameters.




Exit




Installation

24 Netware Connec


13. To adjust the configuration parameters for your ISDN-Controller, selectthe ISDN-Controller entry in the list and press “Enter”. The followingISDN-Controller configuration dialog appears:

14. Press “Enter”. Select the I/O address of your ISDN-Controller.









15. If you are using an ISA ISDN-Controller, press “Enter” and choose anavailable interrupt level.

16. Press “Enter” to change the D-channel protocol.


18. Enter the outside dialing prefix required by your PBX.

19. Enter the minimum number of digits of a number for which the outsidedialing prefix should be added automatically. Press “Esc” to close thisconfiguration menu.

20. To configure another ISDN-Controller, press the “Ins” key in the “List ofISDN-Controllers to load”, and repeat steps 14–19.


Installation

Netware Conne


Close the ISDN-Controller configuration dialog by pressing “Esc” andproceed to configure the “Global Parameters”.

21. For the “International Dialing Prefix”, enter the prefix dialed before thecountry code when making an international call. In most Europeancountries, this is “00”. Close this configuration dialog by pressing“Esc”.

For detailed information on the other parameters, please see Chapter 8in the “NetWare Connect for ISDN 2.0 Installation and AdministrationGuide”.

22. Close the ISDN-Controller configuration by selecting “Exit” and thenchoose “Yes” to end the installation procedure. The following messageis displayed:

23. Press “Enter”.

24. Close the “Currently Installed Products” list by pressing “Esc”, then re-open it by pressing “Enter”.

NetWare Connect for ISDN 2.1 now appears in the list of installed prod-ucts as the entry “Connect v2.0.50 NetWare Connect for ISDN 2.0”.

Close the Novell NetWare server’s installation program and switch to the sys-tem console.

Configuration of Global Parameters


per NWCI Port Disabled

24h Maximum Charge Units:

Disabled

ISDN Line Management Daily Log:

sys:etc/nwciline.*

ISDN Accounting Daily Log:

sys:etc/nwciacct.*

International Dialing Prefix:

Installation Completed Successfully.

<Press Esc to continue>




3.3 Automatic Configuration

26 Netware Connec

1. At the system console, start the configuration module by entering:

load nwccon

2. On NetWare 4.x servers you are prompted to specify the “ConnectRights Level”. Enter the user name and password of the Administrator(Admin) or a user with equivalent rights. Confirm by pressing “Enter”.

“Connect Rights Level” refers to a container in the NDS. All users in thiscontainer and its subcontainers can access NetWare Connect for ISDNwithout additional configuration or granting user rights. By default thisis the server’s root. This means that all users entered in the NDS haveaccess to NetWare Connect for ISDN.

For detailed information on granting user rights, see the document TID1005092, available from Novell’s Web site at http://www.novell.com.

3. The message “Welcome to NIAS Remote Access” is displayed and theprompt “Do you want instructions?” appears. Select “No” and confirmby pressing “Enter” twice.

4. Depending on the NetWare version installed, you may now see themessage “There are no AIO ports defined. NIAS Remote Access willhelp you load the appropriate AIO driver(s).” Confirm by pressing on“Enter”.

5. Acknowledge the information window that follows by pressing “Enter”again.

6. The next dialog asks, “Do you have additional licenses to add?” Answer“No” and press “Enter”.

7. A message now informs you that no AIO ports are defined. Press “En-ter”.

8. Under “What kind of serial adapter do you have installed?”, select theAVM ISDN-Controller in the list.

9. Acknowledge the message “The requested driver was loaded success-fully” by pressing “Enter”.

10. Next you are asked, “Do you need more AIO drivers?” Choose “No”.

11. To the question “Keep current modem settings,” answer “Yes”.

The following dialog prompts you: “Now select the services you want toload”. Among the services listed, CCS and RNSI are those provided byNetWare Connect for ISDN.



Netware Conne


12. Select “CCS” and press “Enter” to activate the CAPI Connect Service.This allows every workstation in the LAN to use CAPI applications.


14. Then select “RNSI” and press “Enter” to configure and start the RemoteNode Service for ISDN. This service allows remote workstations(equipped with NetWAYS/ISDN or PPP over ISDN) to dial in and accessresources in the LAN. The configuration menu for RNSI appears.

15. Configure the RNSI service. At least enter an IPX address that has notyet been assigned in the “General Parameters”, and the number of yourISDN line in “Parameters for ISDN-Controller NWCI1”.

A complete description of the RNSI configuration is found in this manu-al in Chapter 4, “Configuration”, Section 4.2, and in the “NetWareConnect for ISDN 2.0 Installation and Administration Guide”, Chapter 5,“Configuring RNSI”.

16. Select “Exit” to close the configuration and confirm by selecting “Yes”.


Exit the configuration program and switch to the system console.

This completes the installation and configuration of NetWare Connect forISDN 2.0. The software is now active.

Configuration of RNSI

General Parameters

Parameters for ISDN-Controller NWCI1

Call Acceptance Database

PPP CLI List

Static RNSI Clients

Exit

3.4 Removing NetWare Connect for ISDN
The Novell NetWare server’s installation menu is also used to removeNetWare Connect for ISDN 2.0 from the server. In the de-installation process,all components installed and configuration parameters entered during theNetWare Connect for ISDN 2.0 installation procedure are deleted.


28 Netware Connec


To remove NetWare Connect for ISDN 2.0, proceed as follows:

1. If NetWare Connect for ISDN 2.0 is active, enter the following commandat the system console:

nwcstop

2. Next, unload the driver AIO.NLM by entering the following command atthe system console:

unload aio

3. Start the installation menu by entering the following command at thesystem console:

load install

The Novell NetWare server’s installation program is loaded and themenu “Installation Options” appears.

4. Depending on the NetWare version installed, the menu “Other Installa-tion Actions” may appear. If so, then select the item “View/Config-ure/Remove Installed Products” and press “Enter”.

A list of all currently installed products appears.

5. Select the entry “Connect v2.0.50 NetWare Connect for ISDN 2.0” andpress the “Del” key.

6. You are prompted to confirm that you want to remove NetWare Connectfor ISDN 2.0. Select “Yes”.

7. In NetWare 4.x, an NDS administrator login is now required. Enter theAdministrator name and password. Select the command “Perform Log-in and Continue” and confirm the entries by pressing “Enter”.

NetWare Connect for ISDN 2.0 is now removed from your server.

8. Acknowledge the message that NetWare Connect for ISDN 2.0 was suc-cessfully removed by pressing “Esc” or “Enter”.

Close the Novell NetWare server’s installation program and switch to the sys-tem console.

This completes the removal of NetWare Connect for ISDN 2.0.


Configuration


4 Configuration

This chapter describes the configuration of NetWare Connect for ISDN NIASEdition 2.1, which is the version installed on all NetWare 5 servers and onother NetWare servers with NIAS 4.1.

The configuration procedures for NetWare Connect for ISDN 2.0 are basicallythe same as those described below for NetWare Connect for ISDN NIAS Edi-tion 2.1. For the exact descriptions of the menus and dialogs involved, how-ever, please see the Chapter 5, “Configuring NetWare Connect for ISDNServices”, and Chapter 8, “Configuring ISDN-Controllers” in the “NetWareConnect for ISDN 2.0 Installation and Administration Guide”. The “NetWareConnect for ISDN 2.0 Installation and Administration Guide” is included withNetWare Connect for ISDN.

The server module NWCCON is used to configure NetWare Connect for ISDN.This module is started by entering load nwccon at the server console.

The “Remote Access Options” menu contains the following items:

Some of these options are used in configuring NetWare Connect for ISDN,and are described in this manual. Other options in this module are used forNIAS configuration. For details please see the NetWare documentation.

Remote Access Options

Configure Ports

Configure Port Groups

Configure Synchronous Interfaces

Configure Security

Configure Services

Set Up ...

Generate Configuration Report

Please note that changes in the configuration take effect only after you haverestarted NetWare Connect for ISDN. To activate the configuration changes,stop and restart NetWare Connect for ISDN by entering the commandsnwcstop and nwcstart at the server console.

Netware Connect for ISDN – 4 Configuration 29

CAPI Connect Service


4.1 CAPI Connect Service

30 Netware Connec

The CAPI Connect Service (CCS) is simply loaded on the server, not config-ured. All settings necessary for CAPI connections, such as multiple subscrib-er number (MSN) assignments, are performed in the ISDN applications onthe workstations.

Activating CCS on the Server
Whether CCS is loaded is specified in the service settings. Enter the follow-ing command at the system console:
load nwccon

Then select the following menu command and settings:

...Set Up

Select Remote Access Services

CCS = Yes

If “Yes” appears after “CCS”, then the service is activated when NetWareConnect for ISDN is started by entering nwcstart. To deactivate the ser-vice, select “CCS” and press the “Del” key to set it to “No”. To activate a ser-vice, select it in the list and then press “Enter”.

When CCS is started, the protocols IPX and TCP/IP are bound to the service,provided they have been correctly installed and configured on the server.The corresponding message is displayed when CCS is loaded:

CCS: IP bound to <IP address> Port <port number>CCS: IPX bound to <IPX address>:1 Port <port number>

Both protocols do not necessarily have to be installed in order to activateCCS. CCS can also be used if bound to one of the two network protocols.

Make sure that the IP port 890 is not being used by any other application,since CCS listens for requests from NDC clients on this port.

In order for the workstations to use CCS, they must have Network DistributedCAPI (NDC) installed and loaded.

t for ISDN – 4 Configuration

Installing NDC on the Client


Installing NDC on the Client
To install NDC for Windows 95/98 and Windows NT, proceed as follows:
1. Select the “Run” command in the Windows Start menu.

2. Enter the following command in the command line:

<CD-ROM drive>:\SYSTEM\NDC\WINDOWS\SETUP

3. Click on “OK” to start the installation.

4. In the first dialog, select the language in which you want to run the in-stallation program. Confirm by clicking on “OK”.

The installation program’s sign-on window appears.

5. Click on “Continue”.

You can cancel the installation at any time by pressing “Esc” or by click-ing on “Cancel”.

6. Enter the path in which you want to install NDC for Windows.

The default shown is C:\PROGRAM FILES\AVM\NETWORK DISTRIBUTEDCAPI. You can change this to any other path you wish, however. Confirmyour entry by clicking on “OK”.

7. The Setup program now copies all the necessary files to the specifiedpath.

The Start menu now contains a new program group named “NetworkDistributed CAPI”. This folder contains the program shortcut “NetworkDistributed CAPI”.

8. To complete the installation, restart Windows.


Operating NDC


Operating NDC

32 Netware Connec

When NDC is started on the workstation, a user interface for login, protocolconfiguration and message output is displayed:

NDC Window in Windows 95 and Windows 98

“Connection” Dialog

This page allows the user to enter the information (user name and pass-word) that NDC will use to log in to the selected server. It may be necessaryto enter the user name with its complete context.

When the connection between NDC and CCS has been successfully estab-lished, the NDC window closes automatically. An icon in the system trayshows that NDC is loaded. The color of the icon indicates the current driverstatus:

“Protocols” Dialog Page

This dialog page allows you to choose between the protocols IPX and TCP/IP,provided both of them are correctly installed on the workstation. For TCP/IP,a manual configuration option is also available. This is necessary if the NDCclient and the server running CCS are in different segments of the LAN, sincethe broadcast packets used to search for a server automatically are not for-warded to other IP segments.

Significance of the NDC Status Icon Color in the System Tray

GRAY NDC is loaded; no connection to any server.

RED NDC is connected to a server; no CAPI applications active.

GREEN NDC is connected to a server; one or more CAPI applications are active; no ISDN connection is currently active.

Blinking The blink rhythm indicates the number of active ISDN con-nections.


NDC Automation


“Messages” Dialog Page

NDC messages are displayed on this dialog page. For further information onusing NDC, please see the detailed on-line Help (press the “F1” key or clickon the “Help” button).

NDC Automation
To simplify NDC’s operation for the user, the administrator can set up NDCso that it automatically starts and logs in to the server, and so that certainapplications are automatically started when NDC is loaded.
Starting NDC Automatically

There are two mechanisms that can be used to load NDC automatically inWindows 95/98.

Note that the first method described can also be used in Windows NT.

� Autostart

When this option is activated, NDC is automatically started by an appropri-ate entry in the Windows registry.

� On Login

When this option is activated, NDC is automatically started on each Win-dows login. Note: This method is recommended only if you are using a CAPIapplication which (a) must be loaded automatically as a system service, and(b) requires that a CAPI interface be present on starting.

Connecting NDC to a Server Automatically

If the option “Automatic Connect” is activated, NDC attempts to reestablishthe last successful connection to a server. The server name, user name andpassword needed are stored by default in the Windows Registry.

If you use the option “Automatic Connect” together with the option “On Log-in” in Windows 95/98, NDC cannot perform a user-specific server login,since the current user is not yet known at the time of connection. In thiscase, the default values for server name, user name and password aredrawn from the Windows Registry. If the Registry does not contain this infor-mation—i.e., the “default user” has not connected to a server with NDC be-fore—then the automatic connection attempt ends with an error message,and the user must enter the login information manually.


Removing NDC

34 Netware Connec


Starting CAPI Applications Automatically

To avoid problems in the start-up procedure and ensure that CAPI applica-tions are only started after NDC has been loaded, workstation users can cre-ate a special NDC Autostart program group. All applications in this folder arestarted automatically once NDC has been loaded by means of the “Automat-ic Connect” option. The folder must be named “NDC-Autostart” and be locat-ed in the appropriate subdirectory of the Windows folder: either in “Startmenu / Programs” or, for a user-specific environment, in “Profiles / <username> / Start menu / Programs”.

CAPI applications can also be started automatically without using the NDCoption “Automatic Connect”. Create a shortcut to start the programWNDC.EXE and add the argument “-x” to its command line. This shortcutthen loads NDC and starts all applications in the NDC Autostart folder.

Removing NDC
NDC can be removed from the Windows 95/98 or Windows NT system usingthe “Add/Remove Programs” applet in the Control Panel.
1. Open “Start / Settings / Control Panel / Add/Remove Programs”.

2. Select “AVM Network Distributed CAPI” in the list of installed programs.

3. Click on the “Add/Remove” button and confirm that you want to re-move NDC.

4. Click on “OK” to end the removal procedure.

Further information on the installation and operation of NDC in other operat-ing systems can be found in “Using NDC and CAPI Applications” on pp. 163–172 of the “NetWare Connect for ISDN 2.0 Installation and AdministrationGuide”.

First Test Connection with NDC and CCS
After you have installed, configured and loaded NetWare Connect for ISDNon the server and Network Distributed CAPI (NDC) on the workstation, youcan test whether CCS and NDC work properly. The program Connect32 can beused to perform a simple test connection. The program is included on theCD-ROM accompanying your AVM ISDN-Controller, in the directory \TOOLS\CONNECT.32.
Install and start Connect32. If necessary, enter the Multiple Subscriber Num-ber for the workstation to use in the Connect32 settings. Then dial a connec-tion to the AVM Data Call Center (+49-30-399 84 300).


Remote Node Service for ISDN


4.2 Remote Node Service for ISDN
Unlike CCS, RNSI is a server-based “listening” application that answers dial-in connections from outside the LAN. This means that RNSI must be config-ured on the server. The server module NWCCON includes an RNSI configura-tion menu for this purpose under “Configure Services”.
A number of options are available to ensure LAN access security and stableconnections.

For a detailed description of the complete RNSI configuration, see the “Net-Ware Connect for ISDN 2.0 Installation and Administration Guide”, pp. 79–103.

The following sections contain simple configuration examples for the RNSIservice.

Number Configuration
Appropriate configuration of ISDN numbers for the line to which RNSI is con-nected is especially important for dial-in remote access to the LAN overISDN.
The following examples describe the configuration of ISDN numbers in RNSIfor operation on an ISDN BRI line (Example 1) and on a PBX extension line(Example 2):

When the services CCS and RNSI are used simultaneously, it is important toassign the RNSI service a dedicated MSN. The assignment of a separateMSN permits exact addressing of incoming calls. If RNSI is not assigned aspecific MSN, the service automatically answers all incoming calls with theservice indicator (SI) 7, including calls intended for other CAPI-based datacommunication applications.

Example 1: Connected to a BRI Line Using DSS1 in Berlin, Germany

Global Configuration (load nwcicon, “Configure Global Parameters”)





ISDN Line Management Daily Log: sys:etc/nwciline.*


International Dialing Prefix: 00



36 Netware Connec


ISDN-Controller Configuration (load nwcicon, “Configure ISDN-Control-lers”, select controller)

RNSI Configuration (load nwccon, “Configure Services / RNSI / Parame-ters for ISDN-Controller NWCI1”)

Example 2: Connected to a PBX Extension Using DSS1 in Berlin, Germany,with DDI Number 789 and Outside Dialing Prefix 0

Global Configuration (load nwcicon, “Configure Global Parameters”)







...Number Length: 4

Configuration of RNSI Parameters forISDN-Controller NWCI1

Country Code: 49

Area Code: 030

ISDN Number: 5567892

PBX Extension:

MSN: 5567892

Expert Configuration: (view or modify)





ISDN Line Management Daily Log: sys:etc/nwciline.*


International Dialing Prefix: 00




ISDN-Controller Configuration (load nwcicon, “Configure ISDN-Control-lers, select controller)

RNSI Configuration (load nwccon, ”Configure Services / RNSI / Parame-ters for ISDN-Controller NWCI1“)

The number configured in RNSI must match the actual dial-in number of theISDN line in order for the call to be answered reliably.

RNSI can be tested using a client (such as NetWAYS/ISDN or PPP over ISDNsoftware) that is connected to another ISDN line and not connected to theLAN.





Connected to a PBX: Enabled


...Number Length: 4

Configuration of RNSI Parameters forISDN-Controller NWCI1

Country Code: 49

Area Code: 030

ISDN Number: 39976

PBX Extension: 789

MSN:



Network Protocol Configuration


Network Protocol Configuration

38 Netware Connec

Both IPX and TCP/IP connections to the LAN can be made through RNSI. Thelink between the client and RNSI is treated as a separate network segment,and is configured in the RNSI settings under ”General Parameters”.

The following illustration shows a sample configuration with IP addresses.

TCP/IP Configuration: LAN, RNSI and NetWAYS/ISDN

The WAN connection is configured as a separate TCP/IP network.

The “Address Range” for “Dynamic IP Address Assignment” offered in theRNSI configuration can be used only by clients that request an address un-der BootP. DHCP requests are not answered by NetWare Connect for ISDN,but are forwarded to a DHCP server.

AVM ISDN-Controller A1

NetWAYS/ISDN

NetWare Connectfor ISDN server

RNSI

...

...

...

...

LAN 192.168.120.1 255.255.255.0

RNSI 193.168.120.1 255.255.255.0

192.168.120.4

192.168.120.3

192.168.120.2

193.168.120.2

ISDN

AVM ISDN-Controller B1 T1 or T1-B

...................................

Charge Control
NetWare Connect for ISDN offers two ways to control connection charges: re-call request and COSO (Charge One Site Only).
When the recall request is activated, the client’s ISDN line is charged only forthe initial call to the LAN. All subsequent connections are charged to theserver. This function applies to a given ISDN-Controller, and is quite simpleto configure.

COSO allows the complete connection charges to be assigned to either endof the connection, the client or the server. This setting applies to the entireRNSI service, and requires thorough configuration work.


Charge Control


First, check which functions are supported by your client software. Bothends of the connection must support recall requests or COSO in order foryou to use these capabilities. All current Windows versions ofNetWAYS/ISDN support both of these functions.

Recall Request

When the recall request is activated, the client’s ISDN line is charged only forthe initial call to the LAN. All subsequent physical connections are chargedto the server until the logical connection is terminated.

Basic Server Configuration for Recall Request

load nwccon

Configure Services

RNSI

Parameters for ISDN-Controller NWCI


Allow Recall Request = Enabled

Basic NetWAYS/ISDN Client Configuration for Recall Request in the Call Desti-nation Settings

� "Number" Page:

– Remote Access Server = AVM NetWare Connect for ISDN

� "Costs" Page:

– Assign charges to = Caller

– Call-back request = Negotiate automatically request charge assign-ment to remote site

Recommended Configuration Options for Recall Request

The following additional parameters should be configured in order to limitthe client’s charges to one charge unit per logical connection, while ensuringthat the server only accumulates charges for connections to authorized cli-ents:


Charge Control

40 Netware Connec


Call Acceptance

Every client that dials in through an ISDN-Controller for which recall requestis “enabled” can reverse the charges so that the server is charged for theconnection. In this case it is a good idea to restrict RNSI access to authorizedclients:

load nwccon

Configure Services

RNSI

Parameters for ISDN-Controller NWCI


Call Acceptance = Only Registered Numbers: ...

All authorized clients must now be entered in the Call Acceptance Database(also found in the RNSI configuration).

Force Dialback

Because the initial call is charged to the client, it is a good idea to keep thiscall as short as possible. This is achieved by configuring a “Security Recall”.This setting can be configured for all users or for selected users:

load nwccon

Configure Security

Set Global Parameters

Default Dialback Mode =

Force Dialback to a Caller-Specified Number


Charge Control


COSO: Charge One Site Only

When this option is activated, one site, either the server or the client, ischarged for all physical connections. The following configuration exampleshows the settings for assigning all charges to the server. To assign chargesto the client, “local” and “remote” must be exchanged.

COSO is activated for the entire RNSI, not for specific ISDN-Controllers.

NetWAYS/ISDN Client Configuration for COSO in the Call destination Settings

� "Number" Page:

– Remote Access Server = AVM NetWare Connect for ISDN

� "Costs" Page:

– Assign charges to = Remote system

– Call-back request = None

� Static IP address if necessary in the network neighborhood (dynamicaddress assignment is not permitted)

� Static IPX address (dynamic address assignment is not permitted withNetWAYS/ISDN)

Server COSO Configuration

� Activate COSO for RNSI to assign charges to the server:

load nwccon

Configure Services

RNSI

General Parameters

COSO = Local

� Enter all clients in the static RNSI client list:

load nwccon

Configure Services

RNSI

Static RNSI Clients

Enter here the user name, number, CLI (D-channel caller ID), and the IPX ad-dress (and IP address if necessary) for each client.

Clients not entered or incorrectly configured here will not be able to connectreliably!


Port Configuration


42 Netware Connec

Recall must not be “disabled” at both ends.

Port Configuration
The port configuration determines how NetWare Connect for ISDN allocatesports when the RNSI service is active. Two configuration options are avail-able:
Exclusive Port Reservation

This setting specifies that a port and the B channel allocated to it remain re-served from the time the connection is first established until the logical con-nection is terminated.

The logical connection between the remote computer and NetWare Connectfor ISDN is maintained even when the physical connection is cleared downbecause no data is being transferred (Inactivity Timeout). During this time,the reserved port is blocked for other remote computers: incoming calls arerejected.

This setting ensures that a B channel is available whenever the remote com-puter needs to transfer data again.

On-Demand Port Acquirement

This setting specifies that a port and the B channel allocated to it are not re-served when the physical connection between the remote computer andNetWare Connect for ISDN is cleared down due to an inactivity timeout.

This port configuration is more flexible than exclusive port reservation, sinceit allows several remote computers to share a B channel.

The disadvantage of this option, however, is that every remote computermay not always be able to establish the physical connection to NetWare Con-nect for ISDN at all times, since it may happen that the required B channel isin use by a different remote computer.


Performance


Performance
Workstations outside the LAN must send or obtain over ISDN all data—in-cluding programs—that is not stored on the local disk drive. Since ISDN’snative throughput is far lower than that of LAN media, remote workstationsmay work slower than workstations in the LAN.
There are ways to optimize the performance of a NetWAYS/ISDN worksta-tion, however, both by taking advantage of NetWAYS/ISDN features, and byjudicious configuration and selection of other software.

NetWAYS/ISDN

� “Bundling” or Channel on Demand* uses both B channels of the ISDNline for the network connection (for 128 Kbit/s rather than 64 KBit/sthroughput). Please note that the connection charges incurred are dou-bled.

� “Compression”* enhances performance when the information beingtransferred is compressible data, such as fixed-length databaserecords, for example.

� “Header Compression” compresses network protocol header informa-tion. This option is only available in Windows versions ofNetWAYS/ISDN.*
In the DOS version of NetWAYS/ISDN, these options are available only for active ISDN-Controllers.
Configuration and Software Selection

� “Packet Burst Mode” is a Novell networking function. In Burst Mode,acknowledgments are sent not on receipt of each individual packet, butfor several packets in a “burst”. All new clients and NetWare serversfrom version 3.12 on use this function.

This function is not available for DOS clients that use NETX rather thanVLM. NetWare 3.11 servers can load this function as an additional op-tion.

� Programs should be installed locally on the workstation and notlaunched from a server-based installation. This applies to Login.exeand similar programs as well. Some programs consist not only of EXEfiles, but also files with extensions such as OVL, MSG and HLP. Thesetoo should be stored locally.

� User data should be stored on the server only if it needs to be sharedwith other users, or backed up by the server’s backup system.


Performance

44 Netware Connec


� Database and other applications should be configured so that theyonly transmit actual user data over the ISDN line, while user-specifictemporary files are stored locally rather than on network drives.

� Ports can be reserved for specific remote workstations, or sharedamong several remote computers.

PPP over ISDN

Auto-Framing

Auto-framing is currently not supported for incoming calls. For this reason,all remote PPP users who want to dial in to NetWare Connect for ISDN mustbe entered in the PPP CLI list (CLI = Calling Line Identification, the caller IDtransmitted over the ISDN D channel). This list contains the CLI numbers ofall PPP users. NetWare Connect for ISDN only recognizes PPP clients thatsend a D-channel CLI.

If a PPP client is not found in the PPP CLI list, NetWare Connect for ISDN usesthe proprietary AVM protocol, and the PPP client’s connection cannot be es-tablished.

Authentication Password Assignment

NetWare Connect for ISDN supports PAP and CHAP for the authentication ofremote PPP clients. PAP authentication can be specified for each dial-in in-terface, i.e. for each ISDN-Controller (command load nwcicon, “Config-ure Services / RNSI / Parameters for ISDN-Controllers / NWCI/Expert Config-uration”.

NetWare Connect for ISDN allows you to configure user names both for localauthentication and for authentication by the remote computer.

� Local Authentication

Before a connection is established between a remote user and NetWareConnect for ISDN, the remote client’s user name is verified with thename in the field “Remote User Name”.

� Authentication by the Remote Computer

If the remote computer requires authentication of the LAN, the local us-er name and password are presented to it for verification.

Please note that NetWare Connect for ISDN always authenticates remote RN-SI users against NDS or the NetWare bindery in addition to PAP or CHAP. Forthis reason the information in the PPP CLI list must match the NDS or bind-ery user account information exactly.


ISDN-Controller Configuration


PPP Call-back

NetWare Connect for ISDN currently supports neither recall requests in ac-cordance with RFC 1570 (LCP Extensions) nor in accordance with the Mi-crosoft Draft (Recall Control Protocol, CBCP) on connections with MicrosoftDial-up Networking.

This means that remote PPP users cannot issue a recall request in order tohave the server accept the connection charges. However, for security rea-sons it is possible to call back remote PPP clients using the “Forced Dial-back” mechanism of NetWare Connect for ISDN.

Forced Dialback is a feature of NetWare Connect for ISDN. For further infor-mation on this feature, please see the “NetWare Connect for ISDN 2.0 Instal-lation and Administration Guide”, pp. 141–149.

4.3 ISDN-Controller Configuration
The ISDN-Controller configuration is performed at the server console usingthe NWCICON module.
To start the ISDN-Controller configuration, enter the following command atthe system console:

load nwcicon

The configuration parameters for the ISDN-Controller(s) are entered under“Configure ISDN-Controllers” in this menu. General settings for NetWareConnect for ISDN are entered under “Configure Global Parameters”.




CD-Key [ - - - ]

Exit

In addition to the server module NWCICON, you can also use the NetWareAdministrator (NWAdmin) to check your ISDN-Controller settings from anyworkstation.


Setting up an ISDN-Controller


Setting up an ISDN-Controller

46 Netware Connec

To configure an ISDN-Controller, proceed as follows:

One ISDN-Controller is already shown in the list with default configurationparameters. To configure an ISDN-Controller, select it in the list and press“Enter”.

1. Press “Enter” and select the I/O address corresponding to the jumpersetting or the PCI address of your ISDN-Controller.











2. If you are using an ISA-Controller, press “Enter” and select an availableinterrupt level.

3. Press “Enter” to change the D-channel protocol.

DSS1: internationally standardized D-channel protocol (formerly calledE-DSS1 or Euro-D).

1TR6: German national D-channel protocol.

1TR6 for PRI: national D-channel protocol for use with AVM ISDN-Con-trollers T1 and T1-B.

DSS1 for PRI: international ISDN D-channel protocol for the AVM ISDN-Controllers T1 and T1-B.

Point-to-Point 1TR6: German national D-channel protocol for an AVMISDN-Controller B1 on a point-to-point line.

Point-to-Point DSS1: international D-channel protocol for an AVM ISDN-Controller B1 on a point-to-point line.


General ISDN-Controller Parameters


The mechanisms used to identify ISDN numbers are somewhat differ-ent for DDI numbers, MSNs and EAZs. If you select the protocol Point-to-Point 1TR6 or Point-to-Point DSS1, then the workstations in the LANmust use CAPI applications that support DDI numbers.

All protocols support both terrestrial and GSM connections.


5. Enter the outside dialing prefix required by your PBX (if “Connected to aPBX” is “Enabled”).

6. Enter the minimum number of digits of a number for which the outsidedialing prefix should be added automatically.

7. Confirm your entries by pressing “Enter”. The “List of ISDN-Controllersto Load” is in the foreground once again.

8. To configure another ISDN-Controller, press the “Ins” key and repeatsteps 1–7.

9. Close the ISDN-Controller configuration dialog by pressing “Esc” andproceed to configure the “Global Parameters”.

General ISDN-Controller Parameters


24h Maximum Physical Connection Timeper NWCI Port: Disabled24h Maximum Charge Units: Disabled

ISDN Line Management Daily Log: sys:etc/nwciline.*ISDN Accounting Daily Log: sys:etc/nwciacct.*International Dialing Prefix: 00

For the “International Dialing Prefix”, enter the prefix dialed before the coun-try code when making an international call. In most European countries, thisis “00”.

For detailed information on the other parameters, please see Chapter 8,“Configuring Global Parameters”, in the “NetWare Connect for ISDN 2.0 In-stallation and Administration Guide”, pp. 160–161.


Special Instructions for Configuring PCI Controllers


Special Instructions for Configuring PCI Controllers

48 Netware Connec

If you have an AVM ISDN-Controller B1 PCI installed in your server, thenplease observe the following instructions before configuring the ISDN-Con-troller:

� Older NetWare versions 3.12 and 4.10 require a patch in order to sup-port PCI controllers. In NetWare 3.12 / 4.10, verify whether the followingNLMs are loaded. Enter modules to display a list of all the NLMs load-ed.

– MSM31X.NLM and NBI31X.NLM, August 1996

– MSM.NLM and NBI.NLM, August 1996

If these modules are not present in the system, update your NetWareversion as recommended in Novell’s minimum patch list. The currentpatches can be found on Novell’s Internet site at:

http://novell.com/misc/patlst.htm#nw

Both of these NLMs have to be loaded by AUTOEXEC.NCF before Net-Ware Connect for ISDN and the network adapters. Please note the in-stallation requirements indicated in the patch documentation.

� NetWare Connect for ISDN supports interrupt sharing. In order for theISDN-Controller to share an interrupt with a network adapter, the net-work adapter must also support this feature.

4.4 Port and Security Configuration
For detailed information on port configuration, please see “Configuring thePorts” in the “NetWare Connect for ISDN 2.0 Installation and AdministrationGuide”, pp. 109–119.
For details on security configuration, see “Configuring Security” in the“NetWare Connect for ISDN 2.0 Installation and Administration Guide”, pp.121–162.

Please note that the sections on NASI and NCS do not apply to NetWare Con-nect for ISDN.


Operation


5 Operation

This chapter briefly describes the operation of NetWare Connect for ISDNNIAS Edition 2.1, which is the NetWare Connect for ISDN version installed onNetWare 5 servers and other NetWare servers with NIAS 4.1.

For instructions on operating NetWare Connect for ISDN 2.0, please see the“NetWare Connect for ISDN 2.0 Installation and Administration Guide”,Chapter 12, “Managing NetWare Connect for ISDN”, pp. 229–240.

5.1 Stopping NetWare Connect for ISDN
To stop NetWare Connect for ISDN, proceed as follows:
1. Notify all workstations that are logged in to CCS or RNSI so that theycan log out.

2. Before stopping NetWare Connect for ISDN, close any configuration andmonitoring modules that may be active, such as NWCCON, NWCICON,NWCSTAT, CCSSTAT or RNSISTAT.

3. Stop NetWare Connect for ISDN by entering the following command atthe system console:

nwcstop

This executes all the commands in the file NWCSTOP.NCF, which is createdduring the NetWare Connect for ISDN installation and automatically updatedon each configuration change.

5.2 Starting NetWare Connect for ISDN
To start NetWare Connect for ISDN, enter the following command at the sys-tem console:
nwcstart

This executes all the commands in NWCSTART.NCF. This file starts both thedrivers and the services enabled. The file NWCSTART.NCF is created duringthe NetWare Connect for ISDN installation, and automatically updated oneach configuration change.

Netware Connect for ISDN – 5 Operation 49

Monitoring the Remote Node Service for ISDN


5.3 Monitoring the Remote Node Service for ISDN

50 Netware Connec

The server module RNSISTAT is supplied to allow you to monitor the status ofRNSI. Start the module by entering the following command at the systemconsole:

load rnsistat

For a detailed descriptions of the RNSI status display, please see “ViewingRNSI Status” in the “NetWare Connect for ISDN 2.0 Installation and Admin-istration Guide”, pp. 249–250.

5.4 Monitoring the CAPI Connect Service
The server module CCSSTAT is supplied to allow you to monitor the status ofCCS. Start the module by entering the following command at the system con-sole:
load ccsstat

In addition to informing you how long CCS has been active, the display alsocontains all other information about the current status of the service:

� Statistics on CCS since the last start, including accumulated charges,available ports, clients logged in and the number of outgoing calls.

� CCS’s current addresses.

� The names and current connections of the users currently logged in toCCS.

For a detailed description of the CCS status display, please see “ViewingCCS Status” in the “NetWare Connect for ISDN 2.0 Installation and Adminis-tration Guide”, pp. 248–249.

t for ISDN – 5 Operation

Monitoring the ISDN Interface


5.5 Monitoring the ISDN Interface
The server module NWCSTAT is supplied to allow you to monitor the status ofthe ISDN interfaces. Start the module by entering the following command atthe system console:
load nwcstat

The “Status Options” menu is displayed:

To display the ISDN interface status screen, select the item “Display Port Sta-tus”.

Status Options

Display Port Status

Display Service Status

Display Alerts

Display Audit Trail

Exit

For detailed information on the ISDN interface status screen, please see“Monitoring Port Status” in the “NetWare Connect for ISDN 2.0 Installationand Administration Guide”, pp. 243–246.

5.6 Connection and Accounting Logs
For information on the connection and accounting logs, see “Writing DailyISDN Log Files” in the “NetWare Connect for ISDN 2.0 Installation and Ad-ministration Guide”, pp. 254–256.
Netware Connect for ISDN – 5 Operation 51

Connection and Accounting Logs

52 Netware Connec


t for ISDN – 5 Operation

Information for Administrators


6 Information for Administrators

This chapter provides the system administrator with additional informationabout NetWare Connect for ISDN functions and configuration.

6.1 NDS and NetWare Connect for ISDN
NetWare Connect for ISDN’s NDS support, described below, is available onlyon NetWare 4.1 and later servers with NDS. This object is not available inNetWare versions 3.12 and 3.2.
NDS Extension
During the installation of NetWare Connect for ISDN, two new objects are cre-ated in the NDS tree: the CONNECT object and the NWCI object.
The CONNECT object is located in the same container as the server objectwhich represents the server on which NetWare Connect for ISDN was in-stalled.

The name of the object is CONNECT_<server name>.

The NWCI object is the object used in configuring the NetWare Connect forISDN by means of the NetWare Administrator. The location of this object inthe NDS tree is determined during the installation by the administrator per-forming the procedure. The object is named NWCI_<server name> and is sym-bolized by a special icon.

Snap-In for NetWare Administrator (NWAdmin)
The Snap-In for NetWare Administrator makes it possible to configure basicRNSI parameters and to display the ISDN-Controller configuration from anyWindows workstation.
Prerequisites for Use of the Snap-In

Make sure the following components are present:

� NDS object “NWCI_<server name>”

This object is created in the NDS tree by the administrator during theNetWare Connect for ISDN installation process.

� NetWare Administrator, version 4.11.11 or higher

The NetWare Administrator (NWAdmin) is a component of NetWare 4.xand 5.x.

Netware Connect for ISDN – 6 Information for Administrators 53

Snap-In for NetWare Administrator (NWAdmin)

54 Netware Connec


� NWSNAPIN installed on the workstation

The Snap-In is installed on the workstation by starting Setup.exe in the di-rectory SYS:SYSTEM\NWCI\NWSNAPIN. The Setup program copies some ad-ditional DLL files to the Windows folder and enters the necessary keys in theRegistry.

To perform NetWare Connect for ISDN configuration, start the NetWare Ad-ministrator and open the container in which the NWCI object is located. Thendouble-click on the object icon to access the service and ISDN-Controllerconfiguration.

Service Configuration

The service configuration contains “Global” parameters that apply to all Net-Ware Connect for ISDN services. These include security limits for NWCI portsand settings for the accounting and connection logs.

Settings specific to RNSI are also available under “RNSI General”. These in-clude all parameters for configuring RNSI network addresses, all filter andspoofing settings, and all RNSI port use, charge control and call-back set-tings.

Please note that configuration changes only take effect after NetWare Con-nect for ISDN has been restarted. Stop and restart NetWare Connect for ISDNby entering the commands nwcstop and nwcstart at the server console.

ISDN-Controller Configuration

The ISDN-Controller configuration in the NetWare Administrator Snap-In pro-vides a dialog to set configuration parameters for each ISDN-Controller in-stalled.

In the “Global” settings, the interrupt level, I/O address and D-channel pro-tocol of each ISDN-Controller are displayed. These parameters can only bechanged at the server console: they can only be viewed here, not edited.

The configuration settings for PABX extension lines can also be changed inthis dialog. The ISDN-Controller can be enabled for connection to a PBX ex-tension (see also Section 4.3, “ISDN-Controller Configuration”, in this manu-al).

If the PBX setting is activated on the server, the corresponding setting in theNDC clients’ CAPI applications must be disabled so that the outside dialingprefix is not added to outgoing numbers twice.

Controller-specific parameters for RNSI number configuration are accessibleunder “RNSI General”. The values entered here are necessary in order forRNSI to answer incoming calls correctly, and are sent to the client as the call-er-specified number to use when the call-back function is activated.

t for ISDN – 6 Information for Administrators

Internal Mechanisms and Further Configuration and Operating Instructions


Complete information on these settings can be found in Section 4.2 of thismanual, “Remote Node Service for ISDN”, and in “Configuring RNSI Param-eters for Each ISDN-Controller” in the “NetWare Connect for ISDN 2.0 Instal-lation and Administration Guide”, pp. 90–93.

Please note that configuration changes only take effect after NetWare Con-nect for ISDN has been restarted. Stop and restart NetWare Connect for ISDNby entering the commands nwcstop and nwcstart at the server console.

6.2 Internal Mechanisms and Further Configuration and Operating Instructions
A description of the port allocation mechanisms for incoming and outgoingconnections can be found in the sections “Dynamic Port Allocation and PortSharing” and “ISDN-Controller Mapping for Dial-Out and Dial-In” in the “Net-Ware Connect for ISDN 2.0 Installation and Administration Guide”, pp. 37–39.
For detailed information on the forwarding of incoming connections in theLAN, please see the “NetWare Connect for ISDN 2.0 Installation and Admin-istration Guide”, sections “Forwarding Incoming Calls to Applications”, pp.37–39, and “Dialing in to NetWare Connect for ISDN Services”, pp. 214–227.

For instructions on operating several NetWare Connect servers in a WANconnected by dial-up lines, see the “NetWare Connect for ISDN 2.0 Installa-tion and Administration Guide”, section “More Than One NetWare Connectfor ISDN Within a WAN Connected over ISDN”, pp. 207–208.

All components of NetWare Connect for ISDN are ready for the transition tothe year 2000, as are the AVM ISDN-Controllers B1, T1 and T1-B.

Please note, however, that NetWare Connect for ISDN builds on componentsof the NetWare operating system which may be affected by Year 2000 prob-lems. For further information from Novell on Year 2000 conformance, see:

http://www.novell.com/p2000/product.html

Netware Connect for ISDN – 6 Information for Administrators 55

Diagnostics

56 Netware Connec


The following list contains Year-2000 recommendations for all current Net-Ware Connect for ISDN versions.

Year-2000 Recommendations for All NetWare Connect for ISDN Versions

Product Name Version Revision Recommendation

NWC for ISDN 1.0 all Upgrade to NWC for ISDN 2.0Revision 2.0.45 or later.

NWC for ISDN 2.0 2.0.43or older

Upgrade to Revision 2.0.45or later.

NWC for ISDN 2.0 2.0.45or later

This release is Year 2000 ready.

NWC for ISDN 2.1 2.1.01or later

This release is Year 2000 ready.

NetWare/Intranetware

all See Novell’s recommendations.

ISDN-Controller B1, T1, T1-B1

all Year 2000 ready.

6.3 Diagnostics

Testing the ISDN Line
If problems arise in establishing connections through NetWare Connect forISDN, it is a good idea to test the ISDN-Controller and the ISDN line at thelowest level, in DOS. Drivers and testing tools for this purpose are suppliedon the “NetWare Connect for ISDN 2.1” CD in the directory \UTILITY.
For further information, see “Testing ISDN Access” in the “NetWare Connectfor ISDN 2.0 Installation and Administration Guide”, p. 257.

Support: NWCIINFO.NLM
NWCIINFO.NLM is a special tool to document the installation and configura-tion of the NetWare Connect for ISDN server.
For further information on NWCIINFO.NLM, see “NWCIINFO.NLM” in the“NetWare Connect for ISDN 2.0 Installation and Administration Guide”, p.259.

System and Error Messages
A list of the most important system and error messages can be found in“System and Error Messages” in the “NetWare Connect for ISDN 2.0 Instal-lation and Administration Guide”, pp. 275–283.
t for ISDN – 6 Information for Administrators

Documents

NetWare Connect for ISDN 2 - AVM · and efficiency. NetWare Connect for ISDN is a software product that inte-grates ISDN in a Novell network. In purchasing NetWare Connect for ISDN