<div dir="ltr"><div><div>Shedding some more light on the situation, here are some further facts I could figure out:<br><br>1) I did the same test without the proxy in between (UAC <--> UAS) purely in SIPp, everything was fine, no dead call error<br>
<br></div>2) With the Kamailio proxy in between, I can see that there is a problem in call termination. The client is not receiving any "200 OK" for the "BYE"s it is sending. <br><br></div>Is there anything wrong in my routing logic that is preventing these ACKs?<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jun 19, 2014 at 4:09 PM, AliReza Khoshgoftar Monfared <span dir="ltr"><<a href="mailto:khoshgoftar@gmail.com" target="_blank">khoshgoftar@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Thanks very much Daniel,<br><br></div>This is solving a part of my issue for now.<br>Here is the routing section of my configuration file (it may be good to share it once complete as a minimally working proxy):<br>
<br><br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">route{<br> if (!mf_process_maxfwd_header("10")) {<br> sl_reply("483","Too Many Hops");<br>
break;<br> }<br> if (msg:len >= 4096 ) {<br> sl_reply("513", "Message too big");<br></blockquote><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
<div> } <br></div></blockquote><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><div> if (!method=="REGISTER") record_route(); <br>
</div></blockquote><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><div> if (!loose_route()) {<br> $du = "sip:<a href="http://10.236.214.86:5060" target="_blank">10.236.214.86:5060</a>";<br>
#setdsturi("sip:<a href="http://10.236.214.86:5060" target="_blank">10.236.214.86:5060</a>"); #second way to do it<br> if (!t_relay()) {<br> sl_reply_error();<br>
}<br>
</div></blockquote><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><div> }<br>} <br></div></blockquote><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
<div> </div></blockquote><div><br></div><div>I am trying to set up a kamailio proxy on an EC2 VM using this configurations and have been running a UAC and a UAS using SIPp on two other machines (UAC <--> Kamailio Proxy <--> UAS):<br>
<br>UAC<br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">sipp -sn uac -nr -r 1 -rp 1000 -d 0 -l 1 -p 5060 -trace_msg -i SELF_IP(UAC) -rsa PROXY_IP:5060 UAS_IP:5060<br>
</blockquote><div> </div>UAS:<br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">sipp -sn uas -d 0 -p 5060 -i SELF_IP(UAS) -rsa PRXY_IP:5060 -trace_msg</blockquote>
<div><br></div><div>It looks that messages go through, and are received by the server, but what I get back at the UAC (client) is a "dead call" error:<br><br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
Last Error: Dead call <a href="mailto:1-1734@10.140.34.188" target="_blank">1-1734@10.140.34.188</a> (aborted at index 8), receive...<br></blockquote><br></div><div>Is there a specific meaning to this "dead call" error? Is there anything that my proxy is missing in its routing or does it have to do with the UAC/UAS configs?<br>
<br><br></div><div>Thanks<span class="HOEnZb"><font color="#888888"><br></font></span></div><span class="HOEnZb"><font color="#888888"><div>Alireza<br></div></font></span></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra">
<br><br><div class="gmail_quote">On Tue, Jun 17, 2014 at 5:11 AM, Daniel-Constantin Mierla <span dir="ltr"><<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
listen is to specify local ip address or network interface on which
kamailio should listen for sip traffic.<br>
<br>
To send to an ip address there are couple of variants, in config
file:<br>
<br>
$ru = "sip:" + $rU + "@__NEXT_PROXY_IP__";<br>
t_relay();<br>
exit;<br>
<br>
Or, if you don't want to change the r-uri, then use:<br>
<br>
$du = <a>"sip:__NEXT_PROXY_IP__"</a>;<br>
t_relay();<br>
exit;<br>
<br>
Of course, you have to replace the __NEXT_PROXY_IP__ with the
appropriate value.<br>
<br>
More dynamic option would be using dispatcher module.<br>
<br>
Cheers,<br>
Daniel<div><div><br>
<br>
<div>On 15/06/14 15:28, AliReza Khoshgoftar
Monfared wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div>
<div dir="ltr">
<div>Dear Kamailio users,</div>
<div><br>
</div>
<div>I am trying to set up a simple scenario as follows:</div>
<div><br>
</div>
<div>UAC --> Proxy_1 --> Proxy_2 --> Proxy_3 --> UAC</div>
<div><br>
</div>
<div>I am new to Kamailio and had the following basic questions
that came to my mind after reading the documentation an the
default kamilio.cfg config script:</div>
<div><br>
</div>
<div>1) Is there any good example of the above scenario in which
the UAC and UAS (caller and callee) are modeled using SIPp and
proxies are simple kamailio instances run on different
machines that simply forward the SIP packets?</div>
<div><br>
</div>
<div>2) In specific, I want the proxies to simply forward the
messages to their downstream (I do not care about registration
or other operations and look for a minimally working simple
SIP scenario). Is there any example of such configuration?</div>
<div><br>
</div>
<div>3) Let's imagine Proxy_2 in the above example, in the
default config, it looks like that with modifying line 164,
"listen=udp:<a href="http://10.0.0.10:5060" target="_blank">10.0.0.10:5060</a>" I can
specify the address of its upstream, Proxy_1, but how and
where shall I set the specifications of the downstream,
Proxy_3?</div>
<div><br>
</div>
<div>I suspect it is somewhere in the Routing Logic block (line
449) but not sure how it is exactly done. I see a
"route(SIPOUT)" call for example but I am not sure how and
where the value of SIPOUT is modified. Is it a representation
of the downstream servers in the config file?</div>
<div><br>
</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Alireza </div>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><span><font color="#888888">
</font></span></pre><span><font color="#888888">
</font></span></blockquote><span><font color="#888888">
<br>
<pre cols="72">--
Daniel-Constantin Mierla - <a href="http://www.asipto.com" target="_blank">http://www.asipto.com</a>
<a href="http://twitter.com/#!/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a href="http://www.linkedin.com/in/miconda" target="_blank">http://www.linkedin.com/in/miconda</a></pre>
</font></span></div>
<br>_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br></div>