hb9eue left a comment (kamailio/kamailio#3165)
Hi @kerozin
Some years later, using kamailio in production and having learned *a lot* I
don't think this is a bug, but just how kamailio works and how you are supposed
to use stuff.
One very important think I learned regarding that issue (and mor
Thank you Henning.
I just tested with modparam("rr", "ignore_sips", 1) and indeed this solved the
issue. NAT detection creates an alias that points to TLS which then causes the
connection still using TLS even if the UAC used sips without transport
attribute.
--
Reply to this email directly or
Closed #4092 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4092#event-15808511239
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio - Development
### Description
Some UAC (notably Aastra Phones) use the sips: uri scheme without
;transport=tls when TLS is being used.
I observed kamailio 5.7.6 and most probably also 5.8.4 to insert the sips URI
in the wrong Record-Route header causing replies not to reach the destination.
Reproductio
Re-Tested and closing.
When paying attention to correctly populate the reg XAVP (watch out for if
statements and loops) then the values set seem to work as intended even in 5.7.
So basically usage error. Sorry, about not noticing this.
--
Reply to this email directly or view it on GitHub:
http
Closed #4068 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4068#event-15670875452
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio - Development
Ok I think I got my mistake. I probably failed to correctly set the xavp
on the first invocation it's reg=>element on any next one it's reg[0]=>element
to set in on the same level on the xavp stack.
Re-Testing on 5.8 and 5.7
--
Reply to this email directly or view it on GitHub:
https://github.
Interesting... I set more elements in the xavp and suddenly I get this:
```
# kamctl ul show 315996608 | grep Q
"Q": 0.45,
"Q": 0.45,
"Q": 0.45,
"Q": 0.45,
"Q": 0.45,
```
```
Dec 16 11:49:54 dev-sbc02 kamailio[122946]: INF
I re-visited max_contacts. This is getting logged. I'll re-test, but my main
interest is in forcing the Q value to ensure parallel forking.
```
Dec 16 11:42:09 dev-sbc02 kamailio[122908]: DEBUG: [1 315996608
585ee212b7dd1a5c 1941290511 REGISTER]registrar [save.c:466]:
reg_get_crt_max_contacts()
@linuxmaniac tried before, but again with 6.0.0:
```
xlog("L_INFO","*** OVERRIDING Q VALUE START\n");
$xavp(reg=>q) = 450;
if (!save("location")) {
sl_reply_error();
}
xlog("L_INFO","*** OVERRIDING Q VALUE END\n");
```
```
# kamctl u
Cranked up debug level:
```
xlog("L_INFO","*** OVERRIDING Q VALUE START\n");
$xavp(reg[0]=>q) = 450;
if (!save("location")) {
sl_reply_error();
}
xlog("L_INFO","*** OVERRIDING Q VALUE END\n");
```
```
# kamctl ul show 315996608 | gre
Oh, I just discovered the nightly builds, how convenient :-)
`version: kamailio 6.0.0-dev3 (x86_64/linux) ` <= is this corresponding to the
'master' you mentioned?
Same config as with 5.8.4.
```
# kamctl ul show | grep Q
"Q": -1,
"Q": -1,
Hi Daniel
First I checked with version: 5.8.4 (x86_64/linux) and this part which i
believe is the example config with just the line to set the xavp added:
```
# Handle SIP registrations
route[REGISTRAR] {
if (!is_method("REGISTER")) return;
if(isflagset(FLT_NATS)) {
### Description
I don't know if this is a bug, or if I missing some config requirements. I
mentioned the issue on the sr-user but did not get any comment.
In case serial (or combined serial/parallel) branching is wished, the q value
from the registered contact is considered to define the order
Ok, here we go with debug info:
```
# kamailio -v
version: kamailio 5.7.6 (x86_64/linux)
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE,
USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, MEM_JOIN_FREE, Q_MALLOC,
F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-
### Description
Goal: Build a destination set from multiple contacts gathered from multiple
registered AoR.
Situation: assumptions, observations:
* lookup() returns success there are registered contacts for each AoR.
* All contacts have same q value.
* lookup() can only be called for one AoR, t
Ping to remove stale label
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3656#issuecomment-2122055212
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (SER) -
Hmm, would modparam("dialog", "dlg_filter_mode", 1) fix the issue by not arming
the timer?
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3656#issuecomment-2042863292
You are receiving this because you are subscribed to this thread.
Message ID:
keep alive
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3656#issuecomment-1983264261
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (SER) - Development Mai
Unfortunately not as I'm working with an older version.
But the fix also was for the problem I found with my work-around.
A fix for the original issue that the node not in charge of a dialog might
delete it, is not solved by this fix.
So the issue that a timer is armed on a 'slave' node still is p
Just a short warning to anyone considering using my work-around. I experienced
dialog data corruption which could be due to this or maybe the duplicate key. I
reverted this change to my config.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/365
I guess I stumbled over some other issue or bug...
`[1 dialog 0f57b21a4ca92561-1371066@x.x.x.x 10 KDMQ]jansson
[jansson_funcs.c:47]: janssonmod_get_helper(): json error at line 1, col 3154:
duplicate object key near '"tag1"'`
Indeed, when looking at the JSON structure sent with dialog action 1,
> But still I can see scenarios where the current behaviour can cause problems.
> Imagine a small dialog timeout combined with SIP Session Timer keep-alive
> re-INVITEs. The proxy 1 would not expire the dialog, but proxy2 (which did
> not got the re-INVITE) would expire it.
I also came across
Situation: Two Kamailio nodes syncing dialog profiles via DMQ
Observation: When a dialog timeout is encountered, about half of the time, the
timeout is triggered on the peer node not handling the dialog preventing the
call to be correctly terminated and also leaving entries in the dialog databas
Closed #3655 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3655#event-11049140451
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (SER) - Devel
Somehow hit enter at wrong time.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3655#issuecomment-1824639111
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (
### Description
### Troubleshooting
Reproduction
Debugging Data
```
(paste your debugging data here)
```
Log Messages
```
(paste your log messages here)
```
SIP Traffic
```
(paste your sip traffic here)
```
### Possible Solutions
### Additional Informatio
27 matches
Mail list logo
