similar to: libpri 1.4.11.1 Now Available

The Asterisk Development Team has announced the release of libpri 1.4.11.4. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/libpri/ The release of libpri 1.4.11.4 resolves several issues reported by the community and would have not 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.4. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/libpri/ The release of libpri 1.4.11.4 resolves several issues reported by the community and would have not 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:

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:

I have 2 ISDN BRI boxes, each with 4 spans, where the first one is configured as CPE, the second one as NET(so I don't need real lines for developing and testing). Once in a while I do see the following libpri error messages simultaneously on both boxes: PRI Span: 1 TEI=0 MDL-ERROR (A): Got supervisory frame with F=1 in state 7(Multi-frame established) PRI Span: 2 TEI=0 MDL-ERROR (A): Got

I just updated libpri 1.4 on my system to the latest from that branch and my QSIG connection to an NEC SV8300 stopped working. The trace showing the problem is below: q931.c:5640 q931_connect: Call 7168 enters state 10 (Active). Hold state: Idle > DL-DATA request > Protocol Discriminator: Q.931 (8) len=21 > TEI=0 Call Ref: len= 2 (reference 7168/0x1C00) (Sent to originator) >

On Tue, Apr 3, 2018 at 4:57 PM, Matt Fredrickson <creslin at digium.com> wrote: > On Tue, Apr 3, 2018 at 4:38 PM, Tony Mountifield <tony at softins.co.uk> > wrote: > > In article <CAHZ_z=w5DMg93gShtC93kuC+fnmraPgV46BS956U5BQXVgyhxg@ > mail.gmail.com>, > > Matt Fredrickson <creslin at digium.com> wrote: > >> On Tue, Apr 3, 2018 at 5:44 AM, Tony

connecting legacy PBX to Asterisk (for the very same reason, those PBX use TE-PTMP). If others could join this thread and say if they agree or not with NT-PTMP being the 2nd most needed mode, would be great. Please, do not hesitate to comment. > > > Right now, I would not preclude the possibility that NT-PTMP support > might be added, but I could not give you a concrete time at which

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

What am I doing wrong here? Why is this happening? libpri is version 1.0.7-1 (debian package) asterisk is version 1.0.7.dfsg.1-2 (debian package) zaptel is version 1.0.9.2 -- Executing Dial("SIP/739-5935", "Zap/g1/0916000739") in new stack -- Called g1/0916000739 -- Channel 0/1, span 1 got hangup Oct 10 13:14:45 WARNING[7544]: app_dial.c:412 wait_for_answer:

Hi, In my lab, I'm testing BRI spans in NT/ptmp mode. My setup is: asterisk 11.2.1 libpri 1.4.14 dahdi 2.6.1 wctdm24xxp (HA8 hybrid with B400M) SIP phone <----> Asterisk with HA8 <----> Patton SN4638 <----> Asterisk <----> SIP phone The single BRI line I'm testing remains down: CLI> pri show spans PRI span 1/0: In Alarm, Up, Active I'm quite certain this

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

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 all, Last night I went to replace an Asterisk 1.4 + mISDN + b410p box with Asterisk 1.6.2 and DAHDI BRI - to no avail. I had two servers so copied network setting etc from the working one, moved the card across, ran dahdi_genconf etc and it didn't work. Here's the console output with notices disabled: lucas*CLI> pri intense debug span 1 Enabled debugging on span 1 [Dec 16

The Asterisk Development Team has announced the release of version 1.4.11.3 of libpri. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/libpri/ This release fixes a regression in the calling number assignment logic: * Calling Number assignment logic change in libpri 1.4.11. Restored the old behaviour if there is more than one calling number in

The Asterisk Development Team has announced the release of version 1.4.11.3 of libpri. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/libpri/ This release fixes a regression in the calling number assignment logic: * Calling Number assignment logic change in libpri 1.4.11. Restored the old behaviour if there is more than one calling number in

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 all, So, we reverted the LibPRI version and tested it, and then tried with the latest version of everything. Still no changes. The BRI line is in PTMP. If we set the configs to PTMP in the genconf_parameters and try it, we get the following: [Jan 21 17:32:20] ERROR[20341]: chan_dahdi.c:12645 dahdi_pri_error: Unable to receive TEI from network! If we set it to PTP (which it is not) we