[Sipping-tispan] Parallel Ringing

"Alexeitsev, D" <D.Alexeitsev@t-com.net> Fri, 17 February 2006 13:50 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1FA60C-0001pQ-C7; Fri, 17 Feb 2006 08:50:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1FA603-0001lP-Cv for sipping-tispan@megatron.ietf.org; Fri, 17 Feb 2006 08:50:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24021 for <sipping-tispan@ietf.org>; Fri, 17 Feb 2006 08:48:27 -0500 (EST)
Received: from tcmail22.telekom.de ([217.6.95.236]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FA5vb-0004YQ-2m for sipping-tispan@ietf.org; Fri, 17 Feb 2006 08:45:44 -0500
Received: from g9jbr.mgb01.telekom.de (g9jbr.mgb01.telekom.de [164.20.31.6]) by tcmail21.dmz.telekom.de with ESMTP; Fri, 17 Feb 2006 14:30:31 +0100
Received: by G9JBR.mgb01.telekom.de with Internet Mail Service (5.5.2653.19) id <15YK5AAK>; Fri, 17 Feb 2006 14:30:31 +0100
Message-Id: <97A461F3EE5284469E41ED3728202F41023CAE3E@S4DE9JSAAMW.ost.t-com.de>
From: "Alexeitsev, D" <D.Alexeitsev@t-com.net>
To: sipping-tispan@ietf.org, TISPAN_WG3@LIST.ETSI.ORG
Date: Fri, 17 Feb 2006 14:30:18 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc:
Subject: [Sipping-tispan] Parallel Ringing
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>
Content-Type: multipart/mixed; boundary="===============0598287534=="
Sender: sipping-tispan-bounces@ietf.org
Errors-To: sipping-tispan-bounces@ietf.org

Hello altogether

I would like to discuss the parallel ring service, that was not on the TISPAN release one, but we would like to it get introduced in release two.

>From the signalling point of view, there should be no additional SIP procedures required except for the indication in both directions that the parallel ringing is taking place. That is important for example to be able to prevent a voicemail box being one of the parallel ring targets from automatically accepting the call. On receiving this cause it could delay the answer for some time giving other parties a chance of answering.

As the parallel ringing can be considered as a very special case of call forwarding, that same procedures could be used to indicate it, namely History-Info header. What is needed is just another cause code, that would indicate a parallel ringing.

As a nice side effect this indication would also allow endpoints to understand when to send 486 Busy Here and when 600 Busy Everywhere.

A forking event could be incorporated in to the same cause or could have an explicit one.

Waiting for comments,
Denis Alexeitsev
_______________________________________________
Sipping-tispan mailing list
Sipping-tispan@ietf.org
https://www1.ietf.org/mailman/listinfo/sipping-tispan