[asterisk-users] Suddenly HDLC Bad FCS (8) errors on ISDN-PRI, changed nothing
Hi fellow asterisk users, I am running Asterisk 1.4.29 with an Digium TE121 card (wcte12xp kernel module) an approx. 100 snom320. The whole installation is running without issues since 5 months. Without having changed anything on the asterisk server for at least 2 months, i noticed clicking sounds at external calls over the PRI. Asterisk constantly throws the following messages: ... [May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [May 31 14:03:37] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 [May 31 14:03:38] NOTICE[4163]: chan_dahdi.c:9078 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 1 ... At first (last week) there where only a few of these messages per minute, but today their intervall inceased dramatically. The clicking also increased. Can this be caused by problems of the telco (Deutsche Telekom)? If so, could anybody please provide some additional information about it? Does anybody have any experiences with this issue? For sake of completeness i have included the relevant .conf files, but i highly doubt it's a configuration issue: --- cat /proc/interrupts CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7 0: 63 0 0 0 0 0 0 1 IO-APIC-edge timer 1: 0 0 0 0 0 0 0 8 IO-APIC-edge i8042 6: 0 0 0 0 0 0 0 2 IO-APIC-edge floppy 7: 1 0 0 0 0 0 0 0 IO-APIC-edge 8: 0 0 0 0 0 0 0 19 IO-APIC-edge rtc0 9: 0 0 0 0 0 0 0 0 IO-APIC-fasteoi acpi 12: 0 0 0 0 0 0 0105 IO-APIC-edge i8042 14: 0 0 0 0 0 0 0 76 IO-APIC-edge ide0 18: 0 0 1 2922 0150 648815 506811268 IO-APIC-fasteoi
Re: [asterisk-users] [SPAM] - Asterisk + Sip Phone + BLF - Email found in subject
... and Snom (370) SIP Phones, but with 2 extensions BLF status does not work correctly. have someone ever tested a Sip Phone with more then 60 BLF without problems? Can someone suggest me model and brand? Thanks, bye. Here at our installation with over 100 snom320 we also encounter problems with extensive usage of the BLF. In particular the receptionist phone which uses multiple lines, appr. 30 BLF and hold+transfer. Unfortunatly i can't suggest any phones, but htere are several things you can do to optimiz the BLF: http://wiki.snom.com/FAQ/When_using_%E2%80%9EExtension_Monitoring/Busy_L amp_Field%E2%80%9C_on_more_than_1_Expansion_Module%2C_the_phone_response _becomes_very_slow. It is also possible to get a firmware which is supposed to fix the BLF issues via the snom support (e.g. snom320-7.3.latest_snapshot_snom-SIP-f.bin for 320's). Perhaps this info can help you a a little. Regards Daniel -- _ -- 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
[asterisk-users] Asterisk 1.6.2.5 crash with chan_capi upon calling to PSTN
Hi,
I am having a problem with (Asterisk is crashing) with a Fritz card PCI
/ chan_capi.
Receiving Calls from PSTN works, but outbound calls make asterisk crash
(Speicherzugriffsfehler/Segmentation fault). The crash occurs upon
dialing with the other phone not even ringing.
I hereby ask if somebody reading this list can confirm or disprove my
issue. Does anbody run a recent asterisk 2.6 with chan_capi?
Config files and backtraces are attached.
Many thanks in advance.
Daniel
Versions:
- Debian 5.0.4 Kernel 2.6.26-2-686
- Asterisk 1.6.2.5 from Digium homepage
- AVM Audiovisuelles MKTG Computer System GmbH A1 ISDN [Fritz] (rev
02)
- fritz-fcpci-src-2.6.24-2.6.28
- chan-capi-trunk (rev. 769)
/etc/asterisk/extensions.conf
-
[default]
exten = 304,1,Dial(SIP/304)
exten = 305,1,Dial(SIP/305)
;To PSTN
exten = _0.,1,Dial(CAPI/ISDN1/${EXTEN})
;From PSTN
[isdn-in]
exten = 1234567,1,Dial(SIP/304)
exten = 1234568,1,Dial(SIP/305)
/etc/asterisk/capi.conf
---
[general]
nationalprefix=0 ; or for example +49
internationalprefix=00 ; or for example +
rxgain=1.0 ;linear receive gain (1.0 = no change)
txgain=1.0 ;linear transmit gain (1.0 = no change)
language=de;set default language
[ISDN1]
isdnmode=msn ;'MSN' (point-to-multipoint,
Mehrgeraeteanschluss) or 'DID' (direct inward dial)
incomingmsn=* ;allow incoming calls to this list of MSNs/DIDs,
* = any
controller=1 ;CAPI controller number of this interface/port
group=1;dialout group
softdtmf=on;enable/disable software DTMF detection,
recommended for AVM cards
relaxdtmf=on ;in addition to softdtmf, you can use relaxed
DTMF detection
faxdetect=off ;enable faxdetection and redirection to EXTEN
'fax' for incoming and/or
faxdetecttime=0;Only detect faxes during the first 'n' seconds
of the call.
context=isdn-in;context for incoming calls
echocancelold=yes ;use facility selector 6 instead of correct 8
(necessary for older eicon drivers)
devices=2 ;number of concurrent calls (B-Channels) on this
controller
Asterisk console output
---
srvpbx:/usr/src/chan-capi-trunk# asterisk -gc Asterisk 1.6.2.5,
Copyright (C) 1999 - 2009 Digium, Inc. and others.
Created by Mark Spencer marks...@digium.com Asterisk comes with
ABSOLUTELY NO WARRANTY; type 'core show warranty' for details.
This is free software, with components licensed under the GNU General
Public License version 2 and other licenses; you are welcome to
redistribute it under certain conditions. Type 'core show license' for
details.
=
[ Booting...
[ Reading Master Configuration ]
[ Initializing Custom Configuration Options ] [Mar 9 10:17:53]
NOTICE[29368]: cdr.c:1473 do_reload: CDR simple logging enabled.
[Mar 9 10:17:53] NOTICE[29368]: loader.c:1044 load_modules: 172 modules
will be loaded.
.[Mar 9 10:17:53] NOTICE[29368]: res_smdi.c:1361 load_module: No
SMDI interfaces are available to listen on, not starting SMDI listener.
[Mar 9 10:17:53] WARNING[29368]:
chan_dahdi.c:17018 process_dahdi: Ignoring any changes to 'userbase' (on
reload) at line 23.
[Mar 9 10:17:53] WARNING[29368]: chan_dahdi.c:17018 process_dahdi:
Ignoring any changes to 'vmsecret' (on reload) at line 31.
[Mar 9 10:17:53] WARNING[29368]: chan_dahdi.c:17018 process_dahdi:
Ignoring any changes to 'hassip' (on reload) at line 35.
[Mar 9 10:17:53] WARNING[29368]: chan_dahdi.c:17018 process_dahdi:
Ignoring any changes to 'hasiax' (on reload) at line 39.
[Mar 9 10:17:53] WARNING[29368]: chan_dahdi.c:17018 process_dahdi:
Ignoring any changes to 'hasmanager' (on reload) at line 47.
[Mar 9 10:17:53] NOTICE[29368]: pbx_ael.c:122
pbx_load_module: Starting AEL load process.
[Mar 9 10:17:53] NOTICE[29368]: pbx_ael.c:135 pbx_load_module: AEL load
process: parsed config file name '/etc/asterisk/extensions.ael'.
[Mar 9 10:17:53] NOTICE[29368]: pbx_ael.c:138 pbx_load_module: AEL load
process: checked config file name '/etc/asterisk/extensions.ael'.
[Mar 9 10:17:53] NOTICE[29368]: pbx_ael.c:141 pbx_load_module: AEL load
process: compiled config file name '/etc/asterisk/extensions.ael'.
[Mar 9 10:17:53] NOTICE[29368]: pbx_ael.c:146 pbx_load_module: AEL load
process: merged config file name '/etc/asterisk/extensions.ael'.
[Mar 9 10:17:53] NOTICE[29368]: pbx_ael.c:149 pbx_load_module: AEL load
process: verified config file name '/etc/asterisk/extensions.ael'.
.[Mar 9 10:17:54] WARNING[29368]: utils.c:1536
__ast_string_field_init: trying to reset empty pool [Mar 9 10:17:54]
WARNING[29368]: utils.c:1536 __ast_string_field_init: trying to reset
empty pool [Mar 9 10:17:54] WARNING[29368]: utils.c:1536
__ast_string_field_init: trying to reset empty pool .[Mar 9
10:17:54] NOTICE[29368]: chan_skinny.c:7062
Re: [asterisk-users] AVM Fritz! mISDN with Kernel 2.6.32 - Any experiences? - Email found in subject - Bayesian Filter detected spam
Hi, I have tried the new revision (769) with Asterisk SVN-trunk-r240667M (~ 1.6.2) and it compiles without warnings or errors (see attached make output). It also seems to work flawlessly. I can make and receive calls from/to the PSTN with the Fritz card PCI via the BRI and route them to my voip Telephones. I will also try faxing, but not today. Many thanks for the great work! Sincerly Daniel Leese --- srvpbx:/usr/src/chan-capi-trunk# make ./create_config.sh /usr/include Checking Asterisk version... SVN-trunk-r240667M * assuming Asterisk version 1.6 Using Asterisk 1.6 API * found new 'ast_dsp_set_digitmode' function * found new union data in ast_frame structure * found new union subclass in ast_frame structure * found ast_channel_release function * found new ast_devstate2str function * found requestor in ast_request * found format_t in ast_request * found const char in ast_register_application * found linkedid in ast_channel_alloc * found format_t in frame_defs * found rtp_engine.h config.h complete. [CC] chan_capi.c - chan_capi.o [CC] chan_capi_utils.c - chan_capi_utils.o [CC] chan_capi_rtp.c - chan_capi_rtp.o [CC] chan_capi_command.c - chan_capi_command.o [CC] xlaw.c - xlaw.o [CC] dlist.c - dlist.o [CC] chan_capi_qsig_core.c - chan_capi_qsig_core.o [CC] chan_capi_qsig_ecma.c - chan_capi_qsig_ecma.o [CC] chan_capi_qsig_asn197ade.c - chan_capi_qsig_asn197ade.o [CC] chan_capi_qsig_asn197no.c - chan_capi_qsig_asn197no.o [CC] chan_capi_supplementary.c - chan_capi_supplementary.o [CC] chan_capi_chat.c - chan_capi_chat.o [CC] libcapi20/convert.c - libcapi20/convert.o [CC] libcapi20/capi20.c - libcapi20/capi20.o [CC] libcapi20/capifunc.c - libcapi20/capifunc.o [LD] chan_capi.so (chan_capi.o chan_capi_utils.o chan_capi_rtp.o chan_capi_command.o xlaw.o dlist.o chan_capi_qsig_core.o chan_capi_qsig_ecma.o chan_capi_qsig_asn197ade.o chan_capi_qsig_asn197no.o chan_capi_supplementary.o chan_capi_chat.o libcapi20/convert.o libcapi20/capi20.o libcapi20/capifunc.o) srvpbx:/usr/src/chan-capi-trunk# chan_capi trunk should be compilable now with current asterisk trunk. Armin On Mon, 1 Mar 2010, Armin Schindler wrote: Hi, it seems that the asterisk API here was changed again and chan_capi must be adapted to this. I will have a look. Armin On Mon, 1 Mar 2010, dle...@lstelcom.com wrote: Hi again! I have excellent success with the tiny fcpci and chan_capi, which is also working great with capi4hylafax. See net-dialup/fcpci-0.1-r1 in gentoo (should not be difficult to use this on other distros, but I have never done so). Do not confuse this with the fritzcapi! I managed to install fcpci and it seems to run fine (capiinfo output). Unfortunately i cant compile chan_capi against my Asterisk trunk r240716. Neither the trunk/head nor the 1.1.4 Version compiles. All fail with the following output: srvpbx:/usr/src/chan-capi-HEAD# make [CC] chan_capi.c - chan_capi.o In file included from chan_capi.c:32: chan_capi.h:34:26: error: asterisk/rtp.h: Datei oder Verzeichnis nicht gefunden chan_capi.c: In function âlocal_queue_frameâ: chan_capi.c:803: error: invalid operands to binary == (have âunion anonymousâ and âintâ) chan_capi.c: In function âinterface_cleanupâ: chan_capi.c:1071: warning: implicit declaration of function âast_rtp_destroyâ chan_capi.c: In function âsend_progressâ: chan_capi.c:1165: error: incompatible types in assignment chan_capi.c: In function âclear_channel_fax_loopâ: chan_capi.c:2884: error: invalid operands to binary == (have âunion anonymousâ and âintâ) chan_capi.c: In function âcapidev_handle_did_digitsâ: chan_capi.c:3548: error: incompatible types in assignment chan_capi.c: In function âcapi_queue_cause_controlâ: chan_capi.c:3564: warning: missing braces around initializer chan_capi.c:3564: warning: (near initialization for âfr.subclassâ) chan_capi.c:3569: error: incompatible types in assignment chan_capi.c:3573: error: incompatible types in assignment chan_capi.c: In function âcapidev_handle_info_indicationâ: chan_capi.c:3876: error: incompatible types in assignment chan_capi.c:3886: error: incompatible types in assignment chan_capi.c: In function âhandle_facility_indication_dtmfâ: chan_capi.c:4138: error: incompatible types in assignment chan_capi.c:4149: error: incompatible types in assignment chan_capi.c: In function âcapidev_handle_data_b3_indicationâ: chan_capi.c:4292: error: incompatible types in assignment chan_capi.c:4294: error: incompatible types in assignment chan_capi.c: In function âcapi_signal_answerâ: chan_capi.c:4316: warning: missing braces around initializer chan_capi.c:4316: warning: (near initialization for âfr.subclassâ) chan_capi.c: In function âcapidev_handle_disconnect_indicationâ: chan_capi.c:4605: warning: missing braces around initializer chan_capi.c:4605: warning: (near initialization for
Re: [asterisk-users] AVM Fritz! mISDN with Kernel 2.6.32 - Any experiences? - Email found in subject
Hi again! I have excellent success with the tiny fcpci and chan_capi, which is also working great with capi4hylafax. See net-dialup/fcpci-0.1-r1 in gentoo (should not be difficult to use this on other distros, but I have never done so). Do not confuse this with the fritzcapi! I managed to install fcpci and it seems to run fine (capiinfo output). Unfortunately i cant compile chan_capi against my Asterisk trunk r240716. Neither the trunk/head nor the 1.1.4 Version compiles. All fail with the following output: srvpbx:/usr/src/chan-capi-HEAD# make [CC] chan_capi.c - chan_capi.o In file included from chan_capi.c:32: chan_capi.h:34:26: error: asterisk/rtp.h: Datei oder Verzeichnis nicht gefunden chan_capi.c: In function âlocal_queue_frameâ: chan_capi.c:803: error: invalid operands to binary == (have âunion anonymousâ and âintâ) chan_capi.c: In function âinterface_cleanupâ: chan_capi.c:1071: warning: implicit declaration of function âast_rtp_destroyâ chan_capi.c: In function âsend_progressâ: chan_capi.c:1165: error: incompatible types in assignment chan_capi.c: In function âclear_channel_fax_loopâ: chan_capi.c:2884: error: invalid operands to binary == (have âunion anonymousâ and âintâ) chan_capi.c: In function âcapidev_handle_did_digitsâ: chan_capi.c:3548: error: incompatible types in assignment chan_capi.c: In function âcapi_queue_cause_controlâ: chan_capi.c:3564: warning: missing braces around initializer chan_capi.c:3564: warning: (near initialization for âfr.subclassâ) chan_capi.c:3569: error: incompatible types in assignment chan_capi.c:3573: error: incompatible types in assignment chan_capi.c: In function âcapidev_handle_info_indicationâ: chan_capi.c:3876: error: incompatible types in assignment chan_capi.c:3886: error: incompatible types in assignment chan_capi.c: In function âhandle_facility_indication_dtmfâ: chan_capi.c:4138: error: incompatible types in assignment chan_capi.c:4149: error: incompatible types in assignment chan_capi.c: In function âcapidev_handle_data_b3_indicationâ: chan_capi.c:4292: error: incompatible types in assignment chan_capi.c:4294: error: incompatible types in assignment chan_capi.c: In function âcapi_signal_answerâ: chan_capi.c:4316: warning: missing braces around initializer chan_capi.c:4316: warning: (near initialization for âfr.subclassâ) chan_capi.c: In function âcapidev_handle_disconnect_indicationâ: chan_capi.c:4605: warning: missing braces around initializer chan_capi.c:4605: warning: (near initialization for âfr.subclassâ) chan_capi.c:4654: error: incompatible types in assignment chan_capi.c: In function âcapidev_handle_connection_confâ: chan_capi.c:5025: warning: missing braces around initializer chan_capi.c:5025: warning: (near initialization for âfr.subclassâ) chan_capi.c: At top level: chan_capi.c:7746: warning: initialization from incompatible pointer type chan_capi.c: In function âconf_interfaceâ: chan_capi.c:8153: warning: passing argument 2 of âast_parse_allow_disallowâ from incompatible pointer type chan_capi.c:8156: warning: passing argument 2 of âast_parse_allow_disallowâ from incompatible pointer type make: *** [chan_capi.o] Fehler 1 Please excuse the messed up german output, i have yet to discover how to set a debian box to german keyboard, everything else english. I am limited to Asterisk trunk r240716 because i want to evaluate the T.38 - T.30 gateway function, which can only be patched into this revision. In my opinion there are the following alternatives in order to get the Fritz card running with Asterisk: A) Get chan-capi to compile: Unfortunately my C knowledge seems insufficent for this. I have found out that there is noch rtp.h in the asterisk source dir, only a file named rtp_engine.h. Changing the include accordingly unfortunately only fixes the very first error. I can't make any sense out of the second error (error: invalid operands to binary == (have union anonymous and int)), as, in line 803, the left-hand operand of the == is no union, let alone a anonymous union. I have already posted this at the chan-capi-users ML, but with no answer so far. B) Use a binary chan_capi.so from elsewhere?! I run Debian 5.0.2 Kernel 2.6.26-2-686. Could i take a compiled chan_capi.so from a machine with a different Asterisk 1.6 Version? C) Find another way to use fcpci eith Asterisk. Is this even possible? With mISDN? ...? Comments or any other Ideas are very appreciated. Sincerly Daniel Leese P.s.: Philipp, many thanks fo your answers so far ;) -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] AVM Fritz! mISDN with Kernel 2.6.32 - Any experiences?
Hi to all asterisk-users ;) As some of you may know, Kernel 2.6.32 includes a module for the infamous Fritz passive ISDN cards in conjunction with mISDN. I just would like to know if anybody has tried to use a Fritz card as a BRI adapter for Asterisk with the new module. If so, i would be grateful for some hints or howtos. I am willing to try this myself, but i am quite reluctant as i have wasted weeks with Fritz cards over the last decade, most of the time without any success. Any help is appreciated. Regards Daniel Leese -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] [SPAM] - Re: Asterisk t38modem Fax gateway evaluation - Email found in subject
Hi, Many thanks Steve and Philipp for your input. I am compiling Asterisk 1.6 svn version right now and will try to integrate the T.38 Gateway patches mentioned at https://issues.asterisk.org/view.php?id=13405 (I have some Linux coding experience, but unfortunately my telecommunication knowledge is severly lacking). The ISDN PRI - Analogue Converter solution mentioned by Philipp is impractical for my situation as the hub of the 2-wire POTS lines is not in the same Building as the PRI. I will let you her if my research bears some practical results, as this seems to be something not very well established/documented. Daniel -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] Asterisk t38modem Fax gateway evaluation
Hi, I am trying to fix a Asterisk setup with buggy (POTS) Fax machines. The setup consists of the following components: - A Digium TE121 for connectiong to E1 ISDN - Debian box with Asterisk 1.4 - Grandstream GXW-4008 SIP ATA to which the Fax machines connect I am aware of the problems with this type of ISDN - Asterisk - SIP ATA - Fax machine installations, e.G. different clock source of ISDN and the ATA, ethernet timing issues, etc. So it's no suprise that i encounter the usual problems: No reliable transmission of faxes, errors and aborts with multiple page faxes, ... Unfortunately the installtion is allready completed and purchasing new hardware is not an option. Thus i have come up with the following idea und need some small pointer if this is even possible: remote =whatever= PSTN =ISDN= Digium -- Asterisk -- t38modem =Ethernet= Grandstream =POTS= local FAXE1 TE1211.4 SIP GXW-4008FAX machine t38 Is it possible to decouple the internal Fax communication from ISDN using t38modem or as an alternative Fax For Asterisk, perhaps in conjunction with HylaFAX? I was unable to find any current information about theese subjects on the www. Most postings/articles are 4-6 years old and state that it's impossible, but this was way before t38modem and Fax for Asterisk. I would be really grateful if anybody could come up with some current information, howtows, etc. Many thanks in advance Daniel Leese -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
