Ersek, Laszlo wrote:
> in March 2009, Tarrisse Laurent posted an experimental patch to
> qutecom-dev that enables STUN for SIP accounts [0]. Is there any intent to
> merge this patch?
Until the STUN patch is back you could use a SIP proxy (e.g. a linux
box running 'siproxd') to achieve the same
El Lunes, 22 de Junio de 2009, Jan Kiszka escribió:
> Iñaki Baz Castillo wrote:
> > - First, STUN must be performed at startup in order to get the mapped
> > public IP and port for SIP signalling (local port 5060).
> > - For each call, STUN must be performed in order to get the mapped IP and
> > p
Iñaki Baz Castillo wrote:
> El Lunes, 22 de Junio de 2009, Jan Kiszka escribió:
>> Hi Laurent,
>>
>> Laurent Tarrisse wrote:
>>> Hello Jan,
>>>
>>> It doesn't work : Wengophone used stun just for detect nat type and
>>> owplConfigSetNat function was removed from phapi (don't know why).
>>> You're r
El Lunes, 22 de Junio de 2009, Jan Kiszka escribió:
> Hi Laurent,
>
> Laurent Tarrisse wrote:
> > Hello Jan,
> >
> > It doesn't work : Wengophone used stun just for detect nat type and
> > owplConfigSetNat function was removed from phapi (don't know why).
> > You're right, there is an huge job to
Hi Laurent,
Laurent Tarrisse wrote:
> Hello Jan,
>
> It doesn't work : Wengophone used stun just for detect nat type and
> owplConfigSetNat function was removed from phapi (don't know why).
> You're right, there is an huge job to do.
H. What does "huge" mean? And why? I have no real clue a
Hello Jan,
It doesn't work : Wengophone used stun just for detect nat type and
owplConfigSetNat function was removed from phapi (don't know why).
You're right, there is an huge job to do.
Laurent
Jan Kiszka a écrit :
> Tarrisse Laurent wrote:
>
>> If you use sipaccount, this an experimental
Tarrisse Laurent wrote:
> If you use sipaccount, this an experimental patch to allow stun ;-)
>
I just tried your patch on top of tip: stun.ekiga.net apparently returns
my dial-in IP address, but qutecom continues to issue the SIP request
with my private IP. Should this already work, or are there
Hi Laurent,
I'm using a SIP account. Thanks a lot for the patch, I'll give it a
try tomorrow and let you know.
Mathieu
On Wed, Mar 25, 2009 at 10:32 PM, Tarrisse Laurent wrote:
> Hi Mathieu
>
> What type of account do you use ?
>
> Stun support is implemented with wengo account type not sip ac
Thanks for your help Vadim.
I'll give a try to mediaproxy first even if the RTP proxying is not
what I'm looking for. I'd prefer to save bandwidth and let the clients
talk P2P.
Mathieu
On Wed, Mar 25, 2009 at 10:28 PM, Vadim Lebedev wrote:
> Hi Mathieu,
>
> The stun support is somewhat bastardi
Mathieu,
You seems to be off the mailing list,
please subscribe, and you'll see that Laurent posted a patch to
activate STUN on non wengo accounts
Thanks
Vadim
Le 26 mars 09 à 16:28, Mathieu Osty a écrit :
> Thanks for your help Vadim.
> I'll give a try to mediaproxy first even if the RTP pro
If you use sipaccount, this an experimental patch to allow stun ;-)
Laurent
Tarrisse Laurent a écrit :
Hi Mathieu
What type of account do you use ?
Stun support is implemented with wengo account type not sip account.
Laurent
Mathieu Osty a écrit :
Hi everybody,
I'm currently trying to
Hi Mathieu
What type of account do you use ?
Stun support is implemented with wengo account type not sip account.
Laurent
Mathieu Osty a écrit :
> Hi everybody,
>
> I'm currently trying to setup an architecture based on a private
> Kamailio server and Qutecom 2.2 RC3 clients (Windows and MacOS
Hi Mathieu,
The stun support is somewhat bastardized since wengo relied on http
tunnelling to resolve NAT related problems.
I can suggest you to try to use mediaproxy with kamaillio or
http://www.mbdsys.com/opensource/htproxy/
Thanks
Vadim
Le 25 mars 09 à 18:57, Mathieu Osty a écrit :
13 matches
Mail list logo
