Cisco VCO/4K Open Programmable Switches

Table Of Contents

Product Bulletin No. 1405

Frequently Asked Questions

Generic Software:

SS7 Software:

Product Bulletin No. 1405

---

Clarifications to the Five Previously-published VCO/Summa4 System
End-of-Life Announcements

This product bulletin has been issued to clarify certain End-of-Life milestone dates and to clarify the End-of-Life milestone date definitions contained in the five previously published VCO/Summa4 System End-of-Life Announcements.

The dates and definitions documented in this bulletin take precedence over the corresponding dates and definitions listed in the previous announcements. Please note: The actual milestone dates already documented in the previous bulletins, which are not listed in this bulletin (i.e. the End-of-Life Announcement dates, the End-of-Sales/End-of-Orderability dates, and the End-of-Product-Shipment dates), remain in-effect as documented in the previous bulletins.

Where at all possible, certain key milestone dates have been extended when compared to previously published milestone dates. For example, the Product Obsolete Date for the VCO80-NEBS and VCO80-NEBS-4K chassis categories has been extended from 2/1/2002 to 7/7/2003. See Table 2.

Please refer to Tables 1, 2, 3, and 4, and to the FAQ contained in this bulletin for complete details. If you have further questions, then please contact your Cisco Account Executive.

Table 1  Summary of Key End-of-Life Mile Stones by Previous Product Bulletin

Previous Product Bulletin1	End of Engineering Hardware Maintenance Support Date	End of Service Contract Renewal Date	End of RMA & TAC Support (Product Obsolete Date)
PB873-V332	Not Documented	Not Documented	5/30/2003 "Last Support Date" = "Product Obsolete Date"
PB873-Analog- Network-Card2	Not Documented	Not Documented	5/30/2004 "Last Support Date" = "Product Obsolete Date"
PB873-V422	Not Documented	Not Documented	3/30/2004 "Last Support Date" = "Product Obsolete Date"
PB10262	Not Documented	Not Documented	2/1/2002 "End of HW Maintenance" = "Product Obsolete Date"
PB10312	Not Documented	Not Documented	7/7/2003 "Last Support Date" = "Product Obsolete Date"

1 The previous product bulletins failed to link all possible chassis categories to the "product obsolete date". This was the source of much confusion. See Table 2 for further clarification. 2 The previous Product Bulletins, are located at the following URLs: 2 http://www.cisco.com/en/US/products/hw/switches/ps2246/prod_eol_notice09186a008032d608.html 2 http://www.cisco.com/en/US/products/hw/switches/ps2246/prod_eol_notice09186a008032d489.html 2 http://www.cisco.com/en/US/products/hw/switches/ps2246/prod_eol_notice09186a008032d48a.html 2 http://www.cisco.com/en/US/products/hw/switches/ps2246/prod_eol_notices_list.html

Table 2  Summary of Revised Key End-of-Life Milestones by Chassis Category (Table 2 takes precedence Over Table 1)

Chassis Category	End of Engineering Hardware Maintenance Support Date	End of Service Contract Renewal Date	End of RMA & TAC Support (Product Obsolete Date)
VCO4K-NEBS1	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 2 years).	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 4 years).	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 5 years).
VCO4K1	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 2 years).	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 4 years).	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 5 years).
VCO20-4K1, 2	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 2 years).	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 4 years).	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 5 years).
VCO20	Not to exceed 3/30/20023	3/30/2003	3/30/2004
VCO80-NEBS-4K	Not to exceed 7/7/20013	7/7/2002	7/7/2003
VCO80-NEBS	Not to exceed 7/7/20013	7/7/2002	7/7/2003
SDS1000	Not to exceed 8/1/20003	2/1/2001	2/1/2002

1 This chassis category has not entered into the EOL process at the time that this clarifying Product Bulletin was published. 2 Retrofitting a VCO20 to make it "VCO4K compliant" requires the purchase of a certain set of hardware and requires Cisco on-site service to perform the retrofit and testing. This retrofit also requires that the system serial number be transferred from a VCO20 service contract to a VCO4K service contract. Cisco on-site service is invoiced on a time and material basis. 3 The dates shown (in Table 4) vary per operating system (Generic, SS7) installed on the system, but will not exceed the maximum date shown (here in Table 2) for the given chassis category.

Table 3  Milestone Date Definitions

The dates and definitions documented in this bulletin take precedence over the corresponding dates and definitions listed in the previous announcements. Please note: The actual milestone dates already documented in the previous bulletins, which are not listed in this bulletin (i.e. the End-of-Life Announcement dates, the End-of-Sales/End-of-Orderability dates, and the End-of-Product-Shipment dates), remain in-effect as so-documented in the previous bulletins.

Date	Definition
End of Life Announcement Date:	The date that the "End of Life Announcement" was released to the public. For the actual "End of Life Announcement dates," please refer to the previously published VCO/Summa4 EOL Product Bulletins referenced in Table 1.
End of Sales/Orderability Date:	The date that CCO NetworkMarket Place Tool "Orderability" was de-activated. For the actual "End of Sales/Orderability dates," please refer to the previously published VCO/Summa4 EOL Product Bulletins referenced in Table 1.
End of Production/ Shipment Date:	The date that Manufacturing finished honoring/fulfilling purchase orders for new equipment. For the actual "End of Production/Shipment dates," please refer to the previously published VCO/Summa4 EOL Product Bulletins referenced in Table 1
End of Engineering Hardware Maintenance Support Date:	The date that Engineering ceased/will cease honoring to consider repairing confirmed hardware defects related to components within this system configuration. Note: "Hardware" means the physical card and its physical components. Note: A card's software download file, if any, is classified as "software". A card's firmware is classified as "hardware". For the actual "End of Engineering Hardware Maintenance Support dates," please refer to Table 4 of this Product Bulletin.
End of Engineering Software Maintenance Support Date:	The date that Engineering ceased/will cease honoring to consider repairing confirmed Operating System software defects and/or card download software defects within this system configuration. Note: There are 6 Operating Systems (OSs): Generic_OS, SS7_CKTINT-ANSI_OS (ISUP ANSI), SS7_CKTINT -ITU_OS (ISUP ITU), SS7_SEPT-ANSI_OS (TCAP ANSI), SS7_SEPT-ITU_OS (TCAP ITU), and SS7_CHINA-TUP (CHINA TUP). Note: All cards which use software download files are cards, which only operate against the Generic_OS. For the actual "End of Engineering Software Maintenance Support dates", please refer to Table 4 of this Product Bulletin.
End of Service Contract Renewal Date:	The last date in which a partner/customer can extend/renew a service contract for this system. Note: There are 7 chassis categories: SDS1000, VCO80-NEBS, VCO80-NEBS-4K, VCO20, VCO20-4K, VCO4K, and VCO4K-NEBS. For the actual "End of Service Contract Renewal dates", please refer to Table 4 of this Product Bulletin.
Product Obsolete Date:	The date that Cisco Logistics (in conjunction with Manufacturing) ceased/will cease honoring their commitment to process Return Material Authorization orders (RMA orders) for components within this system configuration. It is also the date that TAC ceased/will cease honoring their commitment to assist customers with any issues related to components within this system configuration (such as identifying the root cause of the reported issue, suggesting workarounds, etc.). For the actual "Product Obsolete dates", please refer to Table 4 of this Product Bulletin.

