About Dynamic Payload Mapping

G.729a and G.729ab use dynamic payload types, but the Oracle® Enterprise Session Border Controllerdoes not propagate these dynamic payload types to corresponding dynamicRTPPayloadType (an optional field in OpenLogicalChannel requests) on the H.323 side.

For an IWF call initiated in H.323, the dynamic payload types for G.729a and G.729ab are retrieved from media profile configurations when the Oracle® Enterprise Session Border Controller converts the list of fastStart OpenLogicalChannel requests to SDP sent on the SIP side. As a result, you must set up media profile configurations for G.729a and G.729ab for the feature to work properly. In these media profiles, the following parameters must be set as follows:

• name—For the G.729a profile, set the name to G.729a. For the G.729ab profile, set the name to G.729ab.
• payload-type—For each media profile (G.729a and G.729ab), DO NOT use payload type 18, which is the static payload type used for G729.