Re: [Ekiga-list] Ekiga 3.2.6 - worked once only



David Ford wrote:
> Hi Eugen
> 
> On 15/04/10 13:27, Eugen Dedu wrote:
>> David Ford wrote:
>>   
>>> Hi Eugen
>>>
>>> On 15/04/10 12:02, Eugen Dedu wrote:
>>>     
>>>> David Ford wrote:
>>>>
>>>>       
>>>>> Hi Eugen
>>>>>
>>>>> On 15/04/10 08:49, Eugen Dedu wrote:
>>>>>
>>>>>         
>>>>>> David Ford wrote:
>>>>>>
>>>>>>
>>>>>>           
>>>>>>> . . . Loads removed . . .
>>>>>>> Do I need to phaff around with the router/some firewall or is
>>>>>>> everything
>>>>>>> working OK and I'm not doing something right?
>>>>>>> Is there some information in the log that I should be looking for
>>>>>>> specifically?
>>>>>>> Are these bits enough or do you want the whole log?
>>>>>>>
>>>>>>>
>>>>>>>              
>>>>>> For me, they are not sufficient.  So the problem is that you cannot
>>>>>> succeed to register, is that right?  Please send the full -d 4.  You
>>>>>> can
>>>>>> also look at the REGISTER packet and the answers.
>>>>>>
>>>>>>
>>>>>>            
>>>>> I've attached the log - I hope it's small enough to get through
>>>>>
>>>>>          
>>>> Well, I see an error:
>>>> 2010/04/14 21:02:59.390      0:09.229
>>>> STUN    STUN
>>>> server 75.101.138.128:3478 unexpectedly went offline.
>>>>
>>>> and afterwards I see that you send a few packets but you do not receive
>>>> any (in fact you do not receive any packet, but STUN had worked).
>>>>
>>>>
>>>>        
>>> It's the same in this log too - but "ping stun.ekiga.net" ran the whole
>>> time with no packet loss.
>>>     
>>>> Does you network connection stop right after starting ekiga?!  Do ping
>>>> stun.ekiga.net and ping ekiga.net work?
>>>>
>>>>
>>>>        
>>> I've put the log here - http://filebin.ca/wapctb/ekiga.d4 - Thanks for
>>>      
>> Hi David,
>>
>> I see now another error:
>>
>> 2010/04/15 12:12:18.653      0:07.758                              
>> MonSock
>> Closed UDP socket 0x91263f0
>> 2010/04/15 12:12:18.653      0:07.758    Opal Liste...0xb70beb70   
>> Listen    UDP
>> read error.
>> 2010/04/15 12:12:18.673      0:07.779                              
>> MonSock
>> Deleting UDP socket 0x91263f0
>> 2010/04/15 12:12:18.674      0:07.780                              
>> PWLib    File
>> handle low water mark set: 33 PUDPSocket
>> 2010/04/15 12:12:18.675      0:07.780                              
>> MonSock
>> Created socket bundle for all interfaces.
>> 2010/04/15 12:12:19.000      0:08.105     Housekeeper:0xb70ffb70   
>> SIP    SUBSCRIBE
>> transaction id=z9hG4bKeec3966a-ed46-df11-8ae4-00095bc6fb02 timeout,
>> making retry 3, timeout 4.000
>> 2010/04/15 12:12:19.000      0:08.105     Housekeeper:0xb70ffb70   
>> SIP    Attempt
>> to write PDU to closed transport
>> udp$86.64.162.35:5060<if=udp$192.168.10.182:5060>
>>
>> and again:
>>
>> 2010/04/15 12:12:21.077      0:10.183                              
>> STUN    STUN
>> server 75.101.138.128:3478 unexpectedly went offline.
>>
>> Both of them are strange, I have not seen them before.  I cannot help,
>> sorry.  If nobody answers in a few days, please report the bug to
>> bugzilla by attaching these two outputs.
>>
>>    
> I've installed wireshark and have a capture file - it's 30K-ish - is it
> any use? Can I send it to you off-list?

Yes please, but chances that I discover the problem are small...

-- 
Eugen


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