sr-users January 2016

sr-users@lists.kamailio.org

86 participants
112 discussions

Re: [SR-Users] P-CSCF
by Aaron Hamstra 30 Jan '16

30 Jan '16

Fred, I think you would need to use rtpengine instead of rtpproxy. https://github.com/sipwise/rtpengine -Aaron From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Fred Schulz Sent: Thursday, January 28, 2016 1:24 PM To: sr-users(a)lists.sip-router.org Subject: [SR-Users] P-CSCF Hi all, we’re just playing around with an IMS setup bases on kamailio. Therefore the kamailio is used as P-,I- and S-CSCF. We where able to register two clients through all components. As we wan to start a call session, the P-CSCF answers with „403 - Forbidden. You must register with an S-CSCF“… I found this snippet in kamailio.cfg: if (!pcscf_is_registered("location")) { send_reply("403","Forbidden - You must register first with a S-CSCF“); break; } Can one tell me what exactly the kamailio is checking there? As I figured out it is looking in database location table. The table contains the registered users registered towards the IMS. Another „problem“ we faced with is the rtpproxy. As the ngcp-mediaproxy-ng is no longer available and replaced with rtpproxy we’re trying to use it. But kamailio said that the proxy isn’t answering the way expected. ERROR: rtpengine [rtpengine.c:1622]: rtpp_test(): proxy responded with invalid response Any advise would be nice. Thank you Fred

2 1

Re: [SR-Users] Kamailio IMS deployment
by sainath.ellendula＠wipro.com 30 Jan '16

30 Jan '16

