Rev 8875 changed the way transaction are cancelled.
Before, the b2b logic was able to push a Reason header down to tm to be appended to the CANCEL request.
The new way of sending CANCEL, doesn't allow setting extra headers in CANCEL requests:
The tm is able to automatically add Reason header for cancelled transaction when a branch is answered, but for b2b. the transaction is not properly detected as being in "200" state.
When a call is forked in b2b mode and the answered, CANCEL requests are sent out to the other branches, but the Reason header is not set.
The reason for this is because in tm:build_cancel() the Trans->uas.status is still set to "180".
We have two issues here:
1. the ability to push extra headers in CANCEL via tm api was lost;
2. the tm uas transaction status is not properly set into a 200 state when a 200 ok is received on a branch.
Log in to post a comment.