Добавил:
Upload Опубликованный материал нарушает ваши авторские права? Сообщите нам.
Вуз: Предмет: Файл:
understanding-SIP.pdf
Скачиваний:
118
Добавлен:
01.03.2016
Размер:
4 Мб
Скачать
☆

Negotiating Media Sessions

293

13.1.7 Bandwidth

The optional b= field contains information about the bandwidth required. It is of the form:

b=modifier:bandwidth-value

The modifier is either CT for conference total or AS for application specific. CT is used for multicast session to specify the total bandwidth that can be used by all participants in the session. AS is used to specify the bandwidth of a single site. The bandwidth-value parameter is the specified number of kilobytes per second.

13.1.8 Time, Repeat Times, and Time Zones

The t= field contains the start time and stop time of the session.

t=start-time stop-time

The times are specified using NTP [4] timestamps. For a scheduled session, a stop-time of zero indicates that the session goes on indefinitely. A start-time and stop-time of zero for a scheduled session indicates that it is permanent. The optional r= field contains information about the repeat times that can be specified in either in NTP or in days (d), hours (h), or minutes (m). The optional z= field contains information about the time zone offsets. This field is used if a reoccurring session spans a change from daylight savings to standard time, or vice versa.

13.1.9 Encryption Keys

The optional k= field was used to carry encryption keys. However, its use is no longer recommended and was included in RFC 4566 for parser compatibility reasons. Instead, a=crypto or a=key-mgt should be used, whose use is described in Chapter 14.

13.1.10 Media Announcements

The optional m= field contains information about the type of media session. The field contains:

m=media port transport format-list

The media parameter is either audio, video, text, application, message,

image, or control. The port parameter contains the port number. The transport

294

SIP: Understanding the Session Initiation Protocol

parameter contains the transport protocol or the RTP profile used. The set of defined RTP profiles is in Table 15.3. The format-list contains more information about the media. Usually, it contains media payload types defined in RTP audio video profiles. More than one media payload type can be listed, allowing multiple alternative codecs for the media session. For example, the following media field lists three codecs:

m=audio 49430 RTP/AVP 0 6 8 99

One of these three codecs can be used for the audio media session. If the intention is to establish three audio channels, three separate media fields would be used. For non-RTP media, Internet media types should be listed in the format-list. For example,

m=application 52341 udp wb

could be used to specify the application/wb media type. Common SDP media types are listed in Table 13.2.

13.1.11 Attributes

The optional a= field contains attributes of the preceding media session. This field can be used to extend SDP to provide more information about the media. If not fully understood by a SDP user, the attribute field can be ignored. There can be one or more attribute fields for each media payload type listed in the media

Table 13.2

Common SDP Media Types

Example

Type

Specificiation

 

 

 

m=audio 49122 RTP/AVP 0

Audio media, also used for

RFC 3551

telephone-events (DTMF)

 

 

m=video 52134 RTP/SAVP 24

Video media

RFC 3551

m=text 11000 RTP/AVP 98

Real-time text (T.140)

RFC 4103

m=application 12454 wb udp

Application media, used

 

m=application 3422 TCP/TLS/BFCP *

for white board (wb), BFCP,

RFC 4566

m=application 554 TCP/RTSP rtsp

RTSP, and others

 

 

 

m=message 12763 TCP/MSRP *

Message media for MSRP

RFC 4975

m=image 54111 TCP t38

Fax (T.38) Note: Fax can also

RFC 3362

use a m=audio media type

RFC 4612

 

m=control

Control media

RFC 2327

Negotiating Media Sessions

295

field. For the media line example in Section 13.1.9, the following three attribute fields could follow the media field:

a=rtpmap:0 PCMU/8000 a=rtpmap:6 DVI4/16000 a=rtpmap:8 PCMA/8000 a=rtpmap:99 iLBC

Other attributes are shown in Table 13.3. Full details of the use of these attributes are in the standard document [2]. The details of the iLBC (Internet low bit rate) codec are in [5].

Attributes can be either session level or media level in SDP. Session level means that the attribute is listed before the first media line in the SDP. If this is the case, the attribute applies to all the media lines below it. Media level means it is listed after a media line. In this case, the attribute only applies to this particular media stream. SDP can include both session level and media level attributes. If the same attribute appears as both, the media level attribute overrides the session level attribute for that particular media stream.

Note that the connection data field can also be session level or media level. There are three possibilities:

 

Table 13.3

 

SDP Attribute Values Defined in RFC 4566

Attribute

Name

 

 

a=rtpmap:

RTP/AVP list.

a=fmtp:

Format transport.

a=ptime:

Length of time in milliseconds for each packet.

a=maxptime:

Maximum ptime.

a=cat:

Category of the session.

a=keywds:

Keywords of session.

a=tool:

Name of tool used to create SDP.

a=orient:

Orientation for whiteboard sessions.

a=type:

Type of conference.

a=charset:

Character set used for subject and information fields.

a=sdplang:

Language for the session description.

a=lang:

Default language for the session.

a=framerate:

Maximum video frame rate in frames per second.

a=quality:

Suggests quality of encoding.

a=direction:

Direction for symmetric media.

a=inactive

Inactive mode.

a=recvonly

Receive only mode.

a=sendrecv

Send and receive mode.

a=sendonly

Send only mode.

Соседние файлы в предмете [НЕСОРТИРОВАННОЕ]