[Sofia-sip-devel] Sofia-SIP - Additional Standard compliance
Hi, I would like to know if I could expect Sofia-SIP Library to be compliant soon with the following standards : - RFC 2782 ? - RFC 2822 ? - RFC 2833 ? - RFC 3398 ? - RFC 3966 ? - draft-ietf-sip-session-timer-04.txt ? - ITU-T T.38 ? Thanks in advance. Best regards, Yann BOURON- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
Re: [Sofia-sip-devel] Sofia-SIP - Additional Standard compliance
2008/1/30, Yann BOURON <[EMAIL PROTECTED]>: > I would like to know if I could expect Sofia-SIP Library to be compliant > soon with the following standards : > - RFC 2782 ? - DNS SRV - already in compliance > - RFC 2822 ? - Email message format - I'm confused, Sofia SIP does not do any e-mail... > - RFC 2833 ? RTP payload format for DTMF and friends - Obsoleted by 4733 and 4734 Signaling RTP payload format in SDP is supported, rest is left to application to handle > - RFC 3398 ? Sofia SIP supports INFO, signaling RFC4733 codec, and sort-a-kind-a multipart mime. So I guess we can put a cross (checkmark in America) in this box, too. > - RFC 3966 ? RFC3261-like support, in other words, tel uri comparison is done character-by-character. > - draft-ietf-sip-session-timer-04.txt ? Sofia SIP supports RFC 4028. I don't know how -04 draft differs from the RFC 4028. > - ITU-T T.38 ? Yet another payload format, or so I hope. Again, codec negotiation is supported. -- Pekka.Pessi mail at nokia.com - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
Re: [Sofia-sip-devel] Sofia-SIP - Additional Standard compliance
If your looking for something that supports the media elements too, we support much of this in freeswitch (www.freeswitch.org) including 2833/4733 and passthrough T.38 (all using sofia for the signaling). Mike On Feb 7, 2008, at 8:22 AM, Pekka Pessi wrote: > 2008/1/30, Yann BOURON <[EMAIL PROTECTED]>: >> I would like to know if I could expect Sofia-SIP Library to be >> compliant >> soon with the following standards : >> - RFC 2782 ? > > - DNS SRV - already in compliance > >> - RFC 2822 ? > > - Email message format - I'm confused, Sofia SIP does not do any e- > mail... > >> - RFC 2833 ? > > RTP payload format for DTMF and friends - Obsoleted by 4733 and 4734 > > Signaling RTP payload format in SDP is supported, rest is left to > application to handle > >> - RFC 3398 ? > > Sofia SIP supports INFO, signaling RFC4733 codec, and sort-a-kind-a > multipart mime. So I guess we can put a cross (checkmark in America) > in this box, too. > >> - RFC 3966 ? > > RFC3261-like support, in other words, tel uri comparison is done > character-by-character. > >> - draft-ietf-sip-session-timer-04.txt ? > > Sofia SIP supports RFC 4028. I don't know how -04 draft differs from > the RFC 4028. > >> - ITU-T T.38 ? > > Yet another payload format, or so I hope. Again, codec negotiation > is supported. > > -- > Pekka.Pessi mail at nokia.com > > - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > ___ > Sofia-sip-devel mailing list > Sofia-sip-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
