I agree Ross. I apologize for the confusion I have been looking for away to duplicate the problem I saw and thought I had duplicated the problem. I did repost that I found out that the camera firmware was still out of date.
Let's just call this thread dead and I will repost if and when I find a way to duplicate my problem. Thanks, Craig I'm working on a way to duplicate the issue I have seen. I'm sorry but I don't recall saying I could not stream from port 554, as I have been using 554 On 11/17/2013 10:32 PM, Ross Finlayson wrote: Sorry, to keep posting. I think the problem is due to the 400 Bad response from the Setup. Yes, and I'm totally confused - because this is the *exact same problem* that you reported two weeks ago. The conclusion at that time was that this was due to a bug in your back-end server (a 'Vivotek' network camera). The solution to this problem (and the only one that I will consider, unless I hear directly from 'Vovotek') is to get Vivotek to fix their cameras. So I don't understand why you are continuing to report this problem, which is a problem with the network camera; not our software. I'm also confused because - in your first message on this thread (and noted in the "Subject:" line) - you said that you were having a problem streaming from a back-end server that used a port number other than 554, but were not having any problem streaming from back-end servers (other than, presumably, Vivotek cameras) that used port 554. Yet all of the examples that you gave today used port 554. So, I think you need to start from scratch, and explain - clearly and specifically - exactly what your new problem is. Ross Finlayson Live Networks, Inc. http://www.live555.com/
_______________________________________________ live-devel mailing list [email protected] http://lists.live555.com/mailman/listinfo/live-devel
