From hw@skalatan.de Sun Oct 17 13:21:02 2021 From: Henning Westerholt To: sr-users@lists.kamailio.org Subject: Re: [SR-Users] Kamailio on AWS Kubernetes with NLB Date: Sun, 17 Oct 2021 11:20:57 +0000 Message-ID: In-Reply-To: =?utf-8?q?=3CVE1PR10MB3872417BFC8B134D0E1D3461E2B99=40VE1PR10MB?= =?utf-8?q?3872=2EEURPRD10=2EPROD=2EOUTLOOK=2ECOM=3E?= MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2016338679==" --===============2016338679== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, I would try to connect to the kamailio container and increase debug level to = see what is happening on a lower level. You can also use tools like ngrep/sng= rep to see if the SIP request is routed to the instance. Cheers, Henning -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com From: sr-users On Behalf Of Cedric Th= iebault Sent: Friday, October 15, 2021 3:37 PM To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Kamailio on AWS Kubernetes with NLB Adding a log in kamailio.cfg in request_route method: xlog("L_INFO", "INFO - request_route - $rm ($fu ($si:$sp) to $tu, $ci)\n"); Using docker-compose I get: 24(30) INFO: {1 1 REGISTER Hotel7dIcm7DCPtmR3jACw..}