Hi, Castillo My doubt was originated observing one environment I have here at my office. These fields I've asked is not precisely filled by these machines owners. As matter fact, it sends the same uri into these fields, no matters from witch peer the server receives the SUBSCRIBE message.
Then, your answer clears this question, even thougth, the RFC 3261 explains how to fill these fields, as you said. The same rules shall be applied to contact field. Thanks again. Leonardo Laface --- Em qua, 27/4/11, Iñaki Baz Castillo <[email protected]> escreveu: De: Iñaki Baz Castillo <[email protected]> Assunto: Re: [Sip-implementors] Subscribe/Notify Para: "Leo Leo" <[email protected]> Cc: [email protected] Data: Quarta-feira, 27 de Abril de 2011, 19:51 2011/4/27 Leo Leo <[email protected]>: > I was wondering how to implement these kind of messages. I've already loocked > at RFC 3265 and there is no comments how to fill the headers: > > To, From and contact. > > I imagine theses fields for the SUBSCRIBER should be the same rules from > REGISTER and for the NOTICE, the same rules from INVITE No, SUBSCRIBE must follow same rules as any request but REGISTER, and NOTICE must be created following the values of the SUBSCRIBE generating the subscription dialog. About the Contact in a SUBSCRIBE, it has not mistery, which is the exact doubt? -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
