search for: hardhdlc

...etect stuff for this ; ;faxdetect=both ;faxdetect=incoming ;faxdetect=outgoing ;faxdetect=no group=1 signalling=bri_cpe context=isdn channel => 1,2,4,5,7,8,10,11,13,14,16,17,19,20,22,23 SrvPhone2:/etc/dahdi# cat system.conf loadzone = be defaultzone = be span = 1,1,0,ccs,ami bchan = 1,2 hardhdlc = 3 span = 2,2,0,ccs,ami bchan = 4,5 hardhdlc = 6 span = 3,3,0,ccs,ami bchan = 7,8 hardhdlc = 9 span = 4,4,0,ccs,ami bchan = 10,11 hardhdlc = 12 span = 5,5,0,ccs,ami bchan = 13,14 hardhdlc=15 span = 6,6,0,ccs,ami bchan = 16,17 hardhdlc = 18 span = 7,7,0,ccs,ami bchan = 19,20 hardhdlc = 21 sp...

...nel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 2" This happens on a regular basis and the E1 becomes up after some time. My zaptel.conf is as follows: # Span 1: TE4/0/1 "T4XXP (PCI) Card 0 Span 1" (MASTER) span=1,1,0,ccs,hdb3 # termtype: te bchan=1-15,17-31 hardhdlc=16 # Span 2: TE4/0/2 "T4XXP (PCI) Card 0 Span 2" span=2,2,0,ccs,hdb3 # termtype: te bchan=32-46,48-62 hardhdlc=47 # Span 3: TE4/0/3 "T4XXP (PCI) Card 0 Span 3" span=3,3,0,ccs,hdb3 # termtype: te bchan=63-77,79-93 hardhdlc=78 # Span 4: TE4/0/4 "T4XXP (PCI) Card 0 Span 4&q...

...are not being used. Follows my config files (snipped to the relevant portions, because most are really big) and some other related info. Any hints on how to solve this will be really really appreciated. /etc/dahdi/system.conf: loadzone=br defaultzone=br span=1,1,0,ccs,hdb3,crc4 bchan=1-15,17-31 hardhdlc=16 span=2,0,0,ccs,hdb3,crc4 bchan=32-46,48-62 hardhdlc=47 span=3,0,0,ccs,hdb3,crc4 bchan=63-77,79-93 hardhdlc=78 span=4,0,0,ccs,hdb3,crc4 bchan=94-108,110-124 hardhdlc=109 echocanceller=oslec,125-162 echocanceller=oslec,163-200 echocanceller=oslec,201-238 echocanceller=oslec,239-254 fxoks=125-...

...fr channel => 8-9 ;; Span 4: B4/0/3 "B4XXP (PCI) Card 0 Span 3" signalling=bri_cpe callerid=asreceived group=7 context=trunk_9_0 language=fr channel => 11-12 /etc/dahdi/system.conf # Span 2: B4/0/1 "B4XXP (PCI) Card 0 Span 1" span=2,1,0,ccs,ami # termtype: te bchan=5-6 hardhdlc=7 echocanceller=mg2,5-6 # Span 3: B4/0/2 "B4XXP (PCI) Card 0 Span 2" span=3,2,0,ccs,ami # termtype: te bchan=8-9 hardhdlc=10 echocanceller=mg2,8-9 # Span 4: B4/0/3 "B4XXP (PCI) Card 0 Span 3" span=4,3,0,ccs,ami # termtype: te bchan=11-12 hardhdlc=13 echocanceller=mg2,11-12 #...

Hi, I'm experiencing difficulties to get a B410P running with Asterisk 10.3.1 and DAHDI 2.6.1. Am I supposed to use DAHDI for this card and ISDN BRI for my country (Belgium)? thx, BC

Hey Guys! Please help me to find out issue. I have two PRI ## Span 1: WPT1/0 "wanpipe1 card 0" span=1,1,0,esf,b8zs bchan=1-23 hardhdlc=24 echocanceller=mg2,1-23 ## Span 2: WPT1/1 "wanpipe2 card 1" span=2,2,0,esf,b8zs bchan=25-47 hardhdlc=48 echocanceller=mg2,25-47 Sometime my calls got through but some time i am getting pri cause 44 sebpbx1*CLI> == Using SIP RTP CoS mark 5 -- Executing [6463279153 at from-s...

...: 1 TEI=0 Sending SABME PRI Span: 1 Changing from state 4(TEI assigned) to 5(Awaiting establishment) PRI Span: 1 TEI=0 Sending SABME Below you can find the /etc/dahdi/system.conf # Span 1: B4/0/1 "B4XXP (PCI) Card 0 Span 1" (MASTER) AMI/CCS RED span=1,0,0,ccs,ami # termtype: nt bchan=1-2 hardhdlc=3 echocanceller=mg2,1-2 # Span 2: B4/0/2 "B4XXP (PCI) Card 0 Span 2" AMI/CCS RED span=2,0,0,ccs,ami # termtype: nt bchan=4-5 hardhdlc=6 echocanceller=mg2,4-5 # Span 3: B4/0/3 "B4XXP (PCI) Card 0 Span 3" AMI/CCS RED span=3,1,0,ccs,ami # termtype: te bchan=7-8 hardhdlc=9 echocan...

