similar to: libpri version 1.4.5 Released

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

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

The Asterisk Development Team has announced the release of version 1.4.11.1 of libpri. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/libpri/ This release fixes a regression in multi component FACILITY messages and includes a minor bug fix for BRI spans: * Multi component FACILITY messages only process the first component. The code was only

The Asterisk Development Team has announced the release of version 1.4.11.1 of libpri. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/libpri/ This release fixes a regression in multi component FACILITY messages and includes a minor bug fix for BRI spans: * Multi component FACILITY messages only process the first component. The code was only

Hi. My configuration is Elastix 1.5.2-2 (asterisk 1.4.24, libpri-1.4.3-5, dahdi-2.1.0.4-7 ) and OpenVox d210e connected to telco provider (Euro ISDN). Here is my /etc/dahdi/system.conf: # Span 1: TE2/0/1 "T2XXP (PCI) Card 0 Span 1" (MASTER) HDB3/CCS ClockSource span=1,1,0,ccs,hdb3 # termtype: te bchan=1-15,17-31 dchan=16 echocanceller=oslec,1-15,17-31 # Span 2: TE2/0/2 "T2XXP

UPDATE. The circuit has run clean since the 7th. It seems the telco found a problem after all but they can't tell me what they did... cause they think it was fixed as part of another case. Grrr. Well, I never doubted the T400P too much but I went ahead and bought a different card just in case. Haven't had to use it so far. One of the biggest reasons I did not think the Wildcard was at

The Asterisk Development team is pleased to announce the release of libpri 1.4.10.2, which is available for immediate download at: http://downloads.asterisk.org/pub/telephony/libpri/libpri-1.4.10.2.tar.gz This release resolves various issues found in libpri 1.4.10.1 and earlier versions related to scheduler events not being deleted and new ones being created on top of them. This can cause the

The Asterisk Development team is pleased to announce the release of libpri 1.4.10.2, which is available for immediate download at: http://downloads.asterisk.org/pub/telephony/libpri/libpri-1.4.10.2.tar.gz This release resolves various issues found in libpri 1.4.10.1 and earlier versions related to scheduler events not being deleted and new ones being created on top of them. This can cause the

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

My client would like to add new functionality, such as call queuing, to their PBX. They presently have a Telrad PBX; it has a T1/PRI circuit from the CLEC and a few POTS lines. They use DID for some incoming calls and an attendant for calls on the main number. The client's commitment to customer service will not allow us to outright replace their PBX with a new system--we could never

I just downloaded the cvs version CVS-07/28/03-14:45:19 and now I cannot recieve the the calls from the zaptel interface which is a E100P with pri signaling. That is something with asterisk becouse rolling back to version from 06/23/03 using the new libpri and zaptel fixes the problem. Here is an exept from the config: [macro-stdexten]; ; ; Standard extension macro: ; ${ARG1} - Extension

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

The latest libpri is supposed to handle this properly, but doesn't seem to. Here's the debug info. CALLERID(name) is set to empty. < Protocol Discriminator: Q.931 (8) len=66 < TEI=0 Call Ref: len= 2 (reference 256/0x100) (Sent from originator) < Message Type: SETUP (5) < [04 03 80 90 a2] < Bearer Capability (len= 5) [ Ext: 1 Coding-Std: 0 Info transfer capability:

Hi all, i do have the following setup ISDN BRI Line -> openVOX Card/Asterisk 1.6.2.6/libpri 1.4.11.2 -> Dialplan Dial DAHDI -> ISDN PBX -> ISDN Equipment The user on the ISDN Equipment das enable call forwarding - Teilrufumleitung / Call deflection - so that call will get forwarded by the telco switch - and not using b channels. The forwarding request is coming in on asterisk (i

Hi, Recently, I made issues after upgrading libpri from 1.4.11.2 to 1.4.11.5. After coming back to 1.4.11.2, everything ran successfully. Unfortunately, I didn't have much time to spend to investigate but I hope I'll soon get an opportunity to try 1.4.11.5 again on another telco line. Basically, the symptoms were that pri show spans kept showing lines to be either down or in alarm. My

I have a working system with asterisk 1.4.26.2 libpri 1.4.1 and zaptel 1.4.12.1 With a digium TE205p. I am trying to update to libpri 1.4.10.2. When I do, incoming calls work but outgoing does not. When I do this I "rm /usr/lib/libpri*" then just install libpri-1.4.10.2 as normal. I then do a make clean in asterisk and make distclean ,then configure, make and make install. I do

We are running Asterisk version 1.4.23-1, libpri-1.4.9 and zaptel-1.4.12.1 and two Digium TE220Ps. Debugs are set to 10. We have a T1 PRI connected to the telco. Over the last 4-5 days, we have getting Yellow/Red alarms coming from the T1 PRI. The other two ports in use are connected to internal test switches (Avaya Legend/Avaya Definity), and are not showing any errors.

Hi all, I have some problem to send a FAX to a given number. I use asterisk 1.2.18, on a openSUSE 10.2, i586 host. The FAX is sent out via an ISDN PRI interface, I'm in Germany, and the destination FAX devices are in Germany too, but in different areas, so I have to use a city prefix. I did set the pri device in debug mode, below are two calls, to two different FAX numbers, the first is

I install the Asterisk into a RedHat9, exactly like manual says, and I'm having the attached error message when try to install libpri. Please, help on it. -------------- next part -------------- [root@LinuxLab zaptel]# cd .. [root@LinuxLab src]# cd libpri/ [root@LinuxLab libpri]# make clean; make install Makefile:93: .depend: No such file or directory ./mkdep -Wall -Werror -Wstrict-prototypes