Summary:	ASTERISK-06621: [patch] sendonly RTP stream handling
Reporter:	Henning Holtschneider (hehol)	Labels:
Date Opened:	2006-03-26 09:58:07.000-0600	Date Closed:	2006-06-01 08:24:20
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_sip/Interoperability
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) sendonly.patch
Description:	When a a=sendonly RTP stream is being received, Asterisk does not reply with a=recvonly, violating RFC 3264, paragraph 6.1. This may cause a call that has been placed on hold on the remote end, to be stuck on hold forever. The attached patch corrects this behaviour. When a a=sendonly stream is being received, Asterisk will reply with a=recvonly until a=sendrecv is being received from the other end.
Comments:	By: Olle Johansson (oej) 2006-05-02 15:33:02 Great stuff. Noticed this at SIPit. Will look into your patch. By: Olle Johansson (oej) 2006-05-16 14:56:18 I think there's a better way. It won't harm to send revonly when a channel is on hold, always. By: Olle Johansson (oej) 2006-05-16 15:15:08 I committed another patch to svn trunk. Please test and see if that solves your issue. Thanks! By: Olle Johansson (oej) 2006-05-16 15:40:57 Another issue here is that we should continue to send RTCP even if we're on hold. I don't believe that happens in Asterisk today. By: Henning Holtschneider (hehol) 2006-06-01 04:40:10 We just finished tests with your patch and I can confirm that it solves the issued we had. I will now backport your changes to the current stable version of Asterisk because we need this in a production environment. If I may upload the patch, keep this issue open. Otherwise, I think this can be considered closed. By: Olle Johansson (oej) 2006-06-01 08:24:06 Well, this bug is fixed and done. Let's not keep reports open unless there is an open issue. We won't add functionality to old releases, so a 1.2 is not that important and 1.4 is not that far away anyway. Thanks for your contribution!