> Thanks for all bug tracking and patches. However, I don't think there is a > need for yet another branch specific to wxCommunicator. > Is there a good reason your fixes cannot be included into the main branch ? >
It is not meant to be specific to wxCommunicator, it will be commercially used once all important bugs are fixed. Sipxtapi branch is too buggy in my opinion to be used commercially, therefore I'm working on a complete revamp of the sipxtapi code. The way my private branch is worked on violates some unwritten rules of Sip foundry but enables me to do the work much faster. That's why its done separately. All changes will be available to public. Theoretically the revamp shouldn't take longer than 2 weeks, but I have only few days left until I have to study for university exams. I expect it will be fully finished maybe on 10th July. You can keep using sipxtapi for development, and then switch to whatever branch you find more stable. Snapshot of the latest revision can be found in http://sourceforge.net/projects/wxcommunicator/ in the downloads section under name "sipxtapi-src-experimental-r26.tar.bz2". It's really an experimental version, but has all patches applied. Experimental means lots of changes were made without any testing. to Daniel: If you encounter your bug here too, then it might be because either speex or GSM is not enabled. I have found that then there is a problem, but I haven't had the time to fix it. If you use GSM and speex everything should work. Jaro _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