...If you edit this file and execute /usr/sbin/dahdi_genconf again, # your manual changes will be LOST. # Dahdi Configuration File # # This file is parsed by the Dahdi Configurator, dahdi_cfg # # Span 1: B4/0/1 "B4XXP (PCI) Card 0 Span 1" (MASTER) span=1,1,0,ccs,ami # termtype: te bchan=1-2 hardhdlc=3 echocanceller=mg2,1-2 # Span 2: B4/0/2 "B4XXP (PCI) Card 0 Span 2" RED span=2,2,0,ccs,ami # termtype: te bchan=4-5 hardhdlc=6 echocanceller=mg2,4-5 # Span 3: B4/0/3 "B4XXP (PCI) Card 0 Span 3" RED span=3,3,0,ccs,ami # termtype: te bchan=7-8 hardhdlc=9 echocanceller=mg2,7-8 # S...

...# Autogenerated by /usr/sbin/genzaptelconf -- do not hand edit # Zaptel Configuration File # # This file is parsed by the Zaptel Configurator, ztcfg # # It must be in the module loading order # Span 1: TE2/0/1 "T2XXP (PCI) Card 0 Span 1" (MASTER) span=1,0,0,ccs,hdb3,crc4 bchan=1-15,17-31 hardhdlc=16 # Span 2: TE2/0/2 "T2XXP (PCI) Card 0 Span 2" span=2,0,0,ccs,hdb3,crc4 bchan=32-46,48-62 hardhdlc=47 # Global data loadzone = es defaultzone = es ##extensions.conf########################################### exten =>999888777,1,Goto(JUMP,s,1) [JUMP] exten => s,1,D...

hello: thanks for Tzafrir Cohen for dahdi testing. I installed dahdi-2.1-r3c svn code and asterisk1-6 for testing OpenVox B400P and junghans card. i fund that there is bug (i think) to dectect NT or TE mode. actually on the board, i set it as TE mode, but after start wcb4xxp, but it show the port is NT mode. to detect the TE mode, I modefy the code in base.c

...=yes transfer=yes canpark=yes cancallforward=yes callreturn=yes callgroup=1 pickupgroup=1 immediate=no overlapdial=yes progzone=uk resetinterval=43200 group=1 channel => 1-15 channel => 17-31 Here is my /etc/zaptel.conf :- loadzone=us defaultzone=us span=1,0,0,ccs,hdb3,crc4 bchan=1-15,17-31 hardhdlc=16 span=2,0,0,ccs,hdb3,crc4 bchan=32-46,48-62 hardhdlc=47 The second span is not used and just has a loopback plug connected. Could anyone advise me what the error message means? Thanks Ben Thompson

How can we set the CDR Master file to rollover at say 30 Meg and create a new one -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100827/2e98385f/attachment.htm

...GNORE_FRONT_END = NO TDMV_SPAN = 3 TDMV_DCHAN = 0 TDMV_HW_DTMF = NO [w3g1] ACTIVE_CH = ALL TDMV_ECHO_OFF = NO TDMV_HWEC = YES zaptel.conf: loadzone=uk defaultzone=uk #Sangoma A104 port 1 [slot:1 bus:16 span:1] <wanpipe1> span=1,0,0,ccs,hdb3,crc4 bchan=1-15,17-31 hardhdlc=16 #Sangoma A104 port 2 [slot:1 bus:16 span:2] <wanpipe2> span=2,0,0,ccs,hdb3,crc4 bchan=32-46,48-62 hardhdlc=47 #Sangoma A104 port 3 [slot:1 bus:16 span:3] <wanpipe3> span=3,0,0,ccs,hdb3,crc4 bchan=63-77,79-93 dchan=78 #Sangoma A104 port 4 [slot:1 bus:16 span:4] <wanpipe4> spa...

...99-533 feet (DSX-1) coding_opts=B8ZS,AMI,HDB3 framing_opts=ESF,D4,CCS,CRC4 coding=AMI framing=CCS ------------------------------------------------------------- /etc/dahdi/system.conf loadzone=uk defaultzone=uk span=1,1,3,ccs,ami span=2,2,3,ccs,ami span=3,3,3,ccs,ami span=4,4,3,ccs,ami bchan=1,2 hardhdlc=3 bchan=4,5 hardhdlc=6 bchan=7,8 hardhdlc=9 bchan=10,11 hardhdlc=12 echocanceller=oslec,1,2,4,5,7,8,10,11 ---------------------------------------------------------------- /etc/asterisk/dahdi-channels.conf ; Span 1: B4/0/1 "B4XXP (PCI) Card 0 Span 1" (MASTER) AMI/CCS RED group=0,11...

