tree af2e5e800dd24e2b5f42a1f670d2fb1daaf9dadd
parent e33966cec2a1b246114026b2c5eb19555a31d303
author Holger Hans Peter Freyther <zecke@selfish.org> 1256649674 +0100
committer Harald Welte <laforge@gnumonks.org> 1257518314 +0900

[mncc] Fix possible transaction/subscriber and real life subscriber leak

In the case a transaction has been already scheduled return 0 was
called but the subscriber and transaction would leak. Fix it by
calling subscr_put and trans_free.

After claiming the channel also remove the reference on the subscr.