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:
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,
На 09.05.11 00:34, firstname.lastname@example.org написа:
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.