Messages

31

Other Yate server issues / Re: Can't make a call connected

« on: March 11, 2013, 06:26:42 AM »

The return value is wrong....

Code: [Select]

"sip\sip:mydomainuser105@192.168.6.225:62465" -> wrong
"sip/sip:mydomainuser105@192.168.6.225:62465" -> correct

As you can see in your log it is / and not \ after the channel type.

Code: [Select]

<sip/2:WARN> Could not create party for 'sip:mydomainuser105@192.168.6.225:62465' [013AC8A8]


32

Yate users hangout place / Re: Yate client cannot connect to the server

« on: March 11, 2013, 06:22:51 AM »

without any information nobody can help you...

33

Linux / Re: Half success

« on: February 20, 2013, 11:39:50 AM »

Pulseaudio for Yate his on his way. Have a look at:

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

34

Features requests / Re: IPv6

« on: February 19, 2013, 12:28:52 PM »

Is the RFC ready for voip ovep ipv6, I mean is there any sip/ss7 stack out there which supports ipv6, would be interesting to know. Or is just a OS problem?

35

Features requests / Re: Pulseaudio support

« on: February 19, 2013, 12:26:28 PM »

Great news and work!

36

Other Yate server issues / Re: How to change param of call.route in regfile module ?

« on: February 19, 2013, 12:25:08 PM »

If you want to add any new parameters you need to use it with copyparam, which copyies the params from ex. preroute to route and cdr msg.
And as I know it is not possible to copy parameters from regfile.conf to any other msg, out of the box, but I'm not 100% about that.
If you plan to use database later, I would start on that, so you have the email in the db and you can access it from your routing function in register.conf

37

Other Yate server issues / Re: Cann't Store cdr information in MySql database

« on: February 19, 2013, 12:17:54 PM »

Hi,

you do not need to add this line on yate.conf

Code: [Select]

[module]
mysqldb.yate=true
register.yate=true

Yate loads every module which is in the modules dir.

You also need to have cdrbuild module for cdrs, make sure it is loaded and you have cdrbuild.conf configured.

And it is not call.cdr = on it is call.cdr=yes for all handlers in register.conf so you need this:

Code: [Select]

; engine.timer: bool: Activate handler on the "engine.timer" message
engine.timer=yes

; call.preroute: bool: Activate handler on the "call.preroute" message
call.preroute=no

; call.route: bool: Activate handler on the "call.route" message
call.route=no

; call.cdr: bool: Activate handler on the "call.cdr" message
call.cdr=yes

It is a big confusing with the bool values in yate, but mostly it is yes or enable and not on/off
If you still have errors please post the yate log output, too.

38

Linux / Re: (Self) Registerless Account?

« on: January 16, 2013, 08:27:20 PM »

Hi,

please use a more recent version of yate, version 2.2 is outdated, current stable is 4.3.
You can add a ppa like: https://launchpad.net/~sico/+archive/yate/
or build from source on your own.

39

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

40

Installation from packets/SVN/.exe/AppStore / Re: Ubuntu Packages

« on: January 15, 2013, 06:41:14 PM »

Hi,

sorry for the delay. I've updated the ppa. Please have a look at it.

https://launchpad.net/~sico/+archive/yate

* pwlib and openh323 are also included

as virrus says

I will be happy to see some critic and suggestions about it too

41

Yate bugs / Re: ysnmp module stops working after some time

« on: January 10, 2013, 08:24:25 AM »

Sorry for the late response...

There is no socket running

Code: [Select]

sudo netstat -nulp | fgrep 161
- none -

After a restart of yate the socket is running:

Code: [Select]

sudo netstat -nulp | fgrep 161
udp        0      0 xx.xx.xx.xx:161        0.0.0.0:*                           8460/yate

Please let me know if you need any other debug.

42

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

43

Yate bugs / Re: SNMP and Database

« on: November 27, 2012, 12:47:30 PM »

Ok I've discussed it with the guys from net-snmp and they told me that having to bug at all, net-snmp works as it should...
Then finally one guy in the #net-snmp chan told me that having a sequence within a table is wrong.

[7:14pm]vankooch: Hi, I'm building a MIB for a application.. I want to know if it is possible to have sequence to be part of a table?
...
[7:37pm] rstory-work: vankooch: no, you can't have a sequence inside a sequence..
[7:37pm] rstory-work: you have to have a second table with the same index as the first plus a secondary index..
[7:38pm] vankooch: ok so I'll have two tables?
[7:38pm] rstory-work: yes

...

44

Yate bugs / Re: transcoding from A-law to u-law not working

« on: November 23, 2012, 08:25:09 PM »

well I'm not sure, but you should put format(s) and other parameters to a rule like, I'm not sure if processes them global

^12234$=sip/sip:\1@IP;rtp_forward=no;format=mulaw;formats=mulaw

45

Installation from packets/SVN/.exe/AppStore / Re: Ubuntu Packages

« on: November 13, 2012, 09:42:27 AM »

I agree with Diana too. I think, there must be minimal possible number of packages.

Modules should separated into it's own package only if it requires some big fat dependency, like database or dahdi/zaptel.

Jabberclient is useful in server too (for example, my server sends me jabber message about who called me while i was away). It is only 118k and will not make yate-core much heavier. The same for gvoice.
Also, i see no reason for separating yate-core from libyate. I can't imagine scenario when libyate will be installed without yate-core.
Javascript may go inside some "yate-server" package with yate server binary itself together with monitoring and jabber server modules and may be with scripts.

So we will have 9 packages instead of 15...

It's not about package size. It's more about a overload of modules for most use cases. It make not much sense to give a new user more than 60 modules to configure...
For exp. a new user installs yate client, why should he use (ysigchan, mgcpca, mgcpgw, ciscosm, sigtransport, lksctp, isupmangler, or rmanager, cpuload, javascript, pbx, dbwave and so on....)
And btw the dependency for mysql or pgsql are small.. libmysqlclient and libpq...there are more for zap/dahdi...
I agree with the lib pkg.. it make not much sense too use it alone, combining script and server make sense, tooo

How about:

• Yate-docs: doc files
• Yate-core: lib, yate binary, rest of modules (>50 modules)
• Yate-client: Client files, GTK
• Yate-server: server modules, monitoring, cpuload,ysnmp, scripting files, javascript, perl,php
• Yate-pgsql: Postgree Driver
• Yate-mysql: Mysql Driver
• Yate-openh323: OpenH323 Chan
• Yate-signaling: ysigchan, mgcpca, mgcpgw, ciscosm, sigtransport, lksctp, isupmangler