similar to: B200p card - use dahdi or mISDN?

Good Evening, The company I work for is attempting to connect an Cisco ISDN Router to an OpenVOX B200P BRI Card so that we can get it to dial out across an existing ISDN PRI Line also installed in the Asterisk PBX Everything has compiled successfully and the BRI card has been detected when mISDN is started: # misdnportinfo Port 1: NT-mode BRI S/T interface port (for phones) -> Interface

Hello all- My client has purchased these two OpenVox cards and I'm configuring a system with Asterisk 1.6. In the past I have used bristuff and libpri with older versions of Asterisk, but now I would like to upgrade to Asterisk 1.6. Question, should I be using mISDN or libpri for these cards when they are in the same system, or does DAHDI now support both cards under asterisk 1.6

Hello I have just set up Asterisk Asterisk 1.4.21.2 on a CentOS 5.2 machine. I am using the OpenVox B200P ISDN card. My problem is that even though chan_misdn module seems to be loaded correctly with Asterisk (I can see it using 'module show' command) the misdn commands are not available to me in the CLI so I cannot tell if my box is correctly interfacing with the ISDN card Any ideas

Hello- I have a system with one D410P and one B200P (both OpenVox). All is well with the D410P, inbound and outbound, and I can initiate calls on the B200P BRI span, but there may be something wrong with my inbound BRI setup: there is no indication of an inbound call when I dial in to it from the PSTN. When I run "pri intense debug" and make a call to the BRI span, I can see a

Hello- After configuring DAHDI and starting asterisk, I get the following message continuously on the Asterisk console: WARNING[2057]: chan_dahdi.c:4158 pri_find_dchan: No D-channels available! Using Primary channel 16 as D-channel anyway! My card is a D410P configured for E1, only the first span is configured, and configuration snippets are as follows: From /etc/dahdi/system.conf:

Hi, Until now I've been using my Digium B410P cards with misdn 1.0.x. I would like to upgrade my systems and am now wondering which is the "best" route to take: - use the latest release of misdn v1 - upgrade to the latest "stable" kernel and use the built-in misdn v2 - use misdn v2 as a seperate package (disable misdn in the kernel) - use dahdi's support for misdn

Asterisk - 1.8.4.1 Dahdi-linux - 2.4.1.2 Dahdi-tools - 2.4.1 Kernel: 2.6.37.6 Kernel BKL: enabled I am upgrading Asterisk on this box. It has an OpenVox A400P PCI analog card with 1 FXO and 1FXS module. This server has been running just fine for two years with Asterisk 1.6.1.0 I've just upgraded all the OS and installed Asterisk 1.8.4.1. On trying to configure the A400P I get: # modprobe

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

Hi, Built a new server at the weekend and install Asterisk 1.6.0.9 and IAX and SIP work great :) The one problem I am having is getting the OpenVox (TDM400 type card) to work. It is successfully identified using WCTDM kernel module and dahdi_scan picks it up just fine. The issue is when I try and setup dahdi_channel.conf as it fails everytime. When running asterisk -rvvvv I see the port pick

Hello, I'm evaluating to possibility to use chan_misdn as a short term workaround, in case latest Dahdi is not stable enough for what we are planning to do (we wish to use Junghanns and Digium BRI hardware with Asterisk 1.6) . I've read www.mISDN.org but still have a couple of questions : 1. Is correct that in a 2.6.27 (and up) enabled kernel, the "embedded" mISDN version is

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

Ok so this is officially driving me crazy. I have an Asterisk 1.6.1.6 install with DAHDI/DAHDI tools (latest) and an OpenVOX TDM400 card with 1 FXO port and 1 FXS port. I have a POTS line from my phone company attached to the POTS line. I have asked for "disconnect supervision" to be provisioned on my line and they claim to have added it. However, my scenario is as follows: I receive a

Hello Unless I overlooked it, the "Asterisk Reference Information Version 1.6.1.6" at www.asterisk.org/docs doesn't include instruction on how to start Dahdi when used to drive a TDP PCI card (OpenVox A400P with a single FXO module www.openvox.cn/products/show.php?itemid=20&lang=2). I'd like to know... 1. How to start Dahdi manually. Is this the right way? modprobe

Dear Supports, I was attempting to install BRI Card(OpenVox B800P) with wcb4xxp in NT mode .But I can not make it worked! Could you please give me some hints? Thanks in advance! Here are my environments: ------------------------------ CentOS-5.3 Kernel-2.6.18-164.el5 asterisk-1.6.1.6 dahdi-linux-complete-2.3.0+2.3.0 libpri-1.4.10.2 OpenVox-B800P(the first port is spliting into

The DAHDI docs actually include the 'steps' that used to be in Zaptel's 'make b410p'. These steps involve downloading and compiling mISDN. Why re-invent the wheel? Just a thought :-). As for the 100ohm termination bit - it's simply changing a couple of dip switches on the b410p card (as described in the manual). Andy -----Original Message----- From:

Hi all, I wanted to switch from my current setup (mISDN) to the native dahdi with b410p support (wcb4xp). All works fine for normal phone calls but not for faxing. Faxes are distorted, if arriving at all, and hylafax logs the usual bad stuff (HDLC frame not byte-oriented.) Our setup uses a digium b410p card with asterisk 1.6, latest libpri and dahdi, hylafax with iaxmodem, and all this on 1

Its been a few days, I was wondering if anyone else has any ideas on how to get this to work? If not, could I ask a the direct question as to if anyone here has (or knows someone who has) successfully got something like a Cisco Router to successfully establish an ISDN data/Internet connection through the Asterisk PBX?

Apart from you were dialling out on your inbound context and vice-versa. The best advice I can give now is to change to mISDN - as this is proven to work with v1.4 and v1.6. Actually - have you tried putting the 100ohm termination on for your NT port? I need to do that with mISDN as it only allows ptmp for ISDN extensions. Cheers Andy -------------- next part

Hi, After an upgrade, I discovered yesterday strange things I would like to share here. Basically, I'me comparing platforms: The first one is a 2.6.26 (Debian Lenny) platform, with Asterisk 1.6.1.18, Libpri 1.4.10.2, Dahdi revision 8853 (must be between 2.3 and 2.5, I think). The second one is a 2.6.32 (Debian Squeeze) platform, with Asterisk 10.5.1, Libpri 1.4.12, Dahdi 2.6.1. Both are

Hi All, We've got msidn configured: Port 1: TE-mode BRI S/T interface line (for phone lines) -> Protocol: DSS1 (Euro ISDN) -> childcnt: 2 -------- mISDN_close: fid(3) isize(131072) inbuf(0x8fd5060) irp(0x8fd5060) iend(0x8fd5060) and running on Asterisk 1.4.21.2: pbx*CLI> misdn show stacks BEGIN STACK_LIST: * Port 1 Type TE Prot. PMP L2Link UP L1Link:UP Blocked:0 Debug:0