Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - vankooch

Pages: 1 2 3 [4]
46
Yate bugs / Re: SNMP and Database
« on: November 07, 2012, 02:07:56 PM »
Hi,

thx for the review. I'm not really getting your point. Are there any downsides? Snmptable is part of net-snmp which is the open source reference implementation of SNMP, can't deal with it and many other os and tools relay on that. So it would be great to have that function. It would be also possible not to use a table at all, and just use snmpwalk, but I think table do a better work. The main reason for me is that I'm currently creating a zabbix template for yate which does not work fully, because of that.

47
Installation from packets/SVN/.exe/AppStore / Re: Ubuntu Packages
« on: November 07, 2012, 01:52:15 PM »
Quote
For OP (vankooch), perhaps looking at the OpenWRT's Makefile for YATE will shed some lights for you. Good luck.

thx for the tip. On the first setup I've forked the deb packages build from the debian voip team, which are outdated. I've also watched the Make file on FreeBSD. I'll have look at the pkg for OpenWRT

I can understand diana, that she don't what to split it too many packages, because it could get wired for the user. On the other side I can understand asymtrixs and I think a normal installation would be >70 modules... which is also too much for avg. user.

How about splitting the packages a bit more in to scenarios, like server, client... Assuming a client installation is alway a GUI version, including jabber client modules, google voice client modules and vice versa for the server package.

  • libyate: lib file
  • Yate: binary,shared,man
  • Yate-dev: yate-config, includes
  • Yate-doc: docs
  • Yate-core: Rest of modules
  • Yate-client: Client files (gtk,..),  jabber, google voice client modules
  • Yate-server: jabber,google server modules, monitoring, cpuload,ysnmp
  • Yate-scrips: sample scripts, javascript module
  • Yate-pgsql: Postgree Driver
  • Yate-mysql: Mysql Driver
  • Yate-openh323: OpenH323 Chan
  • Yate-signaling: ysigchan, mgcpca, mgcpgw, ciscosm, sigtransport, lksctp, isupmangler

The contra is that we have modules packages and scenario packages. But we could merge yate-server and yate-server.
Btw I totally forgot the card drivers, like dahdi... never used them

For Information:

Update:

Mandriva Packages from Null Team:
Code: [Select]
%package alsa
%package gsm
%package speex
%package h323
%package isdn
%package lksctp
%package openssl
%package zlib
%package pgsql
%package mysql
%package client-common
%package qt4
%package scripts


Options on FreeBSD:
Code: [Select]
OPTIONS=MYSQL "MySQL Database support" off \
PGSQL "PostgreSQL Database support" off \
SCTP "Stream Control Transmission Protocol" on \
AMR_NB "AMR Narrow Band encoder (opencore)" off \
ILBC "Enable iLBC codec" off \
SPANDSP "Enable Spandsp faxing support" off \
DAHDI "Dahdi driver" off \
H323 "H323 software channel/protocol support" off \
SSL "Enable SSL support" off \
ALSA "Enable ALSA channel support" off

