[asterisk-bugs] [Asterisk 0011736]: sip hung channels and UDP ports
noreply at bugs.digium.com
noreply at bugs.digium.com
Mon Jan 28 12:26:37 CST 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11736
======================================================================
Reported By: MVF
Assigned To: oej
======================================================================
Project: Asterisk
Issue ID: 11736
Category: Channels/chan_sip/General
Reproducibility: sometimes
Severity: minor
Priority: normal
Status: assigned
Asterisk Version: 1.4.17
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 01-10-2008 15:16 CST
Last Modified: 01-28-2008 12:26 CST
======================================================================
Summary: sip hung channels and UDP ports
Description:
I've found that some sip channels of some SIP-SIP calls are not being
released by asterisk. Issuing the command "show channels" display the exact
information for active calls but if I use the "sip show channels" command
it shows the active calls plus a lot of hung channels (check attach).
I´ve checked the "sip show history" of these hung channels and found
that sometimes due to network problems (or redundant termination) asterisk
could receive a "183 Session Progress" message from termination peer after
a CANCEL message has been received from calling party. This problem causes
that * CancelDestroy a non existing call resulting in a hung sip channel
and UDP ports related to it taken. After some time of operation asterisk
stop processing new calls. Please check the sip show history for a hung
peer (originating peer):
* SIP Call
1. NewChan Channel SIP/SIP_LCR-097a7500 - from
4e061fc824c28fdb500a7d6e748
2. TxReqRel INVITE / 102 INVITE - -UNKNOWN-
3. Rx SIP/2.0 / 102 INVITE / 100 trying
4. Cancel Cause Normal Clearing
5. SchedDestroy 32000 ms
6. TxReqRel CANCEL / 102 CANCEL - -UNKNOWN-
7. SchedDestroy 32000 ms
8. Rx SIP/2.0 / 102 CANCEL / 200 ok
9. Rx SIP/2.0 / 102 INVITE / 183 Session Progress
10. CancelDestroy
11. Rx SIP/2.0 / 102 INVITE / 404 Not Found
12. TxReq ACK / 102 ACK - -UNKNOWN-
You can see how after the cancelling exchange a late 183 arrive from
termination peer and confuze * making it to execute a CancelDestroy over a
no more existing peer.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0010052 NOTIFY race condition when state change...
======================================================================
----------------------------------------------------------------------
MVF - 01-28-08 12:26
----------------------------------------------------------------------
Hi oej, My asterisk has been running for 4 days with chan_sip Revision
99978 and the late 183 problem is gone (Yeah!), thank for all the great
work.
I only have three channels hang for other reason. They hang after a
re-invite is received, it looks close to what revolution reported. Please
check the history of one of these channels:
1. NewChan Channel SIP/SIP_LCR-095acd78 - from
3ea708da55f0c3f43d5dde76019
2. TxReqRel INVITE / 102 INVITE - -UNKNOWN-
3. Rx SIP/2.0 / 102 INVITE / 100 trying
4. Rx SIP/2.0 / 102 INVITE / 200 OK
5. TxReq ACK / 102 ACK - -UNKNOWN-
6. Rx INVITE / 244 INVITE / sip:222222222222 at 10.10.10.106
7. ReInv Re-invite received
8. TxResp SIP/2.0 / 244 INVITE - 100 Trying
9. Hangup Cause Normal Clearing
10. SchedDestroy 32000 ms
11. CancelDestroy
12. Rx INVITE / 245 INVITE / sip:222222222222 at 10.10.10.106
13. TxResp SIP/2.0 / 245 INVITE - 491 Request Pending
14. Rx ACK / 245 ACK / sip:222222222222 at 10.10.10.106
15. Rx CANCEL / 244 CANCEL / sip:222222222222 at 10.10.10.106
16. TxResp SIP/2.0 / 244 CANCEL - 503 Server error
Making some test calls I was able to reproduce this sequence from step 1
to 11, I forced the UA that receives the forwarded re-invite to ignore it
and then CANCEL the call. After that I see the SchedDestroy/CancelDestroy
sequence appear:
1. NewChan Channel SIP/SIP_LCR-097647b8 - from
50b6d3da06c9106372fc1efa798
2. TxReqRel INVITE / 102 INVITE - -UNKNOWN-
3. Rx SIP/2.0 / 102 INVITE / 100 trying
4. Rx SIP/2.0 / 102 INVITE / 183 Session Progress
5. Rx SIP/2.0 / 102 INVITE / 200 OK
6. TxReq ACK / 102 ACK - -UNKNOWN-
7. Rx INVITE / 563 INVITE / sip:5555848119 at 64.76.154.106
8. ReInv Re-invite received
9. TxResp SIP/2.0 / 563 INVITE - 100 Trying
10. Hangup Cause Normal Clearing
11. SchedDestroy 32000 ms
12. CancelDestroy
Anyway for an unknown reason this test channel is released after 32
seconds, maybe the following messages appearing in the history of the hang
channel make the channel actually hang (I can't reproduce those messages
yet).
Please let me know if this make any sense to you and... Saludos a España
y OLe!
Issue History
Date Modified Username Field Change
======================================================================
01-28-08 12:26 MVF Note Added: 0081278
======================================================================
More information about the asterisk-bugs
mailing list