Table 4  Key End of Life Mile Stones by Chassis Category in Details

System Configuration					Milestone Dates
					Product Obsolete Date	End of Service Contract Renewal Date	End of Engineering Software Maintenance Support Date for the VCO- subsystem	End of Engineering Hardware Maintenance Support Date for the VCO- subsystem	End of Engineering Software Maintenance Support Date for the SS7- subsystem	End of Engineering Hardware Maintenance Support Date for the SS7- subsystem
Chassis Category	CBUS Physically Installed?	CBUS Enabled?	Version of "Generic" software present	Version of "SS7" software present	What is the date that TAC support and RMA support for this system configuration expired/will expire?	What is the last date to renew a service contract for this system configuration?	What is the date that VCO- subsystem Software Engineering Maintenance support for this system configuration expired/will expire?	What is the date that VCO- subsystem Hardware Engineering Maintenance support for this system configuration expired/will expire?	What is the date that SS7- subsystem Software Engineering Maintenance support for this system configuration expired/will expire?	What is the date that SS7- subsystem Hardware Engineering Maintenance support for this system configuration expired/will expire?	Notes:
SDS1000	No	N/A	V3.3	None	2/1/02	2/1/01	5/30/98	5/30/97	N/A	N/A
SDS1000	No	N/A	V4.0	None	2/1/02	2/1/01	6/30/99	6/30/98	N/A	N/A
SDS1000	No	N/A	V4.1	None	2/1/02	2/1/01	6/30/99	6/30/98	N/A	N/A
SDS1000	No	N/A	V4.2	None	2/1/02	2/1/01	6/30/99	6/30/98	N/A	N/A
SDS1000	No	N/A	V5.0	None	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
SDS1000	No	N/A	V5.1	None	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
SDS1000	No	N/A	V5.2	None	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
SDS1000	No	N/A	Any Version	V3.0 ANSI ISUP	2/1/02	2/1/01	Generic dependent. See above.	Generic dependent. See above.	6/30/00	6/30/99
SDS1000	No	N/A	Any Version	V5.0 ANSI ISUP	2/1/02	2/1/01	Generic dependent. See above.	Generic dependent. See above.	8/1/01	8/1/00
SDS1000	No	N/A	Any Version	V5.2 ANSI ISUP	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
SDS1000	No	N/A	Any Version	V3.0 ITU ISUP	2/1/02	2/1/01	Generic dependent. See above.	Generic dependent. See above.	6/30/00	6/30/99
SDS1000	No	N/A	Any Version	V5.0 ITU ISUP	2/1/02	2/1/01	Generic dependent. See above.	Generic dependent. See above.	8/1/01	8/1/00
SDS1000	No	N/A	Any Version	V5.1 ITU ISUP	2/1/02	2/1/01	Generic dependent. See above.	Generic dependent. See above.	8/1/01	8/1/00
SDS1000	No	N/A	Any Version	V5.2 ITU ISUP	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
SDS1000	No	N/A	Any Version	V3.0 ANSI TCAP	2/1/02	2/1/01	Generic dependent. See above.	Generic dependent. See above.	8/1/01	8/1/00
SDS1000	No	N/A	Any Version	V3.0 ITU TCAP	2/1/02	2/1/01	Generic dependent. See above.	Generic dependent. See above.	6/30/00	6/30/99
SDS1000	No	N/A	Any Version	V5.1 ITU TCAP	2/1/02	2/1/01	Generic dependent. See above.	Generic dependent. See above.	8/1/01	8/1/00
SDS1000	No	N/A	Any Version	CHINA TUP V5.1	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO80-NEBS	No	N/A	V3.3	None	7/7/03	7/7/02	5/30/98	5/30/97	N/A	N/A
VCO80-NEBS	No	N/A	V4.0	None	7/7/03	7/7/02	6/30/99	6/30/98	N/A	N/A
VCO80-NEBS	No	N/A	V4.1	None	7/7/03	7/7/02	6/30/99	6/30/98	N/A	N/A
VCO80-NEBS	No	N/A	V4.2	None	7/7/03	7/7/02	6/30/99	6/30/98	N/A	N/A
VCO80-NEBS	No	N/A	V5.0	None	7/7/03	7/7/02	4/20/01	4/20/00	N/A	N/A
VCO80-NEBS	No	N/A	V5.1	None	7/7/03	7/7/02	4/20/02	4/20/01	N/A	N/A
VCO80-NEBS	No	N/A	V5.2	None	7/7/03	7/7/02	7/7/02	7/7/01	N/A	N/A
VCO80-NEBS	No	N/A	Any Version	V3.0 ANSI ISUP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	6/30/00	6/30/99
VCO80-NEBS	No	N/A	Any Version	V5.0 ANSI ISUP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	1/1/02	1/1/01
VCO80-NEBS	No	N/A	Any Version	V5.2 ANSI ISUP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	7/7/02	7/7/01
VCO80-NEBS	No	N/A	Any Version	V3.0 ITU ISUP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	6/30/00	6/30/99
VCO80-NEBS	No	N/A	Any Version	V5.0 ITU ISUP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	8/1/01	8/1/00
VCO80-NEBS	No	N/A	Any Version	V5.1 ITU ISUP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	1/1/02	1/1/01
VCO80-NEBS	No	N/A	Any Version	V5.2 ITU ISUP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	7/7/02	7/7/01
VCO80-NEBS	No	N/A	Any Version	V3.0 ANSI TCAP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	7/7/02	7/7/01
VCO80-NEBS	No	N/A	Any Version	V3.0 ITU TCAP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	6/30/00	6/30/99
VCO80-NEBS	No	N/A	Any Version	V5.1 ITU TCAP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	7/7/02	7/7/01
VCO80-NEBS	No	N/A	Any Version	CHINA TUP V5.1	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	7/7/02	7/7/01
VCO80-NEBS-4K	Yes	No	V3.3	None	7/7/03	7/7/02	5/30/98	5/30/97	N/A	N/A
VCO80-NEBS-4K	Yes	No	V4.0	None	7/7/03	7/7/02	6/30/99	6/30/98	N/A	N/A
VCO80-NEBS-4K	Yes	No	V4.1	None	7/7/03	7/7/02	6/30/99	6/30/98	N/A	N/A
VCO80-NEBS-4K	Yes	No	V4.2	None	7/7/03	7/7/02	6/30/99	6/30/98	N/A	N/A
VCO80-NEBS-4K	Yes	No	V5.0	None	7/7/03	7/7/02	4/20/01	4/20/00	N/A	N/A
VCO80-NEBS-4K	Yes	No	V5.1	None	7/7/03	7/7/02	4/20/02	4/20/01	N/A	N/A
VCO80-NEBS-4K	Yes	No	V5.2	None	7/7/03	7/7/02	7/7/02	7/7/01	N/A	N/A
VCO80-NEBS-4K	Yes	No	Any Version	V3.0 ANSI ISUP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	6/30/00	6/30/99
VCO80-NEBS-4K	Yes	No	Any Version	V5.0 ANSI ISUP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	1/1/02	1/1/01
VCO80-NEBS-4K	Yes	No	Any Version	V5.2 ANSI ISUP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	7/7/02	7/7/01
VCO80-NEBS-4K	Yes	No	Any Version	V3.0 ITU ISUP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	6/30/00	6/30/99
VCO80-NEBS-4K	Yes	No	Any Version	V5.0 ITU ISUP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	8/1/01	8/1/00
VCO80-NEBS-4K	Yes	No	Any Version	V5.1 ITU ISUP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	1/1/02	1/1/01
VCO80-NEBS-4K	Yes	No	Any Version	V5.2 ITU ISUP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	7/7/02	7/7/01
VCO80-NEBS-4K	Yes	No	Any Version	V3.0 ANSI TCAP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	7/7/02	7/7/01
VCO80-NEBS-4K	Yes	No	Any Version	V3.0 ITU TCAP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	6/30/00	6/30/99
VCO80-NEBS-4K	Yes	No	Any Version	V5.1 ITU TCAP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	7/7/02	7/7/01
VCO80-NEBS-4K	Yes	No	Any Version	CHINA TUP V5.1	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	7/7/02	7/7/01
VCO80-NEBS-4K	Yes	Yes	V3.3	None	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO80-NEBS-4K	Yes	Yes	V4.0	None	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO80-NEBS-4K	Yes	Yes	V4.1	None	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO80-NEBS-4K	Yes	Yes	V4.2	None	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO80-NEBS-4K	Yes	Yes	V5.0	None	7/7/03	7/7/02	4/20/01	4/20/00	N/A	N/A
VCO80-NEBS-4K	Yes	Yes	V5.1	None	7/7/03	7/7/02	4/20/02	4/20/01	N/A	N/A
VCO80-NEBS-4K	Yes	Yes	V5.2	None	7/7/03	7/7/02	7/7/02	7/7/01	N/A	N/A
VCO80-NEBS-4K	Yes	Yes	Any Version	V3.0 ANSI ISUP	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO80-NEBS-4K	Yes	Yes	Any Version	V5.0 ANSI ISUP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	1/1/02	1/1/01
VCO80-NEBS-4K	Yes	Yes	Any Version	V5.2 ANSI ISUP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	7/7/02	7/7/01
VCO80-NEBS-4K	Yes	Yes	Any Version	V3.0 ITU ISUP	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO80-NEBS-4K	Yes	Yes	Any Version	V5.0 ITU ISUP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	8/1/01	8/1/00
VCO80-NEBS-4K	Yes	Yes	Any Version	V5.1 ITU ISUP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	1/1/02	1/1/01
VCO80-NEBS-4K	Yes	Yes	Any Version	V5.2 ITU ISUP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	7/7/02	7/7/01
VCO80-NEBS-4K	Yes	Yes	Any Version	V3.0 ANSI TCAP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	7/7/02	7/7/01
VCO80-NEBS-4K	Yes	No	Any Version	V3.0 ITU TCAP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	6/30/00	6/30/99
VCO80-NEBS-4K	Yes	Yes	Any Version	V5.1 ITU TCAP	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	7/7/02	7/7/01
VCO80-NEBS-4K	Yes	Yes	Any Version	CHINA TUP V5.1	7/7/03	7/7/02	Generic dependent. See above.	Generic dependent. See above.	7/7/02	7/7/01
VCO20	No	N/A	V3.3	None	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20	No	N/A	V4.0	None	3/30/04	3/30/03	6/30/99	6/30/98	N/A	N/A
VCO20	No	N/A	V4.1	None	3/30/04	3/30/03	6/30/99	6/30/98	N/A	N/A
VCO20	No	N/A	V4.2	None	3/30/04	3/30/03	6/30/99	6/30/98	N/A	N/A
VCO20	No	N/A	V5.0	None	3/30/04	3/30/03	4/20/01	4/20/00	N/A	N/A
VCO20	No	N/A	V5.1	None	3/30/04	3/30/03	4/20/02	4/20/01	N/A	N/A
VCO20	No	N/A	V5.2	None	3/30/04	3/30/03	3/30/03	3/30/02	N/A	N/A
VCO20	No	N/A	Any Version	V3.0 ANSI ISUP	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	6/30/00	6/30/99
VCO20	No	N/A	Any Version	V5.0 ANSI ISUP	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	11/1/02	11/1/01
VCO20	No	N/A	Any Version	V5.2 ANSI ISUP	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	3/30/03	3/30/02
VCO20	No	N/A	Any Version	V3.0 ITU ISUP	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	6/30/00	6/30/00
VCO20	No	N/A	Any Version	V5.0 ITU ISUP	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	8/1/01	8/1/00
VCO20	No	N/A	Any Version	V5.1 ITU ISUP	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	11/1/02	11/1/01
VCO20	No	N/A	Any Version	V5.2 ITU ISUP	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	3/30/03	3/30/02
VCO20	No	N/A	Any Version	V3.0 ANSI TCAP	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	3/30/03	3/30/02
VCO20	No	N/A	Any Version	V3.0 ITU TCAP	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	6/30/00	6/30/99
VCO20	No	N/A	Any Version	V5.1 ITU TCAP	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	3/30/03	3/30/02
VCO20	No	N/A	Any Version	CHINA TUP V5.1	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	3/30/03	3/30/02
VCO20-4K	Yes	No	V3.3	None	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20-4K	Yes	No	V4.0	None	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20-4K	Yes	No	V4.1	None	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20-4K	Yes	No	V4.2	None	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20-4K	Yes	No	V5.0	None	3/30/04	3/30/03	4/20/01	4/20/00	N/A	N/A	If you believe that your system is already a "VCO4K compliant" VCO20 system, then your system may be eligible to be extended to the VCO/4K dates, shown in the next section (below). This is subject to verification by an on-site Cisco audit which is invoiced on a time and material basis. May also involve customer purchasing a certain set of hardware.
VCO20-4K	Yes	No	V5.1	None	3/30/04	3/30/03	4/20/02	4/20/01	N/A	N/A	If you believe that your system is already a "VCO4K compliant" VCO20 system, then your system may be eligible to be extended to the VCO/4K dates, shown in the next section (below). This is subject to verification by an on-site Cisco audit which is invoiced on a time and material basis. May also involve customer purchasing a certain set of hardware.
VCO20-4K	Yes	No	V5.2	None	3/30/04	3/30/03	3/30/03	3/30/02	N/A	N/A	If you believe that your system is already a "VCO4K compliant" VCO20 system, then your system may be eligible to be extended to the VCO/4K dates, shown in the next section (below). This is subject to verification by an on-site Cisco audit which is invoiced on a time and material basis. May also involve customer purchasing a certain set of hardware.
VCO20-4K	Yes	No	Any Version	V3.0 ANSI ISUP	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20-4K	Yes	No	Any Version	V5.0 ANSI ISUP	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	11/1/02	11/1/01	If you believe that your system is already a "VCO4K compliant" VCO20 system, then your system may be eligible to be extended to the VCO/4K dates, shown in the next section (below). This is subject to verification by an on-site Cisco audit which is invoiced on a time and material basis. May also involve customer purchasing a certain set of hardware.
VCO20-4K	Yes	No	Any Version	V5.2 ANSI ISUP	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	3/30/03	3/30/02	If you believe that your system is already a "VCO4K compliant" VCO20 system, then your system may be eligible to be extended to the VCO/4K dates, shown in the next section (below). This is subject to verification by an on-site Cisco audit which is invoiced on a time and material basis. May also involve customer purchasing a certain set of hardware.
VCO20-4K	Yes	No	Any Version	V3.0 ITU ISUP	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20-4K	Yes	No	Any Version	V5.0 ITU ISUP	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	8/1/01	8/1/00	If you believe that your system is already a "VCO4K compliant" VCO20 system, then your system may be eligible to be extended to the VCO/4K dates, shown in the next section (below). This is subject to verification by an on-site Cisco audit which is invoiced on a time and material basis. May also involve customer purchasing a certain set of hardware.
VCO20-4K	Yes	No	Any Version	V5.1 ITU ISUP	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	11/1/02	11/1/01	If you believe that your system is already a "VCO4K compliant" VCO20 system, then your system may be eligible to be extended to the VCO/4K dates, shown in the next section (below). This is subject to verification by an on-site Cisco audit which is invoiced on a time and material basis. May also involve customer purchasing a certain set of hardware.
VCO20-4K	Yes	No	Any Version	V5.2 ITU ISUP	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	3/30/03	3/30/02	If you believe that your system is already a "VCO4K compliant" VCO20 system, then your system may be eligible to be extended to the VCO/4K dates, shown in the next section (below). This is subject to verification by an on-site Cisco audit which is invoiced on a time and material basis. May also involve customer purchasing a certain set of hardware.
VCO20-4K	Yes	No	Any Version	V3.0 ANSI TCAP	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	3/30/03	3/30/02	If you believe that your system is already a "VCO4K compliant" VCO20 system, then your system may be eligible to be extended to the VCO/4K dates, shown in the next section (below). This is subject to verification by an on-site Cisco audit which is invoiced on a time and material basis. May also involve customer purchasing a certain set of hardware.
VCO20-4K	Yes	No	Any Version	V3.0 ITU TCAP	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	6/30/00	6/30/99	If you believe that your system is already a "VCO4K compliant" VCO20 system, then your system may be eligible to be extended to the VCO/4K dates, shown in the next section (below). This is subject to verification by an on-site Cisco audit which is invoiced on a time and material basis. May also involve customer purchasing a certain set of hardware.
VCO20-4K	Yes	No	Any Version	V5.1 ITU TCAP	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	3/30/03	3/30/02	If you believe that your system is already a "VCO4K compliant" VCO20 system, then your system may be eligible to be extended to the VCO/4K dates, shown in the next section (below). This is subject to verification by an on-site Cisco audit which is invoiced on a time and material basis. May also involve customer purchasing a certain set of hardware.
VCO20-4K	Yes	No	Any Version	CHINA TUP V5.1	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	3/30/03	3/30/02	If you believe that your system is already a "VCO4K compliant" VCO20 system, then your system may be eligible to be extended to the VCO/4K dates, shown in the next section (below). This is subject to verification by an on-site Cisco audit which is invoiced on a time and material basis. May also involve customer purchasing a certain set of hardware.
VCO20-4K	Yes	Yes	V3.3	None	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20-4K	Yes	Yes	V4.0	None	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20-4K	Yes	Yes	V4.1	None	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20-4K	Yes	Yes	V4.2	None	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20-4K	Yes	Yes	V5.0	None	3/30/04	3/30/03	4/20/01	4/20/00	N/A	N/A	If you believe that your system is already a "VCO4K compliant" VCO20 system, then your system may be eligible to be extended to the VCO/4K dates, shown in the next section (below). This is subject to verification by an on-site Cisco audit which is invoiced on a time and material basis. May also involve customer purchasing a certain set of hardware.
VCO20-4K	Yes	Yes	V5.1	None	3/30/04	3/30/03	4/20/02	4/20/01	N/A	N/A	If you believe that your system is already a "VCO4K compliant" VCO20 system, then your system may be eligible to be extended to the VCO/4K dates, shown in the next section (below). This is subject to verification by an on-site Cisco audit which is invoiced on a time and material basis. May also involve customer purchasing a certain set of hardware.
VCO20-4K	Yes	Yes	V5.2	None	3/30/04	3/30/03	3/30/03	3/30/02	N/A	N/A	If you believe that your system is already a "VCO4K compliant" VCO20 system, then your system may be eligible to be extended to the VCO/4K dates, shown in the next section (below). This is subject to verification by an on-site Cisco audit which is invoiced on a time and material basis. May also involve customer purchasing a certain set of hardware.
VCO20-4K	Yes	Yes	Any Version	V3.0 ANSI ISUP	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20-4K	Yes	Yes	Any Version	V5.0 ANSI ISUP	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	11/1/02	11/1/01	If you believe that your system is already a "VCO4K compliant" VCO20 system, then your system may be eligible to be extended to the VCO/4K dates, shown in the next section (below). This is subject to verification by an on-site Cisco audit which is invoiced on a time and material basis. May also involve customer purchasing a certain set of hardware.
VCO20-4K	Yes	Yes	Any Version	V5.2 ANSI ISUP	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	3/30/03	3/30/02	If you believe that your system is already a "VCO4K compliant" VCO20 system, then your system may be eligible to be extended to the VCO/4K dates, shown in the next section (below). This is subject to verification by an on-site Cisco audit which is invoiced on a time and material basis. May also involve customer purchasing a certain set of hardware.
VCO20-4K	Yes	Yes	Any Version	V3.0 ITU ISUP	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20-4K	Yes	Yes	Any Version	V5.0 ITU ISUP	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	8/1/01	8/1/00	If you believe that your system is already a "VCO4K compliant" VCO20 system, then your system may be eligible to be extended to the VCO/4K dates, shown in the next section (below). This is subject to verification by an on-site Cisco audit which is invoiced on a time and material basis. May also involve customer purchasing a certain set of hardware.
VCO20-4K	Yes	Yes	Any Version	V5.1 ITU ISUP	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	11/1/02	11/1/01	If you believe that your system is already a "VCO4K compliant" VCO20 system, then your system may be eligible to be extended to the VCO/4K dates, shown in the next section (below). This is subject to verification by an on-site Cisco audit which is invoiced on a time and material basis. May also involve customer purchasing a certain set of hardware.
VCO20-4K	Yes	Yes	Any Version	V5.2 ITU ISUP	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	3/30/03	3/30/02	If you believe that your system is already a "VCO4K compliant" VCO20 system, then your system may be eligible to be extended to the VCO/4K dates, shown in the next section (below). This is subject to verification by an on-site Cisco audit which is invoiced on a time and material basis. May also involve customer purchasing a certain set of hardware.
VCO20-4K	Yes	Yes	Any Version	V3.0 ANSI TCAP	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	3/30/03	3/30/02	If you believe that your system is already a "VCO4K compliant" VCO20 system, then your system may be eligible to be extended to the VCO/4K dates, shown in the next section (below). This is subject to verification by an on-site Cisco audit which is invoiced on a time and material basis. May also involve customer purchasing a certain set of hardware.
VCO20-4K	Yes	Yes	Any Version	V3.0 ITU TCAP	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	6/30/00	6/30/99	If you believe that your system is already a "VCO4K compliant" VCO20 system, then your system may be eligible to be extended to the VCO/4K dates, shown in the next section (below). This is subject to verification by an on-site Cisco audit which is invoiced on a time and material basis. May also involve customer purchasing a certain set of hardware.
VCO20-4K	Yes	Yes	Any Version	V5.1 ITU TCAP	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	3/30/03	3/30/02	If you believe that your system is already a "VCO4K compliant" VCO20 system, then your system may be eligible to be extended to the VCO/4K dates, shown in the next section (below). This is subject to verification by an on-site Cisco audit which is invoiced on a time and material basis. May also involve customer purchasing a certain set of hardware.
VCO20-4K	Yes	Yes	Any Version	CHINA TUP V5.1	3/30/04	3/30/03	Generic dependent. See above.	Generic dependent. See above.	3/30/03	3/30/02	If you believe that your system is already a "VCO4K compliant" VCO20 system, then your system may be eligible to be extended to the VCO/4K dates, shown in the next section (below). This is subject to verification by an on-site Cisco audit which is invoiced on a time and material basis. May also involve customer purchasing a certain set of hardware.
VCO20-4K*	Yes	No	V3.3	None	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20-4K*	Yes	No	V4.0	None	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20-4K*	Yes	No	V4.1	None	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20-4K*	Yes	No	V4.2	None	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20-4K*	Yes	No	V5.0	None	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 4 years)	4/20/01	4/20/00	N/A	N/A	Retrofitting a VCO20 to make it "VCO4K compliant" requires the purchase of a certain set of hardware and requires Cisco to perform the retrofit and testing. This retrofit also requires that the system serial number be transferred from a VCO20 service contract to a VCO4K service contract. Cisco on-site services invoiced on a time and material basis.
VCO20-4K*	Yes	No	V5.1	None	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 4 years)	4/20/02	4/20/01	N/A	N/A	Retrofitting a VCO20 to make it "VCO4K compliant" requires the purchase of a certain set of hardware and requires Cisco to perform the retrofit and testing. This retrofit also requires that the system serial number be transferred from a VCO20 service contract to a VCO4K service contract. Cisco on-site services invoiced on a time and material basis.
VCO20-4K*	Yes	No	V5.2	None	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 4 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 2 years)	N/A	N/A	Retrofitting a VCO20 to make it "VCO4K compliant" requires the purchase of a certain set of hardware and requires Cisco to perform the retrofit and testing. This retrofit also requires that the system serial number be transferred from a VCO20 service contract to a VCO4K service contract. Cisco on-site services invoiced on a time and material basis.
VCO20-4K*	Yes	No	Any Version	V3.0 ANSI ISUP	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20-4K*	Yes	No	Any Version	V5.0 ANSI ISUP	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	11/1/02	11/1/01	Retrofitting a VCO20 to make it "VCO4K compliant" requires the purchase of a certain set of hardware and requires Cisco to perform the retrofit and testing. This retrofit also requires that the system serial number be transferred from a VCO20 service contract to a VCO4K service contract. Cisco on-site services invoiced on a time and material basis.
VCO20-4K*	Yes	No	Any Version	V5.2 ANSI ISUP	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 2 years)	Retrofitting a VCO20 to make it "VCO4K compliant" requires the purchase of a certain set of hardware and requires Cisco to perform the retrofit and testing. This retrofit also requires that the system serial number be transferred from a VCO20 service contract to a VCO4K service contract. Cisco on-site services invoiced on a time and material basis.
VCO20-4K*	Yes	No	Any Version	V3.0 ITU ISUP	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20-4K*	Yes	No	Any Version	V5.0 ITU ISUP	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	8/1/01	8/1/00	Retrofitting a VCO20 to make it "VCO4K compliant" requires the purchase of a certain set of hardware and requires Cisco to perform the retrofit and testing. This retrofit also requires that the system serial number be transferred from a VCO20 service contract to a VCO4K service contract. Cisco on-site services invoiced on a time and material basis.
VCO20-4K*	Yes	No	Any Version	V5.1 ITU ISUP	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	11/1/02	11/1/01	Retrofitting a VCO20 to make it "VCO4K compliant" requires the purchase of a certain set of hardware and requires Cisco to perform the retrofit and testing. This retrofit also requires that the system serial number be transferred from a VCO20 service contract to a VCO4K service contract. Cisco on-site services invoiced on a time and material basis.
VCO20-4K*	Yes	No	Any Version	V5.2 ITU ISUP	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 2 years)	Retrofitting a VCO20 to make it "VCO4K compliant" requires the purchase of a certain set of hardware and requires Cisco to perform the retrofit and testing. This retrofit also requires that the system serial number be transferred from a VCO20 service contract to a VCO4K service contract. Cisco on-site services invoiced on a time and material basis.
VCO20-4K*	Yes	No	Any Version	V3.0 ANSI TCAP	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 2 years)	Retrofitting a VCO20 to make it "VCO4K compliant" requires the purchase of a certain set of hardware and requires Cisco to perform the retrofit and testing. This retrofit also requires that the system serial number be transferred from a VCO20 service contract to a VCO4K service contract. Cisco on-site services invoiced on a time and material basis.
VCO20-4K*	Yes	No	Any Version	V3.0 ITU TCAP	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20-4K*	Yes	No	Any Version	V5.1 ITU TCAP	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 2 years)	Retrofitting a VCO20 to make it "VCO4K compliant" requires the purchase of a certain set of hardware and requires Cisco to perform the retrofit and testing. This retrofit also requires that the system serial number be transferred from a VCO20 service contract to a VCO4K service contract. Cisco on-site services invoiced on a time and material basis.
VCO20-4K*	Yes	No	Any Version	CHINA TUP V5.1	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 2 years)	Retrofitting a VCO20 to make it "VCO4K compliant" requires the purchase of a certain set of hardware and requires Cisco to perform the retrofit and testing. This retrofit also requires that the system serial number be transferred from a VCO20 service contract to a VCO4K service contract. Cisco on-site services invoiced on a time and material basis.
VCO20-4K*	Yes	Yes	V3.3	None	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20-4K*	Yes	Yes	V4.0	None	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20-4K*	Yes	Yes	V4.1	None	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20-4K*	Yes	Yes	V4.2	None	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20-4K*	Yes	Yes	V5.0	None	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 4 years)	4/20/01	4/20/00	N/A	N/A	Retrofitting a VCO20 to make it "VCO4K compliant" requires the purchase of a certain set of hardware and requires Cisco to perform the retrofit and testing. This retrofit also requires that the system serial number be transferred from a VCO20 service contract to a VCO4K service contract. Cisco on-site services invoiced on a time and material basis.
VCO20-4K*	Yes	Yes	V5.1	None	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 4 years)	4/20/02	4/20/01	N/A	N/A	Retrofitting a VCO20 to make it "VCO4K compliant" requires the purchase of a certain set of hardware and requires Cisco to perform the retrofit and testing. This retrofit also requires that the system serial number be transferred from a VCO20 service contract to a VCO4K service contract. Cisco on-site services invoiced on a time and material basis.
VCO20-4K*	Yes	Yes	V5.2	None	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 4 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 2 years)	N/A	N/A	Retrofitting a VCO20 to make it "VCO4K compliant" requires the purchase of a certain set of hardware and requires Cisco to perform the retrofit and testing. This retrofit also requires that the system serial number be transferred from a VCO20 service contract to a VCO4K service contract. Cisco on-site services invoiced on a time and material basis.
VCO20-4K*	Yes	Yes	Any Version	V3.0 ANSI ISUP	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20-4K*	Yes	Yes	Any Version	V5.0 ANSI ISUP	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	11/1/02	11/1/01	Retrofitting a VCO20 to make it "VCO4K compliant" requires the purchase of a certain set of hardware and requires Cisco to perform the retrofit and testing. This retrofit also requires that the system serial number be transferred from a VCO20 service contract to a VCO4K service contract. Cisco on-site services invoiced on a time and material basis.
VCO20-4K*	Yes	Yes	Any Version	V5.2 ANSI ISUP	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 2 years)	Retrofitting a VCO20 to make it "VCO4K compliant" requires the purchase of a certain set of hardware and requires Cisco to perform the retrofit and testing. This retrofit also requires that the system serial number be transferred from a VCO20 service contract to a VCO4K service contract. Cisco on-site services invoiced on a time and material basis.
VCO20-4K*	Yes	Yes	Any Version	V3.0 ITU ISUP	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20-4K*	Yes	Yes	Any Version	V5.0 ITU ISUP	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	8/1/01	8/1/00	Retrofitting a VCO20 to make it "VCO4K compliant" requires the purchase of a certain set of hardware and requires Cisco to perform the retrofit and testing. This retrofit also requires that the system serial number be transferred from a VCO20 service contract to a VCO4K service contract. Cisco on-site services invoiced on a time and material basis.
VCO20-4K*	Yes	Yes	Any Version	V5.1 ITU ISUP	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	11/1/02	11/1/01	Retrofitting a VCO20 to make it "VCO4K compliant" requires the purchase of a certain set of hardware and requires Cisco to perform the retrofit and testing. This retrofit also requires that the system serial number be transferred from a VCO20 service contract to a VCO4K service contract. Cisco on-site services invoiced on a time and material basis.
VCO20-4K*	Yes	Yes	Any Version	V5.2 ITU ISUP	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 2 years)	Retrofitting a VCO20 to make it "VCO4K compliant" requires the purchase of a certain set of hardware and requires Cisco to perform the retrofit and testing. This retrofit also requires that the system serial number be transferred from a VCO20 service contract to a VCO4K service contract. Cisco on-site services invoiced on a time and material basis.
VCO20-4K*	Yes	Yes	Any Version	V3.0 ANSI TCAP	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 2 years)	Retrofitting a VCO20 to make it "VCO4K compliant" requires the purchase of a certain set of hardware and requires Cisco to perform the retrofit and testing. This retrofit also requires that the system serial number be transferred from a VCO20 service contract to a VCO4K service contract. Cisco on-site services invoiced on a time and material basis.
VCO20-4K*	Yes	Yes	Any Version	V3.0 ITU TCAP	N/A	N/A	N/A	N/A	N/A	N/A	Not a supported configuration.
VCO20-4K*	Yes	Yes	Any Version	V5.1 ITU TCAP	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 2 years)	Retrofitting a VCO20 to make it "VCO4K compliant" requires the purchase of a certain set of hardware and requires Cisco to perform the retrofit and testing. This retrofit also requires that the system serial number be transferred from a VCO20 service contract to a VCO4K service contract. Cisco on-site services invoiced on a time and material basis.
VCO20-4K*	Yes	Yes	Any Version	CHINA TUP V5.1	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End-of-Sales date plus 2 years)	Retrofitting a VCO20 to make it "VCO4K compliant" requires the purchase of a certain set of hardware and requires Cisco to perform the retrofit and testing. This retrofit also requires that the system serial number be transferred from a VCO20 service contract to a VCO4K service contract. Cisco on-site services invoiced on a time and material basis.
VCO4K	Yes	No	V5.0	None	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	4/20/01	4/20/00	N/A	N/A
VCO4K	Yes	No	V5.1	None	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	4/20/02	4/20/01	N/A	N/A
VCO4K	Yes	No	V5.2	None	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- ales date plus 4 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 2 years)	N/A	N/A
VCO4K	Yes	No	Any Version	V5.0 ANSI ISUP	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	11/1/02	11/1/01
VCO4K	Yes	No	Any Version	V5.2 ANSI ISUP	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 2 years)
VCO4K	Yes	No	Any Version	V5.0 ITU ISUP	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	8/1/01	8/1/00
VCO4K	Yes	No	Any Version	V5.1 ITU ISUP	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	11/1/02	11/1/01
VCO4K	Yes	No	Any Version	V5.2 ITU ISUP	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 2 years)
VCO4K	Yes	No	Any Version	V3.0 ANSI TCAP	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 2 years)
VCO4K	Yes	No	Any Version	V5.1 ITU TCAP	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 2 years)
VCO4K	Yes	No	Any Version	CHINA TUP V5.1	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 2 years)
VCO4K	Yes	Yes	V5.0	None	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	4/20/01	4/20/00	N/A	N/A
VCO4K	Yes	Yes	V5.1	None	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	4/20/02	4/20/01	N/A	N/A
VCO4K	Yes	Yes	V5.2	None	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 2 years)	N/A	N/A
VCO4K	Yes	Yes	Any Version	V5.0 ANSI ISUP	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	11/1/02	11/1/01
VCO4K	Yes	Yes	Any Version	V5.2 ANSI ISUP	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 2 years)
VCO4K	Yes	Yes	Any Version	V5.0 ITU ISUP	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	8/1/01	8/1/00
VCO4K	Yes	Yes	Any Version	V5.1 ITU ISUP	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	11/1/02	11/1/01
VCO4K	Yes	Yes	Any Version	V5.2 ITU ISUP	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 2 years)
VCO4K	Yes	Yes	Any Version	V3.0 ANSI TCAP	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 2 years)
VCO4K	Yes	Yes	Any Version	V5.1 ITU TCAP	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 2 years)
VCO4K	Yes	Yes	Any Version	CHINA TUP V5.1	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 2 years)
VCO4K-NEBS	Yes	No	V5.0	None	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	4/20/01	4/20/00	N/A	N/A
VCO4K-NEBS	Yes	No	V5.1	None	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	4/20/02	4/20/01	N/A	N/A
VCO4K-NEBS	Yes	No	V5.2	None	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 2 years)	N/A	N/A
VCO4K-NEBS	Yes	No	Any Version	V5.0 ANSI ISUP	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	11/1/02	11/1/01
VCO4K-NEBS	Yes	No	Any Version	V5.2 ANSI ISUP	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 2 years)
VCO4K-NEBS	Yes	No	Any Version	V5.0 ITU ISUP	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	8/1/01	8/1/00
VCO4K-NEBS	Yes	No	Any Version	V5.1 ITU ISUP	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	11/1/02	11/1/01
VCO4K-NEBS	Yes	No	Any Version	V5.2 ITU ISUP	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 2 years)
VCO4K-NEBS	Yes	No	Any Version	V3.0 ANSI TCAP	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 2 years)
VCO4K-NEBS	Yes	No	Any Version	V5.1 ITU TCAP	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 2 years)
VCO4K-NEBS	Yes	No	Any Version	CHINA TUP V5.1	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 2 years)
VCO4K-NEBS	Yes	Yes	V5.0	None	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	4/20/01	4/20/00	N/A	N/A
VCO4K-NEBS	Yes	Yes	V5.1	None	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	4/20/02	4/20/01	N/A	N/A
VCO4K-NEBS	Yes	Yes	V5.2	None	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 2 years)	N/A	N/A
VCO4K-NEBS	Yes	Yes	Any Version	V5.0 ANSI ISUP	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	11/1/02	11/1/01
VCO4K-NEBS	Yes	Yes	Any Version	V5.2 ANSI ISUP	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 2 years)
VCO4K-NEBS	Yes	Yes	Any Version	V5.0 ITU ISUP	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	8/1/01	8/1/00
VCO4K-NEBS	Yes	Yes	Any Version	V5.1 ITU ISUP	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	11/1/02	11/1/01
VCO4K-NEBS	Yes	Yes	Any Version	V5.2 ITU ISUP	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 2 years)
VCO4K-NEBS	Yes	Yes	Any Version	V3.0 ANSI TCAP	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 2 years)
VCO4K-NEBS	Yes	Yes	Any Version	V5.1 ITU TCAP	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 2 years)
VCO4K-NEBS	Yes	Yes	Any Version	CHINA TUP V5.1	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 5 years)	End-date not yet announced. (Note: This End-date will be the End-of- Sales date plus 4 years)	Generic dependent. See above.	Generic dependent. See above.	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 3 years)	End-date not yet announced. (Note: This End-date will be the End- of-Sales date plus 2 years)

