Summary:	ASTERISK-24765: retrans_pkt: Retransmission timeout reached / Hanging up calls
Reporter:	Ingenierie (ingenierie)	Labels:
Date Opened:	2015-02-06 09:54:14.000-0600	Date Closed:	2015-02-16 12:08:22.000-0600
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Channels/chan_sip/General
Versions:	13.1.0	Frequency of Occurrence	Frequent
Related Issues:
Environment:	CentOS release 5.9 Kernel 2.6.18-348.2.1 x86_64	Attachments:
Description:	Hello all, Recently, we upgrade to version Asterisk 13.1.0 with chan_sip stack. With 20 calls there was no problem. But now this server handles 150 concurrent calls and I get the following error : Retransmission timeout reached on transmission {noformat} 2015-02-06 00:34:08.410                Warn        local0        asterisk[28435]: WARNING[28461]: chan_sip.c:4047 in retrans_pkt: Retransmission timeout reached on transmission 05072-OA-01425d07-678a8d304@telec ... 2015-02-06 00:34:08.400                Warn        local0        asterisk[28435]: WARNING[28461]: chan_sip.c:4076 in retrans_pkt: Hanging up call 29868-NY-01425d00-3cdf68ba3@domain.com - no reply to our critic ... 2015-02-06 00:34:08.380                Warn        local0        asterisk[28435]: WARNING[28461]: chan_sip.c:4047 in retrans_pkt: Retransmission timeout reached on transmission 29868-NY-01425d00-3cdf68ba3@telec ... 2015-02-06 00:33:55.586                Warn        local0        asterisk[28435]: WARNING[28461]: chan_sip.c:4076 in retrans_pkt: Hanging up call 29634-DL-01425cda-6a801a7d6@domain.com - no reply to our critic ... 2015-02-06 00:33:55.585                Warn        local0        asterisk[28435]: WARNING[28461]: chan_sip.c:4047 in retrans_pkt: Retransmission timeout reached on transmission 29634-DL-01425cda-6a801a7d6@telec {noformat} The problem occurs about 1 time a day. When this message appears the server begins to reject calls. They are all gradually declined. We are forced to restart the daemon to make the service works again. Have you ever encountered the same issue? We are unable to reproduce the problem. I specified that we don't use SIP SBC or NAT in this scenario. Regards, Ludovic BOUÉ
Comments:	By: Matt Jordan (mjordan) 2015-02-16 12:08:14.866-0600 Thanks for your comments. This does not appear to be a bug report and we are closing it. We appreciate the difficulties you are facing, but it would make more sense to raise your question in the support tracker, http://www.asterisk.org/support.