Profile SDP Description
Last updated
Was this helpful?
Last updated
Was this helpful?
You can specify the Profile SDP Description to define which are supported in the using this Profile.
Here is the default Profile SDP Description.
Each line of the Profile SDP Description consists of text of the form <type>=<value>. <type> is always exactly one character and is case-significant. <value> is a structured text string whose format depends on <type>. It also will be case-significant unless a specific field defines otherwise. Whitespace is not permitted either side of the `=' sign. In general <value> is either a number of fields delimited by a single space character or a free format string.
In our Profile SDP Description, only 2 <type> are used.
The format of media announcement is as follows.
m=<media> <port> <transport> <fmt list>
The first sub-field is the media type. Currently defined media for TMedia is "audio".
The second sub-field is the transport port to which the media stream will be sent. In Toolpack, it is not specified in Profile SDP Description and therefore you should specify "0".
The third sub-field is the transport protocol. For most of the application, you may specify it as "RTP/AVP" - the IETF's Realtime Transport Protocol using the Audio/Video profile carried over UDP.
The fourth and subsequent sub-fields are media formats. For audio and video, these will normally be media payload types as defined in the RTP Audio/Video Profile. When a list of payload formats is given, this implies that all of these formats may be used in the session, but the first of these formats is the default format for the session. When the transport protocol is specified as "RTP/AVP", the payload format can be specified as either
the payload type number for static payload types
the payload type number along with additional encoding information for dynamically allocated payload types.
The payload type, which is carried in the actual RTP packet header, is used to identify the type of codec information carried in the packet. A list of payload type values for each codec is defined within RFC3551. Unfortunately, since the payload type field is only 7 bits-wide, all codecs cannot have a permanent payload type value understood universally by all VoIp systems. Therefore, some codecs have dynamic values that need to be negotiated through a call control or session control protocol such as SIP before the actual RTP session can take place.
Here is the list of codec payload type values per RFC3551.
G.711 uLaw
0
G.723.1
4
G.711 aLaw
8
G.722
9
Comfort Noise
13
G.728
15
G.729AB
18
G.726-40
dynamic
G.726-32
2 or dynamic (depends on the network)
G.726-24
dynamic
G.726-16
dynamic
G.729EG
dynamic
AMR
dynamic
EVRC
dynamic
QCELP
dynamic
When you use dynamic payload types, you need to specify the additional encoding information using the attribute for media announcement.
A media description may have any number of attributes ("a=" fields) which are media specific. The format of attribute is as follows.
a=ora=:<value>
Here are some examples of attributes.
Dynamic payload type
You specify the additional encoding information for dynamic payload type in the following format:
a=rtpmap:<payload type> <encoding name>/<clock rate>[/<encoding parameters>]
For audio streams, <encoding parameters> may specify the number of audio channels. This parameter may be omitted if the number of channels is one provided no additional parameters are needed.
Other media specific attribute
The use of other media specific attributes depends on the specification of the RTP payload format for the specific media type. Here are some example of attributes.
a=fmtp:<format> <format specific parameters>
This attribute allows parameters that are specific to a particular format to be conveyed in a way that SDP doesn't have to understand them. The format must be one of the formats specified for the media. Format-specific parameters may be any set of parameters required to be conveyed by SDP and given unchanged to the media tool that will use this format.
a=ptime:<packet time>
This gives the length of time in milliseconds represented by the media in a packet. This is probably only meaningful for audio data. It should not be necessary to know ptime to decode RTP or vat audio, and it is intended as a recommendation for the encoding/packetisation of audio. It is a media attribute, and is not dependent on charset.
Examples
Here are some examples of the attributes found in the default profile SDP description.
The above defines iLBC codec of 8000/sec sample rate with 20ms frame size.
The above defines the DTMF and telephony tones relay over RTP using RFC2833.
Here is another example, enabling Voice Activity Detection (VAD) for G.711 ulaw, G.711 alaw, G.723.1a and G.729b. It also enable relay of DTMF events 0 to 15 and telephony tones events 32 to 36.
Another example to disable silence suppression explicitly in the SDP.
Below shows an example to enable GSM-FR with a dynamic payload type 99:
Note: 1. Your toolpack license needs to be GSM enabled. Please contact TelcoBridges support if you are not sure. 2. You may need additional third party GSM license(s) from the corresponding patent holders. e.g. GSM-EFR, GSM-HR
Below shows an example to enable GSM-FR with a dynamic payload type 99:
This example is G.711 alaw with a 10ms packet (instead of the default 20ms) :
This example is AMR-WB (using dynamic payload type 113) and G.722 (static payload type 9) :
- SDP: Session Description Protocol
- RTP Profile for Audio and Video Conferences with Minimal Control
- Real-time Transport Protocol (RTP) Payload Format for internet Low Bit Rate Codec (iLBC) Speech
- RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals