similar to: Odd error in libpri

I'm using QSIG between Asterisk and an NEC SV8300. Whenever I make a call from the SV8300, I see: [Oct 4 21:02:49] ERROR[5729]: chan_dahdi.c:12226 dahdi_pri_error: !! < Unknown IE 50 (cs5, len = 3) I see an IE 50 in the Q.932 specification, so I don't understand why this error is occuring.

I'm using QSIG between an NEC SV8300 and Asterisk (after giving up with CCIS). Things work pretty well with the exception of issues on stations on the SV8300. When I call from Asterisk to a SV8300 station and I send my extension as the caller ID number, it shows up on the SV8300 as "OPERATOR". I've tried a few different TON/NPI values with no difference. If I set callerid to a

On June 5, 2011, we migrated from Mantis to Jira as the issue tracker for Asterisk [1]. We temporarily left Mantis running in read-only mode to smooth the transition. At 15 months, temporary has turned into semi-permanent. As a part of other infrastructure changes we are making to the community services, we will finally shut down Mantis for good. We will update our DNS servers on the morning of

On June 5, 2011, we migrated from Mantis to Jira as the issue tracker for Asterisk [1]. We temporarily left Mantis running in read-only mode to smooth the transition. At 15 months, temporary has turned into semi-permanent. As a part of other infrastructure changes we are making to the community services, we will finally shut down Mantis for good. We will update our DNS servers on the morning of

Greetings, A few weeks ago I posted a message about the upcoming migration from Mantis to JIRA for issues.asterisk.org [1]. A lot of testing has been done and all known issues have been resolved. We have scheduled the migration for Sunday, June 5th. The issue tracker will be down most of the day as the migration takes place. Once the migration is complete, the issue tracker will be:

I am suddenly getting a bunch of OLD (as in 3-9 months old) e-mails from mantis saying things like a note has been added to an issue etc., and yet the issue has not been touched in months and the "new note" it is referring to is also months old. Consequently, I never received these e-mails before either. The e-mail itself shows that "carolina.digium.com" received

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:

i'm trying to review issues that i'm monitoring and/or have reported at http://issues.asterisk.org when I click on 'My View' or 'View Issues' I get an error: APPLICATION ERROR #401 Database query failed. Error received from database was #1142: DELETE command denied to user 'mantisreadonly'@'localhost' for table 'mantis_tokens_table' for the

Hi all, I've installed mantis.noarch and mantis-config-httpd.noarch packages. The problem is I always get the same error in Apache:. You don't have permission to access /mantis on this server. It's curious 'cause: * I work in localhost mode and I've running drupal site and phpMyAdmin without problems. So, Apache works fine. * I've created mantis ddbb according the docs

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

I'm having a wierd problem. Somewhere around 1-2% of the time, the first DTMF digit dialed gets dropped. This is occurring during a SpeechBackground application call. If the caller reenters the digits when given a second chance, all is OK. Any suggestions how to debug this intermittent problem?

As previously mentioned on the lists by Olle Johannson, we are actively trying to get Asterisk in shape for a 1.2 release within the next 60 days. To accomplish this, we need a few things to happen: 1) A feature freeze - This will occur at the end of this month, with no new feature submissions accepted after July 31st. Any _pending_ feature patches in Mantis that have passed architecture

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

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

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

Hi Folks, I've been looking around and found some references of some Caller ID patches (Mantis bug#9) for X100P and TDM400 for Netherlands, Sweden and UK. It's been quite hard to understand what has finally been incorporated to the distribution (if anything) or which patches must be applied in witch snapshot of the repository. I've tried some different approaches but nothing worked

Does anyone have a WORKING native MOH patch for Asterisk 1.0.3? Thanks! -- Kristian Kielhofner

Hi All! I've set up Asterisk asterisk-1.6.2.2 My question is why asterisk opens so many sockets and does not close that? My diagnostics commmands: # lsof | grep asteriske | grep UDP | wc -l 1214 # ls -l /proc/`ps axuw | grep asteriskexe | grep -v grep | awk '{ print $2 }'`/fd | wc -l 1257 asx*CLI> core show calls 2 active calls 1253 calls processed asx*CLI> sip show