Plan Status: #185 was successful
Build: #185 was successful
Build Result Summary
Details
- Trigger
- This build occurred because it is a dependant of ASTTRUNK-LUCID-1237.
- Revision
- 345883
- Completed
- Duration
- 3 minutes
- Successful since
- #63 ()
- Labels
- None
Test Summary
- 0 New Failures
- 0 Existing Failures
- 0 Fixed
Code Changes
-
Terry Wilson
Default to nat=yes; warn when nat in general and peer differ
It is possible to enumerate SIP usernames when the general and user/peer
nat settings differ in whether to respond to the port a request is sent
from or the port listed for responses in the Via header. In 1.4 and 1.6.2,
this would mean if one setting was nat=yes or nat=route and the other was
either nat=no or nat=never. In 1.8 and 10, this would mean when one was
nat=force_rport and the other was nat=no.
In order to address this problem, it was decided to switch the default
behavior to nat=yes/force_rport as it is the most commonly used option
and to strongly discourage setting nat per-peer/user when at all possible.
For more discussion of the issue, please see:
http://lists.digium.com/pipermail/asterisk-dev/2011-November/052191.html
(closes issue ASTERISK-18862)
Review: https://reviewboard.asterisk.org/r/1591/
........
Merged revisions 345776 from http://svn.asterisk.org/svn/asterisk/branches/1.4
........
Merged revisions 345800 from http://svn.asterisk.org/svn/asterisk/branches/1.6.2
........
Merged revisions 345828 from http://svn.asterisk.org/svn/asterisk/branches/1.8
........
Merged revisions 345830 from http://svn.asterisk.org/svn/asterisk/branches/10
-
Tilghman Lesher
Update the documentation to better clarify how the existing commands work.
Review: https://reviewboard.asterisk.org/r/1593/
........
Merged revisions 345682 from http://svn.asterisk.org/svn/asterisk/branches/1.8
........
Merged revisions 345683 from http://svn.asterisk.org/svn/asterisk/branches/10