Re: [Ekiga-devel-list] STUN usage with SIP

2015-07-15 Thread Eugen Dedu
On 01/07/15 22:32, schwa...@web.de wrote: Am 01.07.2015 um 11:43 schrieb Eugen Dedu: On 06/06/15 15:04, schwa...@web.de wrote: Hi, Sorry Scwatzi to answer so late, we are too busy. How does STUN work in ekiga? STUN is normaly used as followed: The STUN client should use the same socket

Re: [Ekiga-devel-list] STUN usage with SIP

2015-07-01 Thread Eugen Dedu
On 06/06/15 15:04, schwa...@web.de wrote: Hi, Sorry Scwatzi to answer so late, we are too busy. How does STUN work in ekiga? STUN is normaly used as followed: The STUN client should use the same socket as SIP and the received IP and Port should then be used for constructing Contact- , Via-

Re: [Ekiga-devel-list] STUN usage with SIP

2015-07-01 Thread schwatzi
Am 01.07.2015 um 11:43 schrieb Eugen Dedu: On 06/06/15 15:04, schwa...@web.de wrote: Hi, Sorry Scwatzi to answer so late, we are too busy. How does STUN work in ekiga? STUN is normaly used as followed: The STUN client should use the same socket as SIP and the received IP and Port should

[Ekiga-devel-list] STUN usage with SIP

2015-06-06 Thread schwatzi
Hi, How does STUN work in ekiga? STUN is normaly used as followed: The STUN client should use the same socket as SIP and the received IP and Port should then be used for constructing Contact- , Via- field and SDP. Then a keepalive is needed to keep the NAT Session in the router alive ( to