IETF Logo Mail Archive

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

Nitin Kapoor <nitinkapoorr@gmail.com> Wed, 01 September 2010 22:08 UTC

Return-Path: <nitinkapoorr@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 307133A68F2 for <sip@core3.amsl.com>; Wed, 1 Sep 2010 15:08:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.02
X-Spam-Level:
X-Spam-Status: No, score=-1.02 tagged_above=-999 required=5 tests=[AWL=-0.836, BAYES_40=-0.185, 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 KcwM1oL3ReIm for <sip@core3.amsl.com>; Wed, 1 Sep 2010 15:08:36 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id 712783A6849 for <sip@ietf.org>; Wed, 1 Sep 2010 15:08:23 -0700 (PDT)
Received: by qwc9 with SMTP id 9so7493693qwc.31 for <sip@ietf.org>; Wed, 01 Sep 2010 15:08:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=y7WXG+mVdbW+ud0VNfbceuulMDambrJI+gOPAo8uqWY=; b=QXDaFMVKXWddmYRjugboyRnPZfKG5vuV0lV7s/oH30Zvy0544OwncL2DeE5Ymb5+ix mkj44NjD8Die4/3b+D2JPm/ugwjJdyiWXDY7YZenyeGHqo5I32Ttj+YiqHmJOUHnY9dl O/kahHJNMgxbjjNGmrqLXKxEfl3OYKg+eLheo=
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=uST3CU+bTPsTt2QjQMfkPqWcUpzd401+0Ye+u7TMB2pBvV/HcBUnLivaToPNc1UGHi M2Na9BiLh+VewJ1S+5Saj/0ozhj/196wStZ+C8BSAMsZSu1eTMqrNi/aYvSuSUKbJL3Z RzBiIeNrWTQ4eb+z/rNIOKu4tP/9tRXefd9M0=
MIME-Version: 1.0
Received: by 10.224.130.77 with SMTP id r13mr3756630qas.163.1283378933292; Wed, 01 Sep 2010 15:08:53 -0700 (PDT)
Received: by 10.229.72.28 with HTTP; Wed, 1 Sep 2010 15:08:53 -0700 (PDT)
In-Reply-To: <003901cb49f7$42769ad0$1ede1eac@cisco.com>
References: <AANLkTikg9wcC0Q3hyc3g6h1rJoQfPrEFd=VJc_NCoNCV@mail.gmail.com> <003901cb49f7$42769ad0$1ede1eac@cisco.com>
Date: Wed, 1 Sep 2010 18:08:53 -0400
Message-ID: <AANLkTikyrqTN5TC=R=aUn3vT0gcgX3g8eMO86Tp0JKJe@mail.gmail.com>
From: Nitin Kapoor <nitinkapoorr@gmail.com>
To: Sameer Sawhney <ssawhney@cisco.com>, paulej@packetizer.com
Content-Type: multipart/alternative; boundary=0016e64ccac66e605f048f39f1dc
Cc: sip@ietf.org, sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip] [Sip-implementors] 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 22:08:38 -0000

Thanks for your reply.

I checked the RFC and noticed that it does not limit the codec #s in mline,
but nor does it comment on infinite number of codecs support being
mandatory.

So could you please let me know whether it is mandatory to support them or
not. Because if my SBC is not supporting this then i cannot go and ask them
to support this.

Thanks,
Nitin Kapoor



On 1 September 2010 13:00, Sameer Sawhney <ssawhney@cisco.com> wrote:

> As per spec 2327 this is valid ! check fmt.
>
>
>   media-field =         "m=" media space port ["/" integer]
>                         space proto 1*(space fmt) CRLF
>
>   media =               1*(alpha-numeric)
>                         ;typically "audio", "video", "application"
>                         ;or "data"
>
>   fmt =                 1*(alpha-numeric)
>                         ;typically an RTP payload type for audio
>                         ;and video media
>
>   proto =               1*(alpha-numeric)
>                         ;typically "RTP/AVP" or "udp" for IP4
>
>   port =                1*(DIGIT)
>                         ;should in the range "1024" to "65535" inclusive
>                         ;for UDP based media
>
> -----Original Message-----
> From: sip-implementors-bounces@lists.cs.columbia.edu
> [mailto:sip-implementors-bounces@lists.cs.columbia.edu] On Behalf Of Nitin
> Kapoor
> Sent: Wednesday, September 01, 2010 7:21 PM
> To: sip-implementors@lists.cs.columbia.edu; sip@ietf.org
> Subject: [Sip-implementors] 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
> _______________________________________________
> Sip-implementors mailing list
> Sip-implementors@lists.cs.columbia.edu
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
>

v2.8.7 | Report a Bug | By Email