SIP与WebRTC协议的多媒体会话指南

webrtc

需积分: 11 186 浏览量更新于2024-07-14 收藏 28.69MB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

《SIP与WebRTC IP电话手册》（SIP and WebRTC IP Telephony）是由Radhika Ranjan Roy撰写的一本专业书籍，它探讨了Session Initiation Protocol (SIP) 和 Real-Time Communication (RTC) 技术在IP电话系统中的应用。SIP是一种开放标准，用于控制多媒体通信会话的建立、管理和终止，特别适用于VoIP（Voice over Internet Protocol）环境。WebRTC则是一个开源项目，旨在让实时通信更加简单，使得浏览器和其他网络应用可以直接进行音频、视频和数据的通信，无需依赖第三方插件。书中详细介绍了Session Description Protocol (SDP)，它是SIP协议的核心组成部分，用于描述和交换参与通信的媒体流（如音频、视频、数据共享等）的参数，包括带宽、编码方式、时延等。SDP协商是多媒体会话建立过程中的关键环节，通过这些参数，通信双方能够确定合适的媒体质量和网络资源分配。《Handbook of SDP for Multimedia Session Negotiations》提供了深入理解SDP工作原理和实践技巧的指南，涵盖了如何在SIP和WebRTC框架下优化多媒体会话设置，包括端到端的连接管理、质量保证、安全性和兼容性问题。该书不仅适合网络通信领域的专业人士，也对开发者、系统管理员以及寻求提升VoIP和实时通信性能的技术人员具有很高的参考价值。书中还强调了版权问题，指出尽管出版商已尽力确保信息的准确性和可靠性，但不能保证所有引用材料的版权已被合法授权，因此，如果发现未被提及的版权内容，作者和出版社鼓励读者主动联系版权所有者获取许可。《SIP and WebRTC IP Telephony.pdf》是一本实用的参考资料，涵盖了从理论到实践的广泛内容，是深入了解和实施基于SIP和WebRTC的IP电话技术的宝贵资源。阅读这本书，读者可以学习到如何构建高效、可靠的IP语音通信系统，并处理相关协议和技术挑战。

资源详情

资源推荐

List of Tables

Table 1.1 SIP Response Classes, Descriptions, and Actions ................................................ 5

Table 1.2 W3C WebRTC APIs [2] Draft ......................................................................... 24

Table 1.3 IETF WebRTC Protocol Drafts ....................................................................... 27

Table 2.1 Terminologies and eir Denitions ................................................................ 36

Table 9.1 List of Transport Parameter Values Used in SDP in the ATM Context

(Copyright: IETF) .......................................................................................... 404

Table 9.2 Encoding Names and Payload Types (Copyright: IETF) ................................ 432

Table 9.3 Example of a Custom AAL2 Prole (Copyright: IETF) ................................. 437

Table 13.1 Roles (Copyright IETF) ...................................................................................574

Table 15.1 Binary Representation of the Static SIP/SDP Dictionary for SigComp

(Copyright IETF) ............................................................................................. 635

Table 18.1 SDP Oer (Copyright IETF) .......................................................................... 772

Table 18.2 SDP Answer (Copyright IETF) .......................................................................774

Table 18.3

SDP Oer (Copyright IETF) ....................................................................................... 776

Table 18.4 SDP Answer (Copyright IETF) ...................................................................... 778

Table 18.5 SDP Oer (Copyright IETF) .......................................................................... 780

Table 18.6 SDP Answer (Copyright IETF) .......................................................................782

Table 18.7 SDP Oer (Copyright IETF) .......................................................................... 784

Table 18.8 SDP Answer (Copyright IETF) .......................................................................785

Table 18.9 SDP Oer (Copyright IETF) .......................................................................... 786

Table 18.10 SDP Answer .................................................................................................... 787

Table 18.11 SDP Oer (Copyright IETF) ...........................................................................789

Table 18.12 SDP Answer (Copyright IETF) ....................................................................... 790

Table 18.13 SDP Oer (Copyright IETF) .......................................................................... 792

Table 18.14 SDP Answer (Copyright IETF) ........................................................................793

Table 18.15 SDP Oer w/BUNDLE (Copyright IETF) ..................................................... 795

Table 18.16 SDP Answer w/BUNDLE (Copyright IETF) ................................................. 797

