Re: AW: [Sipping-tispan] Parallel Ringing

"Dale R. Worley" <dworley@pingtel.com> Thu, 02 March 2006 20:19 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FEuH3-0005pJ-40; Thu, 02 Mar 2006 15:19:45 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FEuH2-0005p5-0F for sipping-tispan@ietf.org; Thu, 02 Mar 2006 15:19:44 -0500
Received: from mail.pingtel.com ([65.220.123.3]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FEuH0-0005zO-Ql for sipping-tispan@ietf.org; Thu, 02 Mar 2006 15:19:43 -0500
Received: from localhost.localdomain (mail.pingtel.com [192.168.253.2]) by mail.pingtel.com (Postfix) with ESMTP id A72C66C017 for <sipping-tispan@ietf.org>; Thu, 2 Mar 2006 15:19:38 -0500 (EST)
Subject: Re: AW: [Sipping-tispan] Parallel Ringing
From: "Dale R. Worley" <dworley@pingtel.com>
To: Sipping-TISPAN <sipping-tispan@ietf.org>
In-Reply-To: <97A461F3EE5284469E41ED3728202F41023CAEA4@S4DE9JSAAMW.ost.t-com.de>
References: <97A461F3EE5284469E41ED3728202F41023CAEA4@S4DE9JSAAMW.ost.t-com.de>
Content-Type: text/plain
Date: Thu, 02 Mar 2006 15:19:38 -0500
Message-Id: <1141330778.15288.36.camel@cdhcp139.pingtel.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.4 (2.0.4-7)
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
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

On Thu, 2006-03-02 at 17:23 +0100, Alexeitsev, D wrote:
> In forking the multiple contacts of the single AOR will get called. In
> parallel ringing multiple AORs will get called when a call hits an AOR
> with the activated parallel ringing feature.

This sounds exactly like SIP parallel forking.  Why would parallel
forking have to be "activated"?

Dale



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