Indeed. Looks and works very well.
- Jeff On Apr 14, 2010, at 7:10 AM, Anca Vamanu wrote: > Hi Jeff, > > Now this problem with IP address in from tag is fixed. Now the tag is no > longer obtained by concatenating the callid with the from tag in the > previous message, but an MD5 function is applied on the two. > > Regards, > > -- > Anca Vamanu > www.voice-system.ro > > > > Bogdan-Andrei Iancu wrote: >> Hi Jeff, >> >> Jeff Pyle wrote: >>> Anca, >>> >>> It seems the new From tag is constructed from the call-id of the >>> originating INVITE. Many UAs include their IP address in the >>> call-id. As such the true originating IP address makes it through >>> the top-hiding scenario. >>> >> indeed, that might be a problem! >>> A second place it seems to make it through is the owner of the SDP. >>> >>> It's in the connection info as well, but we can take care of that >>> with rtpproxy or Mediaproxy. No problem here. >>> >> yes, the b2b module take care of signalling - for SDP you need to use >> a media relay. >>> Are there any user-configurble options to minimize the exposure of >>> the original IP? >>> >> in SDP ? if so, nathelper module has the a flag for it - see "o" in: >> >> http://www.opensips.org/html/docs/modules/1.6.x/nathelper.html#id271384 >> >> Regards, >> Bogdan >>> >>> Regards, >>> Jeff >>> _______________________________________________ >>> Users mailing list >>> [email protected] >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >>> >> >> _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
