Re: [Sip-implementors] Can EP send media only peer supports

comment at end. Dale Worley wrote: > On Fri, 2009-08-14 at 14:41 +0800, Rockson Li (zhengyli) wrote: >> I think answerer can add additional codec G729 here per sec 6.1 of >> rfc3264 >> >> >>The stream MAY indicate additional media formats, not listed in the >>corresponding stream in the o

Re: [Sip-implementors] Can EP send media only peer supports

On Fri, 2009-08-14 at 14:41 +0800, Rockson Li (zhengyli) wrote: > I think answerer can add additional codec G729 here per sec 6.1 of > rfc3264 > > >The stream MAY indicate additional media formats, not listed in the >corresponding stream in the offer, that the answerer is willing to >

[Sip-implementors] SIPit registration closes in 3 weeks.

SIPit 25 will be at the University of New Hampshire Interoperability Labs September 14-18, 2009. Registration is currently open, but it closes September 4. If you are planning to attend, please take a moment to register today. More information is available at . RjS _

Re: [Sip-implementors] Can EP send media only peer supports

My two cents of thought. I think when the answerer will include additional media format, the media has to be again re-negotiated between offerer-answerer and that should be done by offerer if he thinks that additional media format is best way to exchange media ( The only question would be if the

Re: [Sip-implementors] Can Reason header be inluded in 18x and 200 OKresponses to INVITE ?

Kapil, Here is my two cents for your query whether is allowed in 18 and 2xx or not and why one has not seen any usage of reason header in 18x and 200ok so far but has seen it only in error responses. First one is already answered by you and our friends by referring to RFC-3326. But RFC-3326 als

Re: [Sip-implementors] Can Reason header be inluded in 18x and 200 OKresponses to INVITE ?

Hi, If you include it in 1XX and 2XX it should not be a problem. RFC does not say anywhere that it MUST not be included. It depends on the usage. Thanks, Shyam -Original Message- From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-boun...@lists.cs.columbia.edu]