IETF Logo Mail Archive

Re: [Sip] Changing route set in SIP outbound

"Worley, Dale R (Dale)" <dworley@avaya.com> Mon, 03 January 2011 15:26 UTC

Return-Path: <dworley@avaya.com>
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E18C03A69EC for <sip@core3.amsl.com>; Mon, 3 Jan 2011 07:26:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.506
X-Spam-Level:
X-Spam-Status: No, score=-102.506 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_00=-2.599, 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 1LE1+9HJnuEO for <sip@core3.amsl.com>; Mon, 3 Jan 2011 07:26:46 -0800 (PST)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (p-us1-iereast-outbound-tmp.us1.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id 4EF563A6981 for <sip@ietf.org>; Mon, 3 Jan 2011 07:26:46 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAAt6IU2HCzI1/2dsb2JhbACkNHOlAQKWN4VKBIRliVY
X-IronPort-AV: E=Sophos;i="4.60,267,1291611600"; d="scan'208";a="52631236"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 03 Jan 2011 10:28:50 -0500
X-IronPort-AV: E=Sophos;i="4.60,267,1291611600"; d="scan'208";a="576112822"
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 03 Jan 2011 10:28:20 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.90]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Mon, 3 Jan 2011 10:28:20 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Avshalom Houri <AVSHALOM@il.ibm.com>, "sip@ietf.org" <sip@ietf.org>
Date: Mon, 03 Jan 2011 10:26:35 -0500
Thread-Topic: [Sip] Changing route set in SIP outbound
Thread-Index: AcurWnai1dk3z8n9SsmNgTGsfRYPxAAACSeC
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B2202288B29@DC-US1MBEX4.global.avaya.com>
References: <OF9E7C0622.288AC539-ONC225780D.005405A1-C225780D.0054B652@il.ibm.com>
In-Reply-To: <OF9E7C0622.288AC539-ONC225780D.005405A1-C225780D.0054B652@il.ibm.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
Cc: "fluffy@cisco.com" <fluffy@cisco.com>, "rohan@ekabal.com" <rohan@ekabal.com>, "francois.audet@skypelabs.com" <francois.audet@skypelabs.com>
Subject: Re: [Sip] Changing route set in SIP outbound
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jan 2011 15:26:48 -0000

________________________________________
From: sip-bounces@ietf.org [sip-bounces@ietf.org] On Behalf Of Avshalom Houri [AVSHALOM@il.ibm.com]

Assume that the first SIP proxy that is part of the route set (in SIP outbound)
crashes and immediately restarts, or a backup proxy takes over. Is there any way to keep the dialog alive if either of the
endpoints senses this failure and recreates a connection or the dialog is doomed and needs to be
fully recreated again? The issue is that the route set includes the connection information, which is no longer valid.
________________________________________

As you phrase the question, the *dialog* cannot be kept alive if the connection in question is lost because the route set cannot be changed.

Dale

v2.23.0 | Report a Bug | By Email