[asterisk-bugs] [JIRA] (ASTERISK-27408) Identify causes and fix pjsip/resolver/srv/failover/in_dialog/transport_tcp

[Corey Farrell (JIRA)]

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

Corey Farrell commented on ASTERISK-27408:
------------------------------------------

bq. We could create a new dialog for the new request but a safer alternative is to just not delete the object from the container on a 503 when failover processing is in process.

My only concern with this is making sure we eventually clean the object.  IE if all failover options produce 503 or the rest don't respond.  I'm saying this without having looked at the code, maybe the required checks/timers are already in place to deal with this.  Just want to make sure this is considered.

> Identify causes and fix pjsip/resolver/srv/failover/in_dialog/transport_tcp
> ---------------------------------------------------------------------------
>
>                 Key: ASTERISK-27408
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27408
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Third-Party/pjproject
>    Affects Versions: GIT, 15.1.1
>            Reporter: Corey Farrell
>         Attachments: 0020-sip_parser-Add-validity-checking-for-numeric-header-.patch, fails.pcapng, works.pcapng
>
>
> With the recent security fix for the sip_parser, 2 of the resolver unbound tests fail.  
> transport_unspecified also fails but transport_udp passes.
> It's possible that the patch exposed some other issue.
> 2 pcaps attached



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