...If you edit this file and execute /usr/sbin/dahdi_genconf again, # your manual changes will be LOST. # Dahdi Configuration File # # This file is parsed by the Dahdi Configurator, dahdi_cfg # # Span 1: B4/0/1 "B4XXP (PCI) Card 0 Span 1" (MASTER) span=1,1,0,ccs,ami # termtype: te bchan=1-2 hardhdlc=3 echocanceller=mg2,1-2 # Span 2: B4/0/2 "B4XXP (PCI) Card 0 Span 2" RED span=2,2,0,ccs,ami # termtype: te bchan=4-5 hardhdlc=6 echocanceller=mg2,4-5 # Span 3: B4/0/3 "B4XXP (PCI) Card 0 Span 3" RED span=3,3,0,ccs,ami # termtype: te bchan=7-8 hardhdlc=9 echocanceller=mg2,7-8 # S...

...t 1 [slot:5 bus:3 span:1] <wanpipe1> switchtype=euroisdn echocancel=yes signalling=pri_cpe channel =>1-15,17-31 /etc/dahdi/system.conf: # Span 1: WPE1/0 "wanpipe1 card 0" (MASTER) HDB3/CCS/CRC4 span=1,1,0,ccs,hdb3,crc4 # termtype: te bchan=1-15,17-31 echocanceller=mg2,1-15,17-31 hardhdlc=16 # Global data loadzone = de defaultzone = de Any hints? Thanks! Regards, Bjoern

...ncfg_dahdi do not hand edit #autogenrated on 2010-12-08 #Dahdi Channels Configurations #For detailed Dahdi options, view /etc/dahdi/system.conf.bak loadzone=us defaultzone=us #Sangoma A104 port 1 [slot:2 bus:2 span:1] <wanpipe1> span=1,1,0,esf,b8zs bchan=1-23 #dchan=24 echocanceller=mg2,1-23 hardhdlc=24 And, from chan_dahdi.conf: ;Sangoma A104 port 1 [slot:2 bus:2 span:1] <wanpipe1> switchtype=national context=ldrouted group=1 echocancel=yes signalling=pri_net channel =>1-23 Any thoughts, pointers, suggestions? The echo is horrible, please help me make it stop. :-) --Tim

...edit this file and execute /usr/sbin/dahdi_genconf again, # your manual changes will be LOST. # Dahdi Configuration File # # This file is parsed by the Dahdi Configurator, dahdi_cfg # # Span 1: B4/0/1 "B4XXP (PCI) Card 0 Span 1" (MASTER) AMI/ccs span=1,1,0,ccs,ami # termtype: te bchan=1-2 hardhdlc=3 echocanceller=mg2,1-2 # Span 2: B4/0/2 "B4XXP (PCI) Card 0 Span 2" AMI/ccs span=2,2,0,ccs,ami # termtype: te bchan=4-5 hardhdlc=6 echocanceller=mg2,4-5 # Span 3: B4/0/3 "B4XXP (PCI) Card 0 Span 3" AMI/ccs RED span=3,3,0,ccs,ami # termtype: te bchan=7-8 hardhdlc=9 echocancell...

...i_termtype SPAN/1 TE SPAN/2 TE SPAN/3 NT SPAN/4 NT # dahdi_genconf system # dahdi_genconf # cat /etc/dahdi/system.conf ... # Span 2: B4/0/2 "B4XXP (PCI) Card 0 Span 2" AMI/CCS span=2,2,0,ccs,ami # termtype: te bchan=4-5 hardhdlc=6 echocanceller=oslec,4-5 # Span 3: B4/0/3 "B4XXP (PCI) Card 0 Span 3" AMI/CCS span=3,3,0,ccs,ami # termtype: te bchan=7-8 hardhdlc=9 echocanceller=oslec,7-8 # cat /etc/asterisk/dahdi-channels.conf ... ; Span 2: B4/0/2 "B4XXP (PCI) Card 0 Span 2" AMI/CCS group=1,12 context=re...

...rom the box in question, but essentially it showed the same as above with "T1" in the second column for all channels instead of "PRI". They both had identical system.conf, which looks like this: loadzone=us defaultzone=us span=1,1,0,esf,b8zs bchan=1-23 echocanceller=mg2,1-23 hardhdlc=24 In fact the *only* things I changed from the old system.conf tonight was swapping "e&m=1-24" for "bchan=1-23" and adding the "hardhdlc=24". The old (now functioning) system.conf looks like this: # Span 1: XBUS-00/XPD-00 "Xorcom XPD [usb:X1067719].1: T1...