[jitsi-dev] Documentation of standards question


#1

Hi,
I'd like to use Jitsi as a SIP client, but need to have some idea of what
RFCs it supports/does not support. Is there any documentation on this? I
can't tell which RFCs Jitsi implements, or (better still) which parts of
those RFCs. For example, with a little digging, I can see what the stack
underlying Freeswitch supports:
http://sofia-sip.sourceforge.net/refdocs/sofia_sip_conformance.html

With docs like these, I can start to have some idea of how session timers
are supported (reINVITE or UPDATE?), reliable provisionals, which of the
(far too many) early-media related RFCs is/is not supported, REFER (in and
out-of-dialog), GRUU, Replaces & Join headers, etc.

Thanks,

Tom

···

--
Tom Strickland

--------------------
Note: The information contained in this message may be privileged and confidential
and protected from disclosure. If the reader of this message is not the intended
recipient, or an employee or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Thrupoint, Inc. - ubq


#2

Hey Tom

Hi,
I'd like to use Jitsi as a SIP client, but need to have some idea of
what RFCs it supports/does not support. Is there any documentation on
this? I can't tell which RFCs Jitsi implements, or (better still) which
parts of those RFCs. For example, with a little digging, I can see what
the stack underlying Freeswitch supports:
http://sofia-sip.sourceforge.net/refdocs/sofia_sip_conformance.html

Have you checked this page out:

http://jitsi.org/features

It doesn't really quote RFCs for any single feature but it does say
quite a lot on what we support.

With docs like these, I can start to have some idea of how session
timers are supported (reINVITE or UPDATE?)

We have no explicit handling for session timers. We do handle reINVITEs
of course, and we generated "NOT_IMPLEMENTED" responses for UPDATEs.

, reliable provisionals,

Not sure I see what this one means.

which
of the (far too many) early-media related RFCs is/is not supported,

Good question. I guess you could say that we simply handle SDP in
provisional responses (e.g. 183 Session Progress). I don't think we ever
actually checked for compliance with a particular RFC

We don't do PRACKs as of now.

REFER (in and out-of-dialog)

Both

, GRUU

Not yet.

, Replaces

yes

& Join headers, etc.

Not yet. .... Would be cool though!

Hope this helps,
Emil

···

On 05.04.12 15:56, Tom Strickland wrote:

Thanks,

Tom

--
Tom Strickland

--------------------
Note: The information contained in this message may be privileged and confidential
and protected from disclosure. If the reader of this message is not the intended
recipient, or an employee or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Thrupoint, Inc. - ubq

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#3

Hi Emil,
Thanks for your reply, which was very helpful. I had already checked out
the features page, which is handy, but lacks some detail when it comes to
specifics. Your reply was very helpful. More inline...

Regards,

Tom Strickland

Hey Tom

> Hi,
> I'd like to use Jitsi as a SIP client, but need to have some idea of
> what RFCs it supports/does not support. Is there any documentation on
> this? I can't tell which RFCs Jitsi implements, or (better still) which
> parts of those RFCs. For example, with a little digging, I can see what
> the stack underlying Freeswitch supports:
> http://sofia-sip.sourceforge.net/refdocs/sofia_sip_conformance.html

Have you checked this page out:

http://jitsi.org/features

It doesn't really quote RFCs for any single feature but it does say
quite a lot on what we support.

> With docs like these, I can start to have some idea of how session
> timers are supported (reINVITE or UPDATE?)
We have no explicit handling for session timers. We do handle reINVITEs
of course, and we generated "NOT_IMPLEMENTED" responses for UPDATEs.

>, reliable provisionals,
Not sure I see what this one means.

RFC 3262 - essentially this is PRACKs etc. and you've said below that you
don't support them yet.

which
of the (far too many) early-media related RFCs is/is not supported,

Good question. I guess you could say that we simply handle SDP in
provisional responses (e.g. 183 Session Progress). I don't think we ever
actually checked for compliance with a particular RFC
We don't do PRACKs as of now.

Early media is a pain, especially when it comes to forking, but some of our
apps demand it.

···

On 5 April 2012 19:10, Emil Ivov <emcho@jitsi.org> wrote:

On 05.04.12 15:56, Tom Strickland wrote:

REFER (in and out-of-dialog)
Both
>, GRUU
Not yet.
>, Replaces
yes
>& Join headers, etc.
Not yet. .... Would be cool though!
Hope this helps,
Emil

>
> Thanks,
> Tom Strickland
Emil Ivov, Ph.D. 67000 Strasbourg,

--------------------
Note: The information contained in this message may be privileged and confidential
and protected from disclosure. If the reader of this message is not the intended
recipient, or an employee or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Thrupoint, Inc. - ubq