[Live-devel] RTSP Client and multicast with AXIS cameras

[Federico Ares]

Hi,

I send a regular rtsp:// request for Axis Cameras. The RTSP transaction is 
complete, and the multicast  stream starts. I believe that "ax protocol" has 
effect only on media player and will not affect RTSPClient's performance.

I still got some problems with the code:

In parseTransportResponse() I had to add a "return true;" line and comment 
the "delete[] foundDestinationStr;" line. Otherwise parseTransportResponse 
returns false even when multicast transport field is parsed correctly.

if (isMulticast && foundDestinationStr != NULL && foundMulticastPortNum)
{
    delete[] foundServerAddressStr;
    serverAddressStr = foundDestinationStr;
    serverPortNum = multicastPortNumRTP;
    return true; // add this line
}
//delete[] foundDestinationStr;

The code still doesnt work for me. Still have the same problem: the server 
starts transmitting but there are no frames incoming. I'm starting to worry 
about my own build. All other stuff seems normal.

I'll give it a look a couple of days and see what I can find out.

Have a nice weekend,

Federico Ares.

----- Original Message ----- 
From: "kamil" <kamildobk at poczta.onet.pl>
To: "LIVE555 Streaming Media - development & use" 
<live-devel at ns.live555.com>
Sent: Thursday, November 03, 2005 8:35 AM
Subject: Re: [Live-devel] RTSP Client and multicast with AXIS cameras


> Hi,
> Thank you for those improvements - I have waited for them too.
>
> In fact it is called an 'Ax protocol' - which is some undocumented 
> Microsoft crap - see :http://www.axis.com/techsup/faq/index.php?id=53526.
> Maybe if some more people complain about it Axis will fix it in some 
> future version.
>
> Some other broken things in Axis protocol I noticed are:
> 1.
> Timeout for multicast session - Axis232D stops sending multicast stream 
> after 60 seconds, I found following explanation:
> http://www.axis.com/techsup/cam_servers/dev/cam_rtsp_api.htm
> 'If the Session header includes a timeout parameter, then the session 
> needs to be kept alive. This can be done by sending RTSP requests to the 
> server containing the session identifier (e.g. OPTIONS) within the 
> specified timeout time or through the use of RTCP.'
> 2.
> Authorization for RTPoverHTTP is required in initial GET/POST requests ( 
> eg. header field 'Authorization: Basic xxxxx' ), and not only in tunneled 
> RTSP.
>
>
>
>
>
>
>
> _________________________________________________________________
> List sprawdzony skanerem poczty mks_vir ( http://www.mks.com.pl )
> _______________________________________________
> live-devel mailing list
> live-devel at lists.live555.com
> http://lists.live555.com/mailman/listinfo/live-devel