Hi, Paul answered your question. However if something is actually sending mixed case "SendOnly", it might have interoperability problems since RFC 4566 section 5 discusses values as being case-sensitive unless a specific field defines otherwise.
> -----Original Message----- > From: [email protected] [mailto:sip- > [email protected]] On Behalf Of Sylvester, Prasanth > (Nokia - IN/Mumbai) > Sent: Tuesday, May 12, 2015 9:35 AM > To: sip-implementors > Subject: [Sip-implementors] SIP Call on hold - Reinvite Session Attribute Vs > Media Attribute > > Hi Team, > > I've a small doubt. I have a working call where A party is talking to B > party. B party putts the call on hold, however I see "Session Attribute" with > a value "SendOnly". Mostly I've seen it coming in Media Attribute. > > "Session Attribute (a): sendonly" Instead of "Media Attribute (a): SendOnly". > > What's the difference? > > I've read some phone (PolyCom) while its set to a different settings, do > this. > For e.g > voIpProt.SIP.useRFC2543hold 0 or 1 0 > > When the phone is set to 0, use SDP media direction parameters (such as > a=sendonly) per RFC 3264 Otherwise use the obsolete c=0.0.0.0 RFC2543 > technique > > Could someone throw some light? Just trying to figure out the difference? > > Cheers, > > Sylvester _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
