Ad Widget

Collapse

Voip Gateways

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • fneto
    Junior Member
    • May 2009
    • 1

    #1

    Voip Gateways

    Hi, all!

    I'm new to Zabbix, I've installed Zabbix 1.6 and it's working ok, I have started to monitore some servers and all is ok!

    My doubt is how can I monitor specific options of voip gateways. I already have the SNMP Mib files of the gateways, but I don't know how can I import theses mibs into zabbix and how to configure zabbix to monitor the parameters that I want in the gateways!

    Could someone give and step by step guide to do it?? Or send me the link of documentation about it.

    Thanks!!
  • Kerrygeek
    Senior Member
    • Dec 2008
    • 115

    #2
    fneto,

    I'm monitoring our Cisco VoIP gateways, I tried using the standard Cisco router template that came with Zabbix but ended up modifying it and making my own out of it. If you do snmpwalk on the gateways you'll see what oids are available. You shouldn't have to import anything into Zabbix, just tell it what to look for in the gateways. If you have many gateways, you can set up a template and apply that template to the gateways so you don't have to set up each one individually.

    I ended up doing snmpwalk on a gateway, then doing it again when one of them happened to be down so I could see what changed and what I needed to monitor. It seems like some manufacturers don't document their snmp very well. On ours, I'm monitoring EVERYTHING with snmp: up/down with ping, then status on all the interfaces and bandwidth on the LAN and WAN interfaces. On the PRI channels I'm just checking the status.

    Hope that helps, once I did snmpwalk with one while the PRI was down it made more sense.

    Good luck,
    Kerry

    Comment

    • rbenea
      Member
      • Apr 2008
      • 35

      #3
      Asterisk and OpenSer monitor

      Hi,

      I used zabbix to monitor Asterisk and OpenSer servers.

      In order to do this I created a perl script executed by cron that was dumping the data into a /tmp/zabbix_log.txt file in form of var:value format. From there I used custom UserParams to get the data by the zabbix_agent.

      I hope this helps,
      Rares

      Comment

      • gfoster
        Junior Member
        • Feb 2016
        • 5

        #4
        Originally posted by Kerrygeek
        fneto,

        I'm monitoring our Cisco VoIP gateways, I tried using the standard Cisco router template that came with Zabbix but ended up modifying it and making my own out of it. If you do snmpwalk on the gateways you'll see what oids are available. You shouldn't have to import anything into Zabbix, just tell it what to look for in the gateways. If you have many gateways, you can set up a template and apply that template to the gateways so you don't have to set up each one individually.

        I ended up doing snmpwalk on a gateway, then doing it again when one of them happened to be down so I could see what changed and what I needed to monitor. It seems like some manufacturers don't document their snmp very well. On ours, I'm monitoring EVERYTHING with snmp: up/down with ping, then status on all the interfaces and bandwidth on the LAN and WAN interfaces. On the PRI channels I'm just checking the status.

        Hope that helps, once I did snmpwalk with one while the PRI was down it made more sense.

        Good luck,
        Kerry
        Kerry,

        Would you mind sharing how you monitor PRI status (ie: status 1-3, with 3 being UP and established) ?

        Greg.

        Comment

        • Kerrygeek
          Senior Member
          • Dec 2008
          • 115

          #5
          Hi Greg. I posted that a long time ago, I don't work there anymore and where I work now we don't have any PRIs, only SIP trunks or POTS lines. What I had to do was wait until one of my PRIs went down and then do an snmpwalk on that router to capture the state of the interfaces. When it came back up, I did the same thing again then compared the interfaces to see which ones were down when the PRI was down. I can't tell you exactly which OID it was but if you compare them you'll see it. If you're lucky enough for your PRI to never go down, wait until after hours and pull the plug, it will only take a few seconds to run snmpwalk on the router if you're on the local network. Even remotely it won't take very long.

          Hope that helps, if not, ping me again and I'll get you to send me the results of your snmpwalk and help you find it.

          Good luck!
          Kerry

          Comment

          • gfoster
            Junior Member
            • Feb 2016
            • 5

            #6
            That's the direction I'm heading in. It seems that the OIDs returned by the top-level PRI interface index (1.3.6.1.2.1.10.20.1.3.4.1.2) align with the order presented in 'show isdn status' on the router itself.

            What I'd really like to be able to do is create items/triggers based upon this top level index, so that it's dynamic (if circuits are added or removed), but I think I'm just going to have to snmpwalk the tree, grab the OIDs for the interfaces that are there and create them manually. Not horrible, but not ideal.

            Comment

            Working...