Hi,
We sometimes get issues caused by truncated SDP bodies. Therefore, we are
looking at using TCP instead of UDP.
What is the recommended configuration when TCP is used?
Currently, I only have the following:
children=16
listen=udp:<ip>:5060
listen=tcp:<ip>:5060
disable_tcp=no
tcp_connection_lifetime=605 (registration expiry is 600)
Also, is there a difference with UDP regarding NAT handling?
Thanks,
Mickael
db_text error
I am getting the following error on using db_text
0(6638) INFO: db_text [dbt_base.c:99]: dbt_init(): using database at: /usr/local/etc/kamailio/ 0(6638) ERROR: db_text [dbt_base.c:207]: dbt_query(): table version not loaded! (too few columns)
0(6638) ERROR: db_text [dbt_base.c:306]: dbt_query(): failed to query the table!
I have thisin my kamailio.cfg
#!define DBURL "text:///usr/local/etc/kamailio/dbtext"
I created the following files
cat > /usr/local/etc/kamailio/dbtext/version
table_name(str) table_version(int)
subscriber:6
location:6
aliases:6
cat > /usr/local/etc/kamailio/dbtext/subscriber
username(str) password(str) ha1(str) domain(str) ha1b(str)
someuser:someuser:xxx:10.1.1.5:xxx
can some advise how to get db_text work for me
Regards
Hi All,
I'm looking to have a better understanding of when to use the Timer process
versus the "Slow Timer" Process. This is what I came up with, but please
correct me:
- The “*Timer*” process is used to handle core processing within
Kamailio. Therefore, you don’t want to put long running logic into the
routing handler
- The “*Slow Timer*” process can be used for long running processes
Hello;
i am trying to understand how is ims_charging working . Kamailio is
a S-CSCF here. kamailio and call dont have a problem but ro_session.
i always get ro_session_ontimeout() ERROR. when look diameter trace
, ims_charging module dont request for 30 more sec for granted and kill
dialog.
Thanks for helps.
14:22:51 S-CSCF ----->CC-Time 15 .. Sec CCR ---> Java-Diamaeter
Server (INITIAL REQ)
14:22:51 S-CSCF <-----CC-Time 15 .. Sec CCA <--- Java-Diamaeter
Server (INITIAL REQ)
14:23:01 S-CSCF ----->CC-Time 10 .. Sec CCR ---> Java-Diamaeter
Server (UPDATE )
14:23:01 S-CSCF <-----CC-Time 30 .. Sec CCA <--- Java-Diamaeter
Server (UPDATE )
14:23:31 S-CSCF ----->CC-Time 30 .. Sec CCR ---> Java-Diamaeter
Server (TERMINATE )
14:23:31 S-CSCF <-----CC-Time 30 .. Sec CCA <--- Java-Diamaeter
Server (TERMINATE )
------ LOG -----
May 7 14:23:31 /usr/local/sbin/kamailio[7602]: ERROR: ims_charging
[ro_timer.c:449]: ro_session_ontimeout(): Diameter call session - event [2]
May 7 14:23:31 /usr/local/sbin/kamailio[7602]: INFO: ims_charging
[ro_timer.c:452]: ro_session_ontimeout(): Call/session must be ended -
no more funds.
May 7 14:23:31 /usr/local/sbin/kamailio[7600]: WARNING: ims_charging
[dialog.c:167]: dlg_terminated(): inconsistent ro timer data on
ro_session 0x7ff1eb4543b8 []
---- CFG ------
$var(cc_ret) = Ro_CCR("CHARGING_CCR_REPLY", "orig", "SCUR", "", "15",
"location");
---- CFG ------
is there any way to make deb packages for only 1 of the modules ??
currently it takes a long time to run "make deb"
im simply trying to build and package db_cassandra ( need the package for
my environment )
As a side note, is there any chance db_cassandra could be added to the
kamailio deb packages ?
--
Sincerely
Jay
Hello,
We would like to match specific calls based on two factors:
1. the source IP address
2. the Request URI
I see in the permissions module, it is possible to match based on the
Source IP + the From URI.
We need two match both in order to return the appropriate 'tag' attribute
from table.
Would anyone know of a way to accomplish this?
Also, I noticed that matching source IP + from uri, you cannot control
which result is returned by permissions module based on regular expression.
In other words if more than one match is made, permissions module seems to
return the first result.
Thank you and I look forward to your response.
V
Hi,
After restarting Kamailio, I got the following errors during the startup:
kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:381]:
db_mongodb_get_columns(): field [caller_sock] not found in result iterator
kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:739]:
db_mongodb_store_result(): failed to set the columns
kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:918]:
db_mongodb_query(): failed to store result
kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:927]:
db_mongodb_query(): failed to do the query
kamailio[12614]: ERROR: dialog [dlg_db_handler.c:257]:
select_entire_dialog_table(): Error while querying database
What may be causing the issue? I should always have a caller_sock in every
dialog document.
Thanks,
Mickael
Hi,
I sometimes see the following in the logs:
kamailio[14433]: ERROR: <core> [tcp_read.c:271]: tcp_read_data(): error
reading: Connection reset by peer (104)
kamailio[14433]: ERROR: <core> [tcp_read.c:1296]: tcp_read_req(): ERROR:
tcp_read_req: error reading
It looks like Kamailio tries to read a request from a TCP socket but the
connection has been reset (not properly ended) by the remote peer.
Is it an error? Does it prevent Kamailio from working properly? If yes, what
is the solution?
Thanks,
Mickael
Hello,
cross posting to get heads up of everyone that wants to join the
discussion, however, do reply to sr-dev(a)lists.sip-router.org, being more
related to development and project files structure.
At this moment we install three kamailio configuration files:
- kamailio.cfg - the default one to be used when starting kamailio
- kamailio-basic.cfg - a more simple version of configuration
- kamailio-advanced.cfg - a more complex version (equivalent of
kamailio-oob.cfg in etc/ source tree)
Somehow it was suggested that apart of kamailio.cfg, the other files
belong more to the docs (shared) folder (where we put INSTALL, README,
etc), because they are not actually used as configuration files by
kamailio installation (one has to change either init.d script or copy
over kamailio.cfg). Also, some are confused not knowing if they are used
or not at runtime.
Shall we relocate where those files are deployed by installation?
Another point: we deploy the radius dictionary with the core. I think it
should be deployed by a radius module and be part of radius modules
package. The question is which module should deploy it? Is auth_radius
fine for everyone? Alternative would be acc_radius.
To complete the cleanup of etc/ folder in the source code, I think the
sip-router*.cfg files should me moved to examples/, at quick look they
are invalid, using paths to old ser modules, no longer available at this
moment (therefore I guess nobody is using them).
Opinions and other suggestions are very welcome!
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio World Conference, May 27-29, 2015
Berlin, Germany - http://www.kamailioworld.com
Hello Vik,
I don't have same problem it works fine for me, but I have same setup on public side where multiply aliases on interface is involved.
Slava.
From: "Vik Killa" <vipkilla(a)gmail.com>
To: "sr-users" <sr-users(a)lists.sip-router.org>
Sent: Monday, May 4, 2015 12:54:21 PM
Subject: Re: [SR-Users] issue with TLS and 2 NIC interfaces
Are you having the same problem as myself?
Thanks,
V
On Fri, May 1, 2015 at 8:20 PM, Slava Bendersky < volga629(a)networklab.ca > wrote:
Hello Vik,
I have similar setup, try define you server configuration in tls.cfg
[server:ip address of alias interface:port of alias interface]
method = TLSv1
verify_certificate = no
require_certificate = no
private_key =
certificate =
ca_list =
crl =
Slava
From: "Vik Killa" < vipkilla(a)gmail.com >
To: "sr-users" < sr-users(a)lists.sip-router.org >
Sent: Wednesday, April 29, 2015 4:32:21 PM
Subject: [SR-Users] issue with TLS and 2 NIC interfaces
Hello,
if i have two interfaces (eth0 and eth0:0)
I set kamailio to listen to the IP on eth0:0
This works great except when I try using TLS, kamailio routes traffic from eth0:0 to eth0 then to correct destination
It should be just doing eth0:0 -> correct destination
If I use UDP/TCP I am not seeing this behavior.
If I set kamailio to listen to eth0 and remove eth0;0, TLS works fine.
I'm running kamailio compiled from source git master a few days ago.
Is anyone else having this problem?
I'm wondering if it's a bug.
Thanks,
V
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)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
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
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
