Ok I did make it work.
It was not working because, on my Qteclient, I put 127.0.0.1 as server ...
and SIP protocol seems to analyze the requested server.
So I told Qteclient to use freephonie.net as server, and I tweaked my local
host file to resolve freephonie.net as 127.0.0.1
Now it seems to work, I was able to send a call.
But what I see, is that delegate seems to hang after some time. Sent
packets are not seen anymore on the delegate console (using the -v switch).
It does not event reconize CTRL+C command anymore. I'll give a feedback if
I see anything new.
----- Original Message -----
From: "ZaMotH" <firstname.lastname@example.org>
Sent: Thursday, September 23, 2010 2:00 PM
Subject: [DeleGate-En] Re: UDP over TCP (Re: SIP proxy possibilities and MSN
>I did try what you told me to, but it does not work. The UDP relay, does
>not transform packets to TCP one (wireshark is only showing udp packet
> So I tried something else :
> On the actual computer I put :
> dg9_9_7.exe SERVER=sockmux -P127.0.0.1:6543 DEST=[SSH relay]:5060/udp RES
> and on the distant computer, running the end of the ssh tunnel I run
> dg9_9_7.exe SERVER=sockmux -P127.0.0.1:6543 DEST=188.8.131.52:5060/udp
> This is what I tried to do :
> Qutecom SIP/UDP<= udp/5060 => Delegate sockmux <= tcp/6543 => SSH tunnel
> <= tcp/6543 => Delegate sockmux <= udp/5060 => SIP server
> With this configuration I do see outgoing frames over the end server to
> the SIP server ... and it is using SIP protocol over udp.
> But now I get a sip error ...
> 8060 746.785539 192.168.1.4 184.108.40.206 SIP Request: REGISTER
> 8062 746.818609 220.127.116.11 192.168.1.4 SIP Status: 100 Trying (0
> 8063 746.819085 18.104.22.168 192.168.1.4 SIP Status: 404 Domain not bound
> (0 bindings)
> This is more like a SIP configuration problem ... I'll check out more over
> that, and bring information if I get something.
> ----- Original Message -----
> From: "Yutaka Sato" <email@example.com>
> Newsgroups: mail-lists.delegate-en
> Cc: <firstname.lastname@example.org>
> Sent: Tuesday, September 14, 2010 6:50 AM
> Subject: [DeleGate-En] UDP over TCP (Re: SIP proxy possibilities and MSN
>> In message <_A4902@delegate-en.ML_> on 09/13/10(22:58:14)
>> you "ZaMotH" <email@example.com> wrote:
>> |First, i'd like to know if Delegat is able to handle a sort of SIP
>> |Usually I use SSH to tunnel my datas, but SSH seems no to handle UDP
>> |This is what I would like to set :
>> |Local SIP Client (QteCOM) --- UDP --- Delegate UDP to TCP --- SSH
>> |Tunnel/TCP --- Delegate TCP to UDP --- SIP server
>> |Is it possible ?
>> DeleGate does not support SIP (yet).
>> Thre are several ways to convey UDP over TCP using a pair of DeleGate.
>> The simplest one is using a pair of DeleGates for UDPrelay.
>> hostA$ delegated -P2000 SERVER=udprelay://hostB:3000.tcp
>> hostB$ delegated -P3000.tcp SERVER=udprelay://hostC:4000
>> With this configuration, UDP port at hostA:2000 will be forwarded
>> to hostC:4000, via TCP port at hostB:3000, as follows:
>> --(UDP)-- hostA:2000 --(TCP)-- hostB:3000 --(UDP)-- hostC:4000
>> 9 9 Yutaka Sato, CSDP#005482 <firstname.lastname@example.org>
>> ( ~ ) National Institute of Advanced Industrial Science and Technology
>> _< >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
>> Do the more with the less -- B. Fuller