Frequently Asked Questions

Q1. When will the VCO-subsystem software (Generic and card downloads) and SS7-subsystem software (CKTINT, SEPT, CHINA-TUP) transition to "sustaining mode"? When will feature enhancement requests be considered only on a Business Case basis? What is the VCO-subsystem and SS7-subsystem software roadmap?

A1. The latest version of Generic software (VCO-subsystem software), the latest versions of SS7 CKTINT ISUP software (both ANSI and ITU), the latest versions of SS7 SEPT TCAP software (both ANSI and ITU), and the latest version of SS7 CHINA TUP software, transitioned to "sustaining mode" on 3/1/2001, shortly after the debut of Generic release train called "V5.2".

This means that feature enhancements will be considered on a Business Case basis.

The current roadmap, at time of publishing of this bulletin is:

Generic Software Roadmap (includes download software for cards): Generic Release 5.2.0 became available in Feb. 2001.

•Generic software transitioned to "Sustaining" mode on 3/1/2001

•Generic Release 5.2.1 targeted for July/August, 2001.

•Patch support of these software releases to be targeted on an as-needed basis.

•Currently, no planned feature enhancements, defect correction only.

•Feature enhancements will be considered on Business Case basis.

•No change to existing Sales, Support, Training, Documentation programs

SS7 CHINA TUP Software Roadmap:

