similar to: Unknown signalling method 'bri_cpe

Hi all, I am having trouble setting the signalling method for the B410P using DAHDI. Asterisk complains that it has never heard of 'bri_cpe' or 'bri_net' - but it doesn't mind having 'pri_cpe' etc. ERROR[4294]: chan_dahdi.c:11327 process_dahdi: Unknown signalling method 'bri_net' Dahdi - dahdi-linux-complete-2.1.0.4+2.1.0.2 Asterisk - 1.4.23.1 Libpri - 1.4.9

Hi, It seems BRI signalling settings are missing from http://www.voip-info.org/wiki/view/Asterisk+config+chan_dahdi.conf I would like to add those parameters : bri_cpe_ptmp bri_cpe bri_net Is this http://www.voip-info.org/wiki/view/Asterisk+config+chan_dahdi.conftied to a specific Asterisk version ? Can I edit this ? Regards -------------- next part -------------- An HTML attachment was

Hi, we upgraded an Asterisk 1.4 with mISDN to 1.6 with chan_dahdi. Due to problems with iax channel posted earlier, we wanted to switch back to 1.4 version. Server has 2 HBA cards, everything is running fine with 1.6, bri_cpe is recognized and the 7 euroISDN channels are running well, ingoing and outgoing. Now we installed 1.4.38 version and no more ISDN. In logs we found this: [2010-12-24

Hello everybody, I try to install -Ubuntu 8.04 server- a B410P and a TDM2400P together with Asterisk 1.4.26-2, dahdi-linux-2.2.0.2 and dahdi-tools-2.2.0. Problem I face is the following one: CLI> module load chan_dahdi.so == Registered application 'DAHDISendKeypadFacility' == Registered application 'ZapSendKeypadFacility' == Parsing

Hi All, I've a BT Versatility PBX that I want to connect to my asterisk 11.9.0 box via BRI port in NT mode but actually I wasn't able to get it working. I've another standalone PBX, it's a Panasonic model, which works fine connected to the same port. The BT connected to a UK BT BRI line works quite fine after roughly a minute once connected. The PBX can be seen at

Hi list! I am installing an * box that will be installed on a site with KPN BRI ISDN in The Netherlands. I am using bristuff fron Junghanns. Does anybody know the correct settings for this? I will not have internet access there which makes it harder to google around on location. switchtype = euroisdn is pretty obvious but what about these settings: signalling = bri_cpe_ptmp ; p2p TE mode

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, When startin * it tells me: ================================ [chan_zap.so] => (Zapata Telephony w/PRI) == Parsing '/etc/asterisk/zapata.conf': Found Sep 3 17:21:59 DEBUG[1076873856]: chan_zap.c:1208 update_conf: Updated conferencing on 1, with 0 conference users -- Registered channel 1, PRI Signalling signalling Sep 3 17:21:59 DEBUG[1076873856]: chan_zap.c:1208 update_conf:

Hi all, As i tested with Asterisk+dahdi+libpri with openvox BRI with NT mode, the ISDN phone does not work. There is the setting and error. ***********************Enviroment***************************** Asterisk-1.6.1.18 dahdi-linux-2.3.0.1 dahdi-tool-2.30. libpri-1.4.11.2 CentOS-5.5 OpenVox B400P ****************************************************************** In my case , I set prot 1 and

Hello, Is it possible, for testing, to connect an cat5 straight patch cord between 2 ports of a Digium B410P card and use these 2 ports as a normal dahdi trunk ? I've tried this: One port is set as NT, the other as TE. I would expect timing to come for system hardware so I choose in /etc/dahdi/system.conf : span=1,0,0,ccs,ami span=2,0,0,ccs,ami Results: - both ports lights are green -

Is there a recommended way to find out the cause of DIALSTATUS = CONGESTION for PRI/BRI channels? Currently I am evaluating the DIALSTATUS variable and I also count the active ISDN channels for the ISDN trunk in question. Counting the active ISDN channels seems somewhat clumsy as the mapping to a specific trunk must be done by hand (or write even more code). I have a setup where outgoing calls

Hi all, As i tested with Asterisk+dahdi+libpri with openvox BRI with NT mode, the ISDN phone does not work. There is the setting and error. ***********************Enviroment********************************** Asterisk-1.6.1.18 dahdi-linux-2.3.0.1 dahdi-tool-2.30. libpri-1.4.11.2 CentOS-5.5 OpenVox B400P ******************************************************************** In my case , I set prot 1

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, these are my first steps with DAHDI and I finally managed to get asterisk to load chan_dahdi (after I found out, that I need libpri). But how do I tell chan_dahdi on which isdn numbers it should react? I haven't found a parameter like "incomingmsn" for chan_capi in the documentation. Thanks for your help, Stefan

Hello out there, I'm running an Asterisk 1.8.15-cert1 with DAHDI. Today I noticed that Asterisk is signalling to the calling party the current internal CallerID whenever I put a call to another internal phone. Example: Customer calls 020212345-555 -> IVR answers and puts caller to the chosen queue -> Someone picks up the phone (Internal ext. 321) -> CallerID shown on customers

Please forgive me, if I misunderstand the problem completely. Following instructions in several german blogs, I want to configure Asterisk with a hfc-pci card, an old NTBA and an ISDN phone as a SIP device. It seems that I have to set signalling in zapata.conf to bri_net_ptmp. When I do this, Asterisk will hang if started with -vvvvc, the last lines of output being: [res_features.so] =>

Hi! Has anybody seen anything like this using zaphfc? On outgoing calls (via isdn) , the line gets hung-up as soon as the called party answers. As seen below i get some protocol error (6) - but i'm not sure if this is related to the "hang-up" which apparently comes a little earlier?! Incomming calls on the isdn (zaphfc) interface is working just fine (P.S. what about the

I have a serious problem that repeats very often, after 30 - 50 calls and I can only solve it by stopped and restarting * :-( After a while, * seems to loose track of something. When an ISDN call from PBX needs to go to the Telco, I get 'Ring requested on unconfigured channel 255/255 span 2' It's always channel 255/255 ??, the 'span' number is random Setup: * between Local

Hi, I'm trying to connect quadbri between powered ISDN phone and ISDN line: ISDN <---1---> TE - * - NT <--2--> Phone I use quadbri, suse 9.2 and latest 0.2.0-RC7k bristuff. I've used sample settings provided with package, but do get strange error (I think that I have wrong setting for P2P or P2MP setting and cables 1 and 2). If I connect phone to ISDN with straight cable

Hi, I have a B400P BRI card with point-to-point connection (signalling: bri_cpe) with this dmesg: http://pastebin.com/sXrRt1yM When i restart asterisk server, the card cannot connect to the telco, the control led flashes red. If I unplug the cable between the ISDN nt and the card and wait 40 sec, the card can connect and works properly. The telco says the asterisk crashes the connection