[asterisk-bugs] [Asterisk 0012101]: SIP channel hung due to CANCEL ReliableXmit (ReTX)
noreply at bugs.digium.com
noreply at bugs.digium.com
Tue Mar 18 16:04:18 CDT 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=12101
======================================================================
Reported By: MVF
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 12101
Category: Channels/chan_sip/General
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Asterisk Version: 1.4.18
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 02-28-2008 13:23 CST
Last Modified: 03-18-2008 16:04 CDT
======================================================================
Summary: SIP channel hung due to CANCEL ReliableXmit (ReTX)
Description:
I've detected a problem that make asterisk keep sip channels up forever
even when the call has been disconnected, the problem keep UDP ports and
memory taken making asterisk to drop new calls when the sip channels hung
increase.
Reviewing the "sip show history" of one of these hung channels I see that
the call is cancel by calling party while is on ringing state, after that
asterisk send CANCEL to the peer but it didn't get an answer (maybe because
of network problems). After I get some bad responses from peer, maybe also
due to network problems that asterisk reply with an ACK but the history
shows a new ReliableXmit timeout message every 30 seconds.
(originating peer)
* SIP Call
1. TxReqRel INVITE / 102 INVITE - -UNKNOWN-
2. Rx SIP/2.0 / 102 INVITE / 100 Trying
3. Rx SIP/2.0 / 102 INVITE / 100 Trying
4. Rx SIP/2.0 / 102 INVITE / 180 Ringing
5. Rx SIP/2.0 / 102 INVITE / 180 Ringing
6. Cancel Cause Normal Clearing
7. SchedDestroy 32000 ms
8. TxReqRel CANCEL / 102 CANCEL - -UNKNOWN-
9. SchedDestroy 32000 ms
10. ReTx 1000 CANCEL sip:17898702397 at 20.20.20.25 SIP/2.0
11. ReTx 2000 CANCEL sip:17898702397 at 20.20.20.25 SIP/2.0
12. Rx SIP/2.0 / 102 CANCEL / 100 Trying
13. ReliableXmit timeout
14. Rx SIP/2.0 / 102 INVITE / 180 Ringing
15. Rx SIP/2.0 / 102 INVITE / 486 Busy Here
16. TxReq ACK / 102 ACK - -UNKNOWN-
17. ReliableXmit timeout
18. ReliableXmit timeout
19. ReliableXmit timeout
20. ReliableXmit timeout
21. ReliableXmit timeout
22. ReliableXmit timeout
23. ReliableXmit timeout
24. ReliableXmit timeout
25. ReliableXmit timeout
26. ReliableXmit timeout
27. ReliableXmit timeout
28. ReliableXmit timeout
29. ReliableXmit timeout
30. ReliableXmit timeout
31. ReliableXmit timeout
32. ReliableXmit timeout
33. ReliableXmit timeout
34. ReliableXmit timeout
35. ReliableXmit timeout
36. ReliableXmit timeout
37. ReliableXmit timeout
38. ReliableXmit timeout
39. ReliableXmit timeout
40. ReliableXmit timeout
41. ReliableXmit timeout
42. ReliableXmit timeout
43. ReliableXmit timeout
44. ReliableXmit timeout
45. ReliableXmit timeout
46. ReliableXmit timeout
47. ReliableXmit timeout
48. ReliableXmit timeout
49. ReliableXmit timeout
50. ReliableXmit timeout
I got a capture for the sip transaction messages that generate these hung
sip channels, please take a look at it in the attached file including two
captures (20080227_sip_channel_hung_at_cancel_ReTX.txt), note that there is
no sip messages sent after the last ACK, the "ReliableXmit timeout"
messages appear in the history of the call filling the 50 slot buffer and
even deleting the old history messages. The "sip show channels" command
shows the channel hung forever.
20.20.20.25 1789870239 185d051b629 00102/00000 0x0 (nothing) No
(d) Tx: ACK
======================================================================
----------------------------------------------------------------------
MVF - 03-18-08 16:04
----------------------------------------------------------------------
Sorry for the lack of correct debug, I'm attaching it now. Call ID
085357c64acd9560021e7b542852562d correspond to the outgoing leg a call that
generate a hung channel. The history for this channel is not in the debug
log because the channel is active forever. This is the history of the
channel obtained from CLI:
B2BUA*CLI> sip show history 085357c64ac
B2BUA*CLI>
* SIP Call
1. NewChan Channel SIP/PEER_DID_01-0a25b420 - from
085357c64acd9560021e7b
2. TxReqRel INVITE / 102 INVITE - -UNKNOWN-
3. Rx SIP/2.0 / 102 INVITE / 100 Trying
4. Rx SIP/2.0 / 102 INVITE / 100 Trying
5. Rx SIP/2.0 / 102 INVITE / 180 Ringing
6. Rx SIP/2.0 / 102 INVITE / 180 Ringing
7. Cancel Cause Normal Clearing
8. SchedDestroy 32000 ms
9. TxReqRel CANCEL / 102 CANCEL - -UNKNOWN-
10. SchedDestroy 32000 ms
11. ReTx 1000 CANCEL sip:5625709200 at 20.88.6.25 SIP/2.0
12. ReTx 2000 CANCEL sip:5625709200 at 20.88.6.25 SIP/2.0
13. Rx SIP/2.0 / 102 CANCEL / 100 Trying
14. Rx SIP/2.0 / 102 INVITE / 180 Ringing
15. ReliableXmit timeout
16. Rx SIP/2.0 / 102 INVITE / 486 Busy Here
17. TxReq ACK / 102 ACK - -UNKNOWN-
18. ReliableXmit timeout
19. ReliableXmit timeout
20. ReliableXmit timeout
21. ReliableXmit timeout
22. ReliableXmit timeout
23. ReliableXmit timeout
24. ReliableXmit timeout
25. ReliableXmit timeout
26. ReliableXmit timeout
27. ReliableXmit timeout
28. ReliableXmit timeout
29. ReliableXmit timeout
30. ReliableXmit timeout
31. ReliableXmit timeout
32. ReliableXmit timeout
33. ReliableXmit timeout
The incoming leg of the call (Call ID
d7c7df47-96c6-a73a-fa14-0002a40217d0) is properly destroy.
Issue History
Date Modified Username Field Change
======================================================================
03-18-08 16:04 MVF Note Added: 0084201
======================================================================
More information about the asterisk-bugs
mailing list