AW: AW: [Sipping-tispan] Parallel Ringing

"Alexeitsev, D" <D.Alexeitsev@t-com.net> Fri, 03 March 2006 10:10 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FF7FM-00074v-4u; Fri, 03 Mar 2006 05:10:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FF7FL-00070E-DA for sipping-tispan@ietf.org; Fri, 03 Mar 2006 05:10:51 -0500
Received: from tcmail22.telekom.de ([217.6.95.236]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FF7FJ-0005nY-WE for sipping-tispan@ietf.org; Fri, 03 Mar 2006 05:10:51 -0500
Received: from g9jbr.mgb01.telekom.de (g9jbr.mgb01.telekom.de [164.20.31.6]) by tcmail21.dmz.telekom.de with ESMTP; Fri, 3 Mar 2006 11:10:47 +0100
Received: by G9JBR.mgb01.telekom.de with Internet Mail Service (5.5.2653.19) id <FXTF01WV>; Fri, 3 Mar 2006 11:10:46 +0100
Message-Id: <97A461F3EE5284469E41ED3728202F41023CAEA8@S4DE9JSAAMW.ost.t-com.de>
From: "Alexeitsev, D" <D.Alexeitsev@t-com.net>
To: dworley@pingtel.com, sipping-tispan@ietf.org
Subject: AW: AW: [Sipping-tispan] Parallel Ringing
Date: Fri, 03 Mar 2006 11:10:41 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Cc:
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

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