search for: lbo

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 wha...

...n=12,12,0,esf,b8zs bchan=265-288 dahdi_scan : [1] active=yes alarms=OK description=T4XXP (PCI) Card 0 Span 1 name=TE4/0/1 manufacturer=Digium devicetype=Wildcard TE410P (3rd Gen) (VPMOCT128) location=Board ID Switch 0 basechan=1 totchans=24 irq=225 type=digital-T1 syncsrc=1 lbo=0 db (CSU)/0-133 feet (DSX-1) coding_opts=B8ZS,AMI framing_opts=ESF,D4 coding=B8ZS framing=ESF [2] active=yes alarms=OK description=T4XXP (PCI) Card 0 Span 2 name=TE4/0/2 manufacturer=Digium devicetype=Wildcard TE410P (3rd Gen) (VPMOCT128) location=Board ID Switch 0 basechan=25 totcha...

Hi all, When configuring Asterisk with an ISDN card, it will at one point become necessary to select the LBO (Line Build-Out) value. This is an integer (0-7) that is determined by the length of the cable and is selected from the following table. Many of us are familiar with it: CSU (dB) DSX-1 (feet) ------------------------------- 0 0 0?133 1 133?266...

could be "hot". Is there any chance this would cause the card to fail after a while? It appears this site just had 4 port Digium card fail today. > Also, I am trying to cross connect with another Asterisk system with > > the normal LBO setting (i.e. span=1,1,0,esf,b8zs) but as of yet the > > systems aren't seeing each other at all. Could the side with the high > > LBO be confusing the other side somehow? > > Shouldn't be... you did use a T1-crossover cable to cross-connect the > two Asterisk boxes, ri...

...body of 'clearTopDownPointers' function is fully equivalent to the body of 'clearBottomUpPointers' function. The advised solution is to change this code into void clearBottomUpPointers() {     PerPtrBottomUp.clear(); } ---- lib/Analysis/InstructionSimplify.cpp:1891     bool NUW = LBO->hasNoUnsignedWrap() && LBO->hasNoUnsignedWrap(); There are identical sub-expressions 'LBO->hasNoUnsignedWrap()' to the left and to the right of the '&&' operator. Looks like the correct code is     bool NUW = LBO->hasNoUnsignedWrap() && RBO-&gt...

...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 type=digital-E1 syncsrc=0 lbo=0 db (CSU)/0-133 feet (DSX-1) coding_opts=HDB3 framing_opts=CCS,CRC4 coding=HDB3 framing=CCS [2] active=yes alarms=RED description=T2XXP (PCI) Card 0 Span 2 name=TE2/0/2 manufacturer=Digium devicetype=Wildcard TE220 (4th Gen) location=Board ID Switch 0 basechan=32 totchans=31 irq=16 type=digital-E1...

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) # 5: -7.5db (CSU) # 6: -15db (CSU) # 7: -22.5db...

At the top of my /etc/dahdi/system.conf file is this line: # Autogenerated by /usr/sbin/dahdi_genconf on Wed Feb 25 18:25:10 2009 -- do not hand edit OK, so how do I adjust the timing source and LBO numbers, and echo cancellers if I'm not supposed to edit this file? Brandon. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090226/c0ac7f88/attachment.htm

...ers' function. The advised solution is to change > this code into > > void clearBottomUpPointers() { > PerPtrBottomUp.clear(); > } This is probably correct. Hopefully John can comment. > > ---- > > lib/Analysis/InstructionSimplify.cpp:1891 > bool NUW = LBO->hasNoUnsignedWrap()&& LBO->hasNoUnsignedWrap(); > > There are identical sub-expressions 'LBO->hasNoUnsignedWrap()' to the left and > to the right of the '&&' operator. Looks like the correct code is > > bool NUW = LBO->hasNoUnsignedW...

