Specifications
137
Caveats for Cisco IOS Release 12.0
78-6455-12
Resolved Caveats—Cisco IOS Release 12.0(2)
Resolved Caveats—Cisco IOS Release 12.0(2)
All the caveats listed in this section are resolved in Cisco IOS Release 12.0(2). This section describes
severity 1 and 2 caveats and select severity 3 caveats.
Access Server
• CSCdk09732
R2 signaling is failing in Croatia. According to the ITU specification (page 60 Note II), the router
needs to act on the SEIZURE signal between 100 to 200 msec. This occurs around 150
milliseconds, within specification. However, for Croatia it has been confirmed by the switch
manufacturer as well the PTT HPT, that the typical value needs to be 50 msec, maximum 60 msec.
• CSCdk20217
On Cisco AS5200 and Cisco AS5300 access servers, assertion failures can result in the servers
failing.
• CSCdk30581
An access server might fail when a MICA device runs out of buffers (prints out NO_BUF messages
on the console) and a lot of EXEC sessions are running. This problem has been observed with the
latest 56K modems.
• CSCdk36682
A Cisco AS5300 access server might fail to place a call and issue the message “no signalling
channel is available for outgoing call” because of certain sequences of shutdown and no shutdown
on T1 controllers, if controllers have both CAS and PRI configured. The workaround is to always
configure no shutdown on controllers with CAS first.
• CSCdk38665
When you configure a channel group, unconfigure the channel group, and then configure a PRI
group with Cisco IOS Release 11.3 T and later, a bus error occurs.
• CSCdk39751
The failed call count does not include unanswered calls.
• CSCdk62405
The absolute-timeout line configuration command does not accept a value for the timeout
parameter.
AppleTalk
• CSCdj72157
AppleTalk subinterfaces on SMDS return the wrong SMDS address when an AARP request is sent.
The router returns the SMDS address associated with the first subinterface regardless of which
subinterface is associated with the AARP request.
• CSCdk38556
Disabling a subinterface turns off AppleTalk route-cache for all subinterfaces on that interface.
Workaround: Enable the subinterfaces’ AppleTalk route-cache after disabling one of the
subinterfaces by issuing the interface subinterface appletalk route-cache command.