Cisco Cisco ASA 5515-X Adaptive Security Appliance - No Payload Encryption Guida Informativa
Avaya does not recognize payload 20, and the ASA does not understand payload type 15. The explanation for
this behavior is because, in 2004, the same RFC defined the payload type as 15. Therefore, since 2004, the
Avaya phones that use this payload type are no longer RFC compliant. So, why did it work with older code?
Because, like Avaya, some of the older code (Version 8.0.x) still supports the old ID. However, the newer
code (Versions 8.2.1+) is supposed to be compliant with the new RFC value and should not support payload
type15. Nonetheless, you can find various versions around that still support payload type15, which is what
causes the problem.
this behavior is because, in 2004, the same RFC defined the payload type as 15. Therefore, since 2004, the
Avaya phones that use this payload type are no longer RFC compliant. So, why did it work with older code?
Because, like Avaya, some of the older code (Version 8.0.x) still supports the old ID. However, the newer
code (Versions 8.2.1+) is supposed to be compliant with the new RFC value and should not support payload
type15. Nonetheless, you can find various versions around that still support payload type15, which is what
causes the problem.
Avaya needs to fix the firmware on the phone so that the built−in VPN client uses the right paylod ID.
Unfortunately, some other Avaya phones, like the 46xx Series, are no longer in production and will not get a
fix. In this case, you either need to obtain new equipment or need to downgrade the ASA to a version on
which it was working. Obviously this latter option is not available if you upgraded in order to get a bug fix in
the first place. Any of Cisco's software versions that work with the older payload ID need to be reported and
the issue fixed on those versions.
Unfortunately, some other Avaya phones, like the 46xx Series, are no longer in production and will not get a
fix. In this case, you either need to obtain new equipment or need to downgrade the ASA to a version on
which it was working. Obviously this latter option is not available if you upgraded in order to get a bug fix in
the first place. Any of Cisco's software versions that work with the older payload ID need to be reported and
the issue fixed on those versions.
Updated: Jul 17, 2013
Document ID: 116294