Exceptions when using ICE functionalities

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

 



On Wed, Aug 6, 2008 at 11:42 AM, Pedro Gon?alves <pedro.pandre at gmail.com>wrote:

> Benny Prijono wrote:
>
>> On Tue, Aug 5, 2008 at 6:20 PM, Pedro Gon?alves <pedro.pandre at gmail.com<mailto:
>> pedro.pandre at gmail.com>> wrote:
>>
>>    Hi!
>>
>>    With the help from PJSIP list useres, I think I am close to having my
>>    program to use PJSIP's ICE functionalities 100% correctly.
>>
>>
>> Not that I'm discouraging you, but I think you've still got some issues to
>> fix there (as discussed on the other thread). :)
>>  Regarding the crashes below, do you know in what stage did these happen?
>> E.g. during ICE creation, in the middle of conversation, or during ICE
>> destroy sequence? We had this bug that looks similar:
>> http://trac.pjsip.org/repos/ticket/567
>>
>>
>>  About the other issues (the ones you told in the other thread, I moved
> the stream destruction to on_media_update(), but these problems persist
> (these problems happen in the answerer).
>
>
Is the problem still with stream not being closed? So what do you exactly do
in on_media_update()? And is on_media_update() called? And do you close the
stream when the call is disconnected? A snippet will help.

And lets discuss this on separate/the other thread please.



> About 1), the failing assert, it happens after initial offer / answer, but
> before the subsequent offer, during ICE negotiation (more specifically,
> during ICE connectivity checks).
>
> I've included both the application log and the capture I made during the
> exception.
>
> I can reproduce this behaviour at any time, so if there is something I can
> do to help us debug this issue, just ask.
>
> I've added some debug information in some PJSIP files, in order to help me
> understand the problem. As you can see in the end of the log, the assert
> problem seems to come from somewhere before pj_stun_session_on_rx_pkt, is it
> not?
> 11:19:15.375 stun_session.c pandre-dbg tdata=339762268
> check->tdata=338037852 on pj_stun_session_on_rx_pkt ckid=0
> 11:19:15.687 stun_session.c pandre-dbg tdata=339762268
> check->tdata=338037852 on on_incoming_response ckid=0
> 11:19:16.292 stun_session.c pandre-dbg tdata=339762268
> check->tdata=338037852 on stun_tsx_on_complete(1)
> 11:19:16.335 stun_session.c pandre-dbg tdata=339762268
> check->tdata=338037852 on stun_tsx_on_complete(2)
>
>
Unfortunately I didn't see the messages (above) in the log, probably because
the file has not completely been written when the assertion occurs. When the
"pj_assert(tdata == check->tdata)" assertion occurs, does "check->tdata"
contain a value, or is it NULL?

Cheers
 Benny
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20080806/f92c2ef2/attachment.html 


[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux