[sip-comm-dev] Jingle bells (Help spread the word)


#1

Hey all,

Despite a few minor glitches here and there, we believe that our Jingle
support is now in a fairly decent state. This means that SIP
Communicator is (to my knowledge) the only FOSS client to offer Jingle
support on windows, linux and mac (and that includes of course video
calls, conferences, call transfers, etc.). Therefore you can now all
feel free to post, blog, twit, digg about this and generally help us
spread the word.

Throughout the years, we've been notoriously bad letting the world know
what we do so we should try and change this!

In case you're lacking inspiration you can use the text from our front
page news entry.

Cheers,
Emil

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#2

Dear All,
have recently tested with nb3174 jingle (Gmail and GMX):
I am not behind router, partner(s) are behind NAT.

1) calling works in both directions (nice audio & video quality, encrypted)!
2) Desktop sharing and remote control works (cool!)
(3 - did not test yet the case when both partners are behind NAT)

!!!!Congratulations!!!! - and I will spread the word now even more!

regards, MS

···

Hey all,

Despite a few minor glitches here and there, we believe that our Jingle
support is now in a fairly decent state. This means that SIP
Communicator is (to my knowledge) the only FOSS client to offer Jingle
support on windows, linux and mac (and that includes of course video
calls, conferences, call transfers, etc.). Therefore you can now all
feel free to post, blog, twit, digg about this and generally help us
spread the word.

Throughout the years, we've been notoriously bad letting the world know
what we do so we should try and change this!

In case you're lacking inspiration you can use the text from our front
page news entry.

Cheers,
Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
Mit freundlichen Grüßen
Mr Smith
mailto:mr.smith476@googlemail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

Hey all,

Despite a few minor glitches here and there, we believe that our Jingle
support is now in a fairly decent state. This means that SIP
Communicator is (to my knowledge) the only FOSS client to offer Jingle
support on windows, linux and mac (and that includes of course video
calls, conferences, call transfers, etc.). Therefore you can now all
feel free to post, blog, twit, digg about this and generally help us
spread the word.

Nice work!

Do you actually do call transfers entirely using jingle or is that via
SIP? If you meant via jingle then what kind of call transfers do you
support (attended, unattended or both)?

Ranga

···

2010/12/19 Emil Ivov <emcho@sip-communicator.org>:

Throughout the years, we've been notoriously bad letting the world know
what we do so we should try and change this!

In case you're lacking inspiration you can use the text from our front
page news entry.

Cheers,
Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
M. Ranganathan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#4

Hi,

we have posted this on linux-bg.org.

Cheers
damencho

···

2010/12/19 Emil Ivov <emcho@sip-communicator.org>:

Hey all,

Despite a few minor glitches here and there, we believe that our Jingle
support is now in a fairly decent state. This means that SIP
Communicator is (to my knowledge) the only FOSS client to offer Jingle
support on windows, linux and mac (and that includes of course video
calls, conferences, call transfers, etc.). Therefore you can now all
feel free to post, blog, twit, digg about this and generally help us
spread the word.

Throughout the years, we've been notoriously bad letting the world know
what we do so we should try and change this!

In case you're lacking inspiration you can use the text from our front
page news entry.

Cheers,
Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#5

Also posted on http://java.net

Emil

На 20.12.10 11:45, Damian Minkov написа:

···

Hi,

we have posted this on linux-bg.org.

Cheers
damencho

2010/12/19 Emil Ivov <emcho@sip-communicator.org>:

Hey all,

Despite a few minor glitches here and there, we believe that our Jingle
support is now in a fairly decent state. This means that SIP
Communicator is (to my knowledge) the only FOSS client to offer Jingle
support on windows, linux and mac (and that includes of course video
calls, conferences, call transfers, etc.). Therefore you can now all
feel free to post, blog, twit, digg about this and generally help us
spread the word.

Throughout the years, we've been notoriously bad letting the world know
what we do so we should try and change this!

In case you're lacking inspiration you can use the text from our front
page news entry.

Cheers,
Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org PHONE: +33.1.77.62.43.30
http://sip-communicator.org FAX: +33.1.77.62.47.31

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#6

На 20.12.10 17:21, M. Ranganathan написа:

Hey all,

Despite a few minor glitches here and there, we believe that our Jingle
support is now in a fairly decent state. This means that SIP
Communicator is (to my knowledge) the only FOSS client to offer Jingle
support on windows, linux and mac (and that includes of course video
calls, conferences, call transfers, etc.). Therefore you can now all
feel free to post, blog, twit, digg about this and generally help us
spread the word.

Nice work!

Do you actually do call transfers entirely using jingle or is that via
SIP? If you meant via jingle then what kind of call transfers do you
support (attended, unattended or both)?

It's entirely via Jingle, and its about both attended and blind
transfers! :slight_smile:

Cheers,
Emil

···

2010/12/19 Emil Ivov <emcho@sip-communicator.org>:

Ranga

Throughout the years, we've been notoriously bad letting the world know
what we do so we should try and change this!

In case you're lacking inspiration you can use the text from our front
page news entry.

Cheers,
Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#7

На 20.12.10 17:21, M. Ranganathan написа:

Hey all,

Despite a few minor glitches here and there, we believe that our Jingle
support is now in a fairly decent state. This means that SIP
Communicator is (to my knowledge) the only FOSS client to offer Jingle
support on windows, linux and mac (and that includes of course video
calls, conferences, call transfers, etc.). Therefore you can now all
feel free to post, blog, twit, digg about this and generally help us
spread the word.

Nice work!

Do you actually do call transfers entirely using jingle or is that via
SIP? If you meant via jingle then what kind of call transfers do you
support (attended, unattended or both)?

It's entirely via Jingle, and its about both attended and blind
transfers! :slight_smile:

Can you point me to relevant standards documents you implement? This
would certainly be the first I have heard about such capabilities and
it is a great achievement. Presumably you interop just fine with
google?

Ranga

···

On Mon, Dec 20, 2010 at 10:23 AM, Emil Ivov <emcho@sip-communicator.org> wrote:

2010/12/19 Emil Ivov <emcho@sip-communicator.org>:

Cheers,
Emil

Ranga

Throughout the years, we've been notoriously bad letting the world know
what we do so we should try and change this!

In case you're lacking inspiration you can use the text from our front
page news entry.

Cheers,
Emil

--
M. Ranganathan


#8

На 20.12.10 17:26, M. Ranganathan написа:

Can you point me to relevant standards documents you implement?

Seb just beat me to it:

http://xmpp.org/extensions/xep-0251.html

This
would certainly be the first I have heard about such capabilities and
it is a great achievement. Presumably you interop just fine with
google?

You can use them as an XMPP server and make calls as long as both
clients support the real Jingle (e.g. SC or Empathy).

We are not yet compatible with the GTalk service however which uses a
dialect of Jingle and the way media negotiation happens. Apparently
they've rectified a part of this in their latest versions but one still
needs to use dialects when exchanging ICE candidates and when performing
connectivity checks (which is 90% of the call establishment anyways). Oh
and there's also the support for streaming RTP over https.

We'll be working on support for Google's dialects early next year.

Cheers,
Emil

···

Ranga

Cheers,
Emil

Ranga

Throughout the years, we've been notoriously bad letting the world know
what we do so we should try and change this!

In case you're lacking inspiration you can use the text from our front
page news entry.

Cheers,

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#9

Great stuff ! Congrats guys, I tweeted about it to make a bit more noise :wink:
I'm thinking to start an XMPP Servlets version of Mobicents SIP Servlets now
on my free time to host XMPP, Converged JEE apps on Mobicents Sip Servlets
and maybe integrate it with SipServlets so that it could act as a gateway as
well between the two...
Which XMPP and Jingle stack do you use by the way ?

Jean

···

On Mon, Dec 20, 2010 at 5:08 PM, Emil Ivov <emcho@sip-communicator.org>wrote:

На 20.12.10 17:26, M. Ranganathan написа:
> Can you point me to relevant standards documents you implement?

Seb just beat me to it:

http://xmpp.org/extensions/xep-0251.html

> This
> would certainly be the first I have heard about such capabilities and
> it is a great achievement. Presumably you interop just fine with
> google?

