[SR-Users] Kamailio IMS deployment

sainath.ellendula at wipro.com sainath.ellendula at wipro.com
Mon Feb 8 11:08:28 CET 2016


Hi Franz,

Thank you for response.

Modified everything as suggested, Still getting the same issue.

Please find the tail  -f /var/log/syslog It looks good. Ping is happening.

root at server:/etc/init.d# tail -f /var/log/syslog
Feb  8 14:39:57 server named[1615]: zone 127.in-addr.arpa/IN: loaded serial 1
Feb  8 14:39:57 server named[1615]: zone net1.test/IN: loaded serial 2010081401
Feb  8 14:39:57 server named[1615]: zone localhost/IN: loaded serial 2
Feb  8 14:39:57 server named[1615]: zone 255.in-addr.arpa/IN: loaded serial 1
Feb  8 14:39:57 server named[1615]: zone net2.test/IN: loaded serial 2010081401
Feb  8 14:39:57 server named[1615]: all zones loaded
Feb  8 14:39:57 server named[1615]: running
Feb  8 14:39:57 server named[1615]: zone 0.0.10.in-addr.arpa/IN: sending notifies (serial 2010081401)
Feb  8 14:39:57 server named[1615]: zone net1.test/IN: sending notifies (serial 2010081401)
Feb  8 14:39:57 server named[1615]: zone net2.test/IN: sending notifies (serial 2010081401)

My files:

vi /opt/OpenIMSCore/FHoSS/deploy/DiameterPeerHSS.xml

<?xml version="1.0" encoding="UTF-8"?>
<!-- HSS Server config -->
<DiameterPeer
        FQDN="hss.net1.test"
        Realm="net1.test"
        Vendor_Id="10415"
        Product_Name="JavaDiameterPeer"
        AcceptUnknownPeers="1"
        DropUnknownOnDisconnect="1"
        Tc="30"
        Workers="4"
        QueueLength="32"
>
        <Peer FQDN="icscf.net1.test" Realm="net1.test" port="3869" />
        <Peer FQDN="scscf.net1.test" Realm="net1.test" port="3870" />

        <Acceptor port="3868" bind="10.0.0.9" />

        <Auth id="16777216" vendor="10415"/><!-- 3GPP Cx -->
        <Auth id="16777216" vendor="4491"/><!-- CableLabs Cx -->
        <Auth id="16777216" vendor="13019"/><!-- ETSI/TISPAN Cx -->
        <Auth id="16777216" vendor="0"/><!-- ETSI/TISPAN Cx -->
        <Auth id="16777217" vendor="10415"/><!-- 3GPP Sh -->
        <Auth id="16777221" vendor="10415"/>

</DiameterPeer>

Vi /usr/local/etc/Kamailio/ icscf.xml

<?xml version="1.0" encoding="UTF-8"?>
<DiameterPeer
        FQDN="icscf.net1.test"
        Realm="net1.test"
        Vendor_Id="10415"
        Product_Name="CDiameterPeer"
        AcceptUnknownPeers="1"
        DropUnknownOnDisconnect="1"
        Tc="30"
        Workers="4"
        QueueLength="8"
        TransactionTimeout="5"
        SessionsHashSize="128"
        DefaultAuthSessionTimeout="3600"
        MaxAuthSessionTimeout="3600"
>

        <Peer FQDN="hss.net1.test" Realm="net1.test" port="3868"/>

        <Acceptor port="3869" bind="10.0.0.11"/>

        <Auth id="16777216" vendor="10415"/> <!--3GPP CxDX -->

        <DefaultRoute FQDN="hss.net1.test" metric="10"/>
</DiameterPeer>

Vi /usr/local/etc/Kamailio/ scscf.xml

<?xml version="1.0" encoding="UTF-8"?>
<DiameterPeer
        FQDN="scscf.net1.test"
        Realm="net1.test"
        Vendor_Id="10415"
        Product_Name="CDiameterPeer"
        AcceptUnknownPeers="1"
        DropUnknownOnDisconnect="1"
        Tc="30"
        Workers="4"
        QueueLength="8"
        TransactionTimeout="5"
        SessionsHashSize="128"
        DefaultAuthSessionTimeout="3600"
        MaxAuthSessionTimeout="3600"
