XP
(1)
Theitn
(1)
Myencoder
(1)
Flinches
(1)
Latency
(1)
Encoder
(1)
Windows
(1)
Aioewit
(1)

WME stops after live broadcast stream startup

Asked By Justin
17-Nov-09 09:51 PM
We are streaming from an XP PC over the public internet to a 2003 server in a
different state.  The encoder will often stop after starting a live audio
stream (push method).  It may stop once or twice, after a short time (few
seconds to a minute) of streaming.  (I have to click Start again to get it
going.)  It might give an error of 'no connection with the server'.  (The
server never flinches or gives any indication of an error.)  After that it
will stream fine for rest of the session.  I do not see anything going on that
would lead me to the problem.  It does not seem to be a networking issue,
unless is it some kind latency issue.

Any ideas as to what might be the problem?

Thanks,
Justin

Justin wrote:I have always had problems using push method.

BC replied to Justin
17-Nov-09 10:21 PM
I have always had problems using push method. Always best to pull if
possible..

BC, this would require the server publishing point to be manually started

Justin replied to BC
17-Nov-09 11:27 PM
BC, this would require the server publishing point to be manually started and
the encoder would have to be seen as a web site, right?  This is not
practical in my case.  The encoder needs to be able to initiate the stream
and start the publishing point.

Justin

Justin wrote:Hi Justin,The publishing point can be set to start automatically

BC replied to Justin
19-Nov-09 06:01 AM
Hi Justin,

The publishing point can be set to start automatically or start when the
first user connects so this is not an issue. I do not get what you mean
about encoder being seen as a website.. I will say again and I am using
this stuff since windows media services on Windows NT4.0 - push from
encoder is not reliable. If any kind of network congestion happens the
encoder loses it is connection and does not reconnect.

BC
"BC" wrote:Mr.
Justin replied to BC
20-Nov-09 09:15 PM
Mr. BC, what I meant was that when you configure the PULL pub point, you
have to supply the URL to the encoder, eg http://myencoder:8080.  Therefore,
the machine the encoder is on must allow an external connect and a static IP.
I'd really like to try this out (because you say it is more reliable) if I
can make it robust and easy.  To be clear, my current push "location" is

appreciate the help,
Justin
Justin wrote:Justin,You need to open up port 8080 (it is the default) and NAT
BC replied to Justin
21-Nov-09 03:21 PM
Justin,

You need to open up port 8080 (it is the default) and NAT it to your
encoder box from the outside.

Then on the WMS put in the location as http://yourpublicip:8080
in aioewit(Theitn that,See http://support.microsoft.com/kb/895182
Volna replied to Justin
23-Nov-09 06:17 AM
in a
io
ew
it
(The
it
n that
,

See http://support.microsoft.com/kb/895182
Post Question To EggHeadCafe