Hi Richard, if i understood well your issue, you are using SEMS behind a NAT, and the callers may also be behind another (or same) NAT. Is that right? The reason why it does not work at the moment is that it never has been a covered scenario. As i understood, it would be enough for your scenario to be able to configure the external IP (i guess you have some port forwarding mechanism) (and maybe the external port also), is that right?
I would like to avoid to implement to much NAT traversal stuff like STUN & Co., but i think that a possibility to configure the external IP and port would be a pretty easy thing to do. Cheers Raphael. Richard Newman wrote: > Has anyone tried this and got it to work? My SDP contains SEMS's > private IP address, so I don't get any media. > > I don't see any configuration directive that will say "put this damn > IP address in the SDP body"; all of the params like "sip_ip" affect > the address that is bound, which isn't what I want. (Because it won't > work, because the machine isn't aware of the external IP address.) > > Google/mailing lists give advice for SEMS + SER + rtpproxy + nathelper > + ..., which is all well and good, but I'd like to use our shiny new > built-in SIP engine. > > If the conclusion is "it won't work", I might spend some time > investigating a config addition to do this simple kind of SDP > modification. > > Any thoughts, folks? > > Thanks, > > -R > > P.S., I'm actually trying this out on EC2: very cool, but running > without NAT isn't a possibility. > _______________________________________________ > Semsdev mailing list > [email protected] > http://lists.iptel.org/mailman/listinfo/semsdev > _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