>

        <Peer FQDN="hss.net1.test" Realm="net1.test" port="3868"/>

        <Acceptor port="3870" bind="10.0.0.12"/>

        <Auth id="16777216" vendor="10415"/><!-- 3GPP Cx -->
        <Auth id="4" vendor="10415"/> <!--3GPP Ro -->

        <DefaultRoute FQDN="hss.net1.test" metric="10"/>


</DiameterPeer>

vi /etc/resolv.conf

domain net1.test
search net1.test
nameserver server.net1.test

vi /etc/bind/named_conf.options

options {
        directory "/var/cache/bind";

        // If there is a firewall between you and nameservers you want
        // to talk to, you may need to fix the firewall to allow multiple
        // ports to talk.  See http://www.kb.cert.org/vuls/id/800113

        // If your ISP provided one or more IP addresses for stable
        // nameservers, you probably want to use them as forwarders.
        // Uncomment the following block, and insert the addresses replacing
        // the all-0's placeholder.

        forwarders {
        //0.0.0.0;
        10.0.0.9; 10.0.0.10; 10.0.0.11; 10.0.0.12;      // my home router
        //      195.202.138.3; 195.202.128.3;   // DNS-servers kabelsignal
        //      10.127.0.11; 10.128.0.12;                               // DNS-servers FH Technikum-Wien - must be used within FH intranet
        };

        //========================================================================
        // If BIND logs error messages about the root key being expired,
        // you will need to update your keys.  See https://www.isc.org/bind-keys
        //========================================================================
        dnssec-validation no;

        auth-nxdomain no;    # conform to RFC1035
        listen-on-v6 { any; };
};

Please guide me any more changes has to be done.. I could not find the path for log file(syslog.conf) to increase the debug level.

Thanks in advance!!

Regards,
Sainath


From: Franz Edler [mailto:franz.edler at technikum-wien.at]
Sent: Thursday, February 4, 2016 10:48 PM
To: Sainath Ellendula (NEP) <sainath.ellendula at wipro.com>
Cc: basitstar at hotmail.com; sr-users at lists.sip-router.org
Subject: RE: Re:[SR-Users] Kamailio IMS deployment

You did not modify the reverse zone-file, just to be consistent.
I see you have assigned 10.0.0.10 to P-CSCF. This address I used for my notebook (VMware host).
After your zone-file modifications you should check it e.g. with ping.

If that does not solve the issue (I assume) then increase the debug level to see what happens in peerstatemachine.c:635.
You can write it in a logfile and send.

BR

From: sainath.ellendula at wipro.com<mailto:sainath.ellendula at wipro.com> [mailto:sainath.ellendula at wipro.com]
Sent: Wednesday, February 3, 2016 12:43 PM
To: franz.edler at technikum-wien.at<mailto:franz.edler at technikum-wien.at>
Cc: basitstar at hotmail.com<mailto:basitstar at hotmail.com>; sr-users at lists.sip-router.org<mailto:sr-users at lists.sip-router.org>
Subject: RE: Re:[SR-Users] Kamailio IMS deployment

Hi Franz,

Sorry for troubling you again, But thank you so much for your response.

I have modified as suggested, still getting same error.

Please find attached files and suggest me any more changes has to be done.

Thanks in advance!!

Regards,
Sainath

From: Franz Edler [mailto:franz.edler at technikum-wien.at]
Sent: Monday, February 1, 2016 11:59 PM
To: Sainath Ellendula (NEP) <sainath.ellendula at wipro.com<mailto:sainath.ellendula at wipro.com>>
Cc: basitstar at hotmail.com<mailto:basitstar at hotmail.com>; sr-users at lists.sip-router.org<mailto:sr-users at lists.sip-router.org>
Subject: RE: Re:[SR-Users] Kamailio IMS deployment

Hi Sainath,

it is always good to read the error-messages .


