Dear Kamailio users,
I have an issue with some upstream carriers quickly replying with 100 Trying but then basically times out.
I'm looking for a good solution to distinguish between the 100 reply and any other replies, and alter the timeout values. My goal is to be able to re-route calls where the 180/183 is not received within a few seconds, and if the 180/183 is received I'd like to give the call a much longer timeout.
I realize there is a "fr_inv_timer" that would do this, but I would not like to set that to low since I fear it would affect many other call types, i.e. if a carrier would send 183 once but for some reason does not resend on regular intervals.
I'm on Kamailio 4.1 and my current settings are:fr_timer : 2000fr_inv_timer : 120000restart_fr_on_each_reply : 1
The only solution I can think of is to update the fr_inv_timer in an on_reply-route if the reply code is 180/183 but I'm not sure that would even work? Is that the way to go or is there another way?
Thanks in advance!/Tobias
Hello All,
I am using Kamailio in front of Freeswitch and Kamailio is handling the
registrations then forwarding to Freeswitch and everything is working for
the most part.
However, there is niggling pain in the neck issue where the user's
User-Agent shows in Freeswitch as kamailio (4.0.6 (x86_64/linux)) instead
of the user's Real User-Agent I am trying to get Kamailio to pass the real
User-Agent of the user without success.
I am able to set a static User-Agent by doing this in the global section.
*user_agent_header = "User-Agent: We love beer";*
However, I am unable to set it dynamically for example:
*user_agent_header = "User-Agent: " + $ua;*
With is one Kamailio doesn't even start so my syntax is probably wrong.
I also tried playing around with the textops module so I have ran out of
ideas
Any ideas?
Thanks in advance.
regards,
Errol
Hi all,
We are experiencing a strange problem in our Kamilio server. Some of the
webrtc endpoint registrations are not updated to the Database and there is
no issue with the registration. Once we flushed the registration for this
endpoint then it is updating to the DB for the new Register Packet.
Flushed the Registration for the endpont : kamctl ul rm <USERNAME>
Kamalio Version: 4.1.2
modparam("usrloc", "db_url", DBURL)
*modparam("usrloc", "db_mode", 1)*
modparam("usrloc", "nat_bflag", 3)
modparam("usrloc", "use_domain", 1)
Is there any other settings to avoid this issue ?
Regards
Varghese Paul
Hello,
I use Kamailio 4.1.3 with siptrace module. In the sip_trace table I see
duplicate information, one line with empty and one line with filled
traced_user column.
The empty lines are useless for me, I would like only entries with
traced_user information.
Here the siptrace part of kamailio.cfg:
#### Parameters for Siptrace module
modparam("siptrace", "db_url", DBURL)
modparam("siptrace", "trace_on", 1)
modparam("siptrace", "trace_flag", 22)
modparam("siptrace", "trace_sl_acks", 0)
modparam("siptrace", "traced_user_avp", "$avp(s:user)")
modparam("siptrace", "trace_delayed", 0)
###### SIP Trace Config in main route
if (!is_method("OPTIONS")) {
if (!ds_is_from_list("2")) {
$avp(s:user) = $fU;
} else {
$avp(s:user) = $rU;
};
if (is_avp_set("$avp(s:user)")){
sip_trace();
#setflag(22);
};
};
Has anyone a tip for me how I can get rid of the empty traced_user lines?
Regards
Fred
Hi Daniel,
Thanks for the response.
Reviewing the logs again, the first occurrence was on 25Sep, after upgrading to 4.1.6+precise on 24Sep.
Previous upgrades were to:
4.1.5+precise 18Aug
4.1.4+precise June
Traffic patterns are fairly uniform over that period.
I've installed the nightly (4.1.6+0~20141004025841.74+precise) and we'll see how that goes until the next release.
Cheers,
Dave
> Date: Thu, 02 Oct 2014 09:02:14 +0200
> From: Daniel-Constantin Mierla <miconda(a)gmail.com>
> To: "Kamailio (SER) - Users Mailing List"
> <sr-users(a)lists.sip-router.org>
> Subject: Re: [SR-Users] Segfault in 4.1.6
> Message-ID: <542CF876.6060900(a)gmail.com>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> Hello,
>
> I see it crashed in dialog, it was a fix for it after 4.1.6 for the
> cleanup timer procedure, affecting some particular cases with dialog
> states (e.g., dialogs not answered even after many minutes since
> creation). It was there before 4.1.6 (most probably from 4.1.0), not
> introduced by that version. What you were using before 4.1.6?
>
> You can get latest version from branch 4.1 either via GIT or via debian
> nightly builds of 4.1 (if using debian).
>
> Otherwise, yes, a coredump with a gdb backtrace will be very helpful.
>
> Cheers,
> Daniel
>
> On 02/10/14 08:31, David Wilson wrote:
> > Hi all,
> >
> > I?ve had Kamailio running nicely for nearly a year, but have hit a segfault twice since upgrading to 4.1.6 earlier this week.
> >
> > The log shows:
> >
> > Oct 2 11:28:03 localhost /usr/sbin/kamailio[1222]: : <core> [pass_fd.c:293]: receive_fd(): ERROR: receive_fd: EOF on 23
> > Oct 2 11:28:03 localhost kernel: [11259.904645] kamailio[1206]: segfault at 58 ip 00007fa56fba0f86 sp 00007fffea594ca0 error 4 in dialog.so[7fa56fb63000+54000]
> > Oct 2 11:28:03 localhost /usr/sbin/kamailio[1175]: ALERT: <core> [main.c:777]: handle_sigs(): child process 1206 exited by a signal 11
> > Oct 2 11:28:03 localhost /usr/sbin/kamailio[1175]: ALERT: <core> [main.c:780]: handle_sigs(): core was not generated
> > Oct 2 11:28:03 localhost /usr/sbin/kamailio[1175]: INFO: <core> [main.c:792]: handle_sigs(): INFO: terminating due to SIGCHLD
> > Oct 2 11:28:03 localhost /usr/sbin/kamailio[1220]: INFO: <core> [main.c:843]: sig_usr(): INFO: signal 15 received
> > ?.
> >
> > The first two lines above seem to be the important parts. Nothing was logged for about 10s prior to this extract. An earlier instance of the issue showed almost the same details:
> >
> > Oct 1 20:39:12 localhost /usr/sbin/kamailio[1219]: : <core> [pass_fd.c:293]: receive_fd(): ERROR: receive_fd: EOF on 23
> > Oct 1 20:39:12 localhost kernel: [554502.639227] kamailio[1207]: segfault at 58 ip 00007fd62c5c6f86 sp 00007fffd77c9890 error 4 in dialog.so[7fd62c589000+54000]
> >
> > I?m trying to catch a core next time it occurs, no core is available yet.
> >
> > Is this a new issue in 4.1.6?
> > Any suggestions about the likely cause?
> >
> > Cheers,
> > Dave.
> >
Hello,
short note to say that the branch 4.2 has been created, as announced on
mailing list a while ago.
This is the official branch to be used for releasing any of the 4.2.x
versions. The first one, v4.2.0, is expected to be out in about one week.
The version used now in master branch is prefixed with 4.3.0, which is
expected to be the next future major release. With this change,
practically commits with new features to be part of 4.3.0 can be pushed
to master branch from now on.
Any fix that is applicable for both master and 4.2 branches has to be
committed first in master branch, then cherry-picked or merged to branch
4.2.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Hi all,
How i can setup multiple kamailio servers should share the single
registration DB.
Requirement: I have two kamailio instances Kamailio-A and Kamalio-B ,both
are sharing the same DB which is postgre*SQL *which is hosted in some other
server.
When a USER AGENT A send a register packet to Kamailio-A it is updating the
registration status in the DB. But in kamailio-B if am doing a
lookup(location) i am getting -1 as return value.
kamctl ul show <USER_AGENT>
404 AOR not found
1. How kamailio retrieving the registrations status ? Is it from the DB or
from the internal cache ?
2. How can i read the registration status from the DB always ?
Let me know if any one need any more information.
Regards
Varghese Paul
Hello. We have multiple kamailio behind load balancer. We use UAC to send
REGISTER procedure to provider. Some providers drop wrong ip. So We have
loadbalanser with external IP and have kamailio servers with external IPs
too. So we need to send REGISTER packets to porovide with source IP of our
Load balancer. Now kamailio send REGISTER pakets with its external IP.
Question is how to send REGISTER with ip adress of loadbalanser?
(allias with it dn and ip already exists at config)
(listet already had it ip too)
thanks/
I'm using Kamailio as SIP Registrar using Websockets.
My topology looks like this:
Sip client (sipml5) ---> wss ---> Nginx ---> ws ---> Kamailio 4.1.5
When I look into my SipMl5 application in the Register Message 200 OK
from Kamailio I see the Nginx private IP address 172.31.22.2
Via: SIP/2.0/WSS
df7jal23ls0d.invalid;rport=37111;received=172.31.22.2;branch=z9hG4bKtv75otkzmPVsdNWevweLt4TN9JnLnQ0p
How can I remove private IP Address in Via header to achieve topology hiding?
>From Kamailio logs:
Oct 6 00:34:21 ip-172-31-27-85 /usr/sbin/kamailio[8941]: DEBUG:
registrar [reply.c:374]: build_contact(): created Contact HF: Contact:
<sips:gogasca@df7jal23ls0d.invalid;rtcweb-breaker=no;transport=wss>;expires=200#015#012
Oct 6 00:34:21 ip-172-31-27-85 /usr/sbin/kamailio[8941]: DEBUG: sl
[sl.c:288]: send_reply(): reply in stateless mode (sl)
Oct 6 00:34:21 ip-172-31-27-85 /usr/sbin/kamailio[8941]: DEBUG:
<core> [msg_translator.c:204]: check_via_address():
check_via_address(172.31.22.2, df7jal23ls0d.invalid, 0)
O
Version: kamailio 4.1.5 (x86_64/linux)
# ------ topoh --------
modparam("topoh", "mask_key", "opencall")
modparam("topoh", "mask_ip", "<Public IP Address of Kamailio>")
modparam("topoh", "vparam_prefix", "llamato")
modparam("topoh", "mask_callid", 1)
modparam("topoh", "sanity_checks", 1)
Thanks Daniel,
I'm trying to use sqlite (mysql is too "heavy" for my environment) but usually I receive a lot of commit failed because database is locked (especially in presentity.c and publish.c)
Is there any way to manage, maybe i've missed some sqlite configuration parameters?
----Messaggio originale----
Da: miconda(a)gmail.com
Data: 6-ott-2014 18.17
A: "Marino Mileti"<marino.mileti(a)alice.it>, "Kamailio (SER) - Users Mailing List"<sr-users(a)lists.sip-router.org>
Ogg: Re: [SR-Users] Presence PUBLISH error
hello,
It seems that the column type and value type are mismatching, but
they can still be compatible.
The fact is that db_text was not designed to handle large data
values, so not tested with presence. Eventually you may want use
sqlite (or other db module) instead or go into db_text and update as
needed.
Cheers,
Daniel
On 06/10/14 15:14, Marino Mileti wrote:
Hi guys,
with Kamailio 4.1.6 standard configuration and dbtext as db
module, when server receives a publish message on the log there's:
ERROR: db_text [dbt_base.c:391]: dbt_insert(): incompatible types
v[5] - c[7]!
ERROR: presence [presentity.c:402]: update_presentity(): inserting
new record in database
ERROR: presence [publish.c:464]: handle_publish(): when updating
presentity
and the server reply with 500 Server Internal Error.
My conf is standard I've only used DBURL to point to my dbtext
files: I've enable presence and presence_xml module
# ----- presence params -----
modparam("presence", "db_url", text:///opt/kamailio-orig/dbtext)
modparam("presence", "db_table_lock_type", 0)
modparam("presence_xml", "db_url",
text:///opt/kamailio-orig/dbtext)
modparam("presence_xml", "force_active", 1)
Any idea?
Marino
_______________________________________________
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
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
