Topics

1

Linux / MOVED: G72x Codecs

« on: March 18, 2014, 05:22:30 AM »

This topic has been moved to Yate based projects.

http://forum.yate.ro/index.php?topic=265.0

2

Yate based projects / G72x Codecs

« on: March 17, 2014, 11:44:19 AM »

Hi,

Here you can find G72x codes for recent yate versions.

Linux x64 Builds:

• 5.0.0
• 5.1.0
• 5.2.0
• 5.4.1

3

Features requests / MOVED: how return first and last name to Yate client by call (db auth)

« on: October 17, 2013, 06:59:34 AM »

This topic has been moved to Yate users hangout place.

http://forum.yate.ro/index.php?topic=213.0

4

Yate IVR / Javascript High System Load

« on: August 27, 2013, 11:20:34 AM »

Hi,

we are currently testing IVR with javascript. Now that everything works like expected from routing and js perspective, the next problem pops ups. Have a look at the graphs, they show system and yate monitoring for the last 7 Days. As you can see the overall load and the context switches all increase over time, also the total mutex used by yate increase pretty linear. The system has almost no load on it...for the last 7 days there was only about 300 calls to process. So I guess for every call my IVR is loaded but not onloaded correctly, so after 300 calls we have too many mutex open and the system load gets 100%

I'm not sure if my script is the problem or yate.. need some more testing?


 

5

Installation from packets/SVN/.exe/AppStore / MOVED: Yate System - Need Advice

« on: June 19, 2013, 05:57:32 AM »

This topic has been moved to Yate based projects.

http://forum.yate.ro/index.php?topic=177.0

6

Yate bugs / Database Modules

« on: January 16, 2013, 07:34:59 AM »

Hello,

I've a strange error with the mysql and the postgre modules. When I start up yate I've got this warnings:

Code: [Select]

<WARN> /usr/lib/x86_64-linux-gnu/yate/mysqldb.yate: file too short
.....
<WARN> /usr/lib/x86_64-linux-gnu/yate/pgsqldb.yate: file too short

but yate does load the modules and they work:

Code: [Select]

<ALL> Plugin::Plugin("mysqldb",true) [0x7ff36291c080]
Loaded module MySQL based on 5.5.28
....
<ALL> Plugin::Plugin("pgsqldb",true) [0x7ff361554080]
Loaded module PostgreSQL
....
Initializing module PostgreSQL
<pgsqldb:INFO> Database account 'dbmain' created poolsize=10 [0x2315470]
<pgsqldb:ALL> 'dbmain.1' intializing connection "host='xxx.xxx.xxx.xxx' port='5432' dbname='xxx' user='xxx' password='xxx'" retry 1 [0x2315470]
<pgsqldb:ALL> Connection for 'dbmain.1' succeeded [0x2315470]
....

The modules do work, we use them from register(cdr,..) and javascript module
I wonder if the waring is just an bug or if my build are not correct, which would be strange because the modules do work...

btw. I'm running on Ubuntu 12.04 LTS with Yate 4.3 (same error with 4.2)

Thanks for the help

7

Yate bugs / ysnmp module stops working after some time

« on: November 30, 2012, 10:55:44 AM »

Hi

the ysnmp module stops woking after sometime, and I can't se any reason for that. I've setup ysnmp with same configs on 3 nodes and two have stopped working after some time... the load on those nodes is almost zero, but they have processed some calls. The last node had no calls, only idle, and on this server ysnmp is still working. Interesting is that the yate still runs on, and works on all nodes, even after ysnmp stops working. With not working I mean that it does not response on any queries. I'll always get timeouts.

Here You can see ysnmp stops working


And as you can see system load it almost zero


I've searched the logs and found this:

Code: [Select]

20121130082613.000612 <snmpagent:WARN> SnmpUdpListener::sendMessage() - could not send message

This is rmanger output after it stops working:

Code: [Select]

status snmpagent
%%+status:snmpagent
name=snmpagent,type=misc;
%%-status
I also tried to run reload from rmanager with no success

I'll increase ysnmp log level and post it later.

BTW. I'm running yate 4.2.1 r5312 on Ubuntu 12.04 amd64

8

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



9

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