RE: [Sipping] 433 error response format.
"adi" <adi@personeta.com> Thu, 26 April 2007 10:17 UTC
Return-path: <sipping-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hh12K-0007OR-2A; Thu, 26 Apr 2007 06:17:16 -0400
Received: from sipping by megatron.ietf.org with local (Exim 4.43) id 1Hh12I-0007OC-TP for sipping-confirm+ok@megatron.ietf.org; Thu, 26 Apr 2007 06:17:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hh12I-0007O3-CF for sipping@ietf.org; Thu, 26 Apr 2007 06:17:14 -0400
Received: from [204.200.195.236] (helo=personeta.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hh12G-0002ls-GI for sipping@ietf.org; Thu, 26 Apr 2007 06:17:14 -0400
Received: from adii ([194.90.193.76]) (authenticated bits=0) by personeta.com (8.13.6.20060614/8.13.6) with ESMTP id l3QAH8p1091157 for <sipping@ietf.org>; Thu, 26 Apr 2007 10:17:10 GMT
Message-Id: <200704261017.l3QAH8p1091157@personeta.com>
From: adi <adi@personeta.com>
To: sipping@ietf.org
Subject: RE: [Sipping] 433 error response format.
Date: Thu, 26 Apr 2007 13:19:04 +0300
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Thread-Index: AceH5/kdH4AxqpxaTHe/iC8yPEWS3wAA7P6w
In-Reply-To: <OF6934D3A1.1CC2A5F1-ON652572C9.0034FFBD-652572C9.0035F075@flextronicssoftware.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73f7847c44628482de9d5f1018acf469
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0539848856=="
Errors-To: sipping-bounces@ietf.org
When receiving 433 it's the UAC responsibility to announce the user that other party of the call is blocking the call because of the anonymity of the caller and the user in case he wants to make the call must remove his anonymity from the new request. This request must be done as a user request and not automatically by the UAC. _____ From: Preethi.Sadasivan@aricent.com [mailto:Preethi.Sadasivan@aricent.com] Sent: Thursday, April 26, 2007 12:47 PM To: sipping@ietf.org Cc: Preethi.Sadasivan@aricent.com Subject: [Sipping] 433 error response format. Hi All, I have a query with reference to the following lines from the draft "draft-ietf-sip-acr-code-04.txt" for 433 error response Section 4. 4 .UAC Behavior A UAC receiving a 433 (Anonymity Disallowed) MUST NOT retry the request without anonymity unless it obtains confirmation from the user that this is desirable. Such confirmation could be obtained through the user interface, or by accessing user defined policy. If the user has indicated that this is desirable, the UAC MAY retry the request without requesting anonymity. How will the UAS indicate the UAC that it has a desire for the request to be retried. Will this be communicated in some headers like that of Retry-Header. Please throw some light on this issue. Thanks and Regards, Preethi.. ---------------------------------------------------------------------------- -- Preethi Sadasivan, Software Engineer, ARICENT , Bangalore. tel: +91-80-41069118 ---------------------------------------------------------------------------- -- *********************** Aricent-Private *********************** "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."
_______________________________________________ Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@cs.columbia.edu for questions on current sip Use sip@ietf.org for new developments of core SIP
- RE: [Sipping] 433 error response format. adi
- [Sipping] 433 error response format. Preethi.Sadasivan
- RE: [Sipping] 433 error response format. Drage, Keith (Keith)
- Re: [Sipping] 433 error response format. Dale.Worley
- RE: [Sipping] 433 error response format. adi
- RE: [Sipping] 433 error response format. Preethi.Sadasivan
- RE: [Sipping] 433 error response format. Avasarala Ranjit-A20990