On non-critical invite transaction

hello sir
I have a problem
I just installed a new asterisk, I have 2 trunks,
You don’t have any client configured
and has this problem coming up.

I can’t find how to solve
or because that waring comes out

[2022-09-07 19:07:04] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on ffjL1GsrC6ztuqKej9FTTy… on non-critical invite transaction.
[2022-09-07 19:07:08] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on 8GD31uIbQuMkzMsuaupf0a… on non-critical invite transaction.
[2022-09-07 19:07:12] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on rFkXofkfA3HRG23ttYCmzD… on non-critical invite transaction.
[2022-09-07 19:07:17] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on a62qifEpgv2zatU5mh9GOf… on non-critical invite transaction.
[2022-09-07 19:07:21] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on qIzzKVzXqQt434egS1aiZs… on non-critical invite transaction.
[2022-09-07 19:07:25] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on 0Kf3UBuxyjA9akTHa0tS8c… on non-critical invite transaction.
[2022-09-07 19:07:29] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on 1Q1qCtcBBFANQqJXCxVB2F… on non-critical invite transaction.
[2022-09-07 19:07:34] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on RQlezpEZxyTRPWGqSKBT5z… on non-critical invite transaction.
[2022-09-07 19:07:38] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on Mda3vJ6oEOcjNJboqsW1ZJ… on non-critical invite transaction.
[2022-09-07 19:07:42] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on qoA8XEZf7LnHxUTb6cx9F3… on non-critical invite transaction.
[2022-09-07 19:07:46] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on qHAOTIpgrqMml2JIpLB4jZ… on non-critical invite transaction.
[2022-09-07 19:07:50] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on t6M2NgBDJThEn3ZKGVXsjm… on non-critical invite transaction.
[2022-09-07 19:07:55] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on 1s0yEijphdlMIvrXEpR5d1… on non-critical invite transaction.
[2022-09-07 19:07:59] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on 5V423pzuVv9op8hYTPoWSg… on non-critical invite transaction.
[2022-09-07 19:08:03] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on 3Id108JQdJbFods1YIHQFD… on non-critical invite transaction.
[2022-09-07 19:08:07] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on IKi2m7SvyKhcIfuL5AzeR9… on non-critical invite transaction.
[2022-09-07 19:08:12] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on wCOqn8aW60L83dC5hztrs3… on non-critical invite transaction.
[2022-09-07 19:08:16] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on yTauYkIFBGOuggTSQNrpdx… on non-critical invite transaction.
[2022-09-07 19:08:20] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on cOPRvynmxTGtoov0SIYFJG… on non-critical invite transaction.
[2022-09-07 19:08:24] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on bwxTXlWtJciFs1EC7Xm4Wy… on non-critical invite transaction.
[2022-09-07 19:08:28] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on VfK47e9j32L6swDJb3I0Sv… on non-critical invite transaction.
[2022-09-07 19:08:32] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on B02VMQVW52RfvC5TGAMftl… on non-critical invite transaction.
[2022-09-07 19:08:36] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on se8neMrlR9yTGiicF2njid… on non-critical invite transaction.
[2022-09-07 19:08:40] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on y1biKTcGtMZOzD72JDZMkq… on non-critical invite transaction.
[2022-09-07 19:08:45] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on bw82x5MwbdAk0zXytxVnrg… on non-critical invite transaction.
[2022-09-07 19:08:49] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on LczZAbV5QpUFADb6DNBXga… on non-critical invite transaction.
[2022-09-07 19:08:53] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on 57P84MkWeOG9wnkXav4bFt… on non-critical invite transaction.
[2022-09-07 19:08:57] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on Znpc1k0Rnr0iL1Hu6nsGSy… on non-critical invite transaction.
[2022-09-07 19:09:02] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on rUITZ9m1Nsgo8Bvam9U5EL… on non-critical invite transaction.
[2022-09-07 19:09:06] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on tTrrepSQ4Mg3Qm1vxbH6bV… on non-critical invite transaction.
[2022-09-07 19:09:10] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on AOZKvTpglsoE3k8KYZlSIz… on non-critical invite transaction.
[2022-09-07 19:09:14] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on mpE6riXKAOdPon6jVFVkAg… on non-critical invite transaction.
[2022-09-07 19:09:19] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on hYmuZbmqYrY82hX34VS96v… on non-critical invite transaction.
[2022-09-07 19:09:23] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on DYo8rcKDd80SeJ1glmJWpj… on non-critical invite transaction.
[2022-09-07 19:09:27] WARNING[1646]: chan_sip.c:4210 retrans_pkt: Timeout on hcikGLzec867R1o7ZXMSc2… on non-critical invite transaction.

You are using a channel driver that is effectively no longer supported, and will be completely removed in next year’s release. You should move to chan_pjsip, unless you have a very specific reason not to.

This warning is either because of a broken peer, that is failing to even reject an unwanted request, or because of a connectivity problem, typically because of NAT misconfiguration or dynamic NAT or firewall rules timing out. From that point of view you need to tell us your networking environment, and the general and peer sections (you may have friend, although that is normally bad practice) settings. Also the output from “sip set debug on” will help understand why the INVITE was being sent.

This wont be a re-INVITE, as that is critical. I guess that connected line update is non-critical. Turning of sendrpid will stop those. I’m not sure if session timer updates are critical.

Also, when posting logs anc configurations, please mark them up as pre-formatted text, using </>.

Regarding your posting on the zombie thread, tcpdump is a diagnostic tool.

fal2ban automatically adds firewall rules, and I suspect what was meant in the old thread was that the added firewall rules outside of the fail2ban system. In any case, you haven’t said anything to suggest that this is in relation to an unauthorised call, and adding firewall rules will prevent all calls from the peer that is responsible for this warning.

If firewalling is a solution, you have more serious problems, as a hostile call should not be able to get this far.

tcpdump captures outside the firewall, so doesn’t reflect what Asterisk is seeing.

Also, in my experience, people who say they have the same problem rarely do.