| Summary: | ASTERISK-01890: Cancel branch after final response. | ||
| Reporter: | Antonio Abajo (zanzibar) | Labels: | |
| Date Opened: | 2006-02-10 00:17:03.000-0600 | Date Closed: | 2011-06-07 14:10:17 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | I am working like proxy parallel role versus two asterisks. When I send two INVITEs one for each one, I receive the final response (200ok) instantaneously. But my application first executes the routine of the first (order millisecond) when still it has not received the second 200ok (this is on the way) and my application generates a CANCEL message to cancel the other branch that still has not received his final response. When this cancel arrives to Asterisk, it answers with a "487 Request Terminate" of the INVITE and 200oK of the CANCEL and soon it continues sending retransmisions of 200 Ok of INVITE. This behavior is not rfc3261 compliant, it say that when you has generated the final response and soon, you receives to CANCEL message, the stack should discard this and it is not occurs. | ||
| Comments: | By: Olle Johansson (oej) 2006-02-10 03:31:58.000-0600 Again, according to the bug guidelines we need SIP debug output from both servers. By: Olle Johansson (oej) 2006-03-02 02:08:55.000-0600 I would really like to look into this issue, but need a full SIP debug from you. THanks. By: Olle Johansson (oej) 2006-05-02 15:34:05 No answer from bug reporter. | ||