Re: [Sip] Warning header

"Worley, Dale R (Dale)" <dworley@avaya.com> Thu, 10 March 2011 15:42 UTC

Return-Path: <dworley@avaya.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 03CDF3A69E6 for <sip@core3.amsl.com>; Thu, 10 Mar 2011 07:42:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.245
X-Spam-Level:
X-Spam-Status: No, score=-102.245 tagged_above=-999 required=5 tests=[AWL=-0.246, BAYES_00=-2.599, J_CHICKENPOX_18=0.6, USER_IN_WHITELIST=-100]
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 O8RoI1AFmbcB for <sip@core3.amsl.com>; Thu, 10 Mar 2011 07:42:31 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 0A3D53A69CC for <sip@ietf.org>; Thu, 10 Mar 2011 07:42:30 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAFMtcU2HCzI1/2dsb2JhbACmZXSkeQKZFoVhBIUcinCIQA
X-IronPort-AV: E=Sophos;i="4.62,296,1297054800"; d="scan'208";a="236111849"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 10 Mar 2011 10:43:47 -0500
X-IronPort-AV: E=Sophos;i="4.62,296,1297054800"; d="scan'208";a="614707346"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 10 Mar 2011 10:43:46 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.187]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Thu, 10 Mar 2011 10:43:46 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: isshed <isshed.sip@gmail.com>, "sip@ietf.org" <sip@ietf.org>, sip-implementors <sip-implementors@lists.cs.columbia.edu>
Date: Thu, 10 Mar 2011 10:43:45 -0500
Thread-Topic: [Sip] Warning header
Thread-Index: AcvfFKOY9DpFfGWFR9GTbzBfj0nUmQAJGGmj
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B220B5C156B@DC-US1MBEX4.global.avaya.com>
References: <AANLkTinCuruaerHNjfw51FnvQ_t6-RwOS5FwgOvWMrmp@mail.gmail.com>
In-Reply-To: <AANLkTinCuruaerHNjfw51FnvQ_t6-RwOS5FwgOvWMrmp@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 15:42:32 -0000

________________________________________
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?
________________________________________

The response is 488, which is correct if the recipient cannot find suitable codecs in the SDP offer.
This makes sense, as the SDP contains no audio coded.

The warning code 306 indicates that the recipient cannot understand one of the a= lines.  Unfortunately,
the message does not indicate which a= line it does not understand.  My understanding is that
if the interpreter of SDP does not understand an a= line, it should ignore it, which is aligned with
the fact that the response contains a warning (as opposed to an error) about not understanding an a= line.

I also see that the m= line mentions codec 101, but there is no a=rtpmap:101 line, which is I think technically
an error, but in practice means that the recipient must ignore codec 101.

Dale