Hi Matti, I've tried to build pjsua on MinGW and did some test calls, however I couldn't reproduce the crash. But then I recalled that there was a bug in G.722 wrapper that may cause assertion (not crash), and it has been fixed weeks ago (r1977). So could you confirm that it is a crash and your source copy is newer than r1977. Regards, nanang 2008/6/16 Matti Zemack <Matti.Zemack at bbc.co.uk>: > Hi all, > > I haven't had too much time to dig into this, basically wanted to see if > others have had the G.722 working without any hick ups. > > I've had some problems with the new G.722 coder (which I am very thankful is > now included in PJSIP). > > When a G.722 call is set up Pjsua randomly crashes. I've got two machines > each with one Pjsua. Sometimes the one machine crashes while setting up a > call, sometimes the other. And I haven't really got a clue why. When > communicating with a separate G.722 device usually one of the Pjsua's can > manage, but then the same call is tried with the other computer which then > crashes. Very random. Memory leak? Usually when one of the machine decides > to start crashing it's Pjsua it continues crashing. When that machine is > finally back to stable usually the other machine starts fighting with us. > > I know I haven't left enough info. I haven't got much more at this time. > Just wanted to see if others have been using the G.722 extensively and > everything working fine or not. > > Setup: Pjsua compiled on MinGW, Win XP. > > Best Regards, > Matti Zemack > BBC R&I > > http://www.bbc.co.uk > This e-mail (and any attachments) is confidential and may contain personal > views which are not the views of the BBC unless specifically stated. > If you have received it in error, please delete it from your system. > Do not use, copy or disclose the information in any way nor act in reliance > on it and notify the sender immediately. > Please note that the BBC monitors e-mails sent or received. > Further communication will signify your consent to this. > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > >
