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

[Sebastien V. <se...@ji...>]

Hi John,

Sorry for delay.

So if you have 40 to 50 active relays it means you have 80 to 100 opened 
sockets (UDP and TCP) and, I think, there is a lot of traffic, right ?. 
Can you see if CPU usage of turnserver process is "normal" and check 
also your bandwidth of your network cards. BTW On which machine/hardware 
do you run turnserver ?

It could also be that the socket event loop has problem to scale. I 
quickly check and I see we can optimize it:
- a little bit with tuning select() loop (I can see this maybe this 
week-end);
- provides a socket event loop abstraction which uses the best API to 
use (epoll for Linux, kqueue for *BSD, select() for others, ...) either 
by coding it directly or uses libevent (it requires more work and I 
don't know if I will have the time in the following months).

Regards,
--
Seb

Le 21/11/2012 13:19, John Nash a écrit :
>
> 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?
>
> 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??..am doing 
> something very wrong?
>
> tcp_port = 5743
>
> Regards
>
> John
>
>
>
> ------------------------------------------------------------------------------
> Monitor your physical, virtual and cloud infrastructure from a single
> web console. Get in-depth insight into apps, servers, databases, vmware,
> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
> Pricing starts from $795 for 25 servers or applications!
> http://p.sf.net/sfu/zoho_dev2dev_nov
>
>
> _______________________________________________
> Turnserver-devel mailing list
> Tur...@li...
> https://lists.sourceforge.net/lists/listinfo/turnserver-devel