+1 for this feature request. I ran into this bottleneck, as discussed on this thread: https://lists.kamailio.org/pipermail/sr-users/2018-February/100447.html As a workaround, I've opted for the async process technique, but it's not perfect, because some operations don't execute properly on the async route. Specifically, I've discovered that set_dlg_profile() does not seem to work on the async route. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1107#issuecomment-368165209

When K connects to another SIP proxy over TCP or TLS, the connection is shared for all requests to that destination. If the receiving SIP proxy is K, it means that only one worker process is handling all those requests. This may become a bottleneck if processing of requests is time consuming, e.g., because of DB operations.

It should therefore be possible one way or another to establish more than one parallel TCP or TLS connections to the same destination. One solution could be based on a function call, such as t_forward_connect(number), to be called before t_relay specifying the desired number of parallel connections shared randomly by outgoing requests.

As simple workaround you could map multiple alias / IP addresses to a single NIC? And feed the dispatcher module with the multiple alias. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1107#issuecomment-587034011

Closed #1107 as not planned. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/1107#event-11042724985 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issue/1107/issue_event/11042724985@github.com>