[sipcore] 4244bis -- some examples
"Worley, Dale R (Dale)" <dworley@avaya.com> Fri, 01 October 2010 17:08 UTC
Return-Path: <dworley@avaya.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 87A693A6C38 for <sipcore@core3.amsl.com>; Fri, 1 Oct 2010 10:08:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.165
X-Spam-Level:
X-Spam-Status: No, score=-102.165 tagged_above=-999 required=5 tests=[AWL=-0.166, BAYES_00=-2.599, J_CHICKENPOX_31=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VGorwjcswszz for <sipcore@core3.amsl.com>; Fri, 1 Oct 2010 10:08:19 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 3A29D3A6C32 for <sipcore@ietf.org>; Fri, 1 Oct 2010 10:08:19 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.57,267,1283745600"; d="scan'208";a="210108813"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 01 Oct 2010 13:09:06 -0400
X-IronPort-AV: E=Sophos;i="4.57,267,1283745600"; d="scan'208";a="522274884"
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by co300216-co-erhwest-out.avaya.com with ESMTP; 01 Oct 2010 13:09:05 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.129]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Fri, 1 Oct 2010 13:09:05 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "sipcore@ietf.org" <sipcore@ietf.org>
Date: Fri, 01 Oct 2010 13:07:54 -0400
Thread-Topic: 4244bis -- some examples
Thread-Index: AQHLYYtaYnyss8b4ikW+oiKQOCM0AA==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B21FFC79C96@DC-US1MBEX4.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [sipcore] 4244bis -- some examples
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Oct 2010 17:08:21 -0000
Four typical cases of redirection, showing the resulting History-Info
entries in the generated requests, per
draft-ietf-sipcore-rfc4244bis-01. The final case, which
combines features of the first three cases, is typical for the
sipXecs/SCS system.
Incoming request has header: History-Info: hhh
The final hi-entry in hhh has hi-index "xxx".
Case 1: Request is forwarded to 3 destinations.
Destinations are sip:A (rc), sip:B (mp), and sip:C.
Outgoing request to A:
History-Info: hhh,
<sip:A>;index=xxx.1;rc
Outgoing request to B:
History-Info: hhh,
<sip:B>;index=xxx.2;mp=xxx
Outgoing request to C:
History-Info: hhh,
<sip:C>;index=xxx.3
Case 2: Request is forwarded to 3 destinations due to 302 response from
redirect server.
Redirect server is sip:R.
Outgoing request to redirect server:
History-Info: hhh,
<sip:R>;index=xxx.1
Incoming response from redirect server: [same]
Destinations in 302 are <sip:A;hit=rc>, <sip:B;hit=mp>, and <sip:C>.
Outgoing request to A:
History-Info: hhh,
<sip:R?Reason=SIP%3bcause%3d302>;index=xxx.1,
<sip:A>;index=xxx.2;rc
[%3b is ';'. %3d is '='.]
Outgoing request to B:
History-Info: hhh,
<sip:R?Reason=SIP%3bcause%3d302>;index=xxx.1,
<sip:B>;index=xxx.3;mp=xxx.1
Outgoing request to C:
History-Info: hhh,
<sip:R?Reason=SIP%3bcause%3d302>;index=xxx.1,
<sip:C>;index=xxx.4
Case 3: Request forwarded to one destination due to failure of a fork
to another destination.
Destinations are sip:A (rc), falling back to sip:B.
Outgoing request to A:
History-Info: hhh,
<sip:A>;index=xxx.1;rc
Outgoing request to B:
History-Info: hhh,
<sip:A?Reason=SIP%3bcause%3d487>;index=xxx.1;rc,
<sip:B>;index=xxx.2
[%3b is ';'. %3d is '='.]
Case 4: Request is sent to redirect server which provides 3
destinations, one of which is low priority.
Redirect server is sip:R.
Outgoing request to redirect server:
History-Info: hhh,
<sip:R>;index=xxx.1
Incoming response from redirect server: [same]
Destinations in 302 are <sip:A;hit=rc>, <sip:B;hit=mp>, and <sip:C>;q=0.1.
Outgoing request to A:
History-Info: hhh,
<sip:R?Reason=SIP%3bcause%3d302>;index=xxx.1,
<sip:A>;index=xxx.2;rc
[%3b is ';'. %3d is '='.]
Outgoing request to B:
History-Info: hhh,
<sip:R?Reason=SIP%3bcause%3d302>;index=xxx.1,
<sip:B>;index=xxx.3;mp=xxx.1
Outgoing request to C:
History-Info: hhh,
<sip:R?Reason=SIP%3bcause%3d302>;index=xxx.1,
<sip:A?Reason=SIP%3bcause%3d487>;index=xxx.2;rc,
<sip:B?Reason=SIP%3bcause%3d487>;index=xxx.3;mp=xxx.1,
<sip:C>;index=xxx.4
- [sipcore] 4244bis -- some examples Worley, Dale R (Dale)
- Re: [sipcore] 4244bis -- some examples Worley, Dale R (Dale)