t_lookup_cancel() does not work after t_newtran()
-------------------------------------------------
Key: SER-432
URL: http://tracker.iptel.org/browse/SER-432
Project: SER
Issue Type: Bug
Components: Transaction Manager
Affects Versions: 2.0, Ipteldorf
Priority: Minor
When t_lookup_cancel() is called after t_newtran(), the T is reset to NULL
without unreferencing it. Furthermore, t_relay_cancel() finds the transaction
later on in the hash table, and assumes that the CANCEL has already been
forwarded because T is not set, which is wrong. The result is that the CANCEL
is not forwarded to the destination.
t_lookup_cancel() should not change T at all, the attached patch corrects it.
The function is also extended with a parameter. If it is set to 1, the message
flags are rewritten with the flags of the INVITE, so it is possible to check in
which state the transaction is cancelled for example.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.iptel.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Serdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/serdev
