--- 1/draft-ietf-sipcore-rfc4244bis-callflows-03.txt 2013-07-08 13:14:25.346321345 -0700 +++ 2/draft-ietf-sipcore-rfc4244bis-callflows-04.txt 2013-07-08 13:14:25.430323310 -0700 @@ -1,25 +1,25 @@ SIPCORE M. Barnes Internet-Draft Polycom Intended status: Informational F. Audet -Expires: September 2, 2013 Skype +Expires: January 2, 2014 Skype S. Schubert NTT H. van Elburg Detecon International Gmbh C. Holmberg Ericsson - Mar 2013 + Jul 2013 Session Initiation Protocol (SIP) History-Info Header Call Flow Examples - draft-ietf-sipcore-rfc4244bis-callflows-03.txt + draft-ietf-sipcore-rfc4244bis-callflows-04.txt Abstract This document describes use cases and documents call flows which require the History-Info header field to capture the Request-URIs as a Session Initiation Protocol (SIP) Request is retargeted. The use cases are described along with the corresponding call flow diagrams and messaging details. Status of this Memo @@ -30,21 +30,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on September 2, 2013. + This Internet-Draft will expire on January 2, 2014. Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -159,21 +159,21 @@ | | 100 Trying F10 | | |<-----------------------------------| | | 486 Busy Here F11 | | |<-----------------------------------| | 486 Busy Here F12 | |<-----------| ACK F13 | | |----------------------------------->| | ACK F14 | | |----------->| | - Figure 1: Figure 1: Example with Sequential Forking + Figure 1: Example with Sequential Forking Message Details F1 INVITE alice -> example.com INVITE sip:bob@example.com SIP/2.0 Via: SIP/2.0/TCP 192.0.2.3:5060;branch=z9hG4bK4321 Max-Forward: 70 From: Alice ;tag=sr3dds To: Bob @@ -286,43 +286,43 @@ Via: SIP/2.0/TCP 192.0.2.3:5060;branch=z9hG4bK4321 From: Alice ;tag=sr3dds To: Bob ;tag=53rdds Supported: histinfo Call-Id: 12345600@example.com Record-Route: History-Info: ;index=1 History-Info: ;\ index=1.1;rc=1 History-Info: ;index=1.2;mp=1 - History-Info: ;\ - index=1.2.1;rc=1.2 + History-Info: ;index=1.2.1;rc=1.2 CSeq: 1 INVITE Contact: Office Content-Length: 0 F9 INVITE example.com -> home INVITE sip:home@192.0.2.6 SIP/2.0 Via: SIP/2.0/TCP proxy.example.com:5060;branch=z9hG4bKx5st Via: SIP/2.0/TCP 192.0.2.3:5060;branch=z9hG4bK4321 Max-Forward: 69 From: Alice ;tag=sr3dds To: Bob Supported: histinfo Call-Id: 12345600@example.com Record-Route: History-Info: ;index=1 History-Info: ;\ index=1.1;rc=1 - History-Info: ;index=1.2;mp=1 + History-Info: ;\ + index=1.2;mp=1 History-Info: ;\ - index=1.2.1;index=1.2.1;rc=1.2 + index=1.2.1;rc=1.2 History-Info: ;index=1.3;mp=1 History-Info: ;index=1.3.1;rc=1.3 CSeq: 1 INVITE Contact: Alice Content-Type: application/sdp Content-Length: F10 100 Trying home -> example.com SIP/2.0 100 Trying @@ -338,21 +338,22 @@ SIP/2.0 486 Busy Here Via: SIP/2.0/TCP proxy.example.com:5060;branch=z9hG4bKx5st Via: SIP/2.0/TCP 192.0.2.3:5060;branch=z9hG4bK4321 From: Alice ;tag=sr3dds To: Bob ;tag=55rdds Call-Id: 12345600@example.com History-Info: ;index=1 History-Info: ;\ index=1.1;rc=1 - History-Info: ;index=1.2;mp=1 + History-Info: ;\ + index=1.2;mp=1 History-Info: ;\ index=1.2.1;index=1.2.1;rc=1.2 History-Info: ;index=1.3;mp=1 History-Info: ;index=1.3.1;rc=1.3 CSeq: 1 INVITE Content-Length: 0 F12 486 Busy Here example.com -> alice SIP/2.0 486 Busy Here Via: SIP/2.0/TCP 192.0.2.3:5060;branch=z9hG4bK4321 @@ -422,21 +423,21 @@ | | 200 F5 | | | |<---------------| | | | | | | 200 F6 | | | |<---------------| | | | | | | | | ACK | | |------------------------------------------------->| | | | | - Figure 2: Figure 2: Example with Privacy Header Fields + Figure 2: Example with Privacy Header Fields Message Details F1 INVITE alice -> atlanta.example.com INVITE sip:bob@biloxi.example.com;p=x SIP/2.0 Via: SIP/2.0/TCP 192.0.2.3:5060;branch=z9hG4bK4321 Max-Forward: 70 From: Alice ;tag=22 To: Bob @@ -570,22 +571,21 @@ | | 200 F5 | | | |<---------------| | | | | | | 200 F6 | | | |<---------------| | | | | | | | | ACK | | |------------------------------------------------->| | | | | - Figure 3: Figure 3: Example with Privacy Header Field for Specific - URI + Figure 3: Example with Privacy Header Field for Specific URI Message Details F1 INVITE alice -> atlanta.example.com INVITE sip:bob@biloxi.example.com;p=x SIP/2.0 Via: SIP/2.0/TCP 192.0.2.3:5060;branch=z9hG4bK4321 Max-Forward: 70 From: Alice ;tag=22 To: Bob @@ -845,21 +845,21 @@ received=192.0.2.101 Via: SIP/2.0/TCP 192.0.2.3:5060;branch=z9hG4bK42t2 Max-Forward: 68 From: Alice ;tag=1235 To: Gold Member Assistance Supported: histinfo Call-Id: 12345600@example.com CSeq: 1 INVITE History-Info: ;index=1 History-Info: ;\ - index=1.1 + rc=1;index=1.1 History-Info: ;index=1.2;mp=1 History-Info: ;index=1.2.1;rc=1.2 History-Info: ;index=1.2.1.1;rc=1.2.1 Contact: Alice Content-Type: application/sdp Content-Length: [SDP Not Shown] F6 200 OK Agent -> Silver.Example.com @@ -870,21 +870,21 @@ Via: SIP/2.0/TCP proxy.example.com:5060;branch=z9hG4bK45q2;\ received=192.0.2.101 Via: SIP/2.0/TCP 192.0.2.3:5060;branch=z9hG4bK42t2 From: Alice ;tag=1235 To: Gold Member Assistance ;tag=2325 Supported: histinfo Call-Id: 12345600@example.com CSeq: 1 INVITE History-Info: ;index=1 History-Info: ;\ - index=1.1 + rc=1;index=1.1 History-Info: ;index=1.2;mp=1 History-Info: ;index=1.2.1;rc=1.2 History-Info: ;index=1.2.1.1;rc=1.2.1 Contact: Agent Content-Type: application/sdp Content-Length: [SDP Not Shown] F7 200 OK Silver.Example.com -> Example.com @@ -893,41 +893,41 @@ Via: SIP/2.0/TCP proxy.example.com:5060;branch=z9hG4bK45q2;\ received=192.0.2.101 Via: SIP/2.0/TCP 192.0.2.3:5060;branch=z9hG4bK42t2 From: Alice ;tag=1235 To: Gold Member Assistance ;tag=2325 Supported: histinfo Call-Id: 12345600@example.com CSeq: 1 INVITE History-Info: ;index=1 History-Info: ;\ - index=1.1 + rc=1;index=1.1 History-Info: ;index=1.2;mp=1 History-Info: ;index=1.2.1;rc=1.2 History-Info: ;index=1.2.1.1;rc=1.2.1 Contact: Agent Content-Type: application/sdp Content-Length: [SDP Not Shown] F8 200 OK Example.com -> Alice SIP/2.0 200 OK Via: SIP/2.0/TCP 192.0.2.3:5060;branch=z9hG4bK42t2 From: Alice ;tag=1235 To: Gold Member Assistance ;tag=2325 Supported: histinfo Call-Id: 12345600@example.com CSeq: 1 INVITE History-Info: ;index=1 History-Info: ;\ - index=1.1 + rc=1;index=1.1 History-Info: ;index=1.2;mp=1 History-Info: ;index=1.2.1;rc=1.2 History-Info: ;index=1.2.1.1;rc=1.2.1 Contact: Agent Content-Type: application/sdp Content-Length: [SDP Not Shown] F9 ACK Alice -> Agent @@ -939,21 +939,21 @@ To: Gold Member Assistance ;tag=2325 Supported: histinfo Call-Id: 12345600@example.com CSeq: 1 ACK Contact: Alice Content-Type: application/sdp Content-Length: [SDP Not Shown] - Figure 4: Figure 4: Example for Automatic Call Distribution + Figure 4: Example for Automatic Call Distribution The first hi-entry with the "mp" header field parameter contains a "mp" header field parameter value of 1 which points to the original- target which allows the operator to identify that the call was from the "Gold" customer. 3.5. Determining the Alias used. SIP user agents are associated with an address-of-record (AOR). It is possible for a single UA to actually have multiple AORs associated @@ -1044,21 +1044,21 @@ Call-Id: 12345600@example.com CSeq: 1 INVITE Record-Route: History-Info: ;index=1 History-Info: ;index=1.1;rc=1 Contact: Alice Content-Type: application/sdp Content-Length: [SDP Not Shown] - Figure 5: Figure 5: Alias Example + Figure 5: Alias Example The last hi-entry with the "rc" header field parameter references the source of retargeting pointing at the alias AoR, which in the example is "john.smith@example.com". 3.6. PBX Voicemail Example A typical use case for voicemail is one whereby the original called party is not reachable and the call arrives at a voicemail system. In some cases multiple alternate destinations may be tried without @@ -1186,44 +1186,44 @@ Via: SIP/2.0/TCP 192.0.2.3:5060;branch=z9hG4bK42t2 Max-Forward: 69 From: Alice ;tag=kkaz- To: Bob Supported: histinfo Call-Id: 12345600@example.com CSeq: 1 INVITE History-Info: ;index=1 History-Info: ;\ index=1.1;rc=1 - History-Info: ;index=1.2;mp=1 - History-Info: ;index=1.2.1;rc=1.2 + History-Info: ;index=1.2;mp=1 + History-Info: ;index=1.2.1;rc=1.2 Contact: Alice Content-Type: application/sdp Content-Length: [SDP Not Shown] F5 180 Ringing Carol -> Example.com SIP/2.0 180 Ringing Via: SIP/2.0/TCP proxy.example.com:5060;branch=z9hG4bK4522;\ received=192.0.2.101 Via: SIP/2.0/TCP 192.0.2.3:5060;branch=z9hG4bK42t2 From: Alice ;tag=kkaz- To: Bob ;tag=setss3x Supported: histinfo Call-Id: 12345600@example.com CSeq: 1 INVITE History-Info: ;index=1 History-Info: ;\ index=1.1;rc=1 - History-Info: ;index=1.2;mp=1 - History-Info: ;index=1.2.1;rc=1.2 + History-Info: ;index=1.2;mp=1 + History-Info: ;index=1.2.1;rc=1.2 Contact: Content-Type: application/sdp Content-Length: [SDP Not Shown] F6 INVITE Example.com -> VM INVITE sip:vm@192.0.2.6;target=sip:bob%40example.com;cause=480\ SIP/2.0 @@ -1231,23 +1231,25 @@ Via: SIP/2.0/TCP 192.0.2.3:5060;branch=z9hG4bK42t2 Max-Forward: 69 From: Alice ;tag=kkaz- To: Bob Supported: histinfo Call-Id: 12345600@example.com CSeq: 1 INVITE History-Info: ;index=1 History-Info: ;\ index=1.1;rc=1 - History-Info: ;index=1.2;mp=1 - History-Info: ;\ - index=1.2.1;rc=1.2 + History-Info: ;index=1.2;mp=1 + + History-Info: ;index=1.2.1;rc=1.2 History-Info: ;\ index=1.3;mp=1 History-Info: ;\ index=1.3.1;rc=1.3 Contact: Alice Content-Type: application/sdp Content-Length: @@ -1276,21 +1278,21 @@ index=1.3;mp=1 History-Info: ;\ index=1.3.1;rc=1.3 Contact: Content-Type: application/sdp Content-Length: [SDP Not Shown] - Figure 6: Figure 6: Enterprise Voivemail Example + Figure 6: Enterprise Voivemail Example The VMS can look at the last hi-entry and find the target of the mailbox by looking at the URI entry in the "target" URI parameter in the hi-entry. 3.7. Consumer Voicemail Example In the case of a consumer, when the call is retargeted, it is usually to another administrative domain. The voicemail system in these environment typically requires the last called party information to @@ -1406,21 +1408,21 @@ Via: SIP/2.0/TCP proxy.example.com:5060;branch=z9hG4bK24s5 Via: SIP/2.0/TCP 192.0.2.3:5060;branch=z9hG4bK42t2 Max-Forward: 69 From: Alice ;tag=kkaz- To: Bob Supported: histinfo Call-Id: 12345600@example.com CSeq: 1 INVITE History-Info: ;index=1 History-Info: \ + %3Btext%3D%22Moved%20Temporarily%22>>\ ;index=1.1;rc=1 History-Info: ;index=1.2;mp=1 History-Info: ;index=1.2.1;rc=1.2 Contact: Alice Content-Type: application/sdp Content-Length: [SDP Not Shown] F5 180 Ringing Carol -> Example.com @@ -1429,21 +1431,21 @@ Via: SIP/2.0/TCP proxy.example.com:5060;branch=z9hG4bK24s5;\ received=192.0.2.101 Via: SIP/2.0/TCP 192.0.2.3:5060;branch=z9hG4bK42t2 From: Alice ;tag=kkaz- To: Bob ;tag=setss3x Supported: histinfo Call-Id: 12345600@example.com CSeq: 1 INVITE History-Info: ;index=1 History-Info: \ + %3Btext%3D%22Moved%20Temporarily%22>">\ ;index=1.1;rc=1 History-Info: ;index=1.2;mp=1 History-Info: ;index=1.2.1;rc=1.2 Contact: Content-Type: application/sdp Content-Length: [SDP Not Shown] F6 INVITE Example.com -> VM @@ -1452,29 +1454,30 @@ Via: SIP/2.0/TCP proxy.example.com:5060;branch=z9hG4bKbbg4 Via: SIP/2.0/TCP 192.0.2.3:5060;branch=z9hG4bK42t2 Max-Forward: 69 From: Alice ;tag=kkaz- To: Bob Supported: histinfo Call-Id: 12345600@example.com CSeq: 1 INVITE History-Info: ;index=1 History-Info: \ + %3Btext%3D%22Moved%20Temporarily%22>>\ ;index=1.1;rc=1 History-Info: ;\ index=1.2;mp=1 History-Info: ;index=1.2.1;rc=1.2 - History-Info: ;\ - index=1.3;mp=1.2 + History-Info: \ + ; + index=1.2.2;mp=1.2 History-Info: \ - ;cause=408;index=1.3.1;rc=1.3 + ;cause=408;index=1.2.2.1;rc=1.3 Contact: Alice Content-Type: application/sdp Content-Length: [SDP Not Shown] F7 200 OK VM -> Example.com SIP/2.0 200 OK Via: SIP/2.0/TCP proxy.example.com:5060;branch=z9hG4bKbbg4 Via: SIP/2.0/TCP 192.0.2.3:5060;branch=z9hG4bK42t2 @@ -1487,28 +1490,28 @@ History-Info: \ ;index=1.1;rc=1 History-Info: ;\ index=1.2;mp=1 History-Info: ;\ index=1.2.1;rc=1.2 History-Info: ;\ index=1.2.2;mp=1.2 History-Info: ;\ - index=1.2.2;rc=1.2.1 + index=1.2.2.1;rc=1.2.2 Contact: Content-Type: application/sdp Content-Length: [SDP Not Shown] - Figure 7: Figure 7: Consumer Voivemail Example + Figure 7: Consumer Voivemail Example The VMS can look at the last hi-entry and find the target of the mailbox by looking for the "target" URI parameter in the hi-entry and the reason by the "cause" URI parameter in the same hi-entry. 3.8. GRUU A variation on the problem in Section 3.5 occurs with Globally Routable User Agent URI (GRUU) [RFC5627]. A GRUU is a URI assigned to a UA instance which has many of the same properties as the AOR, @@ -1620,21 +1623,21 @@ Record-Route: History-Info: ;index=1 History-Info: ;index=1.1;rc=1 Contact: Alice Content-Type: application/sdp Content-Length: [SDP Not Shown] - Figure 8: Figure 8: GRUU Example + Figure 8: GRUU Example By analyzing the entry referenced by the entry with the last "rc", one can realize that the URI used to reach the device was GRUU by finding the "gr" parameter. 3.9. Limited Use Address A limited use address is a SIP URI that is minted on-demand, and passed out to a small number (usually one) remote correspondent. Incoming calls targeted to that limited use address are accepted as @@ -1742,21 +1745,21 @@ CSeq: 1 INVITE Record-Route: History-Info: \ \ ;index=1 History-Info: ;index=1.1;rc=1 Contact: Alice Content-Type: application/sdp Content-Length: - Figure 9: Figure 9: Limited Use Address Example + Figure 9: Limited Use Address Example By analyzing the entry referenced by the entry with the last "rc", one can realize that the URI used to reach the device was GRUU by finding the "gr" parameter. 3.10. Service Invocation Several SIP specifications have been developed which make use of complex URIs to address services within the network rather than subscribers. The URIs are complex because they contain numerous @@ -1889,21 +1892,21 @@ History-Info: ;index=1 History-Info: ;index=1.1;mp=1 History-Info: ;index=1.1.1;rc=1.1 History-Info: ;index=1.1.1.1;rc=1.1.1 Contact: Content-Type: application/sdp Content-Length: [SDP Not Shown] - Figure 10: Figure 10: Service Number Example + Figure 10: Service Number Example 4. Security Considerations The security considerations for the History-Info header field are specified in [I-D.ietf-sipcore-rfc4244bis]. 5. IANA Considerations This document has no IANA considerations.