[jitsi-dev] Jitsi, Mobicents and Telemedicine


#1

Hi All,

I compiled a blog about a Telmedicine application which demonstrates
the integration of video telecommunication systems and Electronic
Health Record Systems(EHR).

Jitsi is the client used to send and receive the video calls, and
Mobicents SIP Servlet is the registrar and proxy.

http://shaymat.blogspot.com/

Cheers,
Shay


#2

Hey Shay,

Thanks for the note! Sounds very interesting!

I just have one quick question. At one point you say:

OSGi events . Since Jitsi is based on Felix and follows the OSGi
spec , I attempted to use OSGi events but unfortunately they are not
implemented by Jitsi.

I was wondering what kind of OSGi events you think would have spared you
the need to modify the INVITE handling?

Also, you mention that:

. The SIP stack that Jitsi uses allows for dynamic registration of
SIP message event handlers, but Jitsi only allows for one processor
at any given time and new ones just overwrite the previous ones.

The above statement is not correct. First of all, jain-sip only allows
for a single SipListener and its addListener() method throws a
TooManyListenersException if you try to add a second one. Check here:

http://www-x.antd.nist.gov/proj/iptel/jain-sip-1.2/javadoc/javax/sip/SipProvider.html#addSipListener(javax.sip.SipListener)

Jitsi on the other hand uses a SipStackSharing class which multiplexes
events over multiple providers. Each provider also uses the notion of
MethodProcessor-s that allow multiple classes to register when for a
particular kind of requests.

Hope this helps,
Emil

На 09.05.11 00:34, matasaro@gmail.com написа:

···

Hi All,

I compiled a blog about a Telmedicine application which
demonstrates the integration of video telecommunication systems and
Electronic Health Record Systems(EHR).

Jitsi is the client used to send and receive the video calls, and
Mobicents SIP Servlet is the registrar and proxy.

http://shaymat.blogspot.com/

Cheers, Shay


#3

Hi Emil,

Thanks for the email.

For the specific use case of TM, getting an OSGi event when an invite arrives, would be great. It might be beneficial for other apps to receive other dialog events such as CANCEL, REINVITE or even OPTIONS.

I see your point about the Method providers , based on my review of the code i attributed the NIST limitations to Jitsi, I'll revise the blog to reflect this new information.

Next step for the app is cloud deployment and the following step would be a multi party video conferencing.

Cheers,
Shay

···

On 11-05-12 07:09 AM, Emil Ivov wrote:

Hey Shay,

Thanks for the note! Sounds very interesting!

I just have one quick question. At one point you say:

OSGi events . Since Jitsi is based on Felix and follows the OSGi
spec , I attempted to use OSGi events but unfortunately they are not
implemented by Jitsi.

I was wondering what kind of OSGi events you think would have spared you
the need to modify the INVITE handling?

Also, you mention that:

. The SIP stack that Jitsi uses allows for dynamic registration of
SIP message event handlers, but Jitsi only allows for one processor
at any given time and new ones just overwrite the previous ones.

The above statement is not correct. First of all, jain-sip only allows
for a single SipListener and its addListener() method throws a
TooManyListenersException if you try to add a second one. Check here:

http://www-x.antd.nist.gov/proj/iptel/jain-sip-1.2/javadoc/javax/sip/SipProvider.html#addSipListener(javax.sip.SipListener)

Jitsi on the other hand uses a SipStackSharing class which multiplexes
events over multiple providers. Each provider also uses the notion of
MethodProcessor-s that allow multiple classes to register when for a
particular kind of requests.

Hope this helps,
Emil

На 09.05.11 00:34, matasaro@gmail.com написа:

Hi All,

I compiled a blog about a Telmedicine application which
demonstrates the integration of video telecommunication systems and
Electronic Health Record Systems(EHR).

Jitsi is the client used to send and receive the video calls, and
Mobicents SIP Servlet is the registrar and proxy.

http://shaymat.blogspot.com/

Cheers, Shay