•SS7 CHINA TUP software transitioned to "Sustaining" mode on 3/1/2001.

•Patch support of these software releases to be targeted on an as-needed basis.

•Currently, no planned feature enhancements, defect correction only.

•Feature enhancements considered on Business Case basis.

•No change to existing Sales, Support, Training, Documentation programs

SS7 CKTINT ISUP Software Roadmap:

•SS7 CKTINT ISUP software transitioned to "Sustaining" mode on 3/1/2001.

•Patch support of these software releases to be targeted on an as-needed basis.

•Currently, no planned feature enhancements, defect correction only.

•Feature enhancements considered on Business Case basis.

•No change to existing Sales, Support, Training, Documentation programs

SS7 SEPT TCAP Software Roadmap:

•SS7 SEPT TCAP software transitioned to "Sustaining" mode on 3/1/2001.

•Patch support of these software releases to be targeted on an as-needed basis.

•Currently, no planned feature enhancements, defect correction only.

•Feature enhancements considered on Business Case basis.

•No change to existing Sales, Support, Training, Documentation programs

Please contract your Cisco Account Executive to confirm current status of the software roadmaps.

Q2. How long will the VCO-subsystem software and SS7-subsystem software be open for bug fixes after the "sustaining mode" date of 3/1/2001 listed above? If an outstanding issue (bug) is identified that still needs to be resolved what should be expected as far as addressing the issue?