You can use them as an XMPP server and make calls as long as both
clients support the real Jingle (e.g. SC or Empathy).

We are not yet compatible with the GTalk service however which uses a
dialect of Jingle and the way media negotiation happens. Apparently
they've rectified a part of this in their latest versions but one still
needs to use dialects when exchanging ICE candidates and when performing
connectivity checks (which is 90% of the call establishment anyways). Oh
and there's also the support for streaming RTP over https.

We'll be working on support for Google's dialects early next year.

Cheers,
Emil

>
> Ranga
>>
>> Cheers,
>> Emil
>>>
>>> Ranga
>>>
>>>
>>>>
>>>> Throughout the years, we've been notoriously bad letting the world
know
>>>> what we do so we should try and change this!
>>>>
>>>> In case you're lacking inspiration you can use the text from our front
>>>> page news entry.
>>>>
>>>> Cheers,

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#10

На 20.12.10 19:23, Jean Deruelle написа:

Great stuff !
Congrats guys, I tweeted about it to make a bit more noise :wink:

Hey, thanks Jean! :slight_smile:

I'm thinking to start an XMPP Servlets version of Mobicents SIP Servlets
now on my free time to host XMPP, Converged JEE apps on Mobicents Sip
Servlets and maybe integrate it with SipServlets so that it could act as
a gateway as well between the two...

This would be so cool! We've been looking for solution along these
lines. XMPP is so comfortable for deploying end-user skype-like services
but the rest of the world is mostly speaking SIP so having a decent
gateway would be really useful.

Which XMPP and Jingle stack do you use by the way ?

We use smack for the basic XMPP support and we are very happy with it.

The Jingle part however, the one that parses and constructs Jingle IQs,
is currently implemented in SIP Communicator since the one in smack was
somewhat incomplete and a bit outdated.

As long as you only care about the signalling however (and I don't think
you are interested in the media caps) you could easily reuse what we
have. Basically we'll only need to provide a jar with the jingle related
classes. We can chat about this and see what would be the easiest option.

Cheers,
Emil

···

Jean

On Mon, Dec 20, 2010 at 5:08 PM, Emil Ivov <emcho@sip-communicator.org > <mailto:emcho@sip-communicator.org>> wrote:

    На 20.12.10 17:26, M. Ranganathan написа:
    > Can you point me to relevant standards documents you implement?

    Seb just beat me to it:

    http://xmpp.org/extensions/xep-0251.html

    > This
    > would certainly be the first I have heard about such capabilities and
    > it is a great achievement. Presumably you interop just fine with
    > google?

    You can use them as an XMPP server and make calls as long as both
    clients support the real Jingle (e.g. SC or Empathy).

    We are not yet compatible with the GTalk service however which uses a
    dialect of Jingle and the way media negotiation happens. Apparently
    they've rectified a part of this in their latest versions but one still
    needs to use dialects when exchanging ICE candidates and when performing
    connectivity checks (which is 90% of the call establishment anyways). Oh
    and there's also the support for streaming RTP over https.

    We'll be working on support for Google's dialects early next year.

    Cheers,
    Emil

    >
    > Ranga
    >>
    >> Cheers,
    >> Emil
    >>>
    >>> Ranga
    >>>
    >>>
    >>>>
    >>>> Throughout the years, we've been notoriously bad letting the
    world know
    >>>> what we do so we should try and change this!
    >>>>
    >>>> In case you're lacking inspiration you can use the text from
    our front
    >>>> page news entry.
    >>>>
    >>>> Cheers,

    ---------------------------------------------------------------------
    To unsubscribe, e-mail:
    dev-unsubscribe@sip-communicator.dev.java.net
    <mailto:dev-unsubscribe@sip-communicator.dev.java.net>
    For additional commands, e-mail:
    dev-help@sip-communicator.dev.java.net
    <mailto:dev-help@sip-communicator.dev.java.net>

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org PHONE: +33.1.77.62.43.30
http://sip-communicator.org FAX: +33.1.77.62.47.31

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#11

На 20.12.10 19:23, Jean Deruelle написа:

Great stuff !
Congrats guys, I tweeted about it to make a bit more noise :wink:

