InfoBlast Home

Table of Contents

Release Notes for Cisco 700 Series Router Software Release 4.0(1)

Release Notes for Cisco 700 Series Router Software Release 4.0(1)

This release note describes the features and caveats for Cisco 700 series software for Software Releases 4.0(1) and earlier. For complete software documentation for Software Release 4.0(1), refer to the Cisco 700 Series Command Reference publication.

Caution The Cisco 750 series routers use a unique version of the software that is not interchangeable with the Cisco 760 series software. Make sure you load the correct version for your router.

This document includes the following sections:

System Support

Software Release 4.0(1) supports the following routers:

Cisco 750 Series CiscoPro CPA760 Series Cisco 760 Series Cisco 770 Series
Cisco 751 CPA761 Cisco 761 Cisco 771
Cisco 752 CPA762 Cisco 762 Cisco 772
Cisco 753 CPA765 Cisco 765 Cisco 775
CPA766 Cisco 766 Cisco 776

Upgrading to Software Release 4.0(1)

After physically installing the router and connecting it for the purposes of local configuration, prepare the router for the new software. The general process for preparing the router is as follows:


Table  1: Enhancements for Software Release 4.0(1)
4.0(1) Feature 750 Series 760 and 770 Series
Default encapsulation PPP Yes Yes
IPCP Address Negotiation Yes Yes
DHCP Relay Agent Yes Yes
DHCP Server No Yes
Port Address Translation No Yes
IP Multicast Forwarding No Yes
RIP V2 Summarization No Yes
RIP Linkup Option Yes Yes
IPXCP Address Negotiation No Yes
Default IPX Route Yes Yes
SAP Helper Yes Yes
IPX Ping No Yes
ConnectPro Support No No
ClickStart Support Yes Yes
ISDN Permanent Connections Yes Yes
3-Way Call Conference/Transfer No Yes
2nd Number Failover No Yes
Callback over D Channel No Yes
Fee Pulse Mode No Yes
A-Law/Mu-Law Option No Yes
Distinctive Ringing No Yes
Set Button Command No 770 Only

Image Names

Table 2 through Table 4 list the filename and memory required for each image. Images named C760, are for both Cisco 760 and Cisco 770 routers.


Table  2: Image Filenames and Memory Requirements for Internet Ready Feature Pack (CD070-IR-4.0)
UNIX Filename DOS Name Description Flash Memory Required DRAM Required
c760-in.b-US.40-1 80146201 C760 Series Internet Ready Feature Set, United States 4.0(1)
0.50 MB
1.5 MB
c760-in.b-NET3.40-1 80146301 C760 Series Internet Ready Feature Set, Europe 4.0(1) 0.50 MB 1.5 MB
c760-in.b-1TR6.40-1 80146401 C760 Series Internet Ready Feature Set, Germany 4.0(1) 0.50 MB 1.5 MB
c760-in.b-TPH.40-1 80146501 C760 Series Internet Ready Feature Set, Australia 4.0(1) 0.50 MB 1.5 MB
c760-in.b-INS.40-1 80146601 C760 Series Internet Ready Feature Set, Japan 4.0(1) 0.50 MB 1.5 MB
Note Internet Ready images do not support IPX routing.

Table  3: Image Filenames and Memory Requirements for SOHO Feature Pack (CD070-SO-4.0)
UNIX Filename DOS Name Description Flash Memory Required DRAM Required
c751-in.s-US.40-1 80147701 C751 Series SOHO Feature Set, United States 4.0(1) 0.25 MB 1.0 MB
c751-in.s-NET3.40-1 80147801 C751 Series SOHO Feature Set, Europe 4.0(1) 0.25 MB 1.0 MB
c751-in.s-1TR6.40-1 80147901 C751 Series SOHO Feature Set, Germany 4.0(1) 0.25 MB 1.0 MB
c751-in.s-TPH.40-1 80148001 C751 Series SOHO Feature Set, Australia 4.0(1) 0.25 MB 1.0 MB
c751-in.s-INS.40-1 80148101 C751eries SOHO Feature Set, Japan 4.0(1) 0.25 MB 1.0 MB
c760-in.s-US.40-1 80146701 C760 Series SOHO Feature Set, United States 4.0(1) 0.50 MB 1.5 MB
c760-in.s-NET3.40-1 80146801 C760 Series SOHO Feature Set, Europe 4.0(1) 0.50 MB 1.5 MB
c760-in.s-1TR6.40-1 80146901 C760 Series SOHO Feature Set, Germany 4.0(1) 0.50 MB 1.5 MB
c760-in.s-TPH.40-1 80147001 C760 Series SOHO Feature Set, Australia 4.0(1) 0.50 MB 1.5 MB
c760-in.s-INS.40-1 80147101 C760 Series SOHO Feature Set, Japan 4.0(1) 0.50 MB 1.5 MB

