| Summary: | ASTERISK-19828: MESSAGE_SEND_STATUS set to SUCCESS despite response of 400 Bad Request | ||
| Reporter: | philipp2 (philipp2) | Labels: | |
| Date Opened: | 2012-05-01 17:01:53 | Date Closed: | 2012-05-04 08:32:17 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_sip/Messaging |
| Versions: | 10.3.1 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Gentoo Linux | Attachments: | |
| Description: | MESSAGE_SEND_STATUS is set to SUCCESS even though the other side responded with 400 "Bad Request". I do realize that the documentation reads for SUCCESS " Successfully passed on to the protocol handler, but delivery has not necessarily been guaranteed", but still: This should either be FAILURE or a new status like ATTEMPTED or FORWARDED instead of SUCCESS in this case. | ||
| Comments: | By: Richard Mudgett (rmudgett) 2012-05-01 18:33:45.752-0500 That is why there is the qualifier to the SUCCESS status. Delivery is dependent upon the lower level driver and is not guaranteed. The lower level driver has no way to pass delivery confirmation to the upper level driver since that function has already returned. The 400 Bad Request comes in after the status is set and the dialplan has already continued. | ||