[asterisk-bugs] [JIRA] (ASTERISK-26447) chan_sip: Better docs needed for SIP_NAT_FORCE_RPORT and SIP_NAT_RPORT_PRESENT
Asterisk Team (JIRA)
noreply at issues.asterisk.org
Thu Oct 6 15:59:01 CDT 2016
[ https://issues.asterisk.org/jira/browse/ASTERISK-26447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232572#comment-232572 ]
Asterisk Team commented on ASTERISK-26447:
------------------------------------------
Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.
A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.
Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].
> chan_sip: Better docs needed for SIP_NAT_FORCE_RPORT and SIP_NAT_RPORT_PRESENT
> ------------------------------------------------------------------------------
>
> Key: ASTERISK-26447
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-26447
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Channels/chan_sip/General
> Affects Versions: 13.11.2, 14.0.2, GIT
> Reporter: Corey Farrell
> Severity: Minor
>
> Need to document flow of {{SIP_NAT_FORCE_RPORT}} and {{SIP_NAT_RPORT_PRESENT}} between global_flags, peers and pvt. sip.h should clearly document how these flags are set, copied and which location is preferred for checking the flag.
> This ticket is created in response to the fix of ASTERISK-26438.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list