similar to: PCI passthrough error

Hi folks, Recently I learned how to configure libvirt with USB pass-though functionality. In my case I configured my guest domain with this block of code: <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x0c93'/> <product id='0x1772'/> <address bus='1'

Hi list, After wrestling with the voicemail system for a while (Asterisk 1.4.14, Debian etch), I got it to work, but I still have lots of questions, like: * Why can't I delete any voicemail messages? (Response: "Message undeleted.") * Why can't I listen to the messages in the Old folder? * Why can't I use the advanced options? (Response:

Hi folks, My client and I are having a problem getting a portable Esaote ultrasound machine to connect to a Samba server. The unit has an integrated laptop with a Windows XP version that can hardly be modified. Upon delivery the vendor only changed the user name and workgroup for us. When I asked for the user password to make a matching Samba account, the vendor refused because they use

Hi folks, Following an upgrade to Debian wheezy, I'm now running Asterisk 1.8.13.1. As opposed to Asterisk 1.6.2.9 that I ran with squeeze, this version can support IPv6. However, it seems that I can't get it to support both IPv4 and IPv6 at the same time. For example, if in sip.conf I set the bindaddr variable to '::' it will only listen on IPv6 and none of my IPv4-only

Hi folks, Following an upgrade from Debian squeeze to wheezy, and Asterisk 1.6.2.9 to 1.8.13, my server is no longer able to register a connection to a SIP account at my ISP (XS4ALL in the Netherlands). At the same time, it is still able to register a different account with another SIP provider, so it must be that they no longer have the same basic requirements. The relevant part of my

Hi list, After a recent upgrade to Asterisk v1.4.14, my message log is now filling up with the following error messages: <-------------> [Dec 29 17:24:52] WARNING[10655]: chan_sip.c:6645 determine_firstline_parts: Bad request protocol Packet --- (1 headers 0 lines) --- bitis*CLI> <--- SIP read from 82.101.62.99:5060 ---> Cirpack KeepAlive Packet <-------------> Seeing

Hi list, Has anyone been able to get ISDN-BRI support to work reliably on Asterisk 1.4? If so, I'd love to know how you did it (hardware, distro, kernel, modules, versions, config files). I've tried to get it to work on a Debian etch system with an HFC-PCI card and the zaptel package (v1.4.7, also from xorcom.com), but with no luck: all three channels that are created when the

Hi all, On an Asterisk/Zaptel 1.4 system, one way to gather diagnostic info is: ~# cat /proc/zaptel/* Span 1: ZTHFC1 "HFC-S PCI A Zaptel Driver card 0 [TE]" (MASTER) AMI/CCS 1 ZTHFC1/0/1 Clear (In use) 2 ZTHFC1/0/2 Clear (In use) 3 ZTHFC1/0/3 HDLCFCS (In use) Span 2: ZTHFC2 "HFC-S PCI A Zaptel Driver card 1 [TE]" AMI/CCS 4 ZTHFC2/0/1 Clear 5 ZTHFC2/0/2

Hi list, Can someone please explain how to get one touch recording (automon) to work reliably? I'm using Asterisk 1.4.14 on a Debian etch system. My current configuration includes the following settings: In /etc/asterisk/sip.conf: [2000] ; Siemens Gigaset S675 IP wireless SIP phone. type=friend secret=1234 context=phones-j dtmfmode=rfc2833 qualify=yes

Hi all, My latest Asterisk system is based on Debian squeeze with Asterisk 1.6.2.6-1 and SIP only. One of my favorite features that I had working with Asterisk 1.4 is the PrivacyManager. However, this was not straightforward, because anonymous SIP calls arrive with ${CALLERID(num)} = "anonymous", instead of being blank. So, to get it to work I added the first three rules to

Hello, We encountered a problem while testing SRIOV on kubevirt [1]: We are currently using the Device "hostdev" generic options to pass-through the VF to the guest. It is not done through the "interface" (with type hostdev) because that option requires access to the PF which is not available in our case (the VF is moved to the container namespace where libvirt runs, but not

Hi list, Now that I've got my Asterisk server to recognize my HFC-PCI card, I've run into some serious problems. The first thing I noticed was this message that would show up every five seconds on the CLI: Dec 27 15:46:42 WARNING[12484]: chan_zap.c:2512 pri_find_dchan: No D-channels available! Using Primary channel 3 as D-channel anyway! == Primary D-Channel on span 1 down

Hi list, Before purchasing a number of Siemens DECT SIP phones, the Gigaset S675 IP, I read that the problems with MWI had been fixed with the latest firmware version (see http://www.voip-info.org/wiki/view/Siemens+Gigaset+S675IP). Now I'm not so sure that's the case. After setting up a network mailbox for one of these phones, as well as an Asterisk voicemail account (ext.

Hi, I've been using libvirt (versions 0.9.11.5, and recently upgraded to 0.10.2), and have been attaching an SR-IOV VF to my VM with the following device configuration: <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address domain='0x0000' bus='0x07' slot='0x10' function='0x0'/>

I'm trying to pass-through my VGA card to a guest session. I found: http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM - which is very frustrating because there's no date on the documentation. I suspect it's old. It does clearly say that you must have VT-d support for pci pass-through. It then goes on to say "Some work towards allowing this ["software

Hi list, Hopefully, some of our Dutch members can help with this one. I'm also based in the Netherlands and am using a Sipura (Linksys) SPA-3000 (firmware v3.1.10(GWd)) as a PSTN to VoIP gateway for my Asterisk test system. It works fine, except that the Called ID (CID) is not working. I'm aware that KPN (our local telco) requires a separate subscription to activate CID on POTS

Hi, I try to add 2 VF functions to VM via network. Livirt networks: vnet0: <network> <name>vnet0</name> <forward mode='hostdev' managed='yes'> <pf dev='eth0'/> </forward> </network> vnet1: <network> <name>vnet0</name> <forward mode='hostdev' managed='yes'> <pf

Hi folks, My site uses puppetmaster 3.2.3 together with Debian wheezy, but I want a few packages from wheezy-backports, like iceweasel and libreoffice. The former I''ve installed as follows: package { "iceweasel": ensure => ''22.0-1~bpo70+1'', provider => ''apt'', install_options

Hi all, For a while now I've been using Asterisk together with HFC-PCI cards (Cologne chipset) for Euro-ISDN BRI support. However, I do not consider this to be the most reliable solution and believe that the most stubborn problems have always been software related. If my clients are willing to spend a bit more money on different hardware, what do you think the best solution would be?

Hi all, Previously, I had the PrivacyManager working for me exactly as would be expected, but after upgrading the OS to Debian lenny and Asterisk to v1.4.21.2 that's no longer the case. Anonymous callers are still confronted with the PrivacyManager, but now no matter what I set the minlength value to, e.g.: exten => jaap,n,PrivacyManager(1,1) ... (I'm not using a