Hi Paul

The HOLD request is nothing but a re INVITE request indicating HOLD.

Could you give a use case where such a thing may happen? I have not come
across any scenario where in the process of putting remote party on
HOLD, media parameters like IP/codec getting changed.  If this happens,
then it cannot be considered a HOLD request.

So how do u distinguish a HOLD request from a non HOLD one if in both
the cases the media parameters (other than a=.....) change?


Regards
Ranjit

-----Original Message-----
From: Paul Kyzivat [mailto:[email protected]] 
Sent: Tuesday, August 25, 2009 12:07 AM
To: Avasarala Ranjit-A20990
Cc: [email protected]; [email protected];
[email protected]; [email protected]
Subject: Re: [Sip-implementors] [Sip] 200 OK response for hold with
different media capabilities



Avasarala Ranjit-A20990 wrote:
> no it should not. For a Hold request, you do not send any media 
> capabilities. U only change the existing media description lines to 
> indicate HOLD.

I beg to differ.

Technically there is no HOLD request.
All there is is an offer that offers to change a media attribute, from
sendrecv to sendonly or inactive, or from sendonly or recvonly to
inactive.

The response may change anything that is permitted to be changed in the
answer, given the offer. So it may not add m-lines, but it can certainly
change media addresses, and within limits may change media formats
(codecs).

        Thanks,
        Paul

> Regards
> Ranjit
> 
>  
> 
> ________________________________
> 
> From: [email protected] [mailto:[email protected]] On Behalf Of 
> [email protected]
> Sent: Monday, August 24, 2009 3:25 PM
> To: [email protected]; [email protected];
> [email protected]
> Subject: [Sip] 200 OK response for hold with different media 
> capabilities
> 
> 
> 
> 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-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

Reply via email to