OpenWRT, if I get it right you can build every modules separately and install it as plugin.   
Code: [Select]
$(eval $(call BuildPackage,$(PKG_NAME)))
$(eval $(call BuildPackage,$(PKG_NAME)-collection-basic))
$(eval $(call BuildPackage,$(PKG_NAME)-scripts-php))
$(eval $(call BuildPackage,$(PKG_NAME)-scripts-perl))
$(eval $(call BuildPackage,$(PKG_NAME)-scripts-python))
$(eval $(call BuildPackage,$(PKG_NAME)-sounds))
$(eval $(call BuildPlugin,accfile,server,SIP or H.323 client (from file),))
$(eval $(call BuildPlugin,alsachan,client,ALSA Sound Channel,+alsa-lib))
$(eval $(call BuildPlugin,amrnbcodec,,AMR-NB Codec,@BROKEN)) # Missing amr-nb library
$(eval $(call BuildPlugin,analog,server,Analog (e.g. POTS) Channel,))
$(eval $(call BuildPlugin,analogdetect,server,Analog Data Detector,))
$(eval $(call BuildPlugin,analyzer,,Test Call Generator and AQ Analyzer,))
$(eval $(call BuildPlugin,callcounters,server,Count Active Call Legs,))
$(eval $(call BuildPlugin,callfork,,Call Forker,))
$(eval $(call BuildPlugin,callgen,,Call Generator,))
$(eval $(call BuildPlugin,ccongestion,server,Accept Status from Installed Engine Monitors,))
$(eval $(call BuildPlugin,cdrbuild,,Call Detail Record Builder,))
$(eval $(call BuildPlugin,cdrfile,,Call Detail Record to File,))
$(eval $(call BuildPlugin,ciscosm,server,SS7 Support,))
$(eval $(call BuildPlugin,clustering,server,Clustering Server Support,))
$(eval $(call BuildPlugin,conference,,Conference Room Mixer,))
$(eval $(call BuildPlugin,cpuload,server,Monitor CPU load and Inform Yate,))
$(eval $(call BuildPlugin,dbpbx,server,PBX IVR and Multi-routing from Database,))
$(eval $(call BuildPlugin,dbwave,server,Wav Media for DB Storage,+$(PKG_NAME)-mod-wavefile))
$(eval $(call BuildPlugin,dumbchan,,Dummy Channel,))
$(eval $(call BuildPlugin,enumroute,,ENUM Routing,))
$(eval $(call BuildPlugin,extmodule,,External Module Handler,))
$(eval $(call BuildPlugin,faxchan,,Spandsp Fax Channel,+libspandsp))
$(eval $(call BuildPlugin,filetransfer,,File Transfer Driver,))
$(eval $(call BuildPlugin,gsmcodec,,GSM Codec,+libgsm))
$(eval $(call BuildPlugin,h323chan,,Open H.323 Channel,+libopenh323 @BROKEN)) # libopenh323 doesn't create package or stagin_dir includes or libs
.....

48
Yate bugs / SNMP and Database
« on: November 05, 2012, 06:54:09 AM »
Hi,

I've setup the ysnmp and monitoring module. It work as expected, but I still have a problem when displaying the Database table.
It looks like the MIBs file is outdated. I've build Yate from SVN checked out on Revision: 5312 and I'm using the MIBS file in version: 201204242240Z

Code: [Select]
snmptable -v 2c -c public yate1.server YATE-MIB::databaseTable
SNMP table: YATE-MIB::databaseTable

 databaseIndex databaseAccount queriesCount failedQueries errorQueries queryExecTime
             1          dbone            0             0            0 0 miliseconds
 YATE-MIB::databaseTable: WARNING: More columns on agent than in MIB

Other tables work without any problems:

Code: [Select]
snmptable -v 2c -c public yate1.server YATE-MIB::activeCallsTable
SNMP table: YATE-MIB::activeCallsTable

 callEntryIndex callEntryID callEntryStatus callEntryCaller    callEntryCalled callEntryDuration callEntryPeerChan
              1    sip/8005        answered        XXXX                   XXXX      3917 seconds          sip/8006
              2    sip/8006        answered        XXXX                   XXXX      3917 seconds          sip/8005
              3    sip/8424        answered        XXXX                   XXXX      2904 seconds          sip/8425
........

When I snmpwalk through the database table I get this:

Code: [Select]
snmpwalk -v 2c -c public yate1.server YATE-MIB::databaseTable
YATE-MIB::databaseIndex.1 = Counter32: 1
YATE-MIB::databaseAccount.1 = STRING: dbone
YATE-MIB::queriesCount.1 = Counter32: 0
YATE-MIB::failedQueries.1 = Counter32: 0
YATE-MIB::errorQueries.1 = Counter32: 0
YATE-MIB::queryExecTime.1 = INTEGER: 0 miliseconds
YATE-MIB::tooManyQueriesAlarms.1 = Counter32: 0
YATE-MIB::tooManyFailedQueriesAlarms.1 = Counter32: 0
YATE-MIB::tooManyErrorQueriesAlarms.1 = Counter32: 0
YATE-MIB::queryExecTooLongAlarms.1 = Counter32: 0
YATE-MIB::noConnectionAlarms.1 = Counter32: 0
YATE-MIB::queriesCountThreshold.1 = Counter32: 1000
YATE-MIB::failedQueriesThreshold.1 = Counter32: 500
YATE-MIB::errorQueriesThreshold.1 = Counter32: 500
YATE-MIB::queryExecTimeThreshold.1 = Counter32: 30000 miliseconds

