similar to: Problem: Digium TDM400 with XOptionsFlex - Line Busy

Hi all, I have hit a wall configuring a TDM400, I have set these up before without issue but today I just can't seem to figure out what I am doing wrong. On an incoming call the following is produced in the Asterisk console with verbose 4 -- Starting simple switch on 'Zap/2-1' Mar 22 16:12:34 NOTICE[2051]: chan_zap.c:6063 ss_thread: Got event 18 (Ring Begin)... Mar 22

Evening all. I'm looking at building an Asterisk system for one of the projects of the Charity where I'm the SysAdmin. The project has two analogue phone lines - BT Featureline Compact, we're in the UK - that I'd like Asterisk to handle. My current quandary is which FXO interface to use. I've been looking at the Digium TDM400P and Sangoma A200, which are similar prices for

Hello everyone! I'm planning on setting up a new system shortly and can't pick the right card... We will have 2 or 3 lines coming in and 7 extensions (GXP2k's). Should I just get 2 or 3 X100P cards? Or do I need the Sangoma A20200 or even the A20200D (Echo cancelation)... I was thinking I'd use a Dell 2.0 GHz machine as the server... If anyone has suggestions as to

Dear R users, Could somebody please help me to find a way of comparing nonlinear, non-nested models in R, where the number of parameters is not necessarily different? Here is a sample (growth rates, y, as a function of internal substrate concentration, x): x <- c(0.52, 1.21, 1.45, 1.64, 1.89, 2.14, 2.47, 3.20, 4.47, 5.31, 6.48) y <- c(0.00, 0.35, 0.41, 0.49, 0.58, 0.61, 0.71, 0.83, 0.98,

v1 was here: https://www.redhat.com/archives/libguestfs/2018-October/msg00047.html v2 was here: https://www.redhat.com/archives/libguestfs/2018-October/msg00051.html v3: - Back to using string/string_format and attribute/attribute_format. - Add both single_element and single_element_format. - Rebased and retested. Rich.

Consolidate and extend the use of funky start_element() etc macros. Rich.

Hi all, Just want to check from the list experienced personal about the Digium HPEC, where I had purchased the HPEC and wish to run with TDM card Sangoma A200. I can't install HPEC to run with Sangama A200 card, even I had changed my hpec file from i686 to i386. The error that I had as bellow; > Found key 'HPEC-XXXXXXXXXX' for 2 channels. > Found valid HPEC licenses for 2

This preliminary patch series adds a libvirt backend to libguestfs. It's for review only because although it launches the guest OK, there are some missing features that need to be implemented. The meat of the patch is in part 4/4. To save you the trouble of interpreting libxml2 fragments, an example of the generated XML and the corresponding qemu command line are attached below. Note the

As far as I can tell, after discussing this matter with other asterisk users in my area, my telco _does_ provide disconnect supervision.. It seems that the problem is actually related to the Sangoma A200 card I'm using, as two other people both using this same card have expressed the same problem.. Are there any other users on this list using the Sangoma A200 FXO port card, and experiencing

v1 was here: https://www.redhat.com/archives/libguestfs/2018-October/msg00047.html However it was broken in a few ways. First of all the documentation was broken because "/**" enhanced comments were not permitted on macros. This is fixed in the new 1/4 patch. Secondly we didn't use single_element() everywhere possible, which is fixed in the new 4/4 patch. Lastly I've

QEMU upstream has broken snapshot=on ... again. These two patches stop using it entirely. Instead we run 'qemu-img create' to create overlay disks as required. Note that the libvirt and UML backends were already doing this: The libvirt backend because <transient/> has never worked, and the UML backend was running uml_mkcow because the UML-equivalent syntax of snapshot=on was

Hello All, Anyone out there using ISDN PRI from either MCI or XO/Allegiance? Gotta make the choice today and the difference per month is only about $25 in favor of MCI. Billing is pretty much the same between the two so I have pretty much no point of reference on which to choose. Any thoughts from anyone experienced with these two compnies would be greatly appreciated! Thanks, Wiley

Hi all, I've got a problem with the nls function. I have an adjustment which works when I fix one of the argument of my function (Xo=150) : *Xo*=150 f<- function (tt*,Xo*,a,b) ifelse(tt<*Xo*,a*exp(-b**Xo*),a*exp(-b*tt)) ajust<-nls(RER~f(tt,*Xo*,a,b),data=data.frame(tt=Ph2[,2*k],RER=Ph2[,2*k+1]),start=list(a=0.5,b=0.014)) But, when I use it as a "normal" parameter (and

This is, I guess, version 3 of this patch series which adds disk labels and hotplugging (only hot-add implemented so far). The good news is .. it works! Rich.

Link to version 1: https://www.redhat.com/archives/libguestfs/2013-February/thread.html#00122 Changes since version 1: - I've pushed two (of the three) code refactoring patches. The third one proved rather hard to move. - selinuxnorelabel option is no more. Instead there is a second internal API (internal_set_libvirt_selinux_norelabel_disks). - fixed bogus commit message -

This rounds off hotplugging support by allowing you to add and remove drives at any stage (before and after launch). Rich.

This patch causes aarch64 to use virtio-pci instead of virtio-mmio. Virtio-pci is considerably faster than virtio-mmio, it's more like how other architectures work, and it supports hotplugging (although it's not likely we'd use the latter feature). I'm not necessarily suggesting that we apply this. Laine (CC'd) has some further patches to libvirt lined up which AIUI would

I''m using Xen 3.4 on Debian Lenny, and a web interface (still in dev), to have a eye on all the stuff. I saw the Xen Cloud project, but I have some questions about it. Can I summarize Xen Cloud like this : "latest" Xen Hypervisor with "improved" API (OCaml replacing python and more stuff) which enhance informations about all Xen hypervisors in same time, to provide a

--- inspector/inspector.c | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/inspector/inspector.c b/inspector/inspector.c index 3583c61df..30d279987 100644 --- a/inspector/inspector.c +++ b/inspector/inspector.c @@ -347,6 +347,7 @@ output_root (xmlTextWriterPtr xo, char *root) char buf[32]; char *canonical_root; size_t size; + int is_bsd; XMLERROR

These patches contain the beginnings of discard (a.k.a. trim or unmap) support. This will allow us to change virt-sparsify to work on disk images in-place (instead of using slow & inefficient copying). The approach used is to add an optional 'discard' parameter to add-drive. It has 3 possible settings: - 'disable' : the default, no discard is done - 'besteffort' :