similar to: Outgoing CallerID w. DAHDI on ISDN BRI

Hello, I am trying to update to dahdi 2.2.1. But somehow the xorcom (2BRI) device does not want to work. I pasted below the information I have. pbx at loicvoip1:~# /usr/share/dahdi/xpp_fxloader reset pbx at loicvoip1:~# /usr/share/dahdi/xpp_fxloader usb 'xpp_fxloader'[4937]: --------- FIRMWARE LOADING: (usb) [1 devices] ..Got all 1 devices 'xpp_fxloader'[5003]: ---------

Hello List, it is a very long time since I wrote here.... It has been still in Zaptel times.... Today I am run into a related problem: I can't get a DAHDI setup to work 100%. I am configuring an Astribank XR00013 (BRI, two ISDN ports). At some degree the installation (latest DAHDI drivers, Asterisk 1.6.0.18 on Centos 5.x) works. I can get incoming calls to the dialplan context that is

Hi all... I'm sorry for repeating my message. I have a problem with caller id on my asterisk server with xorcom astribank. here is my configuration : centos-5, asterisk 1.6.2.1, dahdi-linux-complete-2.2.1, libpri-1.4.10.2 ibm X-3200 series, xorcom astribank (16fxo, 8fxs), 16 line telco (hunting) everything fine until I try to feed my app with caller id. here is the log : --

The Asterisk Development Team is pleased to announce the release of DAHDI Linux 2.2.0 and DAHDI Tools 2.2.0. Both releases are available for immediate download at http://downloads.asterisk.org/pub/telephony In addition to various bug fixes, these releases include: * Support for new Xorcom Astribanks with the TwinStar[tm] option. * Improved hardware echo canceler performance for Digium VPMADT032.

The Asterisk Development Team is pleased to announce the release of DAHDI Linux 2.2.0 and DAHDI Tools 2.2.0. Both releases are available for immediate download at http://downloads.asterisk.org/pub/telephony In addition to various bug fixes, these releases include: * Support for new Xorcom Astribanks with the TwinStar[tm] option. * Improved hardware echo canceler performance for Digium VPMADT032.

The Asterisk Development Team is pleased to announce the release of DAHDI-Linux and DAHDI-Tools version 2.5.0 DAHDI-Linux 2.5.0, DAHDI-Tools 2.5.0 and DAHDI-Linux-Complete 2.5.0+2.5.0 are available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools

The Asterisk Development Team is pleased to announce the release of DAHDI-Linux and DAHDI-Tools version 2.5.0 DAHDI-Linux 2.5.0, DAHDI-Tools 2.5.0 and DAHDI-Linux-Complete 2.5.0+2.5.0 are available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux http://downloads.asterisk.org/pub/telephony/dahdi-tools

Hi, I have upgraded an Asterisk installation with a Xorcom BRI Astribank that was working under Ubuntu 8.04 to Ubuntu 9.10 and the device is no longer initialized. When I reload the udev rules, I see that the rules seems to be correctly loaded: udevd[452]: reading '/etc/udev/rules.d/40-xpp.rules' as rules file However, these rules do not seem to be triggered: # udevadm trigger

Hi, I would appreciate some advice on the following: how does one use a single BRI port HFC chipset based ISDN cards with the latest DAHDI, libpri and Asterisk 1.8? For Asterisk 1.4 I would first install mISDN & mISDNuser and then build Asterisk 1.4. Now I noticed that Digium's HFC chipset based B410P is supported by the latest DAHDI & libpri but reading the source of the

I'm trying to set caller ids on outgoing calls. I have a quad BRI B410P card connected to my telephony provider. I know the list of DID numbers the provider assigned to my company. If I don't set the caller id then the callee always sees the same "top-level" number. If I set the caller id to a specific DID number we own, the callee keeps seeing the "top-level" number,

