Juha Heinanen via sr-users writes:
> 2024-06-17T14:48:27.702827+03:00 siika /usr/bin/sip-proxy[297246]: WARNING:
> db_mysql [km_my_con.c:187]: db_mysql_new_connection(): opt_ssl_ca option not
> supported by mysql version (value (null)) - ignoring
Just to clarify, I have not defined o
When I start Kamailio master version that has been build on Debian 12
with default-libmysqlclient-dev depending on libmariadb-dev-compat, I
get several warnings like this:
2024-06-17T14:48:27.702827+03:00 siika /usr/bin/sip-proxy[297246]: WARNING:
db_mysql [km_my_con.c:187]:
If you want to select something based on phone number (longest) prefix,
then mtree module could be useful.
-- Juha
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to
OK, this is the fix:
diff --git a/src/modules/tm/t_msgbuilder.c b/src/modules/tm/t_msgbuilder.c
index 362ff6c5eb..187be7871d 100644
--- a/src/modules/tm/t_msgbuilder.c
+++ b/src/modules/tm/t_msgbuilder.c
@@ -1246,7 +1246,8 @@ char *build_dlg_ack(struct sip_msg *rpl, struct cell
*Trans,
I added some debug to t_msgbuilder.c and found out that
function build_uac_req() where missing Max-Forwards is added, is not
executed when request is ACK. It is executed when request is INVITE or
BYE.
So where should Max-Forwards check for ACK be done?
-- Juha
t_msgbuilder.c build_uac_req() has:
if(headers == NULL || headers->len < 15
|| _strnstr(headers->s, "Max-Forwards:", headers->len)
== NULL) {
maxfwd_len = MAXFWD_HEADER_LEN;
} else {
maxfwd_len = 0;
}
It should add
Kamailio sends INVITE by tm.t_uac_wait RPC command:
INVITE sip:test-0x55e7f1f78e70@192.168.187.215:5022 SIP/2.0
Via: SIP/2.0/UDP
192.168.187.215;branch=z9hG4bK6cf1.f1d087d6.0
To:
From:
;tag=2dd3d4389fe3d66c5cb97dc370ab7d7b-9c5a2a58
CSeq: 1 INVITE
Call-ID:
satyaprakash ch via sr-users writes:
> We are receiving 2 to 3 contact headers in the 200 OK response of the
> registration request. It appears that the `user_location` is updating
> multiple contact headers for the same extension due to network
> disconnections. Please suggest a solution to
Daniel-Constantin Mierla writes:
> I actually replied on you initial email at that time, saying that is
> interesting to add it. My previous email was a follow up of that email.
OK, looks like I missed it. Will prepare PR.
-- Juha
__
Daniel-Constantin Mierla writes:
> are you still planning to add this patch to the repo?
Based on non-existing comments, looks like I'm the only one interested.
So it is not worth to create a PR.
-- Juha
__
Kamailio - Users Mailing List -
Juha Heinanen via sr-users writes:
> I noticed that sql_query does not (anymore) work when called from
> event route:
I created bug issue https://github.com/kamailio/kamailio/issues/3843
about this to GitHub, since it really looks like a bug, because the same
code has worked fine i
I noticed that sql_query does not (anymore) work when called from event route:
event_route [tcp:closed] { # Handle TCP connection close
# Delete possible leftover registration
if ($conid)
sql_query("sip_proxy_cache", "DELETE FROM location WHERE server_id=0
AND
How about this new function that sets the algorithm?
-- Juha
iff --git a/src/modules/auth/auth_mod.c b/src/modules/auth/auth_mod.c
index 534ad9e20f..4e3a584d22 100644
--- a/src/modules/auth/auth_mod.c
+++ b/src/modules/auth/auth_mod.c
@@ -74,6 +74,10 @@ int w_consume_credentials(struct sip_msg
Juha Heinanen via sr-users writes:
> Currently digest authentication hash algorithm (MD5 or SHA-256) is
> selected when auth module is loaded. How about allowing to select it
> also dynamically using the function flags?
Can't be done, since auth_db functions don't have flags parameter.
Currently digest authentication hash algorithm (MD5 or SHA-256) is
selected when auth module is loaded. How about allowing to select it
also dynamically using the function flags?
-- Juha
__
Kamailio - Users Mailing List - Non Commercial
Daniel-Constantin Mierla writes:
> It might be a regression by commit 675f6c02248, can you try with latest
> master or with the patch of the commit:
>
> -
> https://github.com/kamailio/kamailio/commit/4dc37aee853bbcf9d7fdb96245b76aaa8dfa2930
I tried with latest master and it started OK.
Daniel-Constantin Mierla writes:
> what are the operating system and the compiler used?
Sorry, Debian 12 using gcc version 12.2.0.
-- Juha
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to
My SIP proxy didn't start with Kamailio 5.8 using the same config that
starts OK with 5.7. The error is:
2024-03-11T06:56:06.457107+02:00 lohi /usr/bin/sip-proxy[2358954]: DEBUG: acc
[acc_mod.c:362]: parse_failed_filter(): failed_filter 0 = 407
2024-03-11T06:56:06.457265+02:00 lohi
Kamailio 5.8 build generates on my Debian 12 the following warning:
core/mem/q_malloc.c:996:14: warning: 'qm_strnstr' defined but not used
[-Wunused-function]
996 | static void *qm_strnstr(const void *b1, int l1, const void *b2, int l2)
| ^~
Perhaps the definition
Social Boh via sr-users writes:
> so I have 3 lcr_rule_target use the same
> lcr_rule entry but 3 different Gateways and priority. So the order of
> rules would be longest Request-URI (same) and the priority but the
> result is:
>
> added matched_gws[0]=[3, 5, 200, 2193562]
> added
elhar.mohamed--- via sr-users writes:
> Can you please give more explanation ? I'm not sure I understand what
> you want to tell !
Read, for example, this article:
https://nickvsnetworking.com/enum-dns-based-call-routing/
-- Juha
__
elhar.mohamed--- via sr-users writes:
> I'm using the Kamailio version 5.7.x, I didn't find in the module
> "enum.so" any option that allow to connect to a remote ENUM server.
ENUM lookup is normal DNS lookup.
-- Juha
__
Kamailio - Users
harneet singh writes:
> "A gateway matches a request if user part of Request-URI matches "prefix",
> caller URI matches "from_uri" pattern,* caller URI userpart matches mtree
> with "mt_value"*, and callee URI matches "request_uri" pattern in a tuple
> that is associated with the gateway."
>
>
In my opinion is not a good idea that you need to restart Kamailio each
time there is a change in LCR configuration. Better to make the changes
directly to the DB tables after initial load from cvs.
-- Juha
__
Kamailio - Users Mailing List
harneet singh writes:
> Can someone point to a sample as to how we can *load the LCR Module tables*
> namely the following at startup from a csv file or any other
> mechanism.
You could import cvs files to those tables before starting Kamailio.
DuckDuckGo gave this example:
Daniel-Constantin Mierla writes:
> I found a related patch that was not backported -- I just pushed to 5.6
> branch a bunch of commits, including that one. Try again with latest 5.6
> branch and report if there is still some issue.
Daniel,
Thanks, in lab tests the leak was gone. Will try in
Daniel-Constantin Mierla writes:
> is it the latest stable point version 5.6.2, or the latest version from
> branch 5.6?
Latest from 5.6. I just built new Debian package like this:
MEMDBG=1 $(MAKE) FLAVOUR=kamailio cfg prefix=/usr cfg_prefix=$(BASEDIR) ...
-I does not show DBG_QM_MALLOC.
In latest stable K release, we noticed pkg memory leak (pgk memory usage
increases by each processed call). It turned out that the leak goes
away if acc module cdr_enable is not enabled.
Could be a bug in dialog or acc module. Any debug instructions if the
bug is not obvious?
-- Juha
Daniel-Constantin Mierla writes:
> Grab the gdb output for:
>
> list
>
> p *rule
>
> p *pl
Here:
(gdb) list
2325 in lcr_mod.c
(gdb) p *rule
Cannot access memory at address 0x383734313030
(gdb) p *pl
$1 = {rule_id = 0, prefix = '\000' , prefix_len = 5,
from_uri = '\000' , from_uri_len
Daniel-Constantin Mierla writes:
> has anyone experienced issues with Kamailio running on Debian 11
> Bullseye?
I have been running K on Debian 11 without issues, but not in high
volume production environment.
-- Juha
__
Kamailio - Users
rtpengine module README tells this about module dependencies:
3.1. Kamailio Modules
The following modules must be loaded before this module:
tm module - (optional) if you want to have rtpengine_manage() fully
functional
Looks like this is not correct. If Kamailio connects to
Daniel-Constantin Mierla writes:
> for the records, I just looked in cfg.lex and the following tokens are
> defined to have the same meaning:
>
> YES "yes"|"true"|"on"|"enable"
>
> NO "no"|"false"|"off"|"disable"
>
> By matching the token YES the parser returns 1 and NO
Wiki tells:
dns_srv_lb = yes | no (default no)
and doc/tutorials/dns.txt tells:
dns_srv_lb = on | off
Which one is correct or does it matter?
-- Juha
__
Kamailio - Users Mailing List - Non Commercial Discussions
*
> Daniel-Constantin Mierla writes:
>
> Have you tested the usual cases as well? e.g., tls-to-tls, udp-to-udp,
> ... I don't expect problems, just double-checking. If all ok, then it
> will be backported.
I tested all tcp, tls, and ws combinations and record routing worked
fine. My sip proxy does
Daniel-Constantin Mierla writes:
> Can you try the latest master (or the last commit backported to your
> local branch)? Maybe I nailed down with one more condition in the
> core.
Now two r-r headers are added without
modparam("rr", "enable_double_rr", 2)
and bye work fine.
Can the change be
Daniel-Constantin Mierla writes:
> Probably the code that needs to be changed is in the core, where the
> message is built (msg_translator.c). rr module adds second conditional
> lump for record route, but at that stage is not aware what is going to
> be the final target address.
OK.
> One more
Should I create a bug issue to GitHub about this? I looked at
rr/record.c, but could not figure out, what needs to be changed.
-- Juha
-
> I noticed that when jsSIP UA that has registered over wss calls another
> SIP UA
Daniel-Constantin Mierla writes:
> this should be fixed indeed, can you try and see if setting next
> modparam helps for the moment?
>
> modparam("rr", "enable_double_rr", 2)
That caused two r-r headers to be inserted:
INVITE sip:foo-0x793ee87a90@10.158.141.103:38378;transport=tls SIP/2.0
I noticed that when jsSIP UA that has registered over wss calls another
SIP UA that has registered over tls, record_route() adds only one Route
URI to outgoing INVITE (example below). This causes BYE to fail.
This issue may be caused by the fact that both UAs register over the
same Kamailio tls
Mojtaba writes:
> Would you please let me know about what version of sems you use?
> Please tell me more about it.
Master branch of https://github.com/sems-server/sems.
-- Juha
__
Kamailio - Users Mailing List - Non Commercial Discussions
Mojtaba writes:
> ./core/AmDtmfDetector.cpp:768: undefined reference to `dtmf_rx'
That is defined in libspandsp. The control file below works for me in
Debian Buster.
-- Juha
Source: opensipg-sems
Section: net
Priority: optional
Maintainer: Juha Heinanen
Build-Depends: debhelper (&
Daniel-Constantin Mierla writes:
> Now, for TCP, I expect that the connection is not established if the
> lower layers forbid it, so there should be no real data traffic on it.
> If you list tcp connections with rpc command, do you see the one you
> noticed traffic for using ngrep but Kamailio
Is it somehow possible that ngrep shows incoming INVITE arriving over
TCP to Kamailio's listening address and port, but there is no debug
trace of the request (e.g. receive_msg(): --- received sip message ...)
in syslog?
-- Juha
__
Dmitry Sinina writes:
> Currently https://github.com/yeti-switch/sems supports zrtp as well as
> srtp-dtls and srtp-sdes. But you are right, old applications like sbc
> and dsm requires modifications to run.
What do you mean by "old"? sbc and dsm apps are much younger that many
others.
--
Terry Tailor writes:
> I add check before adding alias
>
> if($(ct{param.value,alias}) == $null) {
> }
>
> It's seems working.
Contact header can contain name-addr, not just addr-spec.
-- Juha
__
Kamailio - Users Mailing List - Non
Transformations (e.g. nameaddr.uri and uri.param.name) on $ct are your
friends.
-- Juha
__
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not
E. Schmidbauer writes:
> Does SEMS support ICE for media negotiation?
If I remember correctly, the answer is "no". ICE is "new" stuff that
has not been added to sems.
-- Juha
__
Kamailio - Users Mailing List - Non Commercial Discussions
Dmitry Sinina writes:
> There is also SEMS forked by yeti-switch project
> https://github.com/yeti-switch/sems It has a lot new features but it is
> not fully compatible with old modules.
Last time I checked, yeti-switch/sems does not have sbc app (at least
not with that name), I had problems
David Villasmil writes:
> I’m using freeswitch in a very simple way, it receives a call, makes an api
> http request, and based on the response does some prefixing, etc. it also
> provides simple conferencing (three-way call) and provides a very detailed
> CDR.
>
> I’m wondering if I could
Daniel-Constantin Mierla writes:
> > Public sems was abandoned years ago.
>
> Maybe abandoned by initial developers, also not getting many new
> features. Otherwise, I noticed Juha Heinanen is more or less maintaining
> the public version of SEMS. Maybe he can comment on
Henning Westerholt writes:
> One related question, the last “official” release 1.6 of sems was in
> 2015 (at least in public github). Are people just using the
> development version in production then, also also just maintain their
> own private fork?
The "development" version (master) of
Daniel-Constantin Mierla writes:
> Probably it hit end of lifetime:
>
> *
> https://www.kamailio.org/docs/modules/stable/modules/tm.html#tm.p.max_inv_lifetime
>
Yes, 3 minutes matches well with 180 sec.
> There is also (iirc) a hard cleanup of hung transactions, if a module or
> script
Syslog showed many mysql/accounting related error between the time the
response arrived to proxy and when proxy crashed (example below). So
perhaps accounting failure delayed processing of the reply. pp Don't
know the reason for the myslq problems.
-- Juha
Jul 2 06:06:51 rox2
Daniel-Constantin Mierla writes:
> Transactions seems to be destroyed. Can you find out how long it took
> from the moment the reply was received and the crash happened?
It turned out that ngrep was available. It showed that reply
T 2021/07/02 06:07:02.069728 edgeproxy:5060 -> proxy:5060 [AP]
Daniel-Constantin Mierla writes:
> Transactions seems to be destroyed. Can you find out how long it took
> from the moment the reply was received and the crash happened?
Can be difficult to find when 486 Busy Here was received, because this
Kamailio instance is not configured to log replies and
Sergey Safarov writes:
> s = 0xef41e788a0679800 0xef41e788a0679800>
> len = -1685145520
>
> you can check
> https://github.com/kamailio/kamailio/issues/2788
> https://github.com/kamailio/kamailio/issues/2736
>
> Here changed memory handling
> You can try the current master or
Kamailio 5.5 crashed when sending reply (bt full below). Before the
crash there had been several mysql related error messages ("Lost
connection to MySQL server during query" and "Too many connections") in
syslog when async worker tried to insert accounting data. So perhaps
this core dump has
Shahid Hussain writes:
> Following are the REGISTER and response messages. Is it possible to
> confirm the JSSIP client has full implementation of SIP outbound?
Looks like it if you define two sockets.
-- Juha
__
Kamailio - Users Mailing
Due to other tests, I had missed baresip account's ;outbound paramater.
Once I added it, also reg-id was added.
-- Juha
WSS 192.168.43.160:50442 -> 192.168.43.160:5061
REGISTER sip:test.tutpro.com SIP/2.0
Via: SIP/2.0/WSS 127.0.0.1:9;branch=z9hG4bK5a4ad01f9164d358;rport
Contact:
Olle E. Johansson writes:
> Full support for SIP outbound (using REG-id when registering etc).
> Last time I looked we did not have all nuts and bolts for it, but
> let’s give it a try.
Yes, reg-id is missing from contact. It would be good to add so that
sip proxy can detect if registration is
Olle E. Johansson writes:
> > Have you checked baresip?
>
> I don’t recall baresip having a full SIP outbound implementation.
baresip is able to register with two outbound proxies and supports gruu
(below). What else is needed?
-- Juha
#
TLS 192.168.43.160:49556 -> 192.168.43.160:5061
Olle E. Johansson writes:
> Full implementation of SIP outbound is the only solution close to
> solving this problem in the IETF standards.
> However, I have seen no single SIP client that have implemented this,
> even though Kamailio supports
> it on the server side. The idea is that you
Shahid Hussain writes:
> Would like to know what is the recommended solution for this problem using
> alias or is it a limitation of using alias?
Maybe a limitation. Try with SIP User Agents that support gruu and thus
identify themselves using sip.instance.
-- Juha
To Barry: I have never shown any mos code for copying. So you must
have mixed people up.
I have never used dialog module, since I don't believe it is the job of
sip proxy to deal with dialogs.
I just did a simple test where placed the xinfo call after
rtpengine_delete() call and got to syslog:
I don't know if it matters, but in modparams you prefix the avp names
with "s:", and don't do it in the xlog call.
-- Juha
__
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users@lists.kamailio.org
Important: keep the
Marrold writes:
> Any suggestions appreciated.
>
> # - presence params -
> modparam("presence", "db_url", DBURL)
> modparam("presence", "db_update_period", 20)
> modparam("presence", "clean_period", 60)
> modparam("presence", "local_log_facility", "LOG_LOCAL3")
> modparam("presence",
Thanks to Daniel who patched topos/topos_redis code, topos now works
also in situations where requests spiral through the same proxy twice,
for example: A - P1 - P2 - P1 - B.
-- Juha
__
Kamailio - Users Mailing List - Non Commercial
Now I have MEMDBG=1 and lots of these kind of messages show up when
Kamailio fails to start due to sqlpos failing to connect to server:
Apr 26 18:06:30 edge /usr/bin/edge-proxy[8548]: CRITICAL:
[core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer
(0x7f7c80b347b0), called
Daniel-Constantin Mierla writes:
>
> On 26.04.21 11:02, Juha Heinanen wrote:
> > Daniel-Constantin Mierla writes:
> >
> >> Is your kamailio compiled without defining DBG_QM_MALLOC (which should
> >> be on by default)
> > Yes, I have not d
Daniel-Constantin Mierla writes:
> Is your kamailio compiled without defining DBG_QM_MALLOC (which should
> be on by default)
Yes, I have not defined DBG_QM_MALLOC.
-- Juha
__
Kamailio - Users Mailing List - Non Commercial Discussions
*
In config file I have:
debug=2
mem_summary=0
Still I get 3400+ memory related syslog message when Kamailio terminates
due to sqlops not been able to connect to mysql server.
According to core cookbook, memdbg and memlog should not be active when
their values are greater than debug value (they
Daniel-Constantin Mierla writes:
> Can you try now with latest git master branch and database storage? The
> logs suggested the wrong profile was used on PRACK reply on P1 when
> returning to A-side.
Thanks, will test ASAP.
-- Juha
___
Kamailio (SER)
Daniel-Constantin Mierla writes:
> update: last evening I pushed a commit to topos_redis, I hope now it
> behaves like when using db backend related to provisional replies.
We tried this morning with latest master and unfortunately P1 still
rejects PRACK with 404 when topos is using redis.
--
Daniel-Constantin Mierla writes:
> This has nothing to do with the dialog, the fact here is that topos was
> not designed for spirals, as I said in one of the previous emails. I am
> trying to fix the missing parts to make it work, if you can provide
> pcap/logs.
Can I email them to you
Daniel-Constantin Mierla writes:
> Hmm ... the issue seems to be related to missing record-route list for
> callee side in the transaction record.
>
> I do not have a test bedwhere I can reproduce during the next days,
> would it be possible for you to use topos with db backend (mysql)
> instead
Daniel-Constantin Mierla writes:
> Can you try with latest master branch? I pushed a commit to topos
> module.
Tried with latest master and the following in-dialog code:
if (!loose_route_mode("1")) {
if (is_method("ACK")) {
if (t_check_trans()) {
Daniel-Constantin Mierla writes:
> The 404 is not sent from the C code of the topos module, can you
> identify what are the cases in your config when a 404 is replied? PRACK
> should have To-tag, so it should via requests within dialog branch.
Yes, 404 is sent from the script:
if
Sorry, but it turned out that in calls where B replies first with "183
Session Progress" and which A acknowledges with PRACK request, P1 is not
able to forward the PRACK, but responds with "404 Not found".
I cannot reproduce this in my test environment, because I don't have a
SIP UA that uses
Daniel-Constantin Mierla writes:
> What is the value for connect_mode modparam?
>
> https://www.kamailio.org/docs/modules/stable/modules/sqlops.html#sqlops.p.connect_mode
It is not set, i.e., has default value 0.
-- Juha
___
Kamailio (SER) - Users
I noticed that Kamailio produces huge (3400+) number qm_free() syslog
messages if sqlops fails to connect to database. Don't know if it is
intentional.
-- Juha
...
Apr 19 18:02:40 edge /usr/bin/edge-proxy[1467]: CRITICAL: [main.c:1716]:
main_loop(): Cannot fork
Apr 19 18:02:40 edge
Daniel-Constantin Mierla writes:
> It seems to be the problem of matching the R-URI of ACK to be myself
> (address of the server), because it is the Contact of the callee, which
> was replaced by 2nd topos processing.
>
> The solution should be to do only loose routing on the edge proxy doing
>
Daniel-Constantin Mierla writes:
> Can you reproduce with debug=3 in kamailio.cfg, send me all the logs
> messages (from the initial invite to ack) along with the pcap and the
> records in the database from the topos_d and topos_t table?
Syslog and pcap are in files
Daniel-Constantin Mierla writes:
> > In case of topology:
> >
> > A - P1 - P2 - P1 - B
> >
> > is the idea to use in P1 context "in" when initial request comes to P1
> > from A or B and context "out" when initial request comes to P1 from P2?
> >
> > Does context need to be set in replies too?
In case of topology:
A - P1 - P2 - P1 - B
is the idea to use in P1 context "in" when initial request comes to P1
from A or B and context "out" when initial request comes to P1 from P2?
Does context need to be set in replies too? If so, is reply context the
same as the corresponding request
Daniel-Constantin Mierla writes:
> If you need to do two different topology striping, one for each Porxy1
> steps, you have to try the development version and set different context
> for initial requests on Proxy1 steps. I didn't really test it for this
> use case, I needed context for some
Henning Westerholt writes:
> as there have been different changes to topology hiding modules in the
> last months, can you specify the exact minor version?
5.4.4
-- Juha
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
Test topology using K 5.4 where topos module is loaded in Proxy1:
A - Proxy1 - Proxy2 - Proxy1 - B
A sends INVITE, B responds with 183 Session Progress, and A sends PRACK.
The result is that PRACK starts to loop in second Proxy1 instance
instead of being forwarded to B.
If topos module is
It is possible to update value of max_while_loops dynamically in config
file?
For example, there could be a need to increase the max in some while
loop, but after the loop is done, decrease it again for other loops.
There exists an rpc command to do that, but I haven't found how to do it
in
This topic was discussed a few years ago, but then the issue was load
balancing between kamailio processes. It may be a problem if there is
lots of SIP traffic over a single TCP/TLS session between two SIP
proxies.
-- Juha
___
Kamailio (SER) - Users
Daniel-Constantin Mierla writes:
> The code initialize the parameter to execute both of them. Do you still
> have the outgoing event route in config? If yes, check maybe it does a drop.
I did the test again and now I got both messages to syslog when
event_mode is not set:
Mar 3 13:35:44 lab
I added
modparam("topos", "event_mode", 2)
and now event_route[topos:msg-sending] got executed with read $rd.
So looks like README has a bug in it.
-- Juha
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
I tried to skip topos stripping based on R-URI hostpart like this:
event_route[topos:msg-outgoing] {
xinfo(" at topos:msg-outgoing with $rd\n");
if ($rd == "example.com")
drop;
}
and got this to syslog:
Mar 2 18:35:59 lab /usr/bin/sip-proxy[22441]: INFO:
Daniel-Constantin Mierla writes:
> I think it does not matter the type of transport for the worker, likely
> the docs had udp because that's usually the first worker. Also, IIRC,
> sip specs mandate UDP support, but kamailio can start without.
Yes, SIP specs mandate UDP support, but if a sip
Alex Balashov writes:
> Because it's in the user part of the From URI, I believe you'll
> ultimately have to use {s.select}.
>
> But you can drill down to the part of the URI you need first:
>
> $(fU{nameaddr.uri}{uri.user}{s.select,1,;})
Or perhaps you can apply param list
Is there a way to execute event_route when all modules have been loaded
and Kamalio is ready to process requests?
I found this in core cookbook, but what if there is no udp sip worker
processes?
event_route[core:worker-one-init] - executed by core after the first
udp sip worker process
> SIP/2.0 200 OK
> Via: SIP/2.0/TLS 52.114.75.24:5061;branch=z9hG4bK6b5ac083
> Record-Route:
>
> Record-Route:
I have ;r2=on in both R-R headers. And also you have ;lr=on in one and
;lr in the other.
-- Juha
___
Kamailio (SER) - Users Mailing
For sure there can be R-R headers in 200 OK to Teams
Microsoft.PSTNHub.SIPProxy.
-- Juha
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
How about this?
https://github.com/kamailio/kamailio/pull/2643
-- Juha
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
I'm returning to this thread, since after some more testing, I found that
loose_route() does not (at least always) detect that a pair of route
headers denotes itself.
In config I have defined:
listen=tls:192.x.x.x:8005 name "ext_tls"
modparam("rr", "sockname_mode", 1)
and Route header looks
Björn Bylander writes:
> My problem is this: When the Perimeta SBC sends its first INVITE (I
> can't say anything about any succeeding INVITEs yet) it's added a
> Record-Route header with the "lr" parameter included which, as far as
> I can see makes Kamailio think it should use loose routing
1 - 100 of 373 matches
Mail list logo