A2. Engineering Bug Fix Support, known as Software Engineering Maintenance Support, continues and then expires according to the system configuration that has been purchased.

For the given system configuration, refer in Table 4 to the column entitled "End of Engineering Software Maintenance Support Date for the VCO-subsystem" and the column entitled "End of Engineering Software Maintenance Support Date for the SS7-subsystem".

Following are 2 examples:

Example #1, system configuration is:

VCO80-NEBS

CBUS Installed? = No

CBUS Enabled? = Not Applicable

GENERIC = V5.1

SS7 = NONE

The VCO-subsystem Software Engineering Maintenance team will consider any confirmed Generic bugs for fix if reported to Cisco by 4/20/2002.

Example #2, system configuration is:

VCO80-NEBS-4K

CBUS Installed? = Yes

CBUS Enabled? = Yes

GENERIC = V5.2

SS7 = V5.2 ITU ISUP.

The VCO-subsystem Software Engineering Maintenance team will consider any confirmed Generic bugs for fix if reported to Cisco by 7/7/2002.

The SS7-subsystem Software Engineering Maintenance team will consider any confirmed SS7 bugs for fix if reported to Cisco by 7/7/2002.

Notice in the above examples that the end of Software Engineering Maintenance date varies per system configuration.

Q3. How long will RMA support on the Field Replaceable Unit (FRU) components be available for my system configuration?

