#EDIR DATA# LANG=CISDN User's GuideDocument Number 007-2376-002ContributorsWritten by Amy SmithProduction by Derrald VogtIllustration by Derrald VogtTechnical Contributions by Michael Wang, Wayne Mesard, Charles Marker, and Vernon Schryver©Copyright 1994, Silicon Graphics, Inc.name='mdash' font=symbol charset=fontspecific code=190 descr='[mdash]' All Rights ReservedThis document contains proprietary and confidential information of Silicon Graphics, Inc. The contents of this document may not be disclosed to third parties, copied, or duplicated in any form, in whole or in part, without the prior written permission of Silicon Graphics, Inc.Restricted Rights LegendUse, duplication, or disclosure of the technical data contained in this document by the Government is subject to restrictions as set forth in subdivision (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 52.227-7013 and/or in similar or successor clauses in the FAR, or in the DOD or NASA FAR Supplement. Unpublished rights reserved under the Copyright Laws of the United States. Contractor/manufacturer is Silicon Graphics, Inc., 2011 N. Shoreline Blvd., Mountain View, CA 94039-7311.ISDN User's GuideDocument Number 007-2376-002Silicon Graphics, Inc.Mountain View, CaliforniaSilicon Graphics and IRIS are registered trademarks and IRIX is a trademark of Silicon Graphics, Inc. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd. Ethernet is a registered trademark of Xerox Corporation.LBL="1"Introduction to ISDNISDN (Integrated Services Digital Network) lets you communicate with other systems and networks via a high-speed telephone line just as you communicate with other systems and networks via an Ethernet cable. Once you set up and establish an ISDN connection, you can use the same UNIX commands and Indigo Magic Desktop methods to log in to other systems and to transfer files.Your Indy comes standard with built-in hardware that supports ISDN connections, and system software that supports ISDN. This guide shows you how to order additional required hardware and services, set up your connection, and use ISDN. Specifically, it contains these chapters:IDREF="13662" TYPE="TITLE"Chapter 2, "Setting Up an ISDN Connection," contains detailed information on setting up the hardware, software, and services needed to use ISDN. It also contains troubleshooting information.IDREF="16965" TYPE="TITLE"Chapter 3, "Using ISDN," shows you how to use PPP (Point-to-Point Protocol) to start and stop an ISDN connection, and how to log in and transfer files between your system and systems on the ISDN network. IDREF="60345" TYPE="TITLE"Chapter 4, "ISDN Reference," contains technical background information on ISDN and advanced information on more complex ISDN configurations.In addition, a glossary of terms appears at the end of the guide.LBL="2"ID="13662"Setting Up an ISDN ConnectionThere are several steps involved in setting up your Indy so it can communicate across an ISDN connection. It may take several weeks to set up the connection, depending on how quickly you can obtain the appropriate hardware and services from your local telephone company. This chapter guides you through all the steps in the process. Be sure to read IDREF="84340" TYPE="TITLE""Prerequisites for Using ISDN" before any other section; if your situation does not satisfy the prerequisites, you will not be able to use an ISDN connection.This chapter contains these sections:IDREF="84340" TYPE="TITLE""Prerequisites for Using ISDN"IDREF="79672" TYPE="TITLE""Ordering ISDN Services and Hardware"IDREF="61065" TYPE="TITLE""Setting Up the ISDN Hardware"IDREF="69994" TYPE="TITLE""Setting Up the ISDN Software"IDREF="38444" TYPE="TITLE""Turning On and Testing the ISDN Connection"IDREF="15017" TYPE="TITLE""Letting Other ISDN Systems Access Your System"IDREF="79935" TYPE="TITLE""Troubleshooting the ISDN Connection"LBL="" HELPID=""ID="84340"Prerequisites for Using ISDNAn ISDN connection is basically a network connection between two systems that transfers information over a high-speed telephone line rather than an Ethernet cable. Your Indy has the appropriate internal hardware to support ISDN connections, but your situation and location must have these characteristics:The remote system that you plan to connect to using ISDN must already be set up to use ISDN; that is, it must already have ISDN hardware, software, and services in place. See also IDREF="70024" TYPE="TITLE""Requirements for Remote ISDN Systems."Your system must be geographically located near a telephone switching office that offers ISDN services. Typically your system must be within 2 or 3 miles (3 or 5 kilometers) of such an office. See also IDREF="79672" TYPE="TITLE""Ordering ISDN Services and Hardware."You need a telephone jack. If you have a standard jack that supports only one telephone number, your local telephone company can easily split the jack so it can support both the existing telephone number and a new, dedicated ISDN telephone number.If you do not have a jack, or you already use two telephone numbers on your existing jack, you can have the telephone company or an electrician install a new telephone wire and jack.LBL="" HELPID=""ID="79672"Ordering ISDN Services and HardwareIf your situation meets all the prerequisites listed in IDREF="84340" TYPE="TITLE""Prerequisites for Using ISDN," you are ready to order your services and hardware.LBL="" HELPID=""ID="10088"Ordering ISDN ServicesContact your telephone company, and go through the list of questions and ordering requests in this section with a person qualified to set up ISDN services.Make sure your telephone company can provide BRI (Basic Rate Interface) ISDN services to your location. Typically your system must be within 2 or 3 miles (3 or 5 kilometers) of a telephone switching office that offers ISDN.Tell the telephone company that you want a BRI (not PRI) ISDN connection.When they ask about the B channels and D channel, tell them:You want circuit-switched data on both B channels. You do not want X.25 (also called packet-switched data); you do not want voice or any of the additional voice-related services (such as call hold, consultation hold, 3-way conference, etc.).You want standard signalling on the D channel. You do not want X.25 (also called packet-switched data), or any additional services.U.S. Customers Only: Ask what type of switch hardware and switch software your telephone company uses. It will be one of four types:5ESS hardware running 5ESS Custom software5ESS hardware running 5ESS National ISDN 1 software (also called NI1 software)DMS100 hardware running BCS level 31, 32, 33, or 34 (Protocol Version 1) softwareDMS100 hardware running BCS level 35 or higher (Protocol Version 2) software (also called DMS100 National ISDN 1 or NI1 software).The telephone company representative may know only the hardware or the software type, but not both. If this is the case, ask the representative to research both the software and hardware types.U.S. Customers Only: The telephone company will request information about your Indy (they may refer to it as an ISDN terminal, Customer Premise Equipment (CPE), or a Terminal Adapter (TA)). The information they need about the Indy varies depending on the type of switch software the telephone company uses. NoteSome telephone companies will not require the detail listed here; they will automatically assume you have a type D terminal, which provides you with a superset of the services you need.The list below shows the switch software type and the appropriate information.5ESS CustomTerminal Type: ENumber of Call Appearances: NoneDisplay: NoIdle Call Appearances: NoneAutohold: NoOnetouch: NoNo. of Circuit-Switched Data Channels: 2EKTS: No5ESS NI1Terminal Type: ANumber of Call Appearances: NoneDisplay: NoIdle Call Appearances: NoneAutohold: NoOnetouch: NoNo. of Circuit-Switched Data Channels: 2EKTS: NoDMS100 BCS level 31, 32, 33, or 34 (Protocol Version 1)Dynamic TEI: YesMaximum number of Keys: 3Ringing Indicator: NoEKTS: NoDMS100 NI1Dynamic TEI: YesMaximum number of Keys: 3Ringing Indicator: NoEKTS: NoU.S. Customers Only: The telephone company may ask these additional questions:Does the system have automatic or fixed TEI (Terminal End Identifier)? It has automatic TEI.Is the system functional or stimulous? It is stimulous. (This applies only if the telephone company's hardware is DMS100.)German Customers Only: Ask the telephone company whether their switch runs 1TR6 or NET3 software.Ask for your ISDN telephone number(s) and SPID (Service Profile Identifier) number(s). The information the telephone company provides varies depending on the type of switch software it uses. The list below shows the switch software type and the information you need.Write down your switch software type and the telephone number(s) and, if necessary, SPID number(s).5ESS Custom: One telephone number. The telephone company may provide you with a corresponding SPID number; you will not need to know this number to set up your ISDN software.5ESS NI1, DMS100 BCS level 31, 32, 33, or 34 (Protocol Version 1), or DMS100 NI1: Two telephone numbers and two corresponding SPID numbers.NTT, 1TR6, or NET3 (also known as Euro-ISDN or DSS-1): One telephone number.This should be enough information for the telephone company to set up your ISDN service. If they need more information about your system, see IDREF="91829" TYPE="TITLE""Technical Background" for more detailed technical information.Before you end your conversation with the telephone company, ask whether you're speaking with the correct person to:Order addtional hardware from the telephone company, or from another vendor that the telephone company recommends. See IDREF="42052" TYPE="TITLE""Ordering ISDN Hardware."Set up long distance calling service for the line. You must do this if you plan to connect to systems that are located outside of your local telephone area code.LBL="" HELPID=""ID="42052"Ordering ISDN HardwareIf you live in Japan or Germany, once you've ordered your ISDN services as described in IDREF="10088" TYPE="TITLE""Ordering ISDN Services," your local telephone company automatically ships you the additional ISDN hardware you need to connect to a telephone jack.If you live in the U.S., you need to explicitly order additional ISDN hardware from your local telephone company, or from another vendor that your telephone company recommends. When you order the hardware, make sure it includes all the appropriate cables. The list below itemizes every piece of equipment and cabling necessary to connect your Indy to a standard telephone jack.An NT1 device: This small device (about the size of a standard VHS video tape) converts the standard 2- or 4-wire telephone jack signal (also called a `U Interface') to an 8-wire ISDN signal (called an `S/T Interface').A power supply unit for the NT1 device: This is roughly the same size as the NT1 device; it supplies power from a standard AC outlet to the NT1 device.A power cable: This connects the power supply unit to the AC outlet. Typically this cable is already connected to the power supply unit.A short, straight-through RJ-45 cable: This connects the NT1 device to the power supply unit (this usually is included with the power supply unit).A longer straight-through RJ-11 cable: This is the standard cable that you use to connect a telephone to a standard jack. With an ISDN connection, you use it to connect the power supply or NT1 device to the jack.A 5- to 7-foot straight-through RJ-45 cable: This 8-wire, high-speed cable with RJ-45 connectors on both ends connects the NT1 device to your Indy.NoteThis is not the same type of cable that you use for a 10BaseT connection.If your telephone company does not supply this cable, you can order it from a number of vendors, including Silicon Graphics, Inc. (part number X5 ISDN) and Inmac.When all your hardware arrives and your ISDN services are ready (see IDREF="10088" TYPE="TITLE""Ordering ISDN Services"), go on to IDREF="61065" TYPE="TITLE""Setting Up the ISDN Hardware."LBL="" HELPID=""ID="61065"Setting Up the ISDN HardwareThere are a wide variety of NT1 devices available in different countries. This section shows a sample setup that consists of an Indy, a Northern Telecom Meridian NT1 device, a Northern Telecom Meridian power supply unit for the NT1, and a telephone wall jack.NoteThese instructions are more current and complete than those in the Indy Owner's Guide.Regardless of the type of NT1 device you have, the connection works in this way:The wall jack supplies a standard, RJ-11 telephone jack; this is called the U interface.Connect one end of a standard, 4-wire RJ-11 cable to the wall jack (U interface), and connect the other end to the RJ-11 port on the power supply unit (if you have one) or the NT1 device. This port should be labelled with a `U'.If you have both a power supply unit and an NT1 device, connect the RJ-11 cable to the wall jack and to the U port on the power supply, then connect the very short RJ-45 cable to the jacks labelled with a U and a solid and dashed line on both the power supply unit and the NT1 device. Also connect the power cable on the power supply unit to a standard A/C outlet.Connect one end of a straight-through, 8-wire RJ-45 cable to either of the RJ-45 ports on the NT1 that are labelled `S/T'. Connect the other end of this cable to the ISDN port on the Indy, which is labelled with an icon of a telephone.NoteOn a new Indy, the ISDN port will be covered with a red sticker. Remove the sticker, then connect the cable.IDREF="80665" TYPE="GRAPHIC"See Figure 2-1 for a setup that includes both an NT1 device and a power supply unit.FILE="NT1_on_indy.ai" POSITION="INLINE" SCALE="FALSE"LBL="2-1"Figure 2-1 ID="80665"A physical ISDN connection between an Indy, an NT1 device, a power supply unit, and a telephone jack.When all the hardware is set up, see IDREF="69994" TYPE="TITLE""Setting Up the ISDN Software."LBL="" HELPID=""ID="69994"Setting Up the ISDN SoftwareOnly the Administrator of a system (the person who knows the root password) can set up ISDN software. It involves these three steps:Install the UUCP, PPP, and ISDN software. This online book is part of the ISDN software, so UUCP, PPP, and ISDN are already installed.Configure system files for basic ISDN use; see IDREF="36352" TYPE="TITLE""Setting Up Basic ISDN."Build a list of remote ISDN systems and networks that you want to access; see IDREF="66072" TYPE="TITLE""Building a List of Remote ISDN Systems and Networks."Once your ISDN software is set up and you are able to access other systems, you can also provide your ISDN information to remote systems so they can access your system; see IDREF="15017" TYPE="TITLE""Letting Other ISDN Systems Access Your System."LBL="" HELPID=""ID="36352"Setting Up Basic ISDNTo set up basic ISDN, you need to know what type of switch software your telephone company offers, and, for 5ESS NI1, DMS100 BCS level 31, 32, 33, or 34 (Protocol Version 1), or DMS100 NI1, you need two telephone numbers and their corresponding SPID numbers. You should have obtained this information in IDREF="10088" TYPE="TITLE""Ordering ISDN Services."Also, you need a hostname and IP address for your system. You can get this information from the network administrator of the network to which you plan to connect.To set up basic ISDN, the Administrator should follow these steps:If you haven't already logged in as root through a shell window, do so now.Choose "Unix Shell" from the Desktop toolchest.Position your cursor within the new window and type:login rootIf a prompt for a password appears, type the password then press . If a prompt appears but the root account has no password, just press .Assign your system a hostname and IP address, and turn on basic networking.In the shell window, type:/usr/Cadmin/bin/cnetIn the window that appears, enter your hostname in the field labeled This interface's name and enter the IP address in the field labeled IP address, then click the box next to Turn on networking for this port.Click the OK button.If you changed your hostname or IP address, several notifiers appear. Click OK in all the notifiers except for the one that asks if you want to restart the system; click Cancel in this notifier, since you'll restart the system later on.NoteIf you see an error notifier that reports that there is a problem with your Ethernet connection, click the Snooze button in the notifier. In the next step you'll turn off this message.Click the Cancel button in the Network Setup tool to dismiss its window.If you do not have an Ethernet cable connected to your system (if ISDN is the only type of networking your're using), turn off the message by hand for now, and create a startup script that will suppress unnecessary error messages that inform you that the cable is disconnected. Type:/usr/etc/ifconfig ec0 downcd /etc/rc2.d(Type the following command on one line, not two.)ln -s ../init.d/isdn.no_ethernet S31isdn.no_ethernetNoteIf you plan to use the Ethernet connection and the ISDN connection simultaneously, do not issue these commands. See IDREF="97595" TYPE="TITLE""Using ISDN and Other Networks Simultaneously."Edit the file /etc/config/isdnd.options to give the system the information it needs about the switch software.Open the file with a text editor such as jot by typing:jot /etc/config/isdnd.optionsFor detailed information on using the jot text editor, choose a topic from its Help menu.This file consists of several lines of information that tell you how to edit the file correctly; each line starts with a pound sign (#). Remove the pound sign from the line in the file that corresponds to your switch software type (see IDREF="10088" TYPE="TITLE""Ordering ISDN Services" if you're unsure of your switch software), and edit the line if necessary.For 5ESS custom, the only line in the file without a leading pound sign is:-t 5ESSFor DMS100 BCS 31, 32, 33, 34 (Protocol Version 1), the only line without a leading pound sign is:-t DMS100 -s -s -n -n Where and are your first and second SPID numbers, and and are your first and second 7-digit (do not use a 1 or an area code) phone numbers (or directory numbers). For example, for a system whose SPID numbers are 415115400101 and 415115403939, and whose phone numbers are 1154001 and 1154039, the line looks like this:-t DMS100 -s 415115400101 -s 415115403939 -n 1154001 -n 1154039For 5ESS NI1 or DMS100 BCS 35 or higher (Protocol Version 2), the only line without a leading pound sign is:-t NI1 -s -s -n -n Where and are your first and second SPID numbers, and and are your first and second 7-digit (do not use a 1 or an area code) phone numbers (or directory numbers). For example, for a system whose SPID numbers are 415115400101 and 415115403939, and whose phone numbers are 4151154001 and 4151154039, the line looks like this:-t NI1 -s 415115400101 -s 415115403939 -n 1154001 -n 1154039For 1TR6 (Germany only), the only line without a leading pound sign is:-t 1TR6For NET3 (Europe, Germany, and UK), the only line without a leading pound sign is:-t NET3For NTT (Japan),the only line without a leading pound sign is:-t NTTSave your changes and quit the editor.Turn on the basic ISDN software by typing:/etc/chkconfig isdnd onThe basic ISDN software is set up. Go on to IDREF="66072" TYPE="TITLE""Building a List of Remote ISDN Systems and Networks."LBL="" HELPID=""ID="66072"Building a List of Remote ISDN Systems and NetworksOnce your basic ISDN software is set up (see IDREF="36352" TYPE="TITLE""Setting Up Basic ISDN"), you can build a list of the systems and networks that you want to access using your ISDN connection.The instructions in this section assume that your Indy is not connected to any other type of network; that is, they assume that the only networking cable that is connected to your system is an ISDN cable, and that no other network interface software is in use on your system. If this is not the case, see IDREF="97595" TYPE="TITLE""Using ISDN and Other Networks Simultaneously."NoteIf you are connecting to a large network, the network's administrator may refer to the remote system as a network hub, and will supply you with a hubname rather than a hostname. In this case, enter the hubname everywhere these instructions ask you to enter a hostname.For each system you need:the system's hostname (hubname)the system's IP addressa login account on the systema password for your login account on the systemthe ISDN telephone number(s) of the systemTo build the list, the Administrator should follow these steps:If you haven't already logged in as root through a shell window, do so now.Choose "Unix Shell" from the Desktop toolchest.Position your cursor within the new window and type:login rootIf a prompt for a password appears, type the password then press . If a prompt appears but the root account has no password, just press .Make sure your /etc/hosts file contains the hostname and IP address of each remote ISDN system.When a hostname contains more than seven characters (for example, mars.foo.bar.com, a typical hostname that includes a domain, contains sixteen characters), you need to add both the full hostname and a shorter name (seven characters or less, also called a hostname alias).Open the file with a text editor such as jot by typing:jot /etc/hostsFor detailed information on using the jot text editor, choose a topic from its Help menu.Look for a line that contains the IP address and hostname of each system. If you find lines for each system, and if the hostname is seven characters or less or the line contains both the full hostname and a short enough hostname alias, go on to step 3. If you do not find one or more lines, add one line for each system to the file. First type the IP address (4 numbers separated by periods), followed by a and the full hostname, followed by a space and the hostname alias (if necessary). For example, for a system named mars.foo.bar.com with an IP address of 192.0.2.8, type:192.0.2.8 mars.foo.bar.com marsIf the line already exists but the hostname is too long, just add a hostname alias to the end of the line.NoteThe hostname alias that you choose must be unique in the /etc/hosts file. When you decide on an alias, search the file (in jot, choose "Search Forward" from the Select menu) to make sure the alias is not already in use.Save your changes and quit the editor.Add information about each remote ISDN system to the /etc/ppp.conf file. This file contains several lines of text that describe how to edit the file, and indicates where in the file you should add your entries.NoteThe edits shown here provide you with a basic setup. For a more advanced setup (for example, one that optimizes connection speed or provides network security) see IDREF="58442" TYPE="TITLE""Using Advanced ISDN Configuration Options."Open the file with a text editor such as jot by typing:jot /etc/ppp.confFor each system, you must supply three lines of information that include the seven-character or less hostname (often this is the hostname alias) of the system, and the name and password of your user login account on that system. You also request a static network route using add_route (see also IDREF="81465" TYPE="TITLE""Changing Network Routing"). Each entry has this form: send_username= send_passwd= add_routeFor example, a three-line entry that lets you access the remote host mars.foo.bar.com (whose alias is mars) using your user name joe with a password of isdn would look like this:mars send_username=joe send_passwd=isdn add_routeAdd a three-line entry for each system. Separate each entry with a blank line to make the file more readable.If your Internet Service Provider or network adminstrator wants you to add any additional lines, do so now. A typical entry would be to add a line after add_route that reads:localhost=0This allows the Internet Service Provider to assign a temporary IP address for your system whenever you make a connection.Save your changes and quit the editor.Add the telephone number(s) of each ISDN system to the /etc/uucp/Systems file.Make a backup copy of the file in case you need a default version in the future.cp /etc/uucp/Systems /etc/uucp/Systems.backupChange the permissions on the original file so you can edit it by typing:chmod u+w /etc/uucp/SystemsOpen the file with a text editor such as jot by typing:jot /etc/uucp/SystemsFor each system, you must supply one line of information for each of the system's telephone numbers. If the system has one telephone number, you'll add one line; if it has two telephone numbers, you'll add two lines. Each line includes the seven-character or less hostname (often this is the hostname alias) of the system, the rate at which the connection will transfer data (typically 56 Kbits/second in the U.S., 64 Kbits/second elsewhere; for information on transferring at 64 Kbits within the U.S., see IDREF="72532" TYPE="TITLE""About Transfer Rates"), and a telephone number.Each line has the form shown below. NoteIn the actual file, do not break the line as shown here; each line starts with the hostname and ends with the word CONNECTED.Any ISDN 38400 "" "" ISDNCALL[] CONNECTEDFor example, the one-line entry that lets you access the remote host mars.foo.bar.com (whose alias is mars), which is located in the U.S. and has a single telephone number of 415-115-4001 would look like this:mars Any ISDN 38400 "" "" ISDNCALL[56]14151154001 CONNECTEDIf the system were located outside of the U.S. (where the line carries 64 Kbits/second), the entry would look like this:mars Any ISDN 38400 "" "" ISDNCALL[64]14151154001 CONNECTEDIf the system had two telephone numbers (which means the system's switching software is DMS100 or NI1), for example, 415-115-4001 and 415-115-4040, the entry would look like this:mars Any ISDN 38400 "" "" ISDNCALL[56]14151154001 CONNECTEDmars Any ISDN 38400 "" "" ISDNCALL[56]14151154040 CONNECTEDAdd a one- or two-line entry for each system. Separate each entry with a blank line.Make sure you leave a space between each item in each line (i.e., in the last example, leave a space after mars, Any, ISDN, 38400, both sets of double-quotes ("" ""), and ISDNCALL[56]14151154001).Save your changes and quit the editor.Unless otherwise advised by your Internet Service Provider or network administrator, turn off the active routing daemon(s) (for more information, see IDREF="81465" TYPE="TITLE""Changing Network Routing") by typing:/etc/chkconfig routed off/etc/chkconfig gated offWhen you have provided the above information for at least one remote system, you can turn on your ISDN connection and test it. Go on to IDREF="38444" TYPE="TITLE""Turning On and Testing the ISDN Connection."LBL="" HELPID=""ID="38444"Turning On and Testing the ISDN ConnectionOnce you have set up the basic ISDN software (see IDREF="36352" TYPE="TITLE""Setting Up Basic ISDN") and you have given your system information on how to access at least one remote system (see IDREF="66072" TYPE="TITLE""Building a List of Remote ISDN Systems and Networks"), you can turn on and test the connection. NoteIn the middle of this procedure you must restart your system. Please read this entire section before restarting the system, and note the title of this section so you can quickly find your place in this online guide again.Only the Administrator can turn on and test the connection by following these steps:If you haven't already logged in as root through a shell window, do so now.Choose "Unix Shell" from the Desktop toolchest.Position your cursor within the new window and type:login rootIf a prompt for a password appears, type the password then press . If a prompt appears but the root account has no password, just press .Close any running applications or open files, then restart your system by typing:rebootLog in to the system as root.Open a shell window by choosing "Unix Shell" from the Desktop toolchest.Connect to a system whose information you entered in IDREF="66072" TYPE="TITLE""Building a List of Remote ISDN Systems and Networks" by typing:ppp -rFor example, to connect to the system named mars, type:ppp -r marsAfter several seconds, you'll know the connection is established and ready to use when you see a message similar to this:ppp[395] IPCP1 ready: to If you see a different message, see IDREF="79935" TYPE="TITLE""Troubleshooting the ISDN Connection."Verify whether the remote system has accepted your password and is running PPP by opening another shell window (do not use the window in which you started the connection) and typing:netstat -CLook for the line that starts with ppp0. If no asterisk (*) appears after ppp0, the connection is working. If an asterisk appears, it is not working; see IDREF="79935" TYPE="TITLE""Troubleshooting the ISDN Connection."To stop the netstat command and return to the system prompt, type:qIn the same window that you typed the netstat command, test the connection to the remote system by typing:/usr/etc/ping marsAfter 10 seconds, press .If you see a message that reports 0% packet loss, the connection is working. Go on to the next step.If the message reports a large percentage of packet loss, the connection or network routing is not working. See IDREF="79935" TYPE="TITLE""Troubleshooting the ISDN Connection."Close the connection by typing:Customize your ISDN setup, or start using the connection now.To set up your /etc/hosts file so you can directly log in to and transfer files between any remote system that's on the same network as the system to which you are connected via ISDN, see IDREF="86754" TYPE="TITLE""Adding Remote Systems to the /etc/hosts File."To let other ISDN systems access your system, see IDREF="15017" TYPE="TITLE""Letting Other ISDN Systems Access Your System."To log in to other systems and transfer information, see IDREF="16965" TYPE="TITLE"Chapter 3, "Using ISDN."LBL="" HELPID=""ID="86754"Adding Remote Systems to the /etc/hosts FileThe /etc/hosts file contains a list of all the remote systems that your system can access once the ISDN connection is open. Each line of the file contains an IP address and a hostname. For each remote system to which you want to log in directly, add a line to /etc/hosts.Only the Administrator can edit /etc/hosts. Follow these steps:Log in as root through a shell window.Choose "Unix Shell" from the Desktop toolchest.Position your cursor within the new window and type:login rootIf a prompt for a password appears, type the password then press . If a prompt appears but the root account has no password, just press .Add the hostname and IP address of each remote system to /etc/hosts.Open the file with a text editor such as jot by typing:jot /etc/hostsFor detailed information on using the jot text editor, choose a topic from its Help menu.Search the file to see whether it already contains the hostname and IP addresses that you plan to add. If they're already there, you do not need to edit the file. If they are not there, continue.Add one line for each system to the end of the file. First type the IP address (4 numbers separated by periods) followed by a and the hostname. For example, for a system named saturn.foo.bar.com with an IP address of 192.0.2.9, type:192.0.2.9 saturn.foo.bar.comSave your changes and quit the editor.LBL="" HELPID=""ID="15017"Letting Other ISDN Systems Access Your SystemTo let other ISDN systems access your system, follow these steps:Use the User Manager from the System toolchest to add a user login account (it's best to give the account a password) for the person who wants to access your system.Give the person this information:His user login account name and password on your system, along with your system's telephone number(s). The person will need to add this information to his ppp.conf and Systems files as described in IDREF="66072" TYPE="TITLE""Building a List of Remote ISDN Systems and Networks."The hostname and IP address of your system. The person will need to add this information to his /etc/hosts file as described in IDREF="66072" TYPE="TITLE""Building a List of Remote ISDN Systems and Networks."Make sure your /etc/ppp.conf file contains this line:_ISDN_INCOMING reconfigureIf the line does not appear in the file (it should be the very last line), add the line using a text editor.If you are concerned with system security, you may want to add more information to your /etc/ppp.conf file; see IDREF="87898" TYPE="TITLE""Using a System Security Scheme."LBL="" HELPID=""ID="79935"Troubleshooting the ISDN ConnectionThe troubleshooting information in this section covers many common error conditions. If you find you need more detailed information, see the ppp man page.LBL="" HELPID=""Troubleshooting GuidelinesMake sure all physical connections are solid, and that the NT1 device is powered on. If you had to solidify a connection or power on the NT1 device, restart the system, and try using ISDN again.Run the confidence test. If there is a problem with your basic ISDN setup (the physical connection, the system software installation, the edits in the /etc/config/isdnd.options file, or the connection to the telephone company), this test will report it.Log in to a shell window as root, then type:/etc/init.d/isdnd stopkillall pppChoose "Run Confidence Tests" from the System toolchest.In the Confidence Tests window, double-click the ISDN icon. (You may need to use the scroll bar to find the ISDN icon.)After a few moments, a notifier appears. If the notifier reports a problem, follow the instructions that the confidence test gives you for correcting the problem.If the notifier tells you your ISDN connection is ready to use, type:/etc/init.d/isdnd startTry the ppp -r command again, then go on to the next step.If your system is still reporting error messages when you type ppp -r , check IDREF="61841" TYPE="TITLE""Error Messages During the Initial Setup" and IDREF="54275" TYPE="TITLE""Error Messages from an Established Setup that Usually Works" for possible solutions.LBL="" HELPID=""ID="61841"Error Messages During the Initial SetupThis section lists various error messages that you may encounter during your initial setup of ISDN. Typically you'll see these messages after trying to connect to a remote system for the first time by typing ppp -r . The messages may appear in your shell window, or in the /var/adm/SYSLOG file.For more informative error or status messages when trying to make a connection, follow these steps:Open another shell window, and in the new window type:isdnstatWhen you actually place the call in the next step, isdnstat reports the progress of the call. For more details, see the isdnstat man page. To stop isdnstat from running, type:qIn the shell window in which you're logged in as root, place the call and request additional information from PPP by typing:ppp -r -dThe window in which you started isdnstat changes to show the progress of ISDN, and the window in which you typed the ppp command gives you information about PPP.You can request even more information by adding additional -d flags to the ppp command line, but this will introduce security problems. See the ppp man page for details.This section covers these error conditions:IDREF="65721" TYPE="TITLE""Unknown Switchtype"IDREF="71060" TYPE="TITLE""Login Failed"IDREF="96029" TYPE="TITLE""System Not in Systems File"IDREF="14723" TYPE="TITLE""Failed to Find Entry in /etc/ppp.conf"IDREF="58732" TYPE="TITLE""Missing Devices or Device Types"LBL="" HELPID=""ID="65721"Unknown SwitchtypeUnknown switchtype ""This means there is a problem with the edits you made in your /etc/config/isdnd.options file. Check your entry in this file (see IDREF="36352" TYPE="TITLE""Setting Up Basic ISDN" for details); in particular, make sure:the line in the file that describes your telephone company's switch software type is the only line that does not start with a pound sign (#)if your switch software type is DMS100 or 5ESS NI1, that your SPID numbers contain the appropriate number of digits (typically 11 - 13), and your phone numbers contain only 7 digits.If you make any changes to the file, save the changes, then type:/etc/init.d/isdnd stop/etc/init.d/isdnd startLBL="" HELPID=""ID="71060"Login Failedppp[348] : fatal error "LOGIN FAILED" on try #2ppp[348] : giving up for nowThis message may appear immediately (within 3 seconds) after trying to make the connection, or may appear after several seconds.If you see the message immediately, your system cannot access the ISDN line through your NT1 device, typically because the NT1 is powered off, or the telephone line is unplugged. Check that all connections are solid and the NT1 is powered on, then follow these steps:Open a shell window, log in as root, then type:/etc/init.d/isdnd stop/etc/killall ppp/etc/init.d/isdnd startWait 30 seconds, then try again, requesting more error or status information, by typing:ppp -r -dIf you see the same error message, there may be a problem with the telephone company's switching software. Contact them to report the problem.If you see the Login Failed message after several seconds, there is a different problem; for example, the remote system may be down or its ISDN connection may already be in use. For more information, follow these steps:Open another shell window, and in the new window type:isdnstatWhen you actually place the call in the next step, isdnstat reports the progress of the call. For more details, see the isdnstat man page. To stop isdnstat from running, type:qIn the shell window in which you're logged in as root, place the call and request additional information from PPP by typing:ppp -r -dThe window in which you started isdnstat changes to show the progress of ISDN, and the window in which you typed the ppp command gives you information about PPP.LBL="" HELPID=""ID="96029"System Not in Systems Fileppp[434] : fatal error "SYSTEM NOT IN Systems FILE" on try #2ppp[348] : giving up for nowThe above message means there is a problem with the edits you made to the /etc/uucp/Systems file. Check your edits (see IDREF="66072" TYPE="TITLE""Building a List of Remote ISDN Systems and Networks"). In particular, make sure:if the telephone number is outside of your local area code, that the telephone number entry exactly matches what you would dial on a telephone to call the number. For example, for connections between two U.S. locations that are in different area codes, it must consist of 11 digits (1 + area code + 7-digit phone number).the word `CONNECTED' appears at the end of each line.the rate is appropriate for your location (typically 56 inside the U.S., 64 elsewhere; see also IDREF="72532" TYPE="TITLE""About Transfer Rates").If you make any changes to the file, save the changes, then try the ppp -r command again.LBL="" HELPID=""ID="14723"Failed to Find Entry in /etc/ppp.confppp[483] : failed to find entry labeled `mars' in /etc/ppp.conf -- assume defaultsppp[483] : fatal error "LOGIN FAILED" on try #2ppp[483] : giving up for nowThe above message means there is a problem with the edits you made to the /etc/ppp.conf file. Check your edits (see IDREF="66072" TYPE="TITLE""Building a List of Remote ISDN Systems and Networks").If you make any changes to the file, save the changes, then try the ppp -r command again.LBL="" HELPID=""ID="58732"Missing Devices or Device TypesDevice Type ISDN wanted Requested Device Type Not Found Call Failed: NO DEVICES AVAILABLEOne or more of the above messages indicates that the file /etc/uucp/Devices is either missing information or is corrupted. Verify that the file contains these two lines:ISDN isdn/modem_b1 - 38400 direct ISDN isdn/modem_b2 - 38400 directIf the lines are missing, add them to the file and save the changes, then try the ppp -r command again.LBL="" HELPID=""ID="54275"Error Messages from an Established Setup that Usually WorksThis section lists various error conditions and messages that you may encounter when starting an ISDN connection that usually works. The messages may appear in your shell window, or in the /var/adm/SYSLOG file.For more informative error or status messages when trying to make a connection, follow these steps:Open another shell window, and in the new window type:isdnstatWhen you actually place the call in the next step, isdnstat reports the progress of the call. For more details, see the isdnstat man page. To stop isdnstat from running, type:qIn the shell window in which you're logged in as root, place the call and request additional information from PPP by typing:ppp -r -dThe window in which you started isdnstat changes to show the progress of ISDN, and the window in which you typed the ppp command gives you information about PPP.You can request even more information by adding additional -d flags to the ppp command line, but this will introduce security problems. See the ppp man page for details.This section covers these error conditions:IDREF="56723" TYPE="TITLE""Login Failed"IDREF="44689" TYPE="TITLE""Network is Unreachable"IDREF="42272" TYPE="TITLE""Unknown Host"LBL="" HELPID=""ID="56723"Login Failedppp[348] : fatal error "LOGIN FAILED" on try #2ppp[348] : giving up for nowThis message may appear immediately (within 3 seconds) after trying to make the connection, or may appear after several seconds.If you see the message immediately, your system cannot access the ISDN line through your NT1 device, typically because the NT1 is powered off, or the telephone line is unplugged. Check that all connections are solid and the NT1 is powered on, then follow these steps:Open a shell window, log in as root, then type:/etc/init.d/isdnd stop/etc/killall ppp/etc/init.d/isdnd startWait 30 seconds, then try again, requesting more error or status information, by typing:ppp -r -dIf you see the same error message, there may be a problem with the telephone company's switching software. Contact them to report the problem.If you see the Login Failed message after several seconds, there is a different problem; for example, the remote system may be down or its ISDN connection may already be in use. For more information, follow these steps:Open another shell window, and in the new window type:isdnstatWhen you actually place the call in the next step, isdnstat reports the progress of the call. For more details, see the isdnstat man page. To stop isdnstat from running, type:qIn the shell window in which you're logged in as root, place the call and request additional information from PPP by typing:ppp -r -dThe window in which you started isdnstat changes to show the progress of ISDN, and the window in which you typed the ppp command gives you information about PPP.LBL="" HELPID=""ID="44689"Network is Unreachable: Network is unreachableThe above message means that your system cannot determine the correct route to take to access the remote system. Check your /etc/ppp.conf file, and make sure your entry for the host you tried to access contains this line:add_routeAdd this line to the entry if it was not already there; use the instructions in IDREF="66072" TYPE="TITLE""Building a List of Remote ISDN Systems and Networks."NoteThe add_route line establishes a static default route. If your Internet Service Provider or network adminstrator requires a different type of routing (for example, if you have a routing daemon turned on), contact that person and describe your problem. See also IDREF="81465" TYPE="TITLE""Changing Network Routing" and the gated and routed man pages.Open another shell window, and in the new window type:isdnstatWhen you actually place the call in the next step, isdnstat reports the progress of the call. For more details, see the isdnstat man page. To stop isdnstat from running, type:qIn the shell window in which you're logged in as root, place the call and request additional information from PPP by typing:ppp -r -dThe window in which you started isdnstat changes to show the progress of ISDN, and the window in which you typed the ppp command gives you information about PPP.If you still cannot access the system, you may have a different routing problem. See IDREF="81465" TYPE="TITLE""Changing Network Routing."LBL="" HELPID=""ID="42272"Unknown Host: Unknown hostThe above message means that the system that you are trying to access does not appear in your /etc/hosts file.Add the system to the /etc/hosts file as described in IDREF="86754" TYPE="TITLE""Adding Remote Systems to the /etc/hosts File."Try to log in to the system again.LBL="3"ID="16965"Using ISDNTo use ISDN, you initiate a connection to a remote system or network in one shell window, then use another shell window to log in to or transfer files between your system and the remote system or network.The connection uses PPP (Point-to-Point Protocol). For more information than is available in this chapter, see the ppp man page.This chapter contains these sections:IDREF="74014" TYPE="TITLE""Starting an ISDN Connection"IDREF="80168" TYPE="TITLE""Logging In to Remote Systems"IDREF="73039" TYPE="TITLE""Transferring Files Across an ISDN Connection"IDREF="77590" TYPE="TITLE""Stopping an ISDN Connection"LBL="" HELPID=""ID="74014"Starting an ISDN ConnectionWhen you start an ISDN connection, you are placing a telephone call from your system to another system. The telephone company charges you by the minute while the connection is open, regardless of whether you are actively transferring files or are logged in to a remote system. Be sure to close the connection when you are not using it (see IDREF="77590" TYPE="TITLE""Stopping an ISDN Connection").Only the Administrator can start an ISDN connection. Follow these steps:Log in as root through a shell window.Choose "Unix Shell" from the Desktop toolchest.Position your cursor within the new window and type:login rootIf a prompt for a password appears, type the password then press . If a prompt appears but the root account has no password, just press .If you like, you can monitor the progress of the ISDN connection or of PPP in a separate shell window. To monitor the progress of the ISDN connection, open another shell window, and type:isdnstatWhen you actually place the call in the next step, isdnstat reports the progress of the call. For more details, see the isdnstat man page. To stop isdnstat from running, type:qTo monitor the progress of PPP, open another shell window, and type:netstat -CWhen you place the call in the next step, the asterisk (*) next to the ppp0 listing should disappear. For more details, see the netstat man page. To stop netstat from running, type:qIn the shell window in which you are logged in as root, start an ISDN connection to a system whose information your entered in IDREF="66072" TYPE="TITLE""Building a List of Remote ISDN Systems and Networks" by typing:ppp -rFor example, to connect to the system named mars, type:ppp -r marsAfter several seconds, you'll know the connection is established and ready to use when you see a message similar to this:ppp[395] IPCP1 ready: to If you see a different message, see IDREF="79935" TYPE="TITLE""Troubleshooting the ISDN Connection."Do not close the shell window in which you started the connection; the window must remain open to keep the connection open. You may want to resize or minimize the window to save screen space.To use the connection, see IDREF="80168" TYPE="TITLE""Logging In to Remote Systems" and IDREF="73039" TYPE="TITLE""Transferring Files Across an ISDN Connection."To close the connection, click the minimized icon of the window in which you made the connection (if you minimized it), position your cursor over the window, and type:The connection is closed when you see the system prompt.NoteBe sure to close your ISDN connection when you are not using it. As long as the connection is open, your telephone company charges you just as it does for a standard telephone call.LBL="" HELPID=""ID="80168"Logging In to Remote SystemsOnce the ISDN connection is open (see IDREF="74014" TYPE="TITLE""Starting an ISDN Connection"), you can log in to:the remote system to which you connected using ISDNany remote system that's on the same network as the system to which you connected, and whose hostname and IP address appear in your /etc/hosts file. For more information, see IDREF="86754" TYPE="TITLE""Adding Remote Systems to the /etc/hosts File."To log in to a remote system, follow these steps:Choose "Unix Shell" from the Desktop toolchest.You can log in to the system using either the rlogin command or the telnet command.To use rlogin, position your cursor over the shell window and type:rlogin -l You are logged in when you see the remote system's prompt. For more information, see the rlogin man page.If you do not see the prompt after several seconds, type:Then see IDREF="79935" TYPE="TITLE""Troubleshooting the ISDN Connection."To use telnet, position your cursor over the shell window and type:telnet When the remote system responds, you see a login prompt. Type your login name, and, if requested, your password. For more information, see the telnet man page.If you do not see the prompt after several seconds, type:Then see IDREF="79935" TYPE="TITLE""Troubleshooting the ISDN Connection."To log out of a remote system, type:logoutWhen you are finished using the remote system, you may want to close your ISDN connection; see IDREF="77590" TYPE="TITLE""Stopping an ISDN Connection."LBL="" HELPID=""ID="73039"Transferring Files Across an ISDN ConnectionOnce the ISDN connection is open (see IDREF="74014" TYPE="TITLE""Starting an ISDN Connection"), you can transfer files between your system and:the remote system to which you connected using ISDNany remote system that's on the same network as the system to which you connected, and whose hostname and IP address appear in your /etc/hosts file. For more information, see IDREF="86754" TYPE="TITLE""Adding Remote Systems to the /etc/hosts File."You can transfer files using any of several transfer utilities. See IDREF="77689" BOOK="IRISEssentials" FILE="ch8.doc" HDG="""Copying Files Across the Network" in the online document IRIS Essentials for details on copying files graphically using the Indigo Magic desktop, and for an overview of rcp and ftp. For more details on rcp and ftp, see their man pages.If you encounter any problems copying files, first make sure that you can successfully log in to the remote system; see IDREF="80168" TYPE="TITLE""Logging In to Remote Systems." If you cannot log in, see IDREF="79935" TYPE="TITLE""Troubleshooting the ISDN Connection." If you can log in but still cannot successfully transfer files, see the man page for the utility you are using, or see IRIS Essentials.LBL="" HELPID=""ID="77590"Stopping an ISDN ConnectionOnly the Administrator can stop (close) an ISDN connection. Be sure to close the connection when you are not using it; the telephone company charges you by the minute while the connection is open, regardless of whether you are actively transferring files or are logged in to a remote system.To close the connection, follow these steps:If the window in which you started the connection is minimized, click it to open it.Position your cursor over the window in which you started the connection, then type:The connection is closed when you see the system prompt. LBL="4"ID="60345"ISDN ReferenceThis chapter contains advanced information on the Indy implementation of ISDN, and on using PPP. It contains these sections:IDREF="91829" TYPE="TITLE""Technical Background"IDREF="97595" TYPE="TITLE""Using ISDN and Other Networks Simultaneously"IDREF="58442" TYPE="TITLE""Using Advanced ISDN Configuration Options"IDREF="55975" TYPE="TITLE""Summary of UUCP, IRIX, ISDN, and PPP Configuration Files"LBL="" HELPID=""ID="91829"Technical BackgroundThe Indy provides a BRI (Basic Rate Interface) S/T interface. There are two B channels, each capable of transferring up to 64 Kbits/second and one D channel, capable of transferring 16 Kbits/second. For more information, see IDREF="72532" TYPE="TITLE""About Transfer Rates."The B channels carry the actual data. The Indy supports only data communications (no voice communications) at this time. The D channel carries signaling and protocol data only. You cannot transmit user data over the D channel.A daemon, isdnd, listens on the D channel for incoming calls. It also makes calls on behalf of local applications. PPP (Point-to-Point Protocol) is shipped with IRIX, and can make ISDN calls and talk over ISDN B channels. isdnd will also accept ASI messages from ASI program entities; see the ISDN Release Notes for details.LBL="" HELPID=""Standards Supported by the IndyISDN on the Indy supports both PPP and ASI. The implementation of PPP supports these standards:magic numbersLCP address and control field compressionLCP protocol field compressionAsynchronous Control Character MapIP header compression (also called VJ compression)PAP authenticationIP address negotiationdemand dialinga non-standard (but not proprietary) multi-link protocolLBL="" HELPID=""ID="70024"Requirements for Remote ISDN SystemsThe remote system must use ISDN and talk either:IETF PPP ; if you're using the security scheme described in IDREF="87898" TYPE="TITLE""Using a System Security Scheme", it must support the PAP authentication/password scheme.ASILBL="" HELPID=""ID="72532"About Transfer RatesAlthough each B channel can transfer 64 Kbits/second, many U.S. and international calls cannot transfer at this rate because the telephone company uses 1 bit out of every 8 to send the data between switch hardware. This makes the actual rate on each B channel 56 Kbits/second.You can transfer information within the U.S at 64 Kbits/second only if both your system and the remote ISDN system use the same physical switch hardware. In most cases, this would require that both systems are located in the same general geographic location (e.g., in the same city) and the calls are placed to each other in the same central switching office.You can also increase your transfer rate by using both B channels simultaneously; see IDREF="57521" TYPE="TITLE""Optimizing Connection Speed."LBL="" HELPID=""ID="97595"Using ISDN and Other Networks SimultaneouslyIf your Indy is connected to a standard Ethernet network, and you also want to use ISDN to connect to a different network, you must work closely with the administrator of the ISDN network to set up network routing on your Indy correctly.This typically involves these steps:Configure gated (the routing daemon you need to use when your system uses two or more networks simultaneously) by editing the /usr/etc/gated.conf file. A sample file appears at the end of these steps.Turn off routed, turn on gated, and restart networking by logging in as root and typing:/etc/chkconfig routed off/etc/chkconfig gated on/etc/init.d/network stop/etc/init.d/network startDelete the add_route line from every entry in the /etc/ppp.conf file.Try out the connection. If you have routing problems (i.e., you see an error message that says : Network is unreachable), contact the administrator of the remote system or network.LBL="" HELPID=""Sample /usr/etc/gated.confIn this example, 192.0.1.1 is the IP address of the local system for both its PPP and Ethernet interfaces. 192.0.1 is the local Ethernet network. For more information, see the gated man page.# gated.conf # # gated configuration file for automatic PPP RIP yes supplier HELLO no EGP no # Trace options traceflags internal external # Do not time out the PPP interface. This keeps gated # from timing out if it doesn't hear RIP packets from # the local system. passiveinterfaces 192.0.1.1 # Braodcast this system as a gateway at all times, # even when the PPP link is not active. net 192.0.1.0 gateway 192.0.1.1 metric 1 rip # Do not waste bandwidth by sending RIP packets to # the local system. noripoutinterface 192.0.1.1LBL="" HELPID=""ID="58442"Using Advanced ISDN Configuration OptionsThis section covers only a few, common options for using PPP across an ISDN line. For more information, see the ppp man page.LBL="" HELPID=""ID="87898"Using a System Security SchemeAs long as the remote system supports the PAP authentication/password scheme, you can add information to /etc/ppp.conf to allow only a select list of users to log in to your system. For example, assume that fred, joe, and mary all have user accounts on your system, but you want to allow only fred and mary to log in via ISDN. In this case, you would add one line in ppp.conf for each user under the _ISDN_INCOMING reconfigure line as shown here:_ISDN_INCOMING reconfigurerecv_username=fredrecv_username=maryIf you do not add any recv_username entries, all users who have a valid login account on your system can log in via ISDN.LBL="" HELPID=""ID="81465"Changing Network RoutingNetwork routing can be very complex. Before you change your routing scheme, contact your network administrator.You control network routing using either:a routing daemon (routed or gated), ora static route (the route add command or add_route in your ppp.conf file)Do not use a static route and a routing daemon at the same time. This will disrupt the routing, and you will not be able to reach remote systems. For more information, see the routed, gated, and ppp man pages.LBL="" HELPID=""ID="57521"Optimizing Connection SpeedThe Indy supports a non-standard method for optimizing connection speed which works best between two Indys. It uses both B channels simultaneously; consequently, it also doubles your telephone usage costs. To each entry in /etc/ppp.conf, add this line:outdevs=2For example, to optimize your connection speed to the host mars, its ppp.conf entry would look like this:marssend_username=joesend_passwd=isdnadd_routeoutdevs=2LBL="" HELPID=""Using Quiet ModePPP's quiet mode starts PPP on demand (when you try to access a system using PPP) and closes the connection after a certain amount of idle time. This makes the PPP connection nearly as seamless as an Ethernet network connection, and also ensures that you do not inadvertantly leave an idle connection open and incur unneccessary telephone charges.Quiet mode has complex routing implications. Contact your network administrator and see the ppp man page for more information.LBL="" HELPID=""ID="55975"Summary of UUCP, IRIX, ISDN, and PPP Configuration FilesThis section summarizes the configuration files that you edit in Chapter 2 to set up your ISDN connection./etc/config/isdnd.options is an ISDN file in which you specify the switch software type that your telephone company uses./etc/uucp/Devices is a UUCP file in which you specify an ISDN line as an available device./etc/uucp/Systems is a UUCP file in which you specify the name and telephone numbers of systems to which you will connect via ISDN./etc/ppp.conf is a PPP file in which you can customize PPP for each system to which you will connect via ISDN. See also IDREF="58442" TYPE="TITLE""Using Advanced ISDN Configuration Options."/etc/hosts is an IRIX networking file in which you specify the hostname, hostname alias, and IP address of each system to which you will connect via ISDN, as well as each system that you will access after establishing an ISDN connection./usr/etc/gated.conf is an IRIX networking file that controls the behavior of the gatedrouting daemon. See also IDREF="97595" TYPE="TITLE""Using ISDN and Other Networks Simultaneously."GlossaryAdministratorThe person who can use the most privileged account, root. This person must have his own personal login account for daily use, but, when there are serious system problems to correct, the person logs in to the root account to change system information using the graphical tools or using the IRIX shell. The Administrator has all the capabilities of a Privileged User, plus the capability to change information in the root account (such as the password) and to log in to an IRIX shell as root. Because there is only one root account, there is only one Administrator per system. The Information Panel for a particular system includes the name of the system's Administrator so other users know who to contact for help.BRIA BRI (Basic Rate Interface) ISDN service includes 2 B channels and 1 D channel. It is the standard type of telephone service you need to use ISDN on an Indy.B channelsISDN on the Indy transfers data across two separate conduits, called B channels. Each B channel is capable of transferring up to 64 Kbits/second. See also D channel.confidence testA test that you run to make sure a particular device (such as the keyboard, mouse, or ISDN) is set up and working properly.Customer Premise Equipment (CPE)A term that the telephone company uses to describe all the end-user equipment needed to make an ISDN connection. For example, the Indy is Customer Premise Equipment (CPE).D channelISDN on the Indy transfers signalling and protocol data (but no user data) on a single conduit, called a D channel. The D channel can transfer up to 16 Kbits/second. See also B channels.hostnameThe name that uniquely identifies each host (system) on the network. hostname aliasA shorter version (for UUCP applications, it must be 7 characters or less) of a hostname.hubnameThe hostname of a system through which all ISDN connections to a particular network are made.IP addressThe number that uniquely identifies each system on the network.Internet Service ProviderThe person or agency that administers the system or network to which you connect via ISDN.ISDNISDN (Integrated Services Digital Network) technology is a combination of software, hardware, and telephone services that let you communicate with other systems and networks over a high-speed telephone line just as you communicate with other systems and networks over an Ethernet cable.login accountA collection of information about a person who can log in to the system. The information includes the person's full name, login name, contact information, and the name of a home directory in which the person can store directories and files.login nameA short version of your own name or your initials; you type it to log in to the system, and the system uses it to label files that belong to you. If your system is on a network, the network administrator usually must approve of the name to make sure it is unique.NT1 deviceA small, external hardware device (often the size of a standard VHS tape) that converts the standard 2- or 4-wire telephone jack signal (the U interface) to an 8-wire ISDN signal (the S/T interface). Depending on the type of NT1 unit you order, you may need a companion power supply unit.PPPPPP (Point-to-Point Protocol) is a standard communications protocol for transmitting network data over point-to-point links using modems or ISDN lines. You can use it to transfer data between systems that are using TCP/IP or UDP/IP.PRIA PRI (Primary Rate Interface) ISDN service requires a T1 link or PBX line; it is used for high-end video teleconferencing, or for a large volume of outbound calls. It will not work over a standard telephone line; the Indy cannot use PRI. See also BRI.passwordA combination of letters and/or numbers that only you know; it is an optional element of your login account. If you specify a password for your account, you must type it after you type your login name before the system lets you access files and directories.permissionsThe information attached to each directory and file that specifies which users can access it and to what degree.promptA character or word that the system displays in an IRIX shell that indicates that the system is ready to accept commands. The default prompt for regular user accounts is %; the default prompt for the root account is #.RJ-11 cableThe standard, 4-wire cable that you use to plug a telephone into a standard wall jack. In an ISDN connection, you use it to connect the NT1 device or power supply unit to the wall jack.RJ-45 cableA high-speed, 8-wire cable that looks similar to the RJ-11 (standard telephone cable) but has larger connectors. In an ISDN connection, you use it to connect the NT1 device to the ISDN port on the Indy. If you have a companion power supply for the NT1 device, you use a second, shorter RJ-45 cable to connect the NT1 device to the power supply unit.root accountThe standard IRIX login account reserved for use by the system administrator. This account's home directory is the (/) directory of the filesystem; the user of the root account has full access to the entire filesystem (that is, can change and delete any file or directory). The user of this account is sometimes referred to as the superuser.routing daemonA continuously running program that determines the network route by which data will be transferred. gated and routed are the two standard routing daemons available on your system.SLIPStandard system software that lets you connect to a network using a serial cable and a modem rather than using an Ethernet cable. Once you're connected, you can use the network as if you were connected by an Ethernet cable. SLIP stands for Serial Line Internet Protocol.SPIDThe SPID (Service Profile Identifier) is a number that typically consists of 11 - 13 digits. For each ISDN telephone number, the telephone company assigns a corresponding SPID number. You need to know your two SPID numbers for these switch software types: 5ESS National ISDN 1; DMS100 BCS level 31, 32, 33, or 34 (Protocol Version 1); DMS BCS level 35 or higher (Protocol Version 2).S/T interfaceThe 8-wire, high speed port used to transfer data using ISDN. The NT1 device's S/T interface port is usually labelled S/T, and the S/T interface port on the Indy (the ISDN port) is labelled with an icon of a telephone. These ports accept an RJ-45 cable.subsystemA portion of a software product. Each product consists of several subsystems; some are requred and some are optional.superuserAn alternate name for the user of the root login account. See also system administrator.switch hardwareThe large computer located in the telephone company's central switching office through which telephone calls are routed. In the U.S., the two types of switch hardware are 5ESS and DMS100. See also switch software.switch softwareThe type of software that runs on the switch hardware. In the U.S., switch software types include 5ESS Custom, 5ESS NI1, DMS100 BCS level 31, 32, 33, or 34 (Protocol Version 1), and DMS100 BCS level 35 or higher (Protocol Version 2); the last type is also sometimes called DMS NI1. In Germany, switch software types include 1TR6 or NET3 (also known as Euro-ISDN or DSS-1). The rest of Europe has NET3 switch software, and Japan has NTT.System toolchestThe toolchest in the upper left portion of the screen from which you can access all system administration tools.TCP/IPThe standard networking software that's included in the system software.Terminal Adapter (TA)Technically this is a device that allows terminals to access ISDN through serial lines. It has become a generic term for ISDN end-user equipment. For example, the telephone company may refer to the Indy as a Terminal Adapter (TA).UUCPStandard system software that lets you connect to a network using a serial cable and a modem rather than using an Ethernet cable. Once you're connected, you can log into a single system through one window; your system essentially behaves like a dumb terminal.U interfaceThe standard, 2- or 4- wire wall jack port for a telephone. It accepts an RJ-11 cable.