Ok, I am sorry, I missed the information 1.0.x branch is done. I am looking forward to 1.8.2 version, the new featured stable version I suppose looking to the road map. Thanks - Vali Dne 21.9.2010 12:52, Benny Prijono napsal(a): > Sorry to break this news, (and I know I've said otherwise in the past) > but I think it's time to say that 1.0.x is done. It's no longer > supported and there will be no further release for this branch. > > In general, we promise to maintain a stable branch for at least 12 > months, and we've done this for 1.0.x. Now that 2.0 is in development > and version 1.8 will be made the new stable, we really can't afford to > maintain 1.0.x > > Best regards, > Benny > > On Tue, Sep 21, 2010 at 5:06 PM, Tom?? Valenta<vali at kamarad.cz> wrote: >> Hi Benny, >> >> my question remained unanswered so I am trying to ask it again. I am using >> PJSIP 1.0.3 in our IVR application and I must say I am completely satisfied. >> PJSIP is a great piece of software. >> >> In 1.0.3 there is a bug, a duplicate of #985 from 1.x branch, I think. Or >> maybe it is #914? Anyway, the application, including PJSIP stack, works fine >> all the time, but when it comes to shut down, the application sometimes >> crashes preventing other parts to clean-up properly. I am using Visual >> Studio 2005 Release build of PJSUA DLL 1.0.3 and when running the >> application in debugger I get following errors: >> >> 1. A dialog box: >> Windows has triggered a breakpoint in VoiceXMLParserSIP.exe. >> This may be due to a corruption of the heap, which indicates a bug in >> VoiceXMLParserSIP.exe or any of the DLLs it has loaded. >> ... >> The output windows may have more diagnostic information. >> >> 2. The output window: >> ... >> The thread 'Win32 Thread' (0x165c) has exited with code 0 (0x0). >> HEAP[VoiceXMLParserSIP.exe]: HEAP: Free Heap block 8378b48 modified at >> 8378c10 after it was freed >> Windows has triggered a breakpoint in VoiceXMLParserSIP.exe. >> ... >> >> I wonder if you are planning to fix it in 1.0.x branch. Or is there a >> workaround you would suggest? If so, is there any performance or other >> penalty? >> >> Thank you. >> Cheers, >> - Vali >> >> _______________________________________________ >> 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 >> > > _______________________________________________ > 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