Table  4: Image Filenames and Memory Requirements for Remote Office Feature Pack (CD070-RO-4.0)
UNIX Filename DOS Name Description Flash Memory Required DRAM Required
c751-in.r-US.40-1 80148201 C751 Series Remote Office Feature Set, United States 4.0(1)
0.25 MB
1.0 MB
c751-in.r-NET3.40-1 80148301 C751 Series Remote Office Feature Set, Europe 4.0(1) 0.25 MB 1.0 MB
c751-in.r-1TR6.40-1 80148401 C751 Series Remote Office Feature Set, Germany 4.0(1) 0.25 MB 1.0 MB
c751-in.r-TPH.40-1 80148501 C751 Series Remote Office Feature Set, Australia 4.0(1) 0.25 MB 1.0 MB
c751-in.r-INS.40-1 80148601 C751 Series Remote Office Feature Set, Japan 4.0(1) 0.25 MB 1.0 MB
c760-in.r-US.40-1 80147201 C760 Series Remote Office Feature Set, United States 4.0(1)
0.50 MB
1.5 MB
c760-in.r-NET3.40-1 80147301 C760 Series Remote Office Feature Set, Europe 4.0(1) 0.50 MB 1.5 MB
c760-in.r-1TR6.40-1 80147401 C760 Series Remote Office Feature Set, Germany 4.0(1) 0.50 MB 1.5 MB
c760-in.r-TPH.40-1 80147501 C760 Series Remote Office Feature Set, Australia 4.0(1) 0.50 MB 1.5 MB
c760-in.r-INS.40-1 80147601 C760 Series Remote Office Feature Set, Japan 4.0(1) 0.50 MB 1.5 MB

Upgrading the DRAM in the Cisco 760 Series Router

Cisco 760 series and Cisco 770 series routers require 1.5 MB of Dynamic Random-Access Memory (DRAM) to run Software Release 4.0(1). The Cisco 750 series routers require 1.0 MB of DRAM to run Software Release 4.0(1). If it is necessary to upgrade the DRAM in your router, see the Adding Additional Dynamic Random-Access Memory in Cisco 760 Series and CiscoPro CPA760 Series Routers publication for instructions.

The Cisco 770 series routers are shipped with 1.5 MB of DRAM. The Cisco 761, 762, 765, and 766 shipped after September 1996 contain 1.5 MB of DRAM. You do not need to add DRAM to these routers to install Cisco 700 series Software Releases 4.0(1). The Cisco 765-US, 765-CA, 765-CE, 765-NL, 765-UK, 766-US, and 766-CA shipped before September 1996 contain 1 MB of DRAM. You must add at least 0.5 MB of DRAM to these router models to run Cisco 700 Series Software Releases 4.0(1) and higher.

If you are running Cisco 700 series Software Release 3.2(4) or greater, use the show memstat command to find the total memory installed in your Cisco 700 series router. The following shows a typical show memstat command output:

Host> show memstat
ID  0: Size:    10 Avail:    8 Max:    8 Used:    1 Addr: 0x000DDBA8
ID  1: Size:    30 Avail:   69 Max:   80 Used:   16 Addr: 0x000DDDE2
ID  2: Size:    18 Avail:   35 Max:   35 Used:    0 Addr: 0x000DE5A8
ID  3: Size:     4 Avail:   36 Max:   36 Used:    0 Addr: 0x000DE850
ID  4: Size:     8 Avail:  220 Max:  220 Used:    1 Addr: 0x000DE908
ID  5: Size:    32 Avail:  223 Max:  400 Used:  180 Addr: 0x000E0650
ID  6: Size:   268 Avail:   20 Max:   20 Used:    1 Addr: 0x000E2238
ID  7: Size:    20 Avail:   80 Max:   80 Used:    2 Addr: 0x000E3764
ID  8: Size:    14 Avail:  124 Max:  200 Used:   76 Addr: 0x000E41E0
ID  9: Size:    54 Avail:   38 Max:   50 Used:   17 Addr: 0x000E629A
ID 10: Size:     8 Avail:    1 Max:    2 Used:    1 Addr: 0x000EEC40
ID 11: Size:    54 Avail:    6 Max:    6 Used:    0 Addr: 0x000EEC70
ID 12: Size:   462 Avail:    4 Max:    4 Used:    0 Addr: 0x000EF588
ID 13: Size:   134 Avail:    2 Max:    2 Used:    0 Addr: 0x000F00C0
ID 14: Size:    68 Avail:    5 Max:    5 Used:    1 Addr: 0x000F0BB8
ID 15: Size:    96 Avail:    5 Max:    6 Used:    2 Addr: 0x000F0DA0
ID 16: Size:   112 Avail:    2 Max:    2 Used:    0 Addr: 0x000F0FA8
NVStore Used: 1203, Remaining 6989 (Deleted 77 + Unused 6912), Total 8192
RamStore Used: 0, Remaining 10000, Total 10000
RAM Size = 0x180000
Available memory=517088, Allocs=119, Frees=0
MbufAllocs=0x5, MbufFrees=0x5, MbufFail=0x0
IbufAllocs=0x0, IbufFrees=0x0, IbufFails=0x0
MlenMax=0xe0, MlenAvail=0xe0, MlenLow=0xdf, MlenAllocs=0x5, MlenFails=0x0
ZeroMax=0x0, ZeroAvail=0x0, ZeroLow=0x7fff, ZeroAllocs=0x0, ZeroFails=0x0

The RAM Size entry indicates the amount of DRAM installed, reported in hexadecimal. Table 5 lists the RAM size hexadecimal values reported by the show memstat command and the corresponding RAM size in megabytes.


Show memstat Command RAM Sizes
RAM Size (hex) Memory
0x100000 1 MB
0x180000 1.5 MB
0x200000 2 MB

If you do not have at least 1.5 MB of DRAM in your Cisco 760 series router, release 4.0 will not run. You can install another 0.5 MB of DRAM or if you downloaded Cisco 700 series Software Release 4.0(1) and the device will not boot because you do not have enough DRAM, you can reload Cisco 700 series Software Release 3.2(5).

To reload Cisco 700 series Software Release 3.2(5):

Step 1 Power up the router.

Step 2 As soon as the boot banner appears, press the ESC key.

Step 3 Read and follow the software load command instructions in the Cisco 700 Series Command Reference publication if you are loading from a floppy disk or the instructions in the CD booklet if you are loading from a CD.

Step 4 Read and follow the set defaults command instructions in the Cisco 700 Series Command Reference publication.

Complete the following tasks to upgrade to Software Release 4.0(1):

Saving a Configuration

The following steps provide an example of saving the configuration to a file using Terminal for Windows, a popular terminal emulation software program:

Step 1 When the terminal emulation program is running, enter the upload command at the command line prompt, but do not press Return after you enter it:

Step 2 From the Transfer menu, select Receive Text File.

Step 3 In the Receive Text dialog box, specify a filename to save the configuration in and select the directory where you want to save the file.

Step 4 Click OK.

Step 5 Return to the terminal emulation program and press Return to execute the command. The configuration is saved to the file specified in Step 3.

Step 6 Click Stop when the configuration has finished uploading. You are ready to download the software.

Loading New Software and Reloading a Configuration

The following steps provide an example of loading the new software using Terminal for Windows, a popular terminal emulation software program:

Step 1 Read and follow the software load command instructions in the Cisco 700 Series Command Reference publication if you are loading from a floppy disk or the instructions in the CD booklet if you are loading from a CD.

