<div dir="ltr">I don't access the server. I only have access to the proxy. Server works fine on the operators' broadband network. Have setup the proxy to make it work on other ISP's network as well. So the proxy receives the traffic on a unsual port which is not blocked and forwards it to 5060 port on the server internally.</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature">Rizwan Khan<br><br><br></div></div>
<br><div class="gmail_quote">On Thu, Dec 4, 2014 at 3:55 PM, 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">
Look at the sip traffic flowing though server (e.g., with ngrep on
port 5060) and see where the packets are routed.<br>
<br>
Cheers,<br>
Daniel<div><div class="h5"><br>
<br>
<div>On 01/12/14 11:30, Rizwan Khan wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">I am not sure if its the issue on my client end as
CSIPSImple is not sendin the PRACK that is expected by the
server or the rtp ports are not opened.
<div><br>
</div>
<div>I guess the ports are opened as I can hear two way voice. </div>
<div><br>
</div>
<div>But the following issues remain:</div>
<div><br>
</div>
<div>1. I cannot receive a call on the SIP number</div>
<div>2. I dont get an indication on the caller (thru CSIPSimple)
that a call has started as in it doesnt start the call timer</div>
<div>3. The call disconnects with an error after some time
..INternal Server Error.</div>
<div><br>
</div>
<div>Regards,<br>
<div class="gmail_extra"><br clear="all">
<div>
<div>Rizwan Khan<br>
<br>
<br>
</div>
</div>
<br>
<div class="gmail_quote">On Mon, Dec 1, 2014 at 11:00 AM,
Rizwan Khan <span dir="ltr"><<a href="mailto:rizkhan@gmail.com" target="_blank">rizkhan@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">Thanks for the help guys.
<div><br>
</div>
<div>I used a stateless proxy and was able to
register. Now I am able to make calls as well but
there is an issue.</div>
<div><br>
</div>
<div>I receive multiple ringing but not receiving 200
ok after that. I keep on receiving the ringing
messages. Although the call gets connected and I
hear two way voice as well.</div>
<div><br>
</div>
<div>Also I am call through the sip number, but its
not receiving any calls.</div>
<div><br>
</div>
<div>Any ideas?</div>
</div>
<div class="gmail_extra"><span><font color="#888888"><br clear="all">
<div>
<div>Rizwan Khan<br>
<br>
<br>
</div>
</div>
</font></span>
<div>
<div>
<br>
<div class="gmail_quote">On Thu, Nov 27, 2014 at
9:04 PM, Daniel Tryba <span dir="ltr"><<a href="mailto:daniel@pocos.nl" target="_blank">daniel@pocos.nl</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On Thursday 27
November 2014 08:29:51 Rizwan Khan wrote:<br>
> We want to use Kamailio as the
pass-thru proxy in front of the SBC just to<br>
> receive the request on a random port,
and then forward the request to the<br>
> SBC internally being on the same
private network.<br>
><br>
> What would be the best way to do it?<br>
<br>
</span>If it is the best is up to the experts,
but a way to do is to check wheter the<br>
source is the SBC or not. If the message is
from the SBC just handle it<br>
statefully (t_relay), if it isn't from the SBC
set the requested domain to the<br>
ipaddr of the SBC (10.1.2.3) and process
stateful. You could use the received<br>
port instead if external clients only
communicate on the special port<br>
($Rp!=6334)<br>
<br>
kamailio.cfg:<br>
<br>
#...<br>
port=5060<br>
port=6334<br>
#...<br>
<br>
request_route {<br>
#...<br>
<br>
if($si!="10.1.2.3")<br>
{<br>
$rd="10.1.2.3";<br>
}<br>
<br>
route(RELAY);<br>
<div>
<div>}<br>
<br>
<br>
<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>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<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>
</pre>
</blockquote>
<br>
</div></div><span class="HOEnZb"><font color="#888888"><pre cols="72">--
Daniel-Constantin Mierla
<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">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>