similar to: Usage of 'alarm_(init|set|commit)'

> +22 = Gamatronic UPSs with alarm interface > + [CP=RTS] [OL=CTS] [LB=\-DCD] [SD=DTR] > + > +22 = CyberPower SL seriess > + [CP=RTS] [OL=CTS] [LB=\-CAR] [SD=DTR] > + > + This part of the patch is no good. While TIOCM_CAR is equivalent to TIOCM_CD (at least in some implementations) CAR certainly isn't handled the same as DCD by genericups. It won't be

The list of status bits we're seeing has increased over the years. Currently for instance, the usbhid-ups driver has defined no less than 20 status bits (and I intend to add two more in the next couple of days, FRANGE and FANFAIL): #define STATUS_ONLINE 0x00001 /* on line */ #define STATUS_DISCHRG 0x00002 /* discharging */ #define STATUS_CHRG 0x00004 /*

Device Manufacturer: NHS Device Name: Laser Senoidal 5000VA upsc output when the UPS is in normal condition: battery.charge: 100 battery.current: 0.4 battery.date: 12292015 battery.runtime: 00000 battery.runtime.low: 59940 battery.temperature: 00 battery.voltage: 163.4 device.mfr: NHS Sistemas de Energia device.model: Laser Senoidal 5000VA device.type: ups driver.name: gamatronic

Here are a series of my recent changes to NUT. The first few in the set are primarily little fixes and improvements. In among those are a few for .gitignore files which of course you can ignore for SVN, and there's one for a commit to a generated file which of course should not be tracked in any VCS. Then there are a couple or three to do with generating the header files used by

Device Manufacturer: NHS Device Name: Expert C Online 6000 upsc output: battery.charge: 100 battery.current: 0.6 battery.date: 01012014 battery.runtime: 00000 battery.runtime.low: 59940 battery.temperature: 29 battery.voltage: 210.5 device.mfr: NHS Sistemas de Energia device.model: EXPERT GIII 8kVA device.type: ups driver.name: gamatronic driver.parameter.pollinterval: 20

Below the answers: > This is the same as https://github.com/networkupstools/nut/issues/254 , right? Yes, this UPS is the same. > Does battery.runtime only get updated when on battery power, or is this with a different load? > battery.runtime.low: 59940 > battery.temperature: 00 Yes, this time time is updated on battery power, This is a dynamic counter that changes with a different

On Nov 12, 2014, at 5:46 AM, Thiago Wiezbicki <thiagowzb at gmail.com> wrote: > > > Device Manufacturer: NHS > Device Name: Expert C Online 6000 > > upsc output: > > battery.charge: 100 > battery.current: 0.6 > battery.date: 01012014 > battery.runtime: 00000 Quick question: does "battery.runtime" update when the device is on battery, or is this

Hello, I am missing any description of zaptel/DAHDI alarms. The TE200 series user manual contains only a description of LEDs states. These alarms states are visible in zttool/dahditool or in astersick CLI (zap show status) and I wonder what is the real meaning of these alarms for E1 channel. Possible alarm states (based on zaptel.h 1.2): 1. No alarms 2. Recovering from alarm 3. In loopback

Asterisk is getting red alarms on my T1, sometimes once or twice a day, but today it happened 5 times. Even once is too many. Every call in progress is dropped. Please help! What do I need to do? What can I try? I've googled and searched this list and can't find anything. Here's an example from the logs: Feb 7 13:37:54 WARNING[32451] chan_zap.c: Detected alarm on channel 6: Red

Greetings to all developers of the Network UPS Tools, and Merry Christmas greetings to those of you who celebrate! I have been looking in to your work from time to time, and I am very impressed with your efforts. I think this is a good time to officially supply the required information about Gamatronic products to the community. Furthermore, I would like to know how our company may contribute