After the new software is loaded, you can load the saved configuration to the router.


Step 2 From the terminal emulation program, go to the Setting menu and select Text Transfer. The Text Transfer dialog box appears.

Step 3 Set flow control to Line at a Time and set Delay Between Lines to 0.5 to 1 second.

Step 4 Click OK.

Step 5 From the Transfer menu, select Send Text File.

Step 6 Select the file you saved in Step 3 in the "Saving a Configuration" section.

Step 7 Click OK. The parameters are transferred to your router.

Step 8 If errors occur during the transfer, enter the set default command, increase the delay between lines and repeat the procedure for loading new software and reloading the configuration, beginning with Step 1.

Configuring the Router Using ClickStart EZSetup

ClickStart allows you to install a Cisco 700 series router by providing a web-based interface that guides you through the installation process. When you have successfully completed an initial installation form, your router is then manageable from a central location, and the fine-tuning or upgrades can be performed remotely.

For the Cisco 700 series routers for Software Release 3.2(4) or higher, the ClickStart EZSetup option is available on the World Wide Web URL http://cco/univercd/data/doc/clckstrt.htm. See the section "Cisco Connection Online" in this document for more information.

Enhancements for Software Release 4.0(1)

Software Release 4.0(1) contains the following software enhancements to Software Release 3.2(5):

The set dhcp server command enables the DHCP Server, with the following options:
set dhcp address start_addr count The range of address to be assigned to DHCP clients, where start_addr is the starting IP address and count is the number of addresses (from 1 to 256) to be assigned. (The default starting address is 10.0.0.2, with 10.0.0.1 assigned to the router.)
set dhcp netmask nnn.nnn.nnn.nnn The subnet mask of the DHCP clients.
set dhcp gateway primary | secondary ip_address The default gateway for the DHCP clients.
set dhcp dns primary | secondary ip_address The Domain Name Servers for the DHCP clients.
set dhcp wins primary | secondary ip_address The WINS servers for the DHCP clients.
reset dhcp domain string The domain string for the DHCP clients.
set dhcp address ip_address | all Removes the lease of an IP address. If ALl is specified, all the leases are cleared.
show dhcp config The current DHCP Server or Relay Agent configuration details.

  • The router can be assigned an IP address from the remote device using Internet Protocol Control Protocol (IPCP) address negotiation. The implementation is based on RFC-1332. It supports IPCP options 1 and 3. (It does not support option 2, TCP/IP Header Compression.) IP unnumbered is supported. IPCP address negotiation is on by default in any profile configured for IP routing. This feature does not support assigning addresses to remote devices.

  • The Port Address Translation (PAT) feature enables local hosts with designated private IP addresses to communicate with the outside world. Basically the router translates the source address of the IP header with a single, global, unique IP address before the packet is forwarded to the outside world. Likewise, IP packets on the return path go through address translations to the designated private IP addresses. When PAT is enabled, the transmission of RIP packets is automatically disabled to prevent leaking private IP addresses to the outside world. To setup a port handler for one of the IP applications defined by the mnemonics or for a decimal port number defined by port number, use the following command:

SEt IP PAt POrthandler DEfault | TElnet | FTp | SMtp | WIns | HTtp | port_number private_ip_addr | OFf
This system level command sets up a port handler for one of the IP applications defined by the mnemonics or for a decimal port number defined by port_number. For example, to define the port 21 (decimal) service handler (for private IP address 10.1.3.1), use set ip pat porthandler 21 10.1.3.1. To undefine the port handler, use set ip pat porthandler 10.1.3.1 off.
There is a limit of 15 entries for this command.
The following example is the PAT configuration used to translate traffic to and from an FTP Server with IP address 10.0.0.3 and a Web Server with IP address 10.0.0.5 that reside on the private LAN: 
(System Level)
Host> set system 760
Host> set user remote
(User Profile)
760:remote> set active remote
760:remote> set ip routing on
760:remote> set ip pat on
760:remote> cd
(System Level)
Host> set ip pat porthandler ftp 10.0.0.3 
Host> set ip pat porthandler http 10.0.0.5

