<div dir="ltr">Hello Carsten :)<div>Thanks for your reply</div><div style=""><br></div><div style="">Actually, we remove the alias from sip massages for a reason, which was a bug in the client generating wrong ip in the alias in BYE msgs in Video Calls only, and even before removing the alias part this problem existed.</div><div style=""><br></div><div style="">under this specific kind of networks, INVITE msg reaches the client, but the co-responding RINGING msg and msgs follows from the client not reaching the P-CSCF at all</div><div style="">for that reason we suspect of a NAT problem.</div><div style=""><br></div><div style="">other networks working Fine without the alias</div><div style=""><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Aug 28, 2018 at 2:47 PM Carsten Bock <<a href="mailto:carsten@ng-voice.com">carsten@ng-voice.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
it's seems not related to CGNAT, but more due to a misconfiguration on<br>
the Proxy-CSCF. It should evaluate the "alias" in the R-URI in order<br>
to send it to the proper address.<br>
<br>
Thanks,<br>
Carsten<br>
--<br>
<br>
Carsten Bock<br>
CEO (Geschäftsführer)<br>
<br>
ng-voice GmbH<br>
Millerntorplatz 1<br>
20359 Hamburg / Germany<br>
<br>
<a href="http://www.ng-voice.com" rel="noreferrer" target="_blank">http://www.ng-voice.com</a><br>
mailto:<a href="mailto:carsten@ng-voice.com" target="_blank">carsten@ng-voice.com</a><br>
<br>
Office +49 40 5247593-40<br>
Fax +49 40 5247593-99<br>
<br>
Sitz der Gesellschaft: Hamburg<br>
Registergericht: Amtsgericht Hamburg, HRB 120189<br>
Geschäftsführer: Carsten Bock<br>
Ust-ID: DE279344284<br>
<br>
Hier finden Sie unsere handelsrechtlichen Pflichtangaben:<br>
<a href="http://www.ng-voice.com/imprint/" rel="noreferrer" target="_blank">http://www.ng-voice.com/imprint/</a><br>
<br>
Am Di., 28. Aug. 2018 um 13:19 Uhr schrieb Amar Tinawi <<a href="mailto:amar.tinawi@gmail.com" target="_blank">amar.tinawi@gmail.com</a>>:<br>
><br>
> Hi Joel<br>
><br>
> the Via's and Record routes is due to IMS structure, but it doesn't affect the concept as i test it with a normal sip Proxy<br>
><br>
> Proxy IP : 94.252.181.93 : 5050<br>
> RTP Engine : 94.252.181.49<br>
> I-cscf : 10.192.129.134<br>
> s-cscf :10.192.129.134<br>
><br>
> Actually i'm using what Mr Carsten introduce for IMS<br>
><br>
> On Mon, Aug 27, 2018 at 8:33 PM Joel Serrano <<a href="mailto:joel@textplus.com" target="_blank">joel@textplus.com</a>> wrote:<br>
>><br>
>> Hi Amar,<br>
>><br>
>> I had a quick look and I see a lot of via/route headers, I will look<br>
>> properly later today, can you give me some details on what IP is what<br>
>> in those traces for when I check them later?<br>
>><br>
>> Also, are you using a kamailio config based on vanilla config<br>
>> (specially regarding NAT handling and Contact/SDP updates/rewrites)?<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> On Sun, Aug 26, 2018 at 11:39 PM, Amar Tinawi <<a href="mailto:amar.tinawi@gmail.com" target="_blank">amar.tinawi@gmail.com</a>> wrote:<br>
>> > it's Kamailio for signaling with RTPengine for media (also the RTP engine<br>
>> > has public IP)<br>
>> ><br>
>> > any call to reach the user behind the CGNAT will fail because of the 200 OK<br>
>> > msg not reaching the Proxy somehow (i checked, the massage is generated in<br>
>> > the client)<br>
>> > and any call initiated by the CGNAT client succeeded<br>
>> ><br>
>> > would you please check the attached<br>
>> > many thanks<br>
>> ><br>
>> > On Mon, Aug 27, 2018 at 6:00 AM Joel Serrano <<a href="mailto:joel@textplus.com" target="_blank">joel@textplus.com</a>> wrote:<br>
>> >><br>
>> >> It would definitely be useful to see sip traces of the different scenarios<br>
>> >> to try and find what the problem is.<br>
>> >><br>
>> >> Can you give some details of what your setup looks like? Is kamailio<br>
>> >> acting as a signaling proxy only or is it also handling RTP with<br>
>> >> rtpengine/rtpproxy?<br>
>> >><br>
>> >> On Sun, Aug 26, 2018 at 13:30 Amar Tinawi <<a href="mailto:amar.tinawi@gmail.com" target="_blank">amar.tinawi@gmail.com</a>> wrote:<br>
>> >>><br>
>> >>> Thanks Joel For reply<br>
>> >>><br>
>> >>> when any user (Not Nated or behind Normal NAT) is trying to reach a<br>
>> >>> client behind CGNAT, the INVITE delivered and the client is start to<br>
>> >>> ringing, but when answering, the answer is not delivered to the proxy, so<br>
>> >>> not delivered to the calling client result to the call started in the<br>
>> >>> CGNATED client and still in establishing in the calling one.<br>
>> >>><br>
>> >>> The call is established successfully when the CGNATED send the INVITE to<br>
>> >>> Not Nated client and two way audio.<br>
>> >>><br>
>> >>> CGNATED to CGNATED not working as well .<br>
>> >>><br>
>> >>><br>
>> >>><br>
>> >>> On Sun, Aug 26, 2018 at 7:57 PM Joel Serrano <<a href="mailto:joel@textplus.com" target="_blank">joel@textplus.com</a>> wrote:<br>
>> >>>><br>
>> >>>> Also, if the client is not behind CGNAT do you get the Ringing from<br>
>> >>>> called party?<br>
>> >>>><br>
>> >>>> Is called party the same in both cases?<br>
>> >>>><br>
>> >>>><br>
>> >>>><br>
>> >>>> On Sun, Aug 26, 2018 at 09:54 Joel Serrano <<a href="mailto:joel@textplus.com" target="_blank">joel@textplus.com</a>> wrote:<br>
>> >>>>><br>
>> >>>>> Can you send the INVITE that proxy sends to called party?<br>
>> >>>>><br>
>> >>>>> On Sun, Aug 26, 2018 at 02:05 Amar Tinawi <<a href="mailto:amar.tinawi@gmail.com" target="_blank">amar.tinawi@gmail.com</a>><br>
>> >>>>> wrote:<br>
>> >>>>>><br>
>> >>>>>> Hello<br>
>> >>>>>> Although my question it's not related to Kamailio directly, but i<br>
>> >>>>>> think someone could help in this strange behavior<br>
>> >>>>>><br>
>> >>>>>> in our tests, we have some clients under private networks, where the<br>
>> >>>>>> provider of those networks implements CGNAT (NAT444) for it's customers to<br>
>> >>>>>> reach internet<br>
>> >>>>>> (Client Private IP) --->(Home router: Private to Private NAT)--->(FW<br>
>> >>>>>> with CGNAT)---------------------------->(Kamailio Proxy Public IP)<br>
>> >>>>>><br>
>> >>>>>><br>
>> >>>>>> Registration is performing fine, but making calls from this client had<br>
>> >>>>>> strange problem as follow:<br>
>> >>>>>><br>
>> >>>>>> Client -------------INVITE--------------> Proxy<br>
>> >>>>>> Proxy -------------Trying---------------->Client<br>
>> >>>>>> Proxy--------------INVITE---------> Called Party<br>
>> >>>>>><br>
>> >>>>>> The called party should send Ringing msg, but the massage get lost<br>
>> >>>>>> somewhere and didn't reach to the Proxy. Although all the IP's in sip<br>
>> >>>>>> massages are public<br>
>> >>>>>> i tried with STUN/TURN and NAThelper module solutions, but didn't help<br>
>> >>>>>><br>
>> >>>>>> is there any way to slove CGNAT with SIP in Kamailio?<br>
>> >>>>>><br>
>> >>>>>><br>
>> >>>>>> Thanks in Advance<br>
>> >>>>>><br>
>> >>>>>><br>
>> >>>>>><br>
>> >>>>>><br>
>> >>>>>><br>
>> >>>>>><br>
>> >>>>>><br>
>> >>>>>> _______________________________________________<br>
>> >>>>>> Kamailio (SER) - Users Mailing List<br>
>> >>>>>> <a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
>> >>>>>> <a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
>> >>>><br>
>> >>>> _______________________________________________<br>
>> >>>> Kamailio (SER) - Users Mailing List<br>
>> >>>> <a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
>> >>>> <a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
>> >>><br>
>> >>> _______________________________________________<br>
>> >>> Kamailio (SER) - Users Mailing List<br>
>> >>> <a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
>> >>> <a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
>> >><br>
>> >> _______________________________________________<br>
>> >> Kamailio (SER) - Users Mailing List<br>
>> >> <a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
>> >> <a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > Kamailio (SER) - Users Mailing List<br>
>> > <a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
>> > <a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
>> ><br>
>><br>
>> _______________________________________________<br>
>> Kamailio (SER) - Users Mailing List<br>
>> <a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
>> <a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
><br>
> _______________________________________________<br>
> Kamailio (SER) - Users Mailing List<br>
> <a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
> <a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br>
_______________________________________________<br>
Kamailio (SER) - Users Mailing List<br>
<a href="mailto:sr-users@lists.kamailio.org" target="_blank">sr-users@lists.kamailio.org</a><br>
<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
</blockquote></div>