|
|
July 17, 2000
The Release Notes for Cisco VCWare Version 6.08 for Cisco AS5300/Voice Gateway describe new features, memory requirements, hardware support, software platform deferrals, and changes to the voice feature card software (VCWare), digital signal processor (DSP) firmware (DSPWare), and Cisco IOS software.
Cisco VCWare Version 6.08 supports modem and facsimile detection and Pulse Code Modulation (PCM) switchover with VoIP RealTime Transport Protocol (RTP) into platform-independent DSPware and is intended for use with Cisco IOS Release 12.1(2a)T1 on Cisco AS5300/Voice Gateway universal access servers.
This document contains the following sections:
The Cisco AS5300 universal access server is an award-winning dialup remote access server and/or Voice-over-IP (VoIP) Gateway. When equipped with voice feature cards (VFCs) and voice-enabled Cisco IOS software, the Cisco AS5300/Voice Gateway supports carrier-class VoIP and Fax-over-IP services.
The Cisco AS5300 includes three feature card slots. One slot holds a T1/E1/PRI feature card, while the other two support digital modem feature cards or voice DSP feature cards. When equipped with modem cards, the Cisco AS5300 serves as a remote access concentrator for dialup (modem or ISDN) Internet access. When equipped with voice feature cards and voice IOS, the Cisco AS5300 serves as a VoIP Gateway. The Cisco AS5300 can serve in both capacities using one slot for modems and the other for voice DSPs. Modem, voice, or fax calls are routed to the appropriate cards/resources via Dialed Number Identification Service (DNIS). A called-party number is one example.
The Cisco AS5300 supports High-Density VoIP applications: Up to 96/120 voice or fax calls using 4 T1/E1 ports in a two-rack unit (RU) form factor. This High-Density VoIP application requires a minimum of Cisco IOS Release 12.0(4)XH1or higher and High-Density voice feature cards with TI c549-based DSP modules (part number AS53-VOXD) and associated voice card firmware.
Cisco IOS 12.0(2)XH was the first release to support High-Density VoIP. Cisco IOS 12.0(4)XH1 was the first release to support the following:
This section contains Cisco IOS release and Cisco VCWare compatibility information, system and memory requirements, and restrictions.
Each Cisco VCWare version should be used with its compatible Cisco IOS release. Cisco VCWare is not backward compatible and should not be used with earlier Cisco IOS releases. Cisco IOS Release 12.1(2a)T1 is the recommended Cisco IOS releases for Cisco VCWare 6.08.
 |
