[SR-Users] Kamailio-5.3.3. NAT and RTP not working

Thu May 14 17:40:54 CEST 2020

Hi ,

I didn't configure rtpengine ..instead of that only I used rrpproxy..will
it not work?

If not please tell me how to configure rtpengine and also tell me if it is
really madatory .. why can't we have sip client to sip client rtps flowing
like how it is happening without NAT.

That's my doubt ..please clarify ..

Thanks.

On Thu, May 14, 2020, 8:57 PM supreeth herle <herlesupreeth at gmail.com>
wrote:

> HI,
>
> Hold on a moment,
>
>
>> 10.40.10.3 - pcscf in port 4060 (pcscf with NAT enabled in pcscf.cfg
>> (!#define WITH_NAT) and configured rtpproxy)
>> 10.40.10.12 - icscf in port 4070
>> 10.40.10.5 - scscf in port 4080
>> 10.40.10.30 - hss
>>
>
> So i assume you are using the examples provided in the ims folder of
> kamailio repo right? Isn't it using RTPEngine and not RTPProxy? Or have you
> modified the P-CSCF configuration to work with RTPProxy?
>
> Best regards,
> Supreeth
>
> On Thu, 14 May 2020 at 16:39, Pavithra Mohanraja <pavimohan3004 at gmail.com>
> wrote:
>
>> Hi ,
>> I have attached working rtp pcap file. But it is getting reverted back to
>> me .
>>
>> As you said , i have tried restarting rtpproxy several times. but it
>> didnt work .
>>
>>
>>
>> On Thu, May 14, 2020 at 7:11 PM supreeth herle <herlesupreeth at gmail.com>
>> wrote:
>>
>>> Thanks for the pcap. Sorry, to ask this but can you also send pcap of
>>> scenario where you see RTP packets?
>>>
>>> Also, did you restart the rtpproxy after altering the
>>> /etc/default/rtpproxy ?
>>>
>>> i.e.
>>>
>>> $ systemctl restart rtpproxy
>>>
>>> Best Regards,
>>> Supreeth
>>>
>>> On Thu, 14 May 2020 at 14:51, Pavithra Mohanraja <
>>> pavimohan3004 at gmail.com> wrote:
>>>
>>>> Hi Supreeth,
>>>> I have attached pcap files . kindly check and let me know.
>>>> filter of rtp packets and check.
>>>>
>>>> *filter : sip || rtp*
>>>>
>>>>
>>>> On Thu, May 14, 2020 at 5:15 PM supreeth herle <herlesupreeth at gmail.com>
>>>> wrote:
>>>>
>>>>> Hi Pavithra,
>>>>>
>>>>> Thanks for the clarification. Can you please attach a pcap of the call
>>>>> where you are not seeing the RTP packets? And, btw is the call getting
>>>>> dropped or something in that scenario?
>>>>>
>>>>> Regards,
>>>>> Supreeth
>>>>>
>>>>>
>>>>> On Thu, 14 May 2020 at 13:34, Pavithra Mohanraja <
>>>>> pavimohan3004 at gmail.com> wrote:
>>>>>
>>>>>> Hi Supreeth,
>>>>>>
>>>>>> I have kamailio ims installed in 4 vms inside openstack.
>>>>>>
>>>>>> 10.40.10.3 - pcscf in port 4060 (pcscf with NAT enabled in pcscf.cfg
>>>>>> (!#define WITH_NAT) and configured rtpproxy)
>>>>>> 10.40.10.12 - icscf in port 4070
>>>>>> 10.40.10.5 - scscf in port 4080
>>>>>> 10.40.10.30 - hss
>>>>>>
>>>>>> so all these vms are running in same subnet.
>>>>>> I have a floating ip associated to pcscf.
>>>>>> Now I have two zoiper clients outside openstack
>>>>>> zoiper1 - 10.0.2.15 (NAT Enabled Network adaptor)
>>>>>> zoiper2 - 10.0.2.15
>>>>>>
>>>>>> when i am making a call from zoiper1 to zoiper2, call is going
>>>>>> properly . SIP messages are coming properly in wireshark packets.
>>>>>> when i filter for RTP packets in wireshark,  it is not coming.
>>>>>>
>>>>>>
>>>>>> when i have the zoiper clients inside openstack itself ,i can able to
>>>>>> see RTP Packets in wireshark between two sip clients without any NAT
>>>>>> related configurations done.
>>>>>>
>>>>>> Kindly help me.
>>>>>> Thanks.
>>>>>>
>>>>>> On Thu, May 14, 2020 at 4:49 PM supreeth herle <
>>>>>> herlesupreeth at gmail.com> wrote:
>>>>>>
>>>>>>> Can you explain some more when you mean by "RTP alone is not
>>>>>>> coming."? And, how are you checking/verifying that?
>>>>>>>
>>>>>>> Regards,
>>>>>>> Supreeth
>>>>>>>
>>>>>>> On Thu, 14 May 2020 at 13:12, Pavithra Mohanraja <
>>>>>>> pavimohan3004 at gmail.com> wrote:
>>>>>>>
>>>>>>>> Hi ,
>>>>>>>>
>>>>>>>> Yes I have configured as you mentioned only . In my pcscf only i
>>>>>>>> have rtpproxy also configured.
>>>>>>>> Floating IP i have given in listen address also as
>>>>>>>> listen = 10.40.10.3:4060 advertise 10.45.4.22:4060
>>>>>>>>
>>>>>>>> 10.40.10.3 - private ip
>>>>>>>> 10.45.4.22 - floating ip
>>>>>>>> Still RTP alone is not coming.
>>>>>>>>
>>>>>>>> Is it the only way of configuring NAT ?
>>>>>>>>
>>>>>>>> Thanks.
>>>>>>>>
>>>>>>>> On Thu, May 14, 2020 at 4:37 PM supreeth herle <
>>>>>>>> herlesupreeth at gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hello Pavithra,
>>>>>>>>>
>>>>>>>>> Have you tried advertising the floating IP of the VM running
>>>>>>>>> RTPProxy as follows?
>>>>>>>>>
>>>>>>>>> Edit /etc/default/rtpproxy file as follows:
>>>>>>>>>
>>>>>>>>> # Additional options that are passed to the daemon.
>>>>>>>>> EXTRA_OPTS="-l 172.24.15.30 -d DBUG:LOG_LOCAL0"
>>>>>>>>>
>>>>>>>>> here, "-l <PUBLIC_IP>"
>>>>>>>>>
>>>>>>>>> Hope it helps.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Supreeth
>>>>>>>>>
>>>>>>>>> On Thu, 14 May 2020 at 13:01, Pavithra Mohanraja <
>>>>>>>>> pavimohan3004 at gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi ,
>>>>>>>>>>
>>>>>>>>>> Could anybody please give me the approach how to configure NAT in
>>>>>>>>>> kamailio IMS.
>>>>>>>>>>
>>>>>>>>>> I have installed kamailio IMS in openstack environment which has
>>>>>>>>>> private ips for all four vms (each component in one vm). pcscf has one
>>>>>>>>>> floating IP attached. I have enabled "WITH_NAT" and configured rtpproxy .
>>>>>>>>>>
>>>>>>>>>> when i make a call from outside of openstack using 2 zoiper
>>>>>>>>>> clients with outbound proxy keeping floating ip of pcscf, I am getting 200
>>>>>>>>>> ok with all SIP packets correctly flowing but there is no RTP Packet.
>>>>>>>>>>
>>>>>>>>>> When i try the same within openstack environment without using
>>>>>>>>>> public ip, I am getting RTP Packets.
>>>>>>>>>>
>>>>>>>>>> Kindly tell me the procedure of NAT Enablement or do i need to do
>>>>>>>>>> anything other than this.
>>>>>>>>>>
>>>>>>>>>> Kindly help because i am stuck with this for long time.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Thanks.
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Kamailio (SER) - Users Mailing List
>>>>>>>>>> sr-users at lists.kamailio.org
>>>>>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Kamailio (SER) - Users Mailing List
>>>>>>>>> sr-users at lists.kamailio.org
>>>>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Kamailio (SER) - Users Mailing List
>>>>>>>> sr-users at lists.kamailio.org
>>>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Kamailio (SER) - Users Mailing List
>>>>>>> sr-users at lists.kamailio.org
>>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>>>>>
>>>>>> _______________________________________________
>>>>>> Kamailio (SER) - Users Mailing List
>>>>>> sr-users at lists.kamailio.org
>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>>>>
>>>>> _______________________________________________
>>>>> Kamailio (SER) - Users Mailing List
>>>>> sr-users at lists.kamailio.org
>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>>>
>>>> _______________________________________________
>>>> Kamailio (SER) - Users Mailing List
>>>> sr-users at lists.kamailio.org
>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>>
>>> _______________________________________________
>>> Kamailio (SER) - Users Mailing List
>>> sr-users at lists.kamailio.org
>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>
>> _______________________________________________
>> Kamailio (SER) - Users Mailing List
>> sr-users at lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users at lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20200514/3fea53c0/attachment.html>