Hi Basit, Thanks for response. I have tried the below commands to grant all privileges. The commands results OK. Still I was facing the same issue which is mentioned in trailing mail. Could anyone guide me here to proceed further. Any suggestions/solutions would be very helpful. Regards, Sainath ---------- Forwarded message ---------- From: "Abdul Basit" <basitstar(a)hotmail.com<mailto:basitstar@hotmail.com>> Date: Jan 27, 2016 7:37 PM Subject: Re: [SR-Users] Kamailio IMS deployment To: "Kamailio SER - Users Mailing List" <sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org>>, "franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at>" <franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at>> Cc: use the following command and try again.. GRANT ALL PRIVILEGES ON *.* TO '<user>'@'<hostname>' IDENTIFIED BY '<password>'; GRANT ALL PRIVILEGES ON *.* TO '<user>'@'%' IDENTIFIED BY '<password>'; FLUSH PRIVILEGES; regards, AB ________________________________ From: sainath.ellendula(a)wipro.com<mailto:sainath.ellendula@wipro.com> To: franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at> Date: Wed, 27 Jan 2016 06:21:52 +0000 CC: sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org> Subject: Re: [SR-Users] Kamailio IMS deployment Hi Franz, Thanks for the response. As suggested followed below commands to check the GRANTs on database hss_db. mysql -u root -p show grants for 'hss'@'server.net1.test'; The output result is same as mentioned below. Could you please guide me here to proceed further. Regards, Sainath ---------- Forwarded message ---------- From: "Franz Edler" <franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at>> Date: Jan 27, 2016 1:07 AM Subject: RE: [SR-Users] Kamailio IMS deployment To: "Kranti Kumar" <krantikumara(a)gmail.com<mailto:krantikumara@gmail.com>>, "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org>> Cc: "Ramya Y" <y.ramya146(a)gmail.com<mailto:y.ramya146@gmail.com>> Obviously the access of HSS to the database did not succeed. You should check if access permissions to the database is enabled for HSS. Check the GRANTs on the database hss_db. mysql -u root -p show grants for 'hss'@'server.net1.test'; quit; The result should be: +-------------------------------------------------------------------------------------------------------------------+ | Grants for hss(a)server.net1.test<mailto:hss@server.net1.test> | +-------------------------------------------------------------------------------------------------------------------+ | GRANT USAGE ON *.* TO 'hss'@'server.net1.test' IDENTIFIED BY PASSWORD '*AC83FCF24B79020EF2C51D780CDFA559F25CC9BE' | | GRANT SELECT, INSERT, UPDATE, DELETE ON `hss_db`.* TO 'hss'@'server.net1.test' | +-------------------------------------------------------------------------------------------------------------------+ BR Franz From: Kranti Kumar [mailto:krantikumara@gmail.com<mailto:krantikumara@gmail.com>] Sent: Sunday, January 24, 2016 10:55 AM To: franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at>; Kamailio (SER) - Users Mailing List <sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org>> Cc: Ramya Y <y.ramya146(a)gmail.com<mailto:y.ramya146@gmail.com>> Subject: Re: [SR-Users] Kamailio IMS deployment Thanks a lot Franz. Observed few issues even after changes done in /etc/bind. Please find the below Errors in each interfaces and also find the attachment of /var/log/syslog(not shared full logs) Could you please help me here to proceed further. HSS – Configured IP : 10.0.0.9 root@server:~# ./hss.sh – Configured IP : 10.0.0.9 Building Classpath Classpath is lib/xml-apis.jar:lib/xercesImpl.jar:lib/xerces-2.4.0.jar:lib/xalan-2.4.0.jar:lib/tomcat-util.jar:lib/tomcat-http.jar:lib/tomcat-coyote.jar:lib/struts.jar:lib/servlets-default.jar:lib/servlet-api.jar:lib/naming-resources.jar:lib/naming-factory.jar:lib/mysql-connector-java-3.1.12-bin.jar:lib/mx4j-3.0.1.jar:lib/log4j.jar:lib/junit.jar:lib/junitee.jar:lib/jta.jar:lib/jsp-api.jar:lib/jmx.jar:lib/jdp.jar:lib/jasper-runtime.jar:lib/jasper-compiler-jdt.jar:lib/jasper-compiler.jar:lib/hibernate3.jar:lib/FHoSS.jar:lib/ehcache-1.1.jar:lib/dom4j-1.6.1.jar:lib/commons-validator.jar:lib/commons-modeler.jar:lib/commons-logging.jar:lib/commons-logging-1.0.4.jar:lib/commons-lang.jar:lib/commons-fileupload.jar:lib/commons-el.jar:lib/commons-digester.jar:lib/commons-collections-3.1.jar:lib/commons-beanutils.jar:lib/cglib-2.1.3.jar:lib/catalina-optional.jar:lib/catalina.jar:lib/c3p0-0.9.1.jar:lib/base64.jar:lib/asm.jar:lib/asm-attrs.jar:lib/antlr-2.7.6.jar::log4j.properties:.. 2016-01-21 14:07:07,876 INFO de.fhg.fokus.hss.main.TomcatServer - startTomcat Tomcat-Server is started. 2016-01-21 14:07:12,462 WARN org.apache.catalina.connector.MapperListener - registerEngine Unknown default host: 10.0.0.9 2016-01-21 14:07:16,578 INFO de.fhg.fokus.hss.web.servlet.ResponseFilter - init Response Filter Initialisation! 2016-01-21 14:07:17,966 INFO de.fhg.fokus.hss.main.TomcatServer - startTomcat WebConsole of FHoSS was started ! 2016-01-21 14:08:21,200 WARN com.mchange.v2.resourcepool.BasicResourcePool - run com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1670988b<mailto:com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1670988b> -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (60). Last acquisition attempt exception: com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception: ** BEGIN NESTED EXCEPTION ** java.net.SocketException MESSAGE: java.net.ConnectException: Connection refused STACKTRACE: java.net.SocketException: java.net.ConnectException: Connection refused PCSCF – Configured IP : 10.0.0.10 root@server:~# kamailio -f /usr/local/etc/kamailio/kamailio-pcscf.cfg loading modules under config path: /usr/local/lib64/kamailio/modules/ 0(2352) INFO: <core> [sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: pcscf.net1.test [10.0.0.10]:4060 Aliases: *: pcscf.net1.test:* WARNING: no fork mode 0(2352) INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob 0(2352) INFO: rr [rr_mod.c:174]: mod_init(): outbound module not available 0(2352) INFO: ims_usrloc_pcscf [hslot.c:62]: ul_init_locks(): locks array size 512 0(2352) INFO: <core> [udp_server.c:150]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(2352) INFO: <core> [udp_server.c:200]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(2352) WARNING: ims_usrloc_pcscf [usrloc_db.c:59]: connect_db(): DB connection already open... continuing ^C^C 0(2352) NOTICE: <core> [main.c:683]: handle_sigs(): Thank you for flying kamailio!!! 1(2373) INFO: <core> [main.c:798]: sig_usr(): signal 15 received 2(2374) INFO: <core> [main.c:798]: sig_usr(): signal 15 received 0(2352) INFO: <core> [sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized ICSCF – Configured IP : 10.0.0.11 root@server:~# kamailio -f /usr/local/etc/kamailio/kamailio-icscf.cfg loading modules under config path: /usr/local/lib64/kamailio/modules/ 0(2353) INFO: <core> [sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: icscf.net1.test [10.0.0.11]:5060 Aliases: *: icscf.net1.test:* WARNING: no fork mode 0(2353) INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob 0(2353) INFO: rr [rr_mod.c:174]: mod_init(): outbound module not available 0(2353) INFO: <core> [udp_server.c:150]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(2353) INFO: <core> [udp_server.c:200]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(2353) INFO: cdp [mod.c:227]: cdp_child_init(): CDiameterPeer child starting ... 0(2353) INFO: cdp [mod.c:229]: cdp_child_init(): ... CDiameterPeer child started 10(2370) INFO: cdp [timer.c:205]: timer_process(): Timer process starting up... 6(2366) INFO: cdp [worker.c:331]: worker_process(): [3] Worker process started... 7(2367) INFO: cdp [receiver.c:445]: receiver_process(): receiver_process(): [] Receiver process doing init on new process... 7(2367) INFO: cdp [receiver.c:450]: receiver_process(): receiver_process(): [] Receiver process starting up... 8(2368) INFO: cdp [receiver.c:445]: receiver_process(): receiver_process(): [hss.net1.test] Receiver process doing init on new process... 8(2368) INFO: cdp [receiver.c:183]: add_serviced_peer(): add_serviced_peer(): Adding serviced_peer_t to receiver for peer [hss.net1.test] 9(2369) INFO: cdp [acceptor.c:82]: acceptor_process(): Acceptor process starting up... 9(2369) WARNING: cdp [tcp_accept.c:123]: create_socket(): create_socket(): Trying to open/bind/listen on 10.0.0.9 port 3869 9(2369) WARNING: cdp [tcp_accept.c:148]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.0.0.9 port 3869 9(2369) INFO: cdp [acceptor.c:96]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... 8(2368) INFO: cdp [receiver.c:450]: receiver_process(): receiver_process(): [hss.net1.test] Receiver process starting up... 10(2370) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 0 10(2370) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test 10(2370) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868 10(2370) WARNING: cdp [receiver.c:911]: peer_connect(): peer_connect(): Error opening connection to to 10.0.0.9 port 3868 >Connection refused 10(2370) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 0 10(2370) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test 10(2370) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868 10(2370) INFO: cdp [receiver.c:932]: peer_connect(): peer_connect(): Peer hss.net1.test:3868 connected 10(2370) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 6 10(2370) WARNING: cdp [peermanager.c:315]: peer_timer(): Inactivity on peer [hss.net1.test], sending DWR... - if we don't get a reply, the peer will be closed 8(2368) INFO: cdp [receiver.c:802]: receive_loop(): select_recv(): [hss.net1.test] read on socket [14] returned 0 > ... dropping 8(2368) INFO: cdp [receiver.c:219]: disconnect_serviced_peer(): drop_serviced_peer(): [hss.net1.test] Disconnecting from peer ^C10(2370) INFO: <core> [main.c:798]: sig_usr(): signal 2 received 0(2353) ALERT: <core> [main.c:725]: handle_sigs(): child process 2361 exited normally, status=0 0(2353) INFO: <core> [main.c:740]: handle_sigs(): dont_fork turned on, living on 0(2353) NOTICE: <core> [main.c:683]: handle_sigs(): Thank you for flying kamailio!!! 2(2362) INFO: <core> [main.c:798]: sig_usr(): signal 15 received 0(2353) INFO: cdp [mod.c:242]: cdp_exit(): CDiameterPeer child stopping ... 0(2353) INFO: cdp [diameter_peer.c:428]: diameter_peer_destroy(): destroy_diameter_peer(): Terminating all children... 0(2353) INFO: cdp [diameter_peer.c:435]: diameter_peer_destroy(): destroy_diameter_peer(): Waiting for child [2370] to terminate... 0(2353) INFO: cdp [diameter_peer.c:447]: diameter_peer_destroy(): destroy_diameter_peer(): All processes terminated. Cleaning up. 0(2353) INFO: cdp [worker.c:140]: worker_destroy(): Unlocking workers waiting on empty queue... 0(2353) INFO: cdp [worker.c:143]: worker_destroy(): Unlocking workers waiting on full queue... 0(2353) CRITICAL: cdp [diameter_peer.c:487]: diameter_peer_destroy(): destroy_diameter_peer(): Bye Bye from C Diameter Peer test 0(2353) INFO: cdp [mod.c:244]: cdp_exit(): ... CDiameterPeer child stoped 0(2353) INFO: <core> [sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized SCSCF – Configured IP : 10.0.0.12 root@server:/etc# kamailio -f /usr/local/etc/kamailio/kamailio-scscf.cfg loading modules under config path: /usr/local/lib64/kamailio/modules/ 0(2371) INFO: <core> [sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: scscf.net1.test [10.0.0.12]:6060 Aliases: *: scscf.net1.test:* WARNING: no fork mode 0(2371) INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob 0(2371) INFO: rr [rr_mod.c:174]: mod_init(): outbound module not available 0(2371) INFO: ims_usrloc_scscf [hslot.c:69]: ul_init_locks(): locks array size 512 0(2371) INFO: ims_usrloc_scscf [hslot_sp.c:67]: subs_init_locks(): locks array size 512 0(2371) INFO: ims_usrloc_scscf [contact_hslot.c:67]: init_contacts_locks(): locks array size 512 0(2371) INFO: <core> [udp_server.c:150]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(2371) INFO: <core> [udp_server.c:200]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(2371) INFO: cdp [mod.c:227]: cdp_child_init(): CDiameterPeer child starting ... 0(2371) INFO: cdp [mod.c:229]: cdp_child_init(): ... CDiameterPeer child started 3(2381) INFO: cdp [worker.c:331]: worker_process(): [0] Worker process started... 4(2382) INFO: cdp [worker.c:331]: worker_process(): [1] Worker process started... 5(2383) INFO: cdp [worker.c:331]: worker_process(): [2] Worker process started... 7(2390) INFO: cdp [receiver.c:445]: receiver_process(): receiver_process(): [] Receiver process doing init on new process... 7(2390) INFO: cdp [receiver.c:450]: receiver_process(): receiver_process(): [] Receiver process starting up... 8(2392) INFO: cdp [receiver.c:445]: receiver_process(): receiver_process(): [hss.net1.test] Receiver process doing init on new process... 8(2392) INFO: cdp [receiver.c:183]: add_serviced_peer(): add_serviced_peer(): Adding serviced_peer_t to receiver for peer [hss.net1.test] 8(2392) INFO: cdp [receiver.c:450]: receiver_process(): receiver_process(): [hss.net1.test] Receiver process starting up... 9(2393) INFO: cdp [acceptor.c:82]: acceptor_process(): Acceptor process starting up... 9(2393) WARNING: cdp [tcp_accept.c:123]: create_socket(): create_socket(): Trying to open/bind/listen on 10.0.0.9 port 3870 9(2393) WARNING: cdp [tcp_accept.c:148]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.0.0.9 port 3870 9(2393) INFO: cdp [acceptor.c:96]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... 10(2394) INFO: cdp [timer.c:205]: timer_process(): Timer process starting up... 10(2394) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 0 10(2394) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test 10(2394) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868 10(2394) WARNING: cdp [receiver.c:911]: peer_connect(): peer_connect(): Error opening connection to to 10.0.0.9 port 3868 >Connection refused 10(2394) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 0 10(2394) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test 10(2394) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868 10(2394) INFO: cdp [receiver.c:932]: peer_connect(): peer_connect(): Peer hss.net1.test:3868 connected 10(2394) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 6 10(2394) WARNING: cdp [peermanager.c:315]: peer_timer(): Inactivity on peer [hss.net1.test], sending DWR... - if we don't get a reply, the peer will be closed 10(2394) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 6 8(2392) INFO: cdp [receiver.c:802]: receive_loop(): select_recv(): [hss.net1.test] read on socket [15] returned 0 > ... dropping 8(2392) INFO: cdp [receiver.c:219]: disconnect_serviced_peer(): drop_serviced_peer(): [hss.net1.test] Disconnecting from peer 10(2394) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 0 10(2394) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test 10(2394) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868 10(2394) WARNING: cdp [receiver.c:911]: peer_connect(): peer_connect(): Error opening connection to to 10.0.0.9 port 3868 >Connection refused ^C11(2398) INFO: <core> [main.c:798]: sig_usr(): signal 2 received 9(2393) INFO: <core> [main.c:798]: sig_usr(): signal 2 received 0(2371) ALERT: <core> [main.c:725]: handle_sigs(): child process 2381 exited normally, status=0 0(2371) INFO: <core> [main.c:740]: handle_sigs(): dont_fork turned on, living on 0(2371) NOTICE: <core> [main.c:683]: handle_sigs(): Thank you for flying kamailio!!! 10(2394) INFO: <core> [main.c:798]: sig_usr(): signal 15 received 0(2371) INFO: cdp [mod.c:242]: cdp_exit(): CDiameterPeer child stopping ... On Fri, Jan 22, 2016 at 2:16 AM, Franz Edler <franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at>> wrote: Hi, you can see the first error is a database error: ERROR: db_mysql [km_my_con.c:124]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on 'server.net1.test' (111) This error I expected because you have to adapt the access permissions to the database. Just check the GRANT statements in my log-file and try to understand what they do. Then adapt it accordingly. BR Franz From: Ramya Y [mailto:y.ramya146@gmail.com<mailto:y.ramya146@gmail.com>] Sent: Wednesday, January 20, 2016 2:19 PM To: franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at>; Kamailio (SER) - Users Mailing List <sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org>> Subject: Re: [SR-Users] Kamailio IMS deployment Hi Franz we have tried with different interfaces(eth0(10.0.0.9),eth1(10.0.0.10),eth2(10.0.0.11),eth3(10.0.0.12) for P/I/S ,but facing below error. root@server:/etc# kamailio -f /usr/local/etc/kamailio/kamailio-pcscf.cfg loading modules under config path: /usr/local/lib64/kamailio/modules/ 0(1630) INFO: <core> [sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: pcscf.net1.test [10.0.0.10]:4060 Aliases: *: pcscf.net1.test:* WARNING: no fork mode 0(1630) INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob 0(1630) INFO: rr [rr_mod.c:174]: mod_init(): outbound module not available 0(1630) INFO: ims_usrloc_pcscf [hslot.c:62]: ul_init_locks(): locks array size 512 0(1630) ERROR: db_mysql [km_my_con.c:124]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on 'server.net1.test' (111) 0(1630) ERROR: <core> [db.c:318]: db_do_init2(): could not add connection to the pool 0(1630) ERROR: ims_usrloc_pcscf [usrloc_db.c:79]: init_db(): unable to connect to the database 0(1630) ERROR: ims_usrloc_pcscf [ul_mod.c:203]: mod_init(): Error initializing db connection 0(1630) ERROR: <core> [sr_module.c:962]: init_mod(): Error while initializing module ims_usrloc_pcscf (/usr/local/lib64/kamailio/modules/ims_usrloc_pcscf.so) ERROR: error while initializing modules 0(1630) INFO: <core> [sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialize could you please help me how to proceed further, steps followed: =========== 1)Modified at - /etc/network/interfaces: created eth1,eth2,eth3 for P/I/S-CSCF. Interfaces are up. 2)Added Bind address at /etc/mysql/my.cnf bind-address 10.0.0.9 bind-address 10.0.0.10 bind-address 10.0.0.11 bind-address 10.0.0.12 3)Modified at /etc/bind/net1.test.zone $ORIGIN net1.test. $TTL 1W @ 1D IN SOA serverkde. root.net1.test ( 2010081401 ; Serial YYYYMMDDXX 3H ; refresh 15M ; retry 1W ; expiry 1D ) ; minimum 1D IN NS server server 1D IN A 10.0.0.9 hss 1D IN CNAME server as1 1D IN CNAME server as2 1D IN CNAME server xcap 1D IN CNAME server server1 1D IN A 10.0.0.10 pcscf 1D IN CNAME server1 server2 1D IN A 10.0.0.11 icscf 1D IN CNAME server2 server3 1D IN A 10.0.0.12 scscf 1D IN CNAME server3 4)Modified at /etc/bind/0.0.10.zone $TTL 86400 @ IN SOA server. root.net2.test ( 2010081401 ; Serial YYYYMMDDXX 28800 ; Refresh 14400 ; Retry 3600000 ; Expire 86400 ) ; Minimum IN NS server.net1.test. IN NS server1.net1.test. IN NS server2.net1.test. IN NS server3.net1.test. 10 IN PTR notebook.net1.test. 9 IN PTR server.net1.test. 7 IN PTR server.net2.test. 5)Modified at /etc/resolve.conf domain net1.test search net1.test nameserver server.net1.test nameserver server1.net1.test nameserver server2.net1.test nameserver server3.net1.test 6)Modified at /etc/hosts 127.0.0.1 localhost 10.0.0.9 server.net1.test server 10.0.0.10 server1.net1.test server1 10.0.0.11 server2.net1.test server2 10.0.0.12 server3.net1.test server3 10.0.0.9 net1.test 10.0.0.10 pcscf.net1.test 10.0.0.11 icscf.net1.test 10.0.0.12 scscf.net1.test Thanks, Ramyasri. On Sun, Jan 17, 2016 at 5:33 PM, Franz Edler <franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at>> wrote: Fine. This exactly was my intention. BR Franz > -----Original Message----- > From: sr-users [mailto:sr-users-bounces@lists.sip-router.org<mailto:sr-users-bounces@lists.sip-router.org>] On Behalf Of > Vasiliy Ganchev > Sent: Monday, January 11, 2016 9:08 AM > To: sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org> > Subject: Re: [SR-Users] Kamailio IMS deployment > > Hi Franz! > > Thanks for sharing! Great job, end excellent materials to get started with > students (beside my main work I also teach students in Odessa National > Academy of Telecommunication). > I was looking for some "light" way how to start with real deployment of IMS, > not pure theory, and this is just the kind I wanted! > > Will try your deploy in education process this year. (will share the results in > the end) > > Cheers! > > > > -- > View this message in context: http://sip- > router.1086192.n5.nabble.com/Kamailio-IMS-deployment-<http://router.1086192.n5.nabble.com/Kamailio-IMS-deployment-> > tp143593p144517.html > Sent from the Users mailing list archive at Nabble.com. > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr- > users(a)lists.sip-router.org<mailto:users@lists.sip-router.org> http://lists.sip-router.org/cgi- > bin/mailman/listinfo/sr-users _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com<http://www.wipro.com> _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

