[ previous ] [ next ] [ threads ]
 To :  yate@v...
 From :  Bill Simon <bill@b...>
 Subject :  Problem with SIP SDP and call hold
 Date :  Mon, 25 May 2015 10:57:04 -0400
I have found a problem with Yate's handling of SDP and cannot determine a fix.

If a caller issues a re-invite to put the call on hold, his SDP includes either "a=sendonly" or "a=inactive" to indicate that the media stream is muted.

Yate responds with a SIP 200 OK which does not echo the attribute back.

Most clients don't seem to care but at least one client I am using (Zoiper) then hangs up the call with the error "not implemented."

Other servers echo the attribute back to the client in the SIP 200 message, so I believe this is is the expected behavior. Unfortunately the RFC is not clear.