[mrtg] Re: Monitoring Cisco H.323 VOIP gateways
Robert Holley
rholley at cisco.com
Wed Jan 22 18:32:34 MET 2003
David,
Correct me if I'm wrong, but it appears that you are looking for the number
of calls connected at one polling interval (e.g "....poll with MRTG so I end
up
with the number of channels that list a "4" for their status?");
You could try looking at this table.
"isdnSigStatsInCalls" "1.3.6.1.2.1.10.20.1.3.3.1.1"
"isdnSigStatsInConnected" "1.3.6.1.2.1.10.20.1.3.3.1.2"
"isdnSigStatsOutCalls" "1.3.6.1.2.1.10.20.1.3.3.1.3"
"isdnSigStatsOutConnected" "1.3.6.1.2.1.10.20.1.3.3.1.4"
IsdnSignalingStatsEntry ::= SEQUENCE {
isdnSigStatsInCalls Counter32,
isdnSigStatsInConnected Counter32,
isdnSigStatsOutCalls Counter32,
isdnSigStatsOutConnected Counter32,
isdnSigStatsChargedUnits Counter32
}
isdnSigStatsInCalls OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of incoming calls on this interface."
::= { isdnSignalingStatsEntry 1 }
isdnSigStatsInConnected OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of incoming calls on this interface
which were actually connected."
::= { isdnSignalingStatsEntry 2 }
isdnSigStatsOutCalls OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of outgoing calls on this interface."
::= { isdnSignalingStatsEntry 3 }
isdnSigStatsOutConnected OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of outgoing calls on this interface
which were actually connected."
::= { isdnSignalingStatsEntry 4 }
regards
Bob
> -----Original Message-----
> From: mrtg-bounce at list.ee.ethz.ch [mailto:mrtg-bounce at list.ee.ethz.ch]On
> Behalf Of Grabowski, David
> Sent: Wednesday, January 22, 2003 11:01 AM
> To: mrtg at list.ee.ethz.ch
> Subject: [mrtg] Monitoring Cisco H.323 VOIP gateways
>
>
> Using MRTG 2.9.25 on Windows2000 to monitor tons and tons of
> stuff1. Love it.
>
> We've got a couple Cisco 26xx series routers acting as H.323
> voice-over-IP gateways with PRI connections to the PSTN.
>
> I've been exhaustively searching for an OID that will simply give
> me the number of active channels on the PRI. Three cases with
> Cisco TAC later, and I've come up with nothing.
>
> However, I did discover that I can look at the individual B
> channel and determine its status in .1.3.6.1.2.1.10.20.1.2.1.1.2.X
>
> Where 'X' is a particular B channel on the PRI. (For reasons I
> haven't bothered to figure out yet, 'X' is in the range of 30-52)
>
> For each entry, I get an integer that is:
>
> 1 - idle
> 2 - connecting
> 3 - connected
> 4 - active
>
> So, the long and the short of it is -- for all 23 channels, can
> someone help me figure out what to poll with MRTG so I end up
> with the number of channels that list a "4" for their status?
>
> TIA
>
> ---------------------------------------------------
> David Grabowski
> Mizuho Securities USA
> 212-209-9349 (New!)
>
>
> ##################################################################
> ###################
> CONFIDENTIAL: This e-mail, including its contents and
> attachments, if any, are confidential. It is neither an offer to
> buy or sell, nor a solicitation of an offer to buy or sell, any
> securities or any related financial instruments mentioned in it.
> If you are not the named recipient please notify the sender and
> immediately delete it. You may not disseminate, distribute, or
> forward this e-mail message or disclose its contents to anybody
> else. Unless otherwise indicated, copyright and any other
> intellectual property rights in its contents are the sole
> property of Mizuho Securities USA Inc.
> E-mail transmission cannot be guaranteed to be secure or
> error-free. The sender therefore does not accept liability for
> any errors or omissions in the contents of this message which
> arise as a result of e-mail transmission. If verification is
> required please request a hard-copy version.
> Although we routinely screen for viruses, addressees should
> check this e-mail and any attachments for viruses. We make no
> representation or warranty as to the absence of viruses in this
> e-mail or any attachments. Please note that to ensure regulatory
> compliance and for the protection of our customers and business,
> we may monitor and read e-mails sent to and from our server(s).
> ##################################################################
> ###################
>
> --
> Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
> Archive http://www.ee.ethz.ch/~slist/mrtg
> FAQ http://faq.mrtg.org Homepage http://www.mrtg.org
> WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
>
>
--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Archive http://www.ee.ethz.ch/~slist/mrtg
FAQ http://faq.mrtg.org Homepage http://www.mrtg.org
WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
More information about the mrtg
mailing list