Summary: | ASTERISK-04581: [patch] Daemon for zaptel status | ||
Reporter: | Tilghman Lesher (tilghman) | Labels: | |
Date Opened: | 2005-07-13 13:12:42 | Date Closed: | 2011-06-07 14:10:49 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Core/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) 20050713__zaptel_Makefile.diff.txt ( 1) ztstatd.c | |
Description: | This is mostly useful for remote network monitoring daemons. It simply prints the alarms on each configured span, when remotely connected on TCP port 5039. Note that you can keep track of the status of a PRI by using the manager interface, but there was no way to keep track of the status of the underlying T1 circuit (or the status of circuits not using PRI, like a channel bank). | ||
Comments: | By: twisted (twisted) 2005-07-13 13:30:21 so I can't run "zap show status" from the manager and get the alarms? Sure I can! stanker*CLI> zap show status Description Alarms IRQ bpviol CRC4 TE410P (PCI) Card 0 Span 1 OK 0 0 0 TE410P (PCI) Card 0 Span 2 OK 0 0 0 TE410P (PCI) Card 0 Span 3 OK 0 0 0 TE410P (PCI) Card 0 Span 4 RED 0 0 0 Which also means I can do that from the manager interface By: Tilghman Lesher (tilghman) 2005-07-13 14:21:18 Ah, I hadn't seen that, and it apparently wasn't in when I wrote the command. Oh, well. |