[asterisk-bugs] [JIRA] (ASTERISK-24824) chan_sip: Asterisk fails to re-activate an inactive media session when an offer does not contain a=sendrecv

Ashley Sanders (JIRA) noreply at issues.asterisk.org
Mon Feb 23 15:37:34 CST 2015


     [ https://issues.asterisk.org/jira/browse/ASTERISK-24824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ashley Sanders updated ASTERISK-24824:
--------------------------------------

    Description: 
1. From Phone A, send an offer to Phone B to establish a call
2. From Phone B, send an offer to Phone A to put the call on hold. 
3. Observe that the MOH start event occurs.
4. From Phone B, send an offer to Phone A to 'un-hold' the call (ensure that the direction attribute from the offer's SDP is omitted)
5. Observe that the MOH stop event never occurs.

This is not the anticipated state. If no direction attribute is present, the direction of the media stream is expected to default to "sendrecv", which should have caused the MOH stop event to occur. 

According to RFC 4566 (Section 6. SDP Attributes): "If none of the attributes "sendonly", "recvonly", "inactive", and "sendrecv" is present, "sendrecv" SHOULD be assumed as the default for sessions that are not of the conference type "broadcast" or "H332" [...]"



  was:
1. From Phone A, send an offer to Phone B to establish a call
2. From Phone B, send an offer to Phone A to put the call on hold. 
3. Observe that the MOH start event occurs.
4. From Phone B, send an offer to Phone A to 'un-hold' the call (ensure that the direction attribute from the offer's SDP is omitted)
5. Observe that the MOH stop event never occurs.

This is not the anticipated state. According to RFC 4566 (Section 6. SDP Attributes): "If none of the attributes "sendonly", "recvonly", "inactive", and "sendrecv" is present, "sendrecv" SHOULD be assumed as the default for sessions that are not of the conference type "broadcast" or "H332" [...]"


> chan_sip: Asterisk fails to re-activate an inactive media session when an offer does not contain a=sendrecv
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-24824
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24824
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 1.8.23.1
>            Reporter: Ashley Sanders
>
> 1. From Phone A, send an offer to Phone B to establish a call
> 2. From Phone B, send an offer to Phone A to put the call on hold. 
> 3. Observe that the MOH start event occurs.
> 4. From Phone B, send an offer to Phone A to 'un-hold' the call (ensure that the direction attribute from the offer's SDP is omitted)
> 5. Observe that the MOH stop event never occurs.
> This is not the anticipated state. If no direction attribute is present, the direction of the media stream is expected to default to "sendrecv", which should have caused the MOH stop event to occur. 
> According to RFC 4566 (Section 6. SDP Attributes): "If none of the attributes "sendonly", "recvonly", "inactive", and "sendrecv" is present, "sendrecv" SHOULD be assumed as the default for sessions that are not of the conference type "broadcast" or "H332" [...]"



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list