similar to: X100p / OEM X100p In MACs

wondering if anybody knows this......does shady dial work only with a zap interface or can it be configured to be used with SIP or IAX. Nauman -----Original Message----- From: asterisk-users-admin@lists.digium.com [mailto:asterisk-users-admin@lists.digium.com] On Behalf Of asterisk-users-request@lists.digium.com Sent: Thursday, July 08, 2004 5:48 PM To: asterisk-users@lists.digium.com Subject:

Hello There, I *think* i've setuped the AreskiCC2 Calling Card system right , but i've yet to make any calls out of it , i added a rate card , trunk and defined some rates , generated some users , added 10 dollars in them , okay , now i call any number , it asks me to enter my pin , i do , it tells me i have ten $ , right after that it says sorry you dont have enough funds for this call

Hello There, I am trying to get Asterisk to work with Billion ISDN Adaptor, But i couldnt get isdn4linux to work. I am pretty new with isdn card but this is the only available option here right now , I've looked at this post and found that the author has been successful in installation of the same card. Can someone please help me out by giving the author's email address , so i can

I am putting together my first *. I had it running with two other pc's running xlite and setup voicemail and a couple of menus and submenus and had that running well. I had order a couple of oem x100p cards from digitnetworks. I installed them as they said with their voicepet2.2.zip drivers and did the modprobe on zaptel and wcfxo and then ran ztcfg -vv and got this: Zaptel Configuration

Hello There, I'd like to define multiple providers for one dial prefix , like , i want if my one trunk gateway is filled the call is transfered to other ip, how can i achieve it with areskicc.Kindly Help. cheers Thanks Junaid Uppal

On Mon, Oct 21, 2019 at 4:14 AM Alex Hung <alex.hung at canonical.com> wrote: > > We have done some tests on three of Intel + nVidia configuration > systems with OEM _OSI strings removed - while some bugs are still > observed, ex. one out of three has suspend/resume issues, no system > crashes were observed - the biggest issue that worries us. > > The positive results

fyi: I decided to go for a different workaround to fix the runpm issues observed with nvidia gpus with nouveau in the "pci: prevent putting nvidia GPUs into lower device states on certain intel bridges" thread that's on the pci and pm mailing list. Maybe it makes sense to wait for that to land before actually removing the ACPI workarounds here? The workaround I had in this series

