Thanks for having a look into it. We did compile with system memory and use
valgrind following the tips on dedicated page
https://www.kamailio.org/wiki/tutorials/troubleshooting/memory
Unfortunately this gave no more clues (though it is possible I used it badly
because it was the first time I
Thanks for your appreciated replies!
I do not think this is a firewall issue because when using `dig` command I get
no issues. Tried with two different sets of options:
* `dig +bufsize=512` : got `Truncated, retrying in TCP mode` then a correct
reply received through TCP
* or simple `dig` : in
### Description
DNS core resolver fails in returning a valid IP when there are too many SRV
results in the DNS reply.
It acts like if no records were found, so request is not relayed and a 478
reply is generated instead (in the example of a DNS name in $ru or $du).
### Troubleshooting
### Description
We noticed a PKG memory leak when using DMQ module's function
_dmq_bcast_message_ .
### Troubleshooting
Reproduction
Issue can be reproduced with configuration below.
* 3 Kamailio nodes each one listening on dedicated port 5070 for DMQ on their
private IP address.
* A
Daniel,
Thinking about it further, I would rather replace this block:
`if(ostate==DLG_STATE_CONFIRMED && sval==DLG_STATE_DELETED) {`
by this one:
`if(sval==DLG_STATE_DELETED) {`
Because if a dialog is changed to deleted state from a state < 4, it stays in
the dialog memory for no reason. I
- only handles active dialogs in state 4
- wipes out a given dialog callously
- no subcalls to dialog-ending functions
- dialog is then removed by the recurring cleaning function execution
- as discussed in sr-users in topic [Dialog] Removing entries from dialog
memory
Pre-Submission
Hi Daniel,
Thanks for the quick fix you proposed, really appreciate it.
I have to admit I didn't even think to try with port 0 for the advertise option!
But it does not seem to behave as I expect: _Via_ headers are still filled with
a port in my case.
I did some deep checks and maybe I am not
### Description
The `advertise` option in a `listen` parameter seems to only allow the
following syntax:
`advertise ip_or_host:port`
The `advertise ip_or_host` syntax is not allowed and gives the following error:
> CRITICAL: [core/cfg.y:3507]: yyerror_at(): parse error in config file
>
@jchavanton many thanks for your quick addition. Behavior is the one I meant.
Sorry for my late feedback.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
### Description
The recently-added **acc_json** module does not support the _multi_leg_info_
parameter from the main **acc** module.
### Expected behavior
**acc_json** module could add the extra leg info attributes in the JSON data,
as the **acc_radius** module already does. Behavior could be
10 matches
Mail list logo
