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

Adam Roach <adam@nostrum.com> Fri, 12 February 2010 15:53 UTC

Return-Path: <adam@nostrum.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 73D8928C1BC for <sip@core3.amsl.com>; Fri, 12 Feb 2010 07:53:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.571
X-Spam-Level:
X-Spam-Status: No, score=-2.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-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 YlqzapkVhMIz for <sip@core3.amsl.com>; Fri, 12 Feb 2010 07:53:09 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 353693A78CA for <sip@ietf.org>; Fri, 12 Feb 2010 07:53:06 -0800 (PST)
Received: from hydra-3.local (ppp-70-249-147-216.dsl.rcsntx.swbell.net [70.249.147.216]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o1CFsKMe012964 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Feb 2010 09:54:20 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <4B7579AC.2000706@nostrum.com>
Date: Fri, 12 Feb 2010 09:54:20 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: Nitin Kapoor <nitinkapoorr@gmail.com>
References: <c80c92d1002120433y102bfa24p6bcd2cd2bee42a87@mail.gmail.com> <c80c92d1002120437l35adde35hd5e865ba1d3b2354@mail.gmail.com> <abcc59881002120512l41572f59pd8f3570ebe774c69@mail.gmail.com> <c80c92d1002120516l4597a5d5p732b3b2671c8c872@mail.gmail.com>
In-Reply-To: <c80c92d1002120516l4597a5d5p732b3b2671c8c872@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------010005020407010109000001"
Received-SPF: pass (nostrum.com: 70.249.147.216 is authenticated by a trusted mechanism)
Cc: sip@ietf.org
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:53:10 -0000

At the bottom of every mail on this email list -- including the ones 
that you're sending -- you'll find the following helpful information:

This list is for NEW development of the core SIP Protocol
Usesip-implementors@cs.columbia.edu  for questions on current sip


Please respect the designated purposes of these mailing lists. Thank you.

/a


On 2/12/10 07:16, Feb 12, Nitin Kapoor wrote:
> Aayush,
>
> Please find the attached Traces for both legs.
>
> Thanks,
> Nitin Kapoor
>
> On 12 February 2010 08:12, aayush bhatnagar 
> <abhatnagar192006@gmail.com <mailto:abhatnagar192006@gmail.com>> wrote:
>
>     Can you paste wireshark logs for both ends of the SBC?
>
>     On 12/02/2010, Nitin Kapoor <nitinkapoorr@gmail.com
>     <mailto: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
>     ======
>
>
>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip