| Summary: | ASTERISK-18721: 603 decline is busy not circuit-busy | ||
| Reporter: | rsw686 (rsw686) | Labels: | |
| Date Opened: | 2011-10-13 12:51:21 | Date Closed: | 2011-11-29 14:06:39.000-0600 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_sip/General |
| Versions: | 1.8.7.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ( 0) asterisk-1.8.7.0-sip-decline.patch | |
| Description: | When placing calls through Gafachi and hitting the termination limit they send back SIP 603 decline. Asterisk is passing this back to app_dial as busy. If a line is busy there is no need to try additional providers. SIP code 603 doesn't indicate busy just that the call was declined. I have attached a patch to send back congestion or circuit-busy to app_dial. This seems like the correct response so I can try additional providers should the call be declined. | ||
| Comments: | By: rsw686 (rsw686) 2011-10-13 14:15:15.623-0500 After some reading I feel this might be a Gafachi issue. Since 6xx response codes are global failures returning busy is technically acceptable since the call shouldn't complete elsewhere. However declined and busy don't mean the same thing. I've sent a support request to Gafachi for their reasoning on returning 603 Decline vs 480 Temporarily Unavailable. Since app_dial only supports a few return cases it is hard to make the correct decision when providers interpret the SIP standard differently. Returning the sip response code to the dial plan isn't a good solution either do to the performance hit it has. By: Leif Madsen (lmadsen) 2011-11-01 10:19:42.477-0500 So at this point, should I really just close this issue? I'm not sure if we want to make a change here based on your output. You could potentially bring this up on the mailing list though for discussion. By: rsw686 (rsw686) 2011-11-01 10:28:38.091-0500 Sounds good. I will bring it up on the mailing list. By: Leif Madsen (lmadsen) 2011-11-07 10:46:25.587-0600 Please link the discussion here once you've posted it. Thanks! By: Matt Jordan (mjordan) 2011-11-15 09:23:18.007-0600 Waiting for feedback from mailing list discussion per previous comments. If this is no longer an issue, please note so here. By: Leif Madsen (lmadsen) 2011-11-29 14:06:32.507-0600 Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested. Further information can be found at http://www.asterisk.org/developers/bug-guidelines | ||