[Sip] Changing route set in SIP outbound
Avshalom Houri <AVSHALOM@il.ibm.com> Mon, 03 January 2011 15:23 UTC
Return-Path: <AVSHALOM@il.ibm.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 CF2DB3A69FA for <sip@core3.amsl.com>; Mon, 3 Jan 2011 07:23:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 UJmvHLqsvUwo for <sip@core3.amsl.com>; Mon, 3 Jan 2011 07:23:12 -0800 (PST)
Received: from mtagate4.uk.ibm.com (mtagate4.uk.ibm.com [194.196.100.164]) by core3.amsl.com (Postfix) with ESMTP id B13723A69F0 for <sip@ietf.org>; Mon, 3 Jan 2011 07:23:11 -0800 (PST)
Received: from d06nrmr1307.portsmouth.uk.ibm.com (d06nrmr1307.portsmouth.uk.ibm.com [9.149.38.129]) by mtagate4.uk.ibm.com (8.13.1/8.13.1) with ESMTP id p03FPHsc003166 for <sip@ietf.org>; Mon, 3 Jan 2011 15:25:17 GMT
Received: from d06av01.portsmouth.uk.ibm.com (d06av01.portsmouth.uk.ibm.com [9.149.37.212]) by d06nrmr1307.portsmouth.uk.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p03FPJlx3555398 for <sip@ietf.org>; Mon, 3 Jan 2011 15:25:19 GMT
Received: from d06av01.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av01.portsmouth.uk.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p03FPHfc027309 for <sip@ietf.org>; Mon, 3 Jan 2011 08:25:17 -0700
Received: from d12mc102.megacenter.de.ibm.com (d12nrml1506.megacenter.de.ibm.com [9.149.164.56] (may be forged)) by d06av01.portsmouth.uk.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p03FPGci027302; Mon, 3 Jan 2011 08:25:17 -0700
To: sip@ietf.org
MIME-Version: 1.0
X-KeepSent: 9E7C0622:288AC539-C225780D:005405A1; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.2 August 10, 2010
From: Avshalom Houri <AVSHALOM@il.ibm.com>
Message-ID: <OF9E7C0622.288AC539-ONC225780D.005405A1-C225780D.0054B652@il.ibm.com>
Date: Mon, 03 Jan 2011 17:25:18 +0200
X-MIMETrack: Serialize by Router on D12MC102/12/M/IBM(Release 8.5.1FP4|July 25, 2010) at 03/01/2011 17:25:19, Serialize complete at 03/01/2011 17:25:19
Content-Type: multipart/alternative; boundary="=_alternative 00545D46C225780D_="
Cc: fluffy@cisco.com, rohan@ekabal.com, francois.audet@skypelabs.com
Subject: [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:23:12 -0000
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. tnx avshalom
- [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)