[sip-comm-dev] FW: SC blocks after placing a few SIP Calls

Carlos Alexandre Carlos.Alexandre at nav.pt
Wed Jul 29 20:57:05 CEST 2009


Hi Emil


I think this is fixed.
I have made some testing but it never hapened again. 


But a new problem has come up with the hunging up of calls. Ill start a thread with it to keep them separated.


 
Thanks
Carlos



-----Original Message-----
>From: Emil Ivov [mailto:emcho at sip-communicator.org] 
Sent: quarta-feira, 8 de Julho de 2009 18:41
To: dev at sip-communicator.dev.java.net
Cc: <dev at sip-communicator.dev.java.net>
Subject: Re: [sip-comm-dev] FW: SC blocks after placing a few SIP Calls

Hey Carlos,

If this is fixed (i.e. If the reason was really direct sound then),  
the latest build should work since DirectSound has been disabled there.

Cheers
Emil


--sent from my mobile

On 8 juil. 2009, at 19:15, "Carlos Alexandre"  
<Carlos.Alexandre at nav.pt> wrote:

> Hi guys
>
> I received an email about the issue that i placed ( 677)
>
> It says that this is probably resolved with r5498.
>
> Where can i get r5498? I always get the code from the nightly builds  
> at
> http://sip-communicator.org/download/nightly-builds/src/
>
>
> or else,
>
> witch build has this fix ?
>
> Thanks
>
> Carlos
>
>
> -----Original Message-----
> From: Lubomir Marinov [mailto:lubomir.marinov at gmail.com]
> Sent: quarta-feira, 17 de Junho de 2009 21:19
> To: dev at sip-communicator.dev.java.net
> Subject: Re: [sip-comm-dev] FW: SC blocks after placing a few SIP  
> Calls
>
> Hi Emil,
>
> I don't have an opinion about adding the freeze reported by Carlos to
> issue #524.
>
> I just want to note that
> https://sip-communicator.dev.java.net/issues/show_bug.cgi?id=658
> reported by Werner describes crashes in the same DirectSound class
> (though in a #read method). I thought it may be a good idea to create
> an umbrella issue for DirectSound to list the various separate issues
> we've stumbled upon.
>
> Best regards,
> Lubo
>
> 2009/6/17 Emil Ivov <emcho at sip-communicator.org>:
>>
>>
>> Lubomir Marinov wrote:
>>> Hi Carlos,
>>>
>>> Thank you! The stack trace shows that DirectSound has blocked the
>>> telephony services for the SIP account when we're trying to  
>>> disconnect
>>> from DirectSound on hang-up.
>>
>> One more issue with direct sound then. Should we add this to
>> https://sip-communicator.dev.java.net/issues/show_bug.cgi?id=524
>>
>> I am not sure this is exactly the same problem but disabling  
>> DirectSound
>> (at least temporarily) seems like a good way to solve both. I guess  
>> this
>> is what we'll do for 1.0
>>
>> Cheers
>> Emil
>>
>>>
>>> As to writing follow-ups to a specific issue, I think you should be
>>> seeing a text area titled Additional Comments when you log into
>>> java.net with your account and visit the issue and it should allow  
>>> you
>>> to add... well, additional comments to the issue.
>>>
>>> Regards,
>>> Lubomir
>>>
>>> 2009/6/17 Carlos Alexandre <Carlos.Alexandre at nav.pt>
>>>> Hi
>>>> I did as you asked
>>>>
>>>> Im attaching 2 files:
>>>>
>>>> Stack_1.txt -> stack after ending the call with blocking hung up.
>>>>
>>>> Stack_2.txt -> stack after placing the following ( and blocked )  
>>>> call.
>>>>
>>>> Hope it helps
>>>>
>>>>
>>>>
>>>> Carlos
>>>>
>>>>
>>>> By the way, is there a way to place a followup in my issues? All  
>>>> i se eis the option to attach files....id like to add some text...
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: Lubomir Marinov [mailto:lubomir.marinov at gmail.com]
>>>> Sent: quarta-feira, 17 de Junho de 2009 17:33
>>>> To: dev at sip-communicator.dev.java.net
>>>> Subject: Re: [sip-comm-dev] FW: SC blocks after placing a few SIP  
>>>> Calls
>>>>
>>>> Hello Carlos,
>>>>
>>>> When the hang happens, could you please create a thread stack trace
>>>> and mail it to us so that we can get further details about it? If  
>>>> you
>>>> have JDK installed, jps will show the PID of the SIP Communicator
>>>> process and jstack <PID> will display the thread stack trace.
>>>>
>>>> If you're experiencing the hang on Windows, the problem sounds like
>>>> the DirectSound hangs some of us have run into.
>>>>
>>>> Thank you,
>>>> Lubomir
>>>>
>>>> 2009/6/17 Werner Dittmann <Werner.Dittmann at t-online.de>:
>>>>> An "old friend" is back ;-) . There are several reports on such  
>>>>> a behaviour
>>>>> some months ago (need to look in the mail archive to get the  
>>>>> mails) but
>>>>> my analysis had the same result: some function in Media handling  
>>>>> did
>>>>> not return and caused the lock you describe.
>>>>>
>>>>> The problem is random and sporadic, thus not easy to fix, also I  
>>>>> don't
>>>>> have the sources of the media (IMHO JMF) library that contains the
>>>>> non-returning function. Also there is a difference between  
>>>>> Windows and
>>>>> Linux implementations of JMF. Maybe this problem is a good  
>>>>> reason to
>>>>> put more emphasis to switch to FMJ where the sources are  
>>>>> available.
>>>>>
>>>>> Regards,
>>>>> Werner
>>>>>
>>>>> Carlos Alexandre schrieb:
>>>>>> After further investigations, it seems there is a deadlock  
>>>>>> between
>>>>>>
>>>>>>
>>>>>>
>>>>>> public synchronized void hangupCallParticipant(CallParticipant  
>>>>>> participant)
>>>>>>
>>>>>>
>>>>>>
>>>>>> of the hunging up of the last call
>>>>>>
>>>>>>
>>>>>>
>>>>>> and
>>>>>>
>>>>>>
>>>>>>
>>>>>> private synchronized CallSipImpl createOutgoingCall(Address  
>>>>>> calleeAddress,javax.sip.message.Message cause) throws  
>>>>>> OperationFailedException
>>>>>>
>>>>>>
>>>>>>
>>>>>> of the following call...
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> public synchronized void hangupCallParticipant(CallParticipant  
>>>>>> participant) never returns because it blocks at the  
>>>>>> "MediaPushBufferDataSource.disconnect()" method that is invoked  
>>>>>> somewhere by it.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> thanks
>>>>>>
>>>>>> ________________________________
>>>>>>
>>>>>> From: Carlos Alexandre [mailto:Carlos.Alexandre at nav.pt]
>>>>>> Sent: quarta-feira, 17 de Junho de 2009 12:46
>>>>>> To: dev at sip-communicator.dev.java.net
>>>>>> Subject: RE: [sip-comm-dev] FW: SC blocks after placing a few  
>>>>>> SIP Calls
>>>>>>
>>>>>>
>>>>>>
>>>>>> After some debugging i found out where exactly SC blocks:
>>>>>>
>>>>>> It blocks while disconnecting a call, while  
>>>>>> performing               the  
>>>>>> "MediaPushBufferDataSource.disconnect()" method.
>>>>>>
>>>>>>
>>>>>>
>>>>>> This can happen randomly , but allways in the first 10 or so  
>>>>>> calls.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hás this happened to anyone?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Carlos
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ________________________________
>>>>>>
>>>>>> From: Carlos Alexandre [mailto:Carlos.Alexandre at nav.pt]
>>>>>> Sent: segunda-feira, 15 de Junho de 2009 12:41
>>>>>> To: dev at sip-communicator.dev.java.net
>>>>>> Subject: [sip-comm-dev] FW: SC blocks after placing a few SIP  
>>>>>> Calls
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ________________________________
>>>>>>
>>>>>> From: Carlos Alexandre
>>>>>> Sent: terça-feira, 9 de Junho de 2009 17:56
>>>>>> To: 'users at sip-communicator.dev.java.net'
>>>>>> Subject: SC blocks after placing a few SIP Calls
>>>>>>
>>>>>>
>>>>>>
>>>>>> I have SC configured with a SIP account (5003, IP  
>>>>>> 200.200.200.249) and running
>>>>>> against an Asterisk SIP server (IP 200.200.200.10).
>>>>>>
>>>>>>
>>>>>>
>>>>>> After placing 5 or 6 successfull calls to another phone (1001),  
>>>>>> SC blocks , and
>>>>>> the call button stops having any efect. Its not possible to  
>>>>>> place any more calls.
>>>>>>
>>>>>>
>>>>>> I tested with build 1896
>>>>>>
>>>>>>
>>>>>>
>>>>>> Here is the FINEST log
>>
>> --
>> Emil Ivov, Ph.D.                               67000 Strasbourg,
>> Project Lead                                   France
>> SIP Communicator
>> emcho at sip-communicator.org                     FAX:   +33.1.77.62.47.31
>> http://sip-communicator.org                    PHONE: +33.1.77.62.43.30
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe at sip-communicator.dev.java.net
> For additional commands, e-mail: dev-help at sip- 
> communicator.dev.java.net
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe at sip-communicator.dev.java.net
> For additional commands, e-mail: dev-help at sip- 
> communicator.dev.java.net
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe at sip-communicator.dev.java.net
For additional commands, e-mail: dev-help at sip-communicator.dev.java.net


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe at sip-communicator.dev.java.net
For additional commands, e-mail: dev-help at sip-communicator.dev.java.net





More information about the dev mailing list