similar to: Fw: Re: mISDN BRI Asterisk 1.4

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

Have you got termination set correctly? I have a B410P working with 2 x NT and 2 x TE ports successfully. I had to turn the 100ohm termination on on the NT ports (even though I have them set as PTP in mISDN.conf). HTH -->> -----Original Message----- -->> From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users- -->> bounces at lists.digium.com] On

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

Hi, As you may know, these ISDN BRI features are very important here in Europe as ISDN Basic Rate Access is very popular among Small & Medium Entreprises. I don't really know why but it seems that in many countries, default is to install small PBX using Point-to-Multipoint (PtMP) mode as opposed to Point-to-Point (PtP) which is the norm for PRI. So basically, in several countries, SME

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, I am struggling to get plain Cologne chip cards to run in NT mode, runs nice in TE mode despite the error message: login as: root root at 192.168.2.22's password: Last login: Tue Sep 1 23:09:24 2009 from 192.168.2.50 Welcome to Elastix ---------------------------------------------------- misdnportinfo Port 1: TE-mode BRI S/T interface line (for phone lines) -> Protocol: DSS1

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

Hi, i use an BN4S0 with misdn an asterisk on Linux 2.6.9. The hfcmulti module is loaded with option: type=0x04 protocol=0x2,0x2,0x22,0x2 layermask=0xf,0xf,0xf,0xf and the fourth port is connected to an ISDN PTMP (MSN) port. Call to #72 from S0 (BN port 4) are not accepted from asterisk but why ? Can anyone give me a hint ?? misdn debug messages follows: lib: NEW_CR Ind with l3id:80001

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

Hi, I need to rebuild a system which has 4 BRI ports and is connected to Point-to-multiPoint lines, in a country where telco often "drop lines for energy savings". I'm planning to use latest 11.4.0 asterisk version along with dahdi and libpri (no misdn). Which version are recommended for Dahdi and Libpri ? My main requirements are, beside having calls coming in and out: - keep a

Hi, At the moment, libpri /w Asterisk 1.6, Dahdi 2.1, is not supporting NT-Point to multi-point mode. Here (France), most small PBXes are connected to ISDN through BRI trunks in PtmP (don't know why but it seems the general case). So this NT-PtmP function would be very helpful to easily slide an Asterisk box between an existing PBX and the network. Does the same case apply elsewhere (UK,

Hi all ! We have 3 NTBAs which are all going to our existing PBX. Our areacode is 06003 and our DDI enabled number 9141. I want to exchange that PBX with Asterisk, but still struggle to get it working. My CAPI.CONF is currently like this: [general] nationalprefix=0 internationalprefix=00 rxgain=0.800000 txgain=0.800000 [interfaces] context=in-capi msn=60039141 incomingmsn=* controller=1

Hello, Following my first mail about this issue [1], I think I know now what the problem is. When I have both lines being used and a third call comes in, the person calling doesn't get a busy tone, he gets something like line unavailable. I've been debugging mISDN and I think the reason is because asterisk is sending the release cause as 0. P[ 3] --> channel:0 mode:TE cause:0

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 list, I'm currently trying to get Asterisk running with an HFC-compatible ISDN card (no-name product, but supposed to work with Asterisk according to the packaging). the ISDN-card is connected to a alcatel ISDN-system where it should act just like a normal ISDN-phone. I went with http://www.misdn.org/index.php/MISDN_with_Asterisk and installed the package from beronet.com including:

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:

I may have found a source of an A-Ticked HFC 4BRI PCI adapter in Australia, and will be testing one next week if all goes well. I don't want to post the details of the reseller online unless invited to do so, so if nobody replies and says they are interested then I won't :) I'll follow up once I've tested it. Let me know if you want the details. James

Hi. When I call my RNIS numbers (with a mobile phone for example), I can see 2 incoming calls on the IPBX, which should not happend. I'm not sure if it's a problem with the telco France Telecom and their ISDN setup, or if it's a problem with the MISDN driver on the IPBX itself. I'm stuck ... Any advices for troubleshooting that? Someone provide working configuration files

Hi, I'm bumping on this : cd /usr/src wget http://www.misdn.org/downloads/mISDN.tar.gz tar xvf mISDN.tar.gz cd mISDN-1_1_18 make <snip> In file included from /usr/src/mISDN-1_1_8/drivers/isdn/hardware/mISDN/core.h:9, from /usr/src/mISDN-1_1_8/drivers/isdn/hardware/mISDN/avm_fritz.c:20: /usr/src/mISDN-1_1_8/include/linux/mISDNif.h:791: error: field

Hi, Before diving into this, I would very pleased to know if someone could yes or no, successfully compile mISDN 1.1.8 on Lenny (latest RC1 or beta2 version) ? Regards After a fresh install on Lenny, I can reproduce at will : apt-get install build-essential linux-headers-2.6.26-1-686 cd /usr/src wget http://www.misdn.org/downloads/mISDN.tar.gz tar xvf mISDN.tar.gz cd mISDN-1_1_8 make ....