|
If none of the strings from the modemcap properly
initialize the modem, you must manually configure the modem or change the modemcap database.
Use the modemcap edit
new_modem_name command to do the following:
Figure
shows the uses of the
modemcap edit usr_new
command. The command line marked
with a 1 creates a new database entry called usr_new entry and sets
the caller-id for the usr_new modem to *U1. The command line marked
with a 2 locks the DTE speed on this modem. Finally, the command
line marked with a 3 points to another modemcap entry to be used as
a template. As a result, any value not found in the current modemcap
entry is set by the template modemcap entry. In this example, the usr_courier
modemcap entry is the template.
Additional commands that can be used when creating variant modem cap entries
follow:
-
The modemcap edit command edits user-created modemcap entries only.
-
Use the no modemcap edit
modemname command to remove the specified modem from the modemcap database. With this command, the whole modemcap entry is deleted.
-
The no
modemcap edit
modemname attribute
command removes a modem attribute from the modemcap entry of a
modem without deleting the entry altogether.
After configuring a modemcap entry with the
modemcap edit
command, use the show modemcap modem_name command to verify the new modemcap attribute values.
Figure
shows the output for the new modemcap created in Figure .
The numbers in the Figure
output correspond to the numbers in Figure
that show each
modemcap edit command from the example.
Specifically, the usr_new modemcap shown in Figure
is identical to the usr_courier entry, with the following exceptions:
-
The DTE speed lock
-
The caller ID field
-
The template
If you use the show running-config command, the usr_new information for the configuration on the previous page appears as follows:
usr_new SPD = &B1:CID = *U1:TPL = usr_courier
|