Table 18.17 SDP Oer (Copyright IETF) .......................................................................... 799

Table 18.18 SDP Answer (Copyright IETF) ........................................................................801

Table 18.19 SDP Oer w/BUNDLE (Copyright IETF) ..................................................... 803

Table 18.20 SDP Answer without BUNDLE (Copyright IETF) ........................................ 805

Table 18.21 SDP Oer (Copyright IETF).......................................................................... 807

Table 18.22

P Answer (Copyright IETF)

...................................................................... 8

Table 18.23

P Oer (Copyright IETF)

..........................................................................8

Table 18.24

P Answer (Copyright IETF)

.......................................................................81

Table 18.25

SDP

Updated Oer (Copyright IETF)

............................................................81

www.TechnicalBooksPDF.com

xvi ◾ List of Tables

Table 18.26 SDP Updated Answer (Copyright IETF) .........................................................814

Table 18.27 SDP Oer (Copyright IETF)...........................................................................816

Table 18.28 SDP Answer (Copyright IETF) .......................................................................819

Table 18.29 SDP Oer with SVC (Copyright IETF) ......................................................... 822

Table 18.30 SDP Answer with SVC (Copyright IETF) ...................................................... 823

Table 18.31 SDP Oer w/Simulcast, RTX (Copyright IETF) .............................................825

Table 18.32 SDP Answer w/Simulcast, RTX (Copyright IETF) ........................................ 827

Table 18.33 SDP Oer w/Simulcast, RTX (Copyright IETF) ............................................ 829

Table 18.34 SDP Answer (One Simulcast Rejected) (Copyright IETF) ..............................831

Table 18.35 SDP Oer (Copyright IETF) ..........................................................................833

Table 18.36 SDP Answer (Copyright IETF) ...................................................................... 834

Table 18.37 SDP Oer (Copyright IETF)...........................................................................837

Table 18.38 SDP Answer (Copyright IETF) ...................................................................... 838

Table 18.39 SDP Oer (Copyright IETF) ..........................................................................839

Table 18.40 SDP Answer (Copyright IETF) ...................................................................... 840

Table 18.41 SDP Simulcast Bundle-Only (Copyright IETF) ............................................. 842

Table 18.42 SDP Answer (Copyright IETF) ...................................................................... 844

Table 18.43 SDP Oer (Copyright IETF) .......................................................................... 846

Table 18.44 SDP Answer (Copyright IETF) ...................................................................... 848

www.TechnicalBooksPDF.com

xvii

Preface

I have been working on networked multimedia communications all along including at my pres-

ent position at the United States Army Research, Development and Engineering Command

(RDECOM), Communications-Electronics Research, Development, and Engineering Center

(CERDEC); Space and Terrestrial Communications Directorate (S&TCD) Laboratories for

large-scale global Session Initiation Protocol (SIP)-based Voice-over-Internet Protocol (VoIP)/

Multimedia networks since 1993 while I had been at AT&T Bell Laboratories. I had been the

editor of Multimedia Communications Forum (MMCF) when it was created by many participat-

ing companies throughout the world including AT&T for promoting the technical standards for

networked multimedia communications to ll an important gap of that time when no standard

bodies came forward to do so. Later on, I had the opportunity to participate in International

Telecommunication Union—Telecommunication (ITU-T) on behalf of AT&T for standardiza-

tion of H.323. H.323 has been the rst successful technical standard for VoIP/multimedia tele-

phony. However, SIP that has been standardized in the Internet Engineering Task Force (IETF)

much later than H.323 and has emulated the simplicity of the protocol architecture of Hypertext

Transfer Protocol (HTTP) has started to be popularized for VoIP over the Internet because of its

friendliness to be meshed with web services.

After so many years of working experiences on SIP for building the large-scale VoIP networks,

I have found that it is an urgent requirement to have a complete book that integrates all SIP-related

Request For Comments (RFCs) in a systematic way that network designers, software develop-

ers, product manufacturers, implementers, interoperability testers, professionals, professors, and

researchers can use as if as a “super-SIP RFC” since the publication of SIP RFC 3261 in the year

2002. To ll this gap, I published the book: Handbook on SIP: Networked Communications IP

Telephony, CRC Press, March 2016.

One of the most fundamental things of the call control protocols such as SIP is that it requires

