<div dir="ltr"><div><div><div>Hi,<br><br></div>Looks like a NAT issue in your network infrastructure, try to capture the SIP signalling on your server by using this command : "ngrep -d any -qt -W byline port <server listening port>" and analyse if it is NATed or not.<br>
<br></div>Regards,<br></div>Nandini<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 1, 2014 at 4:44 PM, kamika <span dir="ltr"><<a href="mailto:kamil.nigmatullin@gmail.com" target="_blank">kamil.nigmatullin@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">When you work with opensips in most cases you cannot use it out of the box<br>
like Asterisk or Freeswitch. You have to learn at least how to record SIP<br>
traces, read and understand SIP flow, understand what opensips.cfg does.<br>
There is a few programs that can record traces - I am personally use tcpdump<br>
and read them in Wireshark using its powerfull voip tools. When you are<br>
able to discover what happend in trace, you can understand where the problem<br>
is hidden whether it nat of network issues.<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://opensips-open-sip-server.1449251.n2.nabble.com/Android-can-t-here-voice-over-the-LTE-tp7590112p7590489.html" target="_blank">http://opensips-open-sip-server.1449251.n2.nabble.com/Android-can-t-here-voice-over-the-LTE-tp7590112p7590489.html</a><br>
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.<br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br></div>