On Fri, Jan 30, 2009 at 8:58 AM, Mark Gertsvolf <[email protected]> wrote: > Mircea Carasel wrote: >> The public address gets generated in the >> nattraversalrules.xml only when the checkbox: Behind NAT is checked. >> (The help text says: >> When the server is deployed behind a NAT, the "Public IP >> address" field must be set to the Internet-facing IP address >> of the NAT / firewall device.If the server is not behind a >> NAT this field is ignored.) I tested on the current build and >> the behavior is as designed I don't know if this is correct >> or not - but this was the requirement. > > In theory it might be possible and useful to use SIP trunking feature in > a deployment where both sipX and the phones are on a routable network > and not behind a NAT. The sipXconfig dependency on the "Behind NAT" > checkbox when generating public IP address field causes headaches with > the above setup. Use of STUN server would be required as a workaround. > > What was the rational for the requirement?
Not sure but in retrospect, "rationality" had nothing to do with it ( and it was my lack thereof ). Ranga > > Thanks, > Mark. > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > -- M. Ranganathan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
