[asterisk-bugs] [JIRA] (ASTERISK-26998) res_pjsip_session: INVITE retransmissions could still setup the same call again.

[Friendly Automation (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-26998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237015#comment-237015 ] 

Friendly Automation commented on ASTERISK-26998:
------------------------------------------------

Change 5632 merged by Jenkins2:
res_pjsip_session.c: Process initial INVITE sooner. (key exists)

[https://gerrit.asterisk.org/5632|https://gerrit.asterisk.org/5632]

> res_pjsip_session: INVITE retransmissions could still setup the same call again.
> --------------------------------------------------------------------------------
>
>                 Key: ASTERISK-26998
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26998
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_session
>    Affects Versions: 13.15.0, 14.4.0
>            Reporter: Richard Mudgett
>            Assignee: Richard Mudgett
>
> There is some leftover code that tries to defer processing an initial incoming INVITE to a session's serializer.  A change done for ASTERISK-26088 made it so the session's serializer is the same calculated distributor serializer the INVITE is supposed to be initially processed in.  Since we are already running in that serializer it is not necessary to defer the processing and doing so would cause the same call resetup problem the earlier change attempted to fix.
> This problem will only express itself under load when the initial INVITE processing is delayed enough that retransmissions get queued in the backlog.  A symptom of the problem is a message containing "(key exists)" for an INVITE message is logged.



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