[SIPForum-discussion] Sdp attribute for Call hold

[Keyur Amin]

Hi Ankur,

a=sendonly is the correct way. Here is some text from the rfc. 

5.1 Unicast Streams If the offerer wishes to only send media on a stream to its peer, it MUST mark the stream as sendonly with the "a=sendonly" attribute.  We refer to a stream as being marked with a certain direction if a direction attribute was present as either a media stream attribute or a session attribute.  If the offerer wishes to only receive media from its peer, it MUST mark the stream as recvonly.  If the offerer wishes to communicate, but wishes to neither send nor receive media at this time, it MUST mark the stream with an "a=inactive" attribute.
 
Thanks,
Keyur Amin

________________________________

 
 


________________________________
 From: "Banda, Srinivas (Srinivas)" <sribanda at avaya.com>
To: ankur bansal <abh.ankur at gmail.com>; "discussion at sipforum.org" <discussion at sipforum.org> 
Sent: Wednesday, June 26, 2013 1:45 AM
Subject: Re: [SIPForum-discussion] Sdp attribute for Call hold
 


 
Hi Ankur,
 
If a party is holding the call and the media attribute says SENDONLY, it means the party is using the MUSIC-ON-HOLD feature.
 
Regards
Srinivas
 
From:discussion-bounces at sipforum.org [mailto:discussion-bounces at sipforum.org] On Behalf Of ankur bansal
Sent: Wednesday, June 19, 2013 11:26 AM
To: discussion at sipforum.org
Subject: [SIPForum-discussion] Sdp attribute for Call hold
 
Hi All
 
Can anyone explain why a=sendonly is sent in offer from side performing HOLD ?
I think a=inactive should be right way of holding call .
Any specific scenario which explain when to use sendonly and when inactive 
 
Thanks & regards
Ankur Bansal
_______________________________________________
This is the SIP Forum discussion mailing list
TO UNSUBSCRIBE, or edit your delivery options, please visit http://sipforum.org/mailman/listinfo/discussion
Post to the list at discussion at sipforum.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20130627/229699e8/attachment-0002.html>