On Thu, May 29, 2008 at 4:57 PM, Ross Finlayson <[EMAIL PROTECTED]> wrote:
You're correct that you can't use the usual *RTP*Source and *RTP*Sink
classes. However, because you wish to pass the RTP header fields 'as is',
you could instead read and send raw-UDP (rather than RTP) packets. You ca
On Thu, May 29, 2008 at 4:57 PM, Ross Finlayson <[EMAIL PROTECTED]> wrote:
> You're correct that you can't use the usual *RTP*Source and *RTP*Sink
> classes. However, because you wish to pass the RTP header fields 'as is',
> you could instead read and send raw-UDP (rather than RTP) packets. You c
I would like to use live555 to create and RTP translator that simply
encrypts the payload of the RTP packets and preserves header
information such as SSRC as required by the RTP standard. It seems to
me I cannot use the usual source/sink facilities since then the sink
would create new header infor
Hello,
I would like to use live555 to create and RTP translator that simply
encrypts the payload of the RTP packets and preserves header
information such as SSRC as required by the RTP standard. It seems to
me I cannot use the usual source/sink facilities since then the sink
would create new heade