the help of another protocol known as Session Description Protocol (SDP) for capability negotia-

tions between the call participants. In my earlier book on SIP, SDP has been briey described. It

has almost been an impossible task to provide the full treatment of SDP in that book.

In the meantime, there has been a profound change in the industry to make the web browser

itself for initiation, establishment, and maintenance of the real-time multimedia call directly. As

a culmination of this, Web Real-Time Control (WebRTC) has emerged as a standardized another

call control protocol developed in the IETF in collaboration with World Wide Consortium

(W2C). IETF is in charge of the development of WebRTC protocol, whereas W2C is developing

WebRTC Application Programming Interfaces (APIs).

e most interesting development is that even WebRTC call control protocol, like SIP, also

needs to use another protocol for capability negotiations between the call participants. WebRTC

working group (WG) has decided to use SDP as the protocol for capability negotiations. When

www.TechnicalBooksPDF.com

xviii ◾ Preface

WebRTC WG investigated the capabilities of existing SDP standards, they found that WebRTC

needs extensions of SDP to accommodate the full spectrum of new capabilities.

Historically, SDP was rst developed to be used for Session Announcement Protocol (SAP)

(RFC 2974) for distribution of the session information related to audio/video codecs and others to

the users who will participate in the session. SDP’s main task had been only one-way distribution

of the session capability (e.g. audio/video codec type, data applications, and/or others) informa-

tion to the participants while SIP was developed to two-way conferencing where session capability

negotiations among the conference participants on real-time, initial SDP capabilities developed

for SAP were not at all suitable. To introduce capability negotiation capabilities, at times it proved

so dicult that people became frustrated whether this SDP might have to be discarded.

Finally, the oer/answer model introduced by RFC 3264 (see Section 3.1) has been the water-

shed that rescues SDP to make a viable candidate for capability negotiations dynamically in real

time among the participants. Since then researchers and developers have been extending SDP

introducing many more capabilities as time goes by. Recently, WebRTC WG has introduced

many other capabilities in SDP.

Although SDP serving quite well for point-to-point multimedia conferencing, its protocol

architecture is such that it cannot be extended for distributed multipoint multimedia conference

as of today. e only multipoint conferencing that is oered today is the centralized star-like

topology with priori known address of the centralized controller. In centralized conference archi-

tecture is again capability negotiations are done using SDP in point-to-point fashion only. When

we work with SDP, we have to know its limitations how and where we can use SDP for setting up

the multimedia conferencing dynamically.

It has created a new urgency to publish a book on SDP providing full treatments due its own

merits. Like all other standards, we have to know exactly how many RFCs have been published

even related to the base SDP over two decades, and how they are interrelated to each other after so

many extensions and enhancements with new features and capabilities, corrections and modica-

tions with latest agreed-upon interpretations based on implementation and interoperability test

experiences, and future researches for breaking new ground knowing what already exists in SDP.

Like SIP, this book on SDP is the rst of this kind that attempts to put all SIP-related RFCs

together with their mandatory and optional texts in a chronological systematic way as if people

can use a single “super-SDP RFC” with almost one-to-one integrity from beginning to end to see

the big picture of SDP in addition to base SDP functionalities.

It should be noted that the texts of each RFC in the IETF are reviewed by all members of a

given WG throughout the world, and rough consensus is made which parts of texts of the draft

need to be “mandatory” and “optional” including whether a RFC needs to be “standards track,”

“informational,” or “experimental.” e key point is when one tries to put all SIP-related RFCs

together making a textbook has serious challenges how to put all texts together because it is not

simply to put one RFC after another one chronologically. It takes texts of each RFC needs to be

put together for each of these particular functionalities, capabilities, and features keeping integ-

rity. Since this book is planned as if it is like a single-SIP RFC, I have a very limited freedom to

change any texts of RFCs other than some editorial texts to make it look like a book. I have used

texts, gures, tables, and references from RFCs as much is necessary so that all can use all those

as they are found in RFCs. All RFCs along with their authors are provided in references, and all

credits of this book go primarily to those authors of these RFCs and many IETF WG members

who shaped nal RFCs with their invaluable comments and inputs. In this connection, I also

extend my sincere thanks to Ms. Alexa, IETF Secretariat, for his kind consent for reproducing

www.TechnicalBooksPDF.com