2 3

Re: [SR-Users] [sr-dev] Fosdem 2016
by Daniel-Constantin Mierla 29 Jan '16

29 Jan '16

Hello, ok, let's see how many we are going to be and then decide how to do it (if we are not a large group, we can just go in the city center and walk around for a place). Cheers, Daniel On 06/01/16 02:30, Alexandr Dubovikov wrote: > Hello Daniel, > > I will be there, plus Lorenzo and Torsen. Make a small event on > Saturday will be very cool, but not at Beer Mania :-) > > Wbr, > Alexandr > > On 05.01.2016 20:06, Daniel-Constantin Mierla wrote: >> Hello, >> >> anyone going to Fosdem? >> >> If no unexpected weather conditions messing the transport system, I am >> going to be there. It would be good to know who else we can meet there. >> >> If there are enough people interested, we can try organizing a social >> event (dinner/drinks) on Saturday evening. Last year we did it together >> with Jitsi team, but they are not coming this year. Perhaps there are >> other folks around the RTC dev room we can ask. >> >> On the other hand, it is harder to find a place if it is a large group, >> even harder to put all together if there are different >> groups/coordinators. Also, it is not easy to discuss withing a large >> group, as typically for a dinner we were seated to tables. Therefore >> organizing for a smaller group just for Kamailio friends could be a good >> alternative. Let's see first the number of participant and the level of >> interest for various options. >> >> This being an announcement, was crossposted to few mailing lists, but as >> most of the people are on sr-users, I think it would be good to reply >> and follow up on this discussion only there. >> >> Cheers, >> Daniel >> > > > _______________________________________________ > sr-dev mailing list > sr-dev(a)lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu

5 6

Memory issue?
by Igor Potjevlesch 29 Jan '16

29 Jan '16

Hello, I got several errors this morning on a Kamailio instance. The first occurred without a complete crash of Kamailio but 4 coredumps have been created: BFD: Warning: /core.3818 is truncated: expected core file size >= 342618112, found: 61579264. [New Thread 3818] Cannot access memory at address 0x7f66e0557658 BFD: Warning: /core.3821 is truncated: expected core file size >= 343044096, found: 21229568. [New Thread 3821] Cannot access memory at address 0x7f66e0557658 BFD: Warning: /core.3822 is truncated: expected core file size >= 342675456, found: 120066048. [New Thread 3822] Cannot access memory at address 0x7f66e0557658 BFD: Warning: /core.3839 is truncated: expected core file size >= 342401024, found: 2691072. [New Thread 3839] Cannot access memory at address 0x3d6f021168 Cannot access memory at address 0x3d6f021168 Cannot access memory at address 0x3d6f021168 It seems that Kamailio auto recovered without fully crashed during this issue. But the Kamailio FIFO was deleted and kamctl didn't worked anymore. I had to properly restart. I have seen in the logs: Jan 21 10:21:11 /usr/local/sbin/kamailio[3843]: ERROR: <core> [dtrie.c:153]: dtrie_insert(): could not allocate shared memory from available pool Jan 21 10:21:11 /usr/local/sbin/kamailio[3839]: ERROR: <core> [dtrie.c:144]: dtrie_insert(): could not allocate shared memory from available pool Jan 21 10:21:11 /usr/local/sbin/kamailio[3839]: ERROR: userblacklist [db.c:91]: db_build_userbl_tree(): could not insert values into trie. Jan 21 10:21:11 /usr/local/sbin/kamailio[3843]: ERROR: userblacklist [db.c:91]: db_build_userbl_tree(): could not insert values into trie. Jan 21 10:21:11 /usr/local/sbin/kamailio[3831]: ERROR: <core> [dtrie.c:144]: dtrie_insert(): could not allocate shared memory from available pool Jan 21 10:21:11 /usr/local/sbin/kamailio[3831]: ERROR: userblacklist [db.c:91]: db_build_userbl_tree(): could not insert values into trie. Jan 21 10:21:11 /usr/local/sbin/kamailio[3841]: ERROR: <core> [dtrie.c:153]: dtrie_insert(): could not allocate shared memory from available pool Jan 21 10:21:12 /usr/local/sbin/kamailio[3821]: ERROR: <core> [dtrie.c:153]: dtrie_insert(): could not allocate shared memory from available pool Jan 21 10:21:12 /usr/local/sbin/kamailio[3821]: ERROR: userblacklist [db.c:91]: db_build_userbl_tree(): could not insert values into trie. Jan 21 10:21:12 /usr/local/sbin/kamailio[3828]: ERROR: <core> [dtrie.c:153]: dtrie_insert(): could not allocate shared memory from available pool Jan 21 10:21:12 /usr/local/sbin/kamailio[3843]: ERROR: <core> [dtrie.c:153]: dtrie_insert(): could not allocate shared memory from available pool Jan 21 10:21:12 /usr/local/sbin/kamailio[3818]: ERROR: <core> [dtrie.c:144]: dtrie_insert(): could not allocate shared memory from available pool Jan 21 10:21:12 /usr/local/sbin/kamailio[3818]: ERROR: userblacklist [db.c:91]: db_build_userbl_tree(): could not insert values into trie. [.] Jan 21 10:21:13 kernel: kamailio[3818]: segfault at 40 ip 00007f66d8812af2 sp 00007fff09c83380 error 4 in libtrie.so.1.0[7f66d8810000+5000] Jan 21 10:21:13 kernel: kamailio[3822]: segfault at 20 ip 00007f66d8812af2 sp 00007fff09c83380 error 4 in libtrie.so.1.0[7f66d8810000+5000] Jan 21 10:21:14 kernel: kamailio[3821]: segfault at 0 ip 00007f66d8812af2 sp 00007fff09c83380 error 4 in libtrie.so.1.0[7f66d8810000+5000] [.] Jan 21 10:21:14 /usr/local/sbin/kamailio[3807]: ALERT: <core> [main.c:784]: handle_sigs(): child process 3828 exited by a signal 11 Jan 21 10:21:14 /usr/local/sbin/kamailio[3807]: ALERT: <core> [main.c:787]: handle_sigs(): core was not generated Jan 21 10:21:14 /usr/local/sbin/kamailio[3807]: ALERT: <core> [main.c:784]: handle_sigs(): child process 3825 exited by a signal 11 Jan 21 10:21:14 /usr/local/sbin/kamailio[3807]: ALERT: <core> [main.c:787]: handle_sigs(): core was not generated Jan 21 10:21:14 /usr/local/sbin/kamailio[3807]: INFO: <core> [main.c:799]: handle_sigs(): terminating due to SIGCHLD Jan 21 10:21:14 /usr/local/sbin/kamailio[3832]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Jan 21 10:21:14 /usr/local/sbin/kamailio[3841]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Jan 21 10:21:14 /usr/local/sbin/kamailio[3876]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received 1 hour later a new crash but here Kamailio has completely restarted with two coredump showing the same error than previous one. And 2 coredumps readable: Core was generated by `/usr/local/sbin/kamailio -P /var/run/kamailio.pid -m 256 -M 64'. Program terminated with signal 11, Segmentation fault. #0 0x00007f13a1550af2 in dtrie_insert (root=0x7f138d7ffb38, number=0x22ba6c0 "003716716", numberlen=9, data=0x2, branches=10) at dtrie.c:141 141 if (node->child[digit] == NULL) { Core was generated by `/usr/local/sbin/kamailio -P /var/run/kamailio.pid -m 256 -M 64'. Program terminated with signal 11, Segmentation fault. #0 0x00007f13a1550af2 in dtrie_insert (root=0x7f138d7ff998, number=0x22b57a8 "0035587482", numberlen=10, data=0x2, branches=10) at dtrie.c:141 141 if (node->child[digit] == NULL) { Kamailio is 4.2.6 on this instance. Regards, Igor.

3 4

RTP Statistics
by Gholamreza Sabery 29 Jan '16

29 Jan '16

Hello everyone. I want to store RTCP Statistics for a RTP session. Currently I am using $rtpstat pseudo-variable which is exported by RTPProxy module. The value of this variable does not show actual number of packets sent and received; and only contains ttl, npkts_ina, npkts_ino, nrelayed and ndropped. I want actual number of packets sent from and actual number of packets received by a client. How can I obtain this information?

2 3

Presence: Notify on publication status refresh
by Aleš Šturm 28 Jan '16

28 Jan '16

Hi all, I am using Kamailio 4.3 as Presence server and I have a question regarding NOTIFY messages sent after publication status refresh. When PUA sends refreshing PUBLISH request (before expiration) Kamailio sends NOTIFY request. Large number of watchers per one presentity causes large traffic. RFC3265 states: NOTIFY messages are sent to inform subscribers of changes in state to which the subscriber has a subscription. But when publication is only refreshed (publication expiration is extended) the publish state is not changed (PUBLISH without XML body). >From RFC5839: The SIP PUBLISH [RFC3903] method uses a similar mechanism, where a refresh of a publication is done by reference to its assigned entity-tag, instead of retransmitting the event state each time the publication expiration is extended. Is it possible to configure Kamailio that wouldn't send NOTIFY request to watchers when publication status refresh (PUBLISH without XML Body) occur? Can anyone help? Thanks in advance, Ales

