similar to: (no subject)

> Hi > > I am running following asterisk installed with apt on Debian 7.1. > > dpkg -l |grep asterisk > ii asterisk 1:1.8.13.1~dfsg-3+deb7u1 > amd64 Open Source Private Branch Exchange (PBX) > ii asterisk-config 1:1.8.13.1~dfsg-3+deb7u1 > all Configuration files for Asterisk > ii

Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Severity: important Tags: security patch When you use xl toolstack, you can't reboot domUs. When you switch back to xm toolstack, than reboot works again. I think the problem with the debian packaged version is the same as in this thread: http://lists.xen.org/archives/html/xen-devel/2011-09/msg01289.html I also think it's a security issue,

On Mon, 2014-04-21 at 15:43 +0200, Sjors Gielen wrote: > Package: xen-utils-4.1 > Version: 4.1.4-3+deb7u1 > Severity: important > > When an LVM LV that serves as the root disk for a Xen DomU contains a boot > loader (or possibly other data) in its volume boot record, pygrub fails to boot > it, printing "Error: boot loader didn't return any data" before exiting.

Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Severity: important When an LVM LV that serves as the root disk for a Xen DomU contains a boot loader (or possibly other data) in its volume boot record, pygrub fails to boot it, printing "Error: boot loader didn't return any data" before exiting. I think this is because of the function "is_disk_image" on line 45 of

On about 25% of inbound calls to a ring group, picking up any one extension as it rings results in dead air. Some details regarding my VoIP network to make the following logs more readable: 192.168.7.130 resolves to the trixbox host. 192.168.7.135 resolves to endpoint 812. 192.168.7.137 resolves to endpoint 811. 192.168.7.138 resolves to endpoint 810. 192.168.7.139 resolves to endpoint 813.

Having an issue with receiving faxes, but when I pass through the fax. Currently, I receive the fax with Digium's Fax for Asterisk, store it and the initiate an outbound call to our fax server. (XMedius Fax). This works, but we would prefer to have Asterisk simply route the call directly to the fax server and take the store and forward out of the equation. When I do that, however, the

Package: xcp-xapi Version: 1.3.2-15 Severity: normal I am trying to pass an SRIOV virtual function in a virtual machine but the attempt fails with the following errors shown in the xcp-xapi.log [20130829T19:29:17.909Z|debug|sriov1|314 UNIX /var/lib/xcp/xapi|VM.start R:9e8e10bd31bb|pciops] PCI devices from other-config:pci to attach: 0/0000:04:00.1 [20130829T19:29:18.012Z|debug|sriov1|314 UNIX

Package: xen-utils-common Version: 4.1.4-3+deb7u1 Severity: normal Dear Maintainer, i changed toolkit to xl, after that i observe that my domU started as HVM domains. I found same problem here: http://mail-index.netbsd.org/port-xen/2012/04/11/msg007216.html When i manualy setup loop devices and specify it as disks in my VM conf file, domU started as PV. -- System Information: Debian Release: 7.1

Hi, Sorry i did't confirm the results sooner. Yes, it's working fine without issues for me. If anyone else can confirm so we can be sure it's 100% resolved. -- Respectfully Mahdi A. Mahdi ________________________________ From: Krutika Dhananjay <kdhananj at redhat.com> Sent: Tuesday, June 6, 2017 9:17:40 AM To: Mahdi Adnan Cc: gluster-user; Gandalf Corvotempesta; Lindsay

Any additional tests would be great as a similiar bug was detected and fixed some months ago and after that, this bug arose?. Is still unclear to me why two very similiar bug was discovered in two different times for the same operation How this is possible? If you fixed the first bug, why the second one wasn't triggered on your test environment? Il 6 giu 2017 10:35 AM, "Mahdi

On 14/05/2020 08:10, John Hughes wrote: > > I am having a problem with one of my callers who is using either g729 > or alaw.  I can do alaw but not g729 so asterisk should negotiate alaw > right?  In fact from the sip debug it looks like it does, but then I > get the dreaded "channel.c:5630 set_format: Unable to find a codec > translation path: (g729) -> (alaw)"

Hi everyone, Here's a follow-up on the two BoFs we've had about doing royalty-free codecs at the IETF. Well, the good new is that the proposal is now in IETF last call until January 20th (see below). No final decision has been made, so it's important to get as much support as possible for the Working Group proposal. You can see the ongoing discussion on the mailing list archive:

Hi everyone, Here's a follow-up on the two BoFs we've had about doing royalty-free codecs at the IETF. Well, the good new is that the proposal is now in IETF last call until January 20th (see below). No final decision has been made, so it's important to get as much support as possible for the Working Group proposal. You can see the ongoing discussion on the mailing list archive:

I?m receiving the following error(s) messages when trying reloading dovecot (Debian wheezy). doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 73: Unknown setting: socket doveconf: Error: managesieve-login: dump-capability process returned 89 Configuration file /etc/dovecot/dovecot.conf : # If you only want to use dovecot-auth, you can set this to "none".

hello *'s, Astcc not workin what is correct format for defining 1-database 2-brands 3-trunks 4-routes i define all these things but not workin may be i define in wrong format.I have FXO card installed.can anyone implement it and also my sip phone generates very loud noise wat is that i tried several settings but not hear any voice just noise. sip.conf [general] context=from-sip port=5060

Hello list, We're currently facing some issues concerning T.38 gateway faxing. This is a device used almost exclusively for receiving faxes. Calls are incoming to asterisk on a SIP trunk (sangoma netborder) using G711A. Gateway mode is activated in the asterisk dialplan towards a Cisco SPA 112 running firmware 1.3.5. We are using asterisk 1.8.13.0 with the T.38 gateway patch applied (I know I

OK. Is this problem unique to templates for a particular guest OS type? Or is this something you see for all guest OS? Also, can you get the output of `getfattr -d -m . -e hex <path>` for the following two "paths" from all of the bricks: path to the file representing the vm created off this template wrt the brick. It will usually be $BRICKPATH/xxxx....xx/images/$UUID where $UUID

The other end is sending g729 even though it was not negotiated. The other end should not do this and it usually seems that the other ends that do send g729. This was recently fixed. See https://issues.asterisk.org/jira/browse/ASTERISK-28139 Richard On Thu, May 14, 2020 at 1:11 AM John Hughes <john at calva.com> wrote: > I am having a problem with one of my callers who is using

Great, thanks! Il 5 giu 2017 6:49 AM, "Krutika Dhananjay" <kdhananj at redhat.com> ha scritto: > The fixes are already available in 3.10.2, 3.8.12 and 3.11.0 > > -Krutika > > On Sun, Jun 4, 2017 at 5:30 PM, Gandalf Corvotempesta < > gandalf.corvotempesta at gmail.com> wrote: > >> Great news. >> Is this planned to be published in next

The fixes are already available in 3.10.2, 3.8.12 and 3.11.0 -Krutika On Sun, Jun 4, 2017 at 5:30 PM, Gandalf Corvotempesta < gandalf.corvotempesta at gmail.com> wrote: > Great news. > Is this planned to be published in next release? > > Il 29 mag 2017 3:27 PM, "Krutika Dhananjay" <kdhananj at redhat.com> ha > scritto: > >> Thanks for that update.