Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-3431

[PATCH] Support kamcmd and kamctl in kamailio local script

Details

    • Improvement
    • Resolution: Fixed
    • Minor
    • None
    • Community Edition, Professional Edition
    • Unix Agent

    Description

      With kamailio 5 the kamctl fifo was removed and kamcmd should be used to access kamailio. This patch makes scripts/agent-local/kamailio work with both kamctl and kamcmd.

      It looks for kamcmd in the default install path (/usr/sbin/kamcmd), since which outputs stuff on centos if it fails to find a file.

      Attachments

        Activity

          [OBS-3431] [PATCH] Support kamcmd and kamctl in kamailio local script

          Thanks, commited in r11881.

          landy Mike Stupalov added a comment - Thanks, commited in r11881.

          Well - there is a patch attached - so I was waiting for you.

          pnlarsson Niklas Larsson added a comment - Well - there is a patch attached - so I was waiting for you.

          Hi Niklas Larsson, we have not received the additional information requested earlier from you in this issue 'With kamailio 5 the kamctl fifo was removed and kamcmd should be used to access kamailio. This patch makes scripts/agent-local/kamailio work with both kamctl and kamcmd.

          It looks for kamcmd in the default install path (/usr/sbin/kamcmd), since which outputs stuff on centos if it fails to find a file.'!

          Issues without your response will be closed within 2 weeks.

          landy Mike Stupalov added a comment - Hi Niklas Larsson, we have not received the additional information requested earlier from you in this issue 'With kamailio 5 the kamctl fifo was removed and kamcmd should be used to access kamailio. This patch makes scripts/agent-local/kamailio work with both kamctl and kamcmd. It looks for kamcmd in the default install path (/usr/sbin/kamcmd), since which outputs stuff on centos if it fails to find a file.'! Issues without your response will be closed within 2 weeks.

          Please make and attach additional information about the device:

          • full snmp dump from device:

            snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

            If device not support SNMP version 2c, replace -v2c with -v1.

          • If you have problems with discovery or poller processes, please do and attach these debugs:

            ./discovery.php -d -h <device>
            ./poller.php -d -h <device>

          • additionally attach device and/or vendor specific MIB files

          Note, this comment is added automatically.

          bot Observium Bot added a comment - Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files Note, this comment is added automatically.

          People

            landy Mike Stupalov
            pnlarsson Niklas Larsson
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: