[asterisk-bugs] [JIRA] (ASTERISK-24594) SIP Signal 183 Session Progress doesn't update Channel status to

[Sid Mason (JIRA)]

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

Sid Mason updated ASTERISK-24594:
---------------------------------

    Description: 
When SIP signal 183 Session Progrress from called party received to asterisk chan_sip.so , it doesn't update the channel status.

Therefore AMI does not report an event on this signal.

I have compiled a patch for this issue to be fixed on channels\chan_sip.c 

Line 23030:
ADD:
if (ast_channel_state(p->owner) != AST_STATE_UP) {

			ast_setstate(p->owner, AST_STATE_PRERING);

}

  was:
When SIP signal 183 Session Progrress from called party received to asterisk chan_sip.so , it doesn't update the channel status.

Therefore AMI does not report an event on this signal.

I have compiled a patch for this issue to be fixed on channels\chan_sip.c 

Line 23030:
ADD:
if (ast_channel_state(p->owner) != AST_STATE_UP) {
			ast_setstate(p->owner, AST_STATE_PRERING);
}


> SIP Signal 183 Session Progress doesn't update Channel status to 
> -----------------------------------------------------------------
>
>                 Key: ASTERISK-24594
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24594
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/Messaging
>    Affects Versions: 11.14.1, 13.0.1
>         Environment: Centos 6.5 64bit
>            Reporter: Sid Mason
>            Severity: Minor
>
> When SIP signal 183 Session Progrress from called party received to asterisk chan_sip.so , it doesn't update the channel status.
> Therefore AMI does not report an event on this signal.
> I have compiled a patch for this issue to be fixed on channels\chan_sip.c 
> Line 23030:
> ADD:
> if (ast_channel_state(p->owner) != AST_STATE_UP) {
> 			ast_setstate(p->owner, AST_STATE_PRERING);
> }



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