search for: fcshdlc

...annels are treated individually and # are not bundled. "bchan" is an alias for this. # "rawhdlc" : The zaptel driver performs HDLC encoding and decoding on the # bundle, and the resulting data is communicated via the master # device. # "fcshdlc" : The zapdel driver performs HDLC encoding and decoding on the # bundle and also performs incoming and outgoing FCS insertion # and verification. "dchan" is an alias for this. # "nethdlc" : The zaptel driver bundles the channels together into an #...

...annels are treated individually and # are not bundled. "bchan" is an alias for this. # "rawhdlc" : The zaptel driver performs HDLC encoding and decoding on the # bundle, and the resulting data is communicated via the master # device. # "fcshdlc" : The zapdel driver performs HDLC encoding and decoding on the # bundle and also performs incoming and outgoing FCS insertion # and verification. "dchan" is an alias for this. # "nethdlc" : The zaptel driver bundles the channels together into an #...

Hey all, I had a user complaining of calls which were dropping mid-conversation. I looked into the time of one of the calls, and saw the following: Apr 4 12:13:03 WARNING[6670] chan_zap.c: No D-channels available! Using Primary channel 28 as D-channel anyway! Apr 4 12:13:05 WARNING[6660] channel.c: Avoided initial deadlock for '0x82b8430', 10 retries! Apr 4 12:13:05 WARNING[6660]

...ls are treated individually and # are not bundled. "bchan" is an alias for this. # "rawhdlc" : The zaptel driver performs HDLC encoding and decoding on the # bundle, and the resulting data is communicated via the master # device. # "fcshdlc" : The zapdel driver performs HDLC encoding and decoding on the # bundle and also performs incoming and outgoing FCS insertion # and verification. "dchan" is an alias for this. # "nethdlc" : The zaptel driver bundles the channels together into an...

...hannels are treated individually and # are not bundled. "bchan" is an alias for this. # "rawhdlc" : The zaptel driver performs HDLC encoding and decoding on the # bundle, and the resulting data is communicated via the master # device. # "fcshdlc" : The zapdel driver performs HDLC encoding and decoding on the # bundle and also performs incoming and outgoing FCS insertion # and verification. "dchan" is an alias for this. # "nethdlc" : The zaptel driver bundles the channels together into an #...

...ls are treated individually and # are not bundled. "bchan" is an alias for this. # "rawhdlc" : The zaptel driver performs HDLC encoding and decoding on the # bundle, and the resulting data is communicated via the master # device. # "fcshdlc" : The zapdel driver performs HDLC encoding and decoding on the # bundle and also performs incoming and outgoing FCS insertion # and verification. "dchan" is an alias for this. # "nethdlc" : The zaptel driver bundles the channels together into an...

Hi, all I have installed TDM400 with 1 FXS and 1 FXP ports. Now I am goig through documentation on how to configure it. It mentions 3 protocols: Loopstart, Groundstart and Koolstart. Which one do I use? Can someone send me sample zaptel.conf file for Australia? This will save me some time and will be used as a working example. Thanks, Rudolf

Hi all, On an Asterisk/Zaptel 1.4 system, one way to gather diagnostic info is: ~# cat /proc/zaptel/* Span 1: ZTHFC1 "HFC-S PCI A Zaptel Driver card 0 [TE]" (MASTER) AMI/CCS 1 ZTHFC1/0/1 Clear (In use) 2 ZTHFC1/0/2 Clear (In use) 3 ZTHFC1/0/3 HDLCFCS (In use) Span 2: ZTHFC2 "HFC-S PCI A Zaptel Driver card 1 [TE]" AMI/CCS 4 ZTHFC2/0/1 Clear 5 ZTHFC2/0/2

...annels are treated individually and # are not bundled. "bchan" is an alias for this. # "rawhdlc" : The zaptel driver performs HDLC encoding and decoding on the # bundle, and the resulting data is communicated via the master # device. # "fcshdlc" : The zapdel driver performs HDLC encoding and decoding on the # bundle and also performs incoming and outgoing FCS insertion # and verification. "dchan" is an alias for this. # "nethdlc" : The zaptel driver bundles the channels together into an #...

...s to what's wrong, as I didn't change anything on the ISDN side compared to my very stable etch setup: same HFC-S card working in TE-mode, same bri_cpe_ptmp signalling, same NT1, I even reused the same cable. I tried the force_l1_up=1 kmod parameter, without seeing any change. I tried using fcshdlc instead of hardhdlc with no luck. I even swapped the NT1 with a new one, also without result. Any pointers on how to debug this TEI assignment problem are welcome. I have an plain ISDN phone that's also connected to the NT1's S-bus which works fine. I can swap the cables between the phone...

...------- zaptel.conf -------------------------------- #setari generale loadzone=us defaultzone=us #TDM2400P - 16 porturi FXS + 8 porturi FXO fxoks=1-16 fxsks=17-24 #TDM2400P - 24 porturi FXS fxoks=25-48 #TE110P - 30 canale ISDN - MEDIASAT(momentan) span=3,1,0,ccs,hdb3,crc4 indclear=49-63,65-79 fcshdlc=64 #TDM400P - 4 porturi FXO fxsks=80-83 ----------------------------- extensions.conf ----------------------------- [macro-faxreceive] exten => s,1,SetVar(FAXFILE=/var/spool/asterisk/fax/${CALLEDFAX}/${UNIQUEID}) exten => s,2,rxfax(${FAXFILE}.tif) [macro-stdexten] ;exten => s,1,Dial(...