Hi Laurent, laurent schweizer wrote: > hello, > > I use sems as billing prepaid application and I have 2 problem . > > the first one is that memory is growing .... bellow report of memory > allocation. > > memory log > http://pastebin.com/mabb4eb6 > > It looks like you have a lot (405) of thrashed sessions still in memory. Are you sure that those sessions are terminated by your app properly?
> the second is more complicated. I see that somes call are send to > sems and not forwarded by sems to the next hop. Could you please try to isolate the issue with a simple (as simple as possible) example? > > to check memory, I generate with pjsua 600 calls and after all calls > was send I wait to stop sems that timers are terminated. > > while I was waiting , suddenly I saw sems sending an old calls. > Concerning this issue, it is the 11th retransmission of a request which been sent previously, but most probably not replied (or SEMS did not get the reply for some reason). 11th retransmission means, after 20 minutes, if my calculation is right... So the real question is, why the transaction timeout timer did not expire after 32 seconds, as it is supposed to do. Just to be sure: did you change that transaction timeout timer? If not, it looks like we have a bug... Could you please redo the test, and then record the complete debug log and send it to me? Cheers, Raphael. > > log of old calls started after long time > > http://pastebin.com/m42b24156 > _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
