<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Alex,<div>Thanks. It's good to know that it should work.</div><div><br></div><div><br></div><div>Daniel,</div><div>It's a 2811 running IOS 12.4(25g).<br><div apple-content-edited="true"><br class="Apple-interchange-newline">
</div>
<blockquote type="cite" dir="auto"><blockquote type="cite">[a] ===> [kamailio] ===> [cisco] ===> [b]<br></blockquote></blockquote><div>This is exactly what I need. I'm trying to modify the request at [kamailio] so that [cisco] forwards to [b].</div><div><br></div><div>Possible complication is that [cisco] is also configured as a voice gateway with a SIP trunk to an external provider and a Call manager on the inside. However, this is independent SIP traffic that [cisco] appears to try to route according to voice rules.</div><div><br></div><div>I can get the call to proceed by adding a dial-peer to [cisco] config, but if I have understood loose-routing, that shouldn't be necessary.</div><div><br></div><div>I have tried several combinations of header and r-URI modifications to test [cisco]'s behaviour, including <i>Route:[cisco];lr </i>but it still seems to respond to the r-uri in the way I initially described.</div><div><br></div><div>All the best,</div><div>Dave </div><div><br></div><br><div><div>On 14 Aug 2013, at 5:09 pm, <a href="mailto:sr-users-request@lists.sip-router.org">sr-users-request@lists.sip-router.org</a> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><br><br>Message: 3<br>Date: Wed, 14 Aug 2013 13:06:19 +0400<br>From: Alex Balashov <<a href="mailto:abalashov@evaristesys.com">abalashov@evaristesys.com</a>><br>To: <a href="mailto:miconda@gmail.com">miconda@gmail.com</a>,<span class="Apple-tab-span" style="white-space:pre"> </span>"Kamailio (SER) - Users Mailing List"<br><span class="Apple-tab-span" style="white-space:pre"> </span><<a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a>><br>Subject: Re: [SR-Users] Loose Routing with Cisco router<br>Message-ID: <<a href="mailto:65a98f42-c370-49fe-91c4-d018b3d61249@email.android.com">65a98f42-c370-49fe-91c4-d018b3d61249@email.android.com</a>><br>Content-Type: text/plain; charset=UTF-8<br><br>I use Kamailio extensively with Cisco AS5xxx series gateways and they have never had a problem dealing with Kamailio's RRs and lr values. <br><br><br>Daniel-Constantin Mierla <<a href="mailto:miconda@gmail.com">miconda@gmail.com</a>> wrote:<br><blockquote type="cite">Hello,<br><br>what model the cisco router is?<br><br>From what I understand, you want to go from:<br><br>[a] ===> [kamailio] ===> [b]<br><br>to:<br><br>[a] ===> [kamailio] ===> [cisco] ===> [b]<br><br>The usual will be that kamailio sets the r-uri to [b] and dsturi <br>(outbound proxy) to [cisco] and then relay. The cisco should have some <br>config options just to forward the traffic based on r-uri, however I <br>never had to deal cisco configs. Maybe you add a Route header with <br>[cisco];lr, then it should match itself in the route header and send to<br><br>r-uri.<br><br>On the other hand, when I had to interoperate with cisco<br>gateways/b2bua, <br>they had no problem understanding loose routing added by kamailio.<br><br>Cheers,<br>Daniel<br><br>On 8/13/13 10:05 AM, David Wilson wrote:<br><blockquote type="cite">Hello All,<br><br>I'm running Kamailio 4.0.2 on Ubuntu 12.04 (precise).<br><br>I have SIP messaging flowing nicely, with UACs registering via<br></blockquote>Kamailio (as a proxy) to a Registrar.<br><blockquote type="cite"><br>Now having problems trying to route messages via a Cisco router<br></blockquote>(12.4(25g)) using loose routing. The plan is to allow the router to<br>see the SIP messaging but forward it to the original location.<br><blockquote type="cite"><br>RFC 3261 seems to cover this case in Section 16.6 part 6: "A proxy<br></blockquote>MAY have a local policy that mandates that a request visit a specific<br>set of proxies before being delivered to the destination."<br><blockquote type="cite"><br>Cisco documentation (SIP Configuration Guide, Cisco IOS Release 12.4)<br></blockquote>states that it implements RFC 3261, including Loose-routing. However,<br>from my observation the router doesn't like a request-URI with anything<br>other than its own IP address (it returns 400 Bad Request - 'Invalid IP<br>address'), but with any attempt to 'decorate' the URI with lr and/or<br>maddr= parameters it returns 400 Bad Request - 'Malformed/Missing' URL.<br>One of these messages is returned regardless of anything I've tried<br>with Via, Record-Route or Route headers.<br><blockquote type="cite"><br>Desired behaviour is for the router to remain in the route-set. A<br></blockquote>different configuration has shown me that this will achieve the<br>required outcome, the tricky part now is just getting that first<br>request to route. I know several ways to make Kamailio send to the<br>router, but the router is not behaving as I expect when I preload a<br>route set (with Route: headers).<br><blockquote type="cite"><br>Recognising that this is probably more of a Cisco problem than<br></blockquote>Kamailio, can anyone confirm whether a Cisco router implements<br>loose-routing when receiving messages, or only when sending?<br><blockquote type="cite"><br>Regards,<br>Dave.<br><br><br>_______________________________________________<br>SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing<br></blockquote>list<br><blockquote type="cite"><a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users<br></blockquote></blockquote><br>--<br>Sent from my mobile, and thus lacking in the refinement one might expect from a fully fledged keyboard. <br><br>Alex Balashov - Principal<br>Evariste Systems LLC<br>235 E Ponce de Leon Ave<br>Suite 106<br>Decatur, GA 30030<br>United States<br>Tel: +1-678-954-0670<br>Web: <a href="http://www.evaristesys.com/">http://www.evaristesys.com/</a>, <a href="http://www.alexbalashov.com">http://www.alexbalashov.com</a><br><br><br><br></blockquote></div><br></div></body></html>