[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Linphone-developers] oRTP - only one of two sessions receiving data

From: t
Subject: Re: [Linphone-developers] oRTP - only one of two sessions receiving data...
Date: Mon, 18 Apr 2011 07:20:33 -0400

Ya hi,

Clearly the rtp must use different source ports and the client must recognize the source ports as different streams...

Since you don't mention udp ports, it's a fair assumption that you did not consider this.


On Sun, Apr 17, 2011 at 8:04 PM, John Pallister <address@hidden> wrote:
Hello list,

I'm really hoping someone can suggest something helpful for me here...

My application runs on Windows XP SP3 over an intranet. No DNS, no
DHCP, no routing, very simple. It uses oRTP for simple point-to-point
routing of G.729-encoded audio; no RTCP, SIP etc. It is compiled with
Visual C++ 2008.

The scenario: a "router" process sends two simultaneous copies of an
RTP stream (received from another process elsewhere on the network) to
two separate oRTP sessions in two threads of a client process, to be
played out of two different audio devices. The RTP stream copies have
different source and destination ports (but are otherwise identical);
the destination ports correspond to those of the oRTP sessions.

The problem: I expect to receive both stream copies, however either
zero, one or two will be received by my application code from oRTP. I
can determine no pattern to how many copies will "work". Multiple
single streams (i.e. not duplicate streams sent simultaneously) are
received correctly and reliably.

Does anyone have any experience with this sort of situation (or
anything vaguely similar), on Windows or otherwise? Am I being naïve
in expecting this to work? Does my router need to do something to the
stream copies to enable them to be reliably differentiated and
received correctly?

Thanks very much,

John :^P
John Pallister

Linphone-developers mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]