From: Mike McCool <[EMAIL PROTECTED]>
Subject: RTSP/1.0 and ClientChallenge
Hi all -
I didn't see this in the archives, so forgive me if this =
has been asked before.
I'm trying to write a simple RTSP/1.0 server that can =
broadcast WAV files over RTP. I've implemented most of =
the functionality, but the RealPlayer G2 won't talk to =
my server. The client sends me an OPTIONS request =
with a header "ClientChallenge", which has a long =
string of letters and numbers after it. =
The Basic RealServer appears to answer this =
ClientChallenge with a RealChallenge1 header, which =
also has a long string of letters and numbers. The =
client responds with a RealChallenge2, and the server =
responds with a RealChallenge3.
In my server, I ignore the client's challenge. The =
client gets to the phase of doing a SETUP on the WAV =
file, but then it will TEARDOWN the connection and =
tell the user that the server is invalid. However, =
I've found that if I filter out the challenge headers, =
the client does the exact same thing to the Basic server.
So what I'm wondering is:
- What are these Challenge headers?
- What's their purpose?
- How do I generate them or work around producing them?
Any help would be appreciated. Thanks!
--MLM
