[SIPForum-discussion] Even Port number for RTP in SDP (NK)

[Murali ZTE]

Hello Nitin,

As per RFC 4566 and other RFC's the RTP ports should be even.

The odd ports will be used for RTCP when it is added in the SDP.

Could you please share the pcap trace to advise further.

Thanks and Regards
Murali




> From: discussion-request at sipforum.org
> Subject: discussion Digest, Vol 102, Issue 11
> To: discussion at sipforum.org
> Date: Mon, 13 Jan 2014 12:00:02 -0500
> 
> Send discussion mailing list submissions to
> 	discussion at sipforum.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://sipforum.org/mailman/listinfo/discussion
> or, via email, send a message with subject or body 'help' to
> 	discussion-request at sipforum.org
> 
> You can reach the person managing the list at
> 	discussion-owner at sipforum.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of discussion digest..."
> 
> 
> Today's Topics:
> 
>    1. Even Port number for RTP in SDP (NK)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Fri, 10 Jan 2014 11:07:34 -0500
> From: NK <nitinkapoorr at gmail.com>
> Subject: [SIPForum-discussion] Even Port number for RTP in SDP
> To: "sip-implementors at cs.columbia.edu"
> 	<sip-implementors at cs.columbia.edu>
> Cc: "sip-implementors at lists.cs.columbia.edu"
> 	<sip-implementors at lists.cs.columbia.edu>
> Message-ID:
> 	<CACFkYe+9aR7w8m9ODn1zXrE+JNPfEHUpEifdBjLPdj5iUZbVTw at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> Dear All,
> 
> Can you please help me on one issue, where one of client is complaining
> that they need RTP even port in SDP not the ODD.  Which is Fax Call.
> 
> Although I checked the RFC 2327 & 4566 for SDP. In RFC 2327 its clearly
> mentioned that we should use even port for RTP compliance, whereas in RFC
> 4566 Its not clearing that is it MANDATORY or not.
> 
> Can you please help me on this.
> 
> >From RFC2327
> 
> 
> 
> m=<media> <port> <transport> <fmt list>
> 
> 
> 
>    A session description may contain a number of media descriptions.   Each
> media description starts with an "m=" field, and is terminated by either
> the next "m=" field or by the end of the session description.A media field
> also has several sub-fields:
> 
>    o The first sub-field is the media type.  Currently defined media
> are "audio",
> "video", "application", "data" and "control", though this list may be
> extended as new communication modalities emerge (e.g.,telepresense).The
> difference between "application" and "data" is that the former is a media
> flow such as whiteboard information, and
> 
> the latter is bulk-data transfer such as multicasting of program executables
> which will not typically be displayed to the user. "control" is used to
> specify an additional conference control channel for the session.
> 
>    o The second sub-field is the transport port to which the media stream
> will be sent.  The meaning of the transport port depends on the network
> being used as specified in the relevant "c" field and on the transport
> protocol defined in the third sub-field.  Other ports used by the media
> application (such as the RTCP port, see
> 
>      [2]) should be derived algorithmically from the base media port.
> 
> 
> *Note: For transports based on UDP, the value should be in the range 1024
> to 65535 inclusive.  For RTP compliance it should be an even number.*
> 
> 
> *Regards,*
> 
> *Nitin Kapoor*
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://sipforum.org/pipermail/discussion/attachments/20140110/a5d6a0ac/attachment-0001.html 
> 
> ------------------------------
> 
> _______________________________________________
> This is the SIP Forum discussion mailing list
> TO UNSUBSCRIBE, or edit your delivery options, please visit http://sipforum.org/mailman/listinfo/discussion
> Post to the list at discussion at sipforum.org
> 
> 
> End of discussion Digest, Vol 102, Issue 11
> *******************************************
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20140118/49d5741e/attachment-0002.html>