On Wed, Nov 25, 2009 at 10:44 PM, Rafael Maia <rmaia_lcm at hotmail.com> wrote:
> Hi,
> i am having problems debugging an SDP negotiation related to call hold.
>
> I receive a an INVITE with the following lines of SDP from an unknown user
> agent:
>
> ...
> a=sendonly
> m=audio 36884 RTP/AVP 8 101
> c=IN IP4 10.184.13.134
> ...
>
>
> PJSIP replies incorrectly with a 200 OK "sendrecv":
>
> ...
> m=audio 57928 RTP/AVP 8 101
> a=rtpmap:8 PCMA/8000
> a=sendrecv
> ...
>
> The "sendonly" is replied with a "sendrecv".
> According to RFC 4566 (5. SDP Specification, page 10), if a "a=sendonly" is
> put at a session level it affects all media sessions ("m=").
>
> Can anyone tell me if PJSIP supports the "a=sendonly" at session level ?
>
We support call hold with sendonly/recvonly. As usual, to find out
what the problem is, please state the PJSIP version that you're using
and send us the log.
Cheers
Benny
