Additional Information
This section contains detailed tables to use as a reference when you are learning about H.323 features or when you are configuring them.
About Payload Types
You set the payload type when you are configuring a media profile to support Slow Start to Fast Start Translation.
When you configure media profiles, you might need set the payload type to identify the format in the SDP m lines. For RTP/AVP, the default transport method of a media profile configuration, this will be the RTP payload type number. Newer codecs have dynamic payload types, which means that they do not have an assigned payload type number.
When you use RTP/AVP as the transport method, you should only set the payload type when there is a standard payload type number for the encoding name; otherwise, leave the payload type blank.
The Oracle® Enterprise Session Border Controller uses the payload type value to determine the encoding type when SDP identifies the standard payload type in the m line, but does not include an a=rtpmap entry. These are two equivalent SDPs:
c=IN IP4 192.0.2.4
m=audio 0 RTP/AVP 0
c=IN IP4 192.0.2.4
m=audio 0 RTP/AVP 0
a=rtpmap:0 PCMU/8000
The first does not include the RTP map entry, but uses the standard payload type of 0. If the Oracle® Enterprise Session Border Controller receives an SDP like the first, it uses the payload type 0 to locate the corresponding media profiles configuration. When an a=rtpmap is present, the Oracle® Enterprise Session Border Controller uses the encoding name in the a=rtpmap line to find the media profile configuration and does not consider the payload type number.
Payload Types for Standard Audio and Visual Encodings
The following is a table of standard audio and visual payload encodings defined in H. Schulzrinne, GND Fokus, RTP Profile for Audio and Visual Conferences with Minimal Control, RFC 1890, and in the RTP Parameters document in IANA’s Directory of Generally Assigned Numbers.
Payload Type | Encoding Name | Audio (A)/Visual (V) | Clock Rate (Hz) |
---|---|---|---|
0 | PCMU | A | 8000 |
1 | 1016 | A | 8000 |
2 | G721 | A | 8000 |
3 | GSM | A | 8000 |
4 | G723 | A | 8000 |
5 | DVI4 | A | 8000 |
6 | DVI4 | A | 16000 |
7 | LPC | A | 8000 |
8 | PCMA | A | 8000 |
9 | G722 | A | 8000 |
10 | L16 | A | 44100 |
11 | L16 | A | 44100 |
12 | QCELP | A | 8000 |
13 | reserved | A | N/A |
14 | MPA | A | 90000 |
15 | G728 | A | 8000 |
16 | DVI4 | A | 11025 |
17 | DVI4 | A | 22050 |
18 | G729 | A | 8000 |
19 | reserved | A | N/A |
20 | unassigned | A | N/A |
21 | unassigned | A | N/A |
22 | unassigned | A | N/A |
23 | unassigned | A | N/A |
dyn | GSM-HR | A | 8000 |
dyn | GSM-EFR | A | 8000 |
dyn | L8 | A | var. |
dyn | RED | A | N/A |
dyn | VDVI | A | var. |
24 | unassigned | V | N/A |
25 | CelB | V | 90000 |
26 | JPEG | V | 90000 |
27 | unassigned | V | N/A |
28 | nv | V | 90000 |
29 | unassigned | V | N/A |
30 | unassigned | V | N/A |
31 | H261 | V | 90000 |
32 | MPV | V | 90000 |
33 | MP2T | AV | 90000 |
34 | H263 | V | 90000 |
35-71 | unassigned | ? | N/A |
72-76 | reserved for RTCP conflict avoidance | N/A | N/A |
77-95 | unassigned | ? | N/A |
96-127 | dynamic | ? | N/A |
dyn | BT656 | V | 90000 |
dyn | H263-1998 | V | 90000 |
dyn | MP1S | V | 90000 |
dyn | MP2P | V | 90000 |
dyn | BMPEG | V | 90000 |
About RAS Message Treatment
When you enabled the H.323 Registration Proxy, the Oracle® Enterprise Session Border Controller modifies and deletes certain fields as outlined in the table below. The Oracle® Enterprise Session Border Controller forwards any fields that are not listed in this table without modifying or deleting them.
Note:
Although the Oracle® Enterprise Session Border Controller forwards a field, it does not always support the feature related to that field.Field Name | Message | Deleted | Modified | Value Used in Modification |
---|---|---|---|---|
alternateEndpoints | RRQ, URQ, ACF | X | N/A | N/A |
alternateGatekeeper | RCF, URQ | X | N/A | N/A |
altGKInfo | RRJ, URJ, DRJ | X | N/A | N/A |
alternateTransportAddresses | RRQ, ARQ, ACF | X | N/A | N/A |
callModel | ARQ | N/A | X | direct |
N/A | ACF | N/A | X | gatekeeperRouted |
callSignalAddress | RRQ | N/A | X | Mapped virtual CSA allocated by the system for registering the endpoint. |
N/A | RCF, ARJ | N/A | X | CSA of gatekeeper stack |
N/A | URQ | N/A | X | If URQ is from an endpoint, endpoint’s mapped virtual CSA. If URQ is from a gatekeeper, real CSA of endpoint. |
destCallSignalAddress | ARQ, ACF | X | N/A | N/A |
destinationInfo.transportID | ARQ, ACF | X | N/A | N/A |
destExtraCallInfo.trasnportID | ARQ, ACF | X | N/A | N/A |
discoveryComplete | RRQ | N/A | X | TRUE |
endpointAlias.trasnportID | URQ | X | N/A | N/A |
endpointAliasPattern.Wwildcard.transportID | URQ | N/A | N/A | N/A |
featureServerAlias.trasnportID | RCF | X | N/A | N/A |
gatekeeperIdentifier | RRQ | N/A | X | Gatekeeper identifier of the gateway stack, either configured in the H.323 gateway stack or discovered dynamically. |
maintainConnection | RRQ, RCF | N/A | X | FALSE |
mutlipleCall | RRQ, RCF | X | FALSE | |
preGrantedARQ.alternateTransportAddresses | RCF | X | N/A | N/A |
preGrantedARQ.useSpecifiedTransport | RCF | X | N/A | N/A |
rasAddress | RRQ | N/A | X | Mapped virtual RAS address allocated by the system for registering endpoint |
remoteExtentsionAddress.trasnportID | ARQ, ACF | X | N/A | N/A |
srcCallSignalAddress | ARQ | X | N/A | N/A |
srcInfo.transportID | ARQ | X | N/A | N/A |
supportedH248Packages | RRQ | X | N/A | N/A |
supportsAltGK | RRQ | X | N/A | N/A |
supportedPrefixes.prefic.transportID | RCF, URQ | X | N/A | N/A |
terminalAlias.transportID | RRQ | X | N/A | N/A |
terminalAliasPattern.wilcard.transportID | RRQ | X | N/A | N/A |
willRespondToIIRR | RCF, ACF | X | N/A | N/A |
willSupplyUUIEs | RRQ, ARQ | N/A | N/A | |
uuiesRequested
setup callProceeding connect alerting information releaseComplete facility progress empty ..., status statusInquiry setupAcknowledge notify |
ACF | N/A | X
X X X X X X X X X X X X |
FALSE
FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE FALSE |