Messages

1

Features requests / Re: WebSocket

« on: May 20, 2014, 03:28:04 AM »

I finally managed to get it working somehow.
WebRTC to SIP is translated by oversip (http://oversip.net/) and yate is patched in several aspects:
 - proper SDP attributes handling
 - bug 0000367 fixed
 - ICE-Lite (rfc5245) sipport added
 - Fake rtcp-mux (rfc5761) support added
Now i can call from Google Chrome with sipml5 to Linksys sip phone, connected to yate.
After more testing i'll prepare patches, and may be, one day, they will accepted by Null team...

If someone is interesting in current project status, please see https://github.com/vir/yate, branch ice.

2

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

« on: November 21, 2012, 03:37:17 AM »

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...

Most of them do not require any configuration. Sample configs are just fine.

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....)

He shouldn't. He installs yate-client, which depends on yate-core (or how it will be called), qt4 and alsa.
If he really wants to use yateclient with PSTN or ISDN, he will install yate-signalling (anyway, it will require some non-trivial configuration).
The same for yate-h323. It should go into "Recommends" of "Suggests" control file field.

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

IMHO, yate binary should go to the yate-server package.
The rest looks pretty well.

By the way, my "point of view" is implemented in my packaging info here:
https://github.com/vir/yate/blob/master/debian
It is far from perfect and some packages should definitely by renamed.
May be *-dbg should go into yate-dev, not sure.
I will be happy to see some critic and suggestions about it too

3

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

« on: November 12, 2012, 02:24:38 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...

4

Yate bugs / Re: enable H264 video support in YATE

« on: November 12, 2012, 01:50:55 AM »

First of all, video calls are always possible when using rtp_forward and sdp_forward.
When rtp stream is going through yate, some problems may arise.
From my experience, problems with video calls are usually caused by missing fmtp: lines in sdp.
Yate reproduces only a few fmtp parameters on outgoing call leg, and most video phones can't live without those parameters.
You can try this patch to fix this issue: http://vir.lclt.ru/yate/sdp-fmtp.diff
It worked for me a couple of years ago, hope it still works