Mitel Forums - The Unofficial Source

Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: Belsden on March 13, 2018, 07:13:45 AM

Title: PRTG monitor SIP trunks
Post by: Belsden on March 13, 2018, 07:13:45 AM

Does anyone have this setup so you can have concurrent stats?

TIA

Title: Re: PRTG monitor SIP trunks
Post by: Jordan on March 13, 2018, 12:04:52 PM

Hi Belsden

We do this from a provider side with a monitoring server running a script to query the trunks on the SBC, write the results to an XML file which PRTG then reads from to put data on a graph for us.

Works really well but when I looked at the script over the weekend, I couldn't work out how it worked!

Jordan

Title: Re: PRTG monitor SIP trunks
Post by: Belsden on March 19, 2018, 08:21:57 AM

Hi Jordan,

Thanks very much for the reply! No worries at all, this is going to be out of my remit lol!

Cheers again,
Belsden

Title: Re: PRTG monitor SIP trunks
Post by: StarDestroyer on March 19, 2018, 01:49:38 PM

I'm also very interested in doing this (except I want to use Zabbix, not PRTG). I've poked around the SNMP MIBs hoping to find the number of SIP trunk licenses purchased as well as how many are used on each trunk, but I'm pretty new to looking at that information and have been unable to find anything. I don't know if it's because I'm so inexperienced that I'm not looking in the right place or if it just doesn't exist via SNMP.

In my case, getting the information from the provider would only tell half the story. In addition to the SIP trunk for access to the PSTN, I also have an internal SIP trunk to my Lync server. I really want to keep tabs on my SIP trunk usage because (I believe) an external caller connecting to a Lync conference call will use 2 SIP licenses.

Title: Re: PRTG monitor SIP trunks
Post by: Dogbreath on March 27, 2018, 10:28:13 AM

You can track the global alarm level with an SNMP poll but it's not going to tell you *what* has a problem. I find a Zabbix alert is sufficient - when there's an alarm, something needs investigating regardless although it would be nice to have more detail.

I only have mitelIpera3000AlmLevel on my Zabbix template at the moment. I could add mitelIpera3000AlmNbrCategories as well but i don't think it will really help me.

MITEL-IperaVoiceLAN-MIB::mitelIpera3000AlmLevel.0 = INTEGER: almClear(1)
MITEL-IperaVoiceLAN-MIB::mitelIpera3000AlmDetectDate.0 = Hex-STRING: 07 E2 03 1B 03 14 09 00 00 00 00
MITEL-IperaVoiceLAN-MIB::mitelIpera3000AlmNbrCategories.0 = INTEGER: 0
MITEL-IperaVoiceLAN-MIB::mitelIpera3000TrapAlmShutdownCause.0 = INTEGER: shutdownCauseNotReported(12)
MITEL-IperaVoiceLAN-MIB::mitelIpera3000TrapAlmShutdownDetailedCause.0 = INTEGER: 0
MITEL-IperaVoiceLAN-MIB::mitelIpera3000AlmResetCause.0 = INTEGER: softwareInitiatedReset(2)
MITEL-IperaVoiceLAN-MIB::mitelIpera3000AlmResetCauseBITS.0 = INTEGER: 259
MITEL-IperaVoiceLAN-MIB::mitelIpera3000Applications.2.1.0 = INTEGER: 0
MITEL-IperaVoiceLAN-MIB::mitelIpera3000Applications.2.2.0 = INTEGER: 0

You can get user licenses but not SIP trunk licenses:

MITEL-IperaVoiceLAN-MIB::mitelIpera3000IPUsrLicPurchased.0 = INTEGER: 50
MITEL-IperaVoiceLAN-MIB::mitelIpera3000IPUsrLicUsed.0 = INTEGER: 50
MITEL-IperaVoiceLAN-MIB::mitelIpera3000IPDevLicPurchased.0 = INTEGER: 0
MITEL-IperaVoiceLAN-MIB::mitelIpera3000IPDevLicUsed.0 = INTEGER: 50

Title: Re: PRTG monitor SIP trunks
Post by: Belsden on March 29, 2018, 06:35:48 AM

That's great, cheers for that Dogbreath. I've been playing around with the SNMP stuff, so i'll see if I can drill down some more!

Title: Re: PRTG monitor SIP trunks
Post by: JasonTaylor on April 03, 2018, 02:21:11 PM

We use PRTG and I would be interested to know more if anyone knows how to get this working? 

Title: Re: PRTG monitor SIP trunks
Post by: Dogbreath on April 10, 2018, 11:16:44 AM

Quote from: Dogbreath on March 27, 2018, 10:28:13 AM

You can track the global alarm level with an SNMP poll but it's not going to tell you *what* has a problem.

Time to eat my own words here...you do actually get to see the category of alarm:

Code: [Select]

MITEL-IperaVoiceLAN-MIB::mitelIpera3000AlmLevel.0 = INTEGER: almCritical(4)
MITEL-IperaVoiceLAN-MIB::mitelIpera3000AlmDetectDate.0 = Hex-STRING: 07 E2 04 0A 10 00 1F 00 00 00 00
MITEL-IperaVoiceLAN-MIB::mitelIpera3000AlmNbrCategories.0 = INTEGER: 1
MITEL-IperaVoiceLAN-MIB::mitelIpera3000CatTblIndex.1 = INTEGER: 1
MITEL-IperaVoiceLAN-MIB::mitelIpera3000CatTblAvailable.1 = INTEGER: 1
MITEL-IperaVoiceLAN-MIB::mitelIpera3000CatTblUnavailable.1 = INTEGER: 1
MITEL-IperaVoiceLAN-MIB::mitelIpera3000CatTblLevel.1 = INTEGER: almCritical(4)
MITEL-IperaVoiceLAN-MIB::mitelIpera3000CatTblMinorThresh.1 = INTEGER: 10
MITEL-IperaVoiceLAN-MIB::mitelIpera3000CatTblMajorThresh.1 = INTEGER: 50
MITEL-IperaVoiceLAN-MIB::mitelIpera3000CatTblCriticalThresh.1 = INTEGER: 100
MITEL-IperaVoiceLAN-MIB::mitelIpera3000CatTblName.1 = STRING: "SIP Link Alarm"

I reckon that when there is more than one alarm you would have a .2. .3. alarm table entries as well but yet to catch a system in that state.