Thanks & Regards, Nataraju A.B.
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:sip-implementors- > [EMAIL PROTECTED] On Behalf Of Marco Ambu > Sent: Tuesday, June 20, 2006 12:22 PM > To: SIP-implementors mailing list > Subject: Re: [Sip-implementors] Dialog creation > > Nataraju A B ha scritto: > > > >> 3) Is there any reason to keep early dialogs in the dialog's map > >> (considering that cannot be used to create a new request)? > >> > >> > > [ABN] did not get you problem exactly :( > > > This is an implementation problem. I think there is no need to keep > early dialog information in the dialog map assuming that all early > dialogs will be destroyed as soon as a final response is received by UAC > (or generated by UAS) and that early dialogs cannot be used to generate > new requests. So I can keep this information, for example, storing the > response received > > Another question. RFC 3261 says that ACK and CANCEL are not target > requests inside a dialog. How can I know which are the requests that are > "target refresh"? I need this information because after a dialog is > confirmed, it can only be destroyed or its remote target can be changed > by target refresh requests. > [ABN] A target refresh request is one which can update the contact address in the peer. As of now defined target refresh requests available are re-INVITE, REFER, UPDATE, SUBSCRIBE, NOTIFY. You can refer the link http://www1.ietf.org/mail-archive/web/sip/current/msg09215.html > > Thanks. > > -- > Marco Ambu > Abbeynet S.p.A. (www.abbeynet.it) > > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
