Cisco Cisco IOS Software Release 12.4(23) Notas de publicación
380
Caveats for Cisco IOS Release 12.4
OL-7656-15 Rev. J0
Resolved Caveats—Cisco IOS Release 12.4(12b)
Conditions: This symptom has been observed on a Cisco 2851 router with Cisco IOS Release
12.4(13). This symptom has not been seen on Cisco IOS Release 12.4 (10) and earlier.
12.4(13). This symptom has not been seen on Cisco IOS Release 12.4 (10) and earlier.
Workaround: There is no workaround.
•
CSCsi27767
Symptoms: One-way audio may occur when a call is transferred or picked up after having been on
hold.
hold.
Conditions: This symptom is observed intermittently on a Cisco Communication Media Module
(CMM) for calls that are transcoded because of a transfer or being placed on hold and for which the
RTP stream terminates on the CMM.
(CMM) for calls that are transcoded because of a transfer or being placed on hold and for which the
RTP stream terminates on the CMM.
The symptom appears to occur because of a significant change in the sequence numbers and
timestamp of the RTP packets while the same SSRC is kept. You can identify this situation with a
packet capture of the RTP stream.
timestamp of the RTP packets while the same SSRC is kept. You can identify this situation with a
packet capture of the RTP stream.
Workaround: There is no workaround.
•
CSCsi42086
Symptoms: A memory leak may occur on a router that is configured for SSG when unsupported
3GPP attributes are received by SSG.
3GPP attributes are received by SSG.
Conditions: This symptom is observed when SSG is configured to function in RADIUS proxy mode.
Workaround: Ensure that the unsupported 3GPP attributes are removed by filtering them before a
RADIUS packet is received by SSG.
RADIUS packet is received by SSG.
TCP/IP Host-Mode Services
•
CSCsi40766
Symptoms: H.323 calls on a Cisco IOS VoIP gateway may fail after the gateway has processed about
54,500 calls.
54,500 calls.
Conditions: This symptom is observed when H.323 uses TCP to transport signaling messages. When
the Cisco IOS gateway must generate a unique port for the local TCP session, this port is selected
from a range of open ports. When the number of times that an unique TCP session is created for the
same IP address on the gateway exceeds 54,500, further attempts to create a local TCP port fail and
calls are not completed.
the Cisco IOS gateway must generate a unique port for the local TCP session, this port is selected
from a range of open ports. When the number of times that an unique TCP session is created for the
same IP address on the gateway exceeds 54,500, further attempts to create a local TCP port fail and
calls are not completed.
The symptom occurs for H.323 calls only when a separate TCP session is established for the H.245
session. When H.245 tunneling is enabled or no H.245 session is established, the symptom does not
occur for H.323 calls.
session. When H.245 tunneling is enabled or no H.245 session is established, the symptom does not
occur for H.323 calls.
When the debug ip tcp transaction command is enabled on the gateway, the "TCP: Ran out of ports
for network 0" debug output is generated when the symptom occurs.
for network 0" debug output is generated when the symptom occurs.
Enabling debugs on a Cisco IOS gateway should always be done with caution to minimize impact
to the performance of the router. As a minimum, ensure that logging to the console is changed from
the default behavior of the debug level to, for example, an informational level.
to the performance of the router. As a minimum, ensure that logging to the console is changed from
the default behavior of the debug level to, for example, an informational level.
Workaround: After the symptom has occurred, reload the Cisco IOS VoIP gateway. To prevent the
symptom from occurring, ensure that for H.323 call processing all H.323 devices have H.245
tunneling enabled. This may not always be possible: for example, H.245 tunneling on Cisco
CallManager is not supported.
symptom from occurring, ensure that for H.323 call processing all H.323 devices have H.245
tunneling enabled. This may not always be possible: for example, H.245 tunneling on Cisco
CallManager is not supported.