A3. RMA support continues and then expires according to the system configuration that was purchased.

For a given system configuration, refer in Table 4 to the column entitled "Product Obsolete Date".

Q4. How long will we be able to obtain TAC support?

A4. TAC support continues and then expires according to the system configuration that you have purchased.

For a given system configuration, refer in Table 4 to the column entitled "Product Obsolete Date".

Q5. Our system configuration has card(s) that require a software download file in order to operate (e.g. the PRI/N card requires the software download file called "prin.dwn", the D+I card requires the software download file called "dni.dwn".). With respect to reading the columns of the detailed matrix, does Cisco classify these software download files as hardware or as software? How do I determine the End of Engineering Maintenance Support Date for these software download files?

A5. Cisco classifies these software download files as software.

In order to determine the End of Engineering Maintenance Support Date for these software download files, use the column entitled "End of Engineering Software Maintenance Support Date for the VCO-subsystem".

By way of example, a suspected bug has been reproduced and confirmed and is located in the prin.dwn file of the PRI/N card. Furthermore, if the system configuration is:

VCO80-NEBS

CBUS Installed? = No

CBUS Enabled? = Not Applicable

GENERIC = V5.2

SS7 = NONE

Then, in accordance with Table 4, "End of Engineering Software Maintenance Support Date for the VCO-subsystem", the bug must reported to Cisco Engineering by 7/7/2002 in order for Cisco Engineering to consider it for fix.