Information on the use of PAT:
Since PAT takes away the end-to-end significance of an IP address, limitations exist when PAT is enabled.

  • PING from an outside host to a host in the private network ends at the Cisco 700 router, and is not forwarded to the inside host.

  • Telnet from an outside host to a host in the private network also ends at the Cisco 700 router if there is no telnet port handler defined.

  • Only one inside or private WWW server is supported. WWW linkages with other inside hosts or servers are not translated.

  • Only one FTP Server, Telnet Server and so forth is supported in the inside network.

  • Packets destined for the Cisco 700 router itself, for example DHCP, SNMP, PING and TFTP, are not subject to the PAT.

  • A maximum of 12 personal computers can simultaneously boot in the inside network. If more than12 personal computers try to boot up simultaneously, one or more can get the error message about not being able to access the server.

  • 400 PAT entries are allocated for sharing among the inside machines. If TCP connections are setup and TCP timeouts are set to keep alive, no more than 400 machines can get to the outside world.

  • The Cisco 700 PAT feature does not handle fragmented FTP packets.

  • Multidestination with unnumbered links does not work for PAT and is not recommended.

  • When a packet is received from the outside, PAT compares the port number with an internally configured port handler list (15 entries, maximum), and if there is a port handler defined for this port, it routes the packet to the appropriate port handler. Otherwise, if there is a default port handler defined it routes the packet there. If it fails to find entries for the above two cases, the Cisco 700 handles the packet itself.

  • Some well known ports cannot have port handlers defined. They include the DHCP client port, used by the Cisco 700 in getting DHCP server responses, and the WINS netbios ports, used by Inside Win'95 PC's to get WINS information.

Refer to the sections describing the set ip pat commands in the Cisco 700 Command Reference publication for more information.

  • The Enhanced Supplementary Voice Services/ISDN feature provides two supplementary services, Call Transfer and three-way Call Conferencing. Call Transfer is the ability to transfer an active call to another number. Three-way Call Conferencing is the ability to add another party to an active call. Up to three people can be conferenced using three-way conferencing. (It is a known limitation that only two Cisco 700 series routers can be conferenced.)

  • The Fee Pulse Mode feature is available for NET3 (same as ETSI) switch types only and requires that you subscribe to "Advice of Charge-D" supplementary service. When the traffic rate falls below the threshold for keeping the call up, the router looks to see how much time is left in the current unit. If the time left is more than the time required to terminate and disconnect the call, the call remains connected. If there is no time remaining, the situation is reevaluated. If traffic is below the threshold, the call is terminated. If the traffic is above the threshold, the time is reset and the call remains connected. When AOC-D is invoked, the switch sends a FACILITY message whenever a unit expires. The router keeps track of the period (in seconds) between these messages.

  • Permanent connections are supported by two new switch types, PERM64 and PERM128. For Japanese (INS) switch types, switch types SD64 and HSD128 are no longer supported; use PERM64 and PERM128.

  • IPX default routes are now supported using the set ipx gateway command. IPX packets are routed to the default gateway if no learned or static route can be found for the destination in the routing table (assuming a default gateway is set and a connection interface exists). The default route is also returned in response to a RIP request, if no route for the network is found. Refer to the Cisco 700 Command Reference publication for more information.

  • When a Service Access Point (SAP) Helper is set, all the SAP Get Nearest Server service request packets received by the router are forwarded to the helper as unicast packets. The router does not look through its own SAP table to try to answer the request.

  • Route Summarization is provided on IP RIP Version 2 (only Version 2 provides the required subnet mask information). When the route summarization is set to auto, the router summarizes routes across the classful boundary to a single route based on the classful boundary. When the route summarization is set to off, the router uses the normal RIP Version 2 routes with VLSMs.

  • The IPX ping feature allows you to determine if the specified IPX node is alive and reachable. Cisco 700 series routers only generate Novell IPX format ping packets. A response by Cisco 700 series routers to Novell IPX ping packets generates a response in Novell IPX format. A response by Cisco 700 series routers to Cisco IPX ping packets generates a response in Cisco IPX format. (If a Novell NetWare server is pinged, the specified server must be running the IPXPING.NLM to respond to the ping. This NLM (NetWare Loadable Module) is part of an IPX Upgrade (IPXRTR.EXE) to NetWare servers.)

  • For interfaces or profiles with IP multicast turned on, an IP multicast packet received from one interface is forwarded to the other interfaces.

  • The IP RIP Update Linkup option for IP RIP enables better interoperability between the router and Cisco IOS software. If the IP RIP update is set to link up for a WAN profile, the IP RIP data is sent as soon as a connection is established and again every 30 seconds for as long as the connection exists. If the connection does not exist, no RIP data is sent. This prevents the line from being brought up by RIP packets where the update is periodic.

  • When a call to the primary outgoing number fails, Second Number Fail-Over causes the associated backup number for that link to be used. If this backup number is not present or is in use, the backup number associated with the other link (if present) is used. This feature applies to both manual and auto data calls.

  • When the router receives an incoming ISDN Setup message, the Callback over D-channel feature extracts the caller ID (if present). The rest of the incoming ISDN Setup message is discarded and the router releases the incoming call. The router searches the user-defined profiles (active and inactive) to see if there is a profile with the CLIcallback set to on. If CLIcallback is set to on, the router checks the caller ID. If the caller ID in the profile matches the caller ID in the incoming call, the router originates a call using the phone number in the profile.

  • The Internet Ready version of this software does not support IPX. This version does not allow the set ipx routing on command.

  • The default encapsulation is Point-to-Point Protocol (PPP), not Combinet Packet Protocol (CPP), to enhance default interoperability with Cisco IOS software.

  • The default PPP authentication outgoing is set to NONE.

  • Software Release 4.0(1) may not interoperate with the existing Connection Manager releases and has not been tested with any of the Connection Manager releases.

  • For the Cisco 770 series routers, use the set button command to assign a profile to the call make | break button command. The ISDN number in the profile will be used to make the call.

  • For the NET3 switch type (Europe), the set alawvoice command can be used to change the voice encoding to Mu-Law for countries such as Taiwan.

  • Distinctive Ringing Feature provides up to three distinctive ring cadences that can be assigned to directory numbers. Use the set phone command to set the ring cadence.

