Hi Daniel, Oh I missed the reply for some reason. Thank you very much for both replying and reminding :) We do want to receive the replies so closing the connection isn't an option. Listening on multiple tcp ports sound like a good temporary solution, but lack of scalability? Regards, Allen From: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Sent: Thursday, 11 July 2013 9:58 p.m. To: Kamailio (SER) - Users Mailing List; Allen Zhang Subject: Re: [SR-Users] how to make dispatcher module use more than one tcp connections to the destinations? Hello, have you seen the reply: http://lists.sip-router.org/pipermail/sr-users/2013-July/078830.html ? Cheers, Daniel On 7/10/13 11:04 PM, Allen Zhang wrote: Hi list, I have a loadbalancer before sipproxies. I call t_reley() on the dispatcher to forward requests to destinations. All goes well under low load. But when load goes up to 500 requests/s, the loadbalancer still sends requests via only one tcp connection. This maxes out the tcp write queue. Of course I can increase the 'tcp_conn_wq_max' value but it doesn't solve the root problem. How do I make the loadbalancer start a new tcp connection to the destination when existing one becomes too busy? (Is it possible?) Regards, Allen _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda