As far as I know, no, there is no way to change the way packets are considered for compression with cRTP.
However, you might be able to just use a simple header compression. Your compression ratio will not be as great as instead of compressing 40 bytes like in cRTP you will be only compressing 28 bytes. But, at least you still have an option. You'd need to use
'ip rtp header-compression iphc-format' under the serial interface or modular QOS cli, here is an example:
class-map match-any identify-voip
mathc ip address 180
compress header ip rtp
access-list 180 permit udp any any range 4512 4600
Unfortunately, this might not work under frame-relay, unless you use ppp over frame-relay. I remember it being supported under PPP and HDLC only. Also, the statistics for rtp compression will not show anything being compressed, as no RTP was identified. I know it doesn't look like this should work, but that's how it is. You are still able to compress the header, but it's not an RTP compression no more.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...