- October 24, 2019 at 4:13 am
About this message: “chan_sip.c: Timeout on 356135904-147483397-409121765 on non-critical invite transaction.”
This may happen for the following reasons:
- A NAT device in the signaling path. A misconfigured NAT device is in the signaling path and stops SIP messages.
- A firewall that blocks messages or reroutes them wrongly in an attempt to assist in a too clever way.
- A SIP middlebox (SBC) that rewrites contact: headers so that we can’t reach the other side with our reply or the ACK.
- A badly configured SIP proxy that forgets to add record-route headers to make sure that signaling works.
- Packet loss. IP and UDP are unreliable transports. If you lose too many packets the retransmits don’t help and communication is impossible. If this happens with signaling, media would be unusable anyway.
- Some routers are configured by default with the “SIP ALG” option. In some cases, this option should be off because the implementation is incomplete.
- Unauthorized invites. Also, you may get this message when SIP scanners try to vulnerate your server.