I always expected it did :)
My point was that you cannot put transport=TCP on a bridge statement
line to an internal registered client and expect it to use a protocol
that was not used at registration.
Hence the clarification based on the context of the thread :)
On Mon, Aug 24, 2009 at 2:53 PM,
It already does exactly this.
/b
On Aug 23, 2009, at 11:49 PM, Jim Burke wrote:
> For terminating calls to registered User Agents (UA) the decision to
> use TCP or UDP should be made using information collected when the UA
> registered. i.e if the UA registers using TCP, FS should use TCP to
>
"Well if you append ;transport=tcp on the bridge lines it will use TCP"
IMHO this statement needs some clarification based on the context of
this thread.
If the destination is another PBX or Freeswitch box then this is ok as
FS will be initiating the TCP connection.
For terminating calls to regi
X-Lite does support TCP, however you need to have NAPTR and SRV DNS
entries. It used to support TLS, but this seems to have been removed
:(
sip.mydomain.net. IN NAPTR 0 0 "s" "SIPS+D2T" "" _sips._tcp.sip.mydomain.net.
sip.mydomain.net. IN NAPTR 1 0 "s" "SIP+D2T" "" _sip._tcp.sip.mydomain.net.
s
Well if you append ;transport=tcp on the bridge lines it will use TCP .
/b
On Aug 17, 2009, at 9:06 AM, Tzury Bar Yochay wrote:
>> FreeSWITCH works very well as a client :P
> I am currently porting it into iPhone and Symbian, I am almost
> done ;-)
>
> anyway, seriously now, can one point to a
> FreeSWITCH works very well as a client :P
I am currently porting it into iPhone and Symbian, I am almost done ;-)
anyway, seriously now, can one point to a wiki page about this?
How do I do that?
I would need 3 server instances to place a call, right?
___
FreeSWITCH works very well as a client :P
/b
On Aug 17, 2009, at 8:53 AM, Tzury Bar Yochay wrote:
> my conclusion is then:
> we are living in a sad world where there is no a production ready,
> cross platform, fully compliant, decent and open source sip client
_
> They make you pay for TCP which is weird since the RFC says TCP is
> required.
>
> /b
my conclusion is then:
we are living in a sad world where there is no a production ready,
cross platform, fully compliant, decent and open source sip client
___
Free
They make you pay for TCP which is weird since the RFC says TCP is
required.
/b
On Aug 17, 2009, at 7:18 AM, bakko wrote:
> Y make my tests with eyebeam.
>
> I thing X-lite dont't support TCP transport.
>
> BR
___
FreeSWITCH-users mailing list
Free
Y make my tests with eyebeam.
I thing X-lite dont't support TCP transport.
BR
___
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/
Tzury Bar Yochay wrote:
> I think I confused you with this TLS/TCP thing.
> For the sake of clarification, I am talking about TCP and _not_ about TLS.
> That is simply transporting the signaling packets over TCP instead of UDP.
> No TLS should be involved at this stage. It is simply communicatio
> I'm not sure whether that's supposed to use TLS. I suspect not.
Jason,
I think I confused you with this TLS/TCP thing.
For the sake of clarification, I am talking about TCP and _not_ about TLS.
That is simply transporting the signaling packets over TCP instead of UDP.
No TLS should be involved
Tzury Bar Yochay wrote:
> Well, as I said at the beginning of this thread, TLS works fine for me.
> The problem is when using TCP (transport=tcp and not transport=tls)
I'm not sure whether that's supposed to use TLS. I suspect not.
___
FreeSWITCH-us
> I've successfully used TLS with FreeSWITCH at both ends (yes, that's with
> FreeSWITCH itself as the softphone).
Well, as I said at the beginning of this thread, TLS works fine for me.
The problem is when using TCP (transport=tcp and not transport=tls)
__
Tzury Bar Yochay wrote:
> Brian/Bakko,
>
> Would you please tell me which softphone are you using?
> As you know, my own one is not working and when I tried tcp with xlite
> (providing transport=tls) I see in wireshark that it is still
> transporting it over udp(!)
I've successfully used TLS wit
Brian/Bakko,
Would you please tell me which softphone are you using?
As you know, my own one is not working and when I tried tcp with xlite
(providing transport=tls) I see in wireshark that it is still
transporting it over udp(!)
thanks allot in advance,
Tzury
On Sun, Aug 16, 2009 at 5:11 PM, Br
Works fine here.
/b
On Aug 16, 2009, at 6:25 AM, Tzury Bar Yochay wrote:
> Hi Brian,
>
> Just for your information here is a mail I got from a colleague of
> mine which I consider as an experienced freeswitch integrator
>
>> "... TCP used to work, and I had about 20-30 client phones
>> connect
I'm just tryng TCP now and work (latest trunk)
I done this test with eyebeam phone registeres to TCP port and call other ip
phone (registered over UDB port).
The audio work fine in both directions.
My configuration:
FS --> internet --> NAT --> Phones
In the internal profile:
Call-ID:
Hi Brian,
Just for your information here is a mail I got from a colleague of
mine which I consider as an experienced freeswitch integrator
> "... TCP used to work, and I had about 20-30 client phones connecting with it.
> About 3 months ago I did an upgrade and TCP no longer worked. I was in pan
On Aug 13, 2009, at 9:37 AM, Tzury Bar Yochay wrote:
>> I need to see the sip packet.
> dumped below
>
>> TCP should be uppercase I'm pretty sure.
> you mean the via should be Via: SIP/2.0/TCP right?
>
Yep
> If so, then that would a bug in the client then.
Some things might accept it but sofia
> I need to see the sip packet.
dumped below
> TCP should be uppercase I'm pretty sure.
you mean the via should be Via: SIP/2.0/TCP right?
If so, then that would a bug in the client then.
#wireshark dumps:
000 00 21 29 66 15 9f 00 23 ae 64 af a6 08 00 45 00 .!)f...# .dE.
0010 02 3e 80 c
I need to see the sip packet. TCP should be uppercase I'm pretty sure.
/b
On Aug 13, 2009, at 9:04 AM, Tzury Bar Yochay wrote:
> nta: Via check: invalid transport "SIP/2.0/tcp" from
> 80.74.97.189:42634
> nta: REGISTER (30669) has invalid Via
___
> It just works... to force TCP you append ;transport=tcp
Hi Brian
In fact this is exactly what I did and I could not get it work.
I am using a console based application supplied by pjsip.org and when
trying to register i get some error messages saying 'invalid transport
"SIP/2.0/tcp"' and 'REGIST
It just works... to force TCP you append ;transport=tcp
In reality you should be using SRV records.
/b
On Aug 13, 2009, at 3:40 AM, Tzury Bar Yochay wrote:
> Hi,
>
> Googeling about this shows that FS aims to support this (in fact it
> supports all 3: UDP/TCP/TLS).
> Yet I could not find the
Hi,
Googeling about this shows that FS aims to support this (in fact it supports
all 3: UDP/TCP/TLS).
Yet I could not find the way to configure FS in order to support that.
In fact, it does not work in my current install.
I have TLS configured and work, but could not make TCP works
thanks in adva
25 matches
Mail list logo
