similar to: SpanDSP Scrunching incoming faxes

Displaying 20 results from an estimated 1000 matches similar to: "SpanDSP Scrunching incoming faxes"

2004 Jun 19
1
RxFax problems
Hey All, I'm still (since April) having problems getting RxFax to work over an ISDN4Linux channel. Just wondering if anyone has had any luck getting it to work? I have done a CVS update today (about half hour ago) and made sure I have the latest version of spandsp according to Steve's website (spandsp-0.0.1k). When I was compiling asterisk, I got the following warnings:
2004 Jun 18
0
Problems reciving fax with Asterisk
Hi, I am trying to recice a fax with * using SpanDSP - but it doesn't create the output file. (See the bottom of log file). * Loads both app_rxfax.so and app_txfax.so fine. Also I can't make * autodetect an incomming fax call (yes I have enabled faxdetect=both in zapata.conf - though it's not a Zap device) Any ideas are welcome :-) Best Regards Michael L?jtnant System Details:
2004 Aug 26
0
Out Dial Problem
Dear All, I just setup the Asterisk with E100P which it's no problem in Dial In but I have problem when outdial. The connection method is like this : E1 PRI <-SIGNAL-1-> MaxLink (PBX) <-SIGNAL-2-> E100P <-> Asterisk <--> SIP \-----> Analog PHone Now when I tried to dial out by SIP X-Lite on Windows, it shows me Connect, Trying,
2004 Sep 21
0
more on spandsp and partially received fax
more detailed output Sep 21 15:54:31 DEBUG[1120357296]: pbx.c:1255 pbx_extension_helper: Launching 'RxFAX' Sep 21 15:54:31 DEBUG[1120357296]: channel.c:1699 ast_set_read_format: Set channel Zap/1-1 to read format SLINR Sep 21 15:54:31 DEBUG[1120357296]: channel.c:1666 ast_set_write_format: Set channel Zap/1-1 to write format SLINR Changed from phase 0 to 1 Slow carrier up Slow carrier
2005 Oct 14
3
Problem with compiling spandsp
New asterisk user, pretty much set up except for spandsp. I get the following when trying to compile: app_rxfax.c app_rxfax.c: In function `phase_e_handler': app_rxfax.c:92: error: structure has no member named `cid' app_rxfax.c:92: error: structure has no member named `cid' app_rxfax.c: In function `rxfax_exec': app_rxfax.c:260: error: structure has no
2005 Aug 08
0
Asterisk-to-IVR Problem
This was submitted to the Dev list last week, but there was no response, and perhaps it wasn't the right group. I am developing an application in which I need asterisk to pass on an incoming call to a separate IVR server. The problem is that asterisk appears to hang up while the IVR is playing back a sequence of recorded voice and systhesized voice prompts. My setup is: Analog line
2003 Nov 18
3
"Unable to find path from G729A to ULAW" on Sipphone.com
I seem to be having a problem with transcoding and/or agreeing on a valid codec. I am running a new image pulled from CVS at 1:30 PM CST. The issue occurs when I try to make a call to a toll-free number over sipphone.com. Here's what I see in the console: NOTICE[1259545280]: File channel.c, Line 1478 (ast_set_read_format): Unable to find a path from G729A to ULAW NOTICE[1259545280]: File
2005 Jan 11
1
rxfax troubles..
what is g723? ive never seen that before... -- Executing Answer("Zap/1-1", "") in new stack -- Accepting call from '2819870065' to '2815692780' on channel 0/1, span 1 -- Executing Wait("Zap/1-1", "1") in new stack -- Executing SetVar("Zap/1-1", "FAXFILE=/var/spool/asterisk/fax/1105486770.492.tif") in new stack --
2004 Jul 13
1
codec issues between linphone and *
Hello I am trying to connect linphone 0.12.2 to an * 0.9.1 box over a LAN using the console version of linphone. both boxs are using the latest alsa drivers on a LFS kernal 2.4. I am running into errors with codec compatability between linphone and *. A point to note is that I am able to connect to asterisk using other sip phones noteably sjphone however linephone is giving me
2003 Sep 26
0
Unable to find a path from ULAW to G723
Hello, I just CVS'd today and now I'm getting these errors when I call one grandstream phone to another both using 711U: NOTICE[1225991360]: File channel.c, Line 1476 (ast_set_read_format): Unable to find a path from ULAW to G723 NOTICE[1225991360]: File channel.c, Line 1446 (ast_set_write_format): Unable to find a path from G723 to ULAW NOTICE[1225991360]: File channel.c, Line 1476
2004 Aug 03
0
avm c4: DISCONNECT_IND ID=001 #0x0193 LEN=0014
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 i fixed wrong capi.conf (there was [controller1] after [interfaces]) now capi.conf is: ; ; CAPI config ; [general] nationalprefix=0 internationalprefix=00 rxgain=0.8 txgain=0.8 [interfaces] msn=855285,859609 incomingmsn=* controller=1,2,3,4 softdtmf=0 accountcode= context=local ;echosquelch=1 ;echocancel=yes ;echotail=64 ;callgroup=1
2005 Feb 08
0
Codec negotiation problems
My PBX seems to have just started showing wierd codec negotiation problems. I'm not all of a sudden getting this on certain phone numbers on my system: Feb 8 22:19:19 NOTICE[1125329728]: channel.c:1683 ast_set_read_format: Unable to find a path from ULAW to G729A Feb 8 22:19:19 NOTICE[1125329728]: channel.c:1650 ast_set_write_format: Unable to find a path from G729A to ULAW --
2005 Oct 03
1
Compiling SpanDSP
Has anybody been successful with compiling the pre3 version of SpanDSP on the current Asterisk CVS? I'm getting: app_rxfax.c: In function `phase_e_handler': app_rxfax.c:77: warning: implicit declaration of function `fax_get_transfer_statistics' app_rxfax.c:78: warning: implicit declaration of function `fax_get_far_ident' app_rxfax.c:79: warning: implicit declaration of
2006 Jan 04
2
suddenly iax calls don't work anymore
Hi, Asterisk is new for me. I had a working configuration, but suddenly I can't call anymore with my voip provider. I am not aware that I changed anything in the configuration, but who knows. Can somebody explain me what is happening here? I changed username, password and number. -- Executing Dial("Zap/2-1",
2005 Aug 12
0
txfax spandsp
I've been using spandsp and rxfax to receive faxes for a while now and over the past few days I've looked into the other side of things - txfax. I can't seem to get it working properly. I've included debug logs below of both the tx and rx side of things. I've tried three different servers, asterisk v1.0.6, 1.0.9 and CVS, FC2 and FC4, libtiff 3.5.7 and 3.7.1, TE405P and
2005 Aug 02
0
app_rxfax errors
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Up until today, I have had no issues with receiving faxes in *. One change I made was that I now have the incoming
2004 Jun 28
2
sip to isdn-capi call problem
anyone has idea what problem can be here, something with codec but i have today CVS version and grandstream phone with 1.5.0 firmware.I try to change codec in phone and also in asterisk-sip.conf but the same. What can be problem ? tnx, Tomaz *CLI> -- Executing Dial("SIP/102-767c", "CAPI/2:5") in new stack -- Called 2:5 -- CAPI[contr1/2003002]/0 is making
2004 Dec 22
2
txfax failure
Hi list, Just installed spandsp. In my limiting testing, I have an issue on a Philips fax machine (HFC21) directly connected to my * server through TDM400, reception with rxfax works fine, but txfax always fails. Below is a transcript of failed transmit. This is with asterisk-1.0.3 (with native moh patch but I don't think it is the source of the problem). I already tried libtiff 3.5.7,
2005 Jan 24
2
Inbound Errors
Whenever I take an inbound call I am getting the following errors: NOTICE[4719]: channel.c:1698 ast_set_write_format: Unable to find a path from speex to gsm NOTICE[4719]: channel.c:1731 ast_set_read_format: Unable to find a path from gsm to speex What typically generates this issue? ~Dan
2003 Apr 23
5
Unable to call H323 phones via asterisk
I receive the following error when I try to call another H323 extension from another H323 when going through *. NOTICE[27669]: File channel.c, Line 1325 (ast_set_read_format): Unable to find a path from 1 to 8 NOTICE[27669]: File channel.c, Line 1296 (ast_set_write_format): Unable to find a path from 8 to 1 WARNING[27669]: File chan_h323.c, Line 528 (oh323_write): Asked to transmit frame type 1,