Re: [Sip] Getting "Media Format = 0"

Vijay Tiwari <vijay11tiwari@gmail.com> Sat, 13 March 2010 16:27 UTC

Return-Path: <vijay11tiwari@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 28FDC3A68E8 for <sip@core3.amsl.com>; Sat, 13 Mar 2010 08:27:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[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 nweqd6E1HL6p for <sip@core3.amsl.com>; Sat, 13 Mar 2010 08:27:11 -0800 (PST)
Received: from mail-iw0-f186.google.com (mail-iw0-f186.google.com [209.85.223.186]) by core3.amsl.com (Postfix) with ESMTP id 843EC3A67FD for <sip@ietf.org>; Sat, 13 Mar 2010 08:27:11 -0800 (PST)
Received: by iwn16 with SMTP id 16so1159054iwn.31 for <sip@ietf.org>; Sat, 13 Mar 2010 08:27:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=kJF5lJ9rE9n53mBc7xJsV3dcQVSRHhrM4IC/zFHbASU=; b=jJApbPywCbzfYpuRgWYpRaZO9Mi4I3VdsDO2X6vUREAtJ66kBbzwp2nK/kCJwFkGHW 0LOriCgwut0QSC2RILIn8bizGw5VrA85G138MgCKQ8AFt/aOO+maJDq/4PUEE39PSW4/ DuBITpsWNTXeYQYWCQcklswaWu4Sb8j20iykE=
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=IyJU+zy2CyNTd4/w6gMyMBUZOn5gHAAa2/44Ava/OJY4B5jdvenEGthmh0zRJz5itY utyIWVkX5uhjtKl6/oj9GT0aX7YDvPzuqRD9AQCisiShrdYrCnwps8U9QmmHRaJRagt0 W+0+UJdMP59DnfCX9bkZeocC7M5lX1foSGwgQ=
MIME-Version: 1.0
Received: by 10.231.159.134 with SMTP id j6mr1011309ibx.29.1268497635302; Sat, 13 Mar 2010 08:27:15 -0800 (PST)
In-Reply-To: <c80c92d1003120606v4b3448f8if296d9b01c3653ae@mail.gmail.com>
References: <c80c92d1003120606v4b3448f8if296d9b01c3653ae@mail.gmail.com>
Date: Sat, 13 Mar 2010 21:57:15 +0530
Message-ID: <484afbd61003130827t6de8df77q1432728e79ba2a94@mail.gmail.com>
From: Vijay Tiwari <vijay11tiwari@gmail.com>
To: Nitin Kapoor <nitinkapoorr@gmail.com>
Content-Type: multipart/alternative; boundary=001636c5c1dff35f6c0481b11e4a
Cc: sip@ietf.org, sip-implementors@cs.columbia.edu, sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip] Getting "Media Format = 0"
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: Sat, 13 Mar 2010 16:27:13 -0000

Hello Nitin

If you are talking about codec payload then

" I can see we are getting the 2 codecs in SDP(G.711 & G.729) with payload
"0, 101, 19". "

in this payload there is no G.729 because for G.729 payload is 18.

thanks
vijay


On Fri, Mar 12, 2010 at 7:36 PM, Nitin Kapoor <nitinkapoorr@gmail.com>wrote;wrote:

> Hello Friends,
>
> I am facing the problem with one of my client. I can see we are getting the
> 2 codecs in SDP(G.711 & G.729) with payload "0, 101, 19".
>
> Now here is my doubt is that whenver my client is sending the SDP in
> initial OFFER with G.729 its offering "Media format = 0".But when i checked
> the RFC 3264 and others, then i observed that it can be possible if you have
> two codecs in one SDP then one media format can be "0".
>
> Below is the OFFERED SDP from my SOURCE UA.
>
> Media Description, name and address (m): audio 17890 RTP/AVP 0 101 19
> Media Type: audio
> Media Port: 17890
> Media Protocol: RTP/AVP
> Media Format: ITU-T G.711 PCMU
> Media Format: DynamicRTP-Type-101
> Media Format: Comfort noise (old)
>
> Connection Information (c): IN IP4 212.48.160.163
> Connection Network Type: IN
> Connection Address Type: IP4
> Connection Address: 212.48.160.163
>
> Media Attribute (a): rtpmap:0 PCMU/8000
> Media Attribute Fieldname: rtpmap
> Media Format: 0
> MIME Type: PCMU
> Sample Rate: 8000
>
> Media Attribute (a): rtpmap:101 telephone-event/8000
> Media Attribute Fieldname: rtpmap
> Media Format: 101
> MIME Type: telephone-event
> Sample Rate: 8000
>
> Media Attribute (a): fmtp:101 0-16
> Media Attribute Fieldname: fmtp
> Media Format: 101 [telephone-event]
> Media format specific parameters: 0-16
> Media Attribute (a): rtpmap:19 CN/8000
> Media Attribute Fieldname: rtpmap
> Media Format: 19
> MIME Type: CN
> Sample Rate: 8000
>
> Media Attribute (a): ptime:20
> Media Attribute Fieldname: ptime
> Media Attribute Value: 20
>
> Here is SDP is offered by my Remote Entity in 183 Session progress in the
> correspondence of of INITIAL INVITE.
>
> Media Description, name and address (m): audio 5870 RTP/AVP 0 101
> Media Type: audio
> Media Port: 5870
> Media Protocol: RTP/AVP
> Media Format: ITU-T G.711 PCMU
> Media Format: DynamicRTP-Type-101
> Media Attribute (a): rtpmap:0 PCMU/8000
> Media Attribute Fieldname: rtpmap
> Media Format: 0
> MIME Type: PCMU
> Sample Rate: 8000
> Media Attribute (a): sendrecv
> Media Attribute (a): rtpmap:101 telephone-event/8000
> Media Attribute Fieldname: rtpmap
> Media Format: 101
> MIME Type: telephone-event
> Sample Rate: 8000
>
>
> Now the problem which i am facing is that after  doing the Negotiation and
> the ACK of 200 OK in the correspondence in INITIAL OFFER/INVITE, i am
> getting a BYE  immediately from my source UA.
>
> Could anyone please help me to diagnose this.
>
> Thanks,
> Nitin kapoor
>
>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is essentially closed and only used for finishing old business.
> Use sip-implementors@cs.columbia.edu for questions on how to develop a SIP
> implementation.
> Use dispatch@ietf.org for new developments on the application of sip.
> Use sipcore@ietf.org for issues related to maintenance of the core SIP
> specifications.
>



-- 
They can because they think they can.