>> Gateway can respond with media capabilities to a offer less INVITE if it is >> acting as a 3PCC, not otherwise. A small correction here. I do not know what Gateway you are talking about here. For me, a gateway is a SIP end-point and would respond with its media capabilities for offer-less INVITE.
On Mon, Aug 24, 2009 at 8:59 PM, Vikram Chhibber<[email protected]> wrote: > On Mon, Aug 24, 2009 at 6:44 PM, Avasarala > Ranjit-A20990<[email protected]> wrote: >> Hi Vikram >> >> Gateway can respond with media capabilities to a offer less INVITE if it is >> acting as a 3PCC, not otherwise. >> > This is exactly what I wrote in my mail. > I would again emphasize Paul’s comment. “Hold” is application’s > interpretation of some values in SDP such as offer with a = > sendonly/inactive. There is no such SDP called as hold SDP. > Furthermore, this offer should be processed as a normal offer as > there could be a change in IP/port, codecs or codecs attributes. >> >> Regards >> Ranjit >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Vikram >> Chhibber >> Sent: Monday, August 24, 2009 11:35 PM >> To: [email protected] >> Cc: [email protected]; [email protected]; [email protected] >> Subject: Re: [Sip-implementors] [Sip] 200 OK response for hold withdifferent >> media capabilities >> >> The gateway can respond with different media capabilities in 200 OK response >> for offer-less INVITE not for offer that we view as for hold. >> The gateway should create response as per rules defined in RFC 3264. >> As far as SIP signalling is concerned, hold INVITE request is treated as a >> regular re-INVITE request. >> >> On Mon, Aug 24, 2009 at 2:55 AM, <[email protected]> wrote: >>> Hi All, >>> >>> >>> >>> I have a small query related to HOLD request being sent out. >>> >>> >>> >>> For a hold request, can gateway respond with different media >>> capabilities in 200 OK response? >>> >>> >>> >>> Is the HOLD treated as any normal Re-INVITE? >>> >>> >>> >>> Regards, >>> >>> Sunil. >>> >>> >>> >>> Please do not print this email unless it is absolutely necessary. >>> >>> The information contained in this electronic message and any >>> attachments to this message are intended for the exclusive use of the >>> addressee(s) and may contain proprietary, confidential or privileged >>> information. If you are not the intended recipient, you should not >>> disseminate, distribute or copy this e-mail. Please notify the sender >>> immediately and destroy all copies of this message and any attachments. >>> >>> WARNING: Computer viruses can be transmitted via email. The recipient >>> should check this email and any attachments for the presence of >>> viruses. The company accepts no liability for any damage caused by any >>> virus transmitted by this email. >>> >>> www.wipro.com >>> >>> _______________________________________________ >>> Sip mailing list https://www.ietf.org/mailman/listinfo/sip >>> This list is for NEW development of the core SIP Protocol Use >>> [email protected] for questions on current sip Use >>> [email protected] for new developments on the application of sip >>> >> >> _______________________________________________ >> Sip-implementors mailing list >> [email protected] >> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors >> > _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [email protected] for questions on current sip Use [email protected] for new developments on the application of sip
