Hi,
I would propose this to be part of jvoicebridge.
As Kristoffer suggested in another mail thread sailfin should access the jvoicebridge with JSR 309 API.
I think its better to keep sailfin and jvoicebridge as separate
components. sailfin handles the control plane and jvoicebridge handles
the media plane.
The real flexible option is
1) sailfin can use the JSR 309 API to invoke the media services. I hope
JSR 309 API is enough to provide the required functionality
2) JSR 309 can use MSCML (in short term) and IETF mediactrl SIP control framework in long term
3) On the media server side MSCML (or mediactrl ) + jvoicebridge can provides the media functionality.
With this architecture the media and control parts are separated with
flexible interfaces and it can be deployed in any combination. For
example
1) sailfin and jvoicebridge (media server) on the same node still sailfinor
2) for scalability reasons sailfin on one node which is acting like a
SIP application server and which can control several Media servers
(jvoicebridge).
Regards
/Krishna
--- On Wed, 12/12/07, Jeanfrancois Arcand <Jeanfrancois.Arcand@Sun.COM> wrote:
From: Jeanfrancois Arcand <Jeanfrancois.Arcand@Sun.COM>
Subject: Re: Instructions how to start new sub-project for RTP using Grizzly
To: dev@grizzly.dev.java.net
Cc: dev@sailfin.dev.java.net, dev@jvoicebridge.dev.java.net
Date: Wednesday, December 12, 2007, 6:32 PM
Hi,
Miroslav Nachev wrote:
> Hi,
>
> jVoiceBridge is a good place but until now I can not contact anybody
> from the community.
>
If you don't get any responses, we can always host it as a sub module in
Grizzly, and later move it to Sailfin or a sub project of Sailfin,
similar to what we do with Grizzly, which is sub project of GlassFish.
Thanks
-- Jeanfrancois
>
> Regards,
> Miro.
>
>
> Kristoffer Gronowski wrote:
>> 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@space-comm.com] Sent: den 12
>>
december 2007 08:44
>> To: dev@grizzly.dev.java.net; dev@sailfin.dev.java.net;
>> dev@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@sailfin.dev.java.net
>> For additional commands, e-mail: dev-help@sailfin.dev.java.net
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@sailfin.dev.java.net
>> For additional commands, e-mail: dev-help@sailfin.dev.java.net
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@grizzly.dev.java.net
> For additional commands, e-mail: dev-help@grizzly.dev.java.net
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sailfin.dev.java.net
For additional commands, e-mail: dev-help@sailfin.dev.java.net |