So I get much more informations than cols on the table. If I try to display the MIB, it looks like if there where groups nested in the YATE-MIB::databaseTable table. I guess we should ungroup YATE-MIB::databaseAlarmCounters and YATE-MIB::databaseThresholds.
In the MIB file we have on line 1251
Code: [Select]
DatabaseEntry ::= SEQUENCE {
databaseIndex Counter32,
databaseAccount DisplayString,
queriesCount Counter32,
failedQueries Counter32,
errorQueries Counter32,
queryExecTime INTEGER,
databaseAlarmCounters DatabaseAlarmCounters,
databaseThresholds DatabaseThresholds
}

I guess when removing the groups and add them as simple column it should work. The MIBS file could look like this, but I guess the ysnmp/monitoring module needs an update, too?

Code: [Select]
DatabaseEntry ::= SEQUENCE {
databaseIndex Counter32,
databaseAccount DisplayString,
queriesCount Counter32,
failedQueries Counter32,
errorQueries Counter32,
queryExecTime INTEGER,
tooManyQueriesAlarms Counter32,
tooManyFailedQueriesAlarms Counter32,
tooManyErrorQueriesAlarms Counter32,
queryExecTooLongAlarms Counter32,
noConnectionAlarms                 Counter32,
        queriesCountThreshold Counter32,
failedQueriesThreshold Counter32,
errorQueriesThreshold Counter32,
queryExecTimeThreshold Counter32
}

Update:

I've edit the YATE-MIB.txt and snmp_mib.conf to match the new table layout and now it works. I have attached the patch files.

Code: [Select]
% snmptable -v 2c -c public  yate1.server YATE-MIB::databaseTable
SNMP table: YATE-MIB::databaseTable

 databaseIndex databaseAccount queriesCount failedQueries errorQueries  queryExecTime tooManyQueriesAlarms tooManyFailedQueriesAlarms tooManyErrorQueriesAlarms queryExecTooLongAlarms noConnectionAlarms queriesCountThreshold failedQueriesThreshold errorQueriesThreshold queryExecTimeThreshold
             1          dbone           22             0            0 2 milliseconds                    0                          0                         0                      0                  0                  1000                    500                   500     30000 milliseconds





49
Installation from packets/SVN/.exe/AppStore / Ubuntu Packages
« on: October 29, 2012, 02:27:21 PM »
Hi,

I'm building Yate debs for Ubuntu for a some time and now I want to setup a new PPA on lauchpad. As Yate has a lot of modules and it can be used for a wide range of usecases, I've split them in different groups/debs. The problem is that I just use some limited working scenario. To have a correct grouping I could need some help.

Current Debs:
  • Yate: binary,shared,man
  • libyate: lib file
  • Yate-dev: yate-config, includes
  • Yate-doc: docs
  • Yate-client: Client files (gtk,..)
  • Yate-scrips: sample scripts
  • Yate-pgsql: Postgree Driver
  • Yate-mysql: Mysql Driver
  • Yate-openh323: OpenH323 Chan
  • Yate-javascript: Javascript module
  • Yate-gvoice: Google Voice module
  • Yate-jabber: Jabber modules
  • Yate-signaling: ysigchan, mgcpca, mgcpgw, ciscosm, sigtransport, lksctp, isupmangler 
  • Yate-monitoring: cpuload, monitoring, ysnmp
  • Yate-core: Rest of modules

This is only a starting point so if you have any ideas you are welcome!

Update:
You can finde the ppa under:
https://launchpad.net/~sico/+archive/yate

Pages: 1 2 3 [4]