On Wed, May 26, 2010 at 7:28 PM, Julien Claassen <[email protected]> wrote: > Hi Motiejus! > If all else fails for the moment, it should be quite simple to move JACK. > Move all jack applications from /usr/local/bin to /usr/bin. > In /usr/local/lib move the dir jack and libjack* to /usr/lib. > That should be it for the moment. another thing is to hack the JACK > confiugre script. I did that as well. As JACK didn't like to install, while a > system wide installation was there. > I hope this can help a bit.
Thanks Julien! I am eager to try that, but with a question. Why should I hack the installation script if jack is already installed and libraries moved? Please explain that in more detail :-) If you mean pre-hacking (before installation) (and no library/binary movement after "hacking" if I understand correctly), could you please share the script (possibly a diff against original?) > Question: Do you also use app_jack in a dialplan from the CLI? How does that > work (reliability wise)? This is my wiki entry. This works, but has three major disadvantages: http://www.voip-info.org/wiki/view/Asterisk+cmd+Dial#DialtogetherwithopeniningJackportsforcal 1. There is a weird sound for ~0.3 second observed when jack ports connect (like "BLUAH hello"). It isn't major (after asking several customers barely noticed anything). However, I can hear this clearly when I am calling; 2. Early RTP (pre-answer) cannot be transferred to jack in this manner (for example, when calling to mobiles or landlines you cannot give jack operator messages). 3. Not much tested in production environment - pretty unstable. See below. Because of the (2) reason I am planning to execute this line: *CLI> core set chanvar SIP/$channel JACK_HOOK(manipulate,i(SIP/$channel:input),o(SIP/$channel:output)) on Through AMI. Executing it through CLI is tested and it worked without problems (including pre-answering). I will write a C++ script that does the AMI observing and jack connecting through AMI, I will push thos to SoundPatty. About reliability... I don't know what (is it my program or old jackd), but something causes deadlocks for jackd and both asterisk and jackd hang until I press ctrl-c for my jackd server (then asterisk "gets back to life"). This is the reason I am upgrading. One notice for deploying jack_hook+asterisk: be sure to disconnect and remove jack client before quitting the program (thread). This fixed some deadlocking my past observings. Regards Motiejus -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
