![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
This chapter describes how to start and stop the Cisco 200 software. You can start and stop the software automatically using batch files, and you can also start and stop the software using manual procedures. This chapter contains the following sections:
To use batch files to start or stop the Cisco 200 automatically, follow the instructions in this section. These batch files are for use with NetWare VLMs.
If you are using NetWare VLMs, take the following steps to start the Cisco 200 software using the batch file installed on your PC during the Cisco 200 software installation:
Contents of CONNECT.BAT for NI1
The contents of the CONNECT.BAT file for the NI1 protocol are shown below:
Contents of CONNECT.BAT for 5ESS Point-to-Point
The contents of the CONNECT.BAT file for the 5ESS Point-to-Point Protocol are shown below:
Contents of CONNECT.BAT for 5ESS Multipoint
The contents of the CONNECT.BAT file for the 5ESS Multipoint Protocol are shown below:
Contents of CONNECT.BAT for DSS1
The contents of the CONNECT.BAT file for the DSS1 Protocol are shown below:
Unless the Cisco 200 software is unloaded, it continues to accept calls. To stop the Cisco 200 from accepting calls, you must unload the Cisco 200 driver.
If you are using NetWare VLMs, you can stop the Cisco 200 using the DCONNECT.BAT batch file that was automatically installed during the Cisco 200 software installation. Follow these steps:
The contents of the DCONNECT.BAT file are shown below:
Loading and Unloading Drivers Manually
You can manually start and stop the Cisco 200 software. If you prefer to load and unload drivers manually, rather than automatically using the batch files, follow the instructions in this section.
To load drivers manually from the DOS prompt, enter the appropriate commands, depending on the operating system you are using. See Table 4-1.
These commands must be entered in the order shown. They will load the Cisco 200 drivers in high memory. If you prefer to load the drivers in conventional memory, omit "LH" from the command strings.
Table 4-1 : Commands for Loading Cisco 200 Drivers Manually
In Table 4-1:
You can unload the Cisco 200 driver(s) manually rather than using the DCONNECT.BAT file. (This is required if you are using NETX.)
To unload drivers manually from the DOS prompt, take the appropriate steps, depending on the operating system you are using. See Table 4-2.
Table 4-2 : Commands for Unloading Cisco 200 Drivers Manually
To unload the Cisco 200 drivers manually, these steps must be followed in the order shown.
This section describes the command line switches that are used with several of the driver and configuration files. These switches allow you to customize your Cisco 200 communications.
The command line switches for the CAPI200 driver use the following format:
CAPI200 command line switches are defined in Table 4-3.
Cisco 200 Driver Command Line Switches
The command line switches for the Cisco 200 driver are defined in Table 4-4.
The command line switches for the ISDN200 file use the following format:
ISDN200 command line switches are defined in Table 4-5.
Copyright 1988-1996 © Cisco Systems Inc.
CD\
directory
CONNECT
routername
You are attached to server
servername.
See the section "Loading and Unloading Drivers Manually" later in this chapter for more information about customizing the way the Cisco 200 handles ISDN connections.
**************************************************************
rem batchfile to access a remote LAN via Cisco 200 Personal
rem Office for ISDN
rem
rem usage: connect(Remote Name)
rem
rem example: connect HEADQUARTERS rem
**************************************************************
cd\nwclient
echo on
lh capi200 -p 1 -s 7145551111100 -s 7145551112200 -n 5551111 -n 5551112
lh lsl
lh CISCO200
c:\windows\odihlp.exe
isdn200 %1
if errorlevel 1 goto unload
lh ipxodi
lh vlm
goto exit
:unload
CISCO200 u
lsl u
capi200 -d
:exit
cd\nwclient
**************************************************************
rem batchfile to access a remote LAN via Cisco 200 Personal
rem Office for ISDN
rem
rem usage: connect (Remote Name)
rem
rem example: connect HEADQUARTERS
rem **********************************************************
echo on
lh capi200 -p 2 -s 0155511110
lh lsl
lh CISCO200
isdn200 %1
if errorlevel 1 goto unload
lh ipxodi
lh vlm
goto exit
:unload
CISCO200 u
lsl u
capi200 -d
:exit
**************************************************************
rem batchfile to access a remote LAN via Cisco 200 Personal
rem Office for ISDN
rem
rem usage: connect (Remote Name)
rem
rem example: connect HEADQUARTERS
rem
**************************************************************
echo on
lh capi200 -p 2 -s 0155511110
lh lsl
lh CISCO200
isdn200 %1
if errorlevel 1 goto unload
lh ipxodi
lh vlm
goto exit
:unload
CISCO200 u
lsl u
capi200 -d
:exit
**************************************************************
rem batchfile to access a remote LAN via Cisco 200 Personal
rem Office for ISDN
rem
rem usage: connect (Remote Name)
rem
rem example: connect HEADQUARTERS
rem
**************************************************************
echo on
lh capi200 -p 0
lh lsl
lh CISCO200
isdn200 %1
if errorlevel 1 goto unload
lh ipxodi
lh vlm
goto exit
:unload
CISCO200 u
lsl u
capi200 -d
:exit
DCONNECT
echo on
rem **********************************************************
rem batchfile to unload all Cisco 200 Personal
rem Office for ISDN
rem
rem usage: dconnect
rem
rem example: dconnect
rem
**************************************************************
echo on
vlm u
ipxodi u
CISCO200 u
lsl u
capi200 -d
exit
DOS
Windows 3.1
Windows for Workgroups 3.11
LH CAPI200
LH LSL
LH CISCO200
LH IPXODI
ISDN200
routername
NETX
or
VLM
LOGIN
userid
LH CAPI200
LH LSL
LH CISCO200
ISDN200
routername
LH IPXODI
LH VLM
LOGIN
userid
WIN
LH CAPI200
LH LSL
LH CISCO200
C:\WINDOWS\ODIHLP
ISDN200
routername
LH IPXODI
LH VLM
LOGIN
userid
WIN
DOS
Windows 3.1
Windows for Workgroups 3.11
Enter the following:
LOGOUT
NETX u
or
VLM u
IPXODI u
CISCO200 u
LSL u
CAPI200 -d
LOGOUT
VLM u
IPXODI u
ISDN200 -d
CISCO200 u
LSL u
CAPI200 -d
Reboot the PC from DOS.
CAPI200 -d -a aaa -t tei -p protocol -s spid -n directory
Switch
Description
-d
Deinstalls the program
-a aaa
Uses the I/O address of installed adapter
-t tei
Uses the nonautomatic terminal endpoint identifier (TEI) value
-p protocol
Where protocol is one of the following:
0
1
2
for DSS1
for NI1
for 5ESS
-s spid
Service profile identifier (SPID) for use in North America
-n directory
Directory number for use in North America
Switch
Description
CISCO200
Loads the Cisco 200 software (uses interrupt 0x63)
CISCO200 ?
Displays the help screen
CISCO200 u
Unloads the Cisco 200 software
ISDN200 routername -p parafile -i ii -s -d -l -c
Switch
Description
ISDN200 ?
Displays the help screen.
routername
Short name of the communication router to which a connection should be established (specified in the ISDN200.CFG file).
Note This parameter is required if this is the first time you are connecting to this router or if you were connected to a different router last time.
-p parafile
Pathname of the configuration file, if other than ISDN200.CFG
-i ii
Software interrupt level used by the driver, given in decimal format.
Supports interrupt values: 11, 10, 5, 2, and 9
For example:
CISCO200 -i 9
represents loading the Cisco 200 using interrupt 9.
Note This parameter defaults to auto search.
-s
Puts the current connection to sleep; that is, the call is hung up but the session information is preserved.
-d
Hangs up the current connection immediately
-l
Listen for incoming calls
Note This parameter is required on one Cisco 200 workstation if you want to communicate in a peer-to-peer situation.
-c
Call the last router to which the Cisco 200 was connected. For this to work, the Cisco 200 must be in a disconnected or a sleeping state. This allows the user to reconnect after the -d or -s switches have been used or the inactivity timeout has expired.
Note This parameter is required on one Cisco 200 workstation if you want to communicate in a peer-to-peer situation.