Re: [Opalvoip-devel] Strange RTP connection behavior

[Robert J. <ro...@vo...>]

On 15/06/2013 4:15 PM, Yuriy Cherniavsky wrote:
> Answers inlined below.
>
> On 13 июня 2013, at 03:26, Robert Jongbloed <ro...@vo... 
> <mailto:ro...@vo...>> wrote:
>
>> May I ask, why do you have a "replacement 
>> for AutoStartMediaStreams()" ? What was wrong with it?
> The problem with AutoStartMediaStreams method for me, that on calling 
> my Alerting/Ringing method (its code you can find on this mail thread) 
> for incoming H323 call, it starts patch thread only for 
> outgoing MediaStream. And yes, calling part is hearing my ringtone, 
> but at the same time calling part is sending me some RTP data too (I 
> have checked it with OpenPhone and AddPack). But patch thread for 
> incoming MediaStream was not started, so nobody is reading from RTP 
> socket, and all incoming RTP packets stay in OS socket incoming buffer.

You need to call AutoStartMediaStreams on both connections in the call, 
exactly like you did with OpenSourceMediaStreams() in your code.

> I would like to build this functionality into OpalLocalEndPoint, if I can.
> Of course it will be great, but I see that this problem with patch 
> threads starting sequence much deeper.

I have checked in a possible solution, can you try the current code?

Revision: 29937
Author: rjongbloed
Date: Thursday, 13 June 2013 12:03:10 PM
Message:
Added ability to start early media when alerting on incoming call via 
OpalLocalEndPoint/OpalLocalConnection.
----
Modified : /opal/branches/v3_12/src/opal/opal_c.cxx
Modified : /opal/branches/v3_12/include/opal.h
Modified : /opal/branches/v3_12/src/ep/localep.cxx
Modified : /opal/branches/v3_12/include/ep/localep.h



*Robert Jongbloed*
/OPAL/OpenH323/PTLib Architect and Co-founder./
Commercial support at http://www.voxlucida.com.au