similar to: ISDN config: LBO values

I'm working on an Asterisk system with all of it's PRI ports configured with the LBO setting at 5, like this: span=3,0,5,esf,b8zs As of yet, I am unwilling to change the LBO to 0 to where it probably should be because the system is working and I'm not sure exactly what the LBO does. I'm aware some changes were made to deal with low audio levels. Does anybody know what audio

I have a box with 12 T1s (4 Te410P cards). The PSTN provider is reporting slips and ask me to update the clock source. I have my system.conf set as the following but when I run dahdi_scan only the ports on Card 1 are showing up with syncsrc=1 system.conf : span=1,1,0,esf,b8zs bchan=2-24 mtp2=1 span=2,2,0,esf,b8zs bchan=26-48 mtp2=25 span=3,3,0,esf,b8zs bchan=49-72

Can someone who is knowledgable in the traditional telco space please give me a layman's explanation (or point me to an appropriate url) of LBO as per the zaptel configuration file? # The line build-out (or LBO) is an integer, from the following table: # 0: 0 db (CSU) / 0-133 feet (DSX-1) # 1: 133-266 feet (DSX-1) # 2: 266-399 feet (DSX-1) # 3: 399-533 feet (DSX-1) # 4: 533-655 feet (DSX-1)

Hi all, anyone could pls explain me what does it means ? It a part of zaptel.conf file. LBO= Line Build Out 0: 0 dB (CSU) / 0 - 133 feet (DSX-1) 1: 133 - 266 feet (DSX-1) 2: 266 - 299 feet (DSX-1) 3: 399 - 533 feet (DSX-1) 4: 533 - 655 feet (DSX-1) 5: -7.5 dB (CSU) 6: -15 dB (CSU) 7: -22.5 dB (CSU) Thanks Giordano -- No virus found in this outgoing message. Checked by AVG

Hello! I am trying to configure my digium TE220 dual-span pci express card with Dahdi. I seemed to have managed to set up the card with the Dahdi kernel, as demonstrated by executing dahdi_scan: [1] active=yes alarms=RED description=T2XXP (PCI) Card 0 Span 1 name=TE2/0/1 manufacturer=Digium devicetype=Wildcard TE220 (4th Gen) location=Board ID Switch 0 basechan=1 totchans=31 irq=16

Hi, I have 2 servers: one is running 2 B410P cards with 8 euroisdn lines (mISDN) connected on it, everything runs fine. I prepare a new server - HP 360 G8- with 2 HA8 cards each of them 1 module of 4 lines. Already had with this machine an RMA on both cards as they was faulty and crashed the server. What happends is that when I connect cables on the HA8 modules (those cables are unpluged

Hi all, My problem boils down to these errors: ... Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) == Everyone is busy/congested at this time This is triggered by lines in extentions.conf such as: exten => _X.,1,Dial(ZAP/g1/${EXTEN},,W) The system is CentOS v5.2 with Asterisk 1.4.23 (druid-asterisk-1.4.23.1-2), a Sangoma A104

Hello List, Im just dipping my feet into the asterisk world, and im having major fxo problems Im running Asterisk (from svn) + libpri (from svn) + asterisk-addons (from svn) + asterisk gui (svn 1.4 branch) + zaptel (svn 1.4) on a Debian Etch box, with 1gb ram, running all of the services for my home server (web / db / music server etc), and i would like to run my PSTN line from Kingston Comms,

Still trying to upgrade to 1.6.0.9 for 1.4. It worked - it worked all day yesterday, but this morning: -- Executing [646xxxyyyy at longdistance:1] Answer("SIP/172-08276a60", "") in new stack .......... -- Executing [646xxxyyy at longdistance:6] Dial("SIP/172-08276a60", ""DAHDI/g2"/1646xxxyyyy") in new stack May 27 09:56:57]

Hi, On a (bogus) system equiped with a Digium HA8 and 8 BRI ports, I'm reading this: # asterisk -rx "dahdi show status" Description Alarms IRQ bpviol CRC4 Fra Codi Options LBO HA8-0000 RED 109 0 0 CCS AMI YEL 0 db (CSU)/0-133 feet (DSX-1) HA8-0000 UNCONFI 109 0

HelloI have the following system Asterisk 1.6.1dahdi 2.2.0.2 TE420P card Centos I have noticed that all the four lights are blinking(ie coming red and then off so on)... Previously I also noted that when dahdi drivers are not installed lights blink but one by one in sequence(like in marriage cermonies :P) and after dahdi installation lights get off ... but this time all at same time

I've spent a week playing with Asterisk 1.6 and I love it. What a brilliant piece of software! Progress and learning have been reasonably good. I have external SIP provider calls coming in and have put together a little call platform and I'm stunned at the flexibility. There is one issue for me. I took me a while to click that ZAPTEL now equals Dahdi, but now I'm there I have an

I am having a problem with a new PRI turn-up on dahdi 2.5.0 and asterisk 1.8.5 that I have not seen before. The PRI is setup as B8ZS, ESF and the span shows up and ok. This PRI is merely a crossover T1 going into an old DC0 class 5 switch. I am getting the following errors over and over again [Aug 16 10:26:10] NOTICE[8002]: chan_dahdi.c:3043 my_handle_dchan_exception: PRI got event: HDLC Bad FCS

I've got an asterisk 1.4.24 box with dahdi complete 2.1.0.3+2.1.0.2 I've got a 2 port T2XXP card attached with on T1 currently plugged in. Inbound calls work fine, but outbound fail with the rather cryptic: [May 19 17:28:07] WARNING[11360]: app_dial.c:1237 dial_exec_full: Unable to create channel of type 'DAHDI' (cause 0 - Unknown) There are similar threads I've found on the

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

After speaking with several people, and even participating in a forum of several other people with echo issues, I thought I'd share what we've done (well actually what our chief R&D engineer, Brett Bourn has done...) First let me say that normal cheapy PC hardware couldn't be made to function with out echo. We tried on both the single port Digium T1 card and the 4 port Digium T1

As best i could figure it out, I've installed dahdi and rc4. My TDM400P doesn't answer fxo or fxs. /etc/dahdi/system.conf: loadzone = us defaultzone=us fxoks=1,2 fxsks=4 /etc/asterisk/chan_dahdi.conf: [house-phones] context=internal ; Uses the [internal] context in extensions.conf signalling=fxo_ks ; fxo_ks Use FXO signalling for an FXS chanel dahdichan => 1 ;

Hi, I have a digium card (igium, Inc. Wildcard TE405P quad-span T1/E1/J1 card 5.0V (rev 02)) 4 ports I want to make a loop test between digium card E1 to test the configuration of dahdi What I want to do scenario is I connect port 1 and port4 in the digium card with E1 cable SIPcall-->E1 Digium port 1--->(Loop)E1 port 2---->sip extension local. kindly can any can help me to

Does anyone know if I could use modprobe command to find out rather than set the jumper on a Digium PRI card? I want to find out the jumper settings on the card without opening the box which will cause down time. Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I have a X101P card and am running Asterisk SVN-trunk-r226890. The X101P card seems to be identified properly: debian:/usr/src/dahdi-tools# dahdi_hardware pci:0000:01:01.0 wcfxo+ e159:0001 Wildcard X101P debian:/usr/src/dahdi-tools# dahdi_cfg -vv DAHDI Tools Version - SVN-trunk-r7409 DAHDI Version: SVN-trunk-r7445 Echo Canceller(s): MG2 Configuration ======================