Specifications

136
Caveats for Cisco IOS Release 12.0
78-6455-12
Resolved Caveats—Cisco IOS Release 12.0(3)
• CSCdk64929
When you configure X.25-over-TCP (XOT) keepalives on the X.25 route statements, a router might
restart with following (decoded) traceback:
c3640-js-mz.113-6.1.symbols read in
Enter hex value: 0x605FF664
0x605FF664:xot_update_keepalive(0x605ff644)+0x20
Enter hex value: 0x606094F8
0x606094F8:x25swt_verify_call(0x606092e4)+0x214
Enter hex value: 0x6060D880
0x6060D880:x25swt_process_incoming_call(0x6060d840)+0x40
Enter hex value: 0x6060D7CC
0x6060D7CC:x25swt_flagged_wakeup(0x6060d704)+0xc8
There is no workaround.
• CSCdk65469
A switch type TS014 numbering plan misidentifies the called number as “national” when it should
be “unknown.” There is no workaround.
• CSCdk66109
Under unusual circumstances that include protocol processing delays induced by debug reporting,
X.25 switching operations can cause a Cisco router to reload. There is no workaround.
• CSCdk66393
ISDN PRI switch type primary-ntt can get a slot map in Channel IE in an incoming Setup message.
It should not include the “interface specifier” in Channel IE of the Call Proceeding message. There
is no workaround.
• CSCdk66501
Call control blocks (CCBs) are not properly cleaned up on a Cisco 7500 series router with multiple
PRIs. Multiple CCBs are assigned to a single B-channel on a PRI after you issue the show isdn
status command. This might cause the router and ISDN switch to get out of synchronization with
regard to the available B-channels. This condition might cause a user to fail to connect, with the
failure reason being “Requested channel not available.” There is no workaround.
• CSCdk67475
Under heavy usage conditions on an X.25 serial link, a Cisco router running translated X.25 to
virtual asynchronous connections (PPP/IPX) might reload. This appears to be an infrequent
occurrence. There is no workaround.
• CSCdk67735
VPDN does not support Microsoft Challenge Handshake Authentication Protocol (MS-CHAP).
Workaround: Use CHAP or PAP.
• CSCdk70026
A status message with “endpointRef” is not processed in the multipoint state table. This could
result in releasing a multipoint virtual circuit. There is no workaround.
• CSCdk76492
Under heavy call connection and disconnection activity, the system might restart because of a
software error. There is no workaround.