Hi,
We are using MobilyGen MG1264 chip.
And they served liveMedia module for rtsp server as qboxserver and client as
qboxreceiver.
Encoder uses rtsp server and Decoder uses rtsp client.
Actually, I don't know what the difference is from your original.
We have problems, as you know I hope.
Thanks for the report. This will be fixed in the next release of the software.
--
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
>Hi,
>
>1) I'm a "streaming" fan and a newbie. When I ran your 555 media
>server, It apparently is streaming from 192.168.86.1. Is this a dhcp
>assigned address?
This depends upon your OS. But it is (in your case) an IP address
for your computer's network interface.
> I haven't had a chance
Hi,
1) I'm a "streaming" fan and a newbie. When I ran your 555 media server,
It apparently is streaming from 192.168.86.1. Is this a dhcp assigned
address? I haven't had a chance to browse thru the code yet. Is it
using default rtp port (I think 5000 or something)?
2) When I ran genWindowsM
Dear Sir:
In an application where the RTSP server has a limit on the number of
connections, the server may send something like "RTSP/1.0 406 Not
Acceptable\r\n\r\n" and/or close the incoming socket immediately because the
max number of connection is reached.
If the sample agent openRTSP(VLC, too)
Ross Finlayson <[EMAIL PROTECTED]> wrote:
> Probably the easiest fix for this problem (until I get around to
> rewriting/cleaning up the whole RTSP request parsing code) is to
> change
> j < reqStrSize-8
> to
> (int)j < (int)(reqStrSize-8)
Hey Ross,
I'm happy that you liked my bug r
