Cisco Cisco IOS Software Release 12.2
537
Caveats for Cisco IOS Release 12.2
OL-3513-16 Rev. G0
Resolved Caveats—Cisco IOS Release 12.2(7c)
–
The boot system command is not in the configuration.
–
There is a complete and bootable Cisco IOS image on the disk, and there is a boot image in
bootflash.
bootflash.
Workaround: Set the router to boot the image from the disk using the boot system global
configuration command.
configuration command.
•
CSCdw94847
The call success rate (CSR) degrades about 5 percent when a Tool Command Language (TCL) 1.0
Debit Card script is used in a busy network environment. This symptom is observed on a
Cisco AS5800 universal access server that is running Cisco IOS Release 12.2(7a) or
Release 12.2(7b). Calls may be disconnected unexpectedly when this symptom occurs. This
symptom may be caused by a slow response from the RADIUS server when calls are set up and torn
down at the same time.
Debit Card script is used in a busy network environment. This symptom is observed on a
Cisco AS5800 universal access server that is running Cisco IOS Release 12.2(7a) or
Release 12.2(7b). Calls may be disconnected unexpectedly when this symptom occurs. This
symptom may be caused by a slow response from the RADIUS server when calls are set up and torn
down at the same time.
Workaround: Use a faster RADIUS server.
•
CSCdx06621
A router may reload with a bus error while the shortest path first (SPF) is computed. This symptom
is observed if multiple routers are advertising the same prefix in Type-5 or Type-7 link-state
advertisements (LSAs). There is no workaround.
is observed if multiple routers are advertising the same prefix in Type-5 or Type-7 link-state
advertisements (LSAs). There is no workaround.
•
CSCdx14383
A memory leak may occur when an E1 controller uses E1-R2 signaling. This symptom is observed
on an E1 controller that is installed on a Cisco AS5300 universal access server that is using E1-R2
signaling and that is running Cisco IOS Release 12.2(7). This symptom can be verified by examining
the command output of the show chunk | beg vtsp EXEC command:
on an E1 controller that is installed on a Cisco AS5300 universal access server that is using E1-R2
signaling and that is running Cisco IOS Release 12.2(7). This symptom can be verified by examining
the command output of the show chunk | beg vtsp EXEC command:
1320 8 2276 537 0 537 0 VTSP EVENT pool 0x618CC5C8
1320 8 713180 537 0 537 0 (data) 0x622BCA58
32 0 852 20 0 20 4 Call Management 0x6182D0D0
The value 0 (bold in the output above) indicates the number of voice telephony security parameter
(VTSP) EVENT chunks that are in use. This value should be 0 if no calls are present (as in the case
of the command output that is shown above). This value changes according to the number of active
calls. A continuous increase of this value indicates that VTSP EVENT memory is not being released,
eventually resulting in chunk memory allocation (MALLOC) failures. There is no workaround.
(VTSP) EVENT chunks that are in use. This value should be 0 if no calls are present (as in the case
of the command output that is shown above). This value changes according to the number of active
calls. A continuous increase of this value indicates that VTSP EVENT memory is not being released,
eventually resulting in chunk memory allocation (MALLOC) failures. There is no workaround.
•
CSCdx39412
A gateway may use an incorrect cause code value to release calls that are disconnected because of
the expiration of the Real-Time Transport Control Protocol (RTCP) timer. This symptom is observed
on a Cisco AS5300 universal access gateway that has the RTCP timer feature enabled by issuing the
timer receive-rtcp timer gateway configuration command to detect and release idle calls. There is
no workaround.
the expiration of the Real-Time Transport Control Protocol (RTCP) timer. This symptom is observed
on a Cisco AS5300 universal access gateway that has the RTCP timer feature enabled by issuing the
timer receive-rtcp timer gateway configuration command to detect and release idle calls. There is
no workaround.
•
CSCdx46031
After a call is stopped, the connection identity (conf-id) value is not displayed in the command
output of the debug voip aaa privileged EXEC command. This symptom is observed if the debug
voip aaa privileged EXEC command is issued while the gw-accounting aaa global configuration
command is enabled.
output of the debug voip aaa privileged EXEC command. This symptom is observed if the debug
voip aaa privileged EXEC command is issued while the gw-accounting aaa global configuration
command is enabled.
Workaround: To establish matching start and stop accounting routines, use the call ID in the
following accounting start and stop routines:
following accounting start and stop routines:
start_h323_ccapi_accounting(5)
stop_h323_ccapi_accounting(5)