11 May
2020
11 May
'20
8:23 p.m.
Hello,
so it looks like kamailio used random port for opening connections to our partners but did
not updates record-route port properly. AWS has symmetric NAT and that works fine.
Is there any way how to identify port and rewrite record-route?
Thanks.
Bye,
Michal
On 7 May 2020, at 17:25, Michal Popovic
<michal.popovic(a)cloudtalk.io> wrote:
Hello,
our kamailio used for sip trunk interconnections is behind NAT and our cloud provider
opens random outgoing ports for outbound connections.
Our record-route is set to our external address and port 5060, that is probably
incorrect, but we did not had any issues.
One of our partners suddenly begin sending BYEs to the port advertised in record-route
instead of port from where he received call.
What is a correct approach here if we are not able to determine open port behind NAT?
Bye,
Michal
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users