About every hour I see the yellow alarms on all or a number of channels of my PRI which is connected to the dutch telephony network, Asterisk keeps on working fine.... Here's an example where channel 1-24 went into alarm: WARNING[90124]: File chan_zap.c, Line 4139 (handle_init_event): Detected alarm on channel 1: Yellow Alarm WARNING[90124]: File chan_zap.c, Line 4139 (handle_init_event):

Julius: I just realized after committing Michal's patch that you have a more comprehensive patch on the tracker that approaches this piece of code differently. We can go ahead and apply the following patch to the trunk if you still think it's relevant: https://alioth.debian.org/tracker/index.php?func=detail&aid=303719&group_id=30602&atid=411544 If you have a newer version of

Arjen de Korte wrote: > > + * drivers/apc-hid.c: > + - Commented out the 'fullycharged' status. If anyone can explain the > + use of this, please step forward. This flag is defined on p.36 of the "Universal Serial Bus Usage Tables for HID Power Devices", Release 1.0 November 1, 1997, a USB standards document available on the web. The document defines this

Hi everyone! I have a Digium Card TDM410 But, it appear for me this massege chan_dahdi.c:8061 handle_alarms: Detected alarm on channel 3: Red Alarm But my line is ok! But sometimes it back sig_analog.c:3807 analog_handle_init_event: Alarm cleared on channel 2 But it again back to red alarm. What can be happen? My lines is all ok! But when I put on Digium Card TDM410 is very inconsistent

Calling out on PSTN over a TDM400P seems to generate a Red Alarm - whatever that is. I have another extension on the PSTN, and I can dial out over that. zttool shows no alarms. asterisk*CLI> zap show status Description Alarms IRQ bpviol CRC4 Fra Codi Options LBO Wildcard TDM400P REV I Board 1 OK 0 0 0 CAS Unk YEL 0 db

Humm, if I put a filter in this lines, maybe back? 2016-01-05 12:36 GMT-02:00, Ryan, Travis <RyanT at oscarwinski.com>: > >> -----Original Message----- >> From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users- >> bounces at lists.digium.com] On Behalf Of Vitor Mazuco >> Sent: Tuesday, January 05, 2016 9:21 AM >> To: Asterisk Users Mailing

hi,all i have just set up asterisk 1.6.0.7 rc1 with spandsp 0.0.5 pre4 to ReceiveFAX, link to a E1 (DE410P) using dahdi this can receive the fax from E1 successfully, but i see many error message in the log like this: [Mar 16 09:24:38] ERROR[23540] channel.c: ast_read() called with no recorded file descriptor. when i receive a 5 pages fax, i will see this error message over 200 lines..... it

Here is the scenario: Asterisk 1.14.13; zaptel 1.4.6; Digium TE120P (same problem with various previous versions; same problem with different TE120P cards). The customer has a partial (10 B-Channel) PRI that when it is busy (eight or more B channels in use), tends to fail as shown below... [Jan 26 23:00:31] ERROR[31893] chan_zap.c: Write to 28 failed: Unknown error 500 [Jan 26 23:00:31]

Hello, We are having issues with a NEW Sangoma A108D: -- Executing [691918892 at pbx1:1] Dial("SIP/xtravoip200-009d24b0", "DAHDI/g0/691918892|30|m") in new stack [Oct 1 10:04:43] WARNING[14171]: channel.c:3170 ast_request: No translator path exists for channel type DAHDI (native 76) to 256 [Oct 1 10:04:43] WARNING[14171]: app_dial.c:1237 dial_exec_full: Unable to create

Hello! I am trying to configure my digium TE220 dual-span pci express card with Dahdi. I seemed to have managed to set up the card with the Dahdi kernel, as demonstrated by executing dahdi_scan: [1] active=yes alarms=RED description=T2XXP (PCI) Card 0 Span 1 name=TE2/0/1 manufacturer=Digium devicetype=Wildcard TE220 (4th Gen) location=Board ID Switch 0 basechan=1 totchans=31 irq=16