Software Release Modifications

This section describes the corrections to the software releases. Each software correction includes the Cisco DDTS tracking number.

Modifications from 3.2.(5) to 4.0 (1)

This section describes Software Release 4.0(1) corrections to Software Release 3.2(5).


  1. A Cisco 765 router placed a call on one B channel. The remote Cisco IOS software cleared and called the Cisco 765 back on another B channel. The callback to the Cisco 765 fails. Software Release 4.0(1) corrects the problem. [CSCdi74626]

  2. The attempted access of an Octel Voice Mail system resulted in the call being disconnected. The call is released when information messages are received from a DMS switch type in state 4. [CSCdi74573]

  3. Some BT System X switches sent invalid length (0xFC) in the Calling Party Number IE, causing the router to crash. This has been fixed by rejecting calls with invalid Calling Party Number IE. [CSCdi80176]

  4. The POTS port on Cisco 765 routers occasionally locked up. A busy signal was heard and the port could not be disconnected. Software Release 4.0(1) corrects the problem. [CSCdi85725]

  5. Although the router has no physical voice abilities, the router answered incoming voice calls. Software Release 4.0(1) corrects the problem. [CSCdi76205]

  6. If internal tones were on and the U.S. code was loaded on the router, both internal tones and the tones for the ISDN lines were generated. Now, when the software is loaded, the internal tone generator is turned off. Upon off-hook, the caller only hears the tone provided by the central office. [CSCdi57762]

Modifications from 3.2(4) to 3.2(5)

This section describes Software Release 3.2(5) corrections to Software Release 3.2(4).


  1. When the set default gateway was called, and a profile was opened, the IP static route in the first profile was deleted by the second profile. The software and hardware were modified to fix this problem. [CSCdi67490] and [CSCdi67502]

  2. Many Japanese answering machines and telephones were not working with the analog phone interface. They could not detect an incoming call, a disconnect or both. This is how the answering machines know when the call has ended. The software and hardware were modified to fix this problem. [CSCdi74591]

Software Release Caveats

This section describes suggestions for optimum use of Cisco 700 series software releases. Where applicable, the software caveat includes the Cisco DDTS tracking number.

Software Release 4.0(1) Caveats

This section describes suggestions for optimum use of Cisco 700 series Software Release 4.0(1).


  1. When using the PERM64 switch type for permanent connection, the Cisco 700 series router always uses B1-Channel. If B2-Channel is enabled (but not B1), the B2-Channel does not work. For PERM128, both B1 and B2 channels are enabled and combined as a 128 Kbps pipe connection. [CSCdi76629]

  2. When a Cisco 760 or Cisco 770 series router is running on a Dedicated Mode line, the analog phone interface (POTS) cannot be used. If a phone is hooked up, you receive a fast-busy tone. Error messages are logged (if the log is enabled), but the condition does not affect other operations. [CSCdi76599]

  3. For certain NET3 switch types, call waiting tones to a third party disconnect a first and second party. In other words, a voice call is connected between parties A and B. C tries to call A and A hears a call waiting tone. If A does not respond to the call waiting tone and C hangs up, A and B are disconnected. To avoid this condition, turn the Call Waiting feature off.

  4. For DMS switch types, a call cannot be transferred until the party the call is being transferred to answers the call. In other words, a voice call is connected between parties A and B, if B transfers the call from A to C and B hangs up before C answers, the call is disconnected.

  5. The set alawvoice on|off command works if it is entered as se al on or se al of. It does not work correctly if the command is written out as set alawvoice on or set alawvoice off. [CSCdi87384]

  6. During a voice call, if the '*' is pressed on the phone keypad, the other party cannot be heard for three seconds. For example, if '*' is pressed while in voice mail, it takes three seconds to hear it again.

  7. If you downgrade from Software Release 4.0 to Software Release 3.2, you must use the set default command to set all variable parameters to the default values before uploading your original 3.2 configuration. The directory numbers in Software Release 4.0 are stored differently than the directory numbers in Software Release 3.2. If you do not reset the default variable parameters, the results are unpredictable.

  8. 3W Call Conferencing does not work for 5ESS-NI1 switches. After the second command is entered, the B channel is disabled. The controller (originator) is blocked off from the voice call with the other two parties. [CSCdi90483]

  9. For IPCP address negotiation, if the IPCP address assignment is placed on the Internal profile, the address cannot be in the same network as the remote router's ethernet address. A manually configured IP address can exist on the Internal profile, allowing the IPCP address to be assigned on the WAN profile. The IPCP address on the WAN profile can be in the same network as the remote router's ethernet address.

  10. The Cisco 766 router dials into a Cisco 4000 series router, gets an IP address from the default pool, but cannot ping anything in either direction. To correct the problem, try the following modifications to the configuration:

Step 1 Set the Internal profile net mask to 0.0.0.0 and IP address to 10.0.0.1.

Step 2 Set the LAN profile IP address to 0.0.0.0 and net mask to 0.0.0.0 and turn on bridging.

Step 3 Reboot the 760.

This forces the DHCP server to be set up on the LAN side and forces the negotiated IP address from the 4000 to be set on the WAN user profile. The 760 does IPCP negotiation with the illegal address of 10.0.0.1 and is rejected by the IOS router which assigns an IP address of 171.68.74.241 and the 760 sets this IP address into its WAN profile.


Software Release 3.2(4) Caveats

