<HTML>
<HEAD>
<TITLE>RTCPInstance questions</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Hi all,<BR>
<BR>
I am connecting a client to an RTP server. I instantiate the groupsocks, and the RTPSources and the RTCP instance all fine, and the stream comes in great. However, I have a couple of questions about the RTCPInstance class.<BR>
<BR>
1. Should we be sending RTCP messages when the connection is in a paused state. My initial thoughts were no, but then I thought that without the RTCPInstance running and sending messages, how would a server know the client has not gone away. <BR>
<BR>
2. I have debug turned on and I see RTCP messages being received from myself. Ie: saw incoming RTCP packet (from address 10.221.224.6, port 7999). The client is running on 10.221.224.6, and the server is on a separate box. It looks to me like the client is receiving its own messages, but is not chomping them like I would expect. I think the call to see if the packets was from ourselves (RTCVP.cpp line 336) is failing for some reason. I have no other live555 processes running on the same box, and so would expect the packet to be ignored. <BR>
<BR>
3. Occasionally, I will see the sudden the RTCPInstance schedule function get called in a tight loop. I am unsure what the cause is, I will be investigating further, but was curious to see if anyone has seen this one before. <BR>
<BR>
Regards,<BR>
Stuart</SPAN></FONT>
<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>