Hey, thanks Jean! :slight_smile:

I'm thinking to start an XMPP Servlets version of Mobicents SIP Servlets
now on my free time to host XMPP, Converged JEE apps on Mobicents Sip
Servlets and maybe integrate it with SipServlets so that it could act as
a gateway as well between the two...

This would be so cool! We've been looking for solution along these
lines. XMPP is so comfortable for deploying end-user skype-like services
but the rest of the world is mostly speaking SIP so having a decent
gateway would be really useful.

Which XMPP and Jingle stack do you use by the way ?

We use smack for the basic XMPP support and we are very happy with it.

The Jingle part however, the one that parses and constructs Jingle IQs,
is currently implemented in SIP Communicator since the one in smack was
somewhat incomplete and a bit outdated.

As long as you only care about the signalling however (and I don't think
you are interested in the media caps) you could easily reuse what we
have. Basically we'll only need to provide a jar with the jingle related
classes. We can chat about this and see what would be the easiest option.

Cheers,
Emil

Not directly related to what you are doing but maybe Jean can consider
a NAT friendly SIP/JINGLE protocol translator sitting in a SIP server.
A back to Back UA that goes JINGLE <-> SIP so you can talk to existing
SIP endpoints (of which there are many in the business world) and
Jingle endpoints, of which there are far many more thanks to Google.

Ranga

···

On Mon, Dec 20, 2010 at 12:57 PM, Emil Ivov <emcho@sip-communicator.org> wrote:

Jean

On Mon, Dec 20, 2010 at 5:08 PM, Emil Ivov <emcho@sip-communicator.org >> <mailto:emcho@sip-communicator.org>> wrote:

На 20\.12\.10 17:26, M\. Ranganathan написа:
&gt; Can you point me to relevant standards documents you implement?

Seb just beat me to it:

http://xmpp.org/extensions/xep-0251.html

&gt; This
&gt; would certainly be the first I have heard about such capabilities and
&gt; it is a great achievement\. Presumably you interop just fine with
&gt; google?

You can use them as an XMPP server and make calls as long as both
clients support the real Jingle \(e\.g\. SC or Empathy\)\.

We are not yet compatible with the GTalk service however which uses a
dialect of Jingle and the way media negotiation happens\. Apparently
they&#39;ve rectified a part of this in their latest versions but one still
needs to use dialects when exchanging ICE candidates and when performing
connectivity checks \(which is 90% of the call establishment anyways\)\. Oh
and there&#39;s also the support for streaming RTP over https\.

We&#39;ll be working on support for Google&#39;s dialects early next year\.

Cheers,
Emil

&gt;
&gt; Ranga
&gt;&gt;
&gt;&gt; Cheers,
&gt;&gt; Emil
&gt;&gt;&gt;
&gt;&gt;&gt; Ranga
&gt;&gt;&gt;
&gt;&gt;&gt;
&gt;&gt;&gt;&gt;
&gt;&gt;&gt;&gt; Throughout the years, we&#39;ve been notoriously bad letting the
world know
&gt;&gt;&gt;&gt; what we do so we should try and change this\!
&gt;&gt;&gt;&gt;
&gt;&gt;&gt;&gt; In case you&#39;re lacking inspiration you can use the text from
our front
&gt;&gt;&gt;&gt; page news entry\.
&gt;&gt;&gt;&gt;
&gt;&gt;&gt;&gt; Cheers,

\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
To unsubscribe, e\-mail:
dev\-unsubscribe@sip\-communicator\.dev\.java\.net
&lt;mailto:dev\-unsubscribe@sip\-communicator\.dev\.java\.net&gt;
For additional commands, e\-mail:
dev\-help@sip\-communicator\.dev\.java\.net
&lt;mailto:dev\-help@sip\-communicator\.dev\.java\.net&gt;

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org PHONE: +33.1.77.62.43.30
http://sip-communicator.org FAX: +33.1.77.62.47.31

--
M. Ranganathan


#12

Hi all,

Also spread on linuxfr.org!

Regards,
Valentin

···

On 12/20/2010 06:57 PM, Emil Ivov wrote:

