similar to: Zaptel DAX?

Heh guys, I just received a T400 card, I've been using a T100 for a little while, and it works fine when using a raw channelized T1. I'm relocating my asterisk machine, and PRI's will only be available, haven't found any good config info for PRI's, can someone point me to PRI config info, or let me know what changes I need to make in order to bring them up, I imagine,

Hi, Is this card the same as the T410P, after all, it's made by Digium. There's one prior reference on the mailint list[1] but it didn't answer the question. There was also an SS7 status report[2] last June but it's doesn't seem to have lead anywhere either. There was post saying an SS7 release was immenent last September[3], but then silence. Any info anyone would like to

On Wed, Jun 26, 2019 at 02:27:15PM +0200, Christoph Hellwig wrote: > The functionality is identical to the one currently open coded in > device-dax. > > Signed-off-by: Christoph Hellwig <hch at lst.de> > Reviewed-by: Ira Weiny <ira.weiny at intel.com> > --- > drivers/dax/dax-private.h | 4 ---- > drivers/dax/device.c | 43

On Wed 10-04-19 09:38:24, Pankaj Gupta wrote: > This patch introduces 'daxdev_mapping_supported' helper > which checks if 'MAP_SYNC' is supported with filesystem > mapping. It also checks if corresponding dax_device is > synchronous. Virtio pmem device is asynchronous and > does not not support VM_SYNC. > > Suggested-by: Jan Kara <jack at suse.cz> >

v2 -> v3: - Rebase on top of the other patches. Rich.

NOTE: not for upstream, yet. v1 -> v2: - Remove the dependency on enabling ACPI, since ACPI is now enabled all the time. Rich.

On Fri, Jun 28, 2019 at 09:27:44AM -0700, Dan Williams wrote: > On Fri, Jun 28, 2019 at 8:39 AM Jason Gunthorpe <jgg at mellanox.com> wrote: > > > > On Wed, Jun 26, 2019 at 02:27:15PM +0200, Christoph Hellwig wrote: > > > The functionality is identical to the one currently open coded in > > > device-dax. > > > > > > Signed-off-by: Christoph

On Tue, May 21, 2019 at 6:43 AM Pankaj Gupta <pagupta at redhat.com> wrote: > > This patch sets dax device 'DAXDEV_SYNC' flag if all the target > devices of device mapper support synchrononous DAX. If device > mapper consists of both synchronous and asynchronous dax devices, > we don't set 'DAXDEV_SYNC' flag. > > Signed-off-by: Pankaj Gupta

DAX is explained in detail here: https://lwn.net/Articles/610174/ This patch adds support to supermin for using a DAX root filesystem. The corresponding libguestfs patches will be posted shortly once I've tested them a bit more. This requires qemu >= 2.6. Unfortunately it's not really a win for a few reasons: - Requires enabling ACPI, which slows everything down by hundreds of

On Tue, Jun 11 2019 at 12:37pm -0400, Pankaj Gupta <pagupta at redhat.com> wrote: > This patch sets dax device 'DAXDEV_SYNC' flag if all the target > devices of device mapper support synchrononous DAX. If device > mapper consists of both synchronous and asynchronous dax devices, > we don't set 'DAXDEV_SYNC' flag. > > 'dm_table_supports_dax' is

On Fri, Jun 28, 2019 at 10:08 AM Dan Williams <dan.j.williams at intel.com> wrote: > > On Fri, Jun 28, 2019 at 10:02 AM Jason Gunthorpe <jgg at mellanox.com> wrote: > > > > On Fri, Jun 28, 2019 at 09:27:44AM -0700, Dan Williams wrote: > > > On Fri, Jun 28, 2019 at 8:39 AM Jason Gunthorpe <jgg at mellanox.com> wrote: > > > > > > >

We have been pretty much able to solve our echo problems, except for the primary mode in which we desire to operate our system. See system diagram at bottom. Prior to making adjustments to cancel echos (all echocancel=no): Call Type Result (Before) --------- --------------- CP <- LEC PRI * TDMoE * FXO -> AP

On Mon, Jun 10 2019 at 5:07am -0400, Pankaj Gupta <pagupta at redhat.com> wrote: > This patch sets dax device 'DAXDEV_SYNC' flag if all the target > devices of device mapper support synchrononous DAX. If device > mapper consists of both synchronous and asynchronous dax devices, > we don't set 'DAXDEV_SYNC' flag. > > Signed-off-by: Pankaj Gupta

Hi I plan to setup an asterisk box to function as a SIP gateway forwarding lots of calls to/from a backend of several other asterisk boxes, each with a TE410 card for PSTN connectivity. It will only gateway the calls into the PSTN gateways. No transcoding is planned - only plain ALAW. How many concurrent calls would you think this can handle? I'm asked to plan a system that can handle

Hi, I'm looking into support for SS7 and I found an article (http://www.openss7.com/news13022002.html) which says that OpenSS7 supports Linux Support Inc's T400P-SS7 Quad T1 and E400P-SS7 Quad E1 PCI interface cards. It also says that Linux Support Inc is the primary sponsor of Asterisk. However I cannot find these cards on the Asterisk hardware page

Good day everyone, A Solution now exists for those of you still looking for the first model of Quad T1/E1 Interface Cards - the T400P and E400P. The T400P and E400P were manufactured by Digium until a few months ago, and were designed and released under the GNU Public License as the Tormenta II by Zapata Telephony. Varion, Inc. is now in full production manufacturing these boards. With the

Anyone care to elaborate on the differences between the T400P and the TE405P? -Darren -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20050908/e817f8bb/attachment.htm

Below you will find, what I believe to be a typical setup with a T100P card. My question is - 1. Is this correct? 2. What kind of phones would be needed here... (Would you have to use Digital phones) And if so what would you recommend. PRI/T1----- | | | ---------------- | | | Channel Bank | | |

Hi, We are trying to validate Asterisk as a media gateway PRI <-> SIP with two T400P (8 T1s) per box. The first experience with BOX1 (Compaq, 2.53 GHz, 1 Gb RAM) and just one T400P was encouraging - on the load test with 3 T1s worth of calls we had on average 75% idle CPU. Not so with BOX2 (Dell, single 2.6 GHz Xeon, 1 Gb RAM, 2 T400P) and BOX3 (Dell, dual 2.6 GHz Xeon, 2 Gb RAM, 2 T400P,

The functionality is identical to the one currently open coded in device-dax. Signed-off-by: Christoph Hellwig <hch at lst.de> --- drivers/dax/dax-private.h | 4 ---- drivers/dax/device.c | 43 --------------------------------------- 2 files changed, 47 deletions(-) diff --git a/drivers/dax/dax-private.h b/drivers/dax/dax-private.h index a45612148ca0..ed04a18a35be 100644 ---