| 1 |
<pre>Internet Engineering Task Force (IETF) D. Worley |
| 2 |
Request for Comments: 7088 Ariadne |
| 3 |
Category: Informational February 2014 |
| 4 |
ISSN: 2070-1721 |
| 5 |
|
| 6 |
|
| 7 |
<span class="h1">Session Initiation Protocol Service Example -- Music on Hold</span> |
| 8 |
|
| 9 |
Abstract |
| 10 |
|
| 11 |
"Music on hold" is one of the features of telephone systems that is |
| 12 |
most desired by buyers of business telephone systems. Music on hold |
| 13 |
means that when one party to a call has the call "on hold", that |
| 14 |
party's telephone provides an audio stream (often music) to be heard |
| 15 |
by the other party. Architectural features of SIP make it difficult |
| 16 |
to implement music on hold in a way that is fully standards- |
| 17 |
compliant. The implementation of music on hold described in this |
| 18 |
document is fully effective, is standards-compliant, and has a number |
| 19 |
of advantages over the methods previously documented. In particular, |
| 20 |
it is less likely to produce peculiar user interface effects and more |
| 21 |
likely to work in systems that perform authentication than the music- |
| 22 |
on-hold method described in <a href="./rfc5359#section-2.3">Section 2.3 of RFC 5359</a>. |
| 23 |
|
| 24 |
Status of This Memo |
| 25 |
|
| 26 |
This document is not an Internet Standards Track specification; it is |
| 27 |
published for informational purposes. |
| 28 |
|
| 29 |
This document is a product of the Internet Engineering Task Force |
| 30 |
(IETF). It represents the consensus of the IETF community. It has |
| 31 |
received public review and has been approved for publication by the |
| 32 |
Internet Engineering Steering Group (IESG). Not all documents |
| 33 |
approved by the IESG are a candidate for any level of Internet |
| 34 |
Standard; see <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 35 |
|
| 36 |
Information about the current status of this document, any errata, |
| 37 |
and how to provide feedback on it may be obtained at |
| 38 |
<a href="http://www.rfc-editor.org/info/rfc7088">http://www.rfc-editor.org/info/rfc7088</a>. |
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Worley Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 55 |
|
| 56 |
|
| 57 |
Copyright Notice |
| 58 |
|
| 59 |
Copyright (c) 2014 IETF Trust and the persons identified as the |
| 60 |
document authors. All rights reserved. |
| 61 |
|
| 62 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 63 |
Provisions Relating to IETF Documents |
| 64 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 65 |
publication of this document. Please review these documents |
| 66 |
carefully, as they describe your rights and restrictions with respect |
| 67 |
to this document. Code Components extracted from this document must |
| 68 |
include Simplified BSD License text as described in Section 4.e of |
| 69 |
the Trust Legal Provisions and are provided without warranty as |
| 70 |
described in the Simplified BSD License. |
| 71 |
|
| 72 |
|
| 73 |
|
| 74 |
|
| 75 |
|
| 76 |
|
| 77 |
|
| 78 |
|
| 79 |
|
| 80 |
|
| 81 |
|
| 82 |
|
| 83 |
|
| 84 |
|
| 85 |
|
| 86 |
|
| 87 |
|
| 88 |
|
| 89 |
|
| 90 |
|
| 91 |
|
| 92 |
|
| 93 |
|
| 94 |
|
| 95 |
|
| 96 |
|
| 97 |
|
| 98 |
|
| 99 |
|
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Worley Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 111 |
|
| 112 |
|
| 113 |
Table of Contents |
| 114 |
|
| 115 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-4">4</a> |
| 116 |
<a href="#section-1.1">1.1</a>. Requirements Language ......................................<a href="#page-4">4</a> |
| 117 |
<a href="#section-2">2</a>. Technique .......................................................<a href="#page-4">4</a> |
| 118 |
2.1. Placing a Call on Hold and Establishing an External |
| 119 |
Media Stream ...............................................<a href="#page-5">5</a> |
| 120 |
2.2. Taking a Call off Hold and Terminating the External |
| 121 |
Media Stream ...............................................<a href="#page-6">6</a> |
| 122 |
<a href="#section-2.3">2.3</a>. Example Message Flow .......................................<a href="#page-6">6</a> |
| 123 |
<a href="#section-2.4">2.4</a>. Receiving Re-INVITE and UPDATE from the Remote UA .........<a href="#page-17">17</a> |
| 124 |
<a href="#section-2.5">2.5</a>. Receiving INVITE with Replaces ............................<a href="#page-17">17</a> |
| 125 |
<a href="#section-2.6">2.6</a>. Receiving REFER from the Remote UA ........................<a href="#page-19">19</a> |
| 126 |
2.7. Receiving Re-INVITE and UPDATE from the |
| 127 |
Music-on-Hold Source ......................................<a href="#page-21">21</a> |
| 128 |
<a href="#section-2.8">2.8</a>. Handling Payload Type Numbers .............................<a href="#page-22">22</a> |
| 129 |
<a href="#section-2.8.1">2.8.1</a>. Analysis ...........................................<a href="#page-22">22</a> |
| 130 |
<a href="#section-2.8.2">2.8.2</a>. Solution to the Problem ............................<a href="#page-23">23</a> |
| 131 |
<a href="#section-2.8.3">2.8.3</a>. Example of the Solution ............................<a href="#page-24">24</a> |
| 132 |
<a href="#section-2.9">2.9</a>. Dialog/Session Timers .....................................<a href="#page-28">28</a> |
| 133 |
<a href="#section-2.10">2.10</a>. When the Media Stream Directionality is "inactive" .......<a href="#page-28">28</a> |
| 134 |
<a href="#section-2.11">2.11</a>. Multiple Media Streams ...................................<a href="#page-28">28</a> |
| 135 |
<a href="#section-3">3</a>. Advantages .....................................................<a href="#page-29">29</a> |
| 136 |
<a href="#section-4">4</a>. Caveats ........................................................<a href="#page-30">30</a> |
| 137 |
<a href="#section-4.1">4.1</a>. Offering All Available Media Formats ......................<a href="#page-30">30</a> |
| 138 |
<a href="#section-4.2">4.2</a>. Handling Re-INVITES in a B2BUA ............................<a href="#page-31">31</a> |
| 139 |
<a href="#section-5">5</a>. Security Considerations ........................................<a href="#page-31">31</a> |
| 140 |
<a href="#section-5.1">5.1</a>. Network Security ..........................................<a href="#page-31">31</a> |
| 141 |
<a href="#section-5.2">5.2</a>. SIP (Signaling) Security ..................................<a href="#page-32">32</a> |
| 142 |
<a href="#section-5.3">5.3</a>. RTP (Media) Security ......................................<a href="#page-32">32</a> |
| 143 |
<a href="#section-5.4">5.4</a>. Media Filtering ...........................................<a href="#page-32">32</a> |
| 144 |
<a href="#section-6">6</a>. Acknowledgments ................................................<a href="#page-33">33</a> |
| 145 |
<a href="#section-7">7</a>. References .....................................................<a href="#page-34">34</a> |
| 146 |
<a href="#section-7.1">7.1</a>. Normative References ......................................<a href="#page-34">34</a> |
| 147 |
<a href="#section-7.2">7.2</a>. Informative References ....................................<a href="#page-34">34</a> |
| 148 |
|
| 149 |
|
| 150 |
|
| 151 |
|
| 152 |
|
| 153 |
|
| 154 |
|
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Worley Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 170 |
|
| 171 |
Within systems based on SIP [<a href="./rfc3261" title=""SIP: Session Initiation Protocol"">RFC3261</a>], it is desirable to be able to |
| 172 |
provide features that are similar to those provided by traditional |
| 173 |
telephony systems. A frequently requested feature is "music on |
| 174 |
hold": with this feature, when one party to a call has the call "on |
| 175 |
hold", that party's telephone provides an audio stream (often music) |
| 176 |
to be heard by the other party. |
| 177 |
|
| 178 |
Architectural features of SIP make it difficult to implement music on |
| 179 |
hold in a way that is fully standards-compliant. The purpose of this |
| 180 |
document is to describe a method that is reasonably simple yet fully |
| 181 |
effective and standards-compliant. This method has significant |
| 182 |
advantages over other methods now in use, as described in <a href="#section-3">Section 3</a>. |
| 183 |
|
| 184 |
All current methods of implementing music on hold interoperate with |
| 185 |
each other, in that the two user agents in a call can use different |
| 186 |
methods for implementing music on hold with the same functionality as |
| 187 |
if either of the methods was used by both user agents. Thus, there |
| 188 |
is no loss of functionality if different music-on-hold methods are |
| 189 |
used by different user agents within a telephone system or if a |
| 190 |
single user agent uses different methods within different calls or at |
| 191 |
different times within one call. |
| 192 |
|
| 193 |
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Requirements Language</span> |
| 194 |
|
| 195 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 196 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 197 |
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 198 |
|
| 199 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Technique</span> |
| 200 |
|
| 201 |
The essence of the technique is that when the executing user agent |
| 202 |
(UA) (the user's UA) performs a re-INVITE of the remote UA (the other |
| 203 |
user's UA) to establish the hold state, it provides no Session |
| 204 |
Description Protocol (SDP) [<a href="./rfc4566" title=""SDP: Session Description Protocol"">RFC4566</a>] offer [<a href="./rfc3264" title=""An Offer/Answer Model with Session Description Protocol (SDP)"">RFC3264</a>] [<a href="./rfc6337" title=""Session Initiation Protocol (SIP) Usage of the Offer/Answer Model"">RFC6337</a>], thus |
| 205 |
compelling the remote UA to provide an SDP offer. The executing UA |
| 206 |
then extracts the offer SDP from the remote UA's 2xx response and |
| 207 |
uses that as the offer SDP in a new INVITE to the external media |
| 208 |
source. The external media source is thus directed to provide media |
| 209 |
directly to the remote UA. The media source's answer SDP is returned |
| 210 |
to the remote UA in the ACK to the re-INVITE. |
| 211 |
|
| 212 |
|
| 213 |
|
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Worley Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 223 |
|
| 224 |
|
| 225 |
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Placing a Call on Hold and Establishing an External Media Stream</span> |
| 226 |
|
| 227 |
1. The executing user instructs the executing UA to put the dialog |
| 228 |
on hold. |
| 229 |
|
| 230 |
2. The executing UA sends a re-INVITE without SDP to the remote UA, |
| 231 |
which forces the remote UA to provide an SDP offer in its 2xx |
| 232 |
response. The Contact header of the re-INVITE includes the |
| 233 |
'+sip.rendering="no"' field parameter to indicate that it is |
| 234 |
putting the call on hold (<a href="./rfc4235#section-5.2">[RFC4235], Section 5.2</a>). |
| 235 |
|
| 236 |
3. The remote UA sends a 2xx to the re-INVITE and includes an SDP |
| 237 |
offer giving its own listening address/port. If the remote UA |
| 238 |
understands the sip.rendering feature parameter, the offer may |
| 239 |
indicate that it will not send media by specifying the media |
| 240 |
directionalities as "recvonly" (the reverse of "on hold") or |
| 241 |
"inactive". But the remote UA may offer to send media. |
| 242 |
|
| 243 |
4. The executing UA uses this offer to derive the offer SDP of an |
| 244 |
initial INVITE that it sends to the configured music-on-hold |
| 245 |
(MOH) source. The SDP in this request is largely copied from the |
| 246 |
SDP returned by the remote UA in the previous step, particularly |
| 247 |
regarding the provided listening address/port and payload type |
| 248 |
numbers. But the media directionalities are restricted to |
| 249 |
"recvonly" or "inactive" as appropriate. The executing UA may |
| 250 |
want or need to change the "o=" line. In addition, some |
| 251 |
"a=rtpmap" lines may need to be added to control the assignment |
| 252 |
of RTP payload type numbers (<a href="#section-2.8">Section 2.8</a>). |
| 253 |
|
| 254 |
5. The MOH source sends a 2xx response to the INVITE, which contains |
| 255 |
an SDP answer that should include its media source address as its |
| 256 |
listening address/port. This SDP must necessarily specify |
| 257 |
"sendonly" or "inactive" as the directionality for all media |
| 258 |
streams [<a href="./rfc3264" title=""An Offer/Answer Model with Session Description Protocol (SDP)"">RFC3264</a>]. |
| 259 |
|
| 260 |
Although this address/port should receive no RTP, the specified |
| 261 |
port determines the port for receiving the RTP Control Protocol |
| 262 |
(RTCP) (and conventionally, for sending RTCP [<a href="./rfc4961" title=""Symmetric RTP / RTP Control Protocol (RTCP)"">RFC4961</a>]). |
| 263 |
|
| 264 |
By convention, UAs use their declared RTP listening ports as |
| 265 |
their RTP source ports as well [<a href="./rfc4961" title=""Symmetric RTP / RTP Control Protocol (RTCP)"">RFC4961</a>]. The answer SDP will |
| 266 |
reach the remote UA, thus informing it of the address/port from |
| 267 |
which the MOH media will come and presumably preventing the |
| 268 |
remote UA from ignoring the MOH media if the remote UA filters |
| 269 |
media packets based on the source address. This functionality |
| 270 |
requires the SDP answer to contain the sending address in the |
| 271 |
"c=" line, even though the MOH source does not receive RTP. |
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Worley Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 279 |
|
| 280 |
|
| 281 |
6. The executing UA sends this SDP answer as its SDP answer in the |
| 282 |
ACK for the re-INVITE to the remote UA. The "o=" line in the |
| 283 |
answer must be modified to be within the sequence of "o=" lines |
| 284 |
previously generated by the executing UA in the dialog. Any |
| 285 |
dynamic payload type number assignments that have been created in |
| 286 |
the answer must be recorded in the state of the original dialog. |
| 287 |
|
| 288 |
7. Due to the sip.rendering feature parameter in the Contact header |
| 289 |
of the re-INVITE and the media directionality in the SDP answer |
| 290 |
contained in the ACK, the on-hold state of the dialog is |
| 291 |
established (at the executing end). |
| 292 |
|
| 293 |
8. After this point, the MOH source generates RTP containing the |
| 294 |
music-on-hold media and sends it directly to the listening |
| 295 |
address/port of the remote UA. The executing UA maintains two |
| 296 |
dialogs (one to the remote UA, one to the MOH source) but does |
| 297 |
not see or handle the MOH RTP. |
| 298 |
|
| 299 |
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Taking a Call off Hold and Terminating the External Media Stream</span> |
| 300 |
|
| 301 |
1. The executing user instructs the executing UA to take the dialog |
| 302 |
off hold. |
| 303 |
|
| 304 |
2. The executing UA sends a re-INVITE to the remote UA with SDP that |
| 305 |
requests to receive media. The Contact header of the re-INVITE |
| 306 |
does not include the '+sip.rendering="no"' field parameter. (It |
| 307 |
may contain a sip.rendering field parameter with value "yes" or |
| 308 |
"unknown", or it may omit the field parameter.) Thus, this |
| 309 |
re-INVITE removes the on-hold state of the dialog (at the |
| 310 |
executing end). (Note that the version in "o=" line of the |
| 311 |
offered SDP must account for the SDP versions that were passed |
| 312 |
through from the MOH source. Also note that any payload type |
| 313 |
numbers that were assigned in SDP provided by the MOH source must |
| 314 |
be respected.) |
| 315 |
|
| 316 |
3. When the remote UA sends a 2xx response to the re-INVITE, the |
| 317 |
executing UA sends a BYE request in the dialog to the MOH source. |
| 318 |
|
| 319 |
4. After this point, the MOH source does not generate RTP and |
| 320 |
ordinary RTP flow is reestablished in the original dialog. |
| 321 |
|
| 322 |
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Example Message Flow</span> |
| 323 |
|
| 324 |
This section shows a message flow that is an example of this |
| 325 |
technique. The scenario is as follows. Alice establishes a call |
| 326 |
with Bob. Bob then places the call on hold, with music on hold |
| 327 |
provided from an external source. Bob then takes the call off hold. |
| 328 |
In this scenario, Bob's user agent is the executing UA, while Alice's |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Worley Informational [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 335 |
|
| 336 |
|
| 337 |
UA is the remote UA. Note that this is just one possible message |
| 338 |
flow that illustrates this technique; numerous variations on these |
| 339 |
operations are allowed by the applicable standards. |
| 340 |
|
| 341 |
Alice Bob Music Source |
| 342 |
|
| 343 |
Alice establishes the call: |
| 344 |
|
| 345 |
| | | |
| 346 |
| INVITE F1 | | |
| 347 |
|--------------->| | |
| 348 |
| 180 Ringing F2 | | |
| 349 |
|<---------------| | |
| 350 |
| 200 OK F3 | | |
| 351 |
|<---------------| | |
| 352 |
| ACK F4 | | |
| 353 |
|--------------->| | |
| 354 |
| RTP | | |
| 355 |
|<==============>| | |
| 356 |
| | | |
| 357 |
|
| 358 |
Bob places Alice on hold, compelling Alice's UA to provide SDP: |
| 359 |
|
| 360 |
| | | |
| 361 |
| INVITE F5 | | |
| 362 |
| (no SDP) | | |
| 363 |
|<---------------| | |
| 364 |
| 200 OK F6 | | |
| 365 |
| (SDP offer) | | |
| 366 |
|--------------->| | |
| 367 |
| | | |
| 368 |
|
| 369 |
Bob's UA initiates music on hold: |
| 370 |
|
| 371 |
| | | |
| 372 |
| | INVITE F7 | |
| 373 |
| | (SDP offer, | |
| 374 |
| | rev. hold) | |
| 375 |
| |------------->| |
| 376 |
| | 200 OK F8 | |
| 377 |
| | (SDP answer, | |
| 378 |
| | hold) | |
| 379 |
| |<-------------| |
| 380 |
| | ACK F9 | |
| 381 |
| |------------->| |
| 382 |
| | | |
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Worley Informational [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 391 |
|
| 392 |
|
| 393 |
Bob's UA provides an SDP answer containing the address/port |
| 394 |
of Music Source: |
| 395 |
|
| 396 |
| | | |
| 397 |
| ACK F10 | | |
| 398 |
| (SDP answer, | | |
| 399 |
| hold) | | |
| 400 |
|<---------------| | |
| 401 |
| no RTP | | |
| 402 |
|<..............>| | |
| 403 |
| Music-on-hold RTP | |
| 404 |
|<==============================| |
| 405 |
| | | |
| 406 |
|
| 407 |
The music on hold is active. |
| 408 |
|
| 409 |
Bob takes Alice off hold: |
| 410 |
|
| 411 |
| | | |
| 412 |
| INVITE F11 | | |
| 413 |
| (SDP offer) | | |
| 414 |
|<---------------| | |
| 415 |
| 200 OK F12 | | |
| 416 |
| (SDP answer) | | |
| 417 |
|--------------->| | |
| 418 |
| ACK F13 | | |
| 419 |
|<---------------| | |
| 420 |
| | BYE F14 | |
| 421 |
| |------------->| |
| 422 |
| | 200 F15 | |
| 423 |
| |<-------------| |
| 424 |
| RTP | | |
| 425 |
|<==============>| | |
| 426 |
| | | |
| 427 |
|
| 428 |
The normal media session between Alice and Bob is resumed. |
| 429 |
|
| 430 |
|
| 431 |
|
| 432 |
|
| 433 |
|
| 434 |
|
| 435 |
|
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Worley Informational [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 447 |
|
| 448 |
|
| 449 |
/* Alice calls Bob. */ |
| 450 |
|
| 451 |
F1 INVITE Alice -> Bob |
| 452 |
|
| 453 |
INVITE sips:[email protected] SIP/2.0 |
| 454 |
Via: SIP/2.0/TLS atlanta.example.com:5061 |
| 455 |
;branch=z9hG4bK74bf9 |
| 456 |
Max-Forwards: 70 |
| 457 |
From: Alice <sips:[email protected]>;tag=1234567 |
| 458 |
To: Bob <sips:[email protected]> |
| 459 |
Call-ID: [email protected] |
| 460 |
CSeq: 1 INVITE |
| 461 |
Contact: <sips:[email protected];gr> |
| 462 |
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY |
| 463 |
Supported: replaces, gruu |
| 464 |
Content-Type: application/sdp |
| 465 |
Content-Length: [omitted] |
| 466 |
|
| 467 |
v=0 |
| 468 |
o=alice 2890844526 2890844526 IN IP4 atlanta.example.com |
| 469 |
s= |
| 470 |
c=IN IP4 atlanta.example.com |
| 471 |
t=0 0 |
| 472 |
m=audio 49170 RTP/AVP 0 |
| 473 |
a=rtpmap:0 PCMU/8000 |
| 474 |
|
| 475 |
F2 180 Ringing Bob -> Alice |
| 476 |
|
| 477 |
SIP/2.0 180 Ringing |
| 478 |
Via: SIP/2.0/TLS atlanta.example.com:5061 |
| 479 |
;branch=z9hG4bK74bf9 |
| 480 |
;received=192.0.2.103 |
| 481 |
From: Alice <sips:[email protected]>;tag=1234567 |
| 482 |
To: Bob <sips:[email protected]>;tag=23431 |
| 483 |
Call-ID: [email protected] |
| 484 |
CSeq: 1 INVITE |
| 485 |
Contact: <sips:[email protected]> |
| 486 |
Content-Length: 0 |
| 487 |
|
| 488 |
|
| 489 |
|
| 490 |
|
| 491 |
|
| 492 |
|
| 493 |
|
| 494 |
|
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Worley Informational [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 503 |
|
| 504 |
|
| 505 |
F3 200 OK Bob -> Alice |
| 506 |
|
| 507 |
SIP/2.0 200 OK |
| 508 |
Via: SIP/2.0/TLS atlanta.example.com:5061 |
| 509 |
;branch=z9hG4bK74bf9 |
| 510 |
;received=192.0.2.103 |
| 511 |
From: Alice <sips:[email protected]>;tag=1234567 |
| 512 |
To: Bob <sips:[email protected]>;tag=23431 |
| 513 |
Call-ID: [email protected] |
| 514 |
CSeq: 1 INVITE |
| 515 |
Contact: <sips:[email protected]> |
| 516 |
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY |
| 517 |
Supported: replaces |
| 518 |
Content-Type: application/sdp |
| 519 |
Content-Length: [omitted] |
| 520 |
|
| 521 |
v=0 |
| 522 |
o=bob 2890844527 2890844527 IN IP4 biloxi.example.com |
| 523 |
s= |
| 524 |
c=IN IP4 biloxi.example.com |
| 525 |
t=0 0 |
| 526 |
m=audio 3456 RTP/AVP 0 |
| 527 |
a=rtpmap:0 PCMU/8000 |
| 528 |
|
| 529 |
|
| 530 |
F4 ACK Alice -> Bob |
| 531 |
|
| 532 |
ACK sips:[email protected] SIP/2.0 |
| 533 |
Via: SIP/2.0/TLS atlanta.example.com:5061 |
| 534 |
;branch=z9hG4bK74bfd |
| 535 |
Max-Forwards: 70 |
| 536 |
From: Alice <sips:[email protected]>;tag=1234567 |
| 537 |
To: Bob <sips:[email protected]>;tag=23431 |
| 538 |
Call-ID: [email protected] |
| 539 |
CSeq: 1 ACK |
| 540 |
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY |
| 541 |
Supported: replaces |
| 542 |
Content-Length: 0 |
| 543 |
|
| 544 |
|
| 545 |
|
| 546 |
|
| 547 |
|
| 548 |
|
| 549 |
|
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Worley Informational [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 559 |
|
| 560 |
|
| 561 |
/* Bob places Alice on hold. */ |
| 562 |
|
| 563 |
/* The re-INVITE contains no SDP, thus compelling Alice's UA |
| 564 |
to provide an offer. */ |
| 565 |
|
| 566 |
F5 INVITE Bob -> Alice |
| 567 |
|
| 568 |
INVITE sips:[email protected];gr SIP/2.0 |
| 569 |
Via: SIP/2.0/TLS biloxi.example.com:5061 |
| 570 |
;branch=z9hG4bK874bk |
| 571 |
To: Alice <sips:[email protected]>;tag=1234567 |
| 572 |
From: Bob <sips:[email protected]>;tag=23431 |
| 573 |
Call-ID: [email protected] |
| 574 |
CSeq: 712 INVITE |
| 575 |
Contact: <sips:[email protected]>;+sip.rendering="no" |
| 576 |
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY |
| 577 |
Supported: replaces |
| 578 |
Content-Length: 0 |
| 579 |
|
| 580 |
/* Alice's UA provides an SDP offer. |
| 581 |
Since it does not know that it is being put on hold, |
| 582 |
the offer is the same as the original offer and describes |
| 583 |
bidirectional media. */ |
| 584 |
|
| 585 |
F6 200 OK Alice -> Bob |
| 586 |
|
| 587 |
SIP/2.0 200 OK |
| 588 |
Via: SIP/2.0/TLS biloxi.example.com:5061 |
| 589 |
;branch=z9hG4bK874bk |
| 590 |
;received=192.0.2.105 |
| 591 |
To: Alice <sips:[email protected]>;tag=1234567 |
| 592 |
From: Bob <sips:[email protected]>;tag=23431 |
| 593 |
Call-ID: [email protected] |
| 594 |
CSeq: 712 INVITE |
| 595 |
Contact: <sips:[email protected];gr> |
| 596 |
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY |
| 597 |
Supported: replaces, gruu |
| 598 |
Content-Type: application/sdp |
| 599 |
Content-Length: [omitted] |
| 600 |
|
| 601 |
v=0 |
| 602 |
o=alice 2890844526 2890844526 IN IP4 atlanta.example.com |
| 603 |
s= |
| 604 |
c=IN IP4 atlanta.example.com |
| 605 |
t=0 0 |
| 606 |
m=audio 49170 RTP/AVP 0 |
| 607 |
a=rtpmap:0 PCMU/8000 |
| 608 |
a=active |
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Worley Informational [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 615 |
|
| 616 |
|
| 617 |
/* Bob's UA initiates music on hold. */ |
| 618 |
|
| 619 |
/* This INVITE contains Alice's offer, but with the media |
| 620 |
direction set to "reverse hold", receive-only. */ |
| 621 |
|
| 622 |
F7 INVITE Bob -> Music Source |
| 623 |
|
| 624 |
INVITE sips:[email protected] SIP/2.0 |
| 625 |
Via: SIP/2.0/TLS biloxi.example.com:5061 |
| 626 |
;branch=z9hG4bKnashds9 |
| 627 |
Max-Forwards: 70 |
| 628 |
From: Bob <sips:[email protected]>;tag=02134 |
| 629 |
To: Music Source <sips:[email protected]> |
| 630 |
Call-ID: [email protected] |
| 631 |
CSeq: 1 INVITE |
| 632 |
Contact: <sips:[email protected]> |
| 633 |
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY |
| 634 |
Supported: replaces, gruu |
| 635 |
Content-Type: application/sdp |
| 636 |
Content-Length: [omitted] |
| 637 |
|
| 638 |
v=0 |
| 639 |
o=bob 2890844534 2890844534 IN IP4 atlanta.example.com |
| 640 |
s= |
| 641 |
c=IN IP4 atlanta.example.com |
| 642 |
t=0 0 |
| 643 |
m=audio 49170 RTP/AVP 0 |
| 644 |
a=rtpmap:0 PCMU/8000 |
| 645 |
a=recvonly |
| 646 |
|
| 647 |
|
| 648 |
|
| 649 |
|
| 650 |
|
| 651 |
|
| 652 |
|
| 653 |
|
| 654 |
|
| 655 |
|
| 656 |
|
| 657 |
|
| 658 |
|
| 659 |
|
| 660 |
|
| 661 |
|
| 662 |
|
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Worley Informational [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 671 |
|
| 672 |
|
| 673 |
F8 200 OK Music Source -> Bob |
| 674 |
|
| 675 |
SIP/2.0 200 OK |
| 676 |
Via: SIP/2.0/TLS biloxi.example.com:5061 |
| 677 |
;branch=z9hG4bKnashds9 |
| 678 |
;received=192.0.2.105 |
| 679 |
From: Bob <sips:[email protected]>;tag=02134 |
| 680 |
To: Music Source <sips:[email protected]>;tag=56323 |
| 681 |
Call-ID: [email protected] |
| 682 |
Contact: <sips:[email protected]>;automaton |
| 683 |
;+sip.byeless;+sip.rendering="no" |
| 684 |
CSeq: 1 INVITE |
| 685 |
Content-Length: [omitted] |
| 686 |
|
| 687 |
v=0 |
| 688 |
o=MusicSource 2890844576 2890844576 IN IP4 source.example.com |
| 689 |
s= |
| 690 |
c=IN IP4 source.example.com |
| 691 |
t=0 0 |
| 692 |
m=audio 49170 RTP/AVP 0 |
| 693 |
a=rtpmap:0 PCMU/8000 |
| 694 |
a=sendonly |
| 695 |
|
| 696 |
|
| 697 |
F9 ACK Bob -> Music Source |
| 698 |
|
| 699 |
ACK sips:[email protected] SIP/2.0 |
| 700 |
Via: SIP/2.0/TLS source.example.com:5061 |
| 701 |
;branch=z9hG4bK74bT6 |
| 702 |
From: Bob <sips:[email protected]>;tag=02134 |
| 703 |
To: Music Source <sips:[email protected]>;tag=56323 |
| 704 |
Max-Forwards: 70 |
| 705 |
Call-ID: [email protected] |
| 706 |
CSeq: 1 ACK |
| 707 |
Content-Length: 0 |
| 708 |
|
| 709 |
|
| 710 |
/* Bob's UA now sends the ACK that completes the re-INVITE |
| 711 |
to Alice and completes the SDP offer/answer. |
| 712 |
The ACK contains the SDP received from Music Source and thus |
| 713 |
contains the address/port from which Music Source will send media, |
| 714 |
and implies the address/port that Music |
| 715 |
Source will use to send/receive RTCP. */ |
| 716 |
|
| 717 |
|
| 718 |
|
| 719 |
|
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Worley Informational [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 727 |
|
| 728 |
|
| 729 |
F10 ACK Bob -> Alice |
| 730 |
|
| 731 |
ACK sips:[email protected];gr SIP/2.0 |
| 732 |
Via: SIP/2.0/TLS biloxi.example.com:5061 |
| 733 |
;branch=z9hG4bKq874b |
| 734 |
To: Alice <sips:[email protected]>;tag=1234567 |
| 735 |
From: Bob <sips:[email protected]>;tag=23431 |
| 736 |
Call-ID: [email protected] |
| 737 |
CSeq: 712 ACK |
| 738 |
Contact: <sips:[email protected]>;+sip.rendering="no" |
| 739 |
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY |
| 740 |
Supported: replaces |
| 741 |
Content-Length: [omitted] |
| 742 |
|
| 743 |
v=0 |
| 744 |
o=bob 2890844527 2890844528 IN IP4 biloxi.example.com |
| 745 |
s= |
| 746 |
c=IN IP4 source.example.com |
| 747 |
t=0 0 |
| 748 |
m=audio 49170 RTP/AVP 0 |
| 749 |
a=rtpmap:0 PCMU/8000 |
| 750 |
a=sendonly |
| 751 |
|
| 752 |
/* Bob picks up the call by sending a re-INVITE to Alice. */ |
| 753 |
|
| 754 |
|
| 755 |
F11 INVITE Bob -> Alice |
| 756 |
|
| 757 |
INVITE sips:[email protected];gr SIP/2.0 |
| 758 |
Via: SIP/2.0/TLS biloxi.example.com:5061 |
| 759 |
;branch=z9hG4bK874bk |
| 760 |
To: Alice <sips:[email protected]>;tag=1234567 |
| 761 |
From: Bob <sips:[email protected]>;tag=23431 |
| 762 |
Call-ID: [email protected] |
| 763 |
CSeq: 713 INVITE |
| 764 |
Contact: <sips:[email protected]> |
| 765 |
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY |
| 766 |
Supported: replaces |
| 767 |
Content-Type: application/sdp |
| 768 |
Content-Length: [omitted] |
| 769 |
|
| 770 |
v=0 |
| 771 |
o=bob 2890844527 2890844529 IN IP4 biloxi.example.com |
| 772 |
s= |
| 773 |
c=IN IP4 biloxi.example.com |
| 774 |
t=0 0 |
| 775 |
m=audio 3456 RTP/AVP 0 |
| 776 |
a=rtpmap:0 PCMU/8000 |
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Worley Informational [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 783 |
|
| 784 |
|
| 785 |
F12 200 OK Alice -> Bob |
| 786 |
|
| 787 |
SIP/2.0 200 OK |
| 788 |
Via: SIP/2.0/TLS biloxi.example.com:5061 |
| 789 |
;branch=z9hG4bK874bk |
| 790 |
;received=192.0.2.105 |
| 791 |
To: Alice <sips:[email protected]>;tag=1234567 |
| 792 |
From: Bob <sips:[email protected]>;tag=23431 |
| 793 |
Call-ID: [email protected] |
| 794 |
CSeq: 713 INVITE |
| 795 |
Contact: <sips:[email protected];gr> |
| 796 |
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY |
| 797 |
Supported: replaces, gruu |
| 798 |
Content-Type: application/sdp |
| 799 |
Content-Length: [omitted] |
| 800 |
|
| 801 |
v=0 |
| 802 |
o=alice 2890844526 2890844527 IN IP4 atlanta.example.com |
| 803 |
s= |
| 804 |
c=IN IP4 atlanta.example.com |
| 805 |
t=0 0 |
| 806 |
m=audio 49170 RTP/AVP 0 |
| 807 |
a=rtpmap:0 PCMU/8000 |
| 808 |
|
| 809 |
|
| 810 |
F13 ACK Bob -> Alice |
| 811 |
|
| 812 |
ACK sips:[email protected];gr SIP/2.0 |
| 813 |
Via: SIP/2.0/TLS biloxi.example.com:5061 |
| 814 |
;branch=z9hG4bKq874b |
| 815 |
To: Alice <sips:[email protected]>;tag=1234567 |
| 816 |
From: Bob <sips:[email protected]>;tag=23431 |
| 817 |
Call-ID: [email protected] |
| 818 |
CSeq: 713 ACK |
| 819 |
Contact: <sips:[email protected]> |
| 820 |
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY |
| 821 |
Supported: replaces |
| 822 |
Content-Length: 0 |
| 823 |
|
| 824 |
|
| 825 |
|
| 826 |
|
| 827 |
|
| 828 |
|
| 829 |
|
| 830 |
|
| 831 |
|
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Worley Informational [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 839 |
|
| 840 |
|
| 841 |
F14 BYE Bob -> Music Source |
| 842 |
|
| 843 |
BYE sips:[email protected] SIP/2.0 |
| 844 |
Via: SIP/2.0/TLS biloxi.example.com:5061 |
| 845 |
;branch=z9hG4bK74rf |
| 846 |
Max-Forwards: 70 |
| 847 |
From: Bob <sips:[email protected]>;tag=02134 |
| 848 |
To: Music Source <sips:[email protected]>;tag=56323 |
| 849 |
Call-ID: [email protected] |
| 850 |
CSeq: 2 BYE |
| 851 |
Contact: <sips:[email protected]> |
| 852 |
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY |
| 853 |
Supported: replaces, gruu |
| 854 |
Content-Length: [omitted] |
| 855 |
|
| 856 |
|
| 857 |
F15 200 OK Music Source -> Bob |
| 858 |
|
| 859 |
SIP/2.0 200 OK |
| 860 |
Via: SIP/2.0/TLS atlanta.example.com:5061 |
| 861 |
;branch=z9hG4bK74rf |
| 862 |
;received=192.0.2.103 |
| 863 |
From: Bob <sips:[email protected]>;tag=02134 |
| 864 |
To: Music Source <sips:[email protected]>;tag=56323 |
| 865 |
Call-ID: [email protected] |
| 866 |
Contact: <sips:[email protected]>;automaton |
| 867 |
;+sip.byeless;+sip.rendering="no" |
| 868 |
CSeq: 2 BYE |
| 869 |
Content-Length: 0 |
| 870 |
|
| 871 |
/* Normal media session between Alice and Bob is resumed. */ |
| 872 |
|
| 873 |
|
| 874 |
|
| 875 |
|
| 876 |
|
| 877 |
|
| 878 |
|
| 879 |
|
| 880 |
|
| 881 |
|
| 882 |
|
| 883 |
|
| 884 |
|
| 885 |
|
| 886 |
|
| 887 |
|
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Worley Informational [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 895 |
|
| 896 |
|
| 897 |
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Receiving Re-INVITE and UPDATE from the Remote UA</span> |
| 898 |
|
| 899 |
While the call is on hold, the remote UA can send a request to modify |
| 900 |
the SDP or the feature parameters of its Contact header. This can be |
| 901 |
done with either an INVITE or UPDATE method, both of which have much |
| 902 |
the same effect in regard to MOH. |
| 903 |
|
| 904 |
A common reason for a re-INVITE is when the remote UA desires to put |
| 905 |
the dialog on hold on its end. And because of the need to support |
| 906 |
this case, an implementation must process INVITEs and UPDATEs during |
| 907 |
the on-hold state as described below. |
| 908 |
|
| 909 |
The executing UA handles these requests by echoing requests and |
| 910 |
responses: an incoming request from the remote UA causes the |
| 911 |
executing UA to send a similar request to the MOH source, and an |
| 912 |
incoming response from the MOH source causes the executing UA to send |
| 913 |
a similar response to the remote UA. In all cases, SDP offers or |
| 914 |
answers that are received are added as bodies to the stimulated |
| 915 |
request or response to the other UA. |
| 916 |
|
| 917 |
The passed-through SDP will usually need its "o=" line modified. The |
| 918 |
directionality attributes may need to be restricted by changing |
| 919 |
"active" to "recvonly" and "sendonly" to "inactive", as the executing |
| 920 |
UA will not render media from the remote UA. (If all passed-through |
| 921 |
directionality attributes are "inactive", the optimization described |
| 922 |
in <a href="#section-2.10">Section 2.10</a> may be applied.) In regard to payload type numbers, |
| 923 |
since the mapping has already been established within the MOH dialog, |
| 924 |
"a=rtpmap" lines need not be added. |
| 925 |
|
| 926 |
<span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. Receiving INVITE with Replaces</span> |
| 927 |
|
| 928 |
The executing UA must be prepared to receive an INVITE request with a |
| 929 |
Replaces header that specifies the dialog with the remote UA. If the |
| 930 |
executing UA wants to create this new dialog in the on-hold state, it |
| 931 |
creates a new dialog with the MOH source to obtain MOH. The |
| 932 |
executing UA negotiates the SDP within the dialog created by the |
| 933 |
INVITE with Replaces by passing the offer through to the new MOH |
| 934 |
dialog (if the INVITE contains an offer) or by creating the new MOH |
| 935 |
dialog with an offerless INVITE (if the INVITE does not contain an |
| 936 |
offer). |
| 937 |
|
| 938 |
|
| 939 |
|
| 940 |
|
| 941 |
|
| 942 |
|
| 943 |
|
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Worley Informational [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 951 |
|
| 952 |
|
| 953 |
Continuing the example of <a href="#section-2.3">Section 2.3</a>, the executing UA receives an |
| 954 |
INVITE with Replaces that contains an offer: |
| 955 |
|
| 956 |
Alice Bob Music Source Carol |
| 957 |
|
| 958 |
(For example, Alice has called Carol and initiates an attended |
| 959 |
transfer by sending a REFER to Carol, causing Carol to send an |
| 960 |
INVITE with Replaces to Bob.) |
| 961 |
|
| 962 |
Bob receives INVITE with Replaces from Carol: |
| 963 |
|
| 964 |
| | | | |
| 965 |
| | | INVITE/Replaces | |
| 966 |
| | | From: Carol | |
| 967 |
| | | To: Bob | |
| 968 |
| | | (SDP offer) | |
| 969 |
| |<-------------------------------| |
| 970 |
| | INVITE | | |
| 971 |
| | From: Bob | | |
| 972 |
| | To: Music Source | |
| 973 |
| | (SDP offer, | | |
| 974 |
| | rev. hold) | | |
| 975 |
| |------------->| | |
| 976 |
| | 200 OK | | |
| 977 |
| | From: Bob | | |
| 978 |
| | To: Music Source | |
| 979 |
| | (SDP answer, | | |
| 980 |
| | hold) | | |
| 981 |
| |<-------------| | |
| 982 |
| | ACK | | |
| 983 |
| | From: Bob | | |
| 984 |
| | To: Music Source | |
| 985 |
| |------------->| | |
| 986 |
| | | 200 OK | |
| 987 |
| | | From: Carol | |
| 988 |
| | | To: Bob | |
| 989 |
| | | (SDP answer, | |
| 990 |
| | | hold) | |
| 991 |
| |------------------------------->| |
| 992 |
| | | ACK | |
| 993 |
| | | From: Carol | |
| 994 |
| | | To: Bob | |
| 995 |
| |<-------------------------------| |
| 996 |
| | | Music-on-hold RTP |
| 997 |
| | |================>| |
| 998 |
| | | | |
| 999 |
|
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Worley Informational [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
Bob terminates the previous dialog with Alice: |
| 1010 |
|
| 1011 |
| | | | |
| 1012 |
| BYE | | | |
| 1013 |
| From: Bob | | | |
| 1014 |
| To: Alice | | | |
| 1015 |
|<---------------| | | |
| 1016 |
| 200 OK | | | |
| 1017 |
| From: Bob | | | |
| 1018 |
| To: Alice | | | |
| 1019 |
|--------------->| | | |
| 1020 |
| | | | |
| 1021 |
|
| 1022 |
Bob terminates the MOH dialog for the dialog with Alice: |
| 1023 |
|
| 1024 |
| | | | |
| 1025 |
| | BYE | | |
| 1026 |
| | From: Bob | | |
| 1027 |
| | To: Music Source | |
| 1028 |
| |------------->| | |
| 1029 |
| | 200 OK | | |
| 1030 |
| | From: Music Source | |
| 1031 |
| | To: Bob | | |
| 1032 |
| |<-------------| | |
| 1033 |
| | | | |
| 1034 |
|
| 1035 |
The new session continues on hold, between Bob and Carol. |
| 1036 |
|
| 1037 |
<span class="h3"><a class="selflink" id="section-2.6" href="#section-2.6">2.6</a>. Receiving REFER from the Remote UA</span> |
| 1038 |
|
| 1039 |
The executing UA must be prepared to receive a REFER request within |
| 1040 |
the dialog with the remote UA. The SDP within the dialog created by |
| 1041 |
the REFER is negotiated by sending an offerless INVITE (or offerless |
| 1042 |
re-INVITE) to the MOH source to obtain an offer and then using that |
| 1043 |
offer in the INVITE to the refer target. |
| 1044 |
|
| 1045 |
Similar processing is used for an out-of-dialog REFER whose Target- |
| 1046 |
Dialog header refers to the dialog with the remote UA. |
| 1047 |
|
| 1048 |
Continuing the example of <a href="#section-2.3">Section 2.3</a>, the executing UA receives an |
| 1049 |
INVITE with Replaces that contains an offer: |
| 1050 |
|
| 1051 |
|
| 1052 |
|
| 1053 |
|
| 1054 |
|
| 1055 |
|
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Worley Informational [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
Alice Bob Music Source Carol |
| 1066 |
|
| 1067 |
(For example, Alice initiates an unattended transfer of the call to |
| 1068 |
Carol by sending a REFER to Bob.) |
| 1069 |
|
| 1070 |
Bob receives REFER from Alice: |
| 1071 |
|
| 1072 |
| | | | |
| 1073 |
| REFER | | | |
| 1074 |
| From: Bob | | | |
| 1075 |
| To: Alice | | | |
| 1076 |
| Refer-To: Carol| | | |
| 1077 |
|--------------->| | | |
| 1078 |
| | re-INVITE | | |
| 1079 |
| | From: Bob | | |
| 1080 |
| | To: Music Source | |
| 1081 |
| | (no SDP) | | |
| 1082 |
| |------------->| | |
| 1083 |
| | 200 OK | | |
| 1084 |
| | From: Bob | | |
| 1085 |
| | To: Music Source | |
| 1086 |
| | (SDP offer, | | |
| 1087 |
| | hold) | | |
| 1088 |
| |<-------------| | |
| 1089 |
| | | INVITE | |
| 1090 |
| | | From: Bob | |
| 1091 |
| | | To: Carol | |
| 1092 |
| | | (SDP offer, | |
| 1093 |
| | | hold) | |
| 1094 |
| |------------------------------->| |
| 1095 |
| | | 200 OK | |
| 1096 |
| | | From: Bob | |
| 1097 |
| | | To: Carol | |
| 1098 |
| | | (SDP answer, | |
| 1099 |
| | | rev. hold) | |
| 1100 |
| |------------------------------->| |
| 1101 |
| | ACK | | |
| 1102 |
| | From: Bob | | |
| 1103 |
| | To: Music Source | |
| 1104 |
| | (SDP answer, | | |
| 1105 |
| | rev. hold) | | |
| 1106 |
| |------------->| | |
| 1107 |
| | | ACK | |
| 1108 |
| | | From: Bob | |
| 1109 |
| | | To: Carol | |
| 1110 |
| |------------------------------->| |
| 1111 |
|
| 1112 |
|
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">Worley Informational [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
| | | Music-on-hold RTP |
| 1122 |
| | |================>| |
| 1123 |
| | | | |
| 1124 |
|
| 1125 |
Bob terminates the previous dialog with Alice: |
| 1126 |
|
| 1127 |
| | | | |
| 1128 |
| BYE | | | |
| 1129 |
| From: Bob | | | |
| 1130 |
| To: Alice | | | |
| 1131 |
|<---------------| | | |
| 1132 |
| 200 OK | | | |
| 1133 |
| From: Bob | | | |
| 1134 |
| To: Alice | | | |
| 1135 |
|--------------->| | | |
| 1136 |
| | | | |
| 1137 |
|
| 1138 |
<span class="h3"><a class="selflink" id="section-2.7" href="#section-2.7">2.7</a>. Receiving Re-INVITE and UPDATE from the Music-on-Hold Source</span> |
| 1139 |
|
| 1140 |
It is possible for the MOH source to send a re-INVITE or UPDATE |
| 1141 |
request, and the executing UA can support doing so in similar manner |
| 1142 |
as requests from the remote UA. However, if the MOH source is within |
| 1143 |
the same administrative domain as the executing UA, the executing UA |
| 1144 |
may have knowledge that the MOH source will not (or need not) make |
| 1145 |
such requests and so can respond to any such request with a failure |
| 1146 |
response, avoiding the need to pass the request through. The 403 |
| 1147 |
(Forbidden) response is suitable for this purpose because [<a href="./rfc3261" title=""SIP: Session Initiation Protocol"">RFC3261</a>] |
| 1148 |
specifies that this response indicates "the request SHOULD NOT be |
| 1149 |
repeated". |
| 1150 |
|
| 1151 |
However, in an environment in which Interactive Connectivity |
| 1152 |
Establishment (ICE) [<a href="./rfc5245" title=""Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols"">RFC5245</a>] is supported, the MOH source may need |
| 1153 |
to send requests as part of ICE negotiation with the remote UA. |
| 1154 |
Hence, in environments that support ICE, the executing UA must be |
| 1155 |
able to pass through requests from the MOH source as well as requests |
| 1156 |
from the remote UA. |
| 1157 |
|
| 1158 |
Again, as SDP is passed through, its "o=" line will need to be |
| 1159 |
modified. In some cases, the directionality attributes will need to |
| 1160 |
be restricted. |
| 1161 |
|
| 1162 |
|
| 1163 |
|
| 1164 |
|
| 1165 |
|
| 1166 |
|
| 1167 |
|
| 1168 |
|
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">Worley Informational [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
<span class="h3"><a class="selflink" id="section-2.8" href="#section-2.8">2.8</a>. Handling Payload Type Numbers</span> |
| 1178 |
|
| 1179 |
<span class="h4"><a class="selflink" id="section-2.8.1" href="#section-2.8.1">2.8.1</a>. Analysis</span> |
| 1180 |
|
| 1181 |
In this technique, the MOH source generates an SDP answer that the |
| 1182 |
executing UA presents to the remote UA as an answer within the |
| 1183 |
original dialog. In basic functionality, this presents no problem, |
| 1184 |
because <a href="./rfc3264#section-6.1">[RFC3264], Section 6.1</a> (at the very end) specifies that the |
| 1185 |
payload type numbers used in either direction of RTP are the ones |
| 1186 |
specified in the SDP sent by the recipient of the RTP. Thus, the MOH |
| 1187 |
source will send RTP to the remote UA using the payload type numbers |
| 1188 |
specified in the offer SDP it received (ultimately) from the remote |
| 1189 |
UA. |
| 1190 |
|
| 1191 |
But strict compliance to <a href="./rfc3264#section-8.3.2">[RFC3264], Section 8.3.2</a> requires that |
| 1192 |
payload type numbers used in SDP may only duplicate the payload type |
| 1193 |
numbers used in any previous SDP sent in the same direction if the |
| 1194 |
payload type numbers represent the same media format (codec) as they |
| 1195 |
did previously. However, the MOH source has no knowledge of the |
| 1196 |
payload type numbers previously used in the original dialog, and it |
| 1197 |
may accidentally specify a different media format for a previously |
| 1198 |
used payload type number in its answer (or in a subsequently |
| 1199 |
generated INVITE or UPDATE). This would cause no problem with media |
| 1200 |
decoding, as it cannot send any format that was not in the remote |
| 1201 |
UA's offer, but it would violate [<a href="./rfc3264" title=""An Offer/Answer Model with Session Description Protocol (SDP)"">RFC3264</a>]. |
| 1202 |
|
| 1203 |
Strictly speaking, it is impossible to avoid this problem because the |
| 1204 |
generator of a first answer in its dialog can choose the payload |
| 1205 |
numbers independently of the payload numbers in the offer, and the |
| 1206 |
MOH server believes that its answer is first in the dialog. Thus, |
| 1207 |
the only absolute solution is to have the executing UA rewrite the |
| 1208 |
SDP that passes through it to reassign payload type numbers, which |
| 1209 |
would also require it to rewrite the payload type numbers in the RTP |
| 1210 |
packets -- a very undesirable solution. |
| 1211 |
|
| 1212 |
The difficulty solving this problem (and similar problems in other |
| 1213 |
situations) argues that strict adherence should not be required to |
| 1214 |
the rule that payload type numbers not be reused for different |
| 1215 |
codecs. |
| 1216 |
|
| 1217 |
If an implementation of this technique were to interact with a remote |
| 1218 |
UA that requires strict compliance to [<a href="./rfc3264" title=""An Offer/Answer Model with Session Description Protocol (SDP)"">RFC3264</a>], the remote UA might |
| 1219 |
reject the SDP provided by the MOH server. (In <a href="#section-2.3">Section 2.3</a>, this SDP |
| 1220 |
is in message F10.) As a result, the MOH session will not be |
| 1221 |
established, and the call will remain in its initial state. |
| 1222 |
Implementors that wish to avoid this situation need to implement the |
| 1223 |
solution in <a href="#section-2.8.2">Section 2.8.2</a>. |
| 1224 |
|
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">Worley Informational [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
<span class="h4"><a class="selflink" id="section-2.8.2" href="#section-2.8.2">2.8.2</a>. Solution to the Problem</span> |
| 1234 |
|
| 1235 |
We can construct a technique that will strictly adhere to the payload |
| 1236 |
type rule by exploiting a SHOULD-level requirement in <a href="./rfc3264#section-6.1">[RFC3264], |
| 1237 |
Section 6.1</a>: "In the case of RTP, if a particular codec was |
| 1238 |
referenced with a specific payload type number in the offer, that |
| 1239 |
same payload type number SHOULD be used for that codec in the |
| 1240 |
answer". Or rather, we exploit the "implied requirement" that if a |
| 1241 |
specific payload number in the offer is used for a particular codec, |
| 1242 |
then the answer should not use that payload number for a different |
| 1243 |
codec. If the MOH source obeys this restriction, the executing UA |
| 1244 |
can modify the offer SDP to "reserve" all payload type numbers that |
| 1245 |
have ever been offered by the executing UA to prevent the MOH source |
| 1246 |
from using them for different media formats. |
| 1247 |
|
| 1248 |
When the executing UA is composing the INVITE to the MOH source, it |
| 1249 |
compiles a list of all the (dynamically assigned) payload type |
| 1250 |
numbers and associated media formats that have been used by it (or by |
| 1251 |
MOH sources on its behalf) in the original dialog. (The executing UA |
| 1252 |
must maintain a list of all previously used payload type numbers |
| 1253 |
anyway, in order to comply with [<a href="./rfc3264" title=""An Offer/Answer Model with Session Description Protocol (SDP)"">RFC3264</a>].) |
| 1254 |
|
| 1255 |
Any payload type number that is present in the offer but has been |
| 1256 |
used previously by the executing UA in the original dialog for a |
| 1257 |
different media format is rewritten to describe a dummy media format. |
| 1258 |
(One dummy media format name can be used for many payload type |
| 1259 |
numbers as multiple payload type numbers can refer to the same media |
| 1260 |
format.) A payload type number is added to describe the deleted |
| 1261 |
media format, the number being either previously unused or previously |
| 1262 |
used by the executing UA for that media format. |
| 1263 |
|
| 1264 |
Any further payload type numbers that have been used by the executing |
| 1265 |
UA in the original dialog but that are not mapped to a media format |
| 1266 |
in the current offer are then mapped to a dummy media format. |
| 1267 |
|
| 1268 |
The result is that the modified offer SDP: |
| 1269 |
|
| 1270 |
1. offers the same set of media formats (ignoring dummies) as the |
| 1271 |
original offer SDP (though possibly with different payload type |
| 1272 |
numbers), |
| 1273 |
|
| 1274 |
2. associates every payload type number either with a dummy media |
| 1275 |
format or with the media format that the executing UA has |
| 1276 |
previously used it for, and |
| 1277 |
|
| 1278 |
3. provides a (real or dummy) media format for every payload type |
| 1279 |
number that the executing UA has previously used. |
| 1280 |
|
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
<span class="grey">Worley Informational [Page 23]</span></pre> |
| 1285 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1286 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
These properties are sufficient to force an MOH server that obeys the |
| 1290 |
implied requirement to generate an answer that is a correct answer to |
| 1291 |
the original offer and is also compatible with previous SDP from the |
| 1292 |
executing UA. |
| 1293 |
|
| 1294 |
Note that any re-INVITEs from the remote UA that the executing UA |
| 1295 |
passes through to the MOH server require similar modification, as |
| 1296 |
payload type numbers that the MOH server receives in past offers are |
| 1297 |
not absolutely reserved against its use (as they have not been sent |
| 1298 |
in SDP by the MOH server) nor is there a SHOULD-level proscription |
| 1299 |
against using them in the current answer (as they do not appear in |
| 1300 |
the current offer). |
| 1301 |
|
| 1302 |
This should provide an adequate solution to the problems with payload |
| 1303 |
type numbers, as it will fail only if (1) the remote UA is particular |
| 1304 |
that other UAs follow the rule about not redefining payload type |
| 1305 |
numbers, and (2) the MOH server does not follow the implied |
| 1306 |
requirement of <a href="./rfc3264#section-6.1">[RFC3264], Section 6.1</a>. |
| 1307 |
|
| 1308 |
<span class="h4"><a class="selflink" id="section-2.8.3" href="#section-2.8.3">2.8.3</a>. Example of the Solution</span> |
| 1309 |
|
| 1310 |
Let us show how this process works by modifying the example of |
| 1311 |
<a href="#section-2.3">Section 2.3</a> with this specific assignment of supported codecs: |
| 1312 |
|
| 1313 |
Alice supports formats X and Y. |
| 1314 |
|
| 1315 |
Bob supports formats X and Z. |
| 1316 |
|
| 1317 |
Music Source supports formats Y and Z. |
| 1318 |
|
| 1319 |
In this case, the SDP exchanges are: |
| 1320 |
|
| 1321 |
F1 offers X and Y, F3 answers X and Z. (Only X can be used.) |
| 1322 |
|
| 1323 |
F6 offers X and Y, but F7 offers X, Y, and a place-holder to block |
| 1324 |
use of type 92. |
| 1325 |
|
| 1326 |
F8/F10 answers Y. |
| 1327 |
|
| 1328 |
|
| 1329 |
|
| 1330 |
|
| 1331 |
|
| 1332 |
|
| 1333 |
|
| 1334 |
|
| 1335 |
|
| 1336 |
|
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
<span class="grey">Worley Informational [Page 24]</span></pre> |
| 1341 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span> |
| 1342 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 1343 |
|
| 1344 |
|
| 1345 |
The messages that are changed from <a href="#section-2.3">Section 2.3</a> are: |
| 1346 |
|
| 1347 |
F1 INVITE Alice -> Bob |
| 1348 |
|
| 1349 |
INVITE sips:[email protected] SIP/2.0 |
| 1350 |
Via: SIP/2.0/TLS atlanta.example.com:5061 |
| 1351 |
;branch=z9hG4bK74bf9 |
| 1352 |
Max-Forwards: 70 |
| 1353 |
From: Alice <sips:[email protected]>;tag=1234567 |
| 1354 |
To: Bob <sips:[email protected]> |
| 1355 |
Call-ID: [email protected] |
| 1356 |
CSeq: 1 INVITE |
| 1357 |
Contact: <sips:[email protected];gr> |
| 1358 |
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY |
| 1359 |
Supported: replaces, gruu |
| 1360 |
Content-Type: application/sdp |
| 1361 |
Content-Length: [omitted] |
| 1362 |
|
| 1363 |
v=0 |
| 1364 |
o=alice 2890844526 2890844526 IN IP4 atlanta.example.com |
| 1365 |
s= |
| 1366 |
c=IN IP4 atlanta.example.com |
| 1367 |
t=0 0 |
| 1368 |
m=audio 49170 RTP/AVP 90 91 |
| 1369 |
a=rtpmap:90 X/8000 |
| 1370 |
a=rtpmap:91 Y/8000 |
| 1371 |
|
| 1372 |
|
| 1373 |
F3 200 OK Bob -> Alice |
| 1374 |
|
| 1375 |
SIP/2.0 200 OK |
| 1376 |
Via: SIP/2.0/TLS atlanta.example.com:5061 |
| 1377 |
;branch=z9hG4bK74bf9 |
| 1378 |
;received=192.0.2.103 |
| 1379 |
From: Alice <sips:[email protected]>;tag=1234567 |
| 1380 |
To: Bob <sips:[email protected]>;tag=23431 |
| 1381 |
Call-ID: [email protected] |
| 1382 |
CSeq: 1 INVITE |
| 1383 |
Contact: <sips:[email protected]> |
| 1384 |
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY |
| 1385 |
Supported: replaces |
| 1386 |
Content-Type: application/sdp |
| 1387 |
Content-Length: [omitted] |
| 1388 |
|
| 1389 |
|
| 1390 |
|
| 1391 |
|
| 1392 |
|
| 1393 |
|
| 1394 |
|
| 1395 |
|
| 1396 |
<span class="grey">Worley Informational [Page 25]</span></pre> |
| 1397 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span> |
| 1398 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 1399 |
|
| 1400 |
|
| 1401 |
v=0 |
| 1402 |
o=bob 2890844527 2890844527 IN IP4 biloxi.example.com |
| 1403 |
s= |
| 1404 |
c=IN IP4 biloxi.example.com |
| 1405 |
t=0 0 |
| 1406 |
m=audio 3456 RTP/AVP 90 92 |
| 1407 |
a=rtpmap:90 X/8000 |
| 1408 |
a=rtpmap:92 Z/8000 |
| 1409 |
|
| 1410 |
|
| 1411 |
F6 200 OK Alice -> Bob |
| 1412 |
|
| 1413 |
SIP/2.0 200 OK |
| 1414 |
Via: SIP/2.0/TLS biloxi.example.com:5061 |
| 1415 |
;branch=z9hG4bK874bk |
| 1416 |
;received=192.0.2.105 |
| 1417 |
To: Alice <sips:[email protected]>;tag=1234567 |
| 1418 |
From: Bob <sips:[email protected]>;tag=23431 |
| 1419 |
Call-ID: [email protected] |
| 1420 |
CSeq: 712 INVITE |
| 1421 |
Contact: <sips:[email protected];gr> |
| 1422 |
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY |
| 1423 |
Supported: replaces, gruu |
| 1424 |
Content-Type: application/sdp |
| 1425 |
Content-Length: [omitted] |
| 1426 |
|
| 1427 |
v=0 |
| 1428 |
o=alice 2890844526 2890844526 IN IP4 atlanta.example.com |
| 1429 |
s= |
| 1430 |
c=IN IP4 atlanta.example.com |
| 1431 |
t=0 0 |
| 1432 |
m=audio 49170 RTP/AVP 90 91 |
| 1433 |
a=rtpmap:90 X/8000 |
| 1434 |
a=rtpmap:91 Y/8000 |
| 1435 |
a=active |
| 1436 |
|
| 1437 |
|
| 1438 |
|
| 1439 |
|
| 1440 |
|
| 1441 |
|
| 1442 |
|
| 1443 |
|
| 1444 |
|
| 1445 |
|
| 1446 |
|
| 1447 |
|
| 1448 |
|
| 1449 |
|
| 1450 |
|
| 1451 |
|
| 1452 |
<span class="grey">Worley Informational [Page 26]</span></pre> |
| 1453 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span> |
| 1454 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 1455 |
|
| 1456 |
|
| 1457 |
F7 INVITE Bob -> Music Source |
| 1458 |
|
| 1459 |
INVITE sips:[email protected] SIP/2.0 |
| 1460 |
Via: SIP/2.0/TLS biloxi.example.com:5061 |
| 1461 |
;branch=z9hG4bKnashds9 |
| 1462 |
Max-Forwards: 70 |
| 1463 |
From: Bob <sips:[email protected]>;tag=02134 |
| 1464 |
To: Music Source <sips:[email protected]> |
| 1465 |
Call-ID: [email protected] |
| 1466 |
CSeq: 1 INVITE |
| 1467 |
Contact: <sips:[email protected]> |
| 1468 |
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY |
| 1469 |
Supported: replaces, gruu |
| 1470 |
Content-Type: application/sdp |
| 1471 |
Content-Length: [omitted] |
| 1472 |
|
| 1473 |
v=0 |
| 1474 |
o=bob 2890844534 2890844534 IN IP4 atlanta.example.com |
| 1475 |
s= |
| 1476 |
c=IN IP4 atlanta.example.com |
| 1477 |
t=0 0 |
| 1478 |
m=audio 49170 RTP/AVP 90 91 92 |
| 1479 |
a=rtpmap:90 X/8000 |
| 1480 |
a=rtpmap:91 Y/8000 |
| 1481 |
a=rtpmap:92 x-reserved/8000 |
| 1482 |
a=recvonly |
| 1483 |
|
| 1484 |
|
| 1485 |
F8 200 OK Music Source -> Bob |
| 1486 |
|
| 1487 |
SIP/2.0 200 OK |
| 1488 |
Via: SIP/2.0/TLS biloxi.example.com:5061 |
| 1489 |
;branch=z9hG4bKnashds9 |
| 1490 |
;received=192.0.2.105 |
| 1491 |
From: Bob <sips:[email protected]>;tag=02134 |
| 1492 |
To: Music Source <sips:[email protected]>;tag=56323 |
| 1493 |
Call-ID: [email protected] |
| 1494 |
Contact: <sips:[email protected]>;automaton |
| 1495 |
;+sip.byeless;+sip.rendering="no" |
| 1496 |
CSeq: 1 INVITE |
| 1497 |
Content-Length: [omitted] |
| 1498 |
|
| 1499 |
|
| 1500 |
|
| 1501 |
|
| 1502 |
|
| 1503 |
|
| 1504 |
|
| 1505 |
|
| 1506 |
|
| 1507 |
|
| 1508 |
<span class="grey">Worley Informational [Page 27]</span></pre> |
| 1509 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span> |
| 1510 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 1511 |
|
| 1512 |
|
| 1513 |
v=0 |
| 1514 |
o=MusicSource 2890844576 2890844576 IN IP4 source.example.com |
| 1515 |
s= |
| 1516 |
c=IN IP4 source.example.com |
| 1517 |
t=0 0 |
| 1518 |
m=audio 49170 RTP/AVP 91 |
| 1519 |
a=rtpmap:91 Y/8000 |
| 1520 |
a=sendonly |
| 1521 |
|
| 1522 |
<span class="h3"><a class="selflink" id="section-2.9" href="#section-2.9">2.9</a>. Dialog/Session Timers</span> |
| 1523 |
|
| 1524 |
The executing UA may discover that either the remote UA or the MOH |
| 1525 |
source wishes to use dialog/session liveness timers [<a href="./rfc4028" title=""Session Timers in the Session Initiation Protocol (SIP)"">RFC4028</a>]. Since |
| 1526 |
the timers verify the liveness of dialogs, not sessions (despite the |
| 1527 |
terminology of [<a href="./rfc4028" title=""Session Timers in the Session Initiation Protocol (SIP)"">RFC4028</a>]), the executing UA can support the timers on |
| 1528 |
each dialog (to the remote UA and to the MOH source) independently. |
| 1529 |
(If the executing UA becomes obliged to initiate a refresh |
| 1530 |
transaction, it must send an offerless UPDATE or re-INVITE, as if it |
| 1531 |
sends an offer, the remote element has the opportunity to provide an |
| 1532 |
answer that is different from its previous SDP, which could not |
| 1533 |
easily be conveyed to the other remote element.) |
| 1534 |
|
| 1535 |
<span class="h3"><a class="selflink" id="section-2.10" href="#section-2.10">2.10</a>. When the Media Stream Directionality is "inactive"</span> |
| 1536 |
|
| 1537 |
The directionality of the media stream in the SDP offer in an INVITE |
| 1538 |
or re-INVITE to the music source can be "inactive" if the SDP offer |
| 1539 |
from the remote UA was "sendonly" or "inactive". Generally, this |
| 1540 |
happens when the remote UA also has put the call on hold and provided |
| 1541 |
a directionality of "sendonly". In this situation, the executing UA |
| 1542 |
can omit establishing the dialog with the music source (or can |
| 1543 |
terminate the existing dialog with the music source). |
| 1544 |
|
| 1545 |
If the executing UA uses this optimization, it creates the SDP answer |
| 1546 |
itself, with directionality "inactive" and using its own RTP/RTCP |
| 1547 |
ports, and returns that answer to the remote UA. |
| 1548 |
|
| 1549 |
The executing UA must be prepared for the remote UA to send a |
| 1550 |
re-INVITE with directionality "active" or "recvonly", in which case |
| 1551 |
the executing UA must initiate a dialog with the music source, as |
| 1552 |
described above. |
| 1553 |
|
| 1554 |
<span class="h3"><a class="selflink" id="section-2.11" href="#section-2.11">2.11</a>. Multiple Media Streams</span> |
| 1555 |
|
| 1556 |
There may be multiple media streams (multiple "m=" lines) in any of |
| 1557 |
the SDPs involved in the dialogs. As the SDPs are manipulated, each |
| 1558 |
media description (each starting with an "m=" line) is manipulated as |
| 1559 |
described above for a single media stream, largely independently of |
| 1560 |
the manipulation of the other media streams. But there are some |
| 1561 |
|
| 1562 |
|
| 1563 |
|
| 1564 |
<span class="grey">Worley Informational [Page 28]</span></pre> |
| 1565 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span> |
| 1566 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 1567 |
|
| 1568 |
|
| 1569 |
elaborations that the executing UA may implement to achieve specific |
| 1570 |
effects. |
| 1571 |
|
| 1572 |
If the executing UA desires to present only certain media types as |
| 1573 |
on-hold media, when passing the offer SDP through, it can reject any |
| 1574 |
particular media streams by setting the port number in the "m=" line |
| 1575 |
to zero [<a href="./rfc3264" title=""An Offer/Answer Model with Session Description Protocol (SDP)"">RFC3264</a>]. This ensures that the answer SDP will also have a |
| 1576 |
rejection for that "m=" line. |
| 1577 |
|
| 1578 |
If the executing UA wishes to provide its own on-hold media for a |
| 1579 |
particular "m=" line, it can do so by providing the answer |
| 1580 |
information for that "m=" line. The executing UA may decide to do |
| 1581 |
this when the offer SDP is received (by modifying the "m=" line to |
| 1582 |
rejected state when sending it to the music source) or upon receiving |
| 1583 |
the answer from the music source and discovering that the "m=" line |
| 1584 |
has been rejected. |
| 1585 |
|
| 1586 |
The executing UA may not want to pass a rejected "m=" line from the |
| 1587 |
music source to the remote UA (when the remote UA provided a non- |
| 1588 |
rejected "m=" line) and may instead provide an answer with |
| 1589 |
directionality "inactive" (and specifying its own RTP/RTCP ports). |
| 1590 |
|
| 1591 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Advantages</span> |
| 1592 |
|
| 1593 |
This technique for providing music on hold has advantages over other |
| 1594 |
methods now in use, including: |
| 1595 |
|
| 1596 |
1. The original dialog is not transferred to another UA, so the |
| 1597 |
"remote endpoint URI" displayed by the remote endpoint's user |
| 1598 |
interface and dialog event package [<a href="./rfc4235" title=""An INVITE- Initiated Dialog Event Package for the Session Initiation Protocol (SIP)"">RFC4235</a>] does not change |
| 1599 |
during the call, as contrasted to the method in <a href="./rfc5359#section-2.3">[RFC5359], |
| 1600 |
Section 2.3</a>. This URI is usually displayed to the user as the |
| 1601 |
name and number of the other party on the call, and it is |
| 1602 |
desirable for it not to change to that of the MOH server. |
| 1603 |
|
| 1604 |
2. Compared to [<a href="./rfc5359" title=""Session Initiation Protocol Service Examples"">RFC5359</a>], this method does not require use of an |
| 1605 |
out-of-dialog REFER, which is not otherwise used much in SIP. |
| 1606 |
Out-of-dialog REFERs may not be routed correctly, since neither |
| 1607 |
the From nor Contact URI of the original dialog may route |
| 1608 |
correctly to the remote UA. Also, out-of-dialog requests to UA |
| 1609 |
URIs may not be handled correctly by authorization mechanisms. |
| 1610 |
|
| 1611 |
3. The music-on-hold media are sent directly from the music-on-hold |
| 1612 |
source to the remote UA, rather than being relayed through the |
| 1613 |
executing UA. This reduces the computational load on the |
| 1614 |
executing UA and can reduce the load on the network (by |
| 1615 |
eliminating "hairpinning" of the media through the link serving |
| 1616 |
the executing UA). |
| 1617 |
|
| 1618 |
|
| 1619 |
|
| 1620 |
<span class="grey">Worley Informational [Page 29]</span></pre> |
| 1621 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span> |
| 1622 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 1623 |
|
| 1624 |
|
| 1625 |
4. The remote UA sees, in the incoming SDP, the address/port that |
| 1626 |
the MOH source will send MOH media from (assuming that the MOH |
| 1627 |
source follows the convention of sending its media from its |
| 1628 |
advertised media-listening address/port). Thus, the remote UA |
| 1629 |
will render the MOH media even if it is filtering incoming media |
| 1630 |
based on originating address as a media security measure. |
| 1631 |
|
| 1632 |
5. The technique requires relatively simple manipulation of SDP; in |
| 1633 |
particular, (1) it does not require a SIP element to modify |
| 1634 |
unrelated SDP to be acceptable to be sent within an already |
| 1635 |
established sequence of SDP (a problem with [<a href="#ref-SIP-SERV-EX">SIP-SERV-EX</a>], |
| 1636 |
Section 2.3), and (2) it does not require converting an SDP |
| 1637 |
answer into an SDP offer (which was a problem with the initial |
| 1638 |
draft version of this document, as well as with [<a href="#ref-SIP-SERV-EX">SIP-SERV-EX</a>]). |
| 1639 |
|
| 1640 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Caveats</span> |
| 1641 |
|
| 1642 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Offering All Available Media Formats</span> |
| 1643 |
|
| 1644 |
Unnecessary failures can happen if SDP offerers do not always offer |
| 1645 |
all media formats that they support. Doing so is considered best |
| 1646 |
practice ([<a href="./rfc6337" title=""Session Initiation Protocol (SIP) Usage of the Offer/Answer Model"">RFC6337</a>], Sections <a href="#section-5.1">5.1</a> and <a href="#section-5.3">5.3</a>), but some SIP elements |
| 1647 |
offer only formats that have already been in use in the dialog. |
| 1648 |
|
| 1649 |
An example of how omitting media formats in an offer can lead to |
| 1650 |
failure is as follows. Suppose that the UAs in <a href="#section-2.3">Section 2.3</a> each |
| 1651 |
support the following media formats: |
| 1652 |
|
| 1653 |
Alice supports formats X and Y. |
| 1654 |
|
| 1655 |
Bob supports formats X and Z. |
| 1656 |
|
| 1657 |
Music Source supports formats Y and Z. |
| 1658 |
|
| 1659 |
In this case, the SDP exchanges are: |
| 1660 |
|
| 1661 |
1. Alice calls Bob: |
| 1662 |
Alice offers X and Y (message F1). |
| 1663 |
Bob answers X (F3). |
| 1664 |
|
| 1665 |
2. Bob puts Alice on hold: |
| 1666 |
Alice (via Bob) offers X and Y (F6 and F7). |
| 1667 |
Music Source (via Bob) answers Y (F8 and F10). |
| 1668 |
|
| 1669 |
3. Bob takes Alice off hold: |
| 1670 |
Bob offers X and Z (F11). |
| 1671 |
Alice answers X (F12). |
| 1672 |
|
| 1673 |
|
| 1674 |
|
| 1675 |
|
| 1676 |
<span class="grey">Worley Informational [Page 30]</span></pre> |
| 1677 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span> |
| 1678 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 1679 |
|
| 1680 |
|
| 1681 |
Note that in exchange 2, if Alice assumes that because only format X |
| 1682 |
is currently in use that she should offer only X, the exchange fails. |
| 1683 |
In exchange 3, Bob offers formats X and Z, even though neither is in |
| 1684 |
use at the time (because Bob is not involved in the media streams). |
| 1685 |
|
| 1686 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Handling Re-INVITES in a B2BUA</span> |
| 1687 |
|
| 1688 |
Many UAs provide MOH in the interval during which it is processing a |
| 1689 |
blind transfer, between receiving the REFER and receiving the final |
| 1690 |
response to the stimulated INVITE. This process involves switching |
| 1691 |
the user's interface between three media sources: (1) the session of |
| 1692 |
the original dialog, (2) the session with the MOH server, and (3) the |
| 1693 |
session of the new dialog. It also involves a number of race |
| 1694 |
conditions that must be handled correctly. If the UA is a back-to- |
| 1695 |
back user agent (B2BUA) whose "other side" is maintaining a single |
| 1696 |
dialog with another UA, each switching of media sources potentially |
| 1697 |
causes a re-INVITE transaction within the other-side dialog. Since |
| 1698 |
re-INVITEs take time and must be sequenced correctly (<a href="./rfc3261#section-14">[RFC3261], |
| 1699 |
Section 14</a>), such a B2BUA must allow the events on each side to be |
| 1700 |
non-synchronous and must coordinate them correctly. Failing to do so |
| 1701 |
will lead to "glare" errors (491 or 500), leaving the other-side UA |
| 1702 |
not rendering the correct session. |
| 1703 |
|
| 1704 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span> |
| 1705 |
|
| 1706 |
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Network Security</span> |
| 1707 |
|
| 1708 |
Some mechanism outside the scope of this document must inform the |
| 1709 |
executing UA of the MOH server that it should use. Care must be |
| 1710 |
exercised in selecting the MOH server, because signaling information |
| 1711 |
that is part of the original dialog will be transmitted along the |
| 1712 |
path from the executing UA to the server. If the path between the |
| 1713 |
executing UA and the server is not entirely contained within every |
| 1714 |
network domain that contains the executing UA, the signaling between |
| 1715 |
the UA and the server may be protected by different network security |
| 1716 |
than is applied to the original dialog. |
| 1717 |
|
| 1718 |
Care must also be exercised because media information that is part of |
| 1719 |
the original dialog will be transmitted along the path between the |
| 1720 |
remote UA and the server. If the path between the remote UA and the |
| 1721 |
server does not pass through the same network domains as the path |
| 1722 |
between the remote UA and the executing UA, the media between the UA |
| 1723 |
and the server may be protected by different network security than is |
| 1724 |
applied to the original dialog. |
| 1725 |
|
| 1726 |
|
| 1727 |
|
| 1728 |
|
| 1729 |
|
| 1730 |
|
| 1731 |
|
| 1732 |
<span class="grey">Worley Informational [Page 31]</span></pre> |
| 1733 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span> |
| 1734 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 1735 |
|
| 1736 |
|
| 1737 |
These requirements may be satisfied by selecting an MOH server that |
| 1738 |
is in the same administrative and network domain as the executing UA |
| 1739 |
and whose path to all external addresses is the same as the UA's path |
| 1740 |
to those addresses. |
| 1741 |
|
| 1742 |
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. SIP (Signaling) Security</span> |
| 1743 |
|
| 1744 |
The executing UA and the MOH server will usually be within the same |
| 1745 |
administrative domain, and the SIP signaling path between them will |
| 1746 |
lie entirely within that domain. In this case, the administrator of |
| 1747 |
the domain should configure the UA and server to apply to the dialog |
| 1748 |
between them a level of security that is appropriate for the |
| 1749 |
administrative domain. |
| 1750 |
|
| 1751 |
If the executing UA and the MOH server are not within the same |
| 1752 |
administrative domain, the SIP signaling between them should be at |
| 1753 |
least as secure as the SIP signaling between the executing UA and the |
| 1754 |
remote UA. Thus, the MOH server should support all of the SIP |
| 1755 |
security facilities that are supported by the executing UA, and the |
| 1756 |
executing UA should use in its dialog with the MOH server all SIP |
| 1757 |
security facilities that are used in its dialog with the remote UA. |
| 1758 |
|
| 1759 |
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. RTP (Media) Security</span> |
| 1760 |
|
| 1761 |
The RTP for the MOH media will pass directly between the MOH server |
| 1762 |
and the remote UA and thus may pass outside the administrative domain |
| 1763 |
of the executing UA. While it is uncommon for the contents of the |
| 1764 |
MOH media to be sensitive (and the remote UA will not usually be |
| 1765 |
generating RTP when it is on hold), the MOH RTP should be at least as |
| 1766 |
secure as the RTP between the executing UA and the remote UA. In |
| 1767 |
order to make this possible, the MOH server should support all of the |
| 1768 |
RTP security facilities that are supported by the executing UA. |
| 1769 |
|
| 1770 |
It is possible that the remote UA and the MOH server support an RTP |
| 1771 |
security facility that the executing UA does not support and that it |
| 1772 |
is desirable to use this facility for the MOH RTP. To enable doing |
| 1773 |
so, the executing UA should pass the SDP between the remote UA and |
| 1774 |
the MOH server completely, not omitting elements that it does not |
| 1775 |
understand. |
| 1776 |
|
| 1777 |
<span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. Media Filtering</span> |
| 1778 |
|
| 1779 |
Some UAs filter incoming RTP based on the address of origin as a |
| 1780 |
media security measure, refusing to render the contents of RTP |
| 1781 |
packets that originate from an address that is not shown in the |
| 1782 |
remote SDP as an RTP destination address. The remote UA in the |
| 1783 |
original dialog may use this form of media filtering, and if the |
| 1784 |
executing UA does not update the SDP to inform the remote UA of the |
| 1785 |
|
| 1786 |
|
| 1787 |
|
| 1788 |
<span class="grey">Worley Informational [Page 32]</span></pre> |
| 1789 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span> |
| 1790 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 1791 |
|
| 1792 |
|
| 1793 |
source address of the MOH media, the remote UA may not render the MOH |
| 1794 |
media. Note that the executing UA has no means for detecting that |
| 1795 |
the remote UA uses media filtering, so the executing UA must assume |
| 1796 |
that any remote UA uses media filtering. |
| 1797 |
|
| 1798 |
The technique described in this document ensures that any UA that |
| 1799 |
should render MOH media will be informed of the source address of the |
| 1800 |
media via the SDP that it receives. This allows such UAs to filter |
| 1801 |
media without interfering with MOH operation. |
| 1802 |
|
| 1803 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgments</span> |
| 1804 |
|
| 1805 |
The original version of this proposal was derived from Section 2.3 of |
| 1806 |
[<a href="#ref-SIP-SERV-EX">SIP-SERV-EX</a>] and the similar implementation of MOH in the snom UA. |
| 1807 |
Significant improvements to the sequence of operations, allowing |
| 1808 |
improvements to the SDP handling, were suggested by Venkatesh |
| 1809 |
[<a href="#ref-VENKATESH">VENKATESH</a>]. |
| 1810 |
|
| 1811 |
John Elwell [<a href="#ref-ELWELL" title=""Subject: [Sipping] RE: I-D Action:draft- worley-service-example-00.txt"">ELWELL</a>] pointed out the need for the executing UA to |
| 1812 |
pass through re-INVITEs/UPDATEs in order to allow ICE negotiation, |
| 1813 |
suggested mentioning the role of RTCP listening ports, suggested the |
| 1814 |
possibility of omitting the dialog to the music source if the |
| 1815 |
directionality would be "inactive", and pointed out that if there are |
| 1816 |
multiple media streams, the executing UA may want to select which |
| 1817 |
streams receive MOH. |
| 1818 |
|
| 1819 |
Paul Kyzivat [<a href="#ref-KYZIVAT-1">KYZIVAT-1</a>] [<a href="#ref-KYZIVAT-2">KYZIVAT-2</a>] pointed out the difficulties |
| 1820 |
regarding reuse of payload type numbers and considerations that could |
| 1821 |
be used to avoid those difficulties, leading to the writing of |
| 1822 |
<a href="#section-2.8">Section 2.8</a>. |
| 1823 |
|
| 1824 |
Paul Kyzivat suggested adding <a href="#section-4.1">Section 4.1</a> showing why offerers should |
| 1825 |
always include all supported formats. |
| 1826 |
|
| 1827 |
M. Ranganathan pointed out the difficulties experienced by a B2BUA |
| 1828 |
(<a href="#section-4.2">Section 4.2</a>) due to the multiple changes of media source. |
| 1829 |
|
| 1830 |
<a href="#section-4.1">Section 4.1</a> was significantly clarified based on advice from Attila |
| 1831 |
Sipos [<a href="#ref-SIPOS" title=""Subject: [Sip-implementors] draft-worley- service-example-02"">SIPOS</a>]. |
| 1832 |
|
| 1833 |
The need to discuss dialog/session timers (<a href="#section-2.9">Section 2.9</a>) was pointed |
| 1834 |
out by Rifaat Shekh-Yusef [<a href="#ref-SHEKH-YUSEF">SHEKH-YUSEF</a>]. |
| 1835 |
|
| 1836 |
Robert Sparks clarified the purpose of the "Best Current Practice" |
| 1837 |
status, leading to revising the intended status of this document to |
| 1838 |
"Informational". |
| 1839 |
|
| 1840 |
|
| 1841 |
|
| 1842 |
|
| 1843 |
|
| 1844 |
<span class="grey">Worley Informational [Page 33]</span></pre> |
| 1845 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span> |
| 1846 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 1847 |
|
| 1848 |
|
| 1849 |
In his SecDir review, Stephen Kent pointed out that the Security |
| 1850 |
Considerations should discuss the use of SIP and SDP security |
| 1851 |
features by the MOH server. |
| 1852 |
|
| 1853 |
Numerous improvements to the text were due to reviewers, including |
| 1854 |
Rifaat Shekh-Yusef and Richard Barnes. |
| 1855 |
|
| 1856 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span> |
| 1857 |
|
| 1858 |
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span> |
| 1859 |
|
| 1860 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 1861 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 1862 |
|
| 1863 |
[<a id="ref-RFC3261">RFC3261</a>] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, |
| 1864 |
A., Peterson, J., Sparks, R., Handley, M., and E. |
| 1865 |
Schooler, "SIP: Session Initiation Protocol", <a href="./rfc3261">RFC 3261</a>, |
| 1866 |
June 2002. |
| 1867 |
|
| 1868 |
[<a id="ref-RFC3264">RFC3264</a>] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model |
| 1869 |
with Session Description Protocol (SDP)", <a href="./rfc3264">RFC 3264</a>, June |
| 1870 |
2002. |
| 1871 |
|
| 1872 |
[<a id="ref-RFC4028">RFC4028</a>] Donovan, S. and J. Rosenberg, "Session Timers in the |
| 1873 |
Session Initiation Protocol (SIP)", <a href="./rfc4028">RFC 4028</a>, April 2005. |
| 1874 |
|
| 1875 |
[<a id="ref-RFC4566">RFC4566</a>] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session |
| 1876 |
Description Protocol", <a href="./rfc4566">RFC 4566</a>, July 2006. |
| 1877 |
|
| 1878 |
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span> |
| 1879 |
|
| 1880 |
[<a id="ref-RFC4235">RFC4235</a>] Rosenberg, J., Schulzrinne, H., and R. Mahy, "An INVITE- |
| 1881 |
Initiated Dialog Event Package for the Session Initiation |
| 1882 |
Protocol (SIP)", <a href="./rfc4235">RFC 4235</a>, November 2005. |
| 1883 |
|
| 1884 |
[<a id="ref-RFC4961">RFC4961</a>] Wing, D., "Symmetric RTP / RTP Control Protocol (RTCP)", |
| 1885 |
<a href="https://www.rfc-editor.org/bcp/bcp131">BCP 131</a>, <a href="./rfc4961">RFC 4961</a>, July 2007. |
| 1886 |
|
| 1887 |
[<a id="ref-RFC5245">RFC5245</a>] Rosenberg, J., "Interactive Connectivity Establishment |
| 1888 |
(ICE): A Protocol for Network Address Translator (NAT) |
| 1889 |
Traversal for Offer/Answer Protocols", <a href="./rfc5245">RFC 5245</a>, April |
| 1890 |
2010. |
| 1891 |
|
| 1892 |
[<a id="ref-RFC5359">RFC5359</a>] Johnston, A., Sparks, R., Cunningham, C., Donovan, S., and |
| 1893 |
K. Summers, "Session Initiation Protocol Service |
| 1894 |
Examples", <a href="https://www.rfc-editor.org/bcp/bcp144">BCP 144</a>, <a href="./rfc5359">RFC 5359</a>, October 2008. |
| 1895 |
|
| 1896 |
|
| 1897 |
|
| 1898 |
|
| 1899 |
|
| 1900 |
<span class="grey">Worley Informational [Page 34]</span></pre> |
| 1901 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span> |
| 1902 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 1903 |
|
| 1904 |
|
| 1905 |
[<a id="ref-RFC6337">RFC6337</a>] Okumura, S., Sawada, T., and P. Kyzivat, "Session |
| 1906 |
Initiation Protocol (SIP) Usage of the Offer/Answer |
| 1907 |
Model", <a href="./rfc6337">RFC 6337</a>, August 2011. |
| 1908 |
|
| 1909 |
[<a id="ref-ELWELL">ELWELL</a>] Elwell, J., "Subject: [Sipping] RE: I-D Action:<a href="./draft-worley-service-example-00.txt">draft-</a> |
| 1910 |
<a href="./draft-worley-service-example-00.txt">worley-service-example-00.txt</a>", message to the IETF |
| 1911 |
Sipping mailing list, November 2007, |
| 1912 |
<<a href="http://www1.ietf.org/mail-archive/web/sipping/current/msg14678.html">http://www1.ietf.org/mail-</a> |
| 1913 |
<a href="http://www1.ietf.org/mail-archive/web/sipping/current/msg14678.html">archive/web/sipping/current/msg14678.html</a>>. |
| 1914 |
|
| 1915 |
[<a id="ref-KYZIVAT-1">KYZIVAT-1</a>] |
| 1916 |
Kyzivat, P., "Subject: Re: [Sipping] I-D ACTION:<a href="./draft-ietf-sipping-service-examples-11.txt">draft-</a> |
| 1917 |
<a href="./draft-ietf-sipping-service-examples-11.txt">ietf-sipping-service-examples-11.txt</a>", message to the IETF |
| 1918 |
Sipping mailing list, October 2006, <<a href="http://www1.ietf.org/mail-archive/web/sipping/current/msg12181.html">http://www1.ietf.org/</a> |
| 1919 |
<a href="http://www1.ietf.org/mail-archive/web/sipping/current/msg12181.html">mail-archive/web/sipping/current/msg12181.html</a>>. |
| 1920 |
|
| 1921 |
[<a id="ref-KYZIVAT-2">KYZIVAT-2</a>] |
| 1922 |
Kyzivat, P., "Subject: [Sip-implementors] <a href="./draft-worley-service-example-02">draft-worley-</a> |
| 1923 |
<a href="./draft-worley-service-example-02">service-example-02</a>", message to the sip-implementors |
| 1924 |
mailing list, September 2008, |
| 1925 |
<<a href="http://lists.cs.columbia.edu/pipermail/sip-implementors/2008-September/020394.html">http://lists.cs.columbia.edu/pipermail/sip-implementors/</a> |
| 1926 |
<a href="http://lists.cs.columbia.edu/pipermail/sip-implementors/2008-September/020394.html">2008-September/020394.html</a>>. |
| 1927 |
|
| 1928 |
[<a id="ref-SHEKH-YUSEF">SHEKH-YUSEF</a>] |
| 1929 |
Shekh-Yusef, R., "Subject: [sipcore] <a href="./draft-worley-service-example-03">draft-worley-service-</a> |
| 1930 |
<a href="./draft-worley-service-example-03">example-03</a>", message to the IETF Sipcore mailing list, |
| 1931 |
July 2009, <<a href="http://www.ietf.org/mail-archive/web/sipcore/current/msg00580.html">http://www.ietf.org/mail-archive/web/sipcore/</a> |
| 1932 |
<a href="http://www.ietf.org/mail-archive/web/sipcore/current/msg00580.html">current/msg00580.html</a>>. |
| 1933 |
|
| 1934 |
[<a id="ref-SIPOS">SIPOS</a>] Sipos, A., "Subject: [Sip-implementors] <a href="./draft-worley-service-example-02">draft-worley-</a> |
| 1935 |
<a href="./draft-worley-service-example-02">service-example-02</a>", message to the sip-implementors |
| 1936 |
mailing list, March 2009, <<a href="http://lists.cs.columbia.edu/pipermail/sip-implementors/2009-March/021970.html">http://lists.cs.columbia.edu/</a> |
| 1937 |
<a href="http://lists.cs.columbia.edu/pipermail/sip-implementors/2009-March/021970.html">pipermail/sip-implementors/2009-March/021970.html</a>>. |
| 1938 |
|
| 1939 |
[<a id="ref-SIP-SERV-EX">SIP-SERV-EX</a>] |
| 1940 |
Johnston, A., Sparks, R., Cunningham, C., Donovan, S., and |
| 1941 |
K. Summers, "Session Initiation Protocol Service |
| 1942 |
Examples", Work in Progress, October 2006. |
| 1943 |
|
| 1944 |
[<a id="ref-VENKATESH">VENKATESH</a>] |
| 1945 |
Venkatesh, "Subject: Re: [Sipping] I-D ACTION:<a href="./draft-ietf-sipping-service-examples-11.txt">draft-</a> |
| 1946 |
<a href="./draft-ietf-sipping-service-examples-11.txt">ietf-sipping-service-examples-11.txt</a>", message to the IETF |
| 1947 |
Sipping mailing list, October 2006, <<a href="http://www1.ietf.org/mail-archive/web/sipping/current/msg12180.html">http://www1.ietf.org/</a> |
| 1948 |
<a href="http://www1.ietf.org/mail-archive/web/sipping/current/msg12180.html">mail-archive/web/sipping/current/msg12180.html</a>>. |
| 1949 |
|
| 1950 |
|
| 1951 |
|
| 1952 |
|
| 1953 |
|
| 1954 |
|
| 1955 |
|
| 1956 |
<span class="grey">Worley Informational [Page 35]</span></pre> |
| 1957 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span> |
| 1958 |
<span class="grey"><a href="./rfc7088">RFC 7088</a> Music on Hold February 2014</span> |
| 1959 |
|
| 1960 |
|
| 1961 |
Author's Address |
| 1962 |
|
| 1963 |
Dale R. Worley |
| 1964 |
Ariadne Internet Services, Inc. |
| 1965 |
738 Main St. |
| 1966 |
Waltham, MA 02451 |
| 1967 |
US |
| 1968 |
|
| 1969 |
Phone: +1 781 647 9199 |
| 1970 |
EMail: [email protected] |
| 1971 |
|
| 1972 |
|
| 1973 |
|
| 1974 |
|
| 1975 |
|
| 1976 |
|
| 1977 |
|
| 1978 |
|
| 1979 |
|
| 1980 |
|
| 1981 |
|
| 1982 |
|
| 1983 |
|
| 1984 |
|
| 1985 |
|
| 1986 |
|
| 1987 |
|
| 1988 |
|
| 1989 |
|
| 1990 |
|
| 1991 |
|
| 1992 |
|
| 1993 |
|
| 1994 |
|
| 1995 |
|
| 1996 |
|
| 1997 |
|
| 1998 |
|
| 1999 |
|
| 2000 |
|
| 2001 |
|
| 2002 |
|
| 2003 |
|
| 2004 |
|
| 2005 |
|
| 2006 |
|
| 2007 |
|
| 2008 |
|
| 2009 |
|
| 2010 |
|
| 2011 |
|
| 2012 |
Worley Informational [Page 36] |
| 2013 |
</pre> |