date:20171220

Re: [SR-Users] Multiple Kamailio Servers + Location Table

2017-12-20 Thread Daniel W. Graham

Yes they are all different.

-dan

On Dec 20, 2017, at 4:32 PM, Victor Seva 
> 
wrote:

2017-12-20 17:39 GMT+01:00 Daniel W. Graham 
>:
Only the active server has active IP, clients cannot connect to the ip of 
standbys.

is server_id value set and different on all servers config?
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Multiple Kamailio Servers + Location Table

2017-12-20 Thread Victor Seva

2017-12-20 17:39 GMT+01:00 Daniel W. Graham :

> Only the active server has active IP, clients cannot connect to the ip of
> standbys.
>
>
is server_id value set and different on all servers config?
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio-IMS VM image issue

2017-12-20 Thread Kranti Kumar

Hi,
We are facing below errors while running P-CSCF module. We are able to run
HSS and I-CSCF modules successfully.

ERROR:  [sr_module.c:962]: init_mod(): Error while initializing
module ims_usrloc_pcscf
(/usr/local/lib64/kamailio/modules/ims_usrloc_pcscf.so)

-bash: syntax error near unexpected token `('
0(1337) ERROR: db_mysql [km_my_con.c:124]: db_mysql_new_connection():
driver error: Access denied for user 'pcscf'@'pcscf.net1.test' (using
password: YES)
 0(1337) ERROR:  [db.c:318]: db_do_init2(): could not add connection
to the pool 0(1337) ERROR: ims_usrloc_pcscf [usrloc_db.c:79]: init_db():
unable to connect to the database
 0(1337) ERROR: ims_usrloc_pcscf [ul_mod.c:203]: mod_init(): Error
initializing db connection
 0(1337) ERROR:  [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


Could any one please help us to resolve this issue. We are trying hard to
troubleshoot the issue but no clew.

Regards,
-kranti

On Wed, Dec 20, 2017 at 6:43 PM, ponnam.g...@wipro.com <
ponnam.g...@wipro.com> wrote:

> Hi Franz,
>
>
> This error is now resolved, we had to modify IP in
> DiameterPeerHss.xml after that error is not seen.
>
> hss.sh script is running without any errors, could see following message
>
>
> de.fhg.fokus.hss.main.TomcatServer - startTomcat WebConsole of FHoSS was
> started !
>
>
> ICSCF is also working fine.
>
> however still we are facing couple of issues
>
>
>1. we are unable to access console (10.200..8.171:8080), not sure what
>could be the issue here.
>2. could not start PCSCF , following are the error messages
>
>
>  0(1337) ERROR: db_mysql [km_my_con.c:124]: db_mysql_new_connection():
> driver error: Access denied for user 'pcscf'@'pcscf.net1.test' (using
> password: YES)
>  0(1337) ERROR:  [db.c:318]: db_do_init2(): could not add connection
> to the pool 0(1337) ERROR: ims_usrloc_pcscf [usrloc_db.c:79]: init_db():
> unable to connect to the database
>  0(1337) ERROR: ims_usrloc_pcscf [ul_mod.c:203]: mod_init(): Error
> initializing db connection
>  0(1337) ERROR:  [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
>
>
>
> could you please help?
>
>
>
> Regards,
>
> Raghu
>
>
>
> --
> *From:* Ponnam Raghavender Goud (NEPC)
> *Sent:* Wednesday, December 20, 2017 4:19:52 PM
> *To:* Franz Edler; 'Kranti Kumar'; 'Kamailio (SER) - Users Mailing List'
> *Cc:* 'raghavender goud'
> *Subject:* Re: Kamailio-IMS VM image issue
>
>
> HI Franz,
>
>
> I have checked port status using following command and it returned no
> output
>
>
> root@server:~# netstat -lptu | grep -i 8080
> root@server:~# netstat -lptu
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address   Foreign Address
> State   PID/Program name
> tcp0  0 *:sunrpc*:*
> LISTEN  401/rpcbind
> tcp0  0 *:55285 *:*
> LISTEN  410/rpc.statd
> tcp0  0 *:ssh   *:*
> LISTEN  427/sshd
> tcp0  0 localhost:smtp  *:*
> LISTEN  1244/exim4
> tcp0  0 localhost:6010  *:*
> LISTEN  1453/1
> tcp0  0 *:mysql *:*
> LISTEN  891/mysqld
> tcp6   0  0 [::]:sunrpc [::]:*
> LISTEN  401/rpcbind
> tcp6   0  0 [::]:ssh[::]:*
> LISTEN  427/sshd
> tcp6   0  0 ::1:smtp[::]:*
> LISTEN  1244/exim4
> tcp6   0  0 ::1:6010[::]:*
> LISTEN  1453/1
> tcp6   0  0 [::]:35432  [::]:*
> LISTEN  410/rpc.statd
> udp0  0 *:1000  *:*
> 401/rpcbind
> udp0  0 localhost:1010  *:*
> 410/rpc.statd
> udp0  0 *:bootpc*:*
> 368/dhclient
> udp0  0 *:sunrpc*:*
> 401/rpcbind
> udp0  0 server.net1.test:ntp*:*
> 946/ntpd
> udp0  0 localhost:ntp   *:*
> 946/ntpd
> udp0  0 *:ntp   *:*
> 946/ntpd
> udp0  0 *:53944 *:*
> 410/rpc.statd
> udp0  0 *:32019 *:*
> 368/dhclient
> udp6   0  0 [::]:1000   [::]:*
> 401/rpcbind
> udp6   0  0 [::]:15924  [::]:*
> 368/dhclient
> udp6   0  0 [::]:sunrpc [::]:*
> 401/rpcbind
> udp6   0  0 fe80::f816:3eff:fe2:ntp [::]:*
> 946/ntpd
> udp6   0  0 ::1:ntp [::]:*
> 946/ntpd
> udp6   0  0 [::]:ntp[::]:*
> 946/ntpd
> udp6   0  0 [::]:44928  [::]:*
> 410/rpc.statd
>
>
>
>
> Regards,
>
> Raghu
> --
> *From:* Franz Edler 
> *Sent:* Wednesday,

Re: [SR-Users] Multiple Kamailio Servers + Location Table

2017-12-20 Thread Daniel W. Graham

Only the active server has active IP, clients cannot connect to the ip of 
standbys.

-dan

-Original Message-
From: sr-users [mailto:sr-users-boun...@lists.kamailio.org] On Behalf Of Sergey 
Okhapkin
Sent: Wednesday, December 20, 2017 10:41 AM
To: Kamailio (SER) - Users Mailing List 
Subject: Re: [SR-Users] Multiple Kamailio Servers + Location Table

Is it possible that clients whose records disappear roam between servers? I.e. 
register with the active server, but then registers with a standby server while 
the active one is still up and running?

On Wednesday, December 20, 2017 10:34:42 AM EST Daniel W. Graham wrote:
> Yes, to your first question, most records originally written by the 
> active server disappear. Only way to restore all records to the 
> location table is taking standby servers offline and restart Kamailio 
> on active server. If a restart is not performed records wont reappear 
> in table. db_mode is 2 Database is replication is active passive.
> 
> Daniel W. Graham, CTO
> CMSInter.net LLC
> DIRECT (989) 400-4230
> 
> INTERNET | TELEPHONE | MANAGED IT
> 
> From: Daniel-Constantin Mierla [mailto:mico...@gmail.com]
> Sent: Wednesday, December 20, 2017 3:48 AM
> To: Kamailio (SER) - Users Mailing List ; 
> Daniel W. Graham  Subject: Re: [SR-Users] Multiple 
> Kamailio Servers + Location Table
> 
> 
> Hello,
> 
> On 20.12.17 06:28, Daniel W. Graham wrote:
> When multiple Kamailio servers are using the same database with 
> different server_id's (one active the rest standby in this test), 
> records disappear and are no longer tracked in location database table.
> 
> Some entries remain, but it never populates to the normal amount 
> unless only one server is using the database. I couldn't figure out 
> the proper picture of what happens based on the above ... some questions:
> 
> - only one server (the active) writes to database, with its own id 
> (other servers have different ids), after a while some records written 
> by the active server disappear?
> 
>  - is db_mode=3? If not, what value.
> 
>  - is there any replication at database layer?
> 
> Cheers,
> Daniel
> 
> 
> 
> 
> Anyone run into this before? Happened with 5.0 and is happening with 5.1.
> 
> -dan
> 
> 
> 
> 
> ___
> 
> Kamailio (SER) - Users Mailing List
> 
> sr-users@lists.kamailio.org
> 
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
> 
> 
> 
> --
> 
> Daniel-Constantin Mierla
> 
> www.twitter.com/miconda -- 
> www.linkedin.com/in/miconda
> 
> Kamailio Advanced Training - www.asipto.com
> 
> Kamailio World Conference - May 14-16, 2018 - 
> www.kamailioworld.com


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Multiple Kamailio Servers + Location Table

2017-12-20 Thread Sergey Okhapkin

Is it possible that clients whose records disappear roam between servers? I.e. 
register with the active server, but then registers with a standby server 
while the active one is still up and running?

On Wednesday, December 20, 2017 10:34:42 AM EST Daniel W. Graham wrote:
> Yes, to your first question, most records originally written by the active
> server disappear. Only way to restore all records to the location table is
> taking standby servers offline and restart Kamailio on active server. If a
> restart is not performed records wont reappear in table. db_mode is 2
> Database is replication is active passive.
> 
> Daniel W. Graham, CTO
> CMSInter.net LLC
> DIRECT (989) 400-4230
> 
> INTERNET | TELEPHONE | MANAGED IT
> 
> From: Daniel-Constantin Mierla [mailto:mico...@gmail.com]
> Sent: Wednesday, December 20, 2017 3:48 AM
> To: Kamailio (SER) - Users Mailing List ;
> Daniel W. Graham  Subject: Re: [SR-Users] Multiple
> Kamailio Servers + Location Table
> 
> 
> Hello,
> 
> On 20.12.17 06:28, Daniel W. Graham wrote:
> When multiple Kamailio servers are using the same database with different
> server_id's (one active the rest standby in this test), records disappear
> and are no longer tracked in location database table.
> 
> Some entries remain, but it never populates to the normal amount unless only
> one server is using the database. I couldn't figure out the proper picture
> of what happens based on the above ... some questions:
> 
> - only one server (the active) writes to database, with its own id (other
> servers have different ids), after a while some records written by the
> active server disappear?
> 
>  - is db_mode=3? If not, what value.
> 
>  - is there any replication at database layer?
> 
> Cheers,
> Daniel
> 
> 
> 
> 
> Anyone run into this before? Happened with 5.0 and is happening with 5.1.
> 
> -dan
> 
> 
> 
> 
> ___
> 
> Kamailio (SER) - Users Mailing List
> 
> sr-users@lists.kamailio.org
> 
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
> 
> 
> 
> --
> 
> Daniel-Constantin Mierla
> 
> www.twitter.com/miconda --
> www.linkedin.com/in/miconda
> 
> Kamailio Advanced Training - www.asipto.com
> 
> Kamailio World Conference - May 14-16, 2018 -
> www.kamailioworld.com


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Multiple Kamailio Servers + Location Table

2017-12-20 Thread Daniel W. Graham

Yes, to your first question, most records originally written by the active 
server disappear. Only way to restore all records to the location table is 
taking standby servers offline and restart Kamailio on active server. If a 
restart is not performed records wont reappear in table.
db_mode is 2
Database is replication is active passive.

Daniel W. Graham, CTO
CMSInter.net LLC
DIRECT (989) 400-4230

INTERNET | TELEPHONE | MANAGED IT

From: Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Sent: Wednesday, December 20, 2017 3:48 AM
To: Kamailio (SER) - Users Mailing List ; Daniel 
W. Graham 
Subject: Re: [SR-Users] Multiple Kamailio Servers + Location Table


Hello,

On 20.12.17 06:28, Daniel W. Graham wrote:
When multiple Kamailio servers are using the same database with different 
server_id's (one active the rest standby in this test), records disappear and 
are no longer tracked in location database table.

Some entries remain, but it never populates to the normal amount unless only 
one server is using the database.
I couldn't figure out the proper picture of what happens based on the above ... 
some questions:

- only one server (the active) writes to database, with its own id (other 
servers have different ids), after a while some records written by the active 
server disappear?

 - is db_mode=3? If not, what value.

 - is there any replication at database layer?

Cheers,
Daniel




Anyone run into this before? Happened with 5.0 and is happening with 5.1.

-dan




___

Kamailio (SER) - Users Mailing List

sr-users@lists.kamailio.org

https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users



--

Daniel-Constantin Mierla

www.twitter.com/miconda -- 
www.linkedin.com/in/miconda

Kamailio Advanced Training - www.asipto.com

Kamailio World Conference - May 14-16, 2018 - 
www.kamailioworld.com
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Dispatcher module OPTIONS and event routes: how are they handled by core?

2017-12-20 Thread Daniel-Constantin Mierla

Hello,

an workaround would be to add a custom parameter to the destination
value, like sip:1.2.3.4:5060;sid=1. Unknown parameters should be ignored
by the receiving party. Or if you have only two records with same
address, add to one ";transport=udp".

Of course, coding in C to make it easier in config would be the elegant
solution.

Cheers,
Daniel


On 20.12.17 15:32, George Diamantopoulos wrote:
> Hello Daniel,
>
> Thanks for the reply. Unfortunately I can't really use the database
> records to achieve what I want. The example in my previous message
> didn't show this, but I would like to be able to differentiate between
> the following:
>
> ++---+-+---+--+-+
> | id | setid | destination | flags | priority |
> attrs   |
> ++---+-+---+--+-+
> |  1 | 1 | sip:111.111.11.1:5060   
> | 8 |    0 | socket=udp:44.44.44.1:5060
>   |
> |  2 |    10 | sip:111.111.11.1:5060   
> | 8 |    0 | socket=udp:55.55.55.1:5060
>   |
> ++---+-+---+--+-+
>
> In this case, how can I tell which destination went down? The URI is
> the same, but the sockets differ for each id.
>
> If only $ru is available in these event routes, I can't query the
> database because $ru matches both records. If I can't access the
> socket used with a PV, is there any way to have access to *either* the
> id *or* the setid for the destination for which the event was generated?
>
> Thanks!
>
> BR,
> George
>
> On 20 December 2017 at 10:57, Daniel-Constantin Mierla
> > wrote:
>
> Hello,
>
> those event routes are executed with a so called faked request (a
> request generated internally, unrelated to the OPTIONS request
> sent to the wire), apart of request uri, the rest of values are
> not related to the dispatcher records.
>
> To get access to other attributes of dispatcher records in a
> straight way in the config, it would require C coding, Anyhow,
> even now using scripting, you can try with sql queries to database
> or rpc commands execution via jsonrpcs module and then parse the
> result using jansson module.
>
> Cheers,
> Daniel
>
>
> On 18.12.17 13:33, George Diamantopoulos wrote:
>> Hello all,
>>
>> I use the dispatcher module extensively for load balancing and
>> fail-over. My kamailio instance is multihomed, and I use the
>> "socket" attribute to determine which socket SIP messages should
>> use for each dispatcher destination, as such:
>>
>> 
>> ++---+-+---+--+-+
>> | id | setid | destination | flags | priority |
>> attrs   |
>> 
>> ++---+-+---+--+-+
>> |  1 | 0 | sip:192.168.0.1:5060    
>> | 8 |    0 | socket=udp:10.10.10.1:5060
>>   |
>> |  2 | 1 | sip:111.111.11.1:5060   
>> | 8 |    0 | socket=udp:44.44.44.1:5060
>>   |
>> |  3 | 1 | sip:222.222.22.2:5060   
>> | 8 |    0 | socket=udp:55.55.55.1:5060
>>   |
>> 
>> ++---+-+---+--+-+
>>
>> The dispatcher module uses OPTIONS to probe each destination for
>> availability. When a destination goes down or up, the respective
>> event-route is executed.
>>
>> What I need to do is to be able to "capture" the sending socket
>> used for this probing when a destination becomes unavailable or
>> available in the event-routes. The $fs variable is set, but
>> unfortunately its value does not make sense. Here's an example
>> route and the results that are printed:
>>
>> event_route[dispatcher:dst-down] {
>>     xlog("L_ERR", "Destination down: $rm $ru ($du) $ds $fs $Ru
>> $T_req($fs) $T_req($Ru)\n");
>> }
>>
>> Now say destination with id = '2' goes down. This is what I get
>> in the logs for the event_route above:
>>
>> ERROR:

Re: [SR-Users] Dispatcher module OPTIONS and event routes: how are they handled by core?

2017-12-20 Thread George Diamantopoulos

Hello Daniel,

Thanks for the reply. Unfortunately I can't really use the database records
to achieve what I want. The example in my previous message didn't show
this, but I would like to be able to differentiate between the following:

++---+-+---+--+-
+
| id | setid | destination | flags | priority |
attrs   |
++---+-+---+--+-
+
|  1 | 1 | sip:111.111.11.1:5060   | 8 |0 | socket=udp:
44.44.44.1:5060  |
|  2 |10 | sip:111.111.11.1:5060   | 8 |0 | socket=udp:
55.55.55.1:5060  |
++---+-+---+--+-
+

In this case, how can I tell which destination went down? The URI is the
same, but the sockets differ for each id.

If only $ru is available in these event routes, I can't query the database
because $ru matches both records. If I can't access the socket used with a
PV, is there any way to have access to *either* the id *or* the setid for
the destination for which the event was generated?

Thanks!

BR,
George

On 20 December 2017 at 10:57, Daniel-Constantin Mierla 
wrote:

> Hello,
>
> those event routes are executed with a so called faked request (a request
> generated internally, unrelated to the OPTIONS request sent to the wire),
> apart of request uri, the rest of values are not related to the dispatcher
> records.
>
> To get access to other attributes of dispatcher records in a straight way
> in the config, it would require C coding, Anyhow, even now using scripting,
> you can try with sql queries to database or rpc commands execution via
> jsonrpcs module and then parse the result using jansson module.
>
> Cheers,
> Daniel
>
> On 18.12.17 13:33, George Diamantopoulos wrote:
>
> Hello all,
>
> I use the dispatcher module extensively for load balancing and fail-over.
> My kamailio instance is multihomed, and I use the "socket" attribute to
> determine which socket SIP messages should use for each dispatcher
> destination, as such:
>
> ++---+-+---+--+-
> +
> | id | setid | destination | flags | priority |
> attrs   |
> ++---+-+---+--+-
> +
> |  1 | 0 | sip:192.168.0.1:5060| 8 |0 | socket=udp:
> 10.10.10.1:5060  |
> |  2 | 1 | sip:111.111.11.1:5060   | 8 |0 | socket=udp:
> 44.44.44.1:5060  |
> |  3 | 1 | sip:222.222.22.2:5060   | 8 |0 | socket=udp:
> 55.55.55.1:5060  |
> ++---+-+---+--+-
> +
>
> The dispatcher module uses OPTIONS to probe each destination for
> availability. When a destination goes down or up, the respective
> event-route is executed.
>
> What I need to do is to be able to "capture" the sending socket used for
> this probing when a destination becomes unavailable or available in the
> event-routes. The $fs variable is set, but unfortunately its value does not
> make sense. Here's an example route and the results that are printed:
>
> event_route[dispatcher:dst-down] {
> xlog("L_ERR", "Destination down: $rm $ru ($du) $ds $fs $Ru $T_req($fs)
> $T_req($Ru)\n");
> }
>
> Now say destination with id = '2' goes down. This is what I get in the
> logs for the event_route above:
>
> ERROR:

Re: [SR-Users] Kamailio-IMS VM image issue

2017-12-20 Thread ponnam.g...@wipro.com

Hi Franz,

Thank you so much for the reply.

We have verified mysql db permissions, could not find issue with access 
permissions. Following is the output on console when we try to execute hss.sh 
script

root@server:~# ./hss.sh
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:..
2017-12-20 08:15:58,551 INFO  de.fhg.fokus.hss.main.TomcatServer - startTomcat 
Tomcat-Server is started.
2017-12-20 08:16:10,188 ERROR org.apache.coyote.http11.Http11Protocol - init 
Error initializing endpoint
java.net.BindException: Cannot assign requested address:8080
at 
org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoint.java:297)
at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:142)
at 
org.apache.catalina.connector.Connector.initialize(Connector.java:928)
at org.apache.catalina.startup.Embedded.start(Embedded.java:794)
at de.fhg.fokus.hss.main.TomcatServer.startTomcat(TomcatServer.java:128)
at de.fhg.fokus.hss.main.HSSContainer.(HSSContainer.java:74)
at de.fhg.fokus.hss.main.HSSContainer.main(HSSContainer.java:110)
2017-12-20 08:16:10,291 ERROR de.fhg.fokus.hss.main.HSSContainer -  
Exception occured during starting Tomcat!
Exiting from HSS...
LifecycleException:  Protocol handler initialization failed: 
java.net.BindException: Cannot assign requested address:8080
at 
org.apache.catalina.connector.Connector.initialize(Connector.java:930)
at org.apache.catalina.startup.Embedded.start(Embedded.java:794)
at de.fhg.fokus.hss.main.TomcatServer.startTomcat(TomcatServer.java:128)
at de.fhg.fokus.hss.main.HSSContainer.(HSSContainer.java:74)
at de.fhg.fokus.hss.main.HSSContainer.main(HSSContainer.java:110)

All servers(HSS, PCSCF, SCSCF, ICSCF) can communicate with each other and on 
HSS server no other service is using port 8080. Could you please guide us to 
resolve this issue?


Regards,
Raghavender

From: Franz Edler [mailto:franz.ed...@kabsi.at]
Sent: Wednesday, December 20, 2017 2:01 AM
To: 'Kranti Kumar' ; 'Kamailio (SER) - Users Mailing 
List' 
Cc: 'raghavender goud' ; Ponnam Raghavender Goud (NEPC) 

Subject: AW: Kamailio-IMS VM image issue


** This mail has been sent from an external source. Treat hyperlinks and 
attachments in this email with caution**
Hi Kranti,

you obviously have an error in the mysql configuration.
When you changed some parameters in the architecture you have to adapt also the 
configuration parameters.
Look at the access permissions for MySQL.

Von: Kranti Kumar [mailto:krantikum...@gmail.com]
Gesendet: Dienstag, 19. Dezember 2017 17:35
An: Kamailio (SER) - Users Mailing List 
>; 
franz.ed...@technikum-wien.at; 
franz.ed...@kabsi.at
Cc: raghavender goud >; 
ponnam.g...@wipro.com
Betreff: Kamailio-IMS VM image issue


Hi,

I’m trying to build a testbed using the VMware image you kindly have shared 
here: 
https://www.kamailio.org/w/2016/02/kamailio-ims-getting-started-box/



My configuration details:



HSS - 10.200.8.171 (VM1)

PCSCF - 10.200.8.175 (VM2)

ICSCF - 10.200.8.178 (VM3)

SCSCF - 10.200.8.181 (VM4)



While issuing the command ./hss.sh and

Re: [SR-Users] 4.4.4 CPU 100%

2017-12-20 Thread Daniel-Constantin Mierla

Hello,

can you monitor the traffic and see if you got exposed to someone
stressing your server with opening new connections?

The accept() function is from libc, not something implemented in
kamailio. So if the process is using a lot of CPU and it is stuck in
accept(), then it is something related to the connection layer  ...

Can you share the params for tls module? Another case that can be
exploited in tls related attacks is cypher renegotiation, but that
should be disabled by default in kamailio tls module.

Cheers,
Daniel


On 15.12.17 15:11, Tomas Zanet wrote:
> Hi all, I’ve been using Kamailio 4.4.4 for 8 months without any problems but 
> in recent days, I’m having some issues with our server and, when it happens, 
> it cannot get new registrations.
> Using top I saw a kamailio process is eating all CPU.
>
>   PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
>  1556 kamailio  20   0 1010884  27624  24520 R  98.5  1.4 150:07.59 kamailio
>
> I got backtrace attaching to Kamailio with gdb. Here is the backtrace:
>
> #0  0x7fb996992d6d in accept () at ../sysdeps/unix/syscall-template.S:81
> #1  0x005f3615 in handle_new_connect (si=0x7fb9960b4fa8) at 
> tcp_main.c:3894
> #2  0x005f7029 in handle_io (fm=0x7fb9961da520, ev=1, idx=-1) at 
> tcp_main.c:4199
> #3  0x005c68b2 in io_wait_loop_epoll (h=0xa1fdc0 , t=5, 
> repeat=0) at io_wait.h:1065
> #4  0x005fa04a in tcp_main_loop () at tcp_main.c:4490
> #5  0x004b48ba in main_loop () at main.c:1712
> #6  0x004bad12 in main (argc=13, argv=0x7ffd14247c18) at main.c:2631
> (gdb) bt
>
> At the moment I found the issue, there were 862 sip client registered 
> correctly.
> Our server is configured to use only TLS and mysql as backend.
>
> /usr/local/sbin/kamailio -v
> version: kamailio 4.4.4 (x86_64/linux) 852c47
> flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, DISABLE_NAGLE, 
> USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, 
> TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, 
> USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
> ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, 
> MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
> poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
> id: 852c47
> compiled on 15:56:18 Dec 15 2016 with gcc 4.8.4
>
> Can anyone address me to find out why this happens?
>
> Many thanks,
> T.
>
>
> Tomas Zanet
> R Software designer
> tza...@came.com
> CAME S.p.A.
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - www.asipto.com
Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Multiple Kamailio Servers + Location Table

2017-12-20 Thread Daniel-Constantin Mierla

Hello,


On 20.12.17 06:28, Daniel W. Graham wrote:
>
> When multiple Kamailio servers are using the same database with
> different server_id’s (one active the rest standby in this test),
> records disappear and are no longer tracked in location database table.
>
>  
>
> Some entries remain, but it never populates to the normal amount
> unless only one server is using the database.
>
I couldn't figure out the proper picture of what happens based on the
above ... some questions:

- only one server (the active) writes to database, with its own id
(other servers have different ids), after a while some records written
by the active server disappear?

 - is db_mode=3? If not, what value.

 - is there any replication at database layer?

Cheers,
Daniel


>  
>
> Anyone run into this before? Happened with 5.0 and is happening with 5.1.
>
>  
>
> -dan
>
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - www.asipto.com
Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio-IMS VM image issue

2017-12-20 Thread Franz Edler

But the error log „Cannot assign requested address:8080” says different.

There must be a process which already uses port 8080. Check with a proper Linux 
command.

 

Franz

 

Von: ponnam.g...@wipro.com [mailto:ponnam.g...@wipro.com] 
Gesendet: Mittwoch, 20. Dezember 2017 08:51
An: 'Franz Edler' ; 'Kranti Kumar' 
; 'Kamailio (SER) - Users Mailing List' 

Cc: 'raghavender goud' 
Betreff: RE: Kamailio-IMS VM image issue

 

Hi Franz,

 

Thank you so much for the reply.

 

We have verified mysql db permissions, could not find issue with access 
permissions. Following is the output on console when we try to execute hss.sh 
script

 

root@server:~# ./hss.sh

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:..

2017-12-20 08:15:58,551 INFO  de.fhg.fokus.hss.main.TomcatServer - startTomcat 
Tomcat-Server is started.

2017-12-20 08:16:10,188 ERROR org.apache.coyote.http11.Http11Protocol - init 
Error initializing endpoint

java.net.BindException: Cannot assign requested address:8080

at 
org.apache.tomcat.util.net.PoolTcpEndpoint.initEndpoint(PoolTcpEndpoint.java:297)

at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:142)

at 
org.apache.catalina.connector.Connector.initialize(Connector.java:928)

at org.apache.catalina.startup.Embedded.start(Embedded.java:794)

at de.fhg.fokus.hss.main.TomcatServer.startTomcat(TomcatServer.java:128)

at de.fhg.fokus.hss.main.HSSContainer.(HSSContainer.java:74)

at de.fhg.fokus.hss.main.HSSContainer.main(HSSContainer.java:110)

2017-12-20 08:16:10,291 ERROR de.fhg.fokus.hss.main.HSSContainer -  
Exception occured during starting Tomcat!

Exiting from HSS...

LifecycleException:  Protocol handler initialization failed: 
java.net.BindException: Cannot assign requested address:8080

at 
org.apache.catalina.connector.Connector.initialize(Connector.java:930)

at org.apache.catalina.startup.Embedded.start(Embedded.java:794)

at de.fhg.fokus.hss.main.TomcatServer.startTomcat(TomcatServer.java:128)

at de.fhg.fokus.hss.main.HSSContainer.(HSSContainer.java:74)

at de.fhg.fokus.hss.main.HSSContainer.main(HSSContainer.java:110)

 

All servers(HSS, PCSCF, SCSCF, ICSCF) can communicate with each other and on 
HSS server no other service is using port 8080. Could you please guide us to 
resolve this issue?

 

 

Regards,

Raghavender

 

From: Franz Edler [mailto:franz.ed...@kabsi.at] 
Sent: Wednesday, December 20, 2017 2:01 AM
To: 'Kranti Kumar'  >; 
'Kamailio (SER) - Users Mailing List'  >
Cc: 'raghavender goud'  >; 
Ponnam Raghavender Goud (NEPC)  >
Subject: AW: Kamailio-IMS VM image issue

 

** This mail has been sent from an external source. Treat hyperlinks and 
attachments in this email with caution**

Hi Kranti,

 

you obviously have an error in the mysql configuration.

When you changed some parameters in the architecture you have to adapt also the 
configuration parameters.

Look at the access permissions for MySQL.

 

Von: Kranti Kumar [mailto:krantikum...@gmail.com] 
Gesendet: Dienstag, 19. Dezember 2017 17:35
An: Kamailio (SER) - Users Mailing List  >; franz.ed...@technikum-wien.at 
 ; franz.ed...@kabsi.at 
 
Cc: raghavender goud  >; 
ponnam.g...@wipro.com  
Betreff: Kamailio-IMS VM image issue

 

Hi,

I’m trying to build a testbed using the VMware image you kindly have shared 
here: https://www.kamailio.org/w/2016/02/kamailio-ims-getting-started-box/

 

My configuration details:

 

HSS -

Re: [SR-Users] PIPELIMIT - limit change after time interval change. bug?

2017-12-20 Thread Daniel-Constantin Mierla

Hello,

can you open an issue on bug tracker in order not to forget this one and
approach it once the time allows:

  - https://github.com/kamailio/kamailio/issues

I am mostly out of office these days, checking stuff sporadically, so it
may take a bit of time to get to it.

Cheers,
Daniel


On 18.12.17 18:59, Juan Priotti wrote:
> Hi,
> I'm making some tests with pipelimit module and when changing the time
> interval the limit gets changed in a way that it's multiplied by the
> time interval. For example if I use a time interval of 1 second and a
> limit of 20 (if (!pl_check("$si", "TAILDROP", "20"))) the module start
> limiting right after the traffic gets over 20 CPS. But if I change the
> time interval to 3 seconds, the module starts limiting the traffic
> right after 60 CPS. This is my configuration:
>
> # - pipelimit params-
> modparam("pipelimit", "timer_interval", 3)
> modparam("pipelimit", "hash_size", 10)
> modparam("pipelimit", "db_url", DBURL)
> modparam("pipelimit", "reply_code", 503)
> modparam("pipelimit", "reply_reason", "Limiting")
>
> ...
> ...
> ...
>
> request_route {
> ...
> ...
>         if(is_method("INVITE")) {
>                 $var(limit) = 20;
>                 if (!pl_check("$si", "TAILDROP", "$var(limit)")) {
>                 xlog("L_INFO", "[$ci] $si - Limiting INVITE using pipe
> $var(limit) req/sec\n");
>                 pl_drop();
>                 exit;
>         }
> .
> .
> .
>         }
> }
>
>
> Checking the source for pipelimit module
> (https://github.com/kamailio/kamailio/blob/master/src/modules/pipelimit/pipelimit.c)
> I see that for taildrop it's checking for the limit times the
> time_interval:
>
> case PIPE_ALGO_TAILDROP:
> ret = (pipe->counter <= pipe->limit * timer_interval) ? 1 : -1;
> break;
>
> I've made a change eliminating the time_interval (set it to 1) from
> that check and after that I've got the limit working OK, and the
> traffic gets drop right after it's over the limit (20 cps) using any
> time_interval. Is there some issue with the timer for the check not
> being updated by the module settings (timer_interval)? I'm using
> kamailio 4.4 and I've also tested it in kamailio 4.3 and 5.1 with same
> results.
> Thanks in advance,
>
> Juan Priotti
>
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - www.asipto.com
Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Multiple Kamailio Servers + Location Table

Re: [SR-Users] Multiple Kamailio Servers + Location Table

Re: [SR-Users] Kamailio-IMS VM image issue

Re: [SR-Users] Multiple Kamailio Servers + Location Table

Re: [SR-Users] Multiple Kamailio Servers + Location Table

Re: [SR-Users] Multiple Kamailio Servers + Location Table

Re: [SR-Users] Dispatcher module OPTIONS and event routes: how are they handled by core?

Re: [SR-Users] Dispatcher module OPTIONS and event routes: how are they handled by core?

Re: [SR-Users] Kamailio-IMS VM image issue

Re: [SR-Users] 4.4.4 CPU 100%

Re: [SR-Users] Multiple Kamailio Servers + Location Table

Re: [SR-Users] Kamailio-IMS VM image issue

Re: [SR-Users] PIPELIMIT - limit change after time interval change. bug?

13 matches

Site Navigation

Mail list logo

Footer information