Alexander Chemeris wrote: > On 2/15/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > >> It's a pitty sipxtapi is built on such a buggy sip stack.I think more >> effort should be done to fix various bugs reported in jira to get it to >> a usable state rather than add lots of new experimental features. >> > I may be wrong, but I believe sipXtackLib is not that buggy. Many > bugs, mentioned in issue tracker, is fixed in main main svn branch, > but still not merged to sipXtapi branch. We should have another pass > of merging in near future. > > There are 90 open bugs in jira for sipxtacklib. I think that's way too many. How do you know which ones are fixed in main and not in sipxtapi branch? In jira there is only 1 project sipxtacklib and 1 component. If there is too much work with branch synchronization, perhaps there should be only 1 branch of basic libraries like sipxportlib, sipxtacklib which aren't developed in sipxtapi/mediaupdate branch. If you wanted to use another branch you would have to check out those libs from main branch.
> One other thing I want to mention is that there ais ongoing effort to > use resSIProcate SIP stack with sipXmediaLib. reSIProcate have own > highlevel interface, named DUM, similar in functions to sipXcallLib. > If somebody will be interested in, there will be possible to create > mediaAdapterLib wrapper for DUM to use sipXtapi with reSIProcate > stack. > > I will be interested but in a few months when I should have time for it (and if sipxtacklib will still be so buggy). Jaro _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
