Project

General

Profile

Actions
Copy link

Defect #2401

closed

SIP retransmissions - packet timeout

Added by R Mont almost 11 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
02/02/2014
Due date:
% Done:

0%

Estimated time:
Keywords:

Description

Hi

I have this error since I set up IPtables for the first time.
The call comes in, is being answered and then is hanged up by the server.

[2014-02-02 20:37:27] WARNING6900: chan_sip.c:4174 retrans_pkt: Retransmission timeout reached on transmission 73b4bd613dec2e597d5dfb9159a95646@176.9.39.206 for seqno 102 (Critical Response) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
Packet timed out after 6401ms with no response
[2014-02-02 20:37:27] WARNING6900: chan_sip.c:4203 retrans_pkt: Hanging up call 73b4bd613dec2e597d5dfb9159a95646@176.9.39.206 - no reply to our critical packet (see https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions).

Within IPtables I opened the following IP addresses
81.23.228.140 ACCEPT udp -- 81.23.228.140 0.0.0.0/0 udp dpts:5060:5069
81.23.228.129 ACCEPT udp -- 81.23.228.129 0.0.0.0/0 multiport dports 5060,5061,5062,5063,5064,5065,5066,5067,5068,5069
81.23.228.150 ACCEPT udp -- 81.23.228.150 0.0.0.0/0 multiport dports 5060,5061,5062,5063,5064,5065,5066,5067,5068,5069
85.17.186.7 ACCEPT udp -- 85.17.186.7 0.0.0.0/0 multiport dports 5060,5061,5062,5063,5064,5065,5066,5067,5068,5069

I am not very experienced at reading the SIP trace, but it seems an ACK is missing.
SIP session node 11 20:41:05

Should I add 176.9.39.206 to allow in my IPtables?
What else can be / did I do wrong?

thanks

Actions
Copy link

Also available in: Atom PDF