Hi, my FreeBSD-9/stable machine (FreeBSD freebsd-tower.goebo.site 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #2 r241044M: Sat Sep 29 12:52:01 CEST 2012 lbo@freebsd-tower.goebo.site:/usr/obj/usr/src/sys/GENERIC i386) crashes reproducibly when rsync-ing files to an NFSv4 share on the FreeBSD machine. The crash makes the system reboot. The crash creates files in /var/crash which may be obtained here: [1]. This problem is not limited to the self-compile...

...urce Version = 1.4.12 Operating System = CentOS release 6.2 (Final) Kernel Version = 2.6.32-220.2.1.el6.i686 - 32 Bit ---------------------------------------- pbx*CLI> dahdi show status Description Alarms IRQ bpviol CRC Fra Codi Options LBO B4XXP (PCI) Card 0 Span 1 RED 0 0 0 CCS AMI 399-533 feet (DSX-1) B4XXP (PCI) Card 0 Span 2 RED 0 0 0 CCS AMI 399-533 feet (DSX-1) B4XXP (PCI) Card 0 Span 3 RED 0 0 0 CCS AMI...

...d161:b410 Digium Wildcard B410P but ?dahdi_scan? just recognize the B410P: [1] active=yes alarms=RED description=B4XXP (PCI) Card 0 Span 1 name=B4/0/1 manufacturer=Digium devicetype=Wildcard B410P location=PCI Bus 17 Slot 01 basechan=1 totchans=3 irq=66 type=digital-TE syncsrc=0 lbo=0 db (CSU)/0-133 feet (DSX-1) coding_opts=B8ZS,AMI,HDB3 framing_opts=ESF,D4,CCS,CRC4 coding=AMI framing=CCS [2] active=yes alarms=RED description=B4XXP (PCI) Card 0 Span 2 name=B4/0/2 manufacturer=Digium devicetype=Wildcard B410P location=PCI Bus 17 Slot 01 basechan=4 totchans=3 irq=...

...[ OK ] The dahdi_scan result is the following: [1] active=yes alarms=OK description=B4XXP (PCI) Card 0 Span 1 name=B4/0/1 manufacturer=Digium devicetype=Wildcard B410P location=PCI Bus 17 Slot 01 basechan=1 totchans=3 irq=66 type=digital-TE syncsrc=0 lbo=0 db (CSU)/0-133 feet (DSX-1) coding_opts=B8ZS,AMI,HDB3 framing_opts=ESF,D4,CCS,CRC4 coding=AMI framing=CCS [2] active=yes alarms=OK description=B4XXP (PCI) Card 0 Span 2 name=B4/0/2 manufacturer=Digium devicetype=Wildcard B410P location=PCI Bus 17 Slot 01 basechan=4 totchans=3 irq=6...

...wo more AB-IIs, one in each of the other two suites. The second unit is about 150 cable feet away from the switch and it syncs up just fine, but the third is 400 cable feet away and is having problems with its T1. The dip switches on all three units are set the same, and with the exception of the LBO they're all configured the same in zaptel.conf, yet the furthest AB-II is showing errors. I've swapped AB-IIs between positions to no effect; whichever unit is in the furthest suite cannot fully sync. There are at least two cables available in each segment of the run between the far AB-I...

...[wanpipe1] CARD_TYPE = AFT S514CPU = A CommPort = PRI AUTO_PCISLOT = NO PCISLOT = 4 PCIBUS = 15 FE_MEDIA = E1 FE_LCODE = HDB3 FE_FRAME = NCRC4 FE_LINE = 1 TE_CLOCK = MASTER TE_REF_CLOCK = 0 TE_HIGHIMPEDANCE = NO LBO = 120OH TE_SIG_MODE = CCS FE_TXTRISTATE = NO MTU = 1500 UDPPORT = 9000 TTL = 255 IGNORE_FRONT_END = NO TDMV_SPAN = 1 TDMV_DCHAN = 0 [w1g1] ACTIVE_CH = ALL TDMV_ECHO_OFF = NO TDMV_HWEC = YES # zaptel.conf loadzone=uk defa...

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...

...configure. orange:~# and my zaptel.conf file contains orange:~# more /etc/zaptel.conf fxsks=1 loadzone=uk defaultzone=uk orange:~# but zap show status in the command line shows orange*CLI> zap show status Description Alarms IRQ bpviol CRC4 Fra Codi Options LBO Wildcard X100P Board 1 OK 0 0 0 CAS Unk YEL 0 db (CSU)/0-133 feet (DSX-1) orange*CLI> and i think the Unk means unknown...? Does anyone have any ideas on how to get this line to work, ive followed every howto i can find, and google seems to be comming up...

...55.255.255.0 set ip gateway 192.168.1.1 -Setting the SNMP MIB-II System Group objects. set snmp getcom "public" set snmp setcom "public" set snmp trapcom "public" set snmp trapauth enable set snmp trapevent all -Setting slot a. set a:1 up set a:1 fdl none set a:1 lbo 1 set a:1 framing esf set a:1 id "toasterisk" set a:1 linecode b8zs set a:1 loopdetect csu set a:1:1-24 side drop set a:1:1-24 type voice set a:1:1-24 signal ls set a:2 down set a:2 fdl none set a:2 lbo 1 set a:2 framing esf set a:2 id "CAC DS1# A:2" set a:2 linecode b8zs set a:...

...known) then I can investigate those. Some details below: geriatrix ~ # dahdi_scan [1] active=yes alarms=OK description=T2XXP (PCI) Card 0 Span 1 name=TE2/0/1 manufacturer=Digium devicetype=Wildcard TE210P (4th Gen) location=Board ID Switch 0 basechan=1 totchans=24 irq=48 type=digital-T1 syncsrc=1 lbo=0 db (CSU)/0-133 feet (DSX-1) coding_opts=B8ZS,AMI framing_opts=ESF,D4 coding=B8ZS framing=ESF [2] active=yes alarms=RED description=T2XXP (PCI) Card 0 Span 2 name=TE2/0/2 manufacturer=Digium devicetype=Wildcard TE210P (4th Gen) location=Board ID Switch 0 basechan=25 totchans=24 irq=48 type=digital...

...en default In Service 7 from-pstn en default In Service 8 from-pstn en default In Service dahdi show status Description Alarms IRQ bpviol CRC4 Fra Codi Options LBO Wildcard TE120P Card 0 OK 1 0 0 ESF B8ZS YEL 0 db (CSU)/0-133 feet (DSX-1) CLI> dahdi show version DAHDI Version: 2.1.0.4 Echo Canceller: MG2 What should I try next? Any help appreciated. sean