Re: [Sip] Infinite Number of RTP payload in "mline"

"Paul E. Jones" <paulej@packetizer.com> Wed, 01 September 2010 16:55 UTC

Return-Path: <paulej@packetizer.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 813D23A67F2 for <sip@core3.amsl.com>; Wed, 1 Sep 2010 09:55:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.628
X-Spam-Level:
X-Spam-Status: No, score=-1.628 tagged_above=-999 required=5 tests=[AWL=0.970, BAYES_00=-2.599, HTML_MESSAGE=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 zsB8Tmf4z3ep for <sip@core3.amsl.com>; Wed, 1 Sep 2010 09:55:16 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by core3.amsl.com (Postfix) with ESMTP id 46D0C3A682A for <sip@ietf.org>; Wed, 1 Sep 2010 09:55:12 -0700 (PDT)
Received: from sydney (rrcs-98-101-146-183.midsouth.biz.rr.com [98.101.146.183]) (authenticated bits=0) by dublin.packetizer.com (8.14.2/8.14.2) with ESMTP id o81GtZwN016719 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 1 Sep 2010 12:55:40 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1283360141; bh=BiUnYrYPlMLlTl+5TZiuaeVEVDix1yHSxN2tLqXa5QE=; h=From:To:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=ln4LHrlibdtT5eUBzARnIFbNFNXpaCKkKajhrBQOCwU+/MA2vd/rMc9Bm9PbUER+n +/m7UsL7Zm/H3JpNSuNp9cg8ho/aa+eqZxPS/zHqKmo8wrP7FY8s5d+fZi0iXCrYmF IAiDWO2lqgFxGwHmCMNtUGsD7KD42NTAVmbEL9PA=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "'Nitin Kapoor'" <nitinkapoorr@gmail.com>, <sip-implementors@lists.cs.columbia.edu>, <sip@ietf.org>
References: <AANLkTikg9wcC0Q3hyc3g6h1rJoQfPrEFd=VJc_NCoNCV@mail.gmail.com>
In-Reply-To: <AANLkTikg9wcC0Q3hyc3g6h1rJoQfPrEFd=VJc_NCoNCV@mail.gmail.com>
Date: Wed, 1 Sep 2010 12:54:12 -0400
Message-ID: <054301cb49f6$50e52c90$f2af85b0$@packetizer.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0544_01CB49D4.C9D44FE0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGMsPCF30uBjPYRZnvACLtGKHAuAJN6inrA
Content-Language: en-us
Subject: Re: [Sip] Infinite Number of RTP payload in "mline"
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: Wed, 01 Sep 2010 16:55:21 -0000

This is valid, though I've never seen so many codecs on a single m= line.
Who can practically deal with this? ;-)

 

Paul

 

From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of Nitin
Kapoor
Sent: Wednesday, September 01, 2010 9:51 AM
To: sip-implementors@lists.cs.columbia.edu; sip@ietf.org
Subject: [Sip] Infinite Number of RTP payload in "mline"

 

Dear All,

I am facing the problem where one of source is sending bunch of RTP payload
in "mline", and because of that my MSX is stripping 2 codec from that line,
when its forwarding that OFFER to termination end.

This is the "mline" which i am getting from source:

m=audio 6300 RTP/AVP 18 0 8 35 36 2 38 39 40 41 42 43 44 45 46 47 4 80 3 56
118 101 13 120

This is what my MSX is sending to termination after stripping the payload
from "mline"

m=audio 6300 RTP/AVP 18 0 8 35 36 2 38 39 40 41 42 43 44 45 46 47 4 80 3 56
118 101    

Now i checked some documents but unable to find anything which says its
correct or not.

Could any one please give some direction on this whether such amount of
payload type is correct in "mline" or it not acceptable .

Thanks,
Nitin Kapoor