[sip-comm-dev] interoperability


#1

Hi

  Is there any works going on sip -interoperability in SC ?Key
management project did wish to look onto it in GSOC .But may be there
is more look on the ZRTP implementataion there..I hope it should be
then considered as a standalone thought here

Does SC handle interoperability with session management features? Or
value added functions (call hold ,call resume)? Does SC handle
interoperability with H-323 or PSTN .? IF yes what are the api we use
here?

Next we have to think about key sharing in signalling session or
media-session invoolved signalling session. There is also
internetworking issue. The possible existing solution is either
having the specifications in both clients or setting up media box in
between the clients.The media box will decrypt from the sender and
encrypt to the receiver.But media box is expensive. The question is
who will set up the media box for different vendors.. It should be
trusted also..

  I want to work on it in SC. If someone from developers has already
worked on it or wants to work on it, I am looking for his contribution
and suggestions on it..

  Another question is does SC has any chosen java api or library
implementing SDES-SIP,SRTPMIKEY,DTLS-SRTP . I know bouncycastle is
used with libzrtp in zrtp.. Someone please suggest me.

Rossi

I

···

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


#2

Hi Rossi,

Is there any works going on sip -interoperability in SC ?Key
management project did wish to look onto it in GSOC .But may be there
is more look on the ZRTP implementataion there..I hope it should be
then considered as a standalone thought here

Interoperability tests of ZRTP are of course considered for SC (see the discussion we had around 20th of May with Werner and Emanuel, entitled "Proposal to enhance SIP Communicator with ZRTP").

Does SC handle interoperability with session management features? Or
value added functions (call hold ,call resume)? Does SC handle
interoperability with H-323 or PSTN .? IF yes what are the api we use
here?

SC does not support H323, but support SIP, so call to the PSTN is possible if SIP is supported at the border equipments.

Next we have to think about key sharing in signalling session or
media-session invoolved signalling session. There is also
internetworking issue. The possible existing solution is either
having the specifications in both clients or setting up media box in
between the clients.The media box will decrypt from the sender and
encrypt to the receiver.But media box is expensive. The question is
who will set up the media box for different vendors.. It should be
trusted also..

The use of such media box was not envisioned in SC so far.

I want to work on it in SC. If someone from developers has already
worked on it or wants to work on it, I am looking for his contribution
and suggestions on it..

  Another question is does SC has any chosen java api or library
implementing SDES-SIP,SRTPMIKEY,DTLS-SRTP . I know bouncycastle is
used with libzrtp in zrtp.. Someone please suggest me.

Bouncycastle is also used for the SRTP implementation available in SC.

Cheers,

···

On 2008/05/25, at 8:26, rossi kamal wrote:
--
Romain KUNTZ
kuntz@lsiit.u-strasbg.fr
Louis Pasteur University - Networks and Protocols Team

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