Re: [Sipp-users] Usage of unicast ip in attribute param

[peeyush j. <jai...@gm...>]

Hi Matthew,

Thanks for pointing out the RFC and its relevant section.

Thanks and Regards,
Peeyush Jain

On Sun, Jun 16, 2013 at 2:59 AM, Matthew Briggs
<Mat...@te...> wrote:
> According to RFC3605 what you suggest is correct and permitted:
>
> ===
> <quote>
>
> rtcp-attribute =  "a=rtcp:" port  [nettype space addrtype space
>                          connection-address] CRLF
>
>    In this description, the "port", "nettype", "addrtype" and
>    "connection-address" tokens are defined as specified in "Appendix A:
>    SDP Grammar" of [RFC2327].
>
>    Example encodings could be:
>
>     m=audio 49170 RTP/AVP 0
>     a=rtcp:53020
>
>     m=audio 49170 RTP/AVP 0
>     a=rtcp:53020 IN IP4 126.16.64.4
>
>     m=audio 49170 RTP/AVP 0
>     a=rtcp:53020 IN IP6 2001:2345:6789:ABCD:EF01:2345:6789:ABCD
>
> <endquote/>
>
>
> I see a range of devices out there that claim to support RFC3605, so this is clearly used out there.  However I've never come across it's use and can't guess what the chance of the far-end you're talking to supporting it is.
>
> Matt
>
> ________________________________________
> From: peeyush jain [jai...@gm...]
> Sent: 14 June 2013 21:50
> To: sipp-users
> Subject: [Sipp-users] Usage of unicast ip in attribute param
>
> Hi sipp users,
>
> Can my sip sdp body contain something like this:
>
> a=rtcp:6001 IN IP4 [local_ip]
>
> That is specifying my rtcp port number as 6001 and ip-address to be
> given by [local_ip].
>
> Is specifying ip in a line for rtcp legal/valid?
>
> Thanks and Regards,
> Peeyush Jain
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Sipp-users mailing list
> Sip...@li...
> https://lists.sourceforge.net/lists/listinfo/sipp-users