VoIP Mailing List Archives

[asannucci at gmail.com]

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/mailman/options/freeswitch-users
http://www.freeswitch.org

[brian at freeswitch.org]

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:

[tzury.by at reguluslab...]

[brian at freeswitch.org]

FreeSWITCH works very well as a client

/b

On Aug 17, 2009, at 8:53 AM, Tzury Bar Yochay wrote:

[tzury.by at reguluslab...]

[brian at freeswitch.org]

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:

[jim at evolutiontel.net]

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.
sip.mydomain.net. IN NAPTR 2 0 "s" "SIP+D2U" "" _sip._udp.sip.mydomain.net.


_sip._udp.sip.mydomain.net. 43200 IN SRV 1 10 5060 sip.mydomain.net.
_sip._tcp.sip.mydomain.net. 43200 IN SRV 1 10 5060 sip.mydomain.net.
_sips._tcp.sip.mydomain.net. 43200 IN SRV 1 10 5061 sip.mydomain.net.


On Mon, Aug 17, 2009 at 10:18 PM, bakko<asannucci@gmail.com> wrote:

[jim at evolutiontel.net]

"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 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
send and receive messages, if the UA registers with TLS, then FS
should use TLS, same story for UDP.

On Tue, Aug 18, 2009 at 12:10 AM, Brian West<brian@freeswitch.org> wrote:

[brian at freeswitch.org]

It already does exactly this.

/b

On Aug 23, 2009, at 11:49 PM, Jim Burke wrote:

[jim at evolutiontel.net]

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, Brian West<brian@freeswitch.org> wrote: