Hopefully our server works once more, and this message will come through.
___
Callweaver-users mailing list
Callweaver-users@callweaver.org
http://lists.callweaver.org/mailman/listinfo/callweaver-users
On 04/01/2010 08:19 PM, Igor Moiseev wrote:
Hi Richard! We deployed one faxserver with callweaver and mean values
are the following
Sent faxes about 400/week with error on sending about 10%
Received faxes about 1400/week about 15% of errors
Percents are not very real, because it includes
Eric Chatham wrote:
Hello,
We have a serious problem with Callweaver. It seems faxes are going to
the wrong numbers. We are now engaged in a legal issue because of
this. Sensitive information was going to a customer that should’ve
gone to our HR department. Is there something I need to
Eric Chatham wrote:
On Wednesday, June 10, 2009 07:01
Callweaver version??
spandsp version??
spandsp-0.0.5
callweaver-1.2.1
Strange. When you build callweaver 1.2.1 is should demand
spandsp-0.0.6pre12 or newer, and should have refused to build against
spandsp-0.0.5.
Eric Chatham wrote:
Hello,
I’m new to Callweaver. First, are there any good sources out there to
read up on for Callweaver? Secondly, we currently are running
Callweaver 1.9.99, and would like to upgrade to 1.2.1. What would we
need to do to do the upgrade? We are using CentOS (RHEL 5.1)
Hi Hermann
yao marius hemann kanga wrote:
Thanks you for your reply.
it is very difficult to find a T38 carrier provider but i find one who
claim to support it.
however when i try to place a fax call i find some problem (comfort
noise support in callweaver).
i contact the support , this
Hi,
I think most users of Callweaver have been running recent 1.2 branch SVN
code for a long time now, because that was the only way to get the
latest fixes or to be able to use recent versions of spandsp. Today we
finally got around to making an actual release of callweaver.
You can now find
Kristijan Vrban wrote:
Hello, i have an older fax machine from the '90s Triumph-Adler FX6000
When i send a fax with T.30 TxFAX to it, TxFAX send only the first
page and stop with:
Fax send not successful - result (21) No response after sending a page.
Fax log with one page:
Kristijan Vrban wrote:
to debug this, i wanted to look how a working T.38 transmission look
like, so setup two cw with spandsp6_pre10
[faxout] ;cw 1
exten = s,1,TxFAX(${FAXFILE},debug)
exten = s,n,Hangup
[faxin] ;cw 2
exten = 123,1,RxFAX(/tmp/faxfile.tiff,debug)
exten = 123,n,Hangup()
Kristijan Vrban wrote:
next log, AttraFax - spandsp is working:
http://iax2gate.de/callweaver/AttraFax_spandsp_log
Wireshark say something about Malformed for frame 160 and 161 from
spandsp (again the t4-non-ecm-sig-end)
Kristijan
The Malformed? reports are due to a bug in Wireshark.
Gerald Cox wrote:
When 1.2.0.2 came out I had a heck of a time getting the now broken fax
part of it working. I fixed it by going back to an older version of
spandsp.
I don't remember the specifics or the version numbers, but I believe
your problem is caused by spandsp.
I've been using
Hi,
If anyone is interested in the low speed modems needed for POS
applications (V.22, V.22bis, V.22bisFC and V.29FC) please contact me. I
had some spare time while travelling, and finally got the V.22bis code I
started a long time ago into a start where its basically functional. I'm
now
Michael wrote:
On Sat, 25 Apr 2009 16:59:48 you wrote:
I probably have not understood what exactly you need, however I think you
can try these options
1 . the batch file / call file gets deleted if the number of retries are
ended so you can try changing number of retries
2. an action
Michael wrote:
On Sat, 25 Apr 2009 18:20:16 you wrote:
Well the basic reason is that the free software user base sucks. Rather
than contribute a solution people would rather whine that the whole
world hasn't been given to them for free. After several years of huge
numbers of people
Michael wrote:
IAXmodem and chan_fax already do that. What more are you looking for?
I've had a half finished SIPmodem for ages, which is a bit like IAXmodem
but uses SIP and allows bother T.38 and audio FAXing (IAXmodem is audio
only, as T.38 is not defined over IAX2). I expect that would be
Michael wrote:
Callweaver states the resolution as 7700 and yet the identify command (part
of Image Magick) claims the resolution of the input TIFF file is 204x196.
1. Is the sending resolution determined by the TIFF file or the fax software?
2. Is there any correlation between the
Michael wrote:
There is a dialplan variable called FAX_DISABLE_V17. If you don't set
that, V.17 should work.
I have not set it.
Are you using T.38? A lot of people set their T.38 gateways to inhibit
anything above 9600bps.
Next question - why most of time when calling from
Michael wrote:
Hello,
Is it possible to get CW to support v.17 fax and/or JBIG?
Michael
CW supports V.17.
CW cannot support JBIG right now, for patent reasons. I'm not sure when
the relevant patents expire. JBIG support by FAX machines is patchy, so
I'm not sure how big a benefit it
Michael wrote:
CW supports V.17.
CW cannot support JBIG right now, for patent reasons. I'm not sure when
the relevant patents expire. JBIG support by FAX machines is patchy, so
I'm not sure how big a benefit it might be for most people.
There is no colour FAX support right now, and there
David wrote:
Hello,
When switching to T.38 CW sends these default values for the following
2 parameters:
T38FaxMaxBuffer = 400
T38FaxMaxDatagram = 400
I need to limit them to:
T38FaxMaxBuffer = 200
T38FaxMaxDatagram = 72
I tried doing that in udptl.conf, but noticed that only
Hi Julian,
In your log I can't see any received T.38 packets. i do, however see a
really interesting IP address, which seems to have come from the SIP
information - 99.999.183.2
Regards,
Steve
Julian Yap wrote:
I found it works on occasions. The times that it does work, I see
something
praveen kumar wrote:
praveen kumar wrote:
Hello -
Does anyone in this list had luck with Sonus equipment
(Commpartners)
and Callweaver? I am trying to do T38 fax-in (termination).
Origination is ok.
I tried debugging the log but Callweaver
praveen kumar wrote:
Hello -
Does anyone in this list had luck with Sonus equipment (Commpartners)
and Callweaver? I am trying to do T38 fax-in (termination).
Origination is ok.
I tried debugging the log but Callweaver fails in almost all cases to
establish a handshake. The same config
Hi all,
Anyone who has been having trouble with spandsp's T.38 gateway and FAX
machines which send TEP might find the latest spandsp snapshot
interesting. I want to do more work in this area of spandsp, but the
changes in today's snapshot certainly seem to avoid most problems I've seen.
Steve
Hi Ray,
Ray Jackson wrote:
Hi all,
We have been using Callweaver+SpanDSP for a while now for Fax2email
services and overall it has been working very well. However, some
makes/models of fax machines won't accept fax messages we send and come
back with failure reason:
Hi,
Hi Damjan!
Thanks, this was really a good starting point. Do you know are there any
papers/reports/personal experience about the robustness of T.38 against
jitter/delay/loss?
Audiocodes claims it can deal with up to 400 milliseconds of jitter and 12
seconds round-trip delay
Hi Ken,
Ciscos are fine if you get the right firmware revision. However, they
seem to have produced a number of broken T.38 revisions.
Regards,
Steve
Ken Rice wrote:
AS5300's are cheap and super reliable... And its recommended... A AS5300
only does up to 4 E1/T1s and you can find them
Well, I think it was rather a blanket statement to say the 5400 crashes.
Cisco have produced some really flaky T.38 software, and some good
stuff. I don't think the issue is 5300 vs 5400, but which software
revision they are running. One would hope that new versions become more
polished.
Hi Harold,
Harold Polet wrote:
I can't make anything newer than spandsp-0.0.4pre16 on osx
Unfortunately callweaver release request spandsp-0.0.5
I got :
In file included from make_modem_filter.c:47:
spandsp.h:41:20: error: tiffio.h: No such file or directory
...
make[2]: ***
Harold Polet wrote:
I can't make anything newer than spandsp-0.0.4pre16 on osx
Unfortunately callweaver release request spandsp-0.0.5
I got :
In file included from make_modem_filter.c:47:
spandsp.h:41:20: error: tiffio.h: No such file or directory
...
make[2]: *** [make_modem_filter] Error
Sven Schwyn wrote:
Hola
Is there something similar to app_notify for CallWeaver? Or is there a
chance the 1.0 release of app_notify will work with CW if the source
is callweaverized (with search-n-replace)?
-sven
PS:
Just an idea: How about adding the CW mailinglist to Nabble?
I
Sven Schwyn wrote:
Hola
Is there something similar to app_notify for CallWeaver? Or is there a
chance the 1.0 release of app_notify will work with CW if the source
is callweaverized (with search-n-replace)?
It looks like gentoo has app_notify, and tags it as GPL 2.
Steve
Stefano Marinelli wrote:
Hello everybody.
Tried it with both SIP and Zaptel channels. All right when the faxes are
normal but when they’re “heavy”, with images or pictures, they’re
received by the RxFax() but the resulting .tiff is just 8 bytes big.
Using SIP, after two minutes, the line is
Andreas van dem Helge wrote:
I've never used callweaver beyond (attempting) testing the broken
T38Gateway. The day it works I might consider switching. For now I'll
keep on using Asterisk. Digium generally don't add features that are
broken and remain that way for years usually they
Hi Marek,
The answering party is responsible for reinviting a call from audio to
T.38. This should happen whether or not the calling party offers T.38 as
an option in the SDP of the INVITE. A T.38 capable box should attempt a
re-invite to T.38, and fall back to the current codec if that
Marek Zelem wrote:
Hi all
Thanks a lot for your responses. I will change Fax passthru method of
ATA to REINVITE (it was indeed NSE - thanks Damjan). I can experiment with
it only out of working hours so I have to wait till evening.
But, I have a question about what Steve said.
Marek Zelem wrote:
Hi
I have changed NSE to REINVITE on ATA. Now there is word 're-invite' in
logs, so something changed. But fax is still not working.
I did both directions.
Receiving fax from ISDN CAPI -- ATA -- fax:
http://marek.terminus.sk/cw/full_2_in.gz
Hi,
Several people have tried testing PAP2Ts against the T.38 support in
Callweaver, only to find the PAP2T does not support T.38. Although the
current PAP2T manual still seems to indicate there is no support, it
appears that from version 3.3 of the firmware there is T.38 support. If
anyone
Thomas Kenyon wrote:
Walter Klomp wrote:
Hi Steve, so you are still alive actually :-)
Well, u know what is going to happen there when I complain to them. It
crashes the actual call, not the complete box obviously. Since a 10 year old
AS5300 doesn't have any issues talking to this AS5400
Eugene Prokopiev wrote:
Hi,
There are no activity in BTS at least for faxing related problems and
no letters in this maillists from Steve Underwood, Roy Sigurd
Karlsbakk, Massimo Cetra and some other developers.
Is CallWeaver development alive?
--
Thanks,
Eugene Prokopiev
How alive
Arik Raffael Funke wrote:
Hi,
I am trying to compile RC5 but am without luck. I tried with
spandsp-0.0.3, spandsp-0.0.4pre10 and spandsp-0.0.4pre16. Can anybody
tell me what I am missing if I get the following error messages?
Cheers,
Arik
--- output: configure --with-chan_misdn
Hi Loïc,
Loïc Foucault wrote:
Hi,
I'm using this setup: Callweaver-Internet-NAT-analog gateway.
I'm able to do and receive voice G.711 calls perfectly but When I'm using
T.38, It doesn't work.
The ethereal traces reveal that the Callweaver try to send udp T.38 packets
to the internal IP
Eugene Prokopiev wrote:
Hi,
I use hardware fax machines via dlink voip gateways and TxFax with
G711, not T.38. Some times ago fax machines and TxFax worked fne, but
now only fax machines works. With TxFax I got PHASEESTATUS 13
(Unexpected message received) every time. Now I use last 1.2
Hi all,
After some recent changes to Callweaver and spandsp, T.38 compatibility
has been improving a lot. Some changes I checked into both the 1.2
branch and trunk this weekend seem to have resolved compatibility issues
with yet more T.38 implementations. Anyone who has been having problems
Damjan Jovanovic wrote:
X-ECN Telecoms-MailScanner-Information: Contact ECN Telecoms
X-ECN Telecoms-MailScanner: Found to be clean
X-ECN Telecoms-MailScanner-From: [EMAIL PROTECTED]
X-Spam-Status: No
On Tue, 2007-11-06 at 19:17 -0500, [EMAIL PROTECTED] wrote:
There's basically nothing
Hi,
If you have had trouble using txfax to send to Canon FAX machines,
please try spandsp-0.0.4pre11, or the latest snapshot. spandsp was
setting a bit in a control message incorrectly, due to my
misunderstanding of its purpose. It seems only Canon machines care about
this bit, so most
Andrea Lanza wrote:
Further tests
I see a strange thing.
When using non ecm the fax arrives almost always
When using ecm the fax arrives almost always... but always the result is
failed !
I am getting a lot of faxes perfectly transmitted WITH ECM, all of them
beeing declared as failed
Hi Walter,
Walter Klomp wrote:
Hi,
I am trying to send faxes using spandsp and callweaver over T.38, using the
example from here:
http://www.callweaver.org/wiki/Faxing+with+CallWeaver
But sending multi-page faxes fail (unless I switch off ECM).
I obviously googled my ass off on this, and
Time passes, and Walter has sent me some test data for analysis
Steve Underwood wrote:
Hi Walter,
Walter Klomp wrote:
Hi,
I am trying to send faxes using spandsp and callweaver over T.38, using the
example from here:
http://www.callweaver.org/wiki/Faxing+with+CallWeaver
Paulo Scardine wrote:
Paulo Scardine escreveu:
Hi people.
Sometimes I got unicall channels locked.
Command UC show channels shows strange numeric status instead of
idle. Command show channels reports zero active channels but a
number greater than zero (actually the number of unicall
Rob Gillan wrote:
Hi all,
Thought I'd start a new thread in an attempt to get callweaver
compiled and running on OSX/Darwin (my last title wrongly accusatory
of spandsp).
There is a moral here: Making wild unfounded accusations of crappiness
almost immediately looses all the
Checkov, Andrew wrote:
Hello all,
I suggest to think about reversed logic of T.38 processing - IMHO it will
be better to _disable_ it by default and _enable_ with some variable like
T38_ENABLE for selected peers or sessions.
Currently we are in process of switching our customers
from
David wrote:
Hello list,
Is there a way to know the following info (through the ogi variables)
for an incoming fax?
1. Speed (data rate) used.
Yes
2. Number of pages.
Yes
3. Connection time.
I don't think this one is recorded right now. It would be simple to add
4. Number of pages.
Yes
Hi all,
The Debian repository contains spandsp, but people have asked for
spandsp to include the Debian build files so it is easier to build a
Debian package for a hot off the press revision. I know nothing of the
ways of Debian, but I have now added a set of files to the spandsp
Tamas wrote:
Hi,
probably there is an issue in callweaver.c, as it parses for cwsoundsdir
instead of opbxsoundsdir.
} else if (!strcasecmp(v-name, cwsoundsdir)) {
opbx_copy_string(opbx_config_OPBX_SOUNDS_DIR,
v-value,
and this
parameter was in the config files supplied by the install. I had no
idea to change that parameter.
Thanks for the help...
Am 06.07.2007 um 13:56 schrieb Steve Underwood:
Tamas wrote:
Hi,
probably there is an issue in callweaver.c, as it parses for
cwsoundsdir
Karel K. wrote:
On 6/26/07, Karel K. [EMAIL PROTECTED] wrote:
Hello,
I have tried installing the latest Callweaver, mISDN and SpanDSP(tried
both spandsp-0.0.4pre3 and latest snapshot) version on a Debian 64bit
system.
...
Problem: Any functions producing a sound output eg.
Eugene Prokopiev wrote:
The errors who reported have nothing to do with Callweaver. They are
errors from your iaxmodem/hylafax setup/. These are completely separate
programs, that communication with Callweaver by TCP/IP, and dot not
share any configuration information with it.
I
Hi all,
If anyone has access to the manuals for a TAS240 loop emulator or a TAS
Series 2 Digital network emulator, I'd love to here from you.
Thanks.
Steve
___
Callweaver-users mailing list
Callweaver-users@callweaver.org
Roy Sigurd Karlsbakk wrote:
Den 15.6.2007 kl. 10:44 skrev Thomas Kenyon:
Steve Underwood wrote:
If you wish to discuss activities with a complete disregard for their
legal consequences, would you mind doing it on someone else's
mailing list?
Steve
I think it's a shame that you can't
Thomas Kenyon wrote:
Paulo Scardine wrote:
Thomas Kenyon escreveu:
Is the most simple integration path between callweaver and hylfax, still
the use of the H.323 channel driver and t38modem?
I like IAXModem. In my experience it's very reliable.
It's fantastic, but
Mike Jagdis wrote:
On Mon, May 21, 2007 at 11:12:11PM +0800, Steve Underwood wrote:
That might fix his problem, but why did he got garbage in the strings.
Surely they should be set to something clean.
I _suspect_ the callerid is just never initialised and the channel
drivers
Hi Fred,
Fred wrote:
Hello
I'm looking at the different PBX for Windows available, and was
wondering
if CallWeaver/OpenPBX has been compiled to Windows, or if the code is just
too *nix-specific for this to happen?
Thank you.
As you said, some of the current code is quite
,
Steve
Santiago Ruano Rincón wrote:
On Thu, May 10, 2007 at 09:20:56PM +0800, Steve Underwood wrote:
Hi Alejandro,
I think you have more than one problem there. One appears to be the
inconsistent use of upper and lower case for UniCall in chan_unicall.c.
That used to not matter. Now
64 matches
Mail list logo
