[SR-Users] Kamailio-5.3.3. NAT and RTP not working
Pavithra Mohanraja
pavimohan3004 at gmail.com
Thu Jun 25 10:34:45 CEST 2020
Hi Supreeth,
This is my DNS file
$ORIGIN sip.example.com.
$TTL 1W
@ 1D IN SOA localhost. root.localhost. (
1 ; serial
3H ; refresh
15M ; retry
1W ; expiry
1D ) ; minimum
1D IN NS ns
ns 1D IN A 10.45.5.95
pcscf 1D IN A 10.45.5.95
_sip._udp.pcscf 1D SRV 0 0 5070 pcscf
_sip._tcp.pcscf 1D SRV 0 0 5070 pcscf
icscf 1D IN A 10.45.5.95
_sip._udp 1D SRV 0 0 4060 icscf
_sip._tcp 1D SRV 0 0 4060 icscf
scscf 1D IN A 10.45.5.95
_sip._udp.scscf 1D SRV 0 0 6060 scscf
_sip._tcp.scscf 1D SRV 0 0 6060 scscf
hss 1D IN A 10.45.5.95
And pcscf config file is taken from ur git source
https://github.com/herlesupreeth/Kamailio_IMS_Config
changed only IP and domain name
# IP-Adress for incoming SIP-Traffic, in the following format:
# SIP / UDP
listen=udp:10.45.5.95:5070
# Uncomment the below line only when UE is behind double NAT (e.g. VoIP
calling over WiFi/ CN behind a NAT)
#listen=udp:10.4.128.21:5060 advertise 172.24.15.30:5060
# SIP / TCP
listen=tcp:10.45.5.95:5070
# Uncomment the below line only when UE is behind double NAT (e.g. VoIP
calling over WiFi/ CN behind a NAT)
#listen=tcp:10.4.128.21:5060 advertise 172.24.15.30:5060
# SIP / TCP/TLS
#listen=tls:11.22.33.44:5061
# IPSEC / UDP
#!define IPSEC_LISTEN_ADDR "10.45.5.95"
#!define IPSEC_CLIENT_PORT 5100
#!define IPSEC_SERVER_PORT 6100
# IP used in Rx_AAR_Register - IP of this P-CSCF, to be used in the flow
for the AF-signaling
#!define RX_AF_SIGNALING_IP "10.4.128.21"
# Uncomment the below line only when UE is behind double NAT (e.g. VoIP
calling over WiFi/ CN behind a NAT)
##!define RX_AF_SIGNALING_IP "172.24.15.30"
alias=pcscf.sip.example.com
#!define MY_WS_PORT 80
#!define MY_WSS_PORT 443
#!define PCSCF_URL "sip:pcscf.sip.example.com:5070"
#!define TCP_PROCESSES 8
I am not using pcrf .. rest of the things are same.
OPTIONS request are looping and sometimes registration is getting stopped
with 504 server timeout ..
Unable to find the root-cause.
Kindly do the needful.
On Thu, Jun 25, 2020 at 12:29 PM supreeth herle <herlesupreeth at gmail.com>
wrote:
> can you please paste here your DNS zone file and pcscf configuration
> files? It looks like DNS is not setup properly as sip:example.com is not
> being resolved to point to ICSCF.
>
> Best Regards,
> Supreeth
>
> On Thu, 25 Jun 2020 at 07:20, Pavithra Mohanraja <pavimohan3004 at gmail.com>
> wrote:
>
>> Hi Supreeth,
>>
>> I have followed your guide to build kamailio IMS
>>
>> https://open5gs.org/open5gs/docs/tutorial/02-VoLTE-setup/
>>
>> services are running fine .
>> when i try to make a call . registration fails with 478 unresolvable
>> destination
>>
>> 93(25632) INFO: rr [rr_mod.c:515]: pv_get_route_uri_f(): No route header
>> present.
>> 93(25632) NOTICE: <script>: PCSCF REGISTER:
>> Destination URI: <null>
>> Request URI: sip:sip.example.com;transport=TCP
>> 93(25632) INFO: rr [rr_mod.c:515]: pv_get_route_uri_f(): No route header
>> present.
>> 93(25632) NOTICE: <script>: Source IP and Port: (10.45.5.37:32945)
>> Route-URI:
>> 93(25632) NOTICE: <script>: Received IP and Port: (10.45.5.95:5060)
>> 93(25632) NOTICE: <script>: Contact header: <sip:bob at 10.45.5.37:36858
>> ;rinstance=9cc3de25b0bbb76f;transport=tcp>
>> 93(25632) INFO: ims_registrar_pcscf [sec_agree.c:264]:
>> cscf_get_security(): No security parameters found
>> 93(25632) INFO: ims_registrar_pcscf [sec_agree.c:296]:
>> cscf_get_security_verify(): No security-verify parameters found
>>
>>
>>
>>
>> *93(25632) CRITICAL: <core> [core/dns_cache.c:3157]:
>> dns_srv_sip_resolve(): unknown proto 093(25632) ERROR: tm [ut.h:284]:
>> uri2dst2(): failed to resolve "sip.example.com <http://sip.example.com>"
>> :bug - critical error (-13)93(25632) ERROR: tm [t_fwd.c:1728]:
>> t_forward_nonack(): failure to add branches93(25632) ERROR: sl
>> [sl_funcs.c:392]: sl_reply_error(): stateless error reply used:
>> Unresolvable destination (478/SL)93(25632) ERROR: <script>: REGISTER
>> (sip:bob at sip.example.com <sip%3Abob at sip.example.com>;transport=TCP
>> (10.45.5.37:32945 <http://10.45.5.37:32945>) to sip:bob at sip.example.com
>> <sip%3Abob at sip.example.com>;transport=TCP, QaTgoJXt7UGPJl9-jd0pxQ..)*
>>
>>
>>
>> what might be the issue . I have configured dns server also.
>>
>> kindly help .
>>
>>
>> Thanks,
>> Pavithra
>>
>> On Wed, Jun 24, 2020 at 6:23 PM Pavithra Mohanraja <
>> pavimohan3004 at gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I am not sure if this issue comes in 5.3.4 version .
>>>
>>> The below error i am facing in pcscf .
>>> 0(4152) ERROR: <script>: event_route[htable:mod-init] {
>>> 1(4153) ERROR: db_mysql [km_dbase.c:122]: db_mysql_submit_query():
>>> driver error on query: Unknown column 'aor' in 'field list' (1054)
>>> 1(4153) ERROR: <core> [db_query.c:141]: db_do_query_internal(): error
>>> while submitting query
>>> 1(4153) ERROR: ims_usrloc_pcscf [udomain.c:992]: preload_udomain():
>>> db_query (1) failed
>>> 1(4153) ERROR: ims_usrloc_pcscf [ims_usrloc_pcscf_mod.c:238]:
>>> child_init(): child(1): failed to preload domain 'location'
>>> 1(4153) ERROR: <core> [core/sr_module.c:781]: init_mod_child(): error
>>> while initializing module ims_usrloc_pcscf
>>> (/usr/lib/x86_64-linux-gnu/kamailio/modules/ims_usrloc_pcscf.so) (idx: 1
>>> rank: 1 desc: [udp receiver child=0 sock=172.17.0.3:4060])
>>> 1(4153) ERROR: <core> [core/pt.c:336]: fork_process(): init_child
>>> failed for process 1, pid 4153, "udp receiver child=0 sock=
>>> 172.17.0.3:4060"
>>> 1(4153) CRITICAL: <core> [main.c:1663]: main_loop(): Cannot fork
>>> 24(4199) INFO: ctl [io_listener.c:214]: io_listen_loop():
>>> io_listen_loop: using epoll_lt io watch method (config)
>>> 25(4215) WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB
>>> connection already open... continuing
>>> 28(4218) WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB
>>> connection already open... continuing
>>> 29(4219) WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB
>>> connection already open... continuing
>>> 30(4220) WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB
>>> connection already open... continuing
>>> 31(4221) WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB
>>> connection already open... continuing
>>> 32(4222) WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB
>>> connection already open... continuing
>>> 27(4217) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process():
>>> a new child 0/4217
>>> 33(4223) WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB
>>> connection already open... continuing
>>> 34(4224) WARNING: ims_usrloc_pcscf [usrloc_db.c:67]: connect_db(): DB
>>> connection already open... continuing
>>> root at 7f3840db6813:/etc/kamailio/pcscf# 0(4152) ALERT: <core>
>>> [main.c:762]: handle_sigs(): child process 4153 exited normally, status=255
>>> 0(4152) INFO: <core> [main.c:792]: handle_sigs(): terminating due to
>>> SIGCHLD
>>> 24(4199) INFO: <core> [main.c:847]: sig_usr(): signal 15 received
>>> 23(4198) INFO: <core> [main.c:847]: sig_usr(): signal 15 received
>>> 22(4197) INFO: <core> [main.c:847]: sig_usr(): signal 15 received
>>> 21(4196) INFO: <core> [main.c:847]: sig_usr(): signal 15 received
>>> 20(4195) INFO: <core> [main.c:847]: sig_usr(): signal 15 received
>>>
>>>
>>> Kindly help..
>>>
>>>
>>>
>>> Thanks,
>>> Pavithra
>>>
>>> On Wed, Jun 24, 2020 at 5:16 PM supreeth herle <herlesupreeth at gmail.com>
>>> wrote:
>>>
>>>> Please try to keep the mailing list in loop so that it helps others as
>>>> well facing this issue.
>>>>
>>>> I believe this was resolved in 5.3.3 branch not sure why you are facing
>>>> this issue. Anyways, make sure that modules loaded in kamailio.cfg of PCSCF
>>>> is in following order
>>>>
>>>> loadmodule "ims_dialog"
>>>> loadmodule "ims_usrloc_pcscf"
>>>> #!ifdef WITH_IPSEC
>>>> loadmodule "ims_ipsec_pcscf"
>>>> #!endif
>>>> loadmodule "ims_registrar_pcscf"
>>>>
>>>> Best Regards,
>>>> Supreeth
>>>>
>>>> On Wed, 24 Jun 2020 at 13:36, Pavithra Mohanraja <
>>>> pavimohan3004 at gmail.com> wrote:
>>>>
>>>>> Hi Supreeth,
>>>>>
>>>>> I am getting the below error
>>>>>
>>>>> ms_usrloc_pcscf
>>>>> [/usr/lib/x86_64-linux-gnu/kamailio/modules/ims_usrloc_pcscf.so]
>>>>> 0(455) DEBUG: ims_registrar_pcscf [ims_registrar_pcscf_mod.c:264]:
>>>>> mod_init(): Successfully bound to PCSCF Usrloc module
>>>>> 0(455) DEBUG: <core> [core/sr_module.c:632]:
>>>>> find_mod_export_record(): found export of <bind_ims_ipsec_pcscf> in module
>>>>> ims_ipsec_pcscf
>>>>> [/usr/lib/x86_64-linux-gnu/kamailio/modules/ims_ipsec_pcscf.so]
>>>>> 0(455) ERROR: ims_ipsec_pcscf [cmd.c:85]: bind_ipsec_pcscf():
>>>>> configuration error - trying to bind to ipsec pscscf module before being
>>>>> initialized
>>>>> 0(455) ERROR: <core> [core/sr_module.c:849]: init_mod(): Error while
>>>>> initializing module ims_registrar_pcscf
>>>>> (/usr/lib/x86_64-linux-gnu/kamailio/modules/ims_registrar_pcscf.so)
>>>>> ERROR: error while initializing modules
>>>>> 0(455) ERROR: ims_ipsec_pcscf [ims_ipsec_pcscf_mod.c:305]:
>>>>> mod_destroy(): Error destroying spi generator
>>>>> 0(455) ERROR: ims_ipsec_pcscf [ims_ipsec_pcscf_mod.c:309]:
>>>>> mod_destroy(): Error destroying port generator
>>>>> 0(455) DEBUG: tm [t_funcs.c:84]: tm_shutdown(): start
>>>>> 0(455) DEBUG: tm [t_funcs.c:87]: tm_shutdown(): emptying hash table
>>>>> 0(455) DEBUG: tm [t_funcs.c:89]: tm_shutdown(): removing semaphores
>>>>> 0(455) DEBUG: tm [t_funcs.c:91]: tm_shutdown(): destroying tmcb lists
>>>>>
>>>>>
>>>>> Kindly help
>>>>>
>>>>> On Wed, Jun 24, 2020 at 5:03 PM supreeth herle <
>>>>> herlesupreeth at gmail.com> wrote:
>>>>>
>>>>>> There is no other IPSec configuration needed apart from running
>>>>>> Kamailio P-CSCF and UE sending a SIP Register with Security-Client
>>>>>> information for IPSec creation. Kamailio IMS IPSec module creates IPSec
>>>>>> tunnels using Netlink library.
>>>>>>
>>>>>> Best Regards,
>>>>>> Supreeth
>>>>>>
>>>>>> On Wed, 24 Jun 2020 at 13:29, Pavithra Mohanraja <
>>>>>> pavimohan3004 at gmail.com> wrote:
>>>>>>
>>>>>>> Hi ,
>>>>>>>
>>>>>>> Could you please tell how to configure ipsec (general configuration
>>>>>>> not related to kamailio).
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Pavithra
>>>>>>>
>>>>>>> On Wed, Jun 24, 2020 at 2:12 PM supreeth herle <
>>>>>>> herlesupreeth at gmail.com> wrote:
>>>>>>>
>>>>>>>> reason=404 (Not Found - destination user not found on this S-CSCF)]
>>>>>>>>>
>>>>>>>>
>>>>>>>> Please check your IMPU for the IMS user in the IMS HSS (e.g. FHoSS
>>>>>>>> or any other HSS you are using to enter IMS user details). SCSCF is not
>>>>>>>> able to find a registered user with that IMPU (i am assuming that you are
>>>>>>>> getting this response while calling)
>>>>>>>>
>>>>>>>> Increase the debug level on S-CSCF and check out which IMPU is
>>>>>>>> being referred by SCSCF
>>>>>>>>
>>>>>>>> Best Regards,
>>>>>>>> Supreeth
>>>>>>>>
>>>>>>>> On Wed, 24 Jun 2020 at 10:26, Pavithra Mohanraja <
>>>>>>>> pavimohan3004 at gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> I am facing below error in kamailio-ims 5.3.4 version.
>>>>>>>>>
>>>>>>>>> reason=404 (Not Found - destination user not found on this S-CSCF)]
>>>>>>>>>
>>>>>>>>> could you please help me how should i proceed with and where the
>>>>>>>>> registration details will be stored in kamailio ims.
>>>>>>>>>
>>>>>>>>> It fails at this line in kamailio.cfg file in scscf .
>>>>>>>>>
>>>>>>>>> route[FINAL_TERM] {
>>>>>>>>> if (lookup("location")) {
>>>>>>>>> if (uri==myself) {
>>>>>>>>> if (!t_newtran()) {
>>>>>>>>> sl_reply_error();
>>>>>>>>> exit;
>>>>>>>>> }
>>>>>>>>> xlog("Destination Not Found ----\n");
>>>>>>>>> t_reply("404","Not Found - destination
>>>>>>>>> user not found on this S-CSCF");
>>>>>>>>> exit;
>>>>>>>>> }
>>>>>>>>>
>>>>>>>>> here lookup(location) means what it means. Could you please help me
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Pavithra
>>>>>>>>>
>>>>>>>>> On Thu, May 14, 2020 at 9:59 PM supreeth herle <
>>>>>>>>> herlesupreeth at gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hello Pavithra,
>>>>>>>>>>
>>>>>>>>>> I have written a guide for how to integrate an IMS using Kamailio
>>>>>>>>>> with open5gs EPC, here is the link
>>>>>>>>>> https://open5gs.org/open5gs/docs/tutorial/02-VoLTE-setup/. You
>>>>>>>>>> can find steps to setup rtpengine in that guide.
>>>>>>>>>>
>>>>>>>>>> Regarding requirement of rtpengine, its mandatory if you want to
>>>>>>>>>> use the scripts in that example folder without modification. Also, read the
>>>>>>>>>> READE of sipwise/rtpengine github repo, its very informative (in a gist
>>>>>>>>>> rtpengine offer much more feature than rtpproxy)
>>>>>>>>>>
>>>>>>>>>> why can't we have sip client to sip client rtps flowing like how
>>>>>>>>>>> it is happening without NAT.
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> For this, i would definitely suggest to read about SIP working.
>>>>>>>>>> This is a perfect link
>>>>>>>>>> https://github.com/onmyway133/blog/issues/284 which offers
>>>>>>>>>> extensive material (short and very interesting to read with examples)
>>>>>>>>>> related to SIP.
>>>>>>>>>>
>>>>>>>>>> Best Regards,
>>>>>>>>>> Supreeth
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Thu, 14 May 2020 at 17:51, Pavithra Mohanraja <
>>>>>>>>>> pavimohan3004 at gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> 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
>>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> 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/20200625/5bb7fcb1/attachment.html>
More information about the sr-users
mailing list