Re: [Turnserver-users] Allocate Requests are timed out in TCP mode

[John N. <joh...@gm...>]

One more information I would like to add is...My turn client is sending
turn relay data to Server TCP port 5743 (Which is the Turn TCP listen port)
But should my client not send relay data (RTP) to the port which I got from
Allocation Success Response??..I am doing something very wrong?

tcp_port = 5743

Regards,



John


On Fri, Nov 16, 2012 at 11:18 PM, John Nash <joh...@gm...> wrote:

> Hello,
>
> I am using turnserver ver 0.7 in TCP mode. SIP Clients are communicating
> with turnserver over TCP for all STUN and TURN Relay messages while
> communication with peer is being done over UDP.
>
> It works fine till approximately 40-50 active turn relays (Active calls)
> but after that we start getting "timeout" for "Allocate Requests" and again
> we start getting responses after approx 10 min of idle time. On turn server
> log i do not see any unusual message like error or something related to any
> issue.
>
> My ulimit is set as 999999 and i compiled with ./configure
> --enable-fdsetsize=999999 option. I am using a single user for all my Turn
> clients . I have following options set in the config file
> ## Max relay per username.
> max_relay_per_username = 9950000
>
> ## Allocation lifetime.
> allocation_lifetime = 1800
>
> ## Allocation bandwidth limitation (in KBytes/s).
> ## 0 value means bandwidth quota disabled.
> bandwidth_per_allocation = 1024
>
> ## Restricted user bandwidth (in KBytes/s).
> ## 0 value means bandwidth limitation disabled.
> restricted_bandwidth = 1024
>
>
> Apart from that everything is default. What might case this strange issue?
>
> Regards
>
> John
>