Preface ◾ xix

texts, gures, and tables with IETF copyright notication. My only credit, as I mentioned earlier,

is to put all those RFCs together in a way that looks like one complete SDP RFC.

I have organized this book into eighteen chapters based on their major functionalities, features,

and capabilities as follows:

1. Networked Multimedia Protocols (Sections 1–1.6)

a. Session Initiation Protocol (Sections 1.2–1.2.6)

b. WebRTC Protocol (Sections 1.3–1.3.12)

2. Basic Session Description Protocol (Sections 2–2.13)

3. Negotiations Model in SDP (Sections 3–3.5)

4. Capability Declaration in SDP (Sections 4–4.3)

5. Media-Level Attribute Support in SDP (Sections 5–5.5)

6. Semantics for Signaling Media Decoding Dependency in SDP (Sections 6–6.4)

7. Media Grouping Support in SDP (Sections 7–7.6)

8. Generic Capability Attribute Negotiations in SDP (Sections 8–8.7)

9. Network Protocol Support in SDP (Sections 9–9.8)

10. Transport Protocol Support in SDP (Sections 10–10.3)

11. RTP Media Loopback Support in SDP (Sections 11–11.3)

12. Quality-of-Service Support in SDP (Sections 12–12.7)

13. Application-Specic Extensions in SDP (Sections 13–13.4)

14. Service-Specic Extension in SDP (Sections 14–14.6)

15. Compression Support in SDP (Sections 15–15.3)

16. Security Capability Negotiation in SDP (Sections 16–16.8)

17. Security Considerations in Using SDP Attributes (Sections 17–17.16)

18. Capability Negotiations Using SDP by SIP and WebRTC (Sections 18–18.5)

Out of this, Chapter 1 deals with SIP and WebRTC call control protocol, whereas Chapter 18

provides how SDP is being used for capability negotiations using SIP and WebRTC. e reason

that I have included these two call control protocols is that SDP itself does not say anything how a

point-to-point or multipoint multimedia conferencing needs to be congured. It is the use of SDP

by call control protocols such as SIP and WebRTC how and where SDP can or cannot be used. In

this context, I strongly believe that the readers will appreciate the inclusion of SIP and WebRTC

in Chapters 1 and 18. However, this is not the only way that all of SDP RFCs to be grouped or

chapters/sections need to be put chronologically. My best intellectual instinct has guided me to

arrange these RFCs for the basic SIP functionalities like this although much more complex intel-

ligent capabilities of SDP are yet to be invented in the future. I am looking forward to the readers

whether they will validate my judgment. In addition, I am providing a general statement for the

IETF copyright information as follows:

IETF RFCs have texts that are “mandatory” and “optional” including the use of words

like “SHALL,” “MUST,” “MAY,” “SHOULD,” and “RECOMMENDED.” ese

texts are very critical for providing interoperability for implementation using products

from dierent vendors as well as for inter-carrier communications. e main objective

of this book is, as explained earlier, to create as if it is a single integrated SDP RFC,

the texts have been reproduced from the IETF RFCs for providing interoperability

www.TechnicalBooksPDF.com

剩余924页未读，继续阅读

是这个T飞

粉丝: 0
资源: 15

SIP与WebRTC协议的多媒体会话指南

ip电话.pdf

Telephony.pdf

SIP协议pdf版本

webrtc.tar.gz

webrtc的config.js

CMakeFiles/webrtc-streamer.dir/build.make:102：CMakeFiles/webrtc-streamer.dir/src/fileaudiocapturer.cpp.o] 错误 1

基于sip和webrtc的音视频通话

freepbx webrtc 分级互打

sip线路对接_FreePBX实现SIP/WebRTC和PSTN设备对接完整流程 嵌入网页

sip线路对接_FreePBX实现SIP/WebRTC和PSTN设备对接完整流程

写一个webrtc的软电话谷歌插件

目前Chrome浏览器最新版本的WebRTC支持H.265编解码吗？

vue 使用webrtc.js

webrtc c++ demo

android sip webrtc sip

如何在WebRTC中配置H.265编码?

webrtc零基础开发者教程(中文).pdf

开发一个视频会议系统

vlc可以拉webrtc的流嘛

最新资源

sip线路对接_FreePBX实现SIP/WebRTC和PSTN设备对接完整流程嵌入网页