[Home]

Summary:ASTERISK-08594: 500 ms delay on answer introduced channel locking issue
Reporter:phsultan (phsultan)Labels:
Date Opened:2007-01-17 08:36:03.000-0600Date Closed:2007-01-17 13:44:03.000-0600
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) trunk-sleep_on_answer-1.diff
Description:This has been detected while working on SIP, but other channels might be concerned as well.

In a SIP to SIP call, ACK packets related to INVITE requets are not processed, which eventually leads to an unexpected call tear down by Asterisk.

The attached patch solves this by unlocking the channel before calling ast_safe_sleep() in __ast_answer()

Philippe

****** ADDITIONAL INFORMATION ******

Kevin and John Todd discussed the topic here :
http://www.opensubscriber.com/message/asterisk-dev@lists.digium.com/5785288.html

Here is the relevant part of the log messages :
[Jan 17 15:13:14] ERROR[21648]: chan_sip.c:14906 sipsock_read: We could NOT get the channel lock for SIP/7999-0824e968!
[Jan 17 15:13:14] ERROR[21648]: chan_sip.c:14907 sipsock_read: SIP transaction failed: 000ab761-5947002b-73399f38-51d58a6b@192.168.1.1
   -- Packet2Packet bridging SIP/7999-0824e968 and SIP/192.168.1.100-08246d68
[Jan 17 15:13:33] WARNING[21648]: chan_sip.c:1925 retrans_pkt: Maximum retries exceeded on transmission 000ab761-5947002b-73399f38-51d58a6b@192.168.1.1 for seqno 102 (Critical Response)
[Jan 17 15:13:33] WARNING[21648]: chan_sip.c:1942 retrans_pkt: Hanging up call 000ab761-5947002b-73399f38-51d58a6b@192.168.1.1 - no reply to our critical packet.
Comments:By: Joshua C. Colp (jcolp) 2007-01-17 13:44:02.000-0600

Fixed in trunk as of revision 51193. Thanks!