На 20.12.10 19:23, Jean Deruelle написа:

Great stuff !
Congrats guys, I tweeted about it to make a bit more noise :wink:

Hey, thanks Jean! :slight_smile:

I'm thinking to start an XMPP Servlets version of Mobicents SIP Servlets
now on my free time to host XMPP, Converged JEE apps on Mobicents Sip
Servlets and maybe integrate it with SipServlets so that it could act as
a gateway as well between the two...

This would be so cool! We've been looking for solution along these
lines. XMPP is so comfortable for deploying end-user skype-like services
but the rest of the world is mostly speaking SIP so having a decent
gateway would be really useful.

Which XMPP and Jingle stack do you use by the way ?

We use smack for the basic XMPP support and we are very happy with it.

The Jingle part however, the one that parses and constructs Jingle IQs,
is currently implemented in SIP Communicator since the one in smack was
somewhat incomplete and a bit outdated.

As long as you only care about the signalling however (and I don't think
you are interested in the media caps) you could easily reuse what we
have. Basically we'll only need to provide a jar with the jingle related
classes. We can chat about this and see what would be the easiest option.

Cheers,
Emil

Jean

On Mon, Dec 20, 2010 at 5:08 PM, Emil Ivov<emcho@sip-communicator.org >> <mailto:emcho@sip-communicator.org>> wrote:

     На 20.12.10 17:26, M. Ranganathan написа:
     > Can you point me to relevant standards documents you implement?

     Seb just beat me to it:

     http://xmpp.org/extensions/xep-0251.html

     > This
     > would certainly be the first I have heard about such capabilities and
     > it is a great achievement. Presumably you interop just fine with
     > google?

     You can use them as an XMPP server and make calls as long as both
     clients support the real Jingle (e.g. SC or Empathy).

     We are not yet compatible with the GTalk service however which uses a
     dialect of Jingle and the way media negotiation happens. Apparently
     they've rectified a part of this in their latest versions but one still
     needs to use dialects when exchanging ICE candidates and when performing
     connectivity checks (which is 90% of the call establishment anyways). Oh
     and there's also the support for streaming RTP over https.

     We'll be working on support for Google's dialects early next year.

     Cheers,
     Emil

     >
     > Ranga
     >>
     >> Cheers,
     >> Emil
     >>>
     >>> Ranga
     >>>
     >>>>
     >>>> Throughout the years, we've been notoriously bad letting the
     world know
     >>>> what we do so we should try and change this!
     >>>>
     >>>> In case you're lacking inspiration you can use the text from
     our front
     >>>> page news entry.
     >>>>
     >>>> Cheers,

     ---------------------------------------------------------------------
     To unsubscribe, e-mail:
     dev-unsubscribe@sip-communicator.dev.java.net
     <mailto:dev-unsubscribe@sip-communicator.dev.java.net>
     For additional commands, e-mail:
     dev-help@sip-communicator.dev.java.net
     <mailto:dev-help@sip-communicator.dev.java.net>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#13

Thanks Emil,

I'll ping you to discuss it for sure.

···

On Mon, Dec 20, 2010 at 6:57 PM, Emil Ivov <emcho@sip-communicator.org>wrote:

На 20.12.10 19:23, Jean Deruelle написа:
> Great stuff !
> Congrats guys, I tweeted about it to make a bit more noise :wink:

Hey, thanks Jean! :slight_smile:

> I'm thinking to start an XMPP Servlets version of Mobicents SIP Servlets
> now on my free time to host XMPP, Converged JEE apps on Mobicents Sip
> Servlets and maybe integrate it with SipServlets so that it could act as
> a gateway as well between the two...

This would be so cool! We've been looking for solution along these
lines. XMPP is so comfortable for deploying end-user skype-like services
but the rest of the world is mostly speaking SIP so having a decent
gateway would be really useful.

> Which XMPP and Jingle stack do you use by the way ?

We use smack for the basic XMPP support and we are very happy with it.

The Jingle part however, the one that parses and constructs Jingle IQs,
is currently implemented in SIP Communicator since the one in smack was
somewhat incomplete and a bit outdated.

