<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
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. <br>
<br>
Let's just call this thread dead and I will repost if and when I
find a way to duplicate my problem.<br>
<br>
<br>
Thanks,<br>
Craig<br>
<br>
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<br>
<br>
<div class="moz-cite-prefix">On 11/17/2013 10:32 PM, Ross Finlayson
wrote:<br>
</div>
<blockquote
cite="mid:B7F63AF6-1E07-4701-92BC-E1F6FF5B6BEE@live555.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div>
<blockquote type="cite">
<div text="#000000" bgcolor="#FFFFFF">Sorry, to keep posting.
I think the problem is due to the 400 Bad response from the
Setup. </div>
</blockquote>
<div><br>
</div>
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.</div>
<div><br>
</div>
<div>So I don't understand why you are continuing to report this
problem, which is a problem with the network camera; not our
software.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>So, I think you need to start from scratch, and explain -
clearly and specifically - exactly what your new problem is.</div>
<br>
<div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate;
color: rgb(0, 0, 0); font-family: Helvetica; font-style:
normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal; orphans: 2;
text-align: -webkit-auto; text-indent: 0px; text-transform:
none; white-space: normal; widows: 2; word-spacing: 0px;
-webkit-border-horizontal-spacing: 0px;
-webkit-border-vertical-spacing: 0px;
-webkit-text-decorations-in-effect: none;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width:
0px; "><span class="Apple-style-span" style="border-collapse:
separate; color: rgb(0, 0, 0); font-family: Helvetica;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: 2; text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px;
-webkit-border-vertical-spacing: 0px;
-webkit-text-decorations-in-effect: none;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width:
0px; ">Ross Finlayson<br>
Live Networks, Inc.<br>
<a moz-do-not-send="true" href="http://www.live555.com/">http://www.live555.com/</a></span></span>
</div>
<br>
</blockquote>
<br>
</body>
</html>