<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
<div class="moz-cite-prefix">On 8/3/12 1:43 AM, Varsha
Venkatraramani wrote:<br>
</div>
<blockquote
cite="mid:CABP4ryPryWOQ05RkVjoVzeGPE72p4Qr3wPgPF9o=ERiZaOC9EQ@mail.gmail.com"
type="cite"><br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_quote">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal">I have a question regarding the
below ACK response Kamilaio receives from a carrier.<span
style="color:#1f497d"> Can someone please help me
understand why the “</span><b>Route: <a
moz-do-not-send="true">sip:callmanager@192.168.160.43:5060</a>>
</b>sent from Kamailio is missing a “<” as shown in
the captures below? Our Internal proxy is treating
that as a malformed header and dropping the packet. <br>
</p>
<div>
<div class="h5">
<p class="MsoNormal"><b>ACK from CARRIER</b></p>
<p class="MsoNormal">
U 2012/08/01 18:32:52.219852 <a
moz-do-not-send="true"
href="http://4.55.18.227:5060" target="_blank">4.55.18.227:5060</a>
-> <a moz-do-not-send="true"
href="http://192.168.160.47:5060"
target="_blank">192.168.160.47:5060</a></p>
<p class="MsoNormal"><b>ACK <a
moz-do-not-send="true">sip:callmanager@192.168.160.43:5060</a>
SIP/2.0.</b></p>
<p class="MsoNormal">Via: SIP/2.0/UDP
4.55.18.227:5060;branch=z9hG4bK04B0eef33040e9b8e70.</p>
<p class="MsoNormal">
From: <a moz-do-not-send="true">sip:+14088442721@4.55.18.227:5060;tag=gK043001e3</a>.</p>
<p class="MsoNormal">To: <a moz-do-not-send="true">sip:+19728931740@192.168.160.47:5060;tag=b307370c678f3b44</a>.</p>
<p class="MsoNormal">Call-ID: <a
moz-do-not-send="true"
href="mailto:295226_50030734@4.55.18.227"
target="_blank">295226_50030734@4.55.18.227</a>.</p>
<p class="MsoNormal">CSeq: 18079 ACK.</p>
<p class="MsoNormal">Max-Forwards: 70.</p>
<p class="MsoNormal">Route: <<a
moz-do-not-send="true">sip:192.168.160.47:5060;lr=on</a>>.</p>
<p class="MsoNormal">
<b>Route: <<a moz-do-not-send="true">sip:2c6c6d1ab58c623912f6b8a6ee526982@192.168.160.44:5060</a>>.</b></p>
<p class="MsoNormal">Content-Length: 0.</p>
<p class="MsoNormal">.</p>
<p class="MsoNormal">
<b>ACK FORWARDED TO SIP PROXY</b></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">U 2012/08/01 18:32:52.220612 <a
moz-do-not-send="true"
href="http://192.168.160.47:5060"
target="_blank">192.168.160.47:5060</a> -> <a
moz-do-not-send="true"
href="http://192.168.160.44:5060"
target="_blank">192.168.160.44:5060</a></p>
<p class="MsoNormal"><b>ACK <a
moz-do-not-send="true">sip:2c6c6d1ab58c623912f6b8a6ee526982@192.168.160.44:5060</a>
SIP/2.0.</b></p>
<p class="MsoNormal">Via: SIP/2.0/UDP
192.168.160.47;branch=z9hG4bKcydzigwkX.</p>
<p class="MsoNormal">
Via: SIP/2.0/UDP
4.55.18.227:5060;branch=z9hG4bK04B0eef33040e9b8e70.</p>
<p class="MsoNormal">From: <a
moz-do-not-send="true">sip:+14088442721@4.55.18.227:5060;tag=gK043001e3</a>.</p>
<p class="MsoNormal">To: <a moz-do-not-send="true">sip:+19728931740@192.168.160.47:5060;tag=b307370c678f3b44</a>.</p>
<p class="MsoNormal">Call-ID: <a
moz-do-not-send="true"
href="mailto:295226_50030734@4.55.18.227"
target="_blank">295226_50030734@4.55.18.227</a>.</p>
<p class="MsoNormal">CSeq: 18079 ACK.</p>
<p class="MsoNormal">Max-Forwards: 69.</p>
<p class="MsoNormal">Content-Length: 0.</p>
<p class="MsoNormal"><b>Route: <a
moz-do-not-send="true">sip:callmanager@192.168.160.43:5060</a>>.</b></p>
<p class="MsoNormal">I have attached the config file
for you reference. Kamailio version is 3.2.3</p>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
the next proxy does strict routing, because the Route header has not
'lr' parameter. Based on SIP specs, Kamailio has to take that route
and set it as r-uri and the r-uri has to be added as last route, so
next proxy will be able to do forwarding based on strict routing
rules. Maybe there is an option in that device at 192.168.160.44 to
do loose routing, which is the recommended one in RFC3261 (strict
routing is from the old rfc of SIP).<br>
<br>
Regarding the missing '<' in the Route header sent out from
Kamailio, there was an issue in the code handling this specific
situation, should be fixed now by commit:<br>
<a class="moz-txt-link-freetext" href="http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=cbb62f8619b513605498d00abc5d4c8b2f5654d7">http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=cbb62f8619b513605498d00abc5d4c8b2f5654d7</a><br>
<br>
You have to apply that patch or use the latest git branch 3.2. Let
us know if works fine.<br>
<br>
Cheers,<br>
Daniel<br>
<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla - <a class="moz-txt-link-freetext" href="http://www.asipto.com">http://www.asipto.com</a>
<a class="moz-txt-link-freetext" href="http://twitter.com/#!/miconda">http://twitter.com/#!/miconda</a> - <a class="moz-txt-link-freetext" href="http://www.linkedin.com/in/miconda">http://www.linkedin.com/in/miconda</a>
Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - <a class="moz-txt-link-freetext" href="http://asipto.com/u/katu">http://asipto.com/u/katu</a>
Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - <a class="moz-txt-link-freetext" href="http://asipto.com/u/kpw">http://asipto.com/u/kpw</a></pre>
</body>
</html>