STUN changes in pjsip 1.4

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

 




Alain Totouom schrieb:
> Klaus Darilion wrote:
>> Hi Alain!
>>
>> Attached is the log output and the pcap file.
> 
> If you check the ICMP packets #20, #29 and #31 you'll see that there
> IS another problem at the network layer (ALG, Firewall ?!?) which
> has nothing to do with the patch as i stated before.
> 
> For example if you analyze the ICMP packet #20 and follow the
> corresponding STUN messages through their Transaction ID you get the
> corresponding STUN messages #7,#8,#13,#19 and #20.
> 
> #7,#8 	
> 88.198.53.118:57596 is used to send the Binding Request
> 
> #13,#19	
> the server sends the successful Binding Response to 88.198.53.118:57596
> 
> But for one reason or and another that port is NOT reachable #20,
> thus those responses (#13,#19) never get to the application !!!
 >
> Anyway, there is a discrepancy between the result of the successful
> NAT discovery test and those ICMP (Destination Unreachable) messages.
> 
> Did download the trunk and did apply the patch and still can't
> reproduce that situation.


I applied the patch to 1.4.

There was no firewall or ALG active - I suspect a bug in pjsip that it 
closed the port before getting the resonse -> thus ICMP error.

guess I have to use strace to verify....

regards
Klaus



[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