3 5

Is "new_conn_alias_flags" supported/recommended? It seems to solve my NAT problem, but I'm worried it's not safe.
by Cody Herzog 28 Jan '16

28 Jan '16

Hello. In a test environment, I've been able to use the "new_conn_alias_flags" option to solve a NAT problem, but I'm concerned that the option is not supported/safe. It seems the option is not documented, and cannot be used in the config file, because 'cfg.y' doesn't support parsing it. However, it can be set at runtime using a command such as the following: kamctl kamcmd cfg.set_now_int tcp new_conn_alias_flags 1 **Question #1** Is this option experimental and/or risky? As background, I will now try to describe my NAT problem. Perhaps there is an alternate way to solve my problem which doesn't require using "new_conn_alias_flags". My server architecture uses multiple Kamailio edge proxies, and a single central Kamailio registrar. The edge proxies listen on multiple TLS ports. All servers are on version 4.3.3. My client app includes a port tester, which periodically tests whether certain SIP proxy targets are reachable. These test connections are very brief, and don’t persist. The problem seems to relate to a behavior of iptables as follows: Client A and client B are both behind the same iptables NAT. Client A has a persistent TLS connection to one of the proxies. Client B is doing periodic port testing, and sometimes, the itpables NAT will assign exactly the same external IP and port for a test connection as is already being used by client A for its persistent connection, to the same SIP proxy IP. Only the SIP proxy target port is different. To better explain, I will list out examples for all the relevant IPs and ports along the paths. The IPs and ports I've selected are arbitrary. Client A persistent TLS connection ---------------------------------- Internal IP:Port = 10.10.10.100:30000 External IP:Port = 88.88.88.88:10000 SIP proxy IP:Port = 66.66.66.66:5061 Client B port test connection ------------------------------ Internal IP:Port = 10.10.10.101:35000 External IP:Port = 88.88.88.88:10000 *** Same as above! SIP proxy IP:Port = 66.66.66.66:443 *** SIP proxy port being different is the only thing that makes this a distinct TCP connection from above. When this happens, it seems that some of the TCP connection/alias hash tables inside Kamailio are modified such that future attempts to call client A may fail. Client B's port test connection seems to overwrite some of the state which was important for connections into Client A. After client B's test connection has stomped on client A's state, this is what happens: When an INVITE sent to client A arrives at the proxy, the proxy fails to find the matching persistent TLS connection which already exists, so it tries to open a new outbound TLS connection to client A, but that always fails because client A's NAT doesn't allow it. Such calls end up failing with a 408 timeout error. I added some extra logging to the TCP connection/alias hash code paths, and I can see some of the client A entries being overwritten when client B makes its test connection. Did I explain that well enough? I know it's a bit confusing. Anyway, after doing some code inspection, I noticed that the "new_conn_alias_flags" option seemed like it might improve this problem, or at least change the behavior. It turns out that setting "new_conn_alias_flags" equal to 1 seems to solve my problem. With that setting, client B's test connections do not overwrite any of the TCP connection hashes/aliases for client A's persistent TLS connection, and calls into client A never seem to fail. **Question #2** Does setting "new_conn_alias_flags" to 1 seem like a good way to address my type of problem? If not, is there an alternate way to solve my problem? Perhaps there are some things I should be doing with the NAT helper module that could fix the issue without relying on "new_conn_alias_flags"? I realize that I may need to provide more information to answer these questions fully, but I’m initially hoping to just get some high-level impressions, without going into a ton of details. Thanks.

