Hey;<br><br>I've been upgrading all of our older OpenSER 1.3 proxies to OpenSIPS 1.6.0 (we have several dozen) and I found a problem child in our inbound Verizon proxy. After completely destroying the configs, grasping at straws and all sorts of crazy theories I discovered that apparently OpenSIPS doesn't like the To: that Verizon uses. OpenSER 1.3 has no issue with it, OpenSIPs 1.6 does.<br>
<br>Even when at its most basic config (has the usual module setup, sanity checks, options_reply, loose_route, etc):<br><br>if (method == "INVITE") {<br> rewritehostport("destinationserver:5060');<br>
}<br><br>t_relay();<br><br>I discovered that the call would loop through the config, over and over, until it reached the Maximum Hops counter requirement and the call was dumped with a 483. When I xlog()'d I could see that it was correctly falling into the if { } section, the $ru was being rewritten... and then, bam, it reappeared at the top of the route { } block and went through it again.<br>
<br>I've discovered that if I do this:<br>if (method == "INVITE") {<br>
$ru = "sip:" + $oU + "@proxyserver:5060";<br> rewritehostport("destinationserver:5060');<br>
}<br>
<br>Everything is copacetic. The original To: looks like this:<br>INVITE sip:+12125551212@verizon.inbound.chi1.ourcompany.com:5060;user=phone;transport=UDP;maddr=123.123.123.123 SIP/2.0<br><br>With the IP after 'maddr' replaced with our proxy's IP. Verizon uses DNSSRV, so <a href="http://verizon.inbound.chi1.ourcompany.com">verizon.inbound.chi1.ourcompany.com</a> points to three IPs, each a SER proxy.<br>
<br>Well, anyway, now I have a workaround it's not such a big deal, but I wanted to push it out there and have it in the archives in case anyone else had some insane looping issue and couldn't work out what it was.<br>
<br>(Hey, Bogdan, any luck in getting a test case set up for the non-functioning db_virtual?)<br><br>Thanks;<br><br> - Jock<br>