<HTML>
<HEAD>
<TITLE>Re: [Live-devel] RTCPInstance questions</TITLE>
</HEAD>
<BODY>
<BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>>2. I have debug turned on and I see RTCP messages being received<BR>
>from myself. <BR>
>I presume this is a multicast session (if it were a unicast session,<BR>
>then the RTCP packets should be sent back directly to the server, and<BR>
>the client would never get a chance to receive them itself). I<BR>
>didn't see a question in the paragraph above - but Remember, You Have<BR>
>Complete Source Code.<BR>
<BR>
It turns out I was handling the Groupsocks wrong.<BR>
I have an RtpReceiver class that takes 3 parameters sourceIP destinationIP and destinationPort.<BR>
In multicast mode, the destinationIP would be the multicast address, in unicast mode it would be the IP of the interface the application would receive the stream on.<BR>
<BR>
I was setting the groupAddr of the rtcp socket to be the destination address always (which would mean I would send the packets to myself in unicast, and the multicast group in multicast). Obviously this is wrong, as I should always be sending directly back to the source. I have made this change and things are looking good. <BR>
<BR>
As I was checking into how to setup the groupsocks, I seem to see that in the MediaSession class the groupAddr passed to the changeDestination call is the multicast address when streaming multicast, but the source address of the server when streaming unicast. Is this correct? If so how does one account for multi-homed systems. I am presuming it will filter on the SSRC of the incoming packet?<BR>
<BR>
Thanks for the reply btw, figured it out pretty quick after that.<BR>
<BR>
Stuart</SPAN></FONT></BLOCKQUOTE>
<BR>
- ------------------------------------------------------------------------------<BR>
Confidentiality Notice: The information contained in this transmission is legally privileged and confidential, intended only for the use of the individual(s) or entities named above. This email and any files transmitted with it are the property of Pelco. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you receive this communication in error, please notify us immediately by telephone call to +1-559-292-1981 or forward the e-mail to administrator@pelco.com and then permanently delete the e-mail and destroy all soft and hard copies of the message and any attachments. Thank you for your cooperation. <BR>
- ------------------------------------------------------------------------------<BR>
</BODY>
</HTML>