Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why did my translation stop working after an upgrade to Cisco IOS Software Release 12.0?

0
Posted

Why did my translation stop working after an upgrade to Cisco IOS Software Release 12.0?

0

A. In Cisco IOS Software Releases 11.2 and earlier, translation calls with non-standard protocol identifiers (PIDs) were incorrectly accepted. The destination address matched the first translation entry that did not specify Call User Data (CUD). This translation is more accurate in Cisco IOS Software Release 12.0. The PID should be referred to as PAD (0x01000000) and the CUD data should be empty (the translation occurs if PAD is 0x01000000, but not if the data field of the CUD contains data). The translation line should match this value. This is necessary because the PID refers to how an application handles the incoming call. In our case, translation is always a PAD function. If the router receives an incoming call with an incorrect PID, it refuses the call because, on the remote host, the application is not referring to a PAD function. There are several workarounds for accepting incoming calls that do not refer to a PAD. The most common is the x25 default-pad command. Do not assume th

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123