Paweł Pierścionek wrote:
> Good question. RPMs will be 4.0.0-15824 or newer compiled directly
> from the urtho_4.0 branch I am about to update with the "fixes" for ACD.
> If You are willing to risk the custom build than downloading all RPMs
> from the URL (to be posted on Monday) and doing rpm -Uvh sipx*rpm
> while sipXecs is NOT running should do the trick.
>
> The real problem is how will You maintain the installation after You
> upgrade it to a custom build.

Pawel,

We have to risk a custom build, the only other choice is to dump SipXecs
completely. Which would be a pity, as we have invested a lot of time
already. Once installed we will fully test and after that will have to
take a chance and go live. The hope being that a solution gets
implemented in SipXecs main line build, so that we can switch over to that.

Not ideal, but it is all we have at the moment.


> Bounty is only part of the problem. Convincing FS devs that I am not
> the sole beneficent of the fix is the other part ;)
> There are several tracker issues in sipXecs caused by this problem but
> not classified as having any real use case.
> Eg an assistant cannot att. transfer her boss into a conference bridge
> with sipXecs 4.0.
>
> A bump in priority on those tickets and some attention from Nortel
> would help :)
>
> I'll get back on my third and last attempt on dirty fixing this issue
> myself (race condition inside FS bridge/transfer threads) next week
> and only then will start fixing this issue on OSI levels 8 and 9.
>
> Pawel,
Well I make number 2, so you are not the only one. As to those
additional issues, if you send me the links I will add my vote to the
list as well. Is there someone I should talk to at FreeSwitch? I really
want to get the ball rolling on getting a permanent fix asap.

You have lost me with the "OSI levels 8 and 9" bit?

Damian

_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to