On 2009-06-19, at 12:47, Damian Dowling wrote:

> Paweł Pierścionek wrote:
>>>
>>> Pawel,
>>>
>>> You are a life saver, we won't have anything never 300 agents so  
>>> with a
>>> bit of luck we hopefully won't run into one way audio. The other  
>>> issues
>>> we will live with. What to you need to know from me for building the
>>> RPMs?
>>>
>>> We are running on CentOS 5.3  64bit, and using the latest stable  
>>> version
>>> of SipXecs.
>>>
>>
>> will build RPMs on Monday.
>
> Pawel,
>
> Thanks again. How should I install the RPMS over version 4.0.0-015321?

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.

>
>
>>> I am still curious as to how to get the ACD Server sorted long  
>>> term, any
>>> ideas?
>>>
>>
>> Wait for the replacement I am to announce as soon as I fix the att.
>> transfer issue in FreeSwitch (which might require a bounty to FS
>> developers, no ETA)
>>
>> Pawel,
>
> The bounty I should be able to help with, what is the best way to
> proceed? I take it we would need to chat with someone on the FS  
> Project.
>
> Damian

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,
_______________________________________________
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