Re: [Sip] TCP to UDP rtcp media attributes in SDP not passing through nextone

Nitin Kapoor <nitinkapoorr@gmail.com> Fri, 12 February 2010 15:21 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 95F4C28B23E for <sip@core3.amsl.com>; Fri, 12 Feb 2010 07:21:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.114
X-Spam-Level:
X-Spam-Status: No, score=-1.114 tagged_above=-999 required=5 tests=[AWL=1.484, 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 1Vl-bWXvKdm7 for <sip@core3.amsl.com>; Fri, 12 Feb 2010 07:21:23 -0800 (PST)
Received: from mail-qy0-f183.google.com (mail-qy0-f183.google.com [209.85.221.183]) by core3.amsl.com (Postfix) with ESMTP id D637F28C153 for <sip@ietf.org>; Fri, 12 Feb 2010 07:21:22 -0800 (PST)
Received: by qyk13 with SMTP id 13so1363223qyk.31 for <sip@ietf.org>; Fri, 12 Feb 2010 07:22:37 -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=OwwZIVPbGxR06e9SNdF4N7CX3FHJVOTiWWvH35GxXng=; b=wNmZS7aOMBvkfgYwRkfQjXVScA6eDQCnFcVy8RhBvQdl/DxWXYBhAbhrEMES8rTInu eheB0mXEA7DC2WUoRYy90EAGEi1OMwOGs4wlUkzdOOXY78FQLMYZRbgAlrcjfoH0vM2f rfEBmRid0XK+e4GWSFdcDq3dS76sheijNvzos=
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=T9TFbmrfOxmJ3a0wUFcEvnj2mIX2m1RX3VvWQak5Sbye54yXVydsvFYvLrVf99sHAa GJ3N6LqEXugMTvjaI5TOSMw9yz9noqRdohVkQdo3vc//uhqdZGQCi8uVUR2Ob01afNWE +nhrH8Me/ychmDLacn8R9u3wNz+O9QKS9W/y4=
MIME-Version: 1.0
Received: by 10.229.128.219 with SMTP id l27mr646221qcs.26.1265988157252; Fri, 12 Feb 2010 07:22:37 -0800 (PST)
In-Reply-To: <c80c92d1002120516l4597a5d5p732b3b2671c8c872@mail.gmail.com>
References: <c80c92d1002120433y102bfa24p6bcd2cd2bee42a87@mail.gmail.com> <c80c92d1002120437l35adde35hd5e865ba1d3b2354@mail.gmail.com> <abcc59881002120512l41572f59pd8f3570ebe774c69@mail.gmail.com> <c80c92d1002120516l4597a5d5p732b3b2671c8c872@mail.gmail.com>
Date: Fri, 12 Feb 2010 10:22:37 -0500
Message-ID: <c80c92d1002120722v4f93f9e8yeb93ca465ea3ef7f@mail.gmail.com>
From: Nitin Kapoor <nitinkapoorr@gmail.com>
To: sip@ietf.org
Content-Type: multipart/alternative; boundary=001517577412672601047f68d6d3
Cc: sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip] TCP to UDP rtcp media attributes in SDP not passing through nextone
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: Fri, 12 Feb 2010 15:21:26 -0000

Could any please help me out on this.

Thanks,
Nitin Kapoor

On 12 February 2010 08:16, Nitin Kapoor <nitinkapoorr@gmail.com> wrote:

> Aayush,
>
> Please find the attached Traces for both legs.
>
> Thanks,
> Nitin Kapoor
>
>
> On 12 February 2010 08:12, aayush bhatnagar <abhatnagar192006@gmail.com>wrote;wrote:
>
>> Can you paste wireshark logs for both ends of the SBC?
>>
>> On 12/02/2010, Nitin Kapoor <nitinkapoorr@gmail.com> wrote:
>> > Dear Friend,
>> >
>> > I have some query about UDP & TCP for signaling.
>> >
>> > Basically I am using TCP protocol for signaling from my customer to SBC
>> and
>> > then SBC to Vendor using UDP for signaling. I mean CS user TCP to SBC,
>> UDP
>> > to carrier.  And OCS sends initial 183 with sdp that contains rtcp media
>> > attribute information and SBC does not forward formation to carrier via
>> UDP.
>> >
>> >
>> > Call Flow is like this.
>> >
>> > UAC (Private)                    SBC
>> > UAS(Public)
>> >
>> > |-----------Invite(TCP)---------->
>> > |                                                       |
>> > |
>> > |                                                       |
>> > |<-------- 100 Trying ------------ |
>> >                                           |
>> > |                                        | ----------- Invite
>> > (UDP)----------------------->|
>> > |
>> > |                                                       |
>> > |                                        |<--------- 100 Trying
>> > ---------------------------|
>> > |
>> > |                                                       |
>> >                                          | <---- 183 SDP Session
>> > Progress-------|
>> > |                                        |(183 SDP with RTCP Media
>> >     |
>> > |                                        |Attribute).
>> >                                        |
>> > |<--------- 183 SDP -------------
>> > |
>> > |
>> > | 183 SDP Session
>> > progress|                                                       |
>> > | Without RTCP Media         |
>> >                                                |
>> > |Attribute
>> > |                                                       |
>> > |
>> > |                                                       |
>> > |
>> > |                                                       |
>> > |
>> > |                                                       |
>> >
>> > Could anyone please help me out on this scenario. Why it’s not sending
>> the
>> > RTCP attribute to my UAC? Is there anything related to standard.
>> >
>> > I can share the Traces, if its required.
>> >
>> > Thanks,
>> > Nitin Kapoor
>> >
>>
>>
>> --
>> aayush
>> http://in.linkedin.com/in/abhatnagar19
>> ======
>>
>
>