As long as you only care about the signalling however (and I don't think
you are interested in the media caps) you could easily reuse what we
have. Basically we'll only need to provide a jar with the jingle related
classes. We can chat about this and see what would be the easiest option.

Cheers,
Emil
>
> Jean
>
>
> On Mon, Dec 20, 2010 at 5:08 PM, Emil Ivov <emcho@sip-communicator.org > > <mailto:emcho@sip-communicator.org>> wrote:
>
> На 20.12.10 17:26, M. Ranganathan написа:
> > Can you point me to relevant standards documents you implement?
>
> Seb just beat me to it:
>
> http://xmpp.org/extensions/xep-0251.html
>
> > This
> > would certainly be the first I have heard about such capabilities
and
> > it is a great achievement. Presumably you interop just fine with
> > google?
>
> You can use them as an XMPP server and make calls as long as both
> clients support the real Jingle (e.g. SC or Empathy).
>
> We are not yet compatible with the GTalk service however which uses a
> dialect of Jingle and the way media negotiation happens. Apparently
> they've rectified a part of this in their latest versions but one
still
> needs to use dialects when exchanging ICE candidates and when
performing
> connectivity checks (which is 90% of the call establishment anyways).
Oh
> and there's also the support for streaming RTP over https.
>
> We'll be working on support for Google's dialects early next year.
>
> Cheers,
> Emil
>
> >
> > Ranga
> >>
> >> Cheers,
> >> Emil
> >>>
> >>> Ranga
> >>>
> >>>
> >>>>
> >>>> Throughout the years, we've been notoriously bad letting the
> world know
> >>>> what we do so we should try and change this!
> >>>>
> >>>> In case you're lacking inspiration you can use the text from
> our front
> >>>> page news entry.
> >>>>
> >>>> Cheers,
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> dev-unsubscribe@sip-communicator.dev.java.net
> <mailto:dev-unsubscribe@sip-communicator.dev.java.net>
> For additional commands, e-mail:
> dev-help@sip-communicator.dev.java.net
> <mailto:dev-help@sip-communicator.dev.java.net>
>
>

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org PHONE: +33.1.77.62.43.30
http://sip-communicator.org FAX: +33.1.77.62.47.31


#14

Yes this is what I had in mind when I said
"and maybe integrate it with SipServlets so that it could act as a gateway
as well between the two... "

···

2010/12/20 M. Ranganathan <mranga@gmail.com>

On Mon, Dec 20, 2010 at 12:57 PM, Emil Ivov <emcho@sip-communicator.org> > wrote:
> На 20.12.10 19:23, Jean Deruelle написа:
>> Great stuff !
>> Congrats guys, I tweeted about it to make a bit more noise :wink:
>
> Hey, thanks Jean! :slight_smile:
>
>> I'm thinking to start an XMPP Servlets version of Mobicents SIP Servlets
>> now on my free time to host XMPP, Converged JEE apps on Mobicents Sip
>> Servlets and maybe integrate it with SipServlets so that it could act as
>> a gateway as well between the two...
>
> This would be so cool! We've been looking for solution along these
> lines. XMPP is so comfortable for deploying end-user skype-like services
> but the rest of the world is mostly speaking SIP so having a decent
> gateway would be really useful.
>
>> Which XMPP and Jingle stack do you use by the way ?
>
> We use smack for the basic XMPP support and we are very happy with it.
>
> The Jingle part however, the one that parses and constructs Jingle IQs,
> is currently implemented in SIP Communicator since the one in smack was
> somewhat incomplete and a bit outdated.
>
> As long as you only care about the signalling however (and I don't think
> you are interested in the media caps) you could easily reuse what we
> have. Basically we'll only need to provide a jar with the jingle related
> classes. We can chat about this and see what would be the easiest option.
>
> Cheers,
> Emil

Not directly related to what you are doing but maybe Jean can consider
a NAT friendly SIP/JINGLE protocol translator sitting in a SIP server.
A back to Back UA that goes JINGLE <-> SIP so you can talk to existing
SIP endpoints (of which there are many in the business world) and
Jingle endpoints, of which there are far many more thanks to Google.

Ranga

