[Sip] RE: Comments regarding the reason in draft-ietf-sip-history-info- 04
"Mary Barnes" <mary.barnes@nortelnetworks.com> Wed, 17 November 2004 15:08 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06050 for <sip-web-archive@ietf.org>; Wed, 17 Nov 2004 10:08:46 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CURSp-00034M-TL for sip-web-archive@ietf.org; Wed, 17 Nov 2004 10:11:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CURN7-00044j-50; Wed, 17 Nov 2004 10:05:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CURDv-0008NS-2E for sip@megatron.ietf.org; Wed, 17 Nov 2004 09:55:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04727 for <sip@ietf.org>; Wed, 17 Nov 2004 09:55:52 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CURGL-0002nE-La for sip@ietf.org; Wed, 17 Nov 2004 09:58:26 -0500
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id iAHEtKj23414; Wed, 17 Nov 2004 09:55:20 -0500 (EST)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19) id <WVC4G5V9>; Wed, 17 Nov 2004 09:55:20 -0500
Message-ID: <E3F9D87C63E2774390FE67C924EC99BB053124B3@zrc2hxm1.corp.nortel.com>
From: Mary Barnes <mary.barnes@nortelnetworks.com>
To: 'PROUVOST Sebastien RD-CORE-ISS' <sebastien.prouvost@francetelecom.com>
Date: Wed, 17 Nov 2004 09:55:08 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.6 (/)
X-Scan-Signature: d890c9ddd0b0a61e8c597ad30c1c2176
Cc: sip@ietf.org
Subject: [Sip] RE: Comments regarding the reason in draft-ietf-sip-history-info- 04
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0113581853=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org
X-Spam-Score: 0.6 (/)
X-Scan-Signature: b8f3559805f7873076212d6f63ee803e
Hi Sebastien, I think the need for these specific reasons depends upon how you implement your voicemail service. I think what you perhaps might need in these situations, such as the "call forwarding immediate", is extensions to the Reason header as discussed in draft-elwell-sipping-redirection-reason-01. I don't think this is something that should at all be addressed in the history-info draft, which is just one the proposed building blocks for providing voicemail services. Mary -----Original Message----- From: PROUVOST Sebastien RD-CORE-ISS [mailto:sebastien.prouvost@francetelecom.com] Sent: Wednesday, November 17, 2004 2:36 AM To: Barnes, Mary [NGC:B601:EXCH] Cc: sip@ietf.org Subject: Comments regarding the reason in draft-ietf-sip-history-info-04 Hi Mary, One comment on the history draft regarding the reason in history-info header. Section 4.3.3.1.2 mentions that for retarget as a result of timeouts of internal events, a Reason MAY be associated with the hi-targeted-to-uri. I think that 2 specific values of the reason header shall be specified by the draft as they are necessary to voicemail services (for example in order to render to the caller an annonce associated with the reason such as "the user you are calling is not responding" or "the user you are trying to contact is not available (registered) at the moment") : - a value for timeout (reason = 'no response' for example) - a value for direct retargeting to a default contact URI or to another AoR (reason = 'call forwarding immediate' for example). I am therefore in favour of adding a text looking like this : " As a result of timeouts of internal events, a Reason MAY be associated with the hi-targeted-to-uri. Although other values may be possible this draft defines two values for the Reason in such cases : - Reason ='no response' when the retargeting occurs after timeout - Reason = 'call forwarding immediate' when the proxy directly retargets to a default contact URI or to another AoR " Sébastien
_______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip