Can you please do the trace log again, this time with the PTrace::Thread
and PTrace::ContextIdentifier options enabled?
There seems to be something going on with the mixer push threads, but I
can't track them without those trace. options.
Also, you can send me the trace logs directly rather than to the mailing
list.
*Robert Jongbloed*
/OPAL/OpenH323/PTLib Architect and Co-founder./
Commercial support at http://www.voxlucida.com.au
On 14/05/2014 6:43 AM, Giovani Gracioli wrote:
> I attached the complete log in this email. Note that there are no
> messages from the RTP session 2, which is suppose to be the video
> session. As a consequence, there are no messages of video decoding
> (H263plus video codec in this case). In line 1994, the video stream
> session is opened.
>
> On 10/05/2014 5:55 AM, Giovani Gracioli wrote:
>
>> Thank you for your answer Robert.
>>
>> The system is a CentOS 6.5 with kernel 2.6.32. The OPAL version
>> is 3.14.0 and the PTLib version is 3.14.0 (both were downloaded
>> using the tarball file at the website).
>>
>> I have two soft-phones (two different SIP numbers - 9003 and
>> 9036) calling an OPAL program, which is also a SIP number (9038).
>> They all are registered in an asterisk server. You can see the
>> OPAL program as a server that will receive SIP calls and create a
>> kind of conference, forwarding audio and video to all
>> participants. The final objective is to have some video
>> processing before forwarding, but by now I am using the original
>> OPAL mixer.
>>
>> The soft-phones are running on different windows machines (bria
>> soft-phone). Both are configured to use the g711-alaw audio and
>> h263plus video codecs. When I call to each other directly,
>> without passing to the OPAL program, video and audio are
>> transmitted without problem. When I call to the OPAL program,
>> only the audio is transmitted.
>>
>> I attached the complete log in this email. Note that there are no
>> video decoding nor encoding messages, is this right? I am not
>> sure if they are selecting the right video codec, but there are
>> messages selecting the right codec, such as in line 2680:
>>
>> 2014/05/09 16:33:55.820 SDP Matching "H263-1998",
>> pt=[pt=111], clock=90000
>>
>> The point is that for some unknown reason, video is not being
>> decoded/encoded or transmitted/retransmitted.
>>
>>
|