[OpenSIPS-Users] topology hiding

[BJ Quinn]

Hi, 

I'd like to use topology_hiding(), but I can't quite understand how to integrate it into the routing part of the configuration file. I have my opensips box on a public IP and some machines initiating calls through the opensips box that are also on public IPs, so no NAT going on or anything like that. However, a couple of the carriers we're trying to use don't like seeing the IP address of the machines initiating the call (in Route and Contact headers, etc.) and that's causing problems including some carriers don't think the call has set up properly (even though it goes through), which leads to missing BYEs. Anyway, seems like topology_hiding() is a great idea anyway, regardless of the fact that I've had a carrier specifically request it. 

I'm using 1.10.  So I've started with the basic Residential scenario made from osipsconfig. I didn't check any of the options (like ENABLE_TCP, USE_ALIASES, etc.) and modified only my IP address and added a couple of aliases for the machines making the calls.  I added the following outside of the routing logic to load the dialog module to make topology_hiding() available.

  loadmodule "dialog.so"

Then, under "if(has_totag()) { if (loose_route()) {" I added --

  if ($DLG_status==NULL && !match_dialog() ) {
    xlog(" cannot match request to a dialog \n");
  }

And outside of the "if(has_totag())" section I added --

  if (is_method("INVITE")) {
    create_dialog();
    topology_hiding();
  }

Without these added sections, things are fine on some carriers and with other carriers I have the problems described above which causes me to want to enable topology hiding.  With these added sections, I get 408 timeouts since it appears that the opensips box is responding NOT HERE to the carrier's 200 OKs.

Also, possibly unrelated, in either case I'm getting a weird "\304" added to my Route header.  Should I just replace the Route header and regex that out?

Route: <sip:xx.xx.xx.xx:\304;lr>

Thanks!

-BJ Quinn