IETF Logo Mail Archive

Re: [Sip] Warning header

isshed <isshed.sip@gmail.com> Thu, 10 March 2011 12:23 UTC

Return-Path: <isshed.sip@gmail.com>
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B57FA3A696F for <sip@core3.amsl.com>; Thu, 10 Mar 2011 04:23:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[AWL=0.508, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6, J_CHICKENPOX_18=0.6, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_LOW=-1, WEIRD_PORT=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WJPoC-ieoTLm for <sip@core3.amsl.com>; Thu, 10 Mar 2011 04:23:17 -0800 (PST)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by core3.amsl.com (Postfix) with ESMTP id D67F63A691D for <sip@ietf.org>; Thu, 10 Mar 2011 04:23:17 -0800 (PST)
Received: by pve39 with SMTP id 39so475203pve.31 for <sip@ietf.org>; Thu, 10 Mar 2011 04:24:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=tQ9GvjIgYi4is+feUPUtrOz011LEldqaI+YpctdtfGA=; b=KBqQhzrscA2Ly3xDw/2sO2rn/dSEDHnThv9CbVXMKHng2xOtCYdngtcYsm1lpgoMFw aGsEW6uRraJS+YBt1xAY/SUsXgolw+gULzVlgrD/dyEcCKgFw914sUgDWsiP3I5Hzsnt JDm8RHI+A/dTAeLUTxDYBy78aPjZl4bpygWWs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=SiV8iORXCaefhc22RDPh8f3Cgz3fph+qgYmTemDT+snIEVDwj2rmoTR1M3PUsi5n3K ncN8pdo+U3A2WMCZbnrp5WTiCUmxe9JYaECod2zvoCbz/r5+i0mzS1a4ZHeYbZCTNEz2 vdS0M1O8KTfQ01PQaGIk5mqLIi0V6Fz15JW1I=
MIME-Version: 1.0
Received: by 10.142.201.15 with SMTP id y15mr6361086wff.268.1299759875615; Thu, 10 Mar 2011 04:24:35 -0800 (PST)
Received: by 10.143.41.1 with HTTP; Thu, 10 Mar 2011 04:24:35 -0800 (PST)
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A05851948FF292D@ESESSCMS0356.eemea.ericsson.se>
References: <AANLkTinCuruaerHNjfw51FnvQ_t6-RwOS5FwgOvWMrmp@mail.gmail.com> <7F2072F1E0DE894DA4B517B93C6A05851948FF292D@ESESSCMS0356.eemea.ericsson.se>
Date: Thu, 10 Mar 2011 17:54:35 +0530
Message-ID: <AANLkTikAxoood_0gGTaVVgf=xenV_HLwtrxchBqwOqkT@mail.gmail.com>
From: isshed <isshed.sip@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary="000e0cd32f00adeee5049e1fede9"
Cc: "sip@ietf.org" <sip@ietf.org>, sip-implementors <sip-implementors@lists.cs.columbia.edu>
Subject: Re: [Sip] Warning header
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Mar 2011 12:23:18 -0000

Thanks for reply..

what about the addiftional info response 305 or 307?

My question is which one is best suited here?
Thanks,
Harendra
On Thu, Mar 10, 2011 at 4:53 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
> Per section 20.43 of RFC 3261, 306 seems like a good value.
>
>  "306 Attribute not understood: One or more of the media attributes
>      in the session description are not supported."
>
> Note that it is not a SIP response code, but a code supposed to give
> additional information about the response.
>
> Regards,
>
> Christer
>
>
>
>
>
>
> ________________________________
>
>        From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf
> Of isshed
>        Sent: 10. maaliskuuta 2011 13:17
>        To: sip@ietf.org; sip-implementors
>        Subject: [Sip] Warning header
>
>
>        Hi All,
>
>        If an initial INVITE from an endpoint offer contains the sdp as
> follows.
>
>        m=audio 15190 RTP/AVP 100 101\r\n
>        a=fmtp:18 annexb=yes\r\n
>        a=fmtp:101 0-15\r\n
>        a=rtpmap:100 UNACCEPTABLECODEC/8000\r\n
>        a=sendrecv
>
>        the terminating endpoint returns an error response 488 with a
> warning header as follows.
>
>        Warning: 306 132.177.120.67:5060 "Attribute not understood"
>
>        Is 306 is correct response?
>
>        Thanks,
>
>
>

v2.23.0 | Report a Bug | By Email