This section describes suggestions for optimum use of CiscoPro C760 Software Release 3.2(4).


  1. When using TACACS with the Cisco Connection Manager, you must enter the password within two minutes to prevent a line integrity violation.

  2. If Cisco Connection Manager registers the router while a Cisco ConnectPro session is running, you should reboot the router to log into Cisco ConnectPro again.

  3. NetWare 4.x servers in the same domain over the ISDN WAN link will keep the B channel up continuously because of NDS traffic. Attempting to filter out the NDS traffic will result in loss of communication between the remote server and the services from the domain. [CSCdi44240]

  4. If a router has an IPX routing connection, and encapsulation is changed from PPP to CPP (or from CPP to PPP), IPX routing might cease. To clear this problem, deactivate the connected profiles on both the local and remote routers, and then reactivate the profile. [CSCdi51147]

  5. When a call is made to a router controlled by Connection Manager, and the Connection Manager is using a Security Dynamics authentication server, there is a problem with the way timeouts are handled. After the local router asks for a username, it waits two minutes before timing out and disconnecting the call. If another call is placed immediately after this, it will fail, and the message "Invalid Packet" will appear. [CSCdi54358]

  6. When you download configuration information using the console port, you must slow down the download process to avoid an overrun of configuration information. (A one-second delay is recommended.) Failure to include an appropriate delay might result in the user interface pausing indefinitely, perhaps requiring manual power-cycling of the router to recover. [CSCdi49689]

  7. A problem exists when you make two data calls and one voice call. When you make a data call to another router from one of the channels, and another unit makes a voice call to the other free channel of the called router, if you do not answer the voice call, the message "Call Requested; Voice call routed to Phonex" will appear. The voice call will be dropped. [CSCdi55816]

  8. The upload command is not sending SNMP contact names and SNMP location names correctly. [CSCdi56038]

  9. If your LAN frame type is set to a value other than 802.3, you might experience intermittent failures logging from your remote client workstation to the main LAN. This is sometimes manifested because of a delay in sending the RIP updates, even when your RIP update mode is set to demand. This is more noticeable if you have a multinetwork environment (for example, 802.3, 802.2, Ethernet_II, and SNAP) on the same segment where the RIP and SAP routes can easily exceed the 400-entry design limitation. [CSCdi54882]

  10. When parameters are set to initiate demand calls to multidestination, the system eventually fails to connect to the two different destinations. After several connections and disconnections due to set timeout values, both outgoing calls are initiated toward a single destination. [CSCdi56557]

  11. A password cannot be recovered. In the event of a system password being lost or forgotten, call the Technical Assistance Center (TAC) for a replacement password.

  12. The set phone command Data Over Voice (DOV) Calls field, which applies to U.S. switch types only, is not getting blocked in international code.

  13. After upgrading to Software Release 3.2(4) from Software Release 3.1(2), you must use the set rip receive command to turn RIP on. The 3.1 setting of "on" will be interpreted as "off" by Software Release 3.2(4).
Note British Telecom's Auxiliary working service does not allow the Cisco 765 router to discriminate called numbers to route calls to the second basic telephone service port. To enable this functionality, you must configure the line for Multiple Subscriber Numbers (MSN).

Documentation Corrections and Modifications to the Product Documentation

This section describes corrections and modifications to the printed command reference publication for Software Release 4.0(1). Note that these modifications may be included in online versions of the command reference (that is, the Documentation CD and Cisco Connection Online).

To improve performance, only the services defined in Novell IPX Router Specification 107-000029-001 are supported, and a maximum of 400 IPX route entries and 200 good IPX SAPs are allowed. If you need larger route and SAPs entries, Software Release 4.0(1) supports IPX SAP HELPER and IPX default route commands.



Obtaining Service and Support

For service and support for a product purchased from a reseller, contact the reseller. Resellers offer a wide variety of Cisco service and support programs, which are described in the section "Service and Support" in the information packet that shipped with your chassis.

For service and support for a product purchased directly from Cisco, use CCO.

Cisco Connection Online

CCO is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional content and services.

Note If you purchased your product from a reseller, you can access CCO as a guest. Your reseller offers programs that include direct access to CCO's services.

Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.

CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously--a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.

You can access CCO in the following ways:

  • WWW:  http://www.cisco.com.

  • WWW:  http://www-europe.cisco.com.

  • WWW:  http://www-china.cisco.com.

  • Telnet:  cco.cisco.com.

  • Modem:  From North America, 408 526-8070; from Europe, 33 1 64 46 40 82. Use the following terminal settings: VT100 emulation; databits: 8; parity: none; stop bits: 1; and connection rates up to 28.8 kbps.

Copyright 1989-1997 © Cisco Systems Inc.
InfoBlast Homepage