<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div>Ok so it looks like 1.10 may have been the problem. Things seem to be working with the same config on 1.9. I'm still getting that funny /304 in the route header, but now I've discovered that it's the software initiating the call that is adding that /304 (it only added it when it's in proxy mode, so I didn't see it in the other invites generated by this software from before I tried to put it behind the opensips proxy).<br></div><div><br></div><div>So now here's my question. I'd like to simply strip out the /304 from the route header that comes from the software initiating the call (I don't think I can change that software). But that would require modifying the route header manually AND with topology hiding. Is that allowed? Do I do one or the other first?<br></div><div><br></div><div>Thanks!<br></div><div><br></div><div>-BJ<br></div><div><br></div><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;" data-mce-style="color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"BJ Quinn" <bjquinn@seidal.com><br><b>To: </b>"OpenSIPS users mailling list" <users@lists.opensips.org><br><b>Sent: </b>Saturday, February 8, 2014 12:33:38 PM<br><b>Subject: </b>Re: [OpenSIPS-Users] topology hiding<br><div><br></div><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000" data-mce-style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000;"><div>According to <span class="Object" id="OBJ_PREFIX_DWT183_com_zimbra_url"><span class="Object" id="OBJ_PREFIX_DWT217_com_zimbra_url"><span class="Object" id="OBJ_PREFIX_DWT344_com_zimbra_url"><span class="Object" id="OBJ_PREFIX_DWT361_com_zimbra_url"><a href="http://lists.opensips.org/pipermail/users/2013-October/026992.html" target="_blank" data-mce-href="http://lists.opensips.org/pipermail/users/2013-October/026992.html">http://lists.opensips.org/pipermail/users/2013-October/026992.html</a></span></span></span></span> it appears that there's a bug in 1.10 for dialog based topology hiding? Maybe that's my problem?</div><div><br></div><div>I'm using the RHEL RPMs for 1.10 stable. Maybe the issue mentioned in that post isn't my issue, or maybe the fix has been applied to the 1.10 RPMs? Or maybe I should downgrade to 1.9 and try again?</div><div><br></div><div>-BJ</div><div><br></div><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;" data-mce-style="color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"BJ Quinn" <bjquinn@seidal.com><br><b>To: </b>"OpenSIPS users mailling list" <users@lists.opensips.org><br><b>Sent: </b>Friday, February 7, 2014 4:37:45 PM<br><b>Subject: </b>Re: [OpenSIPS-Users] topology hiding<br><div><br></div><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000" data-mce-style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000;"><div>The traffic goes from the server making the call to the opensips proxy to the carrier. The /304 doesn't exist in the original invite from the server that makes the call. Do you want to see the packets from the calling server to the opensips box to the carrier?<br></div><div><br></div><div>But most importantly, I'm still having trouble getting topology hiding to work. I made the change you suggested, but it appears that opensips is throwing away all responses it's receiving from the carrier, which means that opensips thinks the call never got set up and the invite was never accepted, and then it eventually responds 408 to the original calling server. In fact the invite WAS accepted, and the carrier sent back a 200 ok, but opensips threw it away and never acknowledged it. The outgoing invite from the opensips server looks correct -- opensips has modified the route and contact headers to its own IP, but obviously it doesn't know what to do with the responses that are coming back to it.<br></div><div><br></div><div>The /304 issue is odd and could be causing us issues with certain carriers, but right now I'd like to get topology hiding working with even ONE carrier, and I can't do that yet. All I did was add the section you showed in your response --<br></div><div><br></div><div> if (loose_route() || match_dialog()) {<br> if ($DLG_status==NULL) {<br> xlog(" cannot match request to a dialog \n");<br> # something wrong - might want to drop such requests<br> }</div><div><br></div><div> ... as a replacement to ...</div><div><br></div><div>if (loose_route()) {<br></div><div><br></div><div>And I added --<br></div><div><br></div><div> if (is_method("INVITE")) {<br><div><br></div> topology_hiding();<br> }</div><div><br></div><div> ... right after --<br></div><div><br></div><div> # account only INVITEs<br> if (is_method("INVITE")) {<br><div><br></div> setflag(ACC_DO); # do accounting</div><div> }<br><div><br></div><br></div><div>All this is from the stock config file, with only my listen IPs and a couple aliases added, and obviously the dialog module loaded as well to allow for topology hiding.<br></div><div><br></div><div>Thanks!<br></div><div><br></div><div>-BJ<br></div><div><br></div><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;" data-mce-style="color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Vlad Paiu" <vladpaiu@opensips.org><br><b>To: </b>users@lists.opensips.org<br><b>Sent: </b>Wednesday, February 5, 2014 6:19:41 AM<br><b>Subject: </b>Re: [OpenSIPS-Users] topology hiding<br><div><br></div>Hello,<br><div><br></div>The sequential processing part is a little bit wrong - you should have<br><div><br></div> if (loose_route() || match_dialog()) {<br> if ($DLG_status==NULL) {<br> xlog(" cannot match request to a dialog \n");<br> # something wrong - might want to drop such requests<br> }<br><div><br></div><br>Can you please also post a trace of the traffic flow when the Route <br>header gets that bogus \304 header ? Trying to replicate this on my side <br>and see what's wrong.<br><div><br></div>Best Regards,<br><div><br></div>Vlad Paiu<br>OpenSIPS Developer<br>http://www.opensips-solutions.com<br><div><br></div></div></div></div></div><br>_______________________________________________<br>Users mailing list<br>Users@lists.opensips.org<br>http://lists.opensips.org/cgi-bin/mailman/listinfo/users<br></div><div><br></div></div></body></html>