[asterisk-bugs] [JIRA] (ASTERISK-22407) Error out at config parsing when two or more transports are set to bind on the same interface

Mark Michelson (JIRA) noreply at issues.asterisk.org
Tue Sep 10 09:21:03 CDT 2013


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

Mark Michelson closed ASTERISK-22407.
-------------------------------------

    Resolution: Won't Fix

After discussing this with Rusty, the "weird behaviour" mentioned in the issue description was that calls to endpoints would not work due to transport settings on endpoints pointing to seemingly non-existent transports.

As it turns out, the transport in question was not loading at startup due to binding errors in PJSIP. There was a warning message that had this information as well. So in this particular case, a misconfiguration caused a warning at startup, and another warning at call-time.

The capability to not load res_pjsip.so on misconfiguration currently is not an option since sorcery does not operate that way. As it stands, we are presenting the information as best we can, so no further action will be taken on this issue.
                
> Error out at config parsing when two or more transports are set to bind on the same interface
> ---------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-22407
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22407
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Resources/res_pjsip
>    Affects Versions: SVN, 12
>         Environment: SVN-branch-12-r397614
>            Reporter: Rusty Newton
>            Severity: Minor
>
> If you accidentally or purposefully configure two transports to bind to the same interface, you'll get some weird behaviour!
> If possible, let's error out when parsing the config to prevent any confusion.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list