Hello,
Klaus, Jan, thank you very much for your answers. Below is the list of RFCs I'm interested in. As Klaus says, maybe some of them don't need explicit support, because ser can route these new messages. Or maybe there are RFCs that are not fully supported. Please, let me know if this is the case and if it could be necessary writting a new module or changing SER core.
By the way, can SER initiate a session release (it means, generate a BYE) or generate a REGISTER to an application server? If not, what would be necessary from your point of view?
Again, thank you very much for your time and knowledge. I know that there are a lot of questions in this message, so thank you.
Curro
(These five RFCs are related to new messages, so I suppose Yes) RFC 2976 (October 2000): "The SIP INFO method".
RFC 3262 (June 2002): "Reliability of provisional responses in Session Initiation Protocol (SIP)". (can SER generate PRACK, besides proxying it?)
RFC 3515 (April 2003): "The Session Initiation Protocol (SIP) REFER method".
RFC 3311 (September 2002): "The Session Initiation Protocol (SIP) UPDATE method".
RFC 3428 (December 2002): "Session Initiation Protocol (SIP) Extension for Instant Messaging".
RFC 3313 (January 2003): "Private Session Initiation Protocol (SIP) Extensions for Media Authorization".
RFC 3265 (June 2002): "Session Initiation Protocol (SIP) Specific Event Notification". (As far as I know, SER handles SUBSCRIBE and NOTIFY, but I want to know whether SER can act as the subscriber to the event information, it means, generate SUBSCRIBE)
RFC 3327 (December 2002): "Session Initiation Protocol Extension Header Field for Registering Non-Adjacent Contacts".
RFC 3325 (November 2002): "Private Extensions to the Session Initiation Protocol (SIP) for Network Asserted Identity within Trusted Networks".
RFC 3323 (November 2002): "A Privacy Mechanism for the Session Initiation Protocol (SIP)".
RFC 3608 (October 2003): "Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration".
RFC 3486 (February 2003): "Compressing the Session Initiation Protocol (SIP)".
RFC 3455 (January 2003): "Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)".
RFC 3329 (January 2003): "Security Mechanism Agreement for the Session Initiation Protocol (SIP)".
----- Mensaje Original ----- De: Jan Janak jan@iptel.org Fecha: Lunes, Abril 12, 2004 10:28 pm Asunto: Re: [Serusers] SER 0.8.12 and RFC
There is no such list. If you need it then put together a list of RFCs you are interested in and we will add yes/no to each entry in the list. Jan.
On 12-04 12:38, CURRO_DOMINGUEZ wrote:
Hello all the list
I'm looking some information about SER at www.iptel.org but I've
found
nothing. I would like to know the list of RFC that SER
implements
(related to SIP or SIP extensions), besides RFC3261.
I think it could be interesting to add this information at the
product
sheet.
Can you help me?
Thank you very much
Curro
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers