If you want CUBE to change packetization rates between legs, DSPs will be required.
The only other option is to use the packetization that is offered on the inbound leg on the outbound leg (i.e. it would behave functionally as if the two endpoints on each side of CUBE were talking media negotiation directly with each other). If you are doing h323-to-h323 CUBE you can use codec transparent on both legs as an easy way to do this. Otherwise, you need to know the criteria for each incoming leg and craft an incoming and outgoing dial-peer specifically for those flows. That can get tricky unless you understand inbound and outbound dial-peer matching and translation rules very well.
In summary, you need to buy DSPs or don't have packetization mismatches between endpoints.
That command will work, but in order for the codec to negotiate without a DSP, you need to use that same codec and same packetization on each leg of the CUBE, so that needs to be configured under both the inbound and the outbound dial-peer. You cannot use a different packetization on one side.
1. Introduction Internet security is important with the increasing
attacks that are happening every day. Many internet and browsing
security solutions exist, but some are not very easy to use or maybe the
question is how can I enable them? In this referen...
Cisco Software Manager Server API Guide This document describes the
programmatic interfaces, RESTful APIs, which are supported by Cisco
Software Manager Server (CSM Server). Overview CSM Server supports a set
of finite RESTful APIs. The first step to use ...
If you are using Cisco's new linux-based Cisco Software Manager server,
then you probably want to make sure there is a startup service for
it.I'll assume that you've already installed the CSM server on a
systemd-based linux system. The commands given belo...