Q6. The detailed End of Life matrix, Table 4, does not explicitly document when Cisco will stop processing upgrade requests for the system configuration that I have purchased. What is the last day to order an Upgrade Kit for my system?

A6. When scheduling an upgrade for a system, Cisco strongly encourages you to order the System Upgrade Kit in sufficient time such that the last system upgrade is performed no later than six months before the Product Obsolete date.

Disclaimer: All Upgrade Kits are subject to availability of parts. This statement usually only applies to Upgrade Kits which require new circuit cards for which the "last date of sale" has passed.

Q7. Do up all upgrade requests require approval by Cisco? Who performs the upgrades?

A7. System configuration determines whether or not Cisco approval for your upgrade request is required and whether or not you are required to have Cisco perform the upgrade.

If your request requires Cisco approval, then please initiate the approval process with your Cisco Account Executive.

Generic Software:

Configuration Set #A: This range of configurations are exempt from Cisco Upgrade Request Approval, and, the customer or partner can perform the upgrade of these system configurations.

A.1:

Chassis Category: Either VCO4K-NEBS, VCO4K, VCO20-4K* (*Certified by Cisco as such), or VCO80-NEBS-4K* (*Certified by Cisco as such)

CBUS Physically Installed? YES

CBUS Enabled? Either YES or NO allowed