I'm having trouble getting a xorcom set up. A large part of the problem is that the box is a _long_ way away and I can't get to/at it easily, so while I could probably fix this in a few hours if the machine were in front of me, I'm struggling over a slow unreliable laggy link. Ok, enough whining from me. I have a new Xorcom plugged into the usb of a Suse 11 machine I built Dahdi

Hi, I'm having some trouble setting up a Xorcom Bri 4 port. I have compiled asterisk and zaptel using the Bristuff bristuff-0.3.0-PRE-1y-g patches. So I'm running zaptel-1.2.17.1 and asterisk-1.2.18. The problem I'm having is that for one I get no LEDs showing if the unit is in TE and NT mode (not a issue for me but may have some impact on things) I have no errors in any logs I

, address 2 Dec 30 21:42:08 wedekindpbx1 kernel: [ 3746.344611] ERR-xpp_usb: XBUS-00: x= usb_listen: usb_submit_urb failed: -19 Dec 30 21:42:08 wedekindpbx1 kernel: [ 3746.353325] INFO-xpp: XBUS-00: [] D= isconnecting Dec 30 21:42:08 wedekindpbx1 kernel: [ 3746.353373] Zaptel: Master changed = to XBUS-00/XPD-01 Dec 30 21:42:08 wedekindpbx1 kernel: [ 3746.353382] Zaptel: Master changed = to

Hello, I'm in the process of building an Asterisk machine and need 5 or 6 BRI-Channels. I was looking for the beroNet and Junghans cards and stumbled upon the Xorcom Astribank xBRI products. Has anybody tried out the Astribank xBRI-Channel Banks? Are they production ready or should I go with a beroNet BN8S0 or JUNGHANNS.NET octoBRI ISDN? Thanks in advance, Lars -- We don't like their

Hi! I just wanted to ask if anyone managed to get "ordinary" HFC-S ISDN cards with the zaphfc driver running in a Xen3 DomU. I am referring to this post ( http://lists.xensource.com/archives/html/xen-users/2007-04/msg00202.html ), which perfectly describes my problem and I am therefore going to simply copy-and-paste it here: ----------- snip ------------> Hi, I''m

The Asterisk Development Team is pleased to announce the release of DAHDI-Linux 2.5.0.1 and DAHDI-Tools 2.5.0.1. 2.5.0.1 is a bug fix release. It is recommended that current users of v2.5.0 upgrade. DAHDI-Linux 2.5.0.1, DAHDI-Tools 2.5.0.1, and DAHDI-Linux-Complete 2.5.0.1+2.5.0.1 are available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux

The Asterisk Development Team is pleased to announce the release of DAHDI-Linux 2.5.0.1 and DAHDI-Tools 2.5.0.1. 2.5.0.1 is a bug fix release. It is recommended that current users of v2.5.0 upgrade. DAHDI-Linux 2.5.0.1, DAHDI-Tools 2.5.0.1, and DAHDI-Linux-Complete 2.5.0.1+2.5.0.1 are available for immediate download at: http://downloads.asterisk.org/pub/telephony/dahdi-linux

Hello, I've one astribank with 8 FXO unit and 8 pstn lines connected to the astribank. When I receive calls on my ipphone I get always Unknown callerid. It's is possible to receive the callerid from the lines on the astribank unit? This is my config: [channels] language=es context=from-zaptel signalling=fxs_ks ;rxwink=300 usecallerid=yes callerid=asreceived ;cidsignalling=bell

Hi, I have a problem with people that are calling from analog lines. We have a block of numbers 12345 - 0 to -99. Most calls are transmitting the whole number including the extension. There's no problem with that. But people calling from analog lines are connected to our asterisk box as soon as they finish dialing 12345. They don't get a chance to dial an extension. Just inserting a

Hi, I have a Xorcom Astribank connected to my Asterisk server. In one of the Astribanks FXO port I have a Celular Interface Module. My problem is the Astribank is receiving a early answer from the module, which doesn't happen with a ATA connected to the same module. This is causing some trouble with my billing system. I already tried the answeronpolarityswitch option, what else can I do ?