>>
>> Jean
>>
>>
>> On Mon, Dec 20, 2010 at 5:08 PM, Emil Ivov <emcho@sip-communicator.org > >> <mailto:emcho@sip-communicator.org>> wrote:
>>
>> На 20.12.10 17:26, M. Ranganathan написа:
>> > Can you point me to relevant standards documents you implement?
>>
>> Seb just beat me to it:
>>
>> http://xmpp.org/extensions/xep-0251.html
>>
>> > This
>> > would certainly be the first I have heard about such capabilities
and
>> > it is a great achievement. Presumably you interop just fine with
>> > google?
>>
>> You can use them as an XMPP server and make calls as long as both
>> clients support the real Jingle (e.g. SC or Empathy).
>>
>> We are not yet compatible with the GTalk service however which uses
a
>> dialect of Jingle and the way media negotiation happens. Apparently
>> they've rectified a part of this in their latest versions but one
still
>> needs to use dialects when exchanging ICE candidates and when
performing
>> connectivity checks (which is 90% of the call establishment
anyways). Oh
>> and there's also the support for streaming RTP over https.
>>
>> We'll be working on support for Google's dialects early next year.
>>
>> Cheers,
>> Emil
>>
>> >
>> > Ranga
>> >>
>> >> Cheers,
>> >> Emil
>> >>>
>> >>> Ranga
>> >>>
>> >>>
>> >>>>
>> >>>> Throughout the years, we've been notoriously bad letting the
>> world know
>> >>>> what we do so we should try and change this!
>> >>>>
>> >>>> In case you're lacking inspiration you can use the text from
>> our front
>> >>>> page news entry.
>> >>>>
>> >>>> Cheers,
>>
>>
>>
---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> dev-unsubscribe@sip-communicator.dev.java.net
>> <mailto:dev-unsubscribe@sip-communicator.dev.java.net>
>> For additional commands, e-mail:
>> dev-help@sip-communicator.dev.java.net
>> <mailto:dev-help@sip-communicator.dev.java.net>
>>
>>
>
> --
> Emil Ivov, Ph.D. 67000 Strasbourg,
> Project Lead France
> SIP Communicator
> emcho@sip-communicator.org PHONE: +33.1.77.62.43.30
> http://sip-communicator.org FAX: +33.1.77.62.47.31
>
>

--
M. Ranganathan


#15

Hi Ranga,

Not directly related to what you are doing but maybe Jean can consider

a NAT friendly SIP/JINGLE protocol translator sitting in a SIP server.<<
Asterisk has some support for XMPP/GoogleTalk. Maybe one can do anything with it. I've never tried it.

Conrad

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#16

Yes this is what I had in mind when I said
"and maybe integrate it with SipServlets so that it could act as a gateway
as well between the two... "

Ah! Drink deeply or SIP not the SMACK, young Jedi. Dragons lurk here.

Mid call media re-negotiations and transfers lurk here and various
transfer scenarios between endpoints SIP on the one side and XMPP on
the other lurk here.... but it would be an exciting accomplishment if
you could do it, and nobody would be more pleased than I.

To make life tolerable, you can edit the SDP ( strip all but PCMU /
PCMA ) and disallow media renegotiation ( fake it by replying with the
previously negotiated media in the server ).

Ranga.

···

2010/12/20 Jean Deruelle <jean.deruelle@gmail.com>:

2010/12/20 M. Ranganathan <mranga@gmail.com>

--
M. Ranganathan


#17

Hi Ranga,

Not directly related to what you are doing but maybe Jean can consider

a NAT friendly SIP/JINGLE protocol translator sitting in a SIP server.<<
Asterisk has some support for XMPP/GoogleTalk. Maybe one can do anything with it. I've never tried it.

Conrad

Possibly. It is a non-trivial hack. I do not want to hijack the thread
any more, however. Emil has been most tolerant with me so far.

Regards,

Ranga.

···

On Mon, Dec 20, 2010 at 3:16 PM, Conrad Beckert <conrad_videokonferenz@gmx.de> wrote:

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
M. Ranganathan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#18

Just to let you know that the post on linuxfr has been accepted.

Regards,
Valentin

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net