Version of "Generic" software present: V5.1 or higher

A.2:

Chassis Category: Either VCO80-NEBS, or VCO20

CBUS Physically Installed? NO

CBUS Enabled? N/A

Version of "Generic" software present: V5.1 or higher

Configuration Set #B: This range of configurations requires Cisco Upgrade Request Approval via on-site audit*, and, Cisco must perform the upgrade of these system configurations—should the system pass the on-site technical audit.

Chassis Category: Either VCO4K, VCO20-4K* (*Not certified by Cisco as such), or VCO80-NEBS-4K* (*Either not certified or certified by Cisco as such)

CBUS Physically Installed? YES

CBUS Enabled? Either YES or NO allowed

Version of "Generic" software present: V5.0

*Note: On-site audit billed on a time and material basis. Actual upgrade performed by Cisco billed on a time and material basis. May require purchase of certain hardware should the upgrade be approved.

Configuration Set #C: This range of configurations requires Cisco Upgrade Request Approval via on-site audit*, and, Cisco must perform the upgrade of these system configurations - should the system pass the on-site technical audit.

Chassis Category: Either VCO80-NEBS, VCO80-NEBS-4K, or VCO20

CBUS Physically Installed? NO

CBUS Enabled? N/A

Version of "Generic" software present: V5.0 or lower

*Note: On-site audit billed on a time and material basis. Actual upgrade performed by Cisco billed on a time and material basis. May require purchase of certain hardware should the upgrade be approved.

Configuration Set #D: This range of configurations may not be upgraded.

Chassis Category: SDS in any configuration

SS7 Software:

Configuration Set #E: This range of configurations are exempt from Cisco Upgrade Request Approval, and, the customer or partner can perform the upgrade of these system configurations.

E.1:

Chassis Category:

Either VCO4K-NEBS, VCO4K, VCO20-4K* (*Either not certified or certified by Cisco as such), or VCO80-NEBS-4K* (*Either not certified or certified by Cisco as such)

CBUS Physically Installed? YES

CBUS Enabled? Either YES or NO allowed

Version of "SS7" software present: V5.0 or higher

E.2:

Chassis Category: Either VCO80-NEBS, or VCO20

CBUS Physically Installed? NO

CBUS Enabled? N/A

Version of "SS7" software present: V5.0*

Configuration Set #F: This range of configurations require Cisco Upgrade Request Approval via on-site audit*, and, Cisco must perform the upgrade of these system configurations—should the system pass the on-site technical audit.

Chassis Category: Either VCO80-NEBS, VCO80-NEBS-4K, or VCO20

CBUS Physically Installed? NO

CBUS Enabled? N/A

Version of "SS7" software present: lower than V5.0

*Note: On-site audit billed on a time and material basis. Actual upgrade performed by Cisco billed on a time and material basis. May require purchase of certain hardware should the upgrade be approved.

Configuration Set #G: This range of configurations may not be upgraded.

Chassis Category: SDS in any configuration

Q8. From an Engineering Software Maintenance Support perspective (bug fix support perspective) my system is running a "retired version of Generic Software (e.g. V3.3, V4.0, V4.1, V4.2, V5.0) and/or SS7 Software". Also, the system is in production and running smoothly (no problems related to bugs). After having received this clarifying product bulletin, should I consider upgrading to the latest Generic and/or SS7 operating system software? Does doing so extend "the life of my system configuration"? In other words, does doing so effectively "push out" the product obsolete date?

A8. If your system is in production and running smoothly, albeit on a retired version of operating system software, then Cisco strongly discourages you from upgrading to a later release. You will not be granted any extension in the product obsolete date if you upgrade your system configuration.* This is because the product obsolete date for your chassis category is a fixed date regardless if you are running retired operating system software or non-retired operating system software.

*Note: The only legacy chassis category that can be granted a product obsolete date extension is the VCO20. See the strict guidelines in Q&A number 10 (below). This product obsolete date extension for the VCO20 requires a chassis retrofit not an upgrade (a retrofit is more extensive than an upgrade).

General upgrade guidelines to follow:

•If a software and/or hardware bug is discovered, then Cisco TAC (in Coordination with Cisco Engineering) will advise which software or hardware to migrate to address the problem. There is no need to pro-actively upgrade - merely based on the release of this product bulletin.

•If you regularly deploy Host software feature/maintenance releases, which regularly incorporate new VCO software releases, then continue to upgrade your VCO system configuration accordingly. Note: Please consider the key milestone dates, such as the product obsolete date when planning upgrades.

•All upgrades are subject to the Cisco upgrade policy detailed in Q&A number 7 (above).

Q9. The service support contract for my system has expired. Can I still take full advantage of the milestone dates documented in this bulletin without a service contract? Should I renew my service support contract?

A9. It is in your best interest to always have a service contract in effect. It is in your best interest to always renew your service contract one month before it expires. Contact your Cisco Account Executive for putting your systems under a service support contract.

Service contracts that have expired (without being renewed one month before having expired) and are within 12 months of the product obsolete date are not be eligible for renewal.

Without a service support contract, you system is not entitled to TAC support, RMA support, or Engineering support, without submitting, in advance, a purchase order for such services (these services are billed on an hourly basis).

Q10. What is a VCO20-4K?

A10. The VCO20-4K chassis category is an alternative option offered to customers with VCO20s in lieu of trading-in their VCO20 towards a purchasing of a VCO4K-NEBS systems.

Retrofitting a VCO20 or VCO20 with an SS7 shelf, in order to turn it into a VCO4K, requires swapping out ALL components in the VCO20 except for (1) the fantray, (2) power supplies and (3) power entry module, and, requires swapping out ALL components in the SS7 subsystem, except for (1) the power supplies in the SS7-shelf and (2) the components in the SS7-fallback-switch.

Under this alternative option, trade-in credit is given to those components traded-in towards the new components required to complete the retrofit.

Due to the amount of downtime needed in order to accomplish the retrofit, this alternative option is well suited for VCO20s in a lab environment.

In order to employ this alternative option in a production network while minimizing downtime, the following strategy is proposed:

Assume there are 5 VCO20s in your network. Replace the 1st VCO20 with a new VCO4K-NEBS and do a hot cable cutover. Retrofit the removed VCO20 #1 with the new VCO20-4K components and verify its operation.* Install retrofitted VCO20 and perform a hot cable cutover. Repeat the process for all of the VCO20s in you network.

*Note: Retrofitting a VCO20 to make it "VCO4K compliant" requires the purchase of a certain set of hardware and requires Cisco to perform the retrofit and testing. This retrofit also requires that the system serial number be transferred from a VCO20 service contract to a VCO4K service contract. Cisco on-site services are invoiced on a time and material basis.