ymoona wrote: > Is there a reason why you install the CRT dlls? I install them because without them wxCommunicator wouldn't run on other computers.
> And not set visual not to use them? I'm not sure it can be set anywhere. VS2005 will use them for new exe and dll if you apply service pack 1. > Then they are linked in the sipx dll. It's good news to > hear you're giving the code a make over. I agree the current > sipx-branche isn't very stable. > I've downloaded some packages and now it compiles fine, I only need the > fix the library > paths. I tested r26 using multiple lines and its seems to work fine. But that > is of > course no guarantee. > If you want I can help you with some tests. (load, duration, leak) I would recomend keeping both experimental branch and sipxtapi branch, and if you discover a bug then check whether it exists in sipxtapi branch too. I should have all events working in sipxtapi again soon, and then you can do some testing if you like. If you find it more stable then use it. For finding leaks try both visual leak detector 1.0 and 1.9f. There are some leaks in tacklib, medialib etc but I'm not fixing those now, the priority is leaks in sipxtapi itself. I suggest you keep a list of known leaks, and try to go through all call states, do transfer, send and receive INFO, try subscribe, enable STUN etc. and check whether the event system causes any leaks. In r26 there are leaks in the event system because its the original one. Next revision should have all of them fixed. Keep in mind that experimental branch basically shares tacklib and medialib with sipxtapi branch, and any bugs with SIP signalling or audio problems will also exist in this branch. These problems will be addressed after sipxtapi itself is known to be "safe". Jaro _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
