<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2658.2">
<TITLE>RTSP channel</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2 FACE="Arial">We are developing a new * plugin to make it interoperable with RTSP Streamming servers like Darwin. In this way it would be possible, eg, to make any * video enabled terminal (like sip and h323) to access Real-time multimedia content. For that we are developing an * RTSP channel.</FONT><FONT FACE="Times New Roman"> We are having the following approach:</FONT></P>
<P><FONT FACE="Times New Roman">1- we have an application that handles the RTSP messages exchanged with RTSP server (eg Darwin) that will initialise an ast_channel struct (only with the values needed for the RTP/RTCP session) to link the terminal with RTSP server.</FONT></P>
<P><FONT FACE="Times New Roman">2- we will move the RTSP messages from the application to a new RTSP channel module and complete the ast_channel struct initialization.</FONT></P>
<P><FONT FACE="Times New Roman">This way we may reuse any existing * application like Dial to redirect * extensions to RTSP addresses to have services like simple playvideo or new applications for more complex services like Video portals (to add video to existing voice portals) where we can associate dtmf commands to RTSP commands like pause/play.</FONT></P>
<P><FONT FACE="Times New Roman">What do you think about this approach? Anyone interested to collaborate on this ?</FONT>
<BR><FONT FACE="Times New Roman">Regards,</FONT>
<BR><FONT FACE="Times New Roman">PCh & Neutel</FONT>
</P>
</BODY>
</HTML>