Hi All, Does any one has VM image of Kamailio IMS , please share it. Thank you so much in advance Regards, kranti On Dec 2, 2015 3:16 PM, "Ramya Y" <y.ramya146(a)gmail.com> wrote:

Thanks a lot Franz ! Regards, Ramyasri On Wed, Jan 6, 2016 at 8:39 PM, Franz Edler <franz.edler(a)technikum-wien.at> wrote:

Hi Franz, could you please provide me small description about how to start all nodes(HSS,P/I/S-CSCF and basic call. it would be more helpful to me. And also i was unable to find ./p,i,scscf.sh files under root as described in the log file but i can see only hss.sh . Thanks in advance! Regards, Ramya. On Thu, Jan 7, 2016 at 2:45 PM, Daniel-Constantin Mierla <miconda(a)gmail.com> wrote:

Hi, the p-, i- and scscf.sh files are not required, because these are from the origin OpenIMScore which I installed in an intermediate step (which led to an step4-image with origin OpenIMScore). Unfortunately the log-file which I provided yesterday also included this part. I now have updated the log-file (attached) and eliminated this part (step4) which is not relevant for IMS on Kamailio. Now, how to start the platform: HSS: see line 591 – 596 P-CSCF: line 609 kamailio -f /usr/local/etc/kamailio/kamailio-pcscf.cfg I-CSCF: line 614 kamailio -f /usr/local/etc/kamailio/kamailio-icscf.cfg S-CSCF: line 621 kamailio -f /usr/local/etc/kamailio/kamailio-scscf.cfg Additional info: I configured for testing the kamailio -instances to run in foreground. Therefore you need at least 4 console windows (HSS, P-, I- and S-CSCF). For starting tcpdump for trace-file you need a 5th console. I prefer to use “screen” command to generate the different screens. I hope that helps. For the basic call I used two IMS clients (“Mercuro Silver” and “Boghe”) running on the Windows host. The clients are configured as Alice and Bob with authentication AKAv1-MD5. Authentication data are in HSS preconfigured. If you do not have IMS clients you can start with pure SIP-clients (using digest authentication MD5 instead of AKAv1-MD5). But for that you have to change the REG_AUTH_DEFAULT_ALG parameter in scscf.cfg accordingly. And probably also the default authentication scheme in HSS (USER IDENTITIES -> Private Identity). I did not test this. But in case of problems you should provide a tracefile produced with “tcpdump -i any -s 3000 -w /var/tmp/trace.pcap not port 22 and not port 3306”. Good luck. Franz From: Ramya Y [mailto:y.ramya146@gmail.com] Sent: Thursday, January 7, 2016 3:13 PM To: Daniel-Constantin Mierla &lt;miconda(a)gmail.com&gt;om>; Kamailio (SER) - Users Mailing List &lt;sr-users(a)lists.sip-router.org&gt; Cc: franz.edler(a)technikum-wien.at Subject: Re: [SR-Users] Kamailio IMS deployment Hi Franz, could you please provide me small description about how to start all nodes(HSS,P/I/S-CSCF and basic call. it would be more helpful to me. And also i was unable to find ./p,i,scscf.sh files under root as described in the log file but i can see only hss.sh . Thanks in advance! Regards, Ramya. On Thu, Jan 7, 2016 at 2:45 PM, Daniel-Constantin Mierla &lt;miconda(a)gmail.com <mailto:miconda@gmail.com> > wrote: Hello, thanks for sharing these, I expect to help a lot the people starting to build an IMS core with Kamailio. If you can send me a short description of the IMS network you built with these configs, I would like to post a news article on kamailio.org <http://kamailio.org> to make it more visible. Cheers, Daniel On 06/01/16 16:09, Franz Edler wrote: Hi Ramya, I now succeeded to configure a stripped down version of Kamilio IMS. Here is my log-file and the config-files used: https://www.dropbox.com/s/ehkzi9pbhlp7njc/Kamailio-IMS%20config-files.zip?d… As you can see in the log-file I used several steps to configure the IMS platform. The last step (step 5) contains basic Kamailio and basic IMScore. For the configuration of the IMS core I disabled all additional functions (NAT, dispatcher, SBC …etc) which are not necessary for the core function. I kept the configuration scheme of the original OpenIMSCore using same IP-address but different ports for P-CSCF (4060), I-CSCF (5060) and S-CSCF (6060). I hope I have included all relevant files. And here is the VMware-image of the last step 5: https://www.dropbox.com/s/pwwx009hiigt27v/Debian_8.2-step5-basicKamailio%26… For the VMware configuration I used the following IP addresses: 10.0.0.9 the Kamailio guest system 10.0.0.10 the host system (Windows Notebook) I hope that fits for you. In case of any questions you may ask. BR Franz From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Ramya Y Sent: Wednesday, December 2, 2015 10:46 AM To: sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org> Subject: [SR-Users] Kamailio IMS deployment Hi, I am newbie to kamailio world and we would like to deploy Kamailio based IMS platform. Can any body share the link or Step by step procedure(user Guide) to deploy Kamailio IMS. Regards, Ramya _______________________________________________ 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 -- 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 _______________________________________________ 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

Hi Daniel, Yes, I think so. IMS is a complex system and I used it for a long time for education of myself and later of my students (University of Applied Sciences in Vienna). As OpenIMSCore has now been ported to Kamailio it was now the first time I got some time to configure the core function of IMS in Kamailio. Next steps will be to investigate in the additional functions provided by Kamailio and already integrated by Carsten and others (SBC, dispatcher, etc.). The final plan for me is to understand these add-ons and to provide a documentation (with the help of students). BR Franz From: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Sent: Thursday, January 7, 2016 10:16 AM To: franz.edler(a)technikum-wien.at; Kamailio (SER) - Users Mailing List &lt;sr-users(a)lists.sip-router.org&gt; Subject: Re: [SR-Users] Kamailio IMS deployment Hello, thanks for sharing these, I expect to help a lot the people starting to build an IMS core with Kamailio. If you can send me a short description of the IMS network you built with these configs, I would like to post a news article on kamailio.org to make it more visible. Cheers, Daniel On 06/01/16 16:09, Franz Edler wrote: Hi Ramya, I now succeeded to configure a stripped down version of Kamilio IMS. Here is my log-file and the config-files used: https://www.dropbox.com/s/ehkzi9pbhlp7njc/Kamailio-IMS%20config-files.zip?dl =0 As you can see in the log-file I used several steps to configure the IMS platform. The last step (step 5) contains basic Kamailio and basic IMScore. For the configuration of the IMS core I disabled all additional functions (NAT, dispatcher, SBC .etc) which are not necessary for the core function. I kept the configuration scheme of the original OpenIMSCore using same IP-address but different ports for P-CSCF (4060), I-CSCF (5060) and S-CSCF (6060). I hope I have included all relevant files. And here is the VMware-image of the last step 5: https://www.dropbox.com/s/pwwx009hiigt27v/Debian_8.2-step5-basicKamailio%26b asicIMScore.zip?dl=0 For the VMware configuration I used the following IP addresses: 10.0.0.9 the Kamailio guest system 10.0.0.10 the host system (Windows Notebook) I hope that fits for you. In case of any questions you may ask. BR Franz From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Ramya Y Sent: Wednesday, December 2, 2015 10:46 AM To: sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org> Subject: [SR-Users] Kamailio IMS deployment Hi, I am newbie to kamailio world and we would like to deploy Kamailio based IMS platform. Can any body share the link or Step by step procedure(user Guide) to deploy Kamailio IMS. Regards, Ramya _______________________________________________ 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 -- 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

Hello, thanks -- one more thing, though: can you export the document as pdf to be able to view it easy on different OSes as well as browsers? Cheers, Daniel On 08/01/16 17:47, Franz Edler wrote: -- 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

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-tp143593p14… Sent from the Users mailing list archive at Nabble.com.

Hi Kranti, yes, I understand. My first approach was to use the same configuration as used by OpenIMSCore. It is of course possible to setup P-, I- and S-CSCF with different IP-addresses on different machines or even on one machine using virtual interfaces. Reconfiguring is an interesting exercise which I cannot do due to lack of time. A quick hint: - Just look into the log-file of ma installation and check where the physical address has been used during configuration. - And of course you must also adapt the zone-file od the DNS-server. BR Franz From: Kranti Kumar [mailto:krantikumara@gmail.com] Sent: Monday, January 11, 2016 6:27 PM To: franz.edler(a)technikum-wien.at; Kamailio (SER) - Users Mailing List &lt;sr-users(a)lists.sip-router.org&gt; Cc: Ramya Y &lt;y.ramya146(a)gmail.com&gt;om>; Daniel-Constantin Mierla &lt;miconda(a)gmail.com&gt; Subject: Re: [SR-Users] Kamailio IMS deployment Hi Franz, Thank you very much for your support. Now we are able to make a call between two IMS clients (Boghe). Thank you so much. We are little confusing by seeing Wireshark traces as every node run on the same IP address. We would like to run CSCF (P,S,I), HSS on different IP addresses for better understanding. Is it possible ? If it is possible where I need to do modifications. We have already tried but Failed. Could you please help us. Thank you so much in advance. Regards, -kranti On Thu, Jan 7, 2016 at 11:22 PM, Franz Edler &lt;franz.edler(a)technikum-wien.at <mailto:franz.edler@technikum-wien.at> > wrote: Hi, the p-, i- and scscf.sh files are not required, because these are from the origin OpenIMScore which I installed in an intermediate step (which led to an step4-image with origin OpenIMScore). Unfortunately the log-file which I provided yesterday also included this part. I now have updated the log-file (attached) and eliminated this part (step4) which is not relevant for IMS on Kamailio. Now, how to start the platform: HSS: see line 591 – 596 P-CSCF: line 609 kamailio -f /usr/local/etc/kamailio/kamailio-pcscf.cfg I-CSCF: line 614 kamailio -f /usr/local/etc/kamailio/kamailio-icscf.cfg S-CSCF: line 621 kamailio -f /usr/local/etc/kamailio/kamailio-scscf.cfg Additional info: I configured for testing the kamailio -instances to run in foreground. Therefore you need at least 4 console windows (HSS, P-, I- and S-CSCF). For starting tcpdump for trace-file you need a 5th console. I prefer to use “screen” command to generate the different screens. I hope that helps. For the basic call I used two IMS clients (“Mercuro Silver” and “Boghe”) running on the Windows host. The clients are configured as Alice and Bob with authentication AKAv1-MD5. Authentication data are in HSS preconfigured. If you do not have IMS clients you can start with pure SIP-clients (using digest authentication MD5 instead of AKAv1-MD5). But for that you have to change the REG_AUTH_DEFAULT_ALG parameter in scscf.cfg accordingly. And probably also the default authentication scheme in HSS (USER IDENTITIES -> Private Identity). I did not test this. But in case of problems you should provide a tracefile produced with “tcpdump -i any -s 3000 -w /var/tmp/trace.pcap not port 22 and not port 3306”. Good luck. Franz From: Ramya Y [mailto:y.ramya146@gmail.com <mailto:y.ramya146@gmail.com> ] Sent: Thursday, January 7, 2016 3:13 PM To: Daniel-Constantin Mierla &lt;miconda(a)gmail.com <mailto:miconda@gmail.com> >; Kamailio (SER) - Users Mailing List &lt;sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org> > Cc: franz.edler(a)technikum-wien.at <mailto:franz.edler@technikum-wien.at> Subject: Re: [SR-Users] Kamailio IMS deployment Hi Franz, could you please provide me small description about how to start all nodes(HSS,P/I/S-CSCF and basic call. it would be more helpful to me. And also i was unable to find ./p,i,scscf.sh files under root as described in the log file but i can see only hss.sh . Thanks in advance! Regards, Ramya. On Thu, Jan 7, 2016 at 2:45 PM, Daniel-Constantin Mierla &lt;miconda(a)gmail.com <mailto:miconda@gmail.com> > wrote: Hello, thanks for sharing these, I expect to help a lot the people starting to build an IMS core with Kamailio. If you can send me a short description of the IMS network you built with these configs, I would like to post a news article on kamailio.org <http://kamailio.org> to make it more visible. Cheers, Daniel On 06/01/16 16:09, Franz Edler wrote: Hi Ramya, I now succeeded to configure a stripped down version of Kamilio IMS. Here is my log-file and the config-files used: https://www.dropbox.com/s/ehkzi9pbhlp7njc/Kamailio-IMS%20config-files.zip?d… As you can see in the log-file I used several steps to configure the IMS platform. The last step (step 5) contains basic Kamailio and basic IMScore. For the configuration of the IMS core I disabled all additional functions (NAT, dispatcher, SBC …etc) which are not necessary for the core function. I kept the configuration scheme of the original OpenIMSCore using same IP-address but different ports for P-CSCF (4060), I-CSCF (5060) and S-CSCF (6060). I hope I have included all relevant files. And here is the VMware-image of the last step 5: https://www.dropbox.com/s/pwwx009hiigt27v/Debian_8.2-step5-basicKamailio%26… For the VMware configuration I used the following IP addresses: 10.0.0.9 the Kamailio guest system 10.0.0.10 the host system (Windows Notebook) I hope that fits for you. In case of any questions you may ask. BR Franz From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Ramya Y Sent: Wednesday, December 2, 2015 10:46 AM To: sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org> Subject: [SR-Users] Kamailio IMS deployment Hi, I am newbie to kamailio world and we would like to deploy Kamailio based IMS platform. Can any body share the link or Step by step procedure(user Guide) to deploy Kamailio IMS. Regards, Ramya _______________________________________________ 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 -- 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 _______________________________________________ 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

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 &lt;franz.edler(a)technikum-wien.at&gt; wrote:

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 -- 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 &lt;franz.edler(a)technikum-wien.at&gt; wrote:

Hello Franz, it took me a while due to other tasks around, but finally managed to make the news article based on your document. - https://www.kamailio.org/w/2016/02/kamailio-ims-getting-started-box/ Many thanks again for helping the community, your activity was quite impressive lately for those asking about Kamailio and IMS. Cheers, Daniel On 08/01/16 21:17, Franz Edler wrote: -- 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