[asterisk-bugs] [JIRA] (ASTERISK-18073) If INVITE transaction runs in parallel with INFO transaction, 200 OK for INVITE does not contain contact headers

[Joshua Colp (JIRA)]

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

Joshua Colp updated ASTERISK-18073:
-----------------------------------

    Affects Version/s: 13.18.4

> If INVITE transaction runs in parallel with INFO transaction, 200 OK for INVITE does not contain contact headers
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-18073
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-18073
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/Video
>    Affects Versions: 1.8.4, 13.18.4
>         Environment: Linux Fedora Core 9.
>            Reporter: Emmanuel BUU
>            Severity: Minor
>         Attachments: chan_sip.patch
>
>
> In case of inbound video calls using 183 session progress, the following call flow may happend
> UA                    asterisk
> INVITE --------------->
> <--------- 183 Session Progress
> INFO (Fast Update Request) --->
> <----- 200 OK (INFO) ----------
> ...
> <----- 200 OK (INVITE) --------
> In that case, the 200 OK message for INVITE does not contain any "Contact" header which in our case breaks the loose routing handling of our SIP proxy.
> After investigation, we found out that the function respprep() in chan_sip.c was simply using the LAST method name in the dialog to decide whether or not the Contact header was needed rather than the method matchin THIS request. 



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