I am a spanish speaker and I agree that Asterisk spanish sound files
have a bad accent that sounds no spanish at all. Fortunately there are
spanish packages of sound files for asterisk around the net. A quick
search in google gives this page:
SVN commits to the Asterisk project wrote:
URL: http://svn.digium.com/view/asterisk?view=revrev=77810
Log:
Discovered in experiments on core files: if you wrap the lock and unlock
calls with sip_pvt_lock and sip_pvt_unlock, you lose the tracing info you
would normally get via
On Tuesday 31 July 2007 08:13, Tzafrir Cohen wrote:
On Tue, Jul 31, 2007 at 07:34:54AM -0500, Tilghman Lesher wrote:
On Tuesday 31 July 2007, Tzafrir Cohen wrote:
Asterisk is really the application menuselect was designed for.
However, is there really a point for the common user to
The main problem was in sangoma hardware echocanceler which has some
noise filter. Sangoma today announced new drivers, which this filter
turns off. I've tested it and fax are now going well.
Martin Vít wrote:
Hello,
I'm testing 1.4.5 (no modifications) with E1 card and i've found problem.
I always had the impression that 'nat=yes' is a bit of a legacy parameter
that carries back to a time when SIP signaling was not assumed to be
symmetrical, which was done later as a concession to the ubiquity of NAT.
In other words, a SIP UA was not necessarily justified in concluding that
the
On Tue, Jul 31, 2007 at 10:46:15AM -0500, Tilghman Lesher wrote:
On Tuesday 31 July 2007 08:13, Tzafrir Cohen wrote:
On Tue, Jul 31, 2007 at 07:34:54AM -0500, Tilghman Lesher wrote:
On Tuesday 31 July 2007, Tzafrir Cohen wrote:
Asterisk is really the application menuselect was designed
On Tue, Jul 31, 2007 at 07:34:54AM -0500, Tilghman Lesher wrote:
On Tuesday 31 July 2007, Tzafrir Cohen wrote:
So again: what usage scenarios are there where there is a benefit
from using menuselect with asterisk?
(This is not a rhethorical question. Please provide examples)
I think the
The issues you bring up with menuselect in terms of automating the
build process is why we ripped it out completely from the v1.4 build
process. We just replace the Makefile with our own which is actually a
derivative of the v1.2 Makefile that we corrected quite some time ago
to support
We're getting close to wrapping up the final list of speakers for
AstriCon, but wanted to give the Asterisk community one more chance to
speak up and be heard. If you're interested in presenting at AstriCon,
please go to http://www.astricon.net/ and click on the Speak at
AstriCon link on the
SVN commits to the Digium repositories wrote:
Author: tilghman
Date: Tue Jul 31 11:44:25 2007
New Revision: 77834
URL: http://svn.digium.com/view/asterisk?view=revrev=77834
Log:
Add func_lock, which creates dialplan mutexes, and note that the Macro apps
are now deprecated.
(Closes issue
On 7/31/07, Bob Atkins [EMAIL PROTECTED] wrote:
The issues you bring up with menuselect in terms of automating the build
process is why we ripped it out completely from the v1.4 build process. We
just replace the Makefile with our own which is actually a derivative of the
v1.2 Makefile
It turns out that that I only submitted one bug report
http://bugs.digium.com/view.php?id=7876 originally on 9/3/06 for the
v1.2 build issues which was then extended to the v1.4 build issues and
was left in my court on 3/26/07. I haven't responded because the fixes
would have been ugly band
12 matches
Mail list logo
