Hi Miro!
I would vote for doing this on the jvoicebridge community.
With the reservation that we can get it up to speed.
There is some code that Jonathan said would be submitted on how to run
JVoiceBridge on Sailfin.
I think adding RTP Grizzly support would be a nice enhancement to the
JVoiceBridge.
The other alternative is if RTP is in Grizzly and there is another
project or subproject to Sailfin that builds the IP PBX and uses the RTP
stack from Grizzly.
But it would be good to hear the other communities reasoning on this
too.
BR Stoffe
-----Original Message-----
From: Miroslav Nachev [mailto:miro_at_space-comm.com]
Sent: den 12 december 2007 08:44
To: dev_at_grizzly.dev.java.net; dev_at_sailfin.dev.java.net;
dev_at_jvoicebridge.dev.java.net
Subject: Instructions how to start new sub-project for RTP using Grizzly
Hi,
I investigate jVoiceBridge project and see that there is not used Java
NIO neither Grizzly project. This will add some delay to the whole VoIP
solutions especially for conferences. Also this is good try to be more
involved in Grizzly project. The next my step will be to start IP PBX
using Grizzly/Sailfin.
Also I write a letter to jVoiceBridge mail list but until now I have not
answer which means that the project is not more active. On the other way
the RTP Grizzly Container have to be in Grizzly project maybe?
That's why I would like to ask you for help how to start the
sub-project? Are there any instructions or can you give me some
suggestion?
Regards,
Miro.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_sailfin.dev.java.net
For additional commands, e-mail: dev-help_at_sailfin.dev.java.net