I just committed a first pass at this as revision 917. A new configuration option, "public_ip", has been added and documented in the sample config file. It gets printed out on startup like its siblings.
A utility method (AmSession::advertisedIP()) returns either the public IP, if set, or the local IP. I've changed the appropriate parts of AmSdp::genRequest() and AmSdp::genResponse() to include a call to this method instead of using AmConfig::LocalIP directly. They still bind to the local IP, of course. I've tested with and without "public_ip". Behavior seems unchanged with public_ip omitted, and I successfully received media from SEMS announcement running on EC2 with it included. (Hooray!) I'll spend a little more time on this tomorrow; Contact and Via headers probably still need attention. Other developers with existing test scenarios: please make sure I haven't broken anything! Thanks, -R _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
