1、 ETSI TR 183 046 V3.3.1 (2009-08)Technical Report Telecommunications and Internet converged Services andProtocols for Advanced Networking (TISPAN);SDP Interworking between Call/Session Control Protocols (SIP/SDP, RTSP/SDP; etc.) and the Gateway Control Protocol (H.248/SDP)ETSI ETSI TR 183 046 V3.3.1
2、 (2009-08) 2Reference RTR/TISPAN-03194-NGN-R3 Keywords H.248, interworking, SIP ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse
3、 (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the ref
4、erence version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or ch
5、ange of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyrig
6、ht Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2009. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and
7、 the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Or
8、ganizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TR 183 046 V3.3.1 (2009-08) 3Contents Intellectual Property Rights 5g3Foreword . 5g31 Scope 6g31.1 Applicability . 7g32 References 7g32.1 Normative references . 7g32.2 Informative refer
9、ences 7g33 Definitions and abbreviations . 9g33.1 Definitions 9g33.2 Abbreviations . 9g34 Differences between SIP/SDP and H.248/SDP Usage . 10g34.1 SIP usage of SDP . 10g34.1.1 Basic O/A Model (RFC 3264 i.4): Initial Offer/Answer Exchange . 11g34.1.1.1 Special-Use IP addresses . 12g34.1.1.1.1 Specia
10、l-Use IPv4 addresses . 12g34.1.1.1.2 Special-Use IPv6 addresses . 12g34.1.2 Basic O/A Model (RFC 3264): Subsequent Offer/Answer Exchange(s) 12g34.1.3 Bearer Termination . 12g34.1.4 SDP redundancy between session- and media-level sections . 13g34.1.5 H.248 IP Stream/Termination: Special-Use IP addres
11、ses . 13g34.1.5.1 Special-Use IPv4 addresses . 13g34.1.5.2 Special-Use IPv6 addresses . 14g34.1.6 Extended O/A Model: Initial Offer/Answer Exchange . 14g34.2 H.248 Usage of SDP 14g34.2.1 Local and Remote Descriptor . 14g34.2.2 Wildcarding of SDP fields 16g35 Summary of SDP Usage Differences and Mapp
12、ing Rules . 17g35.1 ITU-T Recommendation V.152 mapping rules 20g35.2 ITU-T Recommendation T.38 mapping rules 21g35.3 Packetization times in SDP 22g36 SDP Mapping Examples 22g36.1 SIP/SDP to H.248/SDP Example . 22g36.2 H.248/SDP to SIP/SDP Example . 24g36.2.1 General Mapping 24g36.2.2 Specific SDP Li
13、nes: Timing (“t=“ Line) . 25g36.2.3 Specific SDP Lines: Media Descriptions (“m=“ Line) . 25g36.2.3.1 SDP Offer with Zero Media Description 25g36.2.3.2 SDP Offer with Media Description(s) . 25g36.2.4 Specific SDP Lines: Origin (“o=“ Line) . 27g36.3 Network Examples . 28g36.3.1 Pure PES scenario . 28g
14、36.3.2 End-to-end Offer/Answer scenario with a RFC 3264-based SIP interface . 29g36.3.2.1 Overview . 29g36.3.2.2 Two Audio Streams. 29g36.3.2.2.1 H.248 MG does not support G.711 (as Audio Codec) . 29g36.3.2.2.2 H.248 MG does support also G.711 (as Audio Codec) . 33g36.3.3 End-to-end scenario with ES
15、 129 163 call procedures . 33g37 Mapping aspects between SDP versions 34g37.1 Introduction 34g37.2 High-level guidelines . 34g37.3 Behaviour in case of “not supported SDP elements“ 34g3ETSI ETSI TR 183 046 V3.3.1 (2009-08) 4Annex A: Special-Use IP Addresses . 35g3A.1 Special-Use IPv4 Addresses . 35g
16、3A.2 Special-Use IPv6 Addresses . 36g3Annex B: Change history 37g3History 38g3ETSI ETSI TR 183 046 V3.3.1 (2009-08) 5Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any
17、, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on
18、 the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) wh
19、ich are, or may be, or may become, essential to the present document. Foreword This Technical Report (TR) has been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). ETSI ETSI TR 183 046 V3.3.1 (2009-08) 61 Scope Th
20、e present document specifically describes the differing SDP usage between SIP i.2 and H.248 i.3 together with the implied mapping capability that is performed by the MGC/Call Server. SDP i.1 has been widely selected as the protocol of choice within VoIP (or multimedia; MMoIP) to describe the media r
21、equirements of a given session/call/connection. However, the different VoIP control protocols that utilise SDP each specify differing requirements in their use of SDP. There is therefore a need for a MGC/Call Server to arbitrate between these variations in the use of SDP and perform the interworking
22、 between them. SDP i.1 has been widely selected as the protocol of choice within VoIP (or multimedia; MMoIP) to describe the media requirements of a given session/call/connection. However, the different VoIP control protocols that utilize SDP each specify differing requirements in their use of SDP.
23、There is therefore a need for a MGC/Call Server to arbitrate between these variations in the use of SDP and perform the interworking between them. Specifically for the present document, the differing SDP usage between SIP i.2 and H.248 i.3 will be described together with the implied mapping capabili
24、ty that is performed by the MGC/Call Server. Any network element (e.g. a MGCF) which handles both H.248/SDP signalling and SIP/SDP signalling provides any necessary interworking between both signalling protocols (see figure 1). Such interworking comprises in general: interworking between SIP and H.2
25、48 signalling on message and procedural level (out of scope of the present document); and interworking between the two SDP segments (SDP-SDP interworking; the scope of the present document). The function providing SDP-to-SDP interworking between SIP/SDP and H.248/SDP signalling is, in the present do
26、cument, termed a “SDP Mapper“ (see also clause 3.1). The SDP Mapper performs SDP-SDP interworking capability to reconcile the different uses of SDP between control protocols H.248 and SIP. In order to perform this role, the SDP Mapper takes into account i) which parts of SDP are required to be sent
27、on an interface, and ii) which parts of SDP are received on an interface. For a given session/call, which use the two different control protocols at each end, some SDP parameters may be transited whilst others may not. The SDP Mapper ensures that the differing requirements with regard to SDP handlin
28、g at each end are mutually satisfied. H.248Media Gateway(MG or MGW)H.248Media Gateway Controller (MGC)Network Element handling both H.248/SDP and SIP/SDP SignallingScope ofthisTechnical ReportH.248/SDPGateway Control Protocol(text encoding mode)SIPe.g. SIP Proxy, SIP User Agent, etcSDP Mapper SIP/SD
29、PSIP-ISessionInitiation ProtocolFigure 1: Scope ETSI ETSI TR 183 046 V3.3.1 (2009-08) 71.1 Applicability This paper is applicable to any MGC/Call Server that exhibits both a SIP and H.248 interface. The former includes interfaces to both User Equipments (i.e. SIP User Agents) and peer SIP proxies (l
30、ike Call Servers). The latter includes interfaces to any H.248-controlled MGW (e.g. RMGW, AMGW, TMGW, BMGW, etc.). 2 References References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions d
31、o not apply. Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. R
32、eferenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. 2.1 Normative referenc
33、es Not applicable. 2.2 Informative references i.1 IETF RFC 4566 (2006): “SDP: Session Description Protocol“. i.2 IETF RFC 3261 (2002): “Session Initiation Protocol“. i.3 ITU-T Recommendation H.248.1 (2005): “Gateway control protocol: Version 3“. i.4 IETF RFC 3264 (2002): “An Offer/Answer Model with
34、Session Description Protocol (SDP)“. i.5 IETF RFC 3262 (2002): “Reliability of Provisional Responses in Session Initiation Protocol (SIP)“. i.6 IETF RFC 4317 (2005): “Session Description Protocol (SDP) Offer/Answer Examples“. i.7 IETF RFC 2327 (1998): “SDP: Session Description Protocol“. i.8 ITU-T R
35、ecommendation Q.1912.5 (2004): “Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control protocol or ISDN User Part“. i.9 ITU-T Recommendation Q. Supplement 45 (09/2003): Technical Report TRQ.2815: “Requirements for interworking BICC/ISUP network with originating/de
36、stination networks based on Session Initiation Protocol and Session Description Protocol“. i.10 ITU-T Recommendation T.38 (2005) “Procedures for real-time Group 3 facsimile communication over IP networks“. i.11 ITU-T Recommendation V.152 (2005): “Procedures for supporting voice-band data over IP net
37、works“. ETSI ETSI TR 183 046 V3.3.1 (2009-08) 8i.12 ITU-T Recommendation H.248.39 (2006): “Gateway control protocol: H.248 SDP parameter identification and wildcarding“. i.13 ITU-T Recommendation H.248.49 (2007): “Gateway control protocol: Session description protocol RFC and capabilities packages“.
38、 i.14 ITU-T Recommendation G.711: “Pulse code modulation (PCM) of voice frequencies“. i.15 IETF RFC 3951: “Internet Low Bit Rate Codec (iLBC)“. i.16 IETF RFC 3952: “Real-time Transport Protocol (RTP) Payload Format for internet Low Bit Rate Codec (iLBC) Speech“. i.17 ETSI ES 283 002: “Telecommunicat
39、ions and Internet converged Services and Protocols for Advanced Networking (TISPAN); H.248 Profile for controlling Access and Residential Gateways“. i.18 ETSI ES 283 024: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); H.248 Profile for controlling
40、 Trunking Media Gateways; Protocol specification“. i.19 ETSI EN 383 001: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control (BICC) Protocol or ISDN User Part (I
41、SUP) ITU-T Recommendation Q.1912.5, modified“. i.20 ETSI TR 183 014: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN Emulation; Development and Verification of PSTN/ISDN Emulation“. i.21 IETF RFC 3108: “Conventions for the use of the Sess
42、ion Description Protocol (SDP) for ATM Bearer Connections“. i.22 IETF RFC 4733: “RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals“. i.23 IETF RFC 2543: “SIP: Session Initiation Protocol“. i.24 IETF RFC 3550: “RTP: A Transport Protocol for Real-Time Applications“. i.25 IETF RFC 355
43、1: “RTP Profile for Audio and Video Conferences with Minimal Control“. i.26 ITU-T Delayed Contribution COM16-D410-E (01/2004), “Proposal to begin work on H.248.1 version 3“, (Clause 2.1.1 “SDP compatibility between H.248 and other SDP-based protocols“). i.27 IETF RFC 3330: “Special-Use IPv4 Addresse
44、s“. i.28 IETF RFC 5156: “Special-Use IPv6 Addresses“. i.29 IETF draft-ietf-mmusic-sdp-capability-negotiation: “SDP Capability Negotiation“. i.30 IETF draft-ietf-mmusic-sdp-media-capabilities: “SDP Media Capability Negotiation“. i.31 3GPP TS 29.802: “(G)MSC-S - (G)MSC-S Nc Interface based on the SIP-
45、I protocol“. i.32 IETF RFC 4291: “IP Version 6 Addressing Architecture“. i.33 IETF RFC 4293: “Management Information Base for the Internet Protocol (IP)“. i.34 IETF RFC 3849: “IPv6 Address Prefix Reserved for Documentation“. i.35 IETF RFC 3056: “Connection of IPv6 Domains via IPv4 Clouds“. i.36 IETF
46、 RFC 4380: “Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)“. i.37 IETF RFC 1897: “IPv6 Testing Address Allocation“. ETSI ETSI TR 183 046 V3.3.1 (2009-08) 9i.38 IETF RFC 3701: “6bone (IPv6 Testing Address Allocation) Phaseout“. i.39 IETF RFC 4843: “An IPv6 Prefix for Over
47、lay Routable Cryptographic Hash Identifiers (ORCHID)“. i.40 IETF RFC 4773: “Administration of the IANA Special Purpose IPv6 Address Block“. i.41 IETF RFC 3232: “Assigned Numbers: RFC 1700 is Replaced by an On-line Database“. i.42 IETF RFC 1918: “Address Allocation for Private Internets“. i.43 IETF R
48、FC 1797: “Class A Subnet Experiment“. i.44 IETF RFC 3068: “An Anycast Prefix for 6to4 Relay Routers“. i.45 IETF RFC 3171: “IANA Guidelines for IPv4 Multicast Address Assignments“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and defini
49、tions apply: SDP Mapper: function for SDP-to-SDP interworking between two different, SDP-using signalling protocols NOTE: One of these signalling protocols is the Gateway Control Protocol according H.248 in text-encoding mode. The other signalling protocol is SIP in the scope of the present document. SIP-I: use of SIP with a message body that encapsulates ISUP information NOTE: Definition according to ITU-T Recommendation Q.1912.5 i.8 and clause 4.8 in ITU-T Sup
