Max CtRiX ha scritto: > > It may happen that the list of stun requests that don't have a response > are kept in memory for a long time. > > So if you do a lot of calls, you may have a large chain of stun requests > using memory that are useless.
Unfortunatly i'm getting the problem with just 1 call right after starting up callweaver > You should see something like: > > cw_log(LOG_DEBUG,"** STUN Sending request after acquiring STUN\n"); > > or > > cw_log(LOG_DEBUG, "deleting this request of reqresp > %d\n",rr->p->stun_resreq_id); > > in your logs. Yes, im' getting normal stun operation during call setup (invite, etc) and on sip registry. Even if i cancel the call before the remote end send an answer everything keep working fine, the problem begin when someone answer my call (thing that should almost always happen). It's like if callweaver tried to make a stun request for every RTP packed sent. I've tried with 3 different stun server: - stun.ekiga.net - stun.sipgate.net:10000 - stun.voip.eutelia.it and sincerely i can't belive none of them is working correctly... > If you're sure that your stun servers work well, try to lower down, in > stun.c, the 300 value to something like 10 or similar. > > ->> here if (req_queue->whendone + 300 < now) > > And tell if it works better (unless there is a leak in the newest code, > but i haven't seen it yet) I'll give it a try tomorrow morning. > In all cases, i don't think that stun can fill the memory in some > seconds. There must me something else going on. I tried with 2 sip providers and both gave the same problem with stun enabled. With stun disabled everything seems to be working fine... > Max Enrico _______________________________________________ Callweaver-users mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-users
