IETF Logo Mail Archive

[Sip] Warning header

isshed <isshed.sip@gmail.com> Thu, 10 March 2011 11:15 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 879B43A6924 for <sip@core3.amsl.com>; Thu, 10 Mar 2011 03:15:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.795
X-Spam-Level:
X-Spam-Status: No, score=-2.795 tagged_above=-999 required=5 tests=[AWL=0.201, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 0a-wk3eY5SQH for <sip@core3.amsl.com>; Thu, 10 Mar 2011 03:15:21 -0800 (PST)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by core3.amsl.com (Postfix) with ESMTP id E55B83A68F0 for <sip@ietf.org>; Thu, 10 Mar 2011 03:15:21 -0800 (PST)
Received: by pwi5 with SMTP id 5so547919pwi.31 for <sip@ietf.org>; Thu, 10 Mar 2011 03:16:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=UE/HGuGQXtHgEDzsQUmFVk7NK7rxWNKcUbaHUI8216o=; b=MDfAguVRGkJwZoIGGnRYYttjVxXuZ/orvssrJ4VyIgFVLfy5oY+PLBIoEGd6Q6Sg+d vp8ItPsvGdRFcE7sBVwrpLHaQ+8rlR198vS0TXzWbkpFxHafZKby2Q0pRY6y/tcqz/CA ksPMGmhIMs31PeFjDNNMZCfbt9N4sTTrhjC6M=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=dfKy/hOVfeITBxOJ98FUkSdyWxA11BhOn8d/zzrVuZZ+zFWmV93KNFyR76QKdI5Lfh dPy43YPGaTxjyyQtLdrPC6MqwdcXeuqMNC48cVyKxRNibUElvDeNDcVP2A2Bd61yO3eW LycXxiCXciIAlJJKpJ7fX5D1915rAb/aRr4jg=
MIME-Version: 1.0
Received: by 10.143.20.17 with SMTP id x17mr6341734wfi.154.1299755799481; Thu, 10 Mar 2011 03:16:39 -0800 (PST)
Received: by 10.143.41.1 with HTTP; Thu, 10 Mar 2011 03:16:39 -0800 (PST)
Date: Thu, 10 Mar 2011 16:46:39 +0530
Message-ID: <AANLkTinCuruaerHNjfw51FnvQ_t6-RwOS5FwgOvWMrmp@mail.gmail.com>
From: isshed <isshed.sip@gmail.com>
To: sip@ietf.org, sip-implementors <sip-implementors@lists.cs.columbia.edu>
Content-Type: multipart/alternative; boundary="00504502cc88b90c43049e1efa73"
Subject: [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 11:15:22 -0000

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