Hello,
there is no tight relation between sip traffic and transport
connections, meaning that you can can enforce any target address when
sending requests within dialog via config operation.
By default kamailio.cfg processing, the connection is matched based on
Route or R-URI addresses. But you can set the target address in $du to
point to port 5060 and then relay.
On 08.06.22 12:41, Vitalii Krutsitskyi wrote:
Hello
General overview of the infrastructure:
Client (Cisco Hardware) ---> AWS NLB ---> Kamailio Instances
The client has a time limit for the opened TCP connections - 10
minutes. This is a hardcoded value that can't not be changed.
Regardless of the traffic that flows through the connection, it is
closed after 10 minutes.
Problem: in case of long-running calls above 10 minutes it is not
possible for Kamailio to send back SIP traffic back to the client
using the original TCP connection. The client has been asked to either
increase the time limit or send SIP reinvites - none of that is
possible due to some client's infrastructure limitations.
Question: is it possible to force Kamailio to open a new TCP
connection and associate it with the call? Client has a 5060 port
always opened which can accept incoming connections.
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
*
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla --
www.asipto.com
www.twitter.com/miconda --
www.linkedin.com/in/miconda
Kamailio Advanced Training - Online: June 20-23, 2022
*
https://www.asipto.com/sw/kamailio-advanced-training-online/