similar to: Problems after upgrading libpri from 1.4.11.2 to 1.4.11.5

Hello, I've got a running system in which logs are full of messages such as: [Jun 10 07:24:14] NOTICE[2414] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 2 The strange thing is those messages are coming from a single span. My setup is : Asterisk 1.6.1.18 Junghanns OctoBRI with wcb4xxp driver libpri 1.4.10.2 dahdi 2.3.0 3 BRI lines in PtMP mode What does this

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

The Asterisk Development Team has announced the release of libpri 1.4.11.5. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/libpri/ The release of libpri 1.4.11.5 resolves several issues reported by the community and would not have been possible without your participation. Thank you! The following are some of the issues resolved in this release:

The Asterisk Development Team has announced the release of libpri 1.4.11.5. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/libpri/ The release of libpri 1.4.11.5 resolves several issues reported by the community and would not have been possible without your participation. Thank you! The following are some of the issues resolved in this release:

Hi, In my 1.6.1.18 with dahdi 2.2.1.1, I've got : # dahdi_hardware pci:0000:01:0a.0 qozap- 1397:16b8 Junghanns OctoBRI ISDN card Does it mean I should download and use qozap or is it a bug in Dahdi ? Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100412/de87e46e/attachment.htm

The Asterisk Development Team has announced the release of version 1.4.11 of libpri. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/libpri/ This release contains many fixes and new features, among them being: 1.) Support for NT-PTMP BRI links, including support for multiple TEIs and connecting of BRI phones. 2.) Support for allowing persistent

The Asterisk Development Team has announced the release of version 1.4.11 of libpri. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/libpri/ This release contains many fixes and new features, among them being: 1.) Support for NT-PTMP BRI links, including support for multiple TEIs and connecting of BRI phones. 2.) Support for allowing persistent

Hello, I recently bought a Junghanns Octobri Card. I have some problems with this card to make outbound calls but I can receive calls. I have 3 lines to PSTN and 3 lines to my existing PBX FRANCE TELECOM <-- OctoBRI --> Asterisk 1.2.4-BRIstuffed-0.3.0-PRE-1h <-- OctoBRI --> PABX e-Generis <----> ISDN Phones |

BUG/SYMPTOMS: 1.Under certain circumstances, octoBRI (and most likely quadBRI) ISDN cards (Junghanns/CologneChip) severely distort certain ISDN payload. 2.Although these claims relate to the bristuff patch, the problem might not be limited to bristuff and in fact be rather asterisk/zaptel/libpri related. 3.Signal distortion is limited to the use of the CVS version of the Bristuff patch for

Hi, I'll soon replace a Junghanns OctoBRI with a Junghanns QuadBRI. As both use wcb4xxp driver (dahdi 2.3.0, libpri 1.4.10.2 and asterisk 1.6.1), I'm planning to proceed this way : 1. Edit 2 versions of files /etc/dahdi/system.conf and /etc/asterisk/dahdi-channels.conf (one for each card). 2. Link current system.conf and dahdi-channels.conf to QuadBRI files. 3. Power PC off 4. Swap cards

The Asterisk Development Team has announced the release of version 1.4.11.2 of libpri. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/libpri/ This release fixes situation where Q.SIG calling name in FACILITY message was not reported to the upper layer: * pri_facility.c: Q.SIG calling name in FACILITY message not reported to the

The Asterisk Development Team has announced the release of version 1.4.11.2 of libpri. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/libpri/ This release fixes situation where Q.SIG calling name in FACILITY message was not reported to the upper layer: * pri_facility.c: Q.SIG calling name in FACILITY message not reported to the

Hi, I'm trying to dial from one Asterisk box to a Patton 4638 BRI gateway. I'm only getting this : [May 8 15:08:24] WARNING[16797]: app_dial.c:1547 dial_exec_full: Unable to create channel of type 'DAHDI' (cause 0 - Unknown) My setup is : Asterisk 1.6.1.18 libpri 1.4.10.2 1 Junghanns QuadBRI PCI-E express with : - driver

Hi, Using Xorcom's bristuff-0.4.0-RC4-xr7.tar.gz (ie asterisk 1.4.25) with an old Junghanns OctoBRI (ie not the 2.0 version), zttool shows every port in TE mode, though half of them are in NT. Alarm column shows OK for every port, such as : OK octoBRI PCI ISDN Card 1 Span 1 [TE] Lay Globally, this system doesn't work (can't dial out through zaptel) Replacing this board

Hi, When reading logs, I can see a couple of lines such as : full.6:[Jun 30 15:53:26] NOTICE[6599] chan_dahdi.c: PRI got event: Alarm (4) on Primary D-channel of span 1 full.6:[Jun 30 15:53:32] NOTICE[6599] chan_dahdi.c: PRI got event: No more alarm (5) on Primary D-channel of span 1 full.6:[Jun 30 15:53:32] NOTICE[6607] chan_dahdi.c: Alarm cleared on channel 1 full.6:[Jun 30 15:53:32]

Hello, In my system, dmesg outputs : [ 13.039788] wcb4xxp 0000:01:0a.0: probe called for b4xx... [ 13.039788] ACPI: PCI Interrupt 0000:01:0a.0[A] -> GSI 21 (level, low) -> IRQ 21 [ 13.039788] wcb4xxp 0000:01:0a.0: Identified HFC-8S Junghanns.NET octoBRI PCI (controller rev 1) at 0001dfe0, IRQ 21 [ 13.041202] wcb4xxp 0000:01:0a.0: NOTE: hardware echo cancellation has been disabled [

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, I have made (S)RPMS of cvs STABLE & HEAD and several other apps and put them online at http://www.laimbock.com/asterisk/ The cvs STABLE RPMS support udev, Eicon Diva Server cards, HFC-S based ISDN cards, QuadBRI and OctoBRI ISDN cards from Junghanns.net and SpanDSP for sending & receiving faxes. The sample files are also included and are put in

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, Looking at dmesg, I can see : [ 45.213205] wcb4xxp 0000:01:07.0: Span 5 has invalid sync priority (5), removing from sync source list [ 45.213205] wcb4xxp 0000:01:07.0: Span 6 has invalid sync priority (6), removing from sync source list [ 45.213205] wcb4xxp 0000:01:07.0: Span 7 has invalid sync priority (7), removing from sync source list [ 45.213205] wcb4xxp 0000:01:07.0: Span 8 has