Hello!
I need help understanding how the *handle_ruri_alias()* function works.
*Call-flow:* Upstream operator -> Kamailio Proxy -> Edpoint.
The upstream operator in the initial SIP INVITE in the Contact field sends
us an alias parameter, in turn, our Kamailio Proxy adds its own too.
The Contact after the Proxy looks something like this:
*Contact:
<sip:10.0.0.115:5060;alias=10.0.0.115~5060~1;alias=3.3.3.3~5060~1>*
When the Endpoint sends us a SIP BYE, then the *handle_ruri_alias()*
absorbs not the last alias, but the first one, and this leads to the
incorrect formation of a $du.
The RURI after the Proxy looks something like this:
*Request-Line: BYE sip:10.0.0.115:5060;alias=3.3.3.3~5060~1 SIP/2.0*
The first thing that comes to mind is a modification of the original
Contact field with storing it's within a dialogue ...
Is it possible to elegantly solve this problem?
--
BR,
Denys Pozniak
Hi
We've seen a few occurrences of this crash since we implemented kamailio
5.4.5 for our inbound call traffic. Preceding the crash we always get a
message in the logs about "dialog [dlg_hash.c:1182]: next_state_dlg():
bogus event 2 in state 5 for dlg" and whenever we see that message, we
get the crash.
Jun 1 10:12:14 thissystem /usr/sbin/kamailio[20001]: CRITICAL: {2 1
INVITE 6787142-3831531134-1330894187(a)some.telco.domain} dialog
[dlg_hash.c:1182]: next_state_dlg(): bogus event 2 in state 5 for dlg
0x7fae153d3cf0 [3973:6059] with clid
'82608924-3831089984-1833452161(a)some.telco.domain' and tags
'3831089984-684203260' ''
The crash happens on line 879 of
https://github.com/kamailio/kamailio/blob/master/src/modules/dialog/dlg_db_…
SET_STR_VALUE(values+7, cell->bind_addr[DLG_CALLER_LEG]->sock_str);
Looking at gdb, I see that cell->bind_addr[DLG_CALLER_LEG] == 0 so
trying to use it results in the segfault. I have thought about patching
that to check for bind_addr being set and bypassing that line if not but
I do not think it's the right fix though it probably would avoid the
current crash (and do odd things later instead!). I did check that
everything else in that function that uses DLG_CALLER_LEG is set
correctly and it appears that it is - or at least if not correctly then
they are at least set!
The "bogus event 2 in state 5" message is coming out from line 1143 in
src/modules/ims_dialog/dlg_hash.c
case DLG_EVENT_RPL1xx:
switch (dlg->state) {
case DLG_STATE_UNCONFIRMED:
case DLG_STATE_EARLY:
dlg->state = DLG_STATE_EARLY;
break;
default:
log_next_state_dlg(event, dlg);
}
break;
(I didn't really understand why it would set dlg->state =
DLG_STATE_EARLY if it's already DLG_STATE_EARLY but...)
I have a couple of core dumps of this from the last day or two - usually
seems to crash at least once a week on our pair of kamailio inbound
servers. If there's any more info I can provide to help fix this
properly rather than my proposed bodge then feel free to ask.
Trevor Hemsley
Disclaimer
The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.
This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.
Hi,
I am working with the UAC module and trying to register with providers, and can see
that kamailio keeps sending the REGISTER from the private IP address socket on the server (eth0).
Is it possible to set the default socket or send socket for the REGISTER message that gets sent out via kamailio?
I am running version 4.4.7.
I notice SIP OPTIONS are being sent out from the public IP address (eth1) on the server (as I have set socket in dispatcher) and was hoping for same behaviour with uac module.
Please can anyone advise?
Many thanks
Jon
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
Hello guys,
I want to test secsipid, but i don't yet have the certificate. So i thought
i'd create a cert like:
openssl req -new -newkey rsa:4096 -nodes -keyout snakeoil.key -out
snakeoil.csr
openssl x509 -req -sha256 -days 365 -in snakeoil.csr -signkey snakeoil.key
-out snakeoil.pem
Then i'm simply doing:
$var(rc) = secsipid_add_identity("$fU", "$rU", "A", "", "
https://somedomain.com/stir/$rd/cert.pem
<https://kamailio.org/stir/$rd/cert.pem>", "/etc/kamailio/snakeoil.pem");
if ( $var(rc) ) {
xlog("L_ERR", "[STIR/SHAKEN][$ci] Shaken authentication added (SIP
Identity Header created)\n");
} else {
xlog("L_ERR", "[STIR/SHAKEN][$ci] Failed\n");
}
But no matter what i do it silently fails:
INVITE d54c2919-39b6-123a-95a7-0e29a5289b8d} <script>:
[STIR/SHAKEN][d54c2919-39b6-123a-95a7-0e29a5289b8d] Failed
I have debug on 6, but i don't get more info regarding the error.
Any ideas?
Regards,
David Villasmil
email: david.villasmil.work(a)gmail.com
phone: +34669448337
Hello,
Kamailio SIP Server v5.4.6 stable release is out.
This is a maintenance release of the latest stable branch, 5.4, that
includes fixes since the release of v5.4.5. There is no change to
database schema or configuration language structure that you have to do
on previous installations of v5.4.x. Deployments running previous v5.4.x
versions are strongly recommended to be upgraded to v5.4.6.
Note that 5.4 is the second last stable branch, still officially maintained
by Kamailio development team. The latest stable branch is 5.5, with
v5.5.0 being release out of it.
For more details about version 5.4.6 (including links and guidelines to
download the tarball or from GIT repository), visit:
* https://www.kamailio.org/w/2021/06/kamailio-v5-4-6-released/
RPM, Debian/Ubuntu packages will be available soon as well.
Many thanks to all contributing and using Kamailio!
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - Online - June 7-10, 2021 (America Timezone)
* https://www.asipto.com/sw/kamailio-advanced-training-online/
Hello,
I am considering to release Kamailio v5.4.6 sometime next week, likely
on Wednesday or Thursday (June 2 or 3, 2021). This is the usual heads up
notification to see if anyone is aware of issues not yet reported to bug
tracker and if yes, do it as soon as possible to give them a chance to
be fixed.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - Online - June 7-10, 2021 (America Timezone)
* https://www.asipto.com/sw/kamailio-advanced-training-online/
Hi to all,
I am interested in the implementation of IPsec module. When I run Kamailio, it is creating processes based on the below formulate:
UDP children * IPSEC_MAX_CONN * interfaces (v4 and v6) + (TCP+UD) processes for each interface.
For example:
children = 16tcp_children=16
IPSEC_MAX_CONN = 25and two interface : IPv6 and V4
Kamailio process count = (16 * 25 * 2 ) + 16 + 16 = 832
But why IPsec module is listening to UDP not TCP? this is an internal connection?
Thank you.
Regards,Hossein
Hello,
I would like to add the maxptime attribut to the sdp body. How and where should I do insertion?
This kamailio is also using RTPEngine, so is it better to do the insertion using RTPEngine? And the source of the SDP is actually FreeSwitch :), maybe there to tweak?
Of course, I don't know either way of doing it so please advise.
Thanks,
Victor
Good afternoon All,
Im hoping for some advise or direction with the below. We are running a Kamailio SBC used for high call volumes and recently decided to upgrade the Database servers as the existing servers were struggling. Both the old and new databases are using MariaDB(version details all below), the problem we face is that since migrating to the new database there appears to a limitation to the amount of DB connections that can be processed or accepted. The SBC functions normally until the CPS starts to exceed around 100cps at which point the SBC stops responding to invites(in bursts which resembles flood prevention). We have checked both the Kamailio logs and the MySQL logs on the DB, both log files have no indication of errors that would cause the problem experienced(the logs attached are seen when the SBC is cut back to use the old DB, not sure they are related to the fault), the connections/processes in mysql do not drastically increase or get stuck either. The fault points to a db connection limit of some kind but all users have no limitations set. If anyone has experienced a similar problem or has any advise it would be greatly appreciated.
Some info on the Kamialio and DB versions
New DB
root@voice-jhb-db01:~# mysql --version
mysql Ver 15.1 Distrib 10.3.27-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2
Old DB
[root@isadb01 ~]# mysql --version
mysql Ver 15.1 Distrib 10.0.36-MariaDB, for Linux (x86_64) using readline 5.1
Kamailio SBC
[root@sbc01 ~]# kamailio -v
version: kamailio 5.1.4 (x86_64/linux)
Kind regards,
Stephen
Voice Engineer
Tel:
2404
Fax:
3468
Email: