Re: AW: AW: [Sipping-tispan] Parallel Ringing

Paul Kyzivat <pkyzivat@cisco.com> Fri, 03 March 2006 15:12 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FFBx0-0007nK-Dc; Fri, 03 Mar 2006 10:12:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FFBwz-0007kk-0L for sipping-tispan@ietf.org; Fri, 03 Mar 2006 10:12:13 -0500
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FFBwx-0000JT-Om for sipping-tispan@ietf.org; Fri, 03 Mar 2006 10:12:12 -0500
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 03 Mar 2006 07:12:11 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="4.02,163,1139212800"; d="scan'208"; a="22928876:sNHT23725412"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k23FC9Wc013975; Fri, 3 Mar 2006 10:12:11 -0500 (EST)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 3 Mar 2006 10:12:09 -0500
Received: from [161.44.79.183] ([161.44.79.183]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 3 Mar 2006 10:12:09 -0500
Message-ID: <44085CC8.3000501@cisco.com>
Date: Fri, 03 Mar 2006 10:12:08 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Alexeitsev, D" <D.Alexeitsev@t-com.net>
Subject: Re: AW: AW: [Sipping-tispan] Parallel Ringing
References: <97A461F3EE5284469E41ED3728202F41023CAEA8@S4DE9JSAAMW.ost.t-com.de>
In-Reply-To: <97A461F3EE5284469E41ED3728202F41023CAEA8@S4DE9JSAAMW.ost.t-com.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 03 Mar 2006 15:12:09.0050 (UTC) FILETIME=[D72A4BA0:01C63ED4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: sipping-tispan@ietf.org
X-BeenThere: sipping-tispan@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of requirements for SIP introduced by ETSI TISPAN <sipping-tispan.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping-tispan>, <mailto:sipping-tispan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/sipping-tispan>
List-Post: <mailto:sipping-tispan@ietf.org>
List-Help: <mailto:sipping-tispan-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping-tispan>, <mailto:sipping-tispan-request@ietf.org?subject=subscribe>
Errors-To: sipping-tispan-bounces@ietf.org

Whether it is done via external means or not, it seems like this 
capability is *equivalent* to parallel forking. It *could* be achieved 
by defining a new AOR and REGISTERing to it, as contacts, the other AORs 
that are to be parallel forked.

	Paul

Alexeitsev, D wrote:
> Hello Dale
> 
> 
>>this sounds exactly like SIP parallel forking.  Why would parallel
>>forking have to be "activated"?
> 
> 
> In my understanding forking alerts only the contacts of a single AOR. Parallel ringing would alert a group of AORs. This group needs to be created somehow offline (no SIP procedure to create a group of AORs for alerting). This creation of the PRNG group I called activation.
> 
> Greetings,
> Denis
> 
> _______________________________________________
> Sipping-tispan mailing list
> Sipping-tispan@ietf.org
> https://www1.ietf.org/mailman/listinfo/sipping-tispan
> 

_______________________________________________
Sipping-tispan mailing list
Sipping-tispan@ietf.org
https://www1.ietf.org/mailman/listinfo/sipping-tispan