But a word of caution on whether "most implementations accept/ initiate this behavior". When it comes to implementation, you have to test case by case. There are many implementations which may not even act on the directionality attribute lines and there are implementations which still follows the RFC2543 way of putting call on hold, which sets the ISDP's c line destination address to zero (0.0.0.0).
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Kyzivat Sent: Friday, August 11, 2006 1:18 PM To: Kapil Nayar Cc: sip-implementors@cs.columbia.edu Subject: Re: [Sip-implementors] ReInvite for Call Hold ON/ OFF andcodec re-negotiation Kapil Nayar wrote: > Hi > > The SDP/ SIP standards donot restrict the Call Hold ON/ OFF (ReInvite > with mode sendonly) and Codec renegotiation (ReInvite with a different > codec list) to be combined in the same transaction (ReInvite with mode > sendonly and different codec list). > Are there any restrictions/ limitations in doing this? > Do most implementations accept/ initiate this behavior? You are asking if it is permissible to change the directionality (sendonly, sendrecv, readonly, inactive) of a media stream and the codecs in a single offer/answer? Yes - its fine to do that. The way you phrase the question suggests you consider the directionality attributes to simply be a way of communicating the Call Hold feature. While the directionality attributes can be used to indicate a desired state due to placing the call on hold, they can also be used for other purposes. Paul _______________________________________________ Sip-implementors mailing list Sip-implementors@cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list Sip-implementors@cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
