[asterisk-bugs] [JIRA] (ASTERISK-25908) Wiki documentation: Deployment - Guides for Asterisk configuration with NAT and firewalls - scope out

[Rusty Newton (JIRA)]

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

Rusty Newton updated ASTERISK-25908:
------------------------------------

    Summary: Wiki documentation: Deployment - Guides for Asterisk configuration with NAT and firewalls - scope out  (was: Wiki documentation: Deployment/Deployment in your Network - Create best practices and guides for Asterisk configuration with NAT and firewalls)

> Wiki documentation: Deployment - Guides for Asterisk configuration with NAT and firewalls - scope out
> -----------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-25908
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25908
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Documentation
>            Reporter: Rusty Newton
>            Severity: Minor
>
> https://wiki.asterisk.org/wiki/display/AST/Deployment+In+Your+Network
> Common issues that administrators face when deploying Asterisk is proper configuration for networks with various combinations of NAT, firewalls and SIP ALGs.
> We should cover the range of related options in at least the two most common channel drivers and provide a few concrete examples that cover common scenarios for the network.
> It should be easy to search through the mailing lists and community forums to get an idea on the specifics of what administrators have issues with.
> I did write https://wiki.asterisk.org/wiki/display/AST/Configuring+res_pjsip+to+work+through+NAT  and Josh wrote https://wiki.asterisk.org/wiki/display/~jcolp/ICE%2C+STUN%2C+and+TURN+Support which is the sort of content that will be relevant in this section.
> Again the focus here is to simply cover a few of the most common scenarios.



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