2 6

kamailio 4.4 writes wrong expires parameter at the database
by Yuriy Gorlichenko 27 Jan '16

27 Jan '16

2 3

Fwd: Invalid Configuration File
by Andrew J. Smith 27 Jan '16

27 Jan '16

Hello! I followed this tutorial (http://kb.asipto.com/kamailio:skype-like-service-in-less-than-one-hour) to the T using virtual box and a debian wheezy image. Actually, I did change one thing: This repository "deb http://deb.kamailio.org/kamailio31-nightly squeeze main" always resulted in a file not found error. So I used these two lines instead: deb http://deb.kamailio.org/kamailio squeeze main deb-src http://deb.kamailio.org/kamailio squeeze main Everything else is fine except for the fact that the MySQL users have different names/passwords. I was able to generate users and configured everything as posted. When I start the service (/etc/init.d/kamailio start) I get an error message: "Not starting Kamailio SIP Server: invalid configuration file! ... failed! failed!" followed by a looooooong list of errors (copied below). I retried with Kamailio33 (31 is not available as far as I can tell). This version has the MySQL users indicated in the tutorial (openser, openserro) - newer versions have a MySQL user named kamailio... Anyway, same long list of errors as before. I also tried the same procedure on a Raspberry Pi... Everything goes exactly as described until I try to start the Kamailio server. If I don't replace the original kamailio.cfg file with the one linked to in the tutorial, the server starts, but I can't seem to connect to it using Jitsi. What am I doing wrong? Any help would be greatly appreciated. Best regards, Andrew -------------------------------------------------------- 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <db_mysql> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 191, column 12-24: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <mi_fifo> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 194, column 12-23: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <kex> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 195, column 12-19: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <tm> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 196, column 12-18: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <tmx> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 197, column 12-19: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <sl> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 198, column 12-18: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <rr> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 199, column 12-18: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <pv> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 200, column 12-18: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <maxfwd> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 201, column 12-22: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <usrloc> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 202, column 12-22: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <registrar> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 203, column 12-25: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <textops> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 204, column 12-23: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <siputils> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 205, column 12-24: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <xlog> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 206, column 12-20: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <sanity> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 207, column 12-22: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <ctl> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 208, column 12-19: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <mi_rpc> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 209, column 12-22: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <acc> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 210, column 12-19: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <auth> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 213, column 12-20: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <auth_db> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 214, column 12-23: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <nathelper> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 234, column 12-25: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <rtpproxy> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 235, column 12-24: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <tls> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 239, column 12-19: failed to load module 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <mi_fifo> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 255, column 54: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <tm> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 260, column 39: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <tm> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 262, column 33: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <tm> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 264, column 38: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <rr> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 269, column 35: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <rr> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 271, column 35: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <registrar> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 275, column 44: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <acc> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 284, column 33: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <acc> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 285, column 32: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <acc> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 286, column 36: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <acc> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 290, column 38: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <acc> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 292, column 30: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <acc> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 293, column 37: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <acc> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 295, column 73: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <acc> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 296, column 45: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <usrloc> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 310, column 75: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <usrloc> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 311, column 32: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <usrloc> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 312, column 35: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <auth_db> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 318, column 76: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <auth_db> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 319, column 41: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <auth_db> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 320, column 50: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <auth_db> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 321, column 43: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <auth_db> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 322, column 36: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <rtpproxy> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 363, column 77: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <nathelper> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 366, column 45: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <nathelper> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 367, column 43: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <nathelper> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 368, column 41: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <nathelper> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 369, column 64: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <nathelper|registrar> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 372, column 65: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <usrloc> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 373, column 34: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <tls> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 379, column 50: Can't set module parameter 0(20143) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command is_method (params 1) 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 418, column 24: unknown command, missing loadmodule? 0(20143) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command t_check_trans (params 0) 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 420, column 21: unknown command, missing loadmodule? 0(20143) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command t_relay (params 0) 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 421, column 12: unknown command, missing loadmodule? 0(20143) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command t_check_trans (params 0) 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 425, column 16: unknown command, missing loadmodule? 0(20143) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command remove_hf (params 1) 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 432, column 19: unknown command, missing loadmodule? 0(20143) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command is_method (params 1) 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 433, column 34: unknown command, missing loadmodule? 0(20143) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command record_route (params 0) 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 434, column 16: unknown command, missing loadmodule? 0(20143) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command is_method (params 1) 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 437, column 24: unknown command, missing loadmodule? 0(20143) ERROR: <core> [pvapi.c:825]: pv_parse_spec2(): error searching pvar "rU" 0(20143) ERROR: <core> [pvapi.c:1029]: pv_parse_spec2(): wrong char [U/85] in [$rU] at [2 (0)] 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 453, column 6-8: Can't get from cache: $rU ERROR: bad config file (63 errors) 0(20143) INFO: <core> [sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized ... failed! failed! --------------------------------------------------------

2 1

doubt using sip tcp creating new transaction
by david escartin 27 Jan '16

27 Jan '16

hello all i'm facing some weird log from kamailio (i think they are weird) when using sip tcp in the caller side and udp in the callee side. seems like the tcp socket is active in the caller side and the call is connected, since the invite transaction completes. After that, if we receive an in-dialog request from the callee side, the kamailio doesnt find the tcp connection created and it has to create again the socket by SYN procedure for the other conn way. up to this point i think it's everything correct. A----the thing i dont understand, is that checking version 4.2.6, the logs i have when the request in-dialog comes from UAS, are like these 5(2979) DEBUG: <core> [tcp_main.c:1820]: tcp_send(): tcp_send: no open tcp connection found, opening new one 5(2979) DEBUG: <core> [ip_addr.c:243]: print_ip(): tcpconn_new: new tcp connection: 79.170.68.171 5(2979) DEBUG: <core> [tcp_main.c:1073]: tcpconn_new(): tcpconn_new: on port 5063, type 2 5(2979) DEBUG: <core> [tcp_main.c:1382]: tcpconn_add(): tcpconn_add: hashes: 1522:2178:0, 4 5(2979) DEBUG: <core> [tcp_main.c:2699]: tcpconn_1st_send(): pending write on new connection 0x7fac1168f028 (-1/968 bytes written) 5(2979) DEBUG: tm [t_funcs.c:395]: t_relay_to(): SER: new transaction fwd'ed B----while when using 4.2.2 or 4.4 1(791) DEBUG: <core> [tcp_main.c:1818]: tcp_send(): tcp_send: no open tcp connection found, opening new one 1(791) DEBUG: <core> [ip_addr.c:243]: print_ip(): tcpconn_new: new tcp connection: 79.170.68.171 1(791) DEBUG: <core> [tcp_main.c:1073]: tcpconn_new(): tcpconn_new: on port 5063, type 2 1(791) DEBUG: <core> [tcp_main.c:1382]: tcpconn_add(): tcpconn_add: hashes: 1522:3421:0, 4 1(791) INFO: <core> [tcp_main.c:2753]: tcpconn_1st_send(): quick connect for 0x7f880540f758 1(791) DEBUG: tm [t_funcs.c:394]: t_relay_to(): SER: new transaction fwd'ed the difference between A and B is that in B i use dialog flags to do the t_relay_to_tcp for the indialog requests (and not in A), and in A i use the advertised IP in the listen addresses since kamailio is behind a NAT, while B machine scenario has public IPs. could those 2 things explain the ebhaviour difference? is there anything abnormal in the case B? thanks a lot and regards david escartin

3 5

← Newer
1
2
3
4
5
6
7
8
...
12
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users January 2016