Re: [Ekiga-devel-list] VP200 H323 protocol hung after successive incoming calls

[Lorin Melander <lwmelander gmail com>]

Ekiga normally destroy PCSS sound endpoint. That's happen you saw.
Ekiga will upgrade from GMAudioInputManager_null to GMAudioInputManager_ptlib.
whenever the connection is successful.

-LM
On Thu, Feb 17, 2011 at 1:28 AM, Eugen Dedu
<Eugen Dedu pu-pm univ-fcomte fr> wrote:
> On 17/02/11 05:57, lwmelander wrote:
>>
>>
>> I am testing on Ekiga 3.2.7 and 3.3.0 version against the VP200 Sorenson
>> VRS
>> which is very popular h232 devices among deaf people.  I notice first
>> VP200
>> call to Ekiga is good but Ekiga ignores successive calls even though VP200
>> is showing me there is ringing in Ekiga and I answer on Ekiga.  Nothing
>> happens.
>
> You mean the connection is established, but you do not hear anything, is
> that right?
>
> This is shown here:
> 2011/02/16 19:44:27.093   0:20.985       Media Patch:0xa68eeb70
> GMAudioInputManager_ptlib       Trying to get frame from closed device
> 2011/02/16 19:44:27.093   0:20.985       Media Patch:0xa68eeb70
> AudioInputCore  Closing current device
> 2011/02/16 19:44:27.093   0:20.985       Media Patch:0xa68eeb70
> GMAudioInputManager_ptlib       Closing device Default (PTLIB/ALSA)
> 2011/02/16 19:44:27.093   0:20.985       Media Patch:0xa68eeb70
> AudioInputCore  Falling back to SILENT (Ekiga/Ekiga)
> 2011/02/16 19:44:27.093   0:20.985       Media Patch:0xa68eeb70
> GMAudioInputManager_null        Setting Device SILENT (Ekiga/Ekiga)
> 2011/02/16 19:44:27.093   0:20.985       Media Patch:0xa68eeb70
> AudioInputCore  Opening device with 1-8000/16
> 2011/02/16 19:44:27.093   0:20.985       Media Patch:0xa68eeb70
> GMAudioInputManager_null        Opening Device SILENT (Ekiga/Ekiga)
> 2011/02/16 19:44:27.093   0:20.985       Media Patch:0xa68eeb70
> GMAudioInputManager_null        Opening Device with 1-8000/16
> 2011/02/16 19:44:27.093   0:20.985       Media Patch:0xa68eeb70 Patch
> Thread ended because all sink writes failed
>
> But I do not know why this happens.
>
> Can anyone help?
>
>> Both Ekiga version works properly when the calls are directed to the
>> VP200.
>> I have output debug file.
>>
>> I am using Ubuntu 10.10.
>> Based on Ekiga 3.3.0 debugging
>> file:///home/lorin/debug/myin.log
>> http://ekiga.1756082.n4.nabble.com/file/n3310195/myin.log myin.log
>
> --
> Eugen
> _______________________________________________
> ekiga-devel-list mailing list
> ekiga-devel-list gnome org
> http://mail.gnome.org/mailman/listinfo/ekiga-devel-list
>