Note The compatibility matrixes below indicate the earliest version of a given Cisco IOS software branch that is compatible with the listed portware. If the indicated version of Cisco IOS software is not available on CCO (Cisco Connection Online) for any reason, any subsequent Cisco IOS software version of the same branch will also work. |
| Cisco VCWare Solution Supported | Cisco VCWare Version | Cisco IOS Software Release | ||
|---|---|---|---|---|
Cisco VCWare Version 6.08 contains the same functionality as the previous release with the following changes:
| 6.08 with Cisco DSPWare 3.3.13 | 12.1(2a)T2 | ||
Cisco VCWare Version 5.12 contains the same functionality as the previous release with the following changes:
| 5.12 with Cisco DSPWare 3.2.18 | 12.0(6)T, 12.0(7)T, 12.1(1), 12.1(1a)T1, 12.1(2a), 12.1(1)AA1, 12.1(2a)AA | ||
Cisco VCWare Version 5.09 contains the same functionality as the previous release with the following changes:
| 5.09 with Cisco DSPWare 3.2.17 | 12.0(7)XR2 | ||
Support for High-Density voice cards (c549-based DSP Modules, p/n AS53-VOXD) and earlier generation c542-based DSP modules. Also adds new codecs including G.723.1, G.726, and G.728.
| 4.10 with Cisco DSPWare 3.1.10 | 12.0(4)XH1, 12.0(6)T, 12.0(7)T | ||
Support for c549-based DSP modules and c542-based DSP modules with two separate VCWare images. | 4.04 with Cisco DSPWare 3.1.7 | 12.0(4)XH, 12.0(5)T2, 12.0(7)T | ||
Support for High-Density voice cards (TI c549-based DSP Modules, p/n AS53-VOXD) and adds new codecs, including G.723.1. | 4.04 with Cisco DSPWare 3.1.7 | 12.0(2)XH | ||
Improved comfort noise functionality. For TI c542-based DSP Modules, p/n AS53-6VOX. | 2.52 with Cisco DSPWare 2.3(3) | 11.3(8)NA1 | ||
Includes E1/R2, MFC/R2 support.2 | 2.4 with Cisco DSPWare 2.3(3) | 11.3(6)NA2 through 11.3(10)NA. Do not use with prior releases of 11.3NA. | ||
Includes T1 CAS support. | 1.0 | 11.3(2)NA to 11.3(5)NA |
| 1For more information about codec feature sets, see the Cisco VCWare release notes. 2All follow-on releases include caveat updates, performance improvements, and so on. |
Further compatibility information is located at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/iosrn/vcwrn/vcwrmtrx.htm
Cisco VCWare Version 6.08 on the Cisco AS5300 universal access server requires the following voice-specific Cisco IOS+ images:
|
Note Support of the Open Settlements Protocol (OSP) on the Cisco AS5300/Voice Gateway requires the Enterprise Voice Plus IPSEC56 IOS images released with 12.0(4)XH1. Only the billing and negotiation/transaction messages between the Voice Gateway and the settlements server are encrypted, not VoIP payload traffic: This image does not support voice encryption. See the Features and Restrictions sections for more information about Cisco VCWare and Cisco IOS release compatibility. |
Table 2 contains the memory requirements for the Cisco AS5300 feature sets supported by Cisco IOS Release 12.0(4)XH1 through 12.1(2a)T1.
For more information about Cisco IOS releases, see Related Documentation.
Table 3 lists the interface and modem cards supported by the Cisco AS5300 universal access server.
Interface Card | Modem Card |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
There are no new or changed features in this release.
For complete information about Cisco IOS Release 12.1(2a)T1, see the Cisco AS5300 Access Server release notes for Cisco IOS Release 12.1(2a)T1 and New Feature Documentation for Cisco IOS Release 12.1(2a)T1.
The following features were introduced in Cisco VCWare Version 4.10 and 5.12 and are still supported with Cisco VCWare Version 6.08.
|
Note The Limited Codecs feature set uses G.729(a) versus the All Codecs feature set, which uses G.729. G.729(a) is a lower-complexity version of G.729; however the two are fully interoperable. |
|
Note The low statistical probability of modem/fax signals over a given channel can be utilized to overcome the bandwidth consumption for these channels. |
Cisco VCWare Version 6.08 requires that the following DSPWare components be implemented:
For switching out of PCM mode back to compressed mode, there are two possible procedures:
During the switch-out of PCM mode, there will be an interruption of the signal (drop-out) until both channels have been reconfigured for compressed speech mode. The host must go into idle mode before you can reconfigure the channel for compressed mode.
Additional restrictions:
|
Note Since four T1 ports translate to 96 calls, this limit applies only to the four E1s. |
|
Note Factory default setting is 20ms packet size. |
There are no bugs in this release.
|
Note If you have an account with Cisco Connection Online (CCO), you can use Bug Navigator II to find caveats of any severity for any Cisco software release. You can reach Bug Navigator II on CCO at Service & Support: Online Technical Support: Software Bug Toolkit Or at http://www.cisco.com/support/bugtools Or see the Software Bug Toolkit section below. |
This section provides instructions for upgrading Voice Feature Card VCWare using a PC. If you are not in a PC environment, use the procedures as general guidelines; the steps are similar.
Use the procedures in the following sections to upgrade your Cisco VCWare:
1. Determining Your Software Release
2. Installing the TFTP Application on Your PC
3. Connecting Your PC with the Access Server
4. Establishing Console Session
5. Pinging Your PC and the Access Server
6. Identifying Voice Feature Cards
7. Replacing Firmware with Cisco VCWare in VCWare Mode or Replacing Firmware with Cisco VCWare in ROM Monitor Mode
Use the following link to download the latest Cisco VCWare software release:
http://www.cisco.com/cgi-bin/tablebuild.pl/vcware
|
Note You must have an account with CCO and be logged in to download new Cisco VCWare software releases. See Obtaining Documentation for access instructions. |
To determine the release of Cisco IOS software running on your access server, log in to the access server and enter the show version user EXEC command:
5300# show version Cisco Internetwork Operating System Software IOS (tm) 5300 Software (C5300-IS-MZ), Version 12.1(2a)T1
The output contains additional information, including processor revision numbers, memory amounts, hardware IDs, and partition information. See Example show version Output for an example of the show version command output.
This section provides instructions for installing a TFTP application on your PC to transfer the latest Cisco VCWare file. Ignore this section if:
|
Note If you are using a UNIX or Sun workstation or a Macintosh, refer to your system user manuals for native TFTP applications. You can also use a remote copy protocol (RCP) application available from independent software vendors. A number of TFTP programs are also available as shareware from public sources on the World Wide Web. |
Use the following steps to install the TFTP:
Step 2 Open your Internet browser, log onto CCO (for login instructions, see Obtaining Documentation), and go to the following site to find the download instructions for the TFTP program:
http://www.cisco.com/kobayashi/sw-center/sw-internet.shtml
|
Note The TFTP program currently at the URL noted above is provided as a courtesy of Cisco Systems and is not an officially supported product. This URL can change at any time without notice. |
Step 3 Click TFTP Server for Windows 95/Windows 98/NT 4.0.
Step 4 Follow the instructions to the Software Download page to download the software to your hard drive.
Step 5 Double-click the executable file and follow the screen directions.
Step 6 Go to your c:\tftpboot directory and double-click tftpsrv.exe to launch the TFTP server application.
Step 7 Set your TFTP server application root directory:
a. Choose Server Root Directory from the Options menu.
b. Double-click tftpboot in the [] list box. If necessary, choose drive C from the Drives list box.
c. Click OK. The status bar below the menu bar displays c:\tftpboot as the TFTP server application root directory.
|
Note You must select the c:\tftpboot directory as your TFTP server application root directory to perform any backup procedures. This also applies if you are using an RCP on your system. |
Continue with the following section, "Connecting Your PC with the Access Server."
Use the steps in this section to connect your PC to the access server. If you are not using a PC, skip this section, or use the procedure as a guideline.
Step 2 Connect your PC COM port to the access server console port using the standard Cisco console cable.
Step 3 Make sure the PC, access server, and hub are all powered ON.
Continue with the following section, "Establishing Console Session."
Use the steps in this section to establish a console session from your PC to the Cisco AS5300. You will use this session to talk to the access server. If you are not using a PC, ignore this section, or use the procedure as a guideline.
Step 2 Double-click Hypertrm.exe to display the Connection Description dialog box.
Step 3 Enter a name for your connection, (AS5300, for example), and click OK. HyperTerminal displays the Phone Number dialog box.
Step 4 Choose the COM port connecting the PC and the access server in the Connect Using list box. You have options to connect directly to one of four COM ports.
Step 5 Click OK. HyperTerminal displays the COM Properties dialog box.
Step 6 Choose the following options in the COM Properties dialog box, then click OK:
Step 7 Press Enter until the access server displays the prompt. You are prompted to enter a login password if login is configured.
|
Note If the access server prompt does not appear, you might have selected the wrong COM port, the cables might not be connected properly, or the access server might not be powered on. Check these before continuing. |
Step 8 Change to enable mode (also called Privileged EXEC mode) by entering the following command and your system password:
5300> enable
Password: password
5300#
Step 9 Keep the HyperTerminal window open, and continue with the following section, "Pinging Your PC and the Access Server."
Use the steps in this section to ping the access server and the PC to verify that they are talking to each other and that there are no configuration problems on your access server. If you are not using a PC, skip this section, or use the procedure as a guideline.
|
Note The PC used for the upgrade and the access server you are upgrading must have the same subnet mask. |
a. On your desktop, choose Start/Run to display the Run dialog box.
b. Enter winipcfg, and click OK to display the IP Configuration dialog box.
5300> winipcfg
c. Choose the PC adapter connector (Ethernet or Token Ring) used for the connection to the router or access server if you have more than one adapter connector installed on your PC.
d. Make a note of the PC IP address, and then click OK.
|
Note You must have an IP address assigned before you can continue. Enter the show running-configuration command at the access server 5300# prompt to verify that the access server has an assigned IP address. If the access server does not have an IP address, see your access server documentation for details on assigning an IP address. |
Step 2 In the HyperTerminal dialog box make sure you are at the 5300# prompt (see Establishing Console Session).
Step 3 Enter the ping command with your PC IP address:
5300# ping XXX.XXX.XXX.XXX
The access server displays five exclamation points (!) if everything is working and it displays five dots (.....) if there is a problem. If there is a problem, check the cabling between the router and the PC and check the access server configuration.
Step 4 Keep the HyperTerminal window open and continue with the following section, "Upgrading to a New Release," which describes how to identify voice cards in the system and download the new software.
To download Cisco VCWare to your voice card, do the following:
1. Identify your voice feature cards to determine whether the VFC is in VCWare mode or ROM monitor mode. Knowing which mode you are in determines how you download software to the VFC. (See Identifying Voice Feature Cards.)
2. Check to see that the version of VFC ROM monitor software version 1.2 or 1.3 is compatible with your installed Cisco IOS image. Cisco VCWare Version 6.08 or higher requires Cisco IOS Release 12.1(2a)T1 or higher.
|
Note In certain countries, use of these products or provision of voice telephony over the Internet may be prohibited and/or subject to laws, regulations, or licenses, including requirements applicable to the use of the products under telecommunications and other laws and regulations; customer must comply with all such applicable laws in the countries where customer intends to use the product. For more information about these regulations, refer to the following link: http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/5300pnc.htm |
Use the following steps to identify the voice cards in the system and determine whether the VFC is in VCWare mode or ROM monitor mode. This determines how you download software to the VFC. If Cisco VCWare is not loaded on the VFC, you can use ROM monitor mode to download the VCWare. Otherwise, download the software in VCWare mode.
5300# show vfc 0-2 technology Technology in VFC slot 0-2 is C549
If the technology is either c542 or the show vfc 0-2 technology command does not work for you, go to Step 5.
Step 2 Determine the complexity mode.
a. To find the complexity mode, enter the following:
5300# show vfc 0-2 cap-list Capability List for VFC in slot 1: 1. cor-vfc-hc-l.3.3.13.bin 2. bas-vfc-hc-l.3.3.13.bin 3. fax-vfc-hc-l.3.3.13.bin 4. cdc-g711-hc-l.3.3.13.bin 5. cdc-g726-hc-l.3.3.13.bin 6. cdc-g729-hc-l.3.3.13.bin 7. cdc-g728-hc-l.3.3.13.bin 8. cdc-g723.1-hc-l.3.3.13.bin
b. Examine the cor-vfc- output (line #1). If it is of the form cor-vfc-hc-l.x.x.x.bin, you are in high complexity mode. If it is of the form cor-vfc-mc-l.x.x.x.bin, you are in medium complexity mode.
Step 3 Enter enable mode:
5300> enable
Step 4 Enter your password:
Password: password 5300#
You are in enable mode when the prompt changes to 5300#.
Step 5 Determine the number of voice cards in the system, the slot number for each card, and the VFC mode (VCWare or ROM monitor) in which you are running.
5300# show vfc 0-2 board
The VFC mode is indicated as follows:
Note the location and the mode type for each voice card. You will need this information when you upgrade the Cisco VCWare.
When you have completed the steps above, use one of the following procedures:
Use the steps that follow to download new voice software if your voice card is running in VCWare mode. When downloading from a diskette, first copy the software from the diskette to a TFTP server. After the software is loaded onto the TFTP server, follow the steps in the next section.
 |
Caution Erasing the VFC files can result in system outage or the corruption of your VFC board. Make sure that the correct version of software resides on your TFTP server before continuing. |
5300# erase vfc slot_number This will erase the contents of VFC Flash. Continue ?[y/n]:Y This will take some time. Please, wait...vfc
If this command fails, use the instructions in the Replacing Firmware with Cisco VCWare in ROM Monitor Mode section.
Step 2 Optional. Verify that the VFC Flash memory is empty:
5300# show vfc slot_number directory
Step 3 Copy your files using the following criteria and the copy tftp: vfc command.
For Cisco IOS Releases 12.0(2)XH, 12.0(4)XH, 12.0(4)XH1, and higher, use the following:
5300# copy tftp: vfc: Address or name of remote host []? 223.255.212.244 Source file name []? /path/vcw-vfc-mz.c549.hc.6.08.bin Destination file name []? vcw-vfc-mz.c549.hc.6.08.bin Accessing tftp://223.255.212.244/path/vcw-vfc-mz.c549.hc.6.08.bin... Voice card slot number slot ? 1 Copy "tftp://223.255.212.244/path/vcw-vfc-mz.c549.hc.6.08.bin" to VFC? [yes/no] Y Loading vcw-vfc-mz.c549.hc.6.08.bin from 223.255.212.244 (via Ethernet0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 491256/982016 bytes]
For Cisco Release 11.3(2)NA, use the following:
5300# copy tftp vfc Voice card slot number slot ? 1 Address or name of remote host [UNKNOWN]? 223.255.212.244 Source file name? /path/vcw-vfc-mz.1.0.bin Destination file name [vcw-vfc-mz.1.0.bin]? vcw-vfc-mz.1.0.bin ! note, the destination filename is *IMPORTANT* Accessing file 'vcw-vfc-mz.1.0.bin' on 223.255.212.244... Loading vcw-vfc-mz.1.0.bin from 223.255.212.244 (via Ethernet0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 291292/291328 bytes]
|
Note The destination image name must begin with "vcw-" (all lowercase); no character can be in front of vcw- (no directory path can be included at the beginning of the image name). Be absolutely certain to enter the name correctly. If any character or space is entered incorrectly, the file will not be recognized and will not be copied. |
Step 4 Verify that Cisco VCWare is in the VFC Flash memory by listing the directory files using the following commands:
5300# show vfc slot_number directory 5300#
Step 5 Reload the VFC code from Flash memory for the specified slot before you unbundle the new VFC image.
5300# clear vfc slot_number 5300#
Step 6 Unbundle Cisco DSPWare from the Cisco VCWare and configure the file and capability lists with default values. (See Step 9 and Step 10.)
5300# unbundle vfc slot_number Do you want to continue ? [y/n]: y
Step 7 Press y to continue.
Step 8 Verify that DSPWare is unbundled by listing the directory files:
5300# show vfc slot_number directory 5300#
Step 9 Verify that the default file list is initialized by listing the default files:
5300# show vfc slot_number default-file 5300#
Step 10 Verify that the capability list is populated by listing the capability list files:
5300# show vfc slot_number cap-list 5300#
Step 11 Reboot the Cisco AS5300 for these changes to take effect.
5300# reload
Check that you have successfully downloaded the software by doing the following:
5300# show vfc 1 dir Files in slot 1 VFC flash: File Name Size (Bytes) 1 . vcw-vfc-mz.c549.hc.6.08.bin 506636 2 . btl-vfc-l.0.1.bin 1882 3 . btj-vfc-l.0.1.bin 4174 4 . jbc-vfc-l.3.0.bin 12808 5 . cor-vfc-hc-l.3.3.13.bin 195392 6 . bas-vfc-hc-l.3.3.13.bin 210 7 . fax-vfc-hc-l.3.3.13.bin 20730 8 . cdc-g711-hc-l.3.3.13.bin 210 9 . cdc-g726-hc-l.3.3.13.bin 5370 10. cdc-g729-hc-l.3.3.13.bin 31124 11. cdc-g728-hc-l.3.3.13.bin 22208 12. cdc-g723.1-hc-l.3.3.13.bin 32736
|
Note If this command times out, repeat the process beginning with the steps in the Identifying Voice Feature Cards section. |
5300A#sh vfc 1 defDefault File List for VFC in slot 1:1. btl-vfc-l.0.1.bin 2. cor-vfc-hc-l.3.3.13.bin 3. bas-vfc-hc-l.3.3.13.bin 4. cdc-g729-hc-l.3.3.13.bin 5. fax-vfc-hc-l.3.3.13.bin 6. jbc-vfc-l.3.0.bin 7. btj-vfc-l.0.1.bin5300A#sh vfc 1 cap-listCapability List for VFC in slot 1:1. cor-vfc-hc-l.3.3.13.bin 2. bas-vfc-hc-l.3.3.13.bin 3. fax-vfc-hc-l.3.3.13.bin 4. cdc-g711-hc-l.3.3.13.bin 5. cdc-g726-hc-l.3.3.13.bin 6. cdc-g729-hc-l.3.3.13.bin 7. cdc-g728-hc-l.3.3.13.bin 8. cdc-g723.1-hc-l.3.3.13.bin
If you are having trouble downloading the voice card software in VCWare mode, try the following:
5300# show vfc 1 board VFC board state is UP, vfc status VCWARE running(0x4) VFC board in slot 1 with 24 dsps 5300#
5300# sh vfc 1 ver vcwVoice Feature Card in Slot 1: VCware Version : 6.08 ROM Monitor Version: 1.2 DSPware Version : 3.3.13 Technology : C549
Use the steps that follow to download new voice software if your voice card is running in ROM monitor mode. When downloading from a diskette, first copy the software from the diskette to a TFTP server. After the software is loaded onto the TFTP server, follow the steps in the next section.
|
Caution Erasing the VFC files can result in system outage or the corruption of your VFC board. Check to ensure that the correct version of software resides on your TFTP server before continuing. |
5300# clear vfc slot_number purge debug vfc slot_number start debug vfc slot_number cons flash erase
This will erase the contents of VFC Flash. Continue ?[y/n]: y This will take some time. Please, wait...vfc
Step 2 Press y to continue.
Step 3 Copy your files using the following criteria and the copy tftp: vfc command.
For Cisco IOS Releases 12.0(2)XH, 12.0(4)XH, 12.0(4)XH1, and higher, use the following:
5300# copy tftp: vfc: Address or name of remote host []? 223.255.212.244 Source file name []? /path/vcw-vfc-mz.c549.hc.6.08.bin Destination file name []? vcw-vfc-mz.c549.hc.6.08.bin Accessing tftp://223.255.212.244/path/vcw-vfc-mz.c549.hc.6.08.bin... Voice card slot number slot ? 1 Copy "tftp://223.255.212.244/path/vcw-vfc-mz.6.08.bin" to VFC? [yes/no] Y Loading vcw-vfc-mz.c549.hc.6.08.bin from 223.255.212.244 (via Ethernet0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 491256/982016 bytes]
For Cisco Release 11.3(2)NA, use the following:
5300# copy tftp vfc Voice card slot number slot ? 1 Address or name of remote host [UNKNOWN]? 223.255.212.244 Source file name? /path/vcw-vfc-mz.1.0.bin Destination file name [vcw-vfc-mz.1.0.bin]? vcw-vfc-mz.1.0.bin ! note, the destination filename is *IMPORTANT* Accessing file 'vcw-vfc-mz.1.0.bin' on 223.255.212.244... Loading vcw-vfc-mz.1.0.bin from 223.255.212.244 (via Ethernet0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 291292/291328 bytes]
|
Note The destination image name must begin with "vcw-" (all lowercase); no character can be in front of vcw- (no directory path can be included at the beginning of the image name). Be absolutely certain to enter the name correctly. If any character or space is entered incorrectly, the file will not be recognized and will not be copied. |
Step 4 Report the type of DSP supported (c542 or c549) by the Cisco VCWare by entering the following command:
5300# show vfc slot_number technology 5300#
Step 5 Reload the VFC code from Flash memory for the specified slot before you unbundle the new VFC image.
5300> clear vfc slot_number
Do you really want to reset this card ? [y/n] y Please, wait...
Step 6 Press y to verify the reset function.
Step 7 Unbundle Cisco DSPWare from Cisco VCWare and configure the file and the capability lists with default values (see also Step 10 and Step 11):
5300# unbundle vfc slot_number
Do you want to continue ? [y/n]: y
Step 8 Press y to continue.
Step 9 Verify that DSPWare is unbundled by listing the directory files as follows:
5300# show vfc slot_number directory 5300#
Step 10 Verify that the default file list is initialized by listing the default files as follows:
5300# show vfc slot_number default-file 5300#
Step 11 Verify that the capability list is populated by listing the capability list files:
5300# show vfc slot_number cap-list 5300#
Step 12 Reboot the Cisco AS5300 for these changes to take effect.
5300# reload
Check that you have successfully downloaded the software by doing the following:
5300# show vfc 1 dir Files in slot 1 VFC flash: File Name Size (Bytes) 1 . vcw-vfc-mz.c549.hc.6.08.bin 506636 2 . btl-vfc-l.0.1.bin 1882 3 . btj-vfc-l.0.1.bin 4174 4 . jbc-vfc-l.3.0.bin 12808 5 . cor-vfc-hc-l.3.3.13.bin 195392 6 . bas-vfc-hc-l.3.3.13.bin 210 7 . fax-vfc-hc-l.3.3.13.bin 20730 8 . cdc-g711-hc-l.3.3.13.bin 210 9 . cdc-g726-hc-l.3.3.13.bin 5370 10. cdc-g729-hc-l.3.3.13.bin 31124 11. cdc-g728-hc-l.3.3.13.bin 22208 12. cdc-g723.1-hc-l.3.3.13.bin 32736
|
Note If this command times out, repeat the process beginning with the steps in the Identifying Voice Feature Cards section. |
5300# show vfc 1 def (full word is default-file) Default File List for VFC in slot 1: 1. btl-vfc-l.0.1.bin 2. cor-vfc-hc-l.3.3.13.bin 3. bas-vfc-hc-l.3.3.13.bin 4. cdc-g729-hc-l.3.3.13.bin 5. fax-vfc-hc-l.3.3.13.bin 6. jbc-vfc-l.3.0.bin 7. btj-vfc-l.0.1.bin 5300# show vfc 1 cap-list Capability List for VFC in slot 1: 1. cor-vfc-hc-l.3.3.13.bin 2. bas-vfc-hc-l.3.3.13.bin 3. fax-vfc-hc-l.3.3.13.bin 4. cdc-g711-hc-l.3.3.13.bin 5. cdc-g726-hc-l.3.3.13.bin 6. cdc-g729-hc-l.3.3.13.bin 7. cdc-g728-hc-l.3.3.13.bin 8. cdc-g723.1-hc-l.3.3.13.bin 5300#
If you are having trouble downloading the voice card software in ROM monitor mode, try the following:
5300# show vfc 1 board VFC board state is UP, vfc status VCWARE running(0x4) VFC board in slot 1 with 24 dsps 5300# Determine if the VFC ROM version you are running is Version 1.2 or Version 1.3. 5300# sh vfc 1 ver vcw Voice Feature Card in Slot 1: VCware Version : 6.08 ROM Monitor Version: 1.2 DSPware Version : 3.3.13 Technology : C549
This section contains tips and workarounds for ensuring correct installation and operation of Cisco VCWare.
The following is an example of output from the show version command with two VFC cards fully populated (60 DSP/voice resources) and the show vfc # version vcware command, which shows that the Cisco VCWare is Version 6.08, and the Cisco DSPWare is Version 3.3.13.
E1_UUT2# show version Cisco Internetwork Operating System Software IOS (tm) 5300 Software (C5300-IS-M), Version 12.1(2a)T1, RELEASE SOFTWARE (fc2) Copyright (c) 1986-1999 by cisco Systems, Inc. Compiled Wed 08-Dec-99 20:25 by phanguye Image text-base:0x600088F8, data-base:0x60C6A000 ROM:System Bootstrap, Version 11.2(9)XA, RELEASE SOFTWARE (fc2) BOOTFLASH:5300 Software (C5300-BOOT-M), Version 12.1(2a)T1, RELEASE SOFTWARE (fc1) sblab162 uptime is 0 minutes System restarted by reload System image file is "tftp://172.29.248.12/wwatson/c5300-is-mz.120-7.XR2" cisco AS5300 (R4K) processor (revision A.22) with 65536K/16384K bytes of memory. Processor board ID 06469180 R4700 CPU at 150Mhz, Implementation 33, Rev 1.0, 512KB L2 Cache Bridging software. X.25 software, Version 3.0.0. Primary Rate ISDN software, Version 1.1. Backplane revision 2 Manufacture Cookie Info: EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x30, Board Hardware Version 1.0, Item Number 73-2414-3, Board Revision A0, Serial Number 06469180, PLD/ISP Version 255.255, Manufacture Date 11-Nov-1997. 1 Ethernet/IEEE 802.3 interface(s) 1 FastEthernet/IEEE 802.3 interface(s) 72 Serial network interface(s) 4 Channelized T1/PRI port(s) 60 Voice resource(s) 128K bytes of non-volatile configuration memory. 16384K bytes of processor board System flash (Read/Write) 8192K bytes of processor board Boot flash (Read/Write) Configuration register is 0x2102 E1_UUT# sh vfc 1 version vcware Voice Feature Card in Slot 1: VCware Version :6.08 ROM Monitor Version:1.3 DSPware Version :3.3.13 Technology :C549 E1_UUT# sh vfc 2 version vcware Voice Feature Card in Slot 2: VCware Version :6.08 ROM Monitor Version:1.3 DSPware Version :3.3.13 Technology :C549
For the latest information on known problems, follow these steps to create a bug Watcher Bin in the Software Bug Toolkit from Obtaining Documentation (CCO):
Step 2 On the CCO home page, click LOGIN (which appears in green in the menu bar at the top of the page) and log in to CCO. If you are not a registered CCO user, follow the instructions to register so that you can log in. Login is complete when the word LOGIN no longer appears in green text in the menu bar.
Step 3 After you log in, click Software & Support on the CCO home page.
Step 4 Under the Technical Support menu, click Software Bug Toolkit II. (Software Bug Toolkit II is not visible on the Software & Support page unless you are logged into CCO as directed in Step 2.)
Step 5 Click Search for Bug by ID Number from the main menu or click Search by ID under Bug Toolkit in the left column of the screen.
Step 6 Enter a bug ID, such as CSCdj80580, in the Search for Bug by ID Number window and click SEARCH. The bug information is displayed.
Step 7 To watch activity on the selected bug, click the WATCH this bug button at the top of the screen. The Pick a Watcher Bin entry screen is displayed.
Step 8 Create a Watcher Bin for the bug selected by entering a New Bin Watcher name, such as V.90 Bugs. A new Watcher Bin is created. The new Watcher Bin creates a link to the Bug Watcher screen.
Step 9 Click Watcher to access the Bug Watcher screen. The new Watcher Bin link is displayed in the left column of the screen.
For instructions on using other bug tools, go to the bottom of the Toolkit II page and click Help--How to Use the Bug Toolkit or click Help under Common Tools in the left column of the screen.
For more information, refer to the following documents and indexes:
You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.
Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).
Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.
Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.
You can access CCO in the following ways:
You can e-mail questions about using CCO to cco-team@cisco.com.
The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.
To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.
To contact by e-mail, use one of the following:
Language | E-mail Address |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate and value your comments.
Posted: Wed Aug 2 15:12:29 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.