Thank you Ross for you reply. Unfortunately, we have no control over camera manufacturers. In many cases, we will not even know which camera has been used by users of our software. We can probably request cameras that we test against in-house to upgrade their software - but then, every camera manufacturer will need their own time for testing out new f/w before releasing the same for upgrade. We cannot wait that long.
Moving forward, we need to find a solution to this problem, so we will invest time in tracking where the bug is. I have two questions in this regard: (a) Will it be beneficial to increase socket's 'receive' buffer size in 'createNewRTPSink' for the RTP source? (This used to be done in older version of openRTSP) (b) Since network cameras are live source of stream, they may not be "pausable". I think most do not support PAUSE command at all. In such a case, data will continue to come from the back-end server even though there is no downstream clients connected. So instead of sending "PAUSE" to backend server (network camera), can we disconnect the connection and start from beginning (send DESCRIBE, and wait for clients to connect)? If this sounds good, what do we need to change in 'ProxyServerMediaSession' code? Thank you for your assistance. Regards, Subhankar. From: live-devel-boun...@ns.live555.com [mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross Finlayson Sent: Thursday, August 29, 2013 3:14 PM To: LIVE555 Streaming Media - development & use Subject: Re: [Live-devel] Issue in ProxyServerMediaSession I think I know what is happening (a "SocketDescriptor" object is getting deleted twice), but unfortunately I don't know why. (A bug like this was fixed in July, but if you're using a recent version of the code, then it appears that another bug remains.) Unfortunately, because noone else has reported this, you're probably going to have to track down this bug yourself. However, you also mentioned the following: In verbose enabled, I see lots & lots of following prints: "RTCPInstance error: Hit limit when reading incoming packet over TCP. Increase "maxRTCPPacketSize" This suggests that your back-end servers (i.e., network cameras) may be implemented using our software, but using an old version. If you upgrade these cameras to use a recent version of our software, then it's possible that they may no longer trigger the bug that you are finding in the proxy server. Note that if the cameras are using our software, then the camera manufacturer is legally *required* - under the terms of the LGPL - to, upon request, upgrade them to use the latest version of the code, or else tell you how you can do this yourself. So, you should ask the camera manufacturer(s) to upgrade their software. Ross Finlayson Live Networks, Inc. http://www.live555.com/ ________________________________ http://www.mindtree.com/email/disclaimer.html
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
