<div dir="ltr"><div>The best way to see what is happening is to capture some packets on the Kamailio system on which calls happen and see if any IP address or port number issues exist in body of SIP messages or not. You can simple use Wireshark to see what is going on.<br><br></div>Regards<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 12, 2016 at 4:58 PM, Marino Mileti <span dir="ltr"><<a href="mailto:marino.mileti@alice.it" target="_blank">marino.mileti@alice.it</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div link="blue" vlink="purple" lang="IT"><div><p class="MsoNormal">Hi guys,<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><span lang="EN-GB">i'm going in trouble with multinat scenario and Kamailio </span><span style="font-family:Wingdings" lang="EN-GB">J</span><span lang="EN-GB"><u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-GB">I've this scenario...<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-GB">Two kamailio boxes with the same configuration (KAM_A and KAM_B). Each box has a WIFI in AP_MODE with the same address (but different SSID obviously) 192.168.254.1. Finally there are 2 clients...CLIENT_1 connected to wifi with KAM_A, and CLIENT_2 connected using wifi with KAM_B. Each box has an instance of RTPEngine configured.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB">KAM_A & KAM_B are also connected using wired connection with other clients in order to allow that a calls to KAM_B (or KAM_A) generate a forking scenario and all clients connected starts to RINGS (wired & wireless client)<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-GB">The mobile client connected on KAM_A makes a call to KAM_B... the forking scenario starts and all clients on KAM_B starts to ring.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB">If any wired client pick up the call everything works fine. If a wireless client pick up the call...no media </span><span style="font-family:Wingdings" lang="EN-GB">L</span><span lang="EN-GB"><u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-GB">Is it possible? Should I've to instruct RTPENGINE in any particular mode?<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p><p class="MsoNormal"><i><span style="font-family:"Cambria","serif";color:#1f497d">Marino Maria Mileti</span></i><i><span style="font-size:12.0pt;font-family:"Cambria","serif";color:#1f497d"><u></u><u></u></span></i></p><p class="MsoNormal"><i><span style="font-size:9.0pt;font-family:"Cambria","serif";color:#1f497d"><a href="mailto:marino.mileti@alice.it" target="_blank"><span style="color:blue">marino.mileti@alice.it</span></a><u></u><u></u></span></i></p><p class="MsoNormal"><i><span style="font-size:9.0pt;font-family:"Cambria","serif";color:#1f497d"><u></u> <u></u></span></i></p><p class="MsoNormal"><i><span style="font-size:9.0pt;font-family:"Cambria","serif";color:#1f497d"><img src="cid:image001.jpg@01D20D00.9127EE40" alt="cid:006a01cb6b0e$67eecdae$_CDOSYS2.0" border="0" height="26" width="36"></span></i><i><span style="font-size:9.0pt;color:#1f497d" lang="EN-US">Reduce your energy consumption and keep polar bears on ice!</span></i><span style="font-size:7.5pt;font-family:"Tahoma","sans-serif";color:#339966" lang="EN-US"> </span><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:#1f497d" lang="EN-GB"><u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p></div>
<br><br>
<hr style="border:none;color:#909090;background-color:#b0b0b0;min-height:1px;width:99%">
<table style="border-collapse:collapse;border:none">
<tbody><tr>
<td style="border:none;padding:0px 15px 0px 8px">
<a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient" target="_blank">
<img src="http://static.avast.com/emails/avast-mail-stamp.png" alt="Avast logo" border="0">
</a>
</td>
<td>
<p style="color:#3d4d5a;font-family:"Calibri","Verdana","Arial","Helvetica";font-size:12pt">
Questa e-mail è stata controllata per individuare virus con Avast antivirus.
<br><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient" target="_blank">www.avast.com</a>
</p>
</td>
</tr>
</tbody></table>
<br>
</div><br>______________________________<wbr>_________________<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" rel="noreferrer" target="_blank">http://lists.sip-router.org/<wbr>cgi-bin/mailman/listinfo/sr-<wbr>users</a><br>
<br></blockquote></div><br></div>