The ERROR de.fhg.fokus.diameter.DiameterPeer.peer.StateMachine - I_Snd_Conn_Req StateMachine: Peer icscf.net1.test:3869 not responding to connection attempt
shows that there is no connectivity towards iscsf and scscf. This is typically the case when you start HSS and icscf and scscf are not already running.
This errors you will always have because either you start HSS first (see error above) or you start icscf and scscf first. Then you will get similar error messages from icscf and scscf.


The ERROR: cdp [peerstatemachine.c:635]: I_Snd_CER(): I_Snd_CER(): Error on finding local host address > Socket operation on non-socket
shows that the local host address cannot be found. Look into the xml-files that define the parameters for the  diameter connection (icscf.xml and scscf.xml).
Both files define the FQDN of the diameter peer. I guess you did not modify the DNS file when you have changed the IP-address of I-CSCF and S-CSCF.
Modify the zone-files accordingly. Then I expect that the error will disappear.

The firs warning WARN  org.apache.catalina.connector.MapperListener - registerEngine Unknown default host: 10.0.0.9
I do not know, what it means. It is not critical. I live with that since the beginning.
Maybe you can explain it to me sometimes . I am not a Tomcat expert.

BR Franz


.
From: sainath.ellendula at wipro.com<mailto:sainath.ellendula at wipro.com> [mailto:sainath.ellendula at wipro.com]
Sent: Monday, February 1, 2016 8:22 AM
To: franz.edler at technikum-wien.at<mailto:franz.edler at technikum-wien.at>
Cc: basitstar at hotmail.com<mailto:basitstar at hotmail.com>; sr-users at lists.sip-router.org<mailto:sr-users at lists.sip-router.org>
Subject: RE: Re:[SR-Users] Kamailio IMS deployment


Hi Franz,



Thank you so much for your response.



As suggested modified changes and don't observe connection refused error.



After modification few more errors observed. Detailed errors as below.



10.0.0.9



/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-02-01 12:09:28,371 INFO  de.fhg.fokus.hss.main.TomcatServer - startTomcat Tomcat-Server is started.

2016-02-01 12:09:29,301 WARN  org.apache.catalina.connector.MapperListener - registerEngine Unknown default host: 10.0.0.9

2016-02-01 12:09:30,294 INFO  de.fhg.fokus.hss.web.servlet.ResponseFilter - init Response Filter Initialisation!

2016-02-01 12:09:31,251 INFO  de.fhg.fokus.hss.main.TomcatServer - startTomcat WebConsole of FHoSS was started !

2016-02-01 12:09:34,813 WARN  org.hibernate.impl.SessionFactoryObjectFactory - addInstance InitialContext did not implement EventContext

2016-02-01 12:09:34,847 INFO  de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - <init> Bean style constructor called, don't forget to configure!

2016-02-01 12:09:34,851 INFO  de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - configure FQDN: hss.net1.test

2016-02-01 12:09:34,852 INFO  de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - configure Realm: net1.test

2016-02-01 12:09:34,853 INFO  de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - configure Vendor_ID : 10415

2016-02-01 12:09:34,854 INFO  de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - configure Product Name: JavaDiameterPeer

2016-02-01 12:09:34,854 INFO  de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - configure AcceptUnknwonPeers: true

2016-02-01 12:09:34,855 INFO  de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - configure DropUnknownOnDisconnect: true

2016-02-01 12:09:34,864 INFO  de.fhg.fokus.hss.main.HSSContainer - waitForExit

Type "exit" to stop FHoSS!

2016-02-01 12:09:34,873 ERROR de.fhg.fokus.diameter.DiameterPeer.peer.StateMachine - I_Snd_Conn_Req StateMachine: Peer icscf.net1.test:3869 not responding to connection attempt

2016-02-01 12:09:34,876 ERROR de.fhg.fokus.diameter.DiameterPeer.peer.StateMachine - I_Snd_Conn_Req StateMachine: Peer scscf.net1.test:3870 not responding to connection attempt



10.0.0.10



root at server:~# kamailio -f /usr/local/etc/kamailio/kamailio-pcscf.cfg

loading modules under config path: /usr/local/lib64/kamailio/modules/

