Technical data
90362-01 Dial-up Connections 7-5
If you are using CHAP authentication (which is on by default for 
inbound connections), this crypto key needs to correspond to the 
CHAP “secret” sent from the remote end of the connection.
Note that adding or changing the crypto key for a dial-up connection 
also changes the crypto key in the dial-in user record of the same 
name.
7.
In the 
Dial-in
 field, select whether or not you want to create a dial-in 
user record to authenticate any inbound connections from the remote 
NetBlazer. Select 
yes
 to have the dial-in record created, 
no
 if you do 
not want a record created. If you do not create a dial-in record, then 
calls from the remote NetBlazer will be rejected because your 
NetBlazer does not have the user record necessary to authenticate 
the connection. If you do create a dial-in record, it will use the same 
password and/or crypto key as you enter on this screen.
8.
In the 
Phone number
 field, type the phone number of the remote 
NetBlazer. You can format the number using spaces, dashes, and 
parentheses; for example, 
9,1 (408) 555-1234
. If your modem needs 
to dial a prefix, such as 9, to reach an outside line, be sure to include 
that number as the first number in this field.
9.
For most configurations, you should leave the 
Characteristics
 field 
set to the default setting of 
dialout
. However, if you are using ISDN, 
you should select 
isdndialout
, which configures a line for use with 
either an ISDN terminal adapter or with a built-in Basic Rate ISDN 
(BRI) adapter. 
All of the other settings are used only in very specific instances. 
pep-dialout
 is used to override standard modem settings when you 
are using pep-compatible modems at both ends of a connection. 
v25dialout
 configures a synchronous line for use with a TA. 
bridial-out
 is used for BRI-only ISDN connections. 
v32dialout
configures a modem for v.32 operations.
Note:
This field is case sensitive. You need to be very careful with case when en-
tering a password.
Also, to avoid problems with remote password files, your crypto key should 
not include any of the following characters: “
@
”,“
:
”, “
%
”, “
\
”, “
/
”, “
{
”, 
“
}
”,
or any nonprinting characters.