On Tue, 2016-04-05 at 13:04 +0100, Richard W.M. Jones wrote: > On Tue, Apr 05, 2016 at 01:47:27PM +0200, Cédric Bosdonnat wrote: > > + let oem_inf = set_free_oem_inf g root scsi_adapter_guid > > "viostor.inf" driverdir in > > Seems better if it was called *get_next*_free_oem_inf? Yes, sounds better. > > (* There should be a key > > *

Hi, This post is to prevent other people that are having trouble with Vista clients from going down a blind alley investigating problems in their samba configurations. After some research I have found (see link below) that there is a general problem for pre-installed OEM editions of Vista Business (and possibly other vista versions) in creating files and folders on network shares. The problem

It seems that checking for oem%d.inf in the DeviceIds registry entry doesn't always list all oemXX.inf files. For example we may have oem1.inf free in the registry key, but used in another one. Also extract this into a separate function for later use to setup another driver. --- v2v/windows_virtio.ml | 52 ++++++++++++++++++++++++++------------------------- 1 file changed, 27 insertions(+),

On Thu, Aug 15, 2019 at 12:19 PM <Mario.Limonciello at dell.com> wrote: > > > -----Original Message----- > > From: Takashi Iwai <tiwai at suse.de> > > Sent: Thursday, August 15, 2019 9:57 AM > > To: Alex Deucher > > Cc: Karol Herbst; Limonciello, Mario; nouveau; Rafael J . Wysocki; LKML; dri-devel; > > Linux ACPI Mailing List; Alex Hung; Ben

On Thu, 15 Aug 2019 18:19:52 +0200, <Mario.Limonciello at dell.com> wrote: > > > -----Original Message----- > > From: Takashi Iwai <tiwai at suse.de> > > Sent: Thursday, August 15, 2019 9:57 AM > > To: Alex Deucher > > Cc: Karol Herbst; Limonciello, Mario; nouveau; Rafael J . Wysocki; LKML; dri-devel; > > Linux ACPI Mailing List; Alex Hung; Ben

We have done some tests on three of Intel + nVidia configuration systems with OEM _OSI strings removed - while some bugs are still observed, ex. one out of three has suspend/resume issues, no system crashes were observed - the biggest issue that worries us. The positive results give us confident to ack the removal of the OEM _OSI strings. While our tests were not able to cover all possible I+N

On Thu, Aug 15, 2019 at 4:34 PM <Mario.Limonciello at dell.com> wrote: > > > -----Original Message----- > > From: Karol Herbst <kherbst at redhat.com> > > Sent: Thursday, August 15, 2019 9:25 AM > > To: Limonciello, Mario > > Cc: Dave Airlie; LKML; Linux ACPI Mailing List; dri-devel; nouveau; Rafael J . > > Wysocki; Alex Hung; Ben Skeggs; David

On Thu, 15 Aug 2019 16:37:05 +0200, Alex Deucher wrote: > > On Thu, Aug 15, 2019 at 10:25 AM Karol Herbst <kherbst at redhat.com> wrote: > > > > On Thu, Aug 15, 2019 at 4:20 PM <Mario.Limonciello at dell.com> wrote: > > > > > > > > There are definitely going to be regressions on machines in the field with the > > > > > in tree

On Tue, 2016-04-05 at 15:13 +0300, Roman Kagan wrote: > On Tue, Apr 05, 2016 at 01:47:27PM +0200, Cédric Bosdonnat wrote: > > It seems that checking for oem%d.inf in the DeviceIds registry > > entry > > doesn't always list all oemXX.inf files. For example we may have > > oem1.inf free in the registry key, but used in another one. > > In my experiments this

On Thu, Aug 15, 2019 at 3:56 PM <Mario.Limonciello at dell.com> wrote: > > > -----Original Message----- > > From: linux-acpi-owner at vger.kernel.org <linux-acpi-owner at vger.kernel.org> On > > Behalf Of Dave Airlie > > Sent: Wednesday, August 14, 2019 5:48 PM > > To: Karol Herbst > > Cc: LKML; Linux ACPI; dri-devel; nouveau; Rafael J . Wysocki;

Hello, I'am using a LSI 1068e OEM version from Super Micro (see lspci). I was able to install a plain CentOS5 with the binary drivers I got from Super Micro. 06:00.0 SCSI storage controller: LSI Logic / Symbios Logic Unknown device 0059 (rev 04) Subsystem: Super Micro Computer Inc Unknown device a180 Flags: bus master, fast devsel, latency 0, IRQ 10 I/O ports at e000

> -----Original Message----- > From: Takashi Iwai <tiwai at suse.de> > Sent: Thursday, August 15, 2019 9:57 AM > To: Alex Deucher > Cc: Karol Herbst; Limonciello, Mario; nouveau; Rafael J . Wysocki; LKML; dri-devel; > Linux ACPI Mailing List; Alex Hung; Ben Skeggs; David Airlie > Subject: Re: [Nouveau] [PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string to >

> On Thu, Aug 15, 2019 at 10:15 AM Karol Herbst <kherbst at redhat.com> wrote: > > > > On Thu, Aug 15, 2019 at 4:13 PM Alex Deucher <alexdeucher at gmail.com> > wrote: > > > > > > On Thu, Aug 15, 2019 at 10:04 AM Karol Herbst <kherbst at redhat.com> wrote: > > > > > > > > On Thu, Aug 15, 2019 at 3:56 PM