SDP negotiation: Call hold problems

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 ?

 

cheers,

 

Rafael Maia

 

 

 
 		 	   		  
_________________________________________________________________
Hotmail: Trusted email with powerful SPAM protection.
http://clk.atdmt.com/GBL/go/177141665/direct/01/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20091125/f998f365/attachment.html>


[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux