search for: print_bug_pag

Can anyone update me on the status of http://bugs.centos.org/print_bug_page.php?bug_id=5897 I'd really like to know if there is a fix for this as we're trying to get AD/NFSv4 working on 6.3 and having one hell of a time. -- James A. Peltier Manager, IT Services - Research Computing Group Simon Fraser University - Burnaby Campus Phone : 778-782-6573 Fax :...

Hi, I download the last svn and I also look around but I cannot find the source, I only found the patch http://bugs.digium.com/print_bug_page.php?bug_id=8919 any one can help me out. thx -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070209/6780fde6/attachment.htm

...d a bug in the CMake build while using MinGW (non-MSYS, non-CYGWIN) where the LTO_export fails with a "The syntax of the command is incorrect" error. This error was previously fixed for Windows in general using TO_NATIVE_PATH, however CMake has a known bug ( http://public.kitware.com/Bug/print_bug_page.php?bug_id=5939 ) where TO_NATIVE_PATH does not replace slashes by backslashes when the MinGW Makefiles generator is used. The attached patch provides a workaround. Considering that the bug has been open since 2007 it is unlikely that kitware will fix this anytime soon. Regards Johannes S. Muelle...

...ke build while using MinGW (non-MSYS, > non-CYGWIN) where the LTO_export fails with a “The syntax of the > command is incorrect” error. This error was previously fixed for > Windows in general using TO_NATIVE_PATH, however CMake has a known bug > ( > http://public.kitware.com/Bug/print_bug_page.php?bug_id=5939 ) where > TO_NATIVE_PATH does not replace slashes by backslashes when the MinGW > Makefiles generator is used. The attached patch provides a workaround. > Considering that the bug has been open since 2007 it is unlikely that > kitware will fix this anytime soon. Yes...

The Asterisk.org development team has announced the release of Zaptel version 1.4.10.1. This release is a bug fix release for a regression in which the Zaptel udev rules were not installed correctly, as well as a few minor fixes in the xpp drivers. This release is available as a tarball as well as a patch against the previous release. It is available for download from downloads.digium.com.

The Asterisk.org development team has announced the release of Zaptel version 1.4.10.1. This release is a bug fix release for a regression in which the Zaptel udev rules were not installed correctly, as well as a few minor fixes in the xpp drivers. This release is available as a tarball as well as a patch against the previous release. It is available for download from downloads.digium.com.

This bug report http://bugs.digium.com/print_bug_page.php?bug_id=12038 apparently has been fixed. I dont see anything on the page saying what released version of asterisk this is in. How can I tell that? jerry

I have a Sangoma b600de analog card using dahdi 2.1.0.4 and I get the following results (same dialplan, config etc): Asterisk 1.6.0.1 => works fine Asterisk 1.6.0.9 => can't dial out unless I dial in once or apply patch >>>==> http://bugs.digium.com/print_bug_page.php?bug_id=14577 Asterisk 1.6.1.0 => can't dial out, regardless of patch or inbound call first. Asterisk incorrectly thinks the line is congested. Anyone else experiencing this? Regards and thanks, Mike v

I just took my first cent server into production and now saslauthd keep crashing after brute force attack. I found a bug report so this has already been reported but not fixed. http://bugs.centos.org/print_bug_page.php?bug_id=2860 I assume this has to be a large problem for many people and am surprised it hasn't been fixed yet. Has anyone found a work around for this bug? Is there a better rpm repo for a saslauthd that won't crash? -bazooka

...drbd.x86_64 8.0.11-1.el5.centos As far as I'm aware DRBD works fine for me. Is there a way I can find out about the new release and weather I should upgrade? I can't figure out the CentOS issue tracking system at bugs.centos.org but a google site search came up with http://bugs.centos.org/print_bug_page.php?bug_id=2657 (a DRBD 82 tracker bug with empty reports), which makes me feel like this version of the package is not 100% trusted. So - should I upgrade it or not? Generally, I try to stick to the "standard" as much as I can, but the text in http://wiki.centos.org/Repositories gives...

...;ZOMBIE>' The very strange thing is that it appears to be pulling the correct context from extensions.conf. If I comment out the include => a10-parking statement, Terry cannot access extension 700 to park the call. What have I missed? I did see this issue - https://issues.asterisk.org/print_bug_page.php?bug_id=14996 - with this test: exten => 5,1,Set(PARKINGEXTEN=803) exten => 5,n,Set(PARKINGLOT=edvinapark) exten => 5,n,Set(CHANNEL(parkinglot)=edvinapark) exten => 5,n,Verbose(2,Parking lot is current set to ${CHANNEL(parkinglot)}) exten => 5,n,Park() which works on my system (...

Hello List, Does anyone know why this is not available in CentOS 6.6. I found it in a SL repo but not in CentOS. I found several CentOS Bugs one answered by JH http://bugs.centos.org/print_bug_page.php?bug_id=6822 saying it had been added to 6.5 2013-12-09 19:05 JohnnyHughes Resolution open => fixed But it is still not available. cat /etc/redhat-release CentOS release 6.6 (Final) yum repolist repo id repo name status base...

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: santi.vcf Type: text/x-vcard Size: 340 bytes Desc: not available Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20070207/fefc16d8/santi.vcf

Does anybody know if SetCallerPres works on calls via SIP through a Cisco gateway? We are trying to mark outbound calls as anonymous and we set it to prohib, but calls still show outbound callerid. We are SIP from * to the Cisco gateway and then PRI outbound. If we strip the callerid num, then the first number on the PRI gets added as teh callerid, so we can't do that. We need to make

I'm expanding our tiny asterisk setup with a couple of external SIP phones, and I've just noticed the issue of the callerid not being displayed on an attended transfer. This bug seems to deal with it: http://bugs.digium.com/print_bug_page.php?bug_id=8824 I'm surprised that this hasn't been dealt with a long time ago - is there perhaps a work-around that I'm not aware of? /Per Jessen, Z?rich

Hi * users, I would like to extract the information present in the SIP REFER message that comes to asterisk. Would SIP_HEADER() allow me to do that ? I have used SIP_HEADER() for extracting the to and from SIP headers previously. Thanks Regards -- Arpit Mehta Graduate Student Department of Computer Science Columbia University Tel: 1-646-387-5998

When I restart or reboot I can not dial out. The dial() incorrectly sees dahdi/1 as busy. I call in once from a cell phone, which is successful then I can call out with out issue. Any ideas would be much appreciated. Sangoma B600de asterisk-1.6.0.9 dahdi-linux-2.1.0.4 linux-2.6.28-gentoo-r5 wanpipe-3.3.16 ###chan_dahdi.conf ;autogenerated by /usr/sbin/wancfg_dahdi do not hand edit

We just started seeing the errors described in <http://bugs.centos.org/print_bug_page.php?bug_id=5575> The question is, given that we're not seeing DRDY errors, and this is showing on all four drives, and there's no RAID, should we just turn off SMART, or is this telling us something important, other than the bug? mark

...ct: Re: [LLVMdev] [patch] EXPORTED_SYMBOL_FILE using mingw and cmake Okay I guess the test would be something like this then if (CMAKE_GENERATOR STREQUAL "MinGW Makefiles") # mingw workaround, as file(TO_NATIVE_PATH ...) is implemented incorrectly # See http://public.kitware.com/Bug/print_bug_page.php?bug_id=5939 string(REPLACE / \\ export_file_backslashes "${export_file}") else() file(TO_NATIVE_PATH "${export_file}" export_file_backslashes) endif() I've written this into patch applied against trunk. Could you test this (I don't use MinGW and don't have...

The following series of patches fill in most of the gaps in the OCaml bindings to libxl, to make them useful for clients such as xapi/xenopsd (from XCP). There are a number of bugfixes to the existing bindings as well. I have an experimental version of xenopsd that successfully uses the new bindings. An earlier version of the first half of the series was submitted to the last by Ian Campbell on