Summary: | ASTERISK-17181: Unwanted Hangup On dial | ||
Reporter: | Chodorenko Michail (chodorenko) | Labels: | |
Date Opened: | 2010-12-29 14:40:40.000-0600 | Date Closed: | 2011-06-07 14:05:08 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Channels/chan_sip/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) server.pcap ( 1) user.pcap | |
Description: | Asterisk unwanted close connection which error "no reply to our critical packet" ****** ADDITIONAL INFORMATION ****** -- Executing [0000@office:1] VoiceMail("SIP/4000-00000007", "4000") in new stack -- <SIP/4000-00000007> Playing 'vm-intro.gsm' (language 'ru') -- <SIP/4000-00000007> Playing 'beep.gsm' (language 'ru') -- Recording the message -- x=0, open writing: /var/spool/asterisk/voicemail/default/4000/tmp/z4Tb8j format: wav, 0xbb779a0 [Dec 29 22:16:53] WARNING[4613]: chan_sip.c:3386 retrans_pkt: Retransmission timeout reached on transmission ZDZiZTFhODg5MmExMmEyZGMyNTk1NGQ2NmNhOTdiZTg. for seqno 2 (Critical Response) -- See doc/sip-retransmit.txt. Packet timed out after 8640ms with no response [Dec 29 22:16:53] WARNING[4613]: chan_sip.c:3415 retrans_pkt: Hanging up call ZDZiZTFhODg5MmExMmEyZGMyNTk1NGQ2NmNhOTdiZTg. - no reply to our critical packet (see doc/sip-retransmit.txt). -- User hung up == Parsing '/var/spool/asterisk/voicemail/default/4000/INBOX/msg0002.txt': == Found == Parsing '/var/spool/asterisk/voicemail/default/4000/INBOX/msg0002.txt': == Found == Parsing '/var/spool/asterisk/voicemail/default/4000/INBOX/msg0002.txt': == Found == Spawn extension (office, 0000, 1) exited non-zero on 'SIP/4000-00000007' Sheme connection is: Asterisk (extIP) <->provider(ethernet) <-> Dslam(pppoe) <-> Dlink 2640 <-> User On D-link siproxd disabled PS: in doc document sip-retransmit.txt is not present | ||
Comments: | By: Chodorenko Michail (chodorenko) 2010-12-29 14:42:33.000-0600 Add tcpdump files from user and server By: Stefan Schmidt (schmidts) 2010-12-30 01:59:28.000-0600 I see nothing wrong in here, only the client does not send the necessary ACK response to the 200 OK message from asterisk. asterisks then retransmit the 200 OK several times and after the T1x64 (normally 30sec) timeout the channel is hung up. You can see this on both sides, server and client that there is no ACK message from the client to the server. Please check your client cause asterisk act exactly like it should do and also what you see in the warning message: no reply to our critical packet (200 OK) best regards stefan |