0(1856) 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(1856) INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob

0(1856) INFO: rr [rr_mod.c:174]: mod_init(): outbound module not available

0(1856) INFO: ims_usrloc_pcscf [hslot.c:62]: ul_init_locks(): locks array size 512

0(1856) INFO: <core> [udp_server.c:150]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992

0(1856) INFO: <core> [udp_server.c:200]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984

0(1856) WARNING: ims_usrloc_pcscf [usrloc_db.c:59]: connect_db(): DB connection already open... continuing

0(1856) INFO: <script>:  [REGISTER] from [sip:alice at net1.test] to [sip:alice at net1.test]

0(1856) ERROR: <script>: REGISTER (sip:alice at net1.test (10.0.0.8:55859) to sip:alice at net1.test, aaeacddd-376e-4a63-5745-2757d1b9a29d)





10.0.0.11



9(1870) WARNING: cdp [tcp_accept.c:123]: create_socket(): create_socket(): Trying to open/bind/listen on 10.0.0.11 port 3869

9(1870) WARNING: cdp [tcp_accept.c:148]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.0.0.11 port 3869

9(1870) INFO: cdp [acceptor.c:96]: acceptor_process(): Acceptor opened sockets. Entering accept loop ...

10(1871) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test  State 0

10(1871) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test

10(1871) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868

10(1871) INFO: cdp [receiver.c:932]: peer_connect(): peer_connect(): Peer hss.net1.test:3868 connected

8(1869) ERROR: cdp [peerstatemachine.c:635]: I_Snd_CER(): I_Snd_CER(): Error on finding local host address > Socket operation on non-socket

10(1871) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test  State 6

10(1871) 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.0.0.12



9(1883) WARNING: cdp [tcp_accept.c:123]: create_socket(): create_socket(): Trying to open/bind/listen on 10.0.0.12 port 3870

9(1883) WARNING: cdp [tcp_accept.c:148]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.0.0.12 port 3870

9(1883) INFO: cdp [acceptor.c:96]: acceptor_process(): Acceptor opened sockets. Entering accept loop ...

7(1881) INFO: cdp [receiver.c:445]: receiver_process(): receiver_process(): [] Receiver process doing init on new process...

7(1881) INFO: cdp [receiver.c:450]: receiver_process(): receiver_process(): [] Receiver process starting up...

10(1884) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test  State 0

10(1884) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test

10(1884) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868

10(1884) INFO: cdp [receiver.c:932]: peer_connect(): peer_connect(): Peer hss.net1.test:3868 connected

8(1882) ERROR: cdp [peerstatemachine.c:635]: I_Snd_CER(): I_Snd_CER(): Error on finding local host address > Socket operation on non-socket

10(1884) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test  State 6

10(1884) 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(1884) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test  State 6



Could you please guide me here. Any suggestions would be very helpful.



Thanks in advance!!



Regards,

Sainath


-----Original Message-----
From: Franz Edler [mailto:franz.edler at technikum-wien.at]
Sent: Saturday, January 30, 2016 1:27 PM
To: Sainath Ellendula (WT01 - NEP) <sainath.ellendula at wipro.com<mailto:sainath.ellendula at wipro.com>>; basitstar at hotmail.com<mailto:basitstar at hotmail.com>; sr-users at lists.sip-router.org<mailto:sr-users at lists.sip-router.org>
Subject: RE: [SR-Users] Kamailio IMS deployment

Hi,

> As suggested, modified the changes in icscf.xml and scscf.xml files, PFA
> modified files.
>
> Still getting few errors ....

Now it seems to be clear to me where the problem might come from:

I have restricted access to mysql server to address 10.0.0.9 only.
You have to change the bind-address statement in /etc/mysql.cnf accordingly.
See: http://dev.mysql.com/doc/refman/5.7/en/server-options.html#option_mysqld_bind-address

Change the address to "*" or to 0.0.0.0.

BR Franz





_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users at lists.sip-router.org<mailto:sr-users at 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>
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>
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20160208/6d81372a/attachment.html>


More information about the sr-users mailing list