IETF Logo Mail Archive

Re: [Sip] Changing route set in SIP outbound

"Nataraju A.B" <nataraju.sip@gmail.com> Tue, 04 January 2011 13:34 UTC

Return-Path: <nataraju.sip@gmail.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 595573A6C18 for <sip@core3.amsl.com>; Tue, 4 Jan 2011 05:34:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.114
X-Spam-Level:
X-Spam-Status: No, score=-2.114 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_LOW=-1]
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 dI2uzHNExUkD for <sip@core3.amsl.com>; Tue, 4 Jan 2011 05:34:27 -0800 (PST)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by core3.amsl.com (Postfix) with ESMTP id B97DC3A6C0D for <sip@ietf.org>; Tue, 4 Jan 2011 05:34:27 -0800 (PST)
Received: by pwi7 with SMTP id 7so2470278pwi.31 for <sip@ietf.org>; Tue, 04 Jan 2011 05:36:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=p8Cw0o9hIwOwEinT6uxTQJGVo3vPnp9ddLmdOlq63Xs=; b=kBV9nGF/3IRkAqR2Sgs96Amll/4HHpkBVi2pqtpnkqxK0za4P5X+5OnZI/kWZ/LsXG jzSr3sxg8s+Gg1eisrt+yakqTQrhDgOjD7fL85rOKkHKcp4jUrsYkrSdUjB7+c8zdhC3 JOOUiWafRfmexRkE3IX6z2g1z/cqYuHkf7Et0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=iyye1FvEe9SYWxqKbLC9Tz5+niYnUv0mSXBAU8z8kj3uUvmYB0TdMANcDNj8M3cGiE 62RZSEakHC7tUGP9lzmLG3eCqICIrxI6G2mTSDACtdt446aMdwjnn79zcRAp9NgwwWKb O5ib/zb58fza2pP0eZkv++64rpmbVJT+vi7Lg=
MIME-Version: 1.0
Received: by 10.142.203.16 with SMTP id a16mr17709790wfg.144.1294148194734; Tue, 04 Jan 2011 05:36:34 -0800 (PST)
Received: by 10.143.18.13 with HTTP; Tue, 4 Jan 2011 05:36:34 -0800 (PST)
In-Reply-To: <AANLkTinDTOgJX8pKDSamOqW3_fhYMqXw3bHSpHzwwzbP@mail.gmail.com>
References: <OF9E7C0622.288AC539-ONC225780D.005405A1-C225780D.0054B652@il.ibm.com> <CD5674C3CD99574EBA7432465FC13C1B2202288B29@DC-US1MBEX4.global.avaya.com> <AANLkTinDTOgJX8pKDSamOqW3_fhYMqXw3bHSpHzwwzbP@mail.gmail.com>
Date: Tue, 04 Jan 2011 19:06:34 +0530
Message-ID: <AANLkTi=idceDZS6dRHHTbHLh5coFj7x0XLhv=kiOHtHX@mail.gmail.com>
From: "Nataraju A.B" <nataraju.sip@gmail.com>
To: aayush <abhatnagar192006@gmail.com>
Content-Type: multipart/alternative; boundary="000e0cd158326f13a90499055bca"
Cc: "fluffy@cisco.com" <fluffy@cisco.com>, "rohan@ekabal.com" <rohan@ekabal.com>, "sip@ietf.org" <sip@ietf.org>, "francois.audet@skypelabs.com" <francois.audet@skypelabs.com>, Avshalom Houri <AVSHALOM@il.ibm.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: Tue, 04 Jan 2011 13:34:29 -0000

AFAIU, Any proxy which forms part of the route-set during call setup. It
must support backup and recovery mechanism.

One simple  example where the proxy supports billing functionality could be
part of the route-set and it shall support back and recovery. In this case
it shall back back up all the necessary data to recover if there is any
failure in the active unit. Otherwise it does not make sense to to be part
of a route-set.


On Mon, Jan 3, 2011 at 9:10 PM, aayush <abhatnagar192006@gmail.com> wrote:

> The route set cannot be changed mid dialog.
>
> Regarding the endpoint detecting the crash of an intermediate proxy,there
> is a periodic session refresh mechanism available in SIP which the endpoint
> must support.
>
> This mechanism is implemented by examining the Session-Expires and Min-SE
> headers.
>
> Conversely if a backup proxy takes over the crashed one, then both proxies
> (Active-Stabdby) must support Virtual IP failover for implementing this
> fault tolerance use case.
>
> On Jan 3, 2011 8:59 PM, "Worley, Dale R (Dale)" <dworley@avaya.com> wrote:
>
> ________________________________________
> 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 immedia...
>
> ________________________________________
>
> 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
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is essentially closed and only used for finishing old business.
> Use sip-implementors@cs.columbia.edu for questions on how to develop a SIP
> implementation.
> Use dispatch@ietf.org for new developments on the application of sip.
> Use sipcore@ietf.org for issues related to maintenance of the core SIP
> specifications.
>
>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is essentially closed and only used for finishing old business.
> Use sip-implementors@cs.columbia.edu for questions on how to develop a SIP
> implementation.
> Use dispatch@ietf.org for new developments on the application of sip.
> Use sipcore@ietf.org for issues related to maintenance of the core SIP
> specifications.
>



-- 
Thanks,
Nataraju A.B.

v2.23.0 | Report a Bug | By Email