Re: [Sip] Changing route set in SIP outbound
Dean Willis <dean.willis@softarmor.com> Sat, 05 February 2011 06:02 UTC
Return-Path: <dean.willis@softarmor.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 67FE23A69FF for <sip@core3.amsl.com>; Fri, 4 Feb 2011 22:02:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.474
X-Spam-Level:
X-Spam-Status: No, score=-103.474 tagged_above=-999 required=5 tests=[AWL=0.124, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, 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 Sud8R4Gd2tMh for <sip@core3.amsl.com>; Fri, 4 Feb 2011 22:02:40 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id 62A523A69CA for <sip@ietf.org>; Fri, 4 Feb 2011 22:02:40 -0800 (PST)
Received: by gyd12 with SMTP id 12so1339637gyd.31 for <sip@ietf.org>; Fri, 04 Feb 2011 22:06:06 -0800 (PST)
Received: by 10.91.8.20 with SMTP id l20mr16301805agi.147.1296885966741; Fri, 04 Feb 2011 22:06:06 -0800 (PST)
Received: from [192.168.2.102] (cpe-66-25-6-220.tx.res.rr.com [66.25.6.220]) by mx.google.com with ESMTPS id d15sm1909767ana.35.2011.02.04.22.06.02 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 04 Feb 2011 22:06:05 -0800 (PST)
References: <OF9E7C0622.288AC539-ONC225780D.005405A1-C225780D.0054B652@il.ibm.com>
In-Reply-To: <OF9E7C0622.288AC539-ONC225780D.005405A1-C225780D.0054B652@il.ibm.com>
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary="Apple-Mail-2-751181776"
Message-Id: <08DF4251-141D-4C76-8580-34E78A7C23DE@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
Date: Sat, 05 Feb 2011 00:06:01 -0600
To: Avshalom Houri <AVSHALOM@il.ibm.com>
X-Mailer: Apple Mail (2.1082)
Cc: sip@ietf.org, fluffy@cisco.com, francois.audet@skypelabs.com, rohan@ekabal.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: Sat, 05 Feb 2011 06:02:41 -0000
On Jan 3, 2011, at 9:25 AM, Avshalom Houri wrote: > 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. Well, if the proxies share credentials and an IP address by some HSRP-like magic, then the dialog might reasonably stay alive. This further requires either stateless operation or state sharing ( embedded state; encoding it into the message headers is an example) between the proxies. This is analogous to the route-set failover question in many a routing model: flow switching, MPLS, frame relay, ATM, or even Token-Ring. SIP has no magic to cure the fundamental issue. At best we can reduce it to a known problem. -- Dean
- [Sip] Changing route set in SIP outbound Avshalom Houri
- Re: [Sip] Changing route set in SIP outbound Worley, Dale R (Dale)
- Re: [Sip] Changing route set in SIP outbound aayush
- Re: [Sip] Changing route set in SIP outbound Nataraju A.B
- Re: [Sip] Changing route set in SIP outbound Dean Willis
- Re: [Sip